1 / x Verification CMMI Verification Hendrik van den Berge Kevin Mets.

1 / xVerification

CMMIVerification

Hendrik van den BergeKevin Mets

2 / x<Process Area>

Delete this slidein final version

Guidelines (remove in final version)• Use English language• Copy only the titles of the practices not the description from the

CMMI – use subpractices as guidance but do not discuss separately• Map CMMI terminology to project terminology (add to glossary)• Add explanatory slides as required• Add references to direct/indirect artifacts for each practice• Include descriptions/screen shots of artifacts• Make a first draft based on documentation of projects and results of

dream questions and add markers where information is missing• Use this draft in interview sessions to ask questions to the group or

discuss• Update final version with interview feedback• Ensure this presentation enables students to understand the

practices of this process area in the context of real projects• Do not forget the slide with Strengths and Opportunities for

Improvement• Check spelling

3 / xVerification

VerificationPurpose

Ensuring that the software meets the requirements Are we building it right? Tests, demonstrations, peer reviews...

4 / xVerification

VerificationSpecific Goals

SG 1 Prepare for verification SP1.1 Select work products for verification

All projects perform testing on their product. SP1.2 Establish the verification environment

All projects have done this Simulation environments, status pages Off-the-shelf packages for performance/stress testing, unit testing,

integration testing...

5 / x

Verification

Verification

SP1.3 Establish verification procedures and criteria All projects have verification procedures (usage of testing packages) Some projects set criteria, e.g “achieve 85% code coverage” Other projects could set similar goals

6 / x

VerificationSpecific Goals

SG 2 Perform peer reviews SP2.1 Prepare for peer reviews

All projects do this Meetings with “higher management”, product demos

SP2.2 Conduct peer reviews All projects to this (see above)

Verification

7 / x

Verification

SP2.3 Analyze peer review data Projects make decisions based on feedback gathered from meetings

Verification

8 / x

VerificationSpecific Goals

SG 3 Verify selected work products SP3.1 Perform verification

All projects perform testing and demonstrations. SP3.2 Analyze verification results

Some projects have evidence of test analysis Probably all projects do this internally

Verification

9 / xVerification

VerificationGeneric Practices GG 2

GP2.1 Establish an Organizational Policy Some groups have explicit guidelines. Example from “TultiMouch Multitouch Platform”: “Processes”:

…

Process and Product Quality Assurance

Dit gaat over alle acties die gebeuren/voorzien zijn voor het garanderen van de qualiteit van de gebruikte

processen en van het geleverde product.

Voor agile/extreme programming voldoen wij hier aan door gewoon:

- Tests te voorzien voor onze quality requirements, functional requirements.

- Per iteratie onze manier van werken te evalueren.

Het is de taak van de quality manager om ervoor te zorgen dat dit niet vergeten wordt.

…

10 / x

VerificationGeneric Practices GG 2(2)

GP2.2 Plan the Process Groups provide test plans Time is reserved to do the testing Demonstrations

Examples from “WAFL” and “Mashedup”:

Verification

11 / xVerification

VerificationGeneric Practices GG 2 (3)

GP2.3 Provide Resources All groups provide several resources Infrastructure

Testing frameworks (e.g. JUnit) Demo applications (e.g. demo from Hadra) Version control (e.g. Subversion) Software Project Management System (e.g. Trac)

Documentation Requirements (use cases, quality attributes, …) Test plans Tutorials State of the art (e.g. “State of the art: Mobile Testing” from “WAFL”)

Time

12 / x

VerificationGeneric Practices GG 2 (4)

GP2.4 Assign Responsibility Manager(s) to overview the verification process (and other processes)

E.g. Quality manager, Test manager, Process manager Individual responsibilities

E.g. from “TultiMouch Multitouch Platform”: “Development Guidelines”: Develop unit test together with the unit no commit in trunk if unit test fails

GP2.5 Train People Documentation and help is provided to aid in the verification process.

GP2.6 Manage Configurations Overview of test results. Version control for the documents, results, … Information available at central place (website).

Verification

13 / xVerification

VerificationGeneric Practices GG 2 (5)

GP2.7 Identify and Involve Relevant Stakeholders Interaction with internal stakeholders (team members, supervisors,…) No indication of interaction with external stakeholders (users, …) (?)

GP2.8 Monitor and Control the Process Meetings and demonstrations are used for evaluating and controlling the

process.

GP2.9 Objectively Evaluate Adherence No specific information about adherence. (?) Probably part of the meetings. (?)

GP2.10 Review Status with Higher Level Management Meetings with course supervisors. Internal group meetings with different managers present.

14 / xVerification

VerificationGeneric Practices GG 3

GP3.1 Establish a Defined Process The verification process is documented.

E.g. results, planning , … But no general verification processes are defined. (?) But this could be the result of the project.

GP3.2 Collect Improvement Information Experience (e.g. software project, appraisals) Sharing information (e.g. presentations, meetings)

15 / xVerification

VerificationProcess Assets

<insert screen shots or descriptions of artifacts demonstrating implementation of specific and generic practices for the Process Area>

Guidelines (remove in final version)• Make the presentation understandable for people not familiar with the

project(s)• Link to artifact references in discussion of Practices

16 / xVerification

VerificationFindings

Strengths Testing is a big part of every project. The importance of verification is

known.

Opportunities for Improvement Verification documentation could be more detailed and more integrated

with other documentation. Organizational policies are not very clear.

Proposed Actions ...

17 / xVerification

VerificationGlossary

CMMI Capability Maturity Model Integration

…

18 / xVerification

VerificationReferences

CMMI for Development version 1.2http://www.sei.cmu.edu/publications/documents/06.reports/06tr008.html

…