CMMI Sample Clauses

CMMI. As part of the maturity of the market many clients are demanding more quality to their IT providers. Also IT companies have realized that the institutionalization of the software process provide maturity to the company and they can reduce costs by non repeating tasks or delivering products according to the requirements needs, feasible in the practice and without bugs. Software is becoming a fundamental part of any company’s processes and therefore those companies want to be sure that the IT provider has certain guarantee to provide a quality product. In addition, many bad experiences from the governments buying software have become into a new trend where the public organism ask for these kinds of guarantees to work from them. This is the reason because CMMI is becoming almost a de facto standard. Something similar is happening in the automotive domain where OEM needs to be sure that the different pieces of software integrated and provided by different users work perfectly. Even more the OEM itself used to appraise the provider’s software processes during the project and also gets involved in some phases of the development provider to ensure the processes are being fulfilled and the product artefacts have being done correctly. For example, in some innovative projects the project starts with many doubts that are resolved during the project, which means that the OEM has to get involved to learn from the taken decisions and this also means the review of process and artefacts. Because of those reasons the different software improvement model like (SPICE, Spice for Space, AutomotiveSpice, CMMI) are becoming very popular between the IT companies. eDIANA Task 6.3 has analysed one of this standards which covers a generic quality maturity model, CMMI for development. With this model the most common software process improvement method will be analysed.