CMM Level 2 KPA’s CS 4320 Fall 2003. Requirements Management 1 Goals: – System requirements...

CMM Level 2 KPA’s

CS 4320

Fall 2003

Requirements Management 1

Goals:– System requirements allocated to software are

controlled using a baseline for engineering and management use.

– Software plans, products and activities are kept consistent with system requirements allocated to software.

System requirements allocated to software == software requirements

Requirements Management 2

Commitment to perform:– Project follows a written organizational policy for managing

software requirements.

Ability to perform:– For each project, responsibility is established for analyzing

the system requirements and allocating them to HW, SW or other system components.

– Allocated requirements are documented.– Adequate resources and funding are provided to manage

requirements.– People are trained for requirements management activities.

Software Project Planning

Goals:– Software estimates are documented for use in

planning and tracking a software project.– Software project activities and commitments are

planned and documented.– Affected groups and individuals agree to their

commitments related to the project.

Software Project Planning

Commitment to Perform– A software project manager is designated to be

responsible for negotiating commitments and developing the project’s SDP.

– The project follows a written organizational policy for planning a software project.

Software Project Planning

Ability to perform– A documented and approved SOW exists for the

software project.– Responsibilities for developing the SDP are assigned.– Adequate resources and funding are provided for

planning the software project.– People involved in planning are trained in estimating

and planning procedures applicable to their area of responsibility.

Software Project Tracking and Oversight

Goals:– Actual results and performances are tracked against

the software plans.– Corrective actions are taken and managed to

closure when actual results and performance deviate significantly from the software plans.

– Changes to SW commitments are agreed to by the affected parties.

Commitment to perform:– A manager is designated to be responsible for the project’s

activities and results.– The project follows a written policy for managing the software

project. Ability to perform:

– An SDP is documented and approved.– The manager explicitly assigns responsibility for SW work

products and activities.– Adequate resources are provided for tracking project.– Managers trained in managing technical and personnel aspects

of the project.– First line managers receive orientation in technical aspects of the

software project.

Software Project Tracking and Oversight

Subcontract Management

Goals:– The prime contractor selects qualified software

subcontractors.– The prime contractor and the software subcontractor

agree to their commitments to each other.– The prime contractor and the software subcontractor

maintain ongoing communications.– The prime contractor tracks the software

subcontractor's actual results and performance against its commitments.

Software Quality Assurance

Goals:– Software quality assurance activities are planned.– Adherence of software products and activities to

the applicable standards, procedures, and requirements is verified objectively.

– Affected groups and individuals are informed of software quality assurance activities and results.

– Noncompliance issues that cannot be resolved within the software project are addressed by senior management.

Commitment to perform:– The project follows a written organizational policy for

implementing SQA. Ability to perform:

– A group that is responsible for coordinating and implementing SQA for the project exists.

– Adequate resources and funding are provided for performing the SQA activities.

– Members of the SQA group are trained to perform their SQA activities.

– The members of the software project receive orientation on the role, responsibilities, authority, and value of the SQA group.

Software Quality Assurance

Software Configuration Management

Goals:– Software configuration management activities

are planned.– Selected software work products are identified,

controlled, and available.– Changes to identified software work products

are controlled.– Affected groups and individuals are informed of

the status and content of software baselines.

Commitment to perform:– The project follows a written organizational policy for

implementing SCM. Ability to perform:

– A board (CCB) having the authority for managing the project's software baselines exists.

– A group that is responsible for coordinating and implementing SCM for the project exists.

– Adequate resources and funding are provided for performing the SCM activities.

– Members of the SCM group are trained in the objectives, procedures, and methods for performing their SCM activities.

– Members of the software engineering group and other software related groups are trained to perform their SCM activities.

Software Configuration Management

So What?

Hey, where’s:– Design Patterns– Architecture– UML– Teamwork– Put your favorite thing here….

Next Time

Level 3….