Author Topic: What is a Requirement? How many types of requirements are there? Explain them wi  (Read 755 times)

1190866504

  • Global Moderator
  • Newbie
  • *****
  • Posts: 5
There are four type of requirement
1)   Business Requirement:  are high level requirement, with statement of the goals, objectives, or needs of the enterprises.
Eg:  as a business person I want a application where I can provide cab so that passenger take a ride .
2)   Stakeholder requirement: is a end user requirement , different class of stakeholder interacting with a application or solution.
Eg : passenger should login, view cabs , fare, distance, time. Payment mode

Admin : can track all data of passengers and payment,
Logistics , how many cabs
Driver : should locate passenger.


3)   Functional Requirement:  login with FB, OR GOOGLE,  book a ride, view ride details


4)   Non – functional Requirment: safety  and quality attribution.
Safety and emergency number

5)   Transition: one time installation of the application to the client location.


1190879106

  • Global Moderator
  • Newbie
  • *****
  • Posts: 12
Requirement is nothing but the need of the client. Once the requirement is raised by the client, BA needs to check for the further information from the stakeholders. After collecting requirements, BA needs to analyze and prioritize requirements.
It is classified as four requirements such as
1.   Business requirements: It is the need of the organization. Here Business Requirements Documents (BRD) is prepared.
Ex:  For a retail store, accepting payments is the need.

2.   Stakeholder requirements: These are the requirements from individual stakeholders. BA needs to collect information from different stakeholders to complete the business requirement which results in a solution. Here User Requirements Document (URD) which is nothing but BRD is prepared
Ex: Accepting payments through cash, card, coupons etc are the stakeholder requirements 

3.   Solution requirements (SRS): It describes all business capability details.

Solution requirements are further classified into
(i)   Functional Requirements (FRS) : Here specific functionalities or capabilities are described.
Ex: Here the payments section should consist of drop down box which includes cash, card, coupons.
Cash -  Bill amount, amount paid, return amount
Card - Swiping a card
Coupons -  Exp date and number
(ii)   Non-Functional Requirements (SSD): These are the technical requirements which are resolved by integrating with external peripherals for quality. These are the IT solutions for a requirement.
Ex: Security measures for the payment, how many seconds are required to accept the payment through card (speed).

4.   Transition requirements (ADD): This is a technical solution for the prescribed requirement. It is a transition from current state to future state.
Ex: extracting payments accepting data from the specific database.
In this process, BA gathers requirements from the business requirements and stakeholders requirements stages and prepares a BRD document and also prepares FRS document in the functional requirements stage.

1190956511

  • Global Moderator
  • Newbie
  • *****
  • Posts: 5
A requirement is basically a need of the Client. This need or requirement will transform into a solution while taking various shapes and forms as it progresses from each stage of SDLC

Requirements serve as the foundation of systems and system components .Requirements vary in intent and in kinds of properties.

Types of requirements .

Business requirements ,Stake holder requirements,Solution requirements ,Transistion requirements

Solution requirements – a) Functional requirements and b) Non functional requirements



Business requirements :  These are high level statements of thegoals, objectives, or needs of the enterprise. They describe the reasons why a project has been initiated, the objectives that the project will achieve and the metrics that will be use to measure its success. Business requirements describe the needs of the organization as a whole and not groups or stake holders within it. They are developed and defined through enterprise analysis

Stake holder requirements: These are the statements of the needs of a particular stake holder or class of stakeholder.They describe the needs that a given stakeholder has and how the stake holder will interact with a solution. Stake holder requirements serve as a bridge between business requirements and the various classes of solution requirements .They are developed and defined through requirements analysis

Solution requirements describe the characteristics of a solution that meet business requirements and stake holder requirements .They are developed and defined through requirement analysis .
They are frequently divided into sub categories ,particularly when the requirements describe a software solution.

Functional requirements: describe the behavior and information that the solution will manage .They describe the capabilities the system will be able to perform in terms of behaviours or operations –specific information technology application actions or responses.

Non Functional requirements :capture the conditions that do not directly relate to the behavior or functionality of the solution ,but rather describe the environmental conditions under which the solution must remain effective or qualities that the systems must have .These can include requirements related to speed,capacity,security,availability and the information architecture and presentation of the user interface.

Transition Requirements: describe capabilities that the solution must have in order to facilitate transition from the current state of the enterprise to a desire future state , but that will not be needed once that transition is complete.They are differentiated from other requirement types because they are always temporary in nature and because they cannot be developed until both and existing and new solution are defined. They typically cover data conversion from existing systems, skill gaps that must be addressed and other related changes to reach the desired future state.


Sri Nikhila

  • Global Moderator
  • Newbie
  • *****
  • Posts: 10
 Requirements Classification Schema:
 The requirements classification schema is further classified into the following:

1)Business Requirements:  Defined as goals and objectives of the business at the enterprise level. They apply to the organization as a whole rather than a specific group within the organisation. Developed and documented as part of ongoing enterprise analysis activities.
Business Requirements are also known Enterprise Requirements. They offer everyone within the organization a common understanding of why certain projects have been initiated in the organisation. They provide organization clear direction that can be followed by everyone in the organisation. Requirements should ideally define something in measurable terms. This is most important with business requirements.  Therefore, business requirements should outline a corresponding metric and target that must be achieved by the business.
The critical activities of an enterprise that must be performed to meet the organizational objective while remaining solution independent.
The Business requirements document (BRD) is the detailed business solution for a project including the documentation of customer needs and expectations.
The BRD process can be incorporated with Six Sigma DMAIC (Define, Measure, Analyse, Improve, and Control) culture.
The common objectives of the BRD are as follows:
?To pursue agreement with stakeholders.
?Provide a foundation to communicate with the technology service provider what are the solution needs to satisfy the customer?s and business? needs.
?Provide inputs into the next phase for this present project.
?To describe how the customer and business needs will be met by the solution.
Examples of business requirements:
?The process must completed.
?The data they need to be used for that process.
?Business rule usually governs the process and that data.
The following are teams and partners who create the BRD project: the following People Involved in the Creation of the BRD process;
?Project core team.
?Business partner.
?Process owner or representatives.
?Subject matter experts


2)Stakeholder Requirements:  Defines the goals and objectives of a particular group within an organization. Unlike Business Requirements, they are intended to provide a higher level direction to group of stakeholders.
They are often developed while considering the contending goals and objectives of other areas of the organization that interact with each other within the organisation. Stakeholder requirements of various groups are reflected in overall balance across the organization to support and achieve the Business Requirements in the best possible way.
Stakeholder requirements do not define what needs to be supported by a particular solution (whether the solution is a business process or system solution), rather they span the gap between Business Requirements and more specific Solution Requirements.
The cause for the frequently change in requirements is due to tighter coupling and dependency between requirements
Major roles in systems engineering played by Stakeholder requirements, they are:
?The basis of system requirements activities.
?The basis of system validation and stakeholder acceptance.
?They Act as a reference for integration and verification activities.
?Serve as means of communication between the technical staff, management, finance department, and the stakeholder community.

3)Solution requirements: The solution may be a process solution or system solution. Solution requirements is written in a way that they support and also align with the Stakeholder and Business Requirements. They are defined throughout the requirements analysis process.

Solution requirements sub-categories are as follows:
A)Functional Requirements:  Defined as the behaviour and information that the solution will have to manage. The functional requirements describe the features and functionality of the system and the information that will be created, edited, updated, and deleted by the system. In the case of a non-system solution, the behaviour typically refers to a workflow and the information refers to the inputs and outputs of the workflow.
The Functional requirements describe how the data will be transformed and by whom.
The list of examples of functional requirements are: a) Business Rules, b) Transaction corrections, c) adjustments, and d) cancellations, e)Administrative functions, f)  Authentication, g) Authorization levels, h) Audit Tracking, I)External Interfaces, and j) Certification Requirements.

B)Non-functional Requirements: It describes the qualities of the process or system.  Instead of describing what the solution must do, the non-functional requirements describes how well the solution must do to achieve something. Non-functional requirements are described qualities of a process or system such as its repeatability, usability, reliability, interoperability, scalability, extensibility.
Mostly used Non-functional Testing Tools are: J Meter, Loadster, Loadrunner, Loadstorm, Neoload, Forecast, Load Complete, and Webserver Stress Tool.

4)Transition Requirements:  Describes any capabilities of the solution that aren?t permanent but instead exist only to facilitate the transition from the current state to the future state. Transition requirements cannot be developed until both the current state and the future solution have been defined once the process or system has been developed and the transition of users and information from the current solution to the new solution has occurred, these capabilities will no longer be needed or supported.
Common categories of transition requirements include:
?Rollout activities.
?Data conversions.
?Training needs.
?Realignment of responsibilities in the user groups.

ARASAVILLI DEEPAK

  • Global Moderator
  • Newbie
  • *****
  • Posts: 10
Requirement:
A requirement is basically a need of a client. This need is transformed into a solution while taking various shapes and forms while undergoing each stages in SDLC.

There are four type of requirements.

1. Business Requirements: 
These are high level requirement, with statement of the goals, objectives, or needs of the enterprises.
It describes about;
- Reason why a project has been initiated.
- Objectives that the project will achieve.
-Metrics that are used to measure the success.
- Need of the organization as a whole.

2. Stakeholder requirements:
These are the statements of needs of a particular stakeholder or a class of stakeholders.
- It describes about the need that the stakeholder has and how that stakeholder interacts with the solution.
- Stakeholder Requirements act as a bridge between Business Requirement and Solution Requirement.
- These are developed and designed through Requirement Analysis.

3. Solution Requirements:
- They describe the characteristics of the solution that meets Business requirement and Stakeholder Requirement.
- They are developed and defined through Requirement Analysis.
- They are frequently divided into sub-categories, particularly when the requirement want a software solution.
a. Functional Requirements:
It describes;
- The behaviour and information that the project will manage.
- The capabilities the system will be able to perform in terms of behaviour/operations.
b. Non-Functional Requirements:
- They donot directly relate to the behaviour/funtionallity of the solution, but they describe the environmental conditions under which the solution must remain effective.
- They are also called as Quality/Supplimentary Requirements.
- They can include requirements related to speed, accuracy, availability etc.

4. Transitional Requirements:
- Capabilities that the solution must have in order to facilitate transition from current state to a future desired state, but will not be needed once the transition is complete.
- They are differentiated from other requirements because they are temporary in nature as they cannot be developed until both an existing and a new solution is defined.
- They include Data conversions, Training needs etc; to reach the desired future state.
- They are developed and defined through Solution assesment and Validation.