| This research is aimed towards defining the quality of software in terms of requirements, stakeholder needs and most importantly on iterative analyses, which would produce a process by which the software quality can be improved with time. This would mean that the requirements would be dynamically updated, stake holder needs will be dynamically updated and the analyses iteratively updated.;By far and away, the most expensive re-engineering task in any system is the maintenance and restoration of complex software, Mazzuchi et al. [22]. In the opinion of the author, the most critical element in this design and implementation scenario is the inability to measure the software quality with enough acumen and confidence to implement an optimal solution. Herein lies the problem, there is a need to have a process by which the stakeholder can ensure a system which is optimal in quality and functionality within the cost and schedule. The model proposed in this research is aimed towards the development phase where the greatest changes in requirements and functionality occur, and it is imperative to make changes in the design early in the system implementation. |
