TYPES OF REQUIREMENTS

TYPES OF REQUIREMENTS:

1. User requirements

      The software must provide a means of representing and accessing external files created by other tools.Statements in natural language plus diagrams of the services the system provides and its operational 

constraints.

2. System requirements

             To be used efficiently, all computer software needs certain hardware components or other software resources to be present on a computer. It is a structured document setting out detailed descriptions of the system services and written as a contract between client and contractor.  These pre-requisites are known as (computer) system requirements and are often used as a guideline as opposed to an absolute rule.

3. Functional requirements

           What a system should be able to do, the functions it should perform.Statements of services the system should provide how the system should react to particular inputs and how the system should behave in particular situations.

4. Non-functional requirements

          Constraints on the services or functions offered by the system such as timing constraints, constraints on the development process, standards, etc.

An example of a non-functional requirement is an initialization sequence incorporated into the software that is specific to a given customer.

5. Domain requirements

              Requirements that come from the application domain of the system and that reflect characteristics of that domain. For example: Library system etc.

6. Customer Requirements 

             The customers are those that perform the eight primary functions of systems engineering, with special emphasis on the operator as the key customer.

7. Operational requirements

             Operational requirements will define the basic need and, at a minimum, answer the questions posed.

8. Architectural Requirements

         An architectural requirement is any requirement that is architecturally significant, whether this significance be implicit or explicit. Implicit architectural requirements are those requirements that have particular attributes. For example, any high-risk, high-priority, or low-stability requirement could be considered to be architecturally significant. The product will be localized.

9. Behavioral Requirements

         Behavior which is abides by the Law, Responsibility for the Image of Infineon, Work-Related Standards and Principles.

10. Performance Requirements

          Performance requirements (PR) are necessary for system design and development. If there is no written performance requirements, it just means that they exists in heads of stakeholders, but nobody bothered to write them down and made sure that everybody agrees with them.

11. Design Requirements

         These Design Requirements apply to all plans, processes, and procedures required for compliance with the Design Process.

12. Derived Requirements

          A derived requirement is one that was not explicitly stated by a stakeholder but has been derived as part of the requirements analysis process. A derived requirement is therefore not directly stated by a primary source but is derived by systems engineers from an explicit statement of requirement

13. Product requirements

          Requirements which specify that the delivered product must behave in a particular way, e.g. execution speed, reliability etc.

14. Organizational requirements

       Requirements which are a consequence of organizational policies and procedures, e.g. process standards used, implementation requirements

etc.

15. External requirements

          Requirements which arise from factors which are external to the system and its development process, e.g. interoperability requirements, legislative requirements etc.