Software Project Maturity

984 Words4 Pages
Software Project Management Question 1 Maturity in software project management refers to the frequency of failure due to faults in a software product, the implication being that the more the software has been used, the more faults will have been uncovered and removed. How does the level of project maturity influence the quality of software? Discuss briefly. The continuous discovery of errors on the software during project maturity helps developers to minimize errors and faults. This will turn lead to minimal software maintenance with improved software quality. How does the level of project maturity influence the success of projects? Discuss briefly. When project maturity is conducted at each project phase, errors can be identified at early stages and be rectified before the final stages of the software project. This prevents and minimizes risks and potential errors with regards to the final software products. Question 2 CMMI Overview Initially developed by the Software Engineering Institute (SZEI) to assess the capability of contractors from whom the DoD buy software. The CMMI was introduced to bring together models profuced for different environments into a single integrated framework. ISO 15504 Overview It is a standard for process assessment that shares many concepts with CMMI. Like CMMI, the standard provides guidance on the assessment of software development processes by comparing the benchmark or process reference model which present the ideal development life cycle. BS EN ISO 9001:2000 Overview Concerns/Disadvantages A British Standard Institution for quality management systems. The standard tries to ensure that a monitoring and control system to check quality is in place. It describes the fundamental features of a quality management systems and its terminology. Developers set down their own specifications and only have to maintain them

More about Software Project Maturity

Open Document