August
1997 QUESTION 2 Total Marks: 20 Marks |
Click here to access other
questions
SUGGESTED SOLUTIONS |
2. | (a) Who may request a systems development? | [1] | |
Management or an end user may request a systems development. | [1] | ||
(b) Due to time constraints a particular company undertook a systems development project in a hurry. The development team had to skip the preliminary investigation phase and go straight into analysis. Consider three aspects of a feasibility study, for each one show how by ignoring its impact the project could fail. Follow on by discussing how the three aspects might interact. | [8] | ||
A project request should be examined for feasibility in terms of | |||
Technical feasibility: The new system might require technology that the company does not have. | [2] | ||
Economic feasibility: The new system might cost too much to develop. | [2] | ||
Operational feasibility: Even if the new system is developed it might not have a market. | [2] | ||
(c) Nonetheless the project was a success and the development team managed to produce a viable system. Consider the case in which the company did undertake a preliminary investigation but whose conclusion was not approved by the management. Explain why this might be the case using your three aspects of the feasibility study to clarify your argument. | [6] | ||
A management decision will most likely be conservative. In terms of | |||
1. Technical feasibility: If the technology needs to be either developed or purchased than there is a need to become familiar with it and a greater opportunity for things to go wrong. Consequently, the management might consider that it is not worth taking this risk. | |||
[2 marks] | |||
2. Economic feasibility: It is usual to over-budget development projects as insurance for unforeseen events. In our case, the project might have had no glitches. | |||
[2 marks] | |||
3. Operational feasibility: The management would have to play it safe when considering how a proposed system might be accepted by the market two or more years hence. Consequently, they are unlikely to accept projects that look only promising. | |||
[2 marks] | |||
the purpose of parts (a) and (b) is to see whether students have acquired the ability to argue a case, consequently the marker should be generous in accessing the responses. | |||
(d) List the remaining stages and provide brief descriptions of the system design life cycle. | [5] | ||
The remaining stages of the SDLC: | |||
1. Requirements determination: involves finding out what takes place in the current system so as improve on it in the next version. | [1] | ||
2. Systems Design: involves determining how to construct the information system to best satisfy the document requirements. | [1] | ||
3. Systems Development: involves constructing the information system. | [1] | ||
4. System Testing: to ensure that the system is reliable and conforms to the specification outlined in the Systems Requirements Document. | [1] | ||
5. Systems Implementation and Evaluation: The system will be used in practice and feedback sought. | [1] |