MANAGEMENT
YTntW
YTntW
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
GLOSSARY<br />
Stakeholder Requirement. A requirement that describes the need of a stakeholder or stakeholder group.<br />
State Diagram. A business analysis model that visually shows how an object moves between different states. This<br />
model helps to show the life cycle of an object in a solution.<br />
State Table. A business analysis model that shows all of the possible states of an object and all of the valid<br />
transitions. This model helps to enumerate all possible states and possible transitions.<br />
SWOT Analysis. Analysis of strengths, weaknesses, opportunities, and threats of an organization, project, or option.<br />
System Interface Table. A business analysis model that documents the requirements for the connections<br />
between each interfacing system involved in a project, including how they are connected and what information<br />
flows between them.<br />
Technique. A defined systematic procedure employed by a human resource to perform an activity to produce a<br />
product or result or deliver a service, and that may employ one or more tools.<br />
Technology Feasibility. An analysis to determine the extent to which a technology exists in an organization<br />
to support a potential solution and if not present, how feasible it would be to acquire and operate the needed<br />
technology.<br />
Template. A partially completed document in a predefined format that provides a defined structure for collecting,<br />
organizing, and presenting information and data.<br />
Threat. A risk that would have a negative effect on one or more project objectives. See also issue, opportunity,<br />
and risk.<br />
Traceability. Traceability provides the ability to track product requirements from their origin to the deliverables that<br />
satisfy them.<br />
Traceability and Monitoring. The domain of requirements management concerned with building and maintaining<br />
the traceability matrix to manage requirements and product scope, baselining the product requirements, assessing<br />
impacts of proposed requirement changes, and managing the required updates to the requirements and other<br />
requirements management deliverables once proposed changes are approved.<br />
Traceability Matrix. See requirements traceability matrix.<br />
Transition Requirements. Requirements that are the temporary capabilities, such as data conversion and training<br />
requirements, needed to transition from the current as-is state to the future state.<br />
Use Case. An analysis model that describes a flow of actor-system interactions and boundaries for those<br />
interactions, including trigger, initiating and participating actors, and preconditions and post conditions.<br />
Use Case Diagram. A business analysis model that shows all of the in-scope use cases for a project and which<br />
actors have a part in those use cases.<br />
User Interface Flow. A business analysis model that shows the specific pages or screens of an application and<br />
how a user can navigate between them.<br />
74 ©2016 Project Management Institute. Requirements Management: A Practice Guide