Software Process Cycle

Generally there are six different steps in the complete cycle:

• Selecting a team: The first step is to select all the team members. Everyone must be software professionals with sound knowledge in software engineering.
• The standard process maturity questionnaire is filled out by the representatives of the site that will be evaluated.
• In accordance with the CMM core process areas, the assessment team analyses the questionnaire results to determine the areas that call for additional investigation.
• The evaluation team visits the location to learn more about the software procedures used there.
• The evaluation team compiles a set of results outlining the organization’s software process’s advantages and disadvantages.
• In order to deliver the findings to the right audience, the assessment team creates a Key Process Area (KPA) profile analysis.

SCAMPI;

SCAMPI stands for Standard CMMI Assessment Method for Process Improvement. To fulfil the demands of the CMMI paradigm, the Standard CMMI Assessment Method for Process Improvement (SCAMPI) was created (Software Engineering Institute, 2000). Moreover, it is based on the CBA IPI. The CBA IPI and SCAMPI both have three steps.

1. Plan and become ready
2. Carry out the evaluation on-site
3. Report findings

The planning and preparation phase includes the following activities:

• Describe the scope of the evaluation.
• Create the assessment strategy.
• Get the evaluation crew ready and trained.
• Make a quick evaluation of the participants.
• CMMI Appraisal Questionnaire distribution
• Look at the survey results.
• Perform a preliminary document evaluation.

The onsite evaluation phase includes the following activities:

• Display the results.
• Execute the findings.
• Complete / end the assessment. 

Software Process Assessment is a disciplined and organized examination of the software process which is being used by any organization bases the on the process model. The Software Process Assessment includes many fields and parts like identification and characterization of current practices, the ability of current practices to control or avoid significant causes of poor (software) quality, cost, schedule and  identifying areas of strengths and weaknesses of the software.