Contains two glossaries of commonly-used terms. Select each letter for that part of the glossary.
Systems Engineering Glossary
Contains a list of the terminology used in requirements management, systems engineering and V&V (validation and verification), including terms used in model-based systems engineering (MBSE). The definitions of some of these terms are often the subject of debate. These are our definitions. If you disagree with any of them, please contact us to discuss! This list is not exhaustive.
A
B
C
D
E
F
G
H
I
N
O
P
Q
R
S
T
U
V
W
P: |
Paper Prototype
|
A non-executable mock-up of a software system’s user interface using inexpensive, low-tech screen sketches.
|
Peer Review
|
An activity in which one or more persons other than the author of a work product examine that product with the intent of finding defects and improvement opportunities.
|
Pilot
|
A controlled execution of a new process with the objective of evaluating the new process under real project conditions to assess its readiness for general deployment.
|
Planguage
|
A keyword-oriented language developed by Tom Gilb that permits precise and quantitative specification of requirements.
|
Post-condition
|
A condition that describes the state of a system after a use case is successfully completed.
|
Pre-condition
|
A condition that must be satisfied before a use case may begin.
|
Procedure
|
A written description of a course of action to be taken to perform a given activity, describing how the activity is to be accomplished.
|
Process
|
A sequence of activities performed for a given purpose. A process description is a documented definition of those activities.
|
Process Assets
|
Documents such as templates, forms, checklists, procedures, process descriptions, and sample work products that are collected to assist an organisation’s effective application of improved software development practices.
|
Product Champion
|
A designated representative of a specific user class who supplies the user requirements for the group that he or she represents.
|
Prototype
|
A partial, preliminary, or possible implementation of a program. Used to explore and validate requirements and design approaches. Types of prototypes include evolutionary, throwaway, paper, horizontal, and vertical. These can be combined, as in an evolutionary vertical prototype.
|
Cradle Glossary
Contains a list of the principal terminology used in Cradle. This list is not exhaustive.
A
B
C
D
E
F
G
H
I
K
L
M
N
O
P
Q
R
S
T
U
V
W
Y