Assignment no : 2

Software Requirement
Engineering

Submitted By:

Registration no :

Class :

KHAWAJA FAREED UNICERSITY OF

ENGINEERING AND INFORMATION
TECHNOLOGY
Q#1.

Suggest why it is important to make a distinction between

developing the user requirements and developing system
requirements in the requirements engineering process.

Answer :

User Requirements :

User requirements are statements about what the user needs the system to
do to solve a specific problem or meet a specific need.

They are generally written in the language of the user and describe the
desired outcomes, features, or functions of the system.

System Requirments:

system requirements are technical descriptions of how the system should

be built to meet the user requirements.

They define the specifications for the system components, interfaces,

performance, security, and other technical aspects necessary to build the
system.

Difference:

The main point of distinguishing between user requirements and system

requirements is to have precision around the perspective, which helps in
making more effective trade-offs, as well as ensuring the appropriate lens
is used when needed.This can lead to better outcomes in software
development projects.
Q#2.

A company decides to develop a web site, which lets people

buy and sell their software applications. This company
works as negotiator between buyers and sellers and takes
commission for this service. The company aims to develop
this website user friendly. You are required to study this
idea deeply and prepare Functional requirement
specification of placing online order module. Note: Before
writing the Functional specification, try to understand the
domain by carefully going through some websites where
online order placing is done.

Answer :

A company decides to develop a web site, which lets people buy and
sell their software applications. This company works as negotiator
between buyers and sellers and takes commission forth is service. The
company aims to develop this website user friendly.
Functional requirements specifications foe placing online order :
 User Registration and login.
 Searching browse.
 Details of products.
 Adding to cart.
 Checkout process.
 Payment method.
 Confirmation and tracking.
 Dashboard.
 Security.
 FeedBack.
By these functional requirements, the online order placing of the website
will provide a user-friendly experience for buying and selling software
applications while ensuring security, and efficient transaction
management.

Q#3.
Explain which requirements elicitation techniques could be
used in the website project from Question No. 2 and for each
technique, specify the stakeholders that this technique is
suitable for. Describe how you would concretely use each
technique in practice with the specified stakeholders, within
the given project.

Answer :
Requirement elicitation can be done by communicating with stakeholders
directly or by doing some research, experiments. The activities can be
planned, unplanned, or both.
1.Interview :

Stakeholders : Developers, buyers, sellers, Costumers service

representative.
Usage : Conduct structured and unstructured interviews with the
stakeholders to gathers their needs, preferance and points.
2.Questionaries:
Stakeholders: Buyers, sellers, existing users (if available).
Usage: A document with pre-defined set of objective questions and
respective options is handed over to all stakeholders to answer, which are
collected and compiled.
3.Survays:
Stakeholders: Buyers, Sellers, targeting audience, marketing team.
Usage : Organization may conduct surveys among various stakeholders
by querying about their expectation and requirements from the upcoming
system.
4. Task analysis
Stakeholders : Business analysts, project manager, client, developer.
Usage: Team of engineers and developers may analyze the operation for
which the new system is required. If the client already has some software
to perform certain operation, it is studied and requirements of proposed
system are collected.
5. Domain Analysis
Stakeholders : Business analysts, project managers, clients,
developers.
 Usage :Every software falls into some domain category. The expert
people in the domain can be a great help to analyze general and specific
requirements.
6. Brainstorming
Stakeholders: project managers, developers, business analysts.
 Usage :An informal debate is held among various stakeholders and all
their inputs are recorded for further requirements analysis.