we may need to draft different types of requirements for each team in their respective format; based on this, requirements has been classified as follows.
Life depends on what word you choose, after a word.
FYI… here is the list of most important and commonly used requirements for any IT projects:
- Business Requirements
- User Requirements
- Functional Requirements
- Data Requirements
- System/Non-Functional Requirements
- Software/Technical Requirements
- Business Rule
- list goes …. on.
Let me try to explain the differences…
- Business Requirement: A business requirement describes what are the Client wants and needs from the final product/system. (e.g: Business Case Document or BRD)
- e.g: Implement Customer Service Application for Retail Industry to manage Customer Calls.
- User Requirement: A user requirement is a task that the user can perform from the final product/system – Business Analyst is required to gather the information from user prospective which satisfy the Business Requirements. (e.g: Business Requirement Document (BRD))
- e.g: Req.1 Customer Service Associate must have an ability to receive a call.
- e.g: Req.2 Associate must have an ability to record a customer call.
- Functional Requirement: A functional requirement is system feature’ that must be built into the system to satisfy the User Requirements; in other words to make user requirements possible, we need to collect the “how” information such as “How can we make it possible to receive calls via CSA”.(e.g: Functional Requirement Document (FRD))
- Customer Service Application must connect with of AT&T Telephone Carrier, to receive a call.
- Data Requirements: A data requirement is information which is required to gather for the system or user requests/provides to satisfy Functional requirement (e.g: Data Requirement Document (DRD)
- e.g: Customer Service Application must have ability to receive the calls, only from US.
- System/Non-Functional requirement: A non-functional requirement is a quality attribute that the system must have. These attributes are not system features (functional requirements), but they do influence how the functionality of the system is implemented or how how system will do so. System requirements usually deal with some aspect of usability , performance, or security or are operational in nature of a system on specific tasks. (e.g: System Requirement Document (SRD))
- e.g: Customer Service Application should be available 24/7 with no down time, if possible.
- Technical/Software Requirement: Collection of Software information to build the Application. These requirements must define what software will do, such as behavior of a system services, tasks or functions the user performs using the system (e.g: Technical Requirement Document (TRD) or Software Design Document (SDD)).
- e.g: These requirements provide an agreement between the IT and the customers on what the application will do & system can meet desired goals. (Proof document, that define technically, it is possible)
- Business Rule: A business rule is a law, policy, standard or procedure by which an organization functions. It is a statement that defines or constrains some aspect of the business to control or influence the behavior of the business.
- e.g: Customer Associate cannot leak customer info to other customer.
If you watch carefully, primary source document is Business Requirements and they interrelated to each other. This also describes, “Business Requirement” Drives most of the requirement documents.
Good Luck! Guys,
Hope, I tried my best. If time permits, I will try to elaborate each Requirement Type with more examples.