Glossary

Allocation: Assigning each requirement to a component of the system where it will be implemented.
Application: The use of capabilities (services and facilities) provided by an information system to satisfy a set of user requirements, such as word processing.
Architecture: The underlying structure of a system.
Artifact: A document representing the result of effort. Artifacts are often referred to as examples of work products needed to provide evidence in support of assessments.
Attribute: A characteristic of a requirement that is useful in sorting, classifying, or managing requirements.

Baseline: A specification or product that has been formally reviewed and agreed on and thereafter serves as the basis for further development. It is changed only through formal change control procedures.
Business requirements: The essential activities of an enterprise. Business requirements are derived from business goals (the objectives of the enterprise). Business scenarios may be used as a technique for understanding business requirements. A key factor in the success of a system is the extent to which the system supports the business requirements and facilitates an organization in achieving them.
Business rules: The policies, conditions, and constraints of the business activities supported by a system; the decision processes, guidelines, and controls behind functional requirements (e.g., procedures, definitions, relationships and workflows in the business, and knowledge needed to perform actions).
Business scenario: A technique that can be used to understand an enterprise or organization. A business scenario describes the business process, application, or set of applications, the business and technology environment,...

< Previous Excerpt

The Requirements Engineering Handbook