Tuesday, December 12, 2017

Requirements Glossary - from A to Z

A   B   C   D   E   F   G   H   I   J   K   L   M   N   O   P   Q   R   S   T   U   V   W   X   Y   Z

A

Accessibility Requirements
Accessibility Requirements refers to ... [More info on Accessibility Requirements

Accuracy Requirements
Accuracy Requirement refers to the non-functional requirement type which is not a functional, data or process requirement and which is concerned with defining the precision which the solution will record or produce data. [More info on Accuracy Requirements]  

Activity Logging Requirements
Activity Logging Requirements refers to ... [More info on Activity Logging Requirements]  

Agile Requirements
Agile Requirements refers to ... [More info on Agile Requirements

Allocate Requirements
Allocate Requirements refers to ... [More info on Allocate Requirements

Requirements Analysis
Requirements Analysis refers to ... [More info on Requirements Analysis]

Requirements Application
Requirements Application refers to ... [More info on Requirements Application

Architecture Requirements
Architecture Requirements refers to ... [More info on Architecture Requirements

Auditing and Reporting Requirements
Auditing and Reporting Requirements refers to ... [More info on Auditing and Reporting Requirements

Availability Requirements
Availability Requirements refers to any requirements that are not a functional, data or process requirements and which are concerned with defining the periods when the solution (system) can be used or should be in operation. [More info on Availability Requirements

B

Backup and Recovery Requirements
Backup and Recovery Requirements refers to ... [More info on Backup and Recovery Requirements

Business Requirements
BABOK 2.0 (A Guide to the Business Analysis Body of Knowledge) states simply that “Business requirements are higher-level statements of the goals, objectives, or needs of the enterprise.” Higher-level is the key term here. Business requirements are what an analyst might show an executive to help him understand the need for the project, not what she would show an engineer to help him build the project.

The purpose of business requirements is to define a project’s business need, as well as the criteria of its success. Business requirements describe why a project is needed, whom it will benefit, when and where it will take place, and what standards will be used to evaluate it. Business requirement generally do not define how a project is to be implemented; the requirements of the business need do not encompass a project’s implementation details. [More info on Business Requirements

C

Capacity Requirements
Capacity Requirements refers to ... [More info on Capacity Requirements

Requirements Change Control Board
Requirements Change Control Board refers to ... [More info on Requirements Change Control Board] 

Communicate Requirements (Communication)
Communicate Requirements refers to ... [More info on Communicate Requirements (Communication)

Compatibility Requirements
Compatibility Requirements refers to ... [More info on Compatibility Requirements

Concurrency Requirements
Concurrency Requirements refers to ... [More info on Concurrency Requirements

Configurability Requirements
Configurability Requirements refers to ... [More info on Configurability Requirements

Customer Requirements
Customer Requirements refers to ... [More info on Customer Requirements]

D

Data Requirements
Data Requirements refers to ... [More info on Data Requirements

Requirements Definition
Requirements Definition refers to ... [More info on Requirements Definition]

Requirements Design
Requirements Design refers to ... [More info on Requirements Design

Requirements Development
Requirements Development refers to ... [More info on Requirements Development]

Requirements Documentation
Requirements Documentation refers to ... [More info on Requirements Documentation]

E

Requirements Education
Requirements are basic to business analysis, and so requirements education is basic to business analysts. “All team members who will function as analysts should receive basic training in requirements engineering,”[1] notes Wiegers in his modern analysis classic Software Requirements. Honing your craft is both admirable and achievable, and you have numerous, helpful outlets at your disposal. The method that you choose is contingent on several things, including how much requirements experience you already have and whether your background is in software development, technical writing, or something else. [More info on Requirements Education

Requirements Elicitation
A thorough discovery of business requirements is almost never readily available at an analyst’s fingertips—rarely can requirements be quickly looked up as one would gather information for a term paper or study for a test. Much of business or technical requirements is not documented anywhere—it resides in the minds of stakeholders, in feedback that has yet to be obtained from end users, and from a study of flowcharts and surveys that have yet to be created. And so requirements must be elicited, or drawn out, and the methodology in doing so must be logical and meticulous...  The purpose of requirements elicitation, therefore, is to thoroughly identify the business needs, risks, and assumptions associated with any given project.  [More info on Requirements Elicitation

Requirements Engineering
Requirements Engineering refers to ... [More info on Requirements Engineering

Enterprise Requirements
Enterprise Requirements refers to ... [More info on Enterprise Requirements

Error-Handling Requirements
Error-Handling Requirements refers to ... [More info on Error-Handling Requirements]

Requirements Estimation
Requirements Estimation refers to ... [More info on Requirements Estimation]

F

Functional Requirements
Functional Requirements refers to ... [More info on Functional Requirements]

G

Requirements Gathering
Requirements Gathering refers to ... [More info on Requirements Gathering]

H

High-level Requirements
High-level Requirements refers to ... [More info on High-level Requirements]

I

Information Requirements
Information Requirements refers to ... [More info on Information Requirements

Requirements Inspections
Requirements Inspections refers to ... [More info on Requirements Inspections] 

Installability Requirements
Installability Requirements refers to ... [More info on Installability Requirements]

IT Requirements
IT Requirements refers to ... [More info on IT Requirements]

J

K

L

Legal and Regulatory Requirements
Legal and Regulatory Requirements refers to ... [More info on Legal and Regulatory Requirements] 

Licensing Requirements
Licensing Requirements refers to ... [More info on Licensing Requirements] 

Localizability Requirements
Localizability Requirements refers to ... [More info on Localizability Requirements]

M

Maintain Requirements
Maintain Requirements refers to ... [More info on Maintain Requirements]

Maintainability Requirements
Maintainability Requirements refers to ... [More info on Maintainability Requirements] 

Requirements Management
Requirements Management refers to ... [More info on Requirements Management

Model Requirements
Model Requirements refers to ... [More info on Model Requirements]

N

Network Requirements
Network Requirements refers to ... [More info on Network Requirements]

Non Functional Requirements
Non-functional requirements are characteristics of a system or solution which describe non-behavioral characteristics or qualities of a system. Non Functional Requirements have also been called the 'ilities': usability, reliability, interoperability, scalability, extensibility, etc. Non-functional requirements are also commonly referred to as quality of service (QoS) requirements or service-level requirements. [More info on Non Functional Requirements]

O

Object Oriented Requirements
Object Oriented Requirements refers to ... [More info on Object Oriented Requirements]

Organizing Requirements
The voluminous amounts of information that an analyst collects during the discovery and elicitation phases warrant a good deal of planning and organization in order to make business or user requirements into a usable, cohesive whole. As with any other organization process, the key element to requirements’ organization success is thorough preparation and planning.   There are two main objectives when organizing requirements: (1) to understand which models are appropriate to include based on the business need, and (2) to understand and clearly communicate the interdependencies and relationships between the various requirements.  [More info on Organizing Requirements]

P

Requirements Package
Requirements Package refers to ... [More info on Requirements Package] 

Requirements Pattern
Requirements Pattern refers to ... [More info on Requirements Pattern] 

Performance Requirements
Performance Requirements refers to ... [More info on Performance Requirements]

Requirements Planning
Requirements Planning refers to ... [More info on Requirements Planning]

Precision Requirements
Precision Requirements refers to ... [More info on Precision Requirements] 

Requirements Prioritization
Requirements Prioritization refers to ... [More info on Requirements Prioritization] 

Requirements Prioritization
Excellent requirements prioritization is essential to any well-run project. It ensures that the project focuses on the most important elements first, and that everyone understands and agrees regarding what the project’s most important elements are. Good prioritization of requirements will also ensure that engineers, programmers and database analysts develop a project’s most critical elements in sync with the business needs.  [More info on Requirements Prioritization

Requirements Process
Requirements Process refers to ... [More info on Requirements Process

Product Requirements
Product Requirements refers to ... [More info on Product Requirements]

Project Requirements
Project Requirements refers to ... [More info on Project Requirements]

Q

R

Requirements
Requirements define precisely what you are going to create or accomplish—what the effort will include, what it will not include, how it will be done, and by whom. Requirements often also include ancillary (but relevant) information such as possible risks to the project and criteria by which to measure the project's success.  To illustrate this information for the reader, requirements may include not only clearly written text, but charts, graphs, diagrams, use cases, and mock-ups, to name just a few tools in the business analyst's box. BABOK 2.0 defines requirements as including but not being limited to "past, pres¬ent, and future conditions or capabilities in an enterprise, and descriptions of organiza¬tional structures, roles, processes, policies, rules, and information systems." In short, requirements can be about any existing or future system, product, process or procedure.  [More info on Requirements

Redundancy Requirements
Redundancy Requirements refers to ... [More info on Redundancy Requirements] 

Requirements Capture Language (RCL)
Requirements Capture Language (RCL) refers to ... [More info on Requirements Capture Language (RCL)]

Reliability Requirements
Reliability Requirements refers to ... [More info on Reliability Requirements] 

Report Requirements
Report Requirements refers to a subset, of a project's requirements, which deal with the details needed to capture the business need related to what reports need to be generated.  The report requirements would generally include information such as the purpose of a report, its justification, attributes and columns, runtime parameters, look and feel requirements, etc. [More info on Report Requirements

Response-Time Requirements
Response-Time Requirements refers to ... [More info on Response-Time Requirements]

Requirements Reuse
Requirements Reuse refers to ... [More info on Requirements Reuse]

S

Scalability Requirements
Scalability Requirements refers to ... [More info on Scalability Requirements] 

Security Requirements
Security Requirements refers to ... [More info on Security Requirements]

Security Quality Requirements Engineering (SQUARE)
Security Quality Requirements Engineering (SQUARE) is a requirements engineering process developed by the Software Engineering Institute’s (SEI) CERT® Program at Carnegie Mellon University (CMU). SQUARE is a nine-step process that delivers categorized, prioritized, and validated security requirements. SQUARE prioritizes requirements based on completed risk assessment and requirement categorization steps. [More info on Security Quality Requirements Engineering (SQUARE)]

Requirements Signoff
Requirements Signoff refers to ... [More info on Requirements Signoff] 

Small Business Requirements
Small Business Requirements refers to ... [More info on Small Business Requirements

Software Requirements
Software Requirements refers to ... [More info on Software Requirements

Solution Requirements
Solution Requirements refers to ... [More info on Solution Requirements]

Requirements Specification
Requirements Specification refers to ... [More info on Requirements Specification]

Stakeholder Requirements
Stakeholder Requirements refers to ... [More info on Stakeholder Requirements]

Requirements Standards
Requirements Standards refers to ... [More info on Requirements Standards]

Startup and Shutdown Requirements
Startup and Shutdown Requirements refers to ... [More info on Startup and Shutdown Requirements] 

Stress Requirements
Stress Requirements refers to ... [More info on Stress Requirements] 

Supplementary Requirements
Supplementary Requirements refers to ... [More info on Supplementary Requirements

Supportability Requirements
Supportability Requirements refers to ... [More info on Supportability Requirements]

System Requirements
System Requirements refers to ... [More info on System Requirements

T

Technical Requirements
Technical Requirements refers to ... [More info on Technical Requirements

Requirements Testing
Requirements Testing refers to ... [More info on Requirements Testing] 

Testing Requirements
Testing Requirements refers to ... [More info on Testing Requirements] 

Throughput Requirements
Throughput Requirements refers to ... [More info on Throughput Requirements] 

Requirements Tool
Requirements Tool refers to ... [More info on Requirements Tool] 

Requirements Traceability
Requirements Traceability refers to ... [More info on Requirements Traceability

Requirements Training
Requirements Training refers to ... [More info on Requirements Training

Training Requirements
Training Requirements refers to ... [More info on Training Requirements] 

Transition Requirements
Transition Requirements refers to ... [More info on Transition Requirements] 

Turnaround-Time Requirements
Turnaround-Time Requirements refers to ... [More info on Turnaround-Time Requirements]  

U

Usability Requirements
Usability Requirements refers to ... [More info on Usability Requirements

Usability Requirements
Usability Requirements refers to ... [More info on Usability Requirements] 

User Interface (UI) Requirements
User Interface (UI) Requirements ... [More info on User Interface (UI) Requirements] 

User Requirements
User Requirements refers to ... [More info on User Requirements] 

V

Validate Requirements
Validate Requirements refers to ... [More info on Validate Requirements] 

Verify Requirements (Requirements Verification)
Verify Requirements (Requirements Verification) refers to ... [More info on Verify Requirements (Requirements Verification)] 

Requirements Visualization (Visualize Requirements)
Requirements Visualization (Visualize Requirements) refers to ... [More info on Requirements Visualization (Visualize Requirements)

W

Website Requirements
Website Requirements refers to ... [More info on Website Requirements

Requirements Workshops
Requirements Workshops refers to ... [More info on Requirements Workshops] 

Writing Requirements
Writing Requirements refers to ... [More info on Writing Requirements]

X

Y

Z

Zebra Requirements
We told you it's A through Z! A Zebra Requirement is the requirement which, when you see it for the first time, you wonder "How did they come up with this one?" Have you ever worked on a project dealing with cows only to stumble upon requirements about zebras?

Copyright 2009-2014 by Modern Analyst Media LLC