Types of Requirements

Posted By on April 24, 2016

Download PDF
Requirements engineering
Software Requirements Specification

Requirements are categorized in several ways. The following are common categorizations of requirements that relate to technical management:

Customer Requirements

  • Operational distribution or deployment: Where will the system be used?
  • Mission profile or scenario: How will the system accomplish its mission objective?
  • Performance and related parameters: What are the critical system parameters to accomplish the mission?
  • Utilization environments: How are the various system components to be used?
  • Effectiveness requirements: How effective or efficient must the system be in performing its mission?
  • Operational life cycle: How long will the system be in use by the user?
  • Environment: What environments will the system be expected to operate in an effective manner?

Architectural Requirements
Architectural requirements explain what has to be done by identifying the necessary systems architecture of a system.

Structural Requirements
Structural requirements explain what has to be done by identifying the necessary structure of a system.
Behavioral Requirements
Behavioral requirements explain what has to be done by identifying the necessary behavior of a system.
Functional Requirements
Functional requirements explain what has to be done by identifying the necessary task, action or activity that must be accomplished.Functional requirements analysis will be used as the top level functions for functional analysis.
Non-functional Requirements
Non-functional requirements are requirements that specify criteria that can be used to judge the operation of a system, rather than specific behaviors.
Core Functionality and Ancillary Functionality Requirements
Murali Chemuturi defined requirements into Core Functionality and Ancillary Functionality requirements.Core Functionality requirements are those without fulfilling which the product cannot be useful at all.Ancillary Functionality requirements are those that are supportive to Core Functionality.The product can continue to work even if some or all of the Ancillary Functionality requirements are fulfilled but with some side effects.Security, safety, user friendliness and so on are examples of Ancillary Functionality requirements.
Performance Requirements
The extent to which a mission or function must be executed; generally measured in terms of quantity, quality, coverage, timeliness or readiness. During requirements analysis, performance (how well does it have to be done) requirements will be interactively developed across all identified functions based on system life cycle factors; and characterized in terms of the degree of certainty in their estimate, the degree of criticality to system success, and their relationship to other requirements.
Design Requirements
The “build to,” “code to,” and “buy to” requirements for products and “how to execute” requirements for processes expressed in technical data packages and technical manuals.
Derived Requirements
Requirements that are implied or transformed from higher-level requirement. For example, a requirement for long range or high speed may result in a design requirement for low weight.
Allocated Requirements
A requirement that is established by dividing or otherwise allocating a high-level requirement into multiple lower-level requirements.
Requirements engineering
Software Requirements Specification

Download PDF

Posted by Akash Kurup

Founder and C.E.O, World4Engineers Educationist and Entrepreneur by passion. Orator and blogger by hobby

Website: http://world4engineers.com