A
Architectural design
1. the process of defining a collection of hardware and software components and their interfaces to establish the framework for the development of a computer system 2. the result of defining a collection of hardware and software components and their interfaces to establish the framework for the development of a computer system. [ISO/IEC 24765]
Architectural mechanisms
Common solutions to common problems that can be used during development to minimize complexity. They represent key technical concepts that will be standardized across the solution. [OpenUP]

NOTE: architectural mechanisms are sometimes called "architectural tactics" or "heuristics"
B
Baseline
A specification or product that has been formally reviewed and agreed upon, that thereafter serves as the basis for further development, and that can be changed only through formal change control procedures. [ISO/IEC 12207]
C
Component
The principal computational elements and data stores that execute in system. [CLEMENTS 03, p.107]
Customer
Organization or person that pays the VSE to create a software product. NOTE: acquirer or user is customer [ISO 9000]
D
Design concern
An area of interest with respect to a software design. [IEEE 1016]
Detailed design
1. the process of refining and expanding the preliminary design of a system or component to the extent that the design is sufficiently complete to be implemented 2. the result of the process in (1). [ISO/IEC 24765]
F
Functional requirement
A requirement that specifies a function that a system or system component must be able to perform. [ISO/IEC 24765]
M
Module
An implementation unit of software that provides a coherent unit of functionality. [CLEMENTS 03, p.43]
N
Nonfunctional requirement
1. a software requirement that describes not what the software will do but how the software will do it. Syn: design constraints, non-functional requirement cf. functional requirement. EXAMPLE: software performance requirements, software external interface requirements, software design constraints, and software quality attributes. Nonfunctional requirements are sometimes difficult to test, so they are usually evaluated subjectively. [ISO/IEC 24765]
S
Software architecture
The structure or structures of a system, which consist of elements, their externally visible properties, and the relationships among them. [CLEMENTS 03, p.xxv]
Software design
In this Deployment package, the combination of Architectural design and Detailed design.
Software product
The set of computers programs, procedures, and possibly associated documentation and data. [ISO/IEC 12207]
Stakeholder
Individual or organization having a right, share, claim, or interest in a system or in its possession of characteristics that meet their needs and expectations. [ISO/IEC 12207]
Subsystem
1. a secondary or subordinate system within a larger system. 2. a system that is part of a larger system. [ISO/IEC 24765]
T
Traceability matrix
A matrix that records the relationship between two or more products of the development process. [ISO/IEC 24765]
Traceable
Having components whose origin can be determined. [ISO/IEC 24765]
V
Validation
Confirmation by examination and provision of objective evidence that the particular requirements for a specific intended use are fulfilled. [ISO/IEC 12207]
Verification
Confirmation by examination and provision of objective evidence that specified requirements have been fulfilled. [ISO/IEC 12207]
View
A representation of a whole system from the perspective of a related set of concerns. [IEEE 1471]