| Term |
Definition |
| Analysis - Requirement Analysis |
The study of each requirement, and their relationship to other requirements. |
| Architecture |
Documentation that describes the orderly arrangement of business and technical components of an enterprise, system or project. |
| Best Practices |
Tried and true processes and methods. Recommended that you consider these methods. |
| Business Requirement |
A statement of business needs. Business requirements generally relate to the needs to fulfill business processes. |
| Definition - Requirement Definition |
Requirement definition is the process of making requirements clear and distinct. |
| Deliverable |
A work product such as a document, a snippet of code. |
| Deliverable - Project Deliverable |
A project deliverable is an article or "artifact" produced by a project. |
| Feature (Software) |
A prominent software capablity. For instance, "site search" is a feature. |
| Functional Requirement |
Need that pertains to a specific business process or software feature. Example is "I need a site search". |
| Non-functional Requirement |
A need that is independant of a business process or software feature. An example is "The systme must cost less than $500,000." |
| QA |
Quality Assurance function within a business. Ensure quality of project deliverables. |
| Requirement |
A statement of need. Example "I require that the system records the first and last name of the applicant". |
| Requirement ID (Identifier) |
Uniquely identifies a requirement. For instance MTCS-001 could identify the first "Maintenance Management System" requirement. Requirement id's are usually formed accoording to a project or enterprise standard. |
| Requirement Management |
The process of creating, storing, revising and consuming requirements in an efficient and effective manner. |
| Requirements Facilitation |
The process of working with a group of Stakeholders to draw out their requirements. This is usually done in a requirements session, where the requirements facilitator uses a combination of a good process and good listening skills to help the process along. |
| Requirements Management Tool |
The software tool that facilitates the process of creating, storing, revising and consuming requirements in an efficient and effective manner.
|
| Requirements Phase |
Stage of the project that deals with defining, documenting, reviewing and approving requirements. |
| Review - Requirements Review |
Review to ensure requirements are atomic, understandable, verifiable, and generally meet standards. Checklists can be used. Stakeholders and the QA group review requirements. |
| Software Requirement |
A statement of need relating to a software feature or features. |
| Software Requirements Document |
Documents the need for software features.
For instance, a software requirements document may state the need for a "site search" feature on a website.
The need for several related features are usually documented in a a software requirements document. |
| Statement of Work |
Project deliverable that states the project goals, approach, deliverables, constraints. Describes project deliverables and approvers. This document ensures a project is well conceived before it is started (Refer to the book "Moby Dick" to describe a project poorly conceived). |
| Template |
A "fill in the blanks" document that guides the requirements documentation process. Many enterprises have "standard" templates that are highly recommended or must be used on projects. |
