Requirements Gathering sometimes requires individuals or teams from client as well as service provider sides to get detailed and accurate requirements (Wikipedia). Assumptions The major assumption is that the information provided is everything that is required and that the information is accurate. Another assumption is that it has been proved that the development of a new system is economically feasible for the Health centre compared to the current system. The other assumptions are that the budget will be enough to develop the new system and the system chosen is the best out of all the possible system choices.
Gaps There are a lot of gaps in several areas. The user requirements are not described in details. The functional and non-functional requirements should be clearly defined and in detail. A feasibility report of the different choices available to the Health centre should be produced. From the report the best choice of the system to be developed should be made with the right justifications. Recommendation The user requirements should be well defined and in details.
The system development should be on time because if it takes longer the developed system may be obsolete. Timeline charts should be developed in order to make sure everything goes according to the schedule. At the end of this phase a decision needs to be made as to what software to use (Anonymous). References Anonymous, Analysis, retrieved on Sunday, May 23, 2010 from http://doit. ort. org/course/devinfosys/2. htm Wikipedia 2010, Systems Development Life Cycle, retrieved on Sunday, May 23, 2010 from http://en. wikipedia. org/wiki/Systems_Development_Life_Cycle