Scribd
Upload
331 views23 pages

Requirement Management and CMM

The document discusses requirements management and the Capability Maturity Model (CMM). It defines requirements management as the process of documenting, analyzing, tracing, prioritizing and agreeing on requirements and then controlling change and communicating to stakeholders. It also outlines the key activities in requirements engineering like elicitation, analysis, negotiation and validation. Finally, it describes the five levels of maturity in the CMM for progressively improving an organization's software development processes.

Uploaded by

Huma Ashraf
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
331 views23 pages

Requirement Management and CMM

The document discusses requirements management and the Capability Maturity Model (CMM). It defines requirements management as the process of documenting, analyzing, tracing, prioritizing and agreeing on requirements and then controlling change and communicating to stakeholders. It also outlines the key activities in requirements engineering like elicitation, analysis, negotiation and validation. Finally, it describes the five levels of maturity in the CMM for progressively improving an organization's software development processes.

Uploaded by

Huma Ashraf
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 23

Requirement Management and

Capability Maturity Model (CMM )


By
Muhammad Yousaf Mushtaq
MS (Software Engineering)

1
Requirements management
• The process of managing changes to the
requirements for a system •
OR
• The process of managing changes to the
requirements for a system • Reasons for
changes in requirements and how to manage
them.

2
Requirements management

3
• Requirements management is the process of
documenting, analyzing, tracing, prioritizing
and agreeing on requirements and then
controlling change and communicating to
relevant stakeholders. It is a continuous
process throughout a project

4
. Requirements Engineering Activities-1
• Requirements Elicitation
• Requirements Analysis
• Negotiation Requirements Specification
• Requirements Validation
• User Needs,
• Domain Information,
• Existing System Information, Regulations,
Standards, Etc.
• Requirements Document
• Agreed Requirements

5
. Requirements Engineering Activities 2
• Requesting changes to the baselined
requirements,
• Performing impact analysis for the requested
changes,
• Approving or disapproving changes,
• Implementing the approved changes
• Measure the progress
• Managing the logical links between individual
requirements and other project work products

6
. Requirements Engineering Activities 3

• It is the process of
– documenting,
– analyzing,
– tracing,
– prioritizing and
– agreeing on requirements and then controlling
change and
– communicating to relevant stakeholders. It is a
continuous process throughout a project.

7
Requirements Baseline
• Set of functional and non-functional
requirements that the development team has
committed to implement in a specific release
• Subsequent changes can be made only
through the project's defined change-control
process

8
Why Requirements management
Important ?
• Requirements management play important role
in success of software.
• It manages changes to requirements and
maintains traceability in requirements documents
• Requirements of a system change to reflect the
changing needs of stake holders.
• They also change due to change in environment,
business plans and laws

9
Legacy systems
• Legacy systems are old software systems that
are used by an organization.
• Usually, they rely on obsolete technology but
are still essential to the business.
• It may not be cost-effective to rewrite or
replace these systems and many organizations
would like to use them in conjunction with
more modern systems

10
Legacy systems
• A legacy system, in the context of computing,
refers to outdated computer systems,
programming languages or
• Application software that are used instead of
available upgraded versions. ...
• But in reality, most organizations
have legacy systems - to some extent.

11
Example Legacy Systems
• Operating systems with "legacy support" can
detect and use older hardware.
• The term may also be used to refer to a
business function; e.g.
• A software or hardware vendor that is
supporting, or providing software
maintenance, for older products

12
Capability Maturity Model (CMM)
• The Capability Maturity Model (CMM) is a
methodology used to develop and refine an
organization's software development process.
• The model describes a five-level evolutionary
path of increasingly organized and
systematically more mature processes

13
Five levels of the CMM:
• Level 1 - Initial. Processes are usually ad hoc
and the organization usually does not provide
a stable environment. ...
• Level 2 - Repeatable. Software development
successes are repeatable. ...
• Level 3 - Defined. ...
• Level 4 - Managed. ...
• Level 5 - Optimizing

14
15
16
17
18
19
20
21
22
23

You might also like