76 lines
4.2 KiB
Markdown
76 lines
4.2 KiB
Markdown
---
|
|
title: Requirements Management
|
|
created_date: 2025-02-19
|
|
updated_date: 2025-02-19
|
|
aliases:
|
|
tags:
|
|
---
|
|
# Requirements Management
|
|
|
|
Notes of the guide found [here](https://www.jamasoftware.com/requirements-management-guide/).
|
|
|
|
## Jama Requirements Management Guide
|
|
### Requirements Management
|
|
Process of gathering, analyzing, verifying and validating the needs and requirements of a given system being developed.
|
|
|
|
#### What is a need?
|
|
Agreed-to expectation for a system to perform some function within specified constraints and an acceptable risk. Needs communicate what stakeholders need and expect from a system.
|
|
#### What is a requirement?
|
|
Its the formalization of one or several needs into an agreed-to obligation for a system to perform some function within specified constraints and an acceptable risk.
|
|
Needs and requirements can have a business focus, a user focus or a technical focus.
|
|
Stakeholder needs are formulated in natural language without the word *shall*, whereas stakeholder requirements are formulated with the word *shall* to make sure they are treated as binding requirements the system will be verified to meet.
|
|
There are often multiple stakeholders and thus multiple needs, which might conflict with each other. It's up to the team to resolve inconsistencies and other issues.
|
|
We have three groups of requirements:
|
|
- Product requirements (aka. system requirements, software requirements, or technical requirements)
|
|
- Stakeholder requirements
|
|
- Business needs
|
|
|
|
#### Why is Requirements Management important
|
|
- empowers everyone to clearly understand stakeholder expectations and confidently deliver a product that has been verified to meet the requirements and validated to meet the needs
|
|
- Product Managmement works with stakeholders (business teams, customers, users, developers, testers, regulators, and quality assurance)
|
|
- product might be simple (100 requirements) or complex (several thousand requirements) (depends on size and regulation) --> proper management allows to get everyone on the same page.
|
|
- Business value of managing requirements is huge --> RM is key to project success
|
|
- Benefits:
|
|
- enhance understanding of needs, expectations and problems that product addresses
|
|
- gain clarity on scope, budget, and schedule
|
|
- minimize costly, time-consuming rework
|
|
- increase quality
|
|
- mitigate risk
|
|
- improve likelihood of delivering the right product, within budget and schedule with required quality
|
|
|
|
**Difference between requirements managment and project management:** Simply, project management is getting the product built within budget and schedule with the available resources. Requirements management is making sure the product is the right product and that it is built right
|
|
|
|
#### Stages of the requirements management process
|
|
1. Planning
|
|
- Development Methodology ([[Software Project Survival Guide by Steve McConnell|Waterfall]] vs [[More Effective Agile by Steve McConnell|Agile]]) helps decide how requirements move through the process: Linear vs iterative
|
|
- The Requirements Management Plan (RPM) is the *documented* process the team uses throughout the development.
|
|
2. Development
|
|
3. System Verification
|
|
4. System Validation
|
|
|
|
##### Needs and Requirements Artifacts
|
|
Part of the RMP is defining the needs and requirements artifacts that will be created during the requirements management process.
|
|
|
|
Needs and requirements artifacts include the data and information concerning the needs and requirements and related information. Examples include diagrams, and models, integrated set of needs, set of product requirements, use cases, design documents, testing plans and procedures. Requirements artifacts are used throughout the product development lifecycle to:
|
|
|
|
- Describe the product being built
|
|
- Identify the actions needed to develop the product
|
|
- Capture the actions performed during development
|
|
- Define the testing needed for system verification and system validation
|
|
- Assist with stakeholder review, communications, and engagement
|
|
|
|
It is a best practice that the following requirement attributes are included for all needs and requirements:
|
|
|
|
- Unique Identifier
|
|
- Rationale
|
|
- Owner
|
|
- Type
|
|
- Definition status
|
|
- Priority
|
|
- Criticality
|
|
- Compliance
|
|
- Version number
|
|
- Change history
|
|
- Trace data
|
|
- Verification status (for requirements)
|
|
- Validation status (for needs) |