REQUIREMENTS. Requirements drive specifications (see Specifications, page____) and they define necessary objectives which must be met.

At the fundamental level, Requirements define what the project is ultimately supposed to do. Most requirements in are defined in functional terms, leaving design and implementation details to the developers. They may include: price, performance, reliability objectives in fine detail, some aspects of the user interface. A requirements document is formal documentation (instructions) describing what functions the product is supposed to provide, what characteristics the product is supposed to have, and what goals the product/service/software is supposed to meet or to enable users to meet. Requirements tend to change through the course of a project, with the result that the product as delivered may not adhere to the available requirements. Like changes to specifications, which are managed by the A3, Specification Change Process Category (page ___), requirements must be managed. Meeting all of the requirements doesn't ensure a quality product, since the requirements may not have been expressed. Sometimes, objectives are not realistic. A product's specifications are more useful for determining the product's quality. Quality assurances (QAs) role should be proactive involvement during the project requirements analysis and specification phases. The return on investment (ROI) of this up-front QA involvement results with companies paying less to fix problems that are found early in any project cycle. Catching problems when the requirements and specifications are being hammered out is the ideal time to head off problems. When reviewing requirements and specifications, a developer must ask the following questions: Are these the "right" requirements? Are they complete? Are they compatible? Are they achievable? Are they reasonable? Are they testable? Other forms of Requirements

User Requirements User requirements typically describe the needs, goals, and tasks of the end user. System Requirements The term system requirements have two meanings. First, it can refer to the requirements that describe the capabilities of the system with which, through which, and on which the product will function. For example, the component (a sensor) may need to run through a specified processor, and may need to employ specified software protocol e.g. Lonworks. Second, it can refer to the requirements that describe the product itself, with the meaning that the product is a system. In the DCOR model a requirement can be driven by the company or by customers. It is imperative that what a company wants in a product, to include performance, cost, reliability, delivery date, any/all of the design fors (manufacturability, assembly, sustainability, reparability, transportability, testing, six sigma, the environment, etc.), support services and product data (see Documentation Matrix page ____ are clearly defined in the requirements document/contract.