The Importance of Requirements

Requirements engineering is difficult. It’s not just a simple matter of writing down what the customer says he wants. A fundamental problem in business is that requirements are inherently dynamic; they will change over time as our  understanding of the problem we are trying to solve changes. The importance of good requirements and the underlying dynamic nature of the process mean that we must be as accurate as possible, and yet be flexible. Flexible does not mean “weak,” but rather than we have a process for developing requirements and accommodating changed requirements as we clarify the real requirements of customers. Ineffective requirements practices are an industry wide problem. This is an area in which you can have a major positive impact. A more disciplined approach to requirements development and management is needed in order to improve project success rates. An alarming 53% of industry’s investment in technical development projects is a casualty of cost overruns and failed projects.

Type of Requirement

Business Requirement:

   Business requirements represent a kind of "why" information. It represent the high level of objectives of the organization or customer who requests the system. Business requirement why the organization is implementing the system. Vision and Scope statement record the business requirement.

User Requirement

  Requirements constitute one type of "what" information. User requirements describe what the user will be able to do with the product, such as goals or tasks that users must be able to perform. Use cases, scenarios, user stories, and event response tables are some ways to represent user requirements.

Functional Requirement

      Functional requirement specify the software functionality that the developer must build into the product to enable the user to accomplish their business requirement . Functional requirements represent one kind of "what" information. The traditional "shall" statements that describe what the system "shall do" or what the system "shall let the user do.“

System Requirement

  Describe the top level requirement for a product that contain multiple subsystem that is a system. A system can be all software or it can be  both software and hardware.

Type of Requirement

There are various types of requirements:

Business Requirement

     Business requirements represent a kind of "why" information. It represent the high level of objectives of the organization or customer who requests the system. Business requirement why the organization is implementing the system. Vision and Scope statement record the business requirement.

User Requirement

      Requirements constitute one type of "what" information. User requirements describe what the user will be able to do with the product, such as goals or tasks that users must be able to perform. Use cases, scenarios, user stories, and event response tables are some ways to represent user requirements.

Functional Requirement

      Functional requirement specify the software functionality that the developer must build into the product to enable the user to accomplish their business requirement . Functional requirements represent one kind of "what" information. The traditional "shall" statements that describe what the system "shall do" or what the system "shall let the user do."

System Requirement

      Describe the top level requirement for a product that contain multiple subsystem that is a system. A system can be all software or it can be  both software and hardware.

 

Responsibilities of requirement analyst

Responsibilities:

1. Prepare Vision and Scope Statement.
2. Identify Project Stakeholders and User Classes.
3. Elicit Requirements.
4. Prepare Requirements Specifications(SRS).
5. Decompose high‐level business and user requirements into functional requirements.
6.  Define Quality attributes and nonfunctional requirements.
7. Lead requirements analysis and verification.
8. Requirement prioritization.
9. Peer reviews and inspections. 
10. Requirements traceability and track.
11. Change Management.
12. Reuse requirement.
13. Assist product management.

Requirement Analyst Job Description

The Requirement Engineer is the individual who has the primary responsibility to elicit, analyze, validate, specify, verify and manage the real needs.

Skill Needed:

1. Interview Skill.
2. Listening Skill.
3. Analytical Skill.
4. Facilitation Skill.
5. Observation Skill.
6. Writing Skill.
7. Modeling Skill.
8. Interpersonal Skill

Knowledge Needed:

1. Understanding Requirement Engineering.
2. Requirement engineering practices.
3. Product management concepts.
4. Application domain knowledge

Requirement Analysis

V-Model of Software Development

Software is one kind of product that satisfy the user requirement.So before develop a software you must know what is the need of user,what should be implemented. So requirement analysis is the major and first step of software development.

If we look at the V-Model, the base of the software development is user requirement.So we must understand what our user need.

What is Requirement:
---A capability that the system must deliver.