Page 143 -

5 - PROJECT SCOPE MANAGEMENT

5.2.2.10 context diagrams

The context diagram is an example of a scope model. Context diagrams visually depict the product scope by
showing a business system (process, equipment, computer system, etc.), and how people and other systems
(actors) interact with it. Context diagrams show inputs to the business system, the actor(s) providing the input, the
outputs from the business system, and the actor(s) receiving the output.

5.2.2.11 document Analysis 5

Document analysis is used to elicit requirements by analyzing existing documentation and identifying
information relevant to the requirements. There are a wide range of documents that may be analyzed to help elicit
relevant requirements. Examples of documents that may be analyzed include, but are not limited to: business plans,
marketing literature, agreements, requests for proposal, current process flows, logical data models, business rules
repositories, application software documentation, business process or interface documentation, use cases, other
requirements documentation, problem/issue logs, policies, procedures, and regulatory documentation such as
laws, codes, or ordinances, etc.

5.2.3 collect requirements: outputs

5.2.3.1 requirements documentation

Requirements documentation describes how individual requirements meet the business need for the project.
Requirements may start out at a high level and become progressively more detailed as more about the requirements
is known. Before being baselined, requirements need to be unambiguous (measurable and testable), traceable,
complete, consistent, and acceptable to key stakeholders. The format of a requirements document may range from
a simple document listing all the requirements categorized by stakeholder and priority, to more elaborate forms
containing an executive summary, detailed descriptions, and attachments.

Components of requirements documentation can include, but, are not limited to:
• Business requirements, including:

○ Business and project objectives for traceability;
○ Business rules for the performing organization; and
○ Guiding principles of the organization.

©2013 Project Management Institute. A Guide to the Project Management Body of Knowledge (PMBOK Guide) – Fifth Edition 117
®

Licensed To: Jorge Diego Fuentes Sanchez PMI MemberID: 2399412
This copy is a PMI Member benefit, not for distribution, sale, or reproduction.