Topic

Design a case study to show verification and validations which can be used at each level of CMM
Submitted To
Mr. Sarabjit Kumar

Submitted By
Umer Faruque 11104662 RD1E25A

1| Page

Index
Sr. No.
1. 2. 3. 4. 5. 6. 7.

Topic Name
Objective Introduction Importance of Validation and Verification Role of CMM Levels in Validation and Verification Difference between 5 levels Future Scope of CMM levels Validation and Verification References

Page No. 2 3 5 5 6 6 7

Objective
Validation and verification are mandatory activities that software companies must perform when developing software products with a high degree of quality. Currently, more companies become aware that adopting CMM (the software process maturity model developed by the Software Engineering Institute) can be a way to develop quality software. However, some companies are resistant to adopt CMM maturity levels because they do not considerer this maturity level a benefit since its implementation is expensive and does not cover the validation and verification efforts. The simultaneous adoption of CMM maturity level 2 with validation and verification process areas (from maturity level 3) lacks some methodological recommendations, since some dependencies exist between those two CMM maturity levels.

Requirements
N.A.

2| Page

Introduction
The Capability Maturity Model (CMM) developed at the Software Engineering Institute is based on the premises that maturity indicates capability and to obtain continuous process improvement it is much better to take small evolutionary steps rather than revolutionary innovations.

Fig-five levels of CMM Initial : Characterised by an ad hoc process. Success depends on individual effort. Repeatable : Basic project management processes track cost, schedule and functionality. This process discipline enables the repetition of earlier successes on similar projects. Defined : Management and engineering activities in the software process are documented, standardised and integrated into an organisation-wide software process. Managed : Detailed measures are collected, both for the software and for product quality. Optimising : Continuous process improvement results from quantitative feedback from the process and from testing new ideas and technologies.

3| Page

Capability Maturity Model (CMM) is a process improvement approach that provides organizations with the essential elements of effective processes that ultimately improve their performance. CMM can be used to guide process improvement across a project, a division, or an entire organization CMM in software engineering and organizational development is a trademarked process improvement approach that provides organizations with the essential elements for effective process improvement. It can be used to guide process improvement across a project, a division, or an entire organization CMM (Capability Maturity Model Integration) is a software development standard from the Software Engineering Institute (SEI). CMM is composed by a set of software development process guidelines and is used to improve the quality of the software and its delivery. Using CMM, SEI addresses practices that companies can use as a guideline for process improvement. It can be seen as a collection of best practices that could be followed to improve the quality of products. However, there are organizations that do not adopt CMM - in particular the Maturity Level 2 -- and the main reasons they give is that: the company is small, the cost to implement CMM is high, they use another Software Process Improvement (SPI) and they not see a clear benefit in using it. Several companies do not want do adopt exclusively CMM Maturity Level 2 because they are mainly interested in the Engineering processes, which is not the focus of this Maturity Level . Since Maturity Level 2 Process Areas are mainly focused in the project management and support processes, most companies tend to consider that the implementation of Maturity Level 2 does not bring significant benefits to compensate the corresponding cost and time overheads. Companies recognize benefits only in the implementation of Process Areas of Maturity Level 3. The software testing - Validation and Verification - V&V- phase is one of the most important in the software development life cycle of many projects. Companies are becoming more aware of the important role that V&V plays in the production of high quality software. CMMI for Acquisition v1.2 was released in November 2007. It addresses supply chain management, acquisition, and outsourcing processes in government and industry. CMM for Services v1.2 was released in February 2009. It addresses guidance for delivering services within an organization and to external customers. CMMI Product Suite (includes Development, Acquisition, and Services), v1.3 is expected to be released in 2010. CMM Version 1.3-Plans for the Next Version. Validation-The purpose of validation is to demonstrate that a product or product component fulfils its intended use when placed in its intended environment. Verification-The purpose of verification is to ensure that selected work products meet their specified requirements.

4| Page

Fig-DFD for verification and validation in CMM levels

Importance of Validation and Verification

Validation and Verification are very important for companies that develop large scale software products due to the size of the solutions. So, those companies have to demonstrate that the product or product components accomplish its intended use when placed in its intended environment, as well as ensuring that selected work products meet their specified requirements. Companies that develop software at a large scale become aware that implementing CMM can be a good choice for developing and delivering software with a high degree of quality. But if a company that is applying for CMM Level 2 assessment must take into consideration that the validation and verification efforts are not considered for that level. This level of maturity is only concerned if an organization ensures that in their projects the requirements are managed and their processes are planned, performed, measured, and controlled. Therefore, it is important for those companies to have the possibility of simultaneously implementing CMMI Level 2 and the Validation and Verification Process Areas.

Role of CMM Levels in Validation and Verification

Level 1 - characterized by chaos, periodic panics, and heroic efforts required by individuals to successfully complete projects. Few if any processes in place; successes may not be repeatable.

5| Page

Level 2 - software project tracking, requirements management, realistic planning, and configuration management processes are in place; successful practices can be repeated. Level 3 - standard software development and maintenance processes are integrated throughout an organization; a Software Engineering Process Group is is in place to oversee software processes, and training programs are used to ensure understanding and compliance. Level 4 - metrics are used to track productivity, processes, and products. Project performance is predictable, and quality is consistently high. Level 5 - the focus is on continuous process improvement. The impact of new processes and technologies can be predicted and effectively implemented when required. Perspective on CMM ratings: During 1997-2001, 1018 organizations were assessed. Of those, 27% were rated at Level 1, 39% at 2,23% at 3, 6% at 4, and 5% at 5. The median size of organizations was 100 software engineering/maintenance personnel; 32% of organizations were U.S. federal contractors or agencies. For those rated at Level 1, the most problematical key process area was in Software Quality Assurance.

Difference between 5 levels

Level 1. Initial the organization is characterized by an ad hoc set of activities. The processes aren't defined and success depends on individual effort and heroics. Level 2. Repeatable At this level, basic project management processes are established to track costs, to schedule, and to define functionality. The discipline is available to repeat earlier successes on similar projects. Level 3. Defined All processes are documented for both management and engineering activities, and standards are defined. Level 4. Managed Detailed measures of each process are defined and product quality data is routinely collected. Both process and products are quantitatively understood and controlled. Level 5. Optimizing Continuous process improvement is enabled by quantitative feedback from the process and from piloting innovative ideas and technologies. There are 3 popular ISO standards that are commonly used for SW projects. They are 12270, 15540, and 9001 . For CMM, the latest version is 1.1, however, it is already considered a legacy standard which is to be replaced by CMMI.

Future Scope of CMM levels Validation and Verification N.A.

6| Page

Reference
1. http://www.scielo.br/scielo.php?pid=S1678-58782010000100002&script=sci_arttext 2. http://my.safaribooksonline.com/book/software-engineering-anddevelopment/cmmi/0321154967/engineering-process-areas/ch07lev2sec11 3. http://ieeexplore.ieee.org/xpl/login.jsp?tp=&arnumber=5298751&url=http%3A%2F %2Fieeexplore.ieee.org%2Fxpls%2Fabs_all.jsp%3Farnumber%3D5298751 4. http://my.safaribooksonline.com/book/software-engineering-anddevelopment/cmmi/0321154967/engineering-process-areas/ch07lev2sec11 5. http://vectorstudy.com/management-theories/capability-maturity-model 6. http://sqa.fyicenter.com/FAQ/TestingTechniques/What_s_the_role_in_CMM_Level_in_Testing_What_s.html 7. www.dtic.mil/ndia/2005systems/tuesday/olson.pdf 8. http://www.bioinfo.in/uploadfiles/13111284371_1_1_BIOINFO_SC.pdf
9. http://www.cse.dcu.ie/essiscope/sm5/approach/cmm-2.html

7| Page