Term
|
Definition
A document that describes detailed information about each WBS item |
|
|
Term
|
Definition
A condition or capability that must be met or possessed by a system, product, service, result, or component to satisfy a contract, standard, specification, or other formal |
|
|
Term
|
Definition
Creating a WBS by starting with the largest items of the project and breaking them into their subordinate items |
|
|
Term
|
Definition
The approved project scope statement and its associated WBS and WBS dictionary |
|
|
Term
|
Definition
A document that includes, at a minimum, a description of the project, including its overall objectives and justification, detailed descriptions of all project deliverables, and the characteristics and requirements of products and services produced as part of the project |
|
|
Term
|
Definition
A product, such as a report or segment of software code, produced as part of a project |
|
|
Term
|
Definition
Using highly organized and intensive workshops to bring together project stakeholder, sponsor, users, business analysts, programmers, and so on to jointly define and design information systems |
|
|
Term
|
Definition
Subdividing project deliverables into smaller pieces |
|
|
Term
|
Definition
A plan that describes how project requirements will be analyzed, documented, and managed |
|
|
Term
|
Definition
The difference between planned and actual performance |
|
|
Term
|
Definition
All the work involved in creating the products of the project and the processes used to create them |
|
|
Term
|
Definition
A task at the lowest level of the WBS |
|
|
Term
|
Definition
The tendency for project scope to keep getting bigger |
|
|
Term
|
Definition
Creating a WBS by having team members identify as many specific tasks related to the project as possible and then grouping them into higher-level categories |
|
|
Term
|
Definition
Developing a working replica of the system or some aspect of the system to help define user requirements |
|
|
Term
|
Definition
The processes involved in defining and controlling what work is or is not included in a project |
|
|
Term
|
Definition
Creating a WBS by using a similar project's WBS as a starting point |
|
|
Term
|
Definition
A process for identifying and modeling business events, who initiated them, and how the system should respond to them |
|
|
Term
|
Definition
A deliverable-oriented grouping of the work involved in a project that defines the total scope of the project |
|
|
Term
REQUIREMENT TRACEABILITY MATRIX (RTM) |
|
Definition
a table that lists requirements, various attributes of each requirement, and the status of the requirements to ensure that all requirements are addressed |
|
|