American International University-Bangladesh (AIUB)

Department of Computer Science

Faculty of Science &Technology (FST) Summer
20-21

Assignment Title
Assignment on Requirement collection
Subject: SOFTWARE REQUIREMENT ENGINEERING
Section: A

Group member’s details

NAME ID
Mohonto, Pronay Kumar 18-38224-2

Banik, Hordoya 18-37995-2

Deep,Md Nazmul Ahamed 18-38008-2

Shusmita,Shanzida Akter 18-37982-2

To build a software that solves problem you need to know or understand the
problem first. By collecting requirements of the specific problem we can easily
understand the solution of the problem. The hardest part of a software
development is collect the all the correct requirements. And If we create a
project that does not serves the purpose of the client that does not satisfy the
client then there is no need to build it instead of benefit there is loss. That is
why it is important to understand what exactly the customer want from the
project. As a project manager first I have to collect the main levels of a software
requirement. And as the project is automated with ERP this will help us to
centralized all the data in one location . In this system the database is shared in
all other departments so the shared data will help us to easy metric reporting and
quick implementation of multiple functions.
There are three different levels for a software requirement .They are-
 1. Business requirements
 User requirements
 Functional requirements
The alignment among these three requirements is very important for the success
of a project. So I have to give very importance to collecting these requirements
properly. In Business requirements it is very important to understand that why
the organization or the company want to implement the project. The main thing
is we have to collect all the business objectives and the plan .In user
requirement we will collect all the goals and tasks that will need to perform any
product. We will use user case and story to find the requirements. And last we
will collect the functional requirements which is related to the behaviour of the
product. In this case our product will be frozen food . After collecting the
requirements the most difficult section of developing a project.

We can develop our projects by doing separate tasks to achieve requirement

engineering in a project. Elicitation, analysis, specification, validation, and
management are the tasks involved. Requirement development is a iterative
process. We will use the elicitation task first in our project.

Elicitation is gathering information from stakeholders and identify the

products. As our project is about poultry farm and frozen food our product will
be the chicken and stakeholders are the farmers and investors. In elicitation we
try to understand the business objectives and the goals. To put it another way,
first we have to analyst business and interacted with stakeholders to gain a
better knowledge of their needs. In elicitation we can apply Prototyping.
Prototyping is used to identify requirements that are either absent or undefined.
Clients are given frequent demos by producing prototypes in this technique so
that they may obtain a sense of how the product will look. Prototypes can be
used to produce a mock-up of a site and use diagrams to describe the process. It
Gives a visual representation of the product and the Stakeholders can provide
feedback early. To collect all the necessary requirements from the stakeholders
we can arrange a elicitation session. During the elicitation session we have to
keep the discussion focused on its objective. Attendees have to prepare question
for the conversation. Based on their answer we have to suggest ideas. Because
is all the member in a team think indivisualy then a lot of out of the box ideas
will come out. We have to agreed on some basic rules such as turn off electronic
devices during the meeting, holding one conversation at a time, expecting
everyone to contribute and give ideas, ask question. Once the rules are set then
we have to make sure that everyone are following the rules. One person known
as facilitator must make sure that everyone is listening the rules that are covered
in the meeting. We need to create a clear plan and work shop agenda ahead of
time and communicate with the developers so that they know what to expect
and start the work accordingly. We have make sure that all the requirements that
are proposed by the customer lie on this project. During elicitation discussion
quality attributes, business rules, user interface ideas, and more information will
be discussed

Then we need to implement analysis in this project for analysis we need to

develop a model application environment for the project. As our project is a
ERP system we have to develop a plan to model or design the project. ERP
increase organizational efficiency by utilizing recourses. In analysis section we
also Decomposing high-level requirements in a simple understandable
requirements. After that in analysis we start allocating requirements for the
system architecture .The last thing we need to do is Negotiate requirements
priority and the implementation priorities of the system requirements.

The next we need to do is specify the requirements in Specification section.

This is very important section for a software requirements because here we
collect SRS document. Here all the users needs to write all the requirements
and diagrams for the suitable for comprehension, review, and use by their
intended audiences .In this section we try to describe all the necessary and the
expected behaviour of the software system. In specification we Adopt
requirement document templates and identify the requirement origin and try to
Uniquely label each of them. To collect all the requirements properly we have
to arrange an interview with the company. It is impossible to arrange interview
with every employee of that company hence we can conduct interview with
the high command of that company. Then we can implement Facilitated
Application Specification Technique this is a crew orientated technique which
is evolved for wishes accumulating and is referred to as facilitated software
specification Techniques FAST. This method helps the introduction of a joint
group of clients and builders who paintings collectively to apprehend the
expectancies and recommend of set of requirements

After the specification is done we will try to validated all the documented
requirements in the section validation. We will try to correct the problems
before the development group accepts them and start the development. Here we
will also check that no requirements should be contradictory ,Completeness or
unnecessary requirements. By Developing the acceptance tests and try to
confirm that a product based on the requirements would meet customer needs
and achieve the business objectives and also simulate the requirements to find
the errors.Requirement has some activities few of them are Knowledge of the
overall area where the systems is applied, The details of the precise customer
problem where the system are going to be applied must be understood,
Interaction of system with external requirements, Detailed investigation of
user needs, Define the constraints for system development.

After collecting the development requirements we need to manage all the

requirements in our next section which is called Requirements Management.
Here we will check the impact of changes the requirements and establish the
connection with the control process. we will track the requirements and try to
track the issues and also maintain the track history of the requirement
changes. We also try to define all the relationships and dependencies exist
between requirements.

This is all are the initial task to do collect all the requirements after that we
have to finalize all the requirements. We can finalize the requirements by
paper prototyping, Mocks-up, Wireframing, proofs of concepts etc.