Requirements Management
- •
def
- •
the process of managing changing requirements — and the system components affected by them — during requirements engineering and system development
- •
- •
why requirements change
- •
"wicked problems" — complex problems that cannot be fully defined from the start; new understanding emerges as work progresses
- •
stakeholder understanding evolves — after seeing a prototype or early result, stakeholders realize what they truly need
- •
business and technology environments change — new government regulations, updated hardware, integration needs with new systems
- •
different stakeholders have different and sometimes conflicting needs that surface over time
- •
e.g., a hospital information system designed for patient data recording may later require graphical health trend displays — a new requirement arising from evolved understanding
- •
- •
planning for requirements management
- •
requirement identification — each requirement must be assigned a unique ID for easy tracking and reference
- •
change management process — define formal steps for evaluating, approving, and implementing changes
- •
traceability policy — determine how relationships between requirements and system design are recorded and maintained
- •
tool support — select software tools for storing, tracking, and auditing changes
- •
- •
- •
requirement change management steps
- •
problem analysis and change specification — stakeholder proposes a change; team validates whether it is valid and clarifies details; feedback returned to the requester who may refine or withdraw the request
- •
change analysis and costing — assess the effect of the proposed change using traceability information; estimate impact on cost, time, and quality; decide whether to proceed
- •
change implementation — modify the requirements document, system design, and implementation as needed; update the change log
- •
- •
tools for requirement change management
- •
IBM Engineering Requirements Management DOORS — enterprise-level tool; supports traceability, versioning, and deep impact analysis; suited for complex systems (aerospace, automotive, medical)
- •
Jama Connect — modern collaborative platform; features version control, traceability matrix, and review & approval workflows
- •
Jira + Confluence — widely used for agile project management; with add-ons, supports requirement management; Confluence used for collaborative documentation and storing RFCs
- •
Helix RM (Perforce) — designed for software requirement traceability; integrates with test case and issue trackers
- •
ReqView — lightweight tool for small-to-medium projects; offline capable; supports traceability, versioning, and multi-format export
- •
Spreadsheet Tools (Google Sheets, Excel) — used for small projects; flexible and accessible but lacks automatic traceability and is version-management risk
- •
- •
documenting changes — Request for Change (RFC)
- •
change log structure (table)
- •
No, Date, RFC ID, Summary of Change, Status, Document Version
- •
- •
RFC document fields
- •
RFC ID — unique identifier for this change request
- •
date of request
- •
requester — person or team requesting the change
- •
title of change
- •
description of change — what is being changed
- •
reason for change — why this change is needed
- •
technical impact — integrations affected, additional modules, cost implications
- •
time estimate
- •
cost estimate
- •
evaluation status — Approved (Disetujui) / Rejected (Ditolak) / Deferred (Ditunda)
- •
implementation decision — what action will be taken and when
- •
- •
- •