Software Requirement

Engineering
In Software Engineering
 Presentation Submitted TO : Mr Kamran.

Submitted From : Manahil Mumtaz,

Muhammad Tayyab,
Aliza Saeed,
Momina Imran.

DEPARTMENT OF INFORMATION TECHNOLOGY

NUML UNIVDERSITY MULTAN
CONTENT:

 Software Requirement Engineering

 Process Of Software Requirement Engineering

 Functional & Non-Functional Requirements

 Development Use Case In Software Requirement Engineering

 01
Software Requirement Engineering.

Presented By : Manahil Mumtaz.

Roll No : 204_BS-IT (2nd).
Software Requirement Engineering:

“Software Requirement Engineering is a process that enables us to systematically

Determine, Analyze, Document and Check the requirements of a software product”

Software requirements engineering refers to the first phase,

before any of the actual designing, coding, testing, or
maintenance takes place. The goal is to create an important
early document and process in the software design.
 Requirements form the basis of all Software products.

 Complete description of what the software system will

do, is represented by software requirement.

 Software requirements are complete specification of the

desired external behaviour of the software system to be
built.
Sources of Software requirements

 Stakeholders : (people affected in some way by the system).

 Documents.

 Existing Software.

 Domain/Business ideas.
 Importance of software Requirement
Engineering
Why is it so important? Like all products, the makers of software
are seeking to produce the best product in the most cost-efficient
manner. If software errors are found in the requirements phase, they
are much, much less expensive to fix than if they are found in later
phases of the development process. For systems regarding safety,
the errors in requirements could potentially be even more harmful
than just losing money.
 Requirements engineering is a tool for regulating
processes in software development life cycles (SDLCs).

It’s not only crucial at the beginning of a project, when

specifications are usually first created, but throughout all stages as
projects often require changes or new specifications while
development is in progress. Engineering and managing requirements
are key processes to maintain control over a project and ensure
coherence across the board. They also enable teams to identify,
analyze and manage changes so that a project stays aligned with
clients’ expectations. Software requirements engineering practices
positively impact different aspects of software development:
 Gathering the crucial requirements
 The ability to apply the right requirements gathering techniques is
essential for the success of a software development project. You
shouldn’t rely on just one method of collecting requirements – you’ll
achieve the best results by combining different techniques, such as:

 Questionnaires and surveys,

 Collaborative workshops and brainstorming sessions,
 Observing existing software and solutions in development,
 Artifact-based analysis,
 Other supporting activities e.g., mind maps, class-
responsibility-collaboration (CRC) cards, use case modeling
and prototyping.
02
Process of SRE.
Presented By : Muhammad Tayyab.
Roll No : 173_BS-IT (2nd).
Process Of Software Requirement Engineering
 The Process to gather the Software Requirement from customers,

Analyze and Document them is known as Requirement Engineering.

Steps Involve in Software Requirement Engineering:

Feasibility Study
 Requirement Elicitation and Analysis.
 Software Requirement Specification.
 Software Requirement Validation.
 Software Requirement Management .
 Feasibility Study
 To create and analyze the reason for developing the software that is
acceptable to users.
 To check aim & goal of the customer & organization behind implementation
of software .
Types Of Feasibility Study
Technical Feasibility : Evaluate the current technologies, which are needed
to achieve Customer requirement within the time the and Budget.
Operational Feasibility : Required software solve business problems and
customer requirements.

( The Output is to decide whether or not the project should be undertaken. )

 1. Requirement Elicitation & Analysis
 Requirement Elicitation is the process of gathering actual requirement

about the needs and expectation of stackholders for a software system.

 To understand customers, Business Manuals, The existing software

of same type , standards and other stakeholders of the project.

Techniques of Requirement Elicitation:

I. Interviews.
II. Survays.
III. Focus Group.
IV. Observation.
V. Prototyping.
 2. System Requirement Specification
 Requirement Revcieved from client are written in natural language.
 After Collecting , System Analyst to document the requirement in technical
language.
 SRS include Data Flow Diagram, Data Dictionary, Entity Relationship
diagram.
SRS Defines:
 How the intended Software will interact with hardware.
 External interface/ GUI.
 Speed of Operation, Response time of system .
 Portability of software across various platforms.
 Maintainability.
 Security Quality And Limitations etc.
 3. System Requirement Validation

 After Sdeveloped, the requirement Discussed in this document are

validated or Tested .
 Requirement Validation done through Requirement reviews taken
by customer, after developing prototyping check with customer &
Test case generations.
Conditions :
 If they can practically implement .
 If they are correct and as per the Functionality and specailly of
software.
 If they can Describe.
 Any changes and aditional requirements.
 4. Software Requirement Management
 Requirement Management is the process of managing changing

requirement during the requirements engineering process.

Activities involved in Software Requirement Management:

Tracking & Controlling Changes: Handling Changing requirements

from customer.
Version Controling: Keeping Track of different version of System.
Communication:Trace to software is design, develop or test as per
requirements or not.
Monitoring & Reporting: If changing requirements has any issue
cantact with client within time.
03
Functional & Non-Functional
Requirements.
Presented By : Aliza Saeed.
Roll No : 201_BS-IT (2nd).
04
Development Use Case In SRE.
Presented By : Momina Imran.
Roll No : 206_BS-IT (2nd).