SOFTWARE ENGINEERING UNIT 2 PART 1:- REQUIREMENT ENGINEERING PROCESS

 BY DR. AJAY KUMAR PATHAK

MJ–11 (TH): SOFTWARE ENGINEERING

F.Y.U.G.P FOR B. Sc. IT SEM 5

REQUIREMENT ENGINEERING PROCESS:- Requirements engineering is the process of identifying, eliciting (causing, producing), analyzing, specifying, validating, and managing the needs and expectations of stakeholders for a software system.

Requirement Engineering is the process of defining, documenting and maintaining the requirements. It is a process of gathering and defining service provided by the system. it is the disciplined application of proven principle , methods ,tools and notations to describe a proposed system’s intended behavior and its associated constraints.

The requirements engineering process is an iterative process that involves several steps, including:-

1.         Feasibility Study:- This is the initial phase of the requirement engineering process. It involves evaluating the feasibility of the proposed software project. The main objective is to determine whether the project is technically, economically, and operationally viable.

During this phase, the following aspects are considered:- 

(a) Technical Feasibility:-   Can the proposed system be developed with the available technology and resources?

(b) Economic Feasibility:-   Is the project economically feasible in terms of cost and benefits?

(c ) Operational Feasibility: Will the system work effectively within the existing organizational structure and processes?

2.         Requirements Elicitation: This is the process of gathering information about the needs and expectations of stakeholders for the software system. This step involves interviews, surveys,

focus groups, and other techniques to gather information from stakeholders.

3.         Requirements Analysis:- This step involves analyzing the information gathered in the requirements elicitation step to identify the high-level goals and objectives of the software system. It also involves identifying any constraints or limitations that may affect the development of the software system.

4.         Requirements Specification:-  This step involves documenting the requirements identified in the analysis step in a clear, consistent, and unambiguous manner. This step also involves prioritizing and grouping the requirements into manageable chunks (peace).

5.         Requirements Validation:- This step involves checking that the requirements are complete, consistent, and accurate. It also involves checking that the requirements are testable and that they meet the needs and expectations of stakeholders.

6.         Requirements Management:- This step involves managing the requirements throughout the software development life cycle, including tracking and controlling changes, and ensuring that the requirements are still valid and relevant.

7.         The Requirements Engineering process:- It is a critical step in the software development life cycle as it helps to ensure that the software system being developed meets the needs and expectations of stakeholders, and that it is developed on time, within budget, and to the required quality.

REQUIREMENTS ELICITATION (    elicitation means the act or process of drawing out information, a reaction, or a fact from someone, often with some difficulty and the process of gathering, analyzing, and defining the requirements for a software system from stakeholders, which include users, customers, and clients.       )          :- It is related to the various ways used to gain knowledge about the project domain and requirements. The various sources of domain knowledge include customers, business manuals, and the existing software of same type, standards and other stakeholders of the project. The techniques used for requirements elicitation include interviews, brainstorming, task analysis, Delphi technique, prototyping, etc. Some of these are discussed here. Elicitation does not produce formal models of the requirements understood. Instead, it extends the domain knowledge of the analyst and thus helps in providing input to the next stage. Requirements elicitation is the process of gathering information about the needs and expectations of stakeholders for a software system. This is the first step in the requirements engineering process and it is critical to the success of the software development project. The goal of this step is to understand the problem that the software system is proposed to solve, and the needs and expectations of the stakeholders who will use the system.

There are several techniques that can be used to elicit requirements, including:-

1.      Interviews: These are one-to-one conversations with stakeholders to gather information about their needs and expectations.

2.      Surveys: These are questionnaires that are distributed to stakeholders to gather information about their needs and expectations.

3.      Focus Groups: These are small groups of stakeholders who are brought together to discuss their needs and expectations for the software system.

4.      Observation: This technique involves observing the stakeholders in their work environment to gather information about their needs and expectations.

5.      Prototyping: This technique involves creating a working model of the software system, which can be used to gather feedback from stakeholders and to validate requirements.

REVIEW AND MANAGEMENT OF USER NEEDS:-

Primary objectives of user needs management, achieve shared understanding among stakeholders, maintain traceability from needs to requirements to test cases, manage scope, and support iterative refinement as context develops

Answer first: A thorough Review and Management approach for User Needs in the Requirements Engineering (RE) process combines active elicitation, structured documentation, continuous validation, and explicit change control to ensure stakeholder needs are understood, traced, and delivered in a way that aligns with overall business goals.

Core concepts and objectives:-     User needs are the expressed goals, constraints, and expectations users have for a system. They define why the system exists and what value it should deliver. In RE (Requirements Engineering), these needs are transformed into requirements that guide design, development, and testing. This ensures the final product satisfies users and stakeholders.

Best practices for effective needs management:-

ü  Start with a clear problem statement and success criteria to anchor the RE effort.
ü  Elicit from a diverse group of stakeholders to reduce bias and uncover hidden needs.
ü  Communicate decisions transparently to avoid scope creep.
ü  Maintain strong traceability from needs to requirements to tests; document the rationale for each requirement.
ü  Validate early and often with real users or domain experts; use incremental prototypes to gather feedback.
ü  Establish a formal change control process to manage evolving needs without destabilizing the project.
ü  Align requirements with compliance, quality, and usability standards to avoid downstream rework.

 UNIT 2 IS COMPLETED