Executive summary

 
Requirement Engineering is the process of analyzing, maintaining, defining, and
documenting process requirements in the engineering design process. Its main role is in
software engineering and system engineering. It also helps in specifying the solutions that
are required by the organization. In addition to that different steps are also involved such as
Feasibility Study, Elicitation, and Analysis of requirement, Software Specification
requirement is the documenting and defining the process for requirement engineering.
Along with Software Validation and Software Requirement Management are the steps of
prime importance in the respective process. This report has highlighted the RE process and
its types. Along with that, it has also discovered the necessity of RE process by XYZ pty
company in terms of the creation of the respective application. This report will also discuss
the importance of collecting effective requirements before implementation, planning, and
execution of any application. It will also explain the basic requirements as Business
Requirement, Functional Requirements, and Non-Functional Requirements. It also discusses
the Minimum Viable Product approach.

Introduction

This report has been prepared on XYZ Pty Ltd company, is an established company that has
been selling hardware tools and paints for the last 30 years using a traditional business
model, based on tradesmen coming to the store and selecting the goods they want to buy.
The case requirements of XYZ Pty Ltd company to expand their business to include an on-
line catalog where items to be browsed, to be put in the shopping bag, and to make an
online payment for select items with goods either being collected from the store or received
via a courier. The principle target of this report is to increase sales, make it a more time-
saving process for the traders, and also to allow other people to shop on-line with
convenience, understand the requirements with envisaged sales growth of 20% in the
development of the application.
Considering the scenario, XYZ is aiming for customers a platform, where they can browse
the catalog, explore particulars of items in detail, add them to the shopping bag, the
number of items selected can be changed, can add and delete items to/from the shopping
bag, select the option of pick-up from store or delivery at home and can make an online
payment or send an inquiry to the store regarding order to be placed. The payment would
be made online or received online at the time of delivery, so this system should possess
enhanced security or privacy techniques. The Company wants to implement the first
Minimum Viable Product (MVP) in the next six months, In the following sections, it would be
discussed that how further investment will be done to finalize the full version in six months,
based on a satisfactory assessment of the MVP implementation. 

Importance of Requirement Engineering

It is crucial to understand the exact requirements of the customer and document them
properly to make the prototype design of an application / a product before it is to be
developed to meet the requirements of real-time scenarios. It is of major concern to get the
outcomes that would be expected from the client and system requirements. (Rivera et al.,
2018) stated that around 80% of the businesses around the world have registered
themselves online which is making it possible to bring more business opportunities for the
people around the world. 

The requirement engineering concept is to understand the exact requirements of the

customer and adequately document them. Both the software engineer e customer work
along to document all the interfacing requirements, functions, and performance of the
application. (Mughal et al., 2018) defined requirement engineering as a method that is
crucial in building the structures for the center programming requirements to obtain the
précised outcomes. Explained it in simpler words by saying that it is crucial to document and
plan all the challenges that could be faced during the development of the system. In this
period, a large document which is Software Requirement Specification (SRS) is created,
which contains a detailed description of the system dos and don to in the common
understandable language. So, to fill the gap between the customer demands and the
thought process of the engineers, requirement engineering plays an important role for the
stakeholders. 

Process of Requirement Engineering 

Requirement engineering provides an appropriate mechanism to understand, the

customer’s desire, assessing feasibility, analyzing the need, and negotiating for the solution,
specify the solution with clarity, managing the requirements, and validating all specifications
as they all are transformed into a system application.

RE is a four-step process, which includes –

1. Feasibility Study
2. Software Requirement Elicitation and Analysis
3. Software Requirement Specification and Validation
4. Software Requirement Management
Requirements engineering activities depends on the type of system to be developed and the
specific practices) involved in an organization. These may include:

1.    Requirement elicitation or Requirement inspection (REN): Stakeholders and engineers

and meet, all concerning needs and want, regarding the software application or product.
2.    Requirement negotiation and analysis: Requirements, taking new ones if the
development is iterative, are identified, and conflicts with stakeholders are resolved at this
stage. written and graphical Both tools are used to successfully aid the requirement. 

3.    System modeling (SM): A few engineering situations or fields specifically require the
product to be completely modeled or designed, before its implementation and utilization
starts. Therefore, this phase must be performed before implementation or utilization.

4.    Requirements specification (RS): These requirements are formally documented in a

format, known as Requirements Specification, which becomes official only after the
validation stage. A Requirements specification Stage can have both graphical and written
useful information models like the software requirement specification model. 

5.    Requirements validation (RV): It is checking of all the documented models and
requirements, that are consistent with the requirements of the stakeholder and meet them.
Only after the final draft of the validation process passes, the Requirements Specification
(RS) becomes official.

6. Requirement management (RM): It is about managing all the activities which are related
to the customer desires, requirements, supervising for the system to be developed, and,
until it is put into use.

Requirements and quality can be improved through below mentioned methodologies: 

1. Visualization. It is about utilization of tool which promotes a better clarity of the

required output such as simulation or visualization done.

2. Consistent language. It is utilizing straightforward and steady with definitions for

prerequisites which are portrayed in common/justifiable language and utilizing the
business phrasing which is pervasive in the Organization.

3. Guidelines. It is the thinking about hierarchical rules to depict all assortment

methods and the everything kinds of necessities to be fulfilled. These rules are
additionally executed and utilized reliably over all activities.
 4. Consistent use of templates. It is delivering of a predictable arrangement of models
and formats for the documentation of the prerequisites.

5. Documenting dependencies. It is tied in with reporting all conditions and

interrelationships for prerequisites.

6.    Analysis of changes. It is playing out all main driver revelation and investigation of
changes to prerequisites and taking significant restorative activities.

Software Requirements Prerequisites

Software requirements are foundation for software development project, so it should be

well-defined, clear, and correct.

A Software Requirement Specifications should be:

o Correct
o Clear
o Comprehensible
o Coherent
o Consistent
o Modifiable
o Unambiguous
o Verifiable
o Prioritized
o Credible source
o Traceable

Software Requirements

The actual meaning of requirement which we need to understand is, “an explanation that
characterizes an item or process functional, operational, useful, or design characteristic or
oblige, which is unambiguous testable or quantifiable, and vital for an item or cycle
adequacy” (Dick, Hull et al. 2017). There is always a possibility that customer feedback and
stakeholders may not deliver effective information regarding the customer and business
requirements. For the development of any product or application, it is necessary to target
the viability or minimum viability of the product/ application commercially. In this case,
study XYZ pty company wants to develop an application or we called it an ‘app’, which will
provide customers the interface to browse the catalog, explore particular item's details, add
an item to a shopping bag, change the number of items, add and delete items to/from
shopping bag. In addition to that to select pick-up from store or delivery to the nominated
address and make an online payment.

The following are the crucial software requirements:

A) Business Requirements:
 
1. The business requirements are to increase the sales, to make it more convenient and
timesaving for the traders and other non-trade people to shop on-line to reach the
envisaged 20% sales growth.
2. The Company wants to implement the first Minimum Viable Product (MVP) in the
next six months to finalize further investment for the full version in the following six
months. 

 
B)  Functional Requirements:
 
1. The company needs to provide an interface where customers can browse the catalog
and explore a particular item’s detail.
2. The company also needs to provide an application to add an item to the shopping
bag, change the number of items, add, and delete items to/from the shopping bag.
3. The customer can select pick-up from the store or delivery to the nominated address
option and can make an online payment. 
 

C) Non-Functional Requirements:
 
1. Store personnel can respond to the inquiries and contact the customer via email or
phone based on the details provided by the customer. 
2. Customers will also rate, and review goods purchased, and service provided by the
store. 
3. Store personnel will be able to respond to the customers' reviews.

References:
1. Institute, P. M. (2016). Requirements management. Project Management Institute.
https://public.ebookcentral.proquest.com/choice/publicfullrecord.aspx?p=4603813.
2. Olsen, D. (2015). The lean product playbook : how to innovate with minimum viable
products and rapid customer feedback. Wiley. INSERT-MISSING-URL.