UMP glossary

See also discussions of the terms.

— A —

Artifact —
Artifact static — the models, documents, etc., which cannot be run on the computer opposite the dynamic artifacts, which are executables.
Artifact dynamic — executables which can be run on the computer opposite the static artifacts: models, documents, etc.

back to top

— C —

Change request — request to change the product under development. Change requests are usually produced by product users (direct and indirect), other project participants and reflect the changes in business need, incomplete or wrong product functionality, etc. Change requests are the subjects of the Change Management procedure.
CM — Configuration Management

back to top

—P—

PIP — Project Initial documentation Package. Any kind of the documents, which initiated project:

• Requests
• Surveys —marketing, etc.
• Executive summaries
• etc.

PBS —Product Business Specification. The document which defines the high-level needs and features of the product, which will be developed. It focuses on the capabilities needed by the target users, and why these needs exist. PBS establishes a long-term vision for the system to be built to address the business objective. This will provide the context for making decisions and evaluating options throughout the course of the systems development life cycle. The PBS does NOT show the details of HOW the product fulfils these needs —they are detailed in the development artifacts: SRS, SAD, SD, source code etc.
Synonyms in other methodologies: Product Vision, Product Scope.

back to top

—Q —

Quality assurance plan —

back to top

— S —

SAD — Software Architecture Design
SD — Software Design
SDP — Software Development Plan
SQA — Software quality assurance
SRS — Software Requirements Specifications

back to top

— U —

UI — User Interface

Use Case model — UML model

back to top

— V —

back to top