We, the Andromeda team have followed a definite process in creating this HOPE system. We had gathered and discussed the requirements from lot of resources like web, by taking to elderly people who might use our system and based on our own experience from our grandparents and from the elderly people we had come across.
Any requirements which use the term shall indicate that that functionality is critical core functionality that will be implemented in the first version of the HOPE system. Other functionality that is identified by our requirements gathering process that is not considered critical core functionality and may be implemented instead in a later version of the HOPE system will be referenced using the word ‘will’.
The software process that we are using in this system is Spiral model. Change is inevitable in software projects so our process is designed to adapt to the changes and allow modification where necessary to the requirements and other documents.
For the implementation of HOPE system, we will follow the Spiral Model. The spiral model is a software development process combining elements of both design and prototyping-in-stages, in an effort to combine advantages of top-down and bottom-up concepts. This model of development combines the features of the prototyping and the waterfall model. The spiral model is intended for large, expensive and complicated projects. The spiral model combines the idea of iterative development with the systematic, controlled aspects of the waterfall model. It allows for incremental releases of the product, or incremental refinement through each time around the spiral. The spiral model also explicitly includes risk management within software development. Identifying major risks, both technical and managerial, and determining how to lessen the risk helps keep the software development process under control.