Page 81 -
P. 81
5 - PROJECT SCOPE MANAGEMENT
5.2.2.10 Context Diagrams
See Section 5.2.2.10 of the PMBOK Guide.
®
5.2.2.11 Document Analysis
See Section 5.2.2.11 of the PMBOK Guide.
®
Use cases and user stories are commonly used to collect and analyze features and functional requirements for
software.
5.2.3 Collect Requirements: Outputs
The outputs in Section 5.2.3 of the PMBOK Guide are applicable as outputs for collecting software requirements.
®
Documentation guidelines for software requirements are presented in IEEE Standard 830 [20] and IEEE Standard
1362 [21].
For adaptive life cycles, the customer, a customer representative, or a knowledgeable user provides the
software requirements in an emergent manner. Adaptive projects typically have a backlog of requirements for
potential assignment to future iteration feature sets (the product feature set in Figure 2-5 of this extension). Product
feature sets are easier to modify (add, delete, modify, reprioritize features) than are the baselined requirements,
architecture, and WBS for a highly predictive software project.
5.2.3.1 Requirements Documentation
See Section 5.2.3.1 of the PMBOK Guide.
®
Software requirements for predictive life cycle software projects are typically documented in a repository of
baselined requirements. Software requirements for future iterations of an adaptive life cycle can be maintained in
product feature backlogs, candidate feature lists, story lists, or in a more automated requirements management
system.
5.2.3.2 Requirements Traceability Matrix
®
See Section 5.2.3.2 of the PMBOK Guide.
Requirements documentation, including traceability, is particularly important for software projects because of
the intangible nature of software. A requirements traceability matrix provides visibility from software requirements
to intermediate work products (e.g., design documentation, test plans, test results), and to the components of the
deliverable product.
70 ©2013 Project Management Institute. Software Extension to the PMBOK Guide Fifth Edition
®
