Facilitated Application Specification Technique (FAST)

Running head: REQUIREMENT ENGINEERING
REQUIREMENT ENGINEERING
Name of Student
Name of the University
Author notes
Word count

2REQUIREMENT ENGINEERING
Executive summary
The primary purpose of this report is to understand requirement-engineering process related
to the software. The notable impact of requirement engineering can be observed from this
study, as well as the impact of poor requirement engineering can also be found. It has been
found that requirement-engineering process aids the company to understand the problems of
the software as well as provides an understanding of the requirements and priorities of the
software. It can also be observed that poor requirement engineering can influence in the
control process of the software.

3REQUIREMENT ENGINEERING
Table of Contents
Introduction................................................................................................................................4
Qualification for requirement engineering.................................................................................5
Importance of requirement engineering.....................................................................................5
Impact of poor requirement engineering in the process.............................................................6
Areas of Requirement engineering.............................................................................................6
Requirement elicitation..........................................................................................................7
Brainstorming.....................................................................................................................7
Facilitated Application Specification Technique (FAST)..................................................8
Quality Function Deployment............................................................................................9
Delphi techniques...............................................................................................................9
Use case-based Requirement elicitation.............................................................................9
Requirement analysis...........................................................................................................10
Requirement specification....................................................................................................10
Requirement validation........................................................................................................10
Software requirement...............................................................................................................10
Functional requirement........................................................................................................10
Non-functional requirement.................................................................................................11
Business requirement...........................................................................................................11
Final advice..............................................................................................................................11
Conclusion................................................................................................................................12
References................................................................................................................................13

4REQUIREMENT ENGINEERING
Introduction
ABC Pty Ltd is a tech company, which is starting its business and tends to operate it
from Sydney, Australia. They are developing an app, which will provide trades and services
to their customers. ABC believed that this app would increase its revenue and will bring
business opportunities over the network. The Engineering process, which defines, maintains
and documents the requirements of engineering, is known as requirement engineering.
Requirement engineering has a role in systems and software engineering. Requirement
engineering is a branch of software engineering, which aids the software to run effectively in
a system (Fantechi et.al., 2018). It is a very essential and important phase of software
development. The primary degree of success of a software system is which it meets its
purpose when needed and implemented in a system. Requirement engineering discovers the
purpose of the software system, identifies the need of the stakeholders and documents them
into the analysis (Sheikh, 2018). It also includes communication and implementation of the
software. It is a sub-function of system engineering practices. This process gathers and
defines services provided by the system. ABC private limited engaged a requirement analyst
who will assist them by providing information related to requirement engineering. The
requirement analyst will advise ABC Pty Ltd about the requirement engineering in this
report. The purpose of this report is to provide advice to ABC regarding requirement
engineering. The requirement engineering will assist ABC to develop the app more
accurately addressing the needs of the company (Laplante, 2017). Requirement engineering
will aid ABC Pty Ltd by addressing the issues of the business and community as well as will
thoroughly study the software to make it more accurate.

5REQUIREMENT ENGINEERING
Qualification for requirement engineering
There are certain qualifications needed for requirement engineering that ABC Pty
should consider when choosing an engineer. There are three levels that an engineer should
have to be a requirement engineer. These three levels include foundation, advance and expert
level. Each level has an examination that needs to be cleared.
To achieve a certificate on the foundation level, the engineer should have proper
knowledge of the core subject. After clearing the subject of the examination, the expert gets a
certificate.
To get a certificate on the advanced level, the engineer should clear the examination.
They should clear the CPRE Foundation level examination for the certificate. The
International Requirement Engineering Board gives the certificates to the engineer after
completion of the three-level examination (Pohl, 2016). ABC Pty Ltd should assess the
certificates of the engineer before hiring a requirement engineer.
To program the software successfully, the engineer should know the programming
and coding.
Importance of requirement engineering
Requirement engineering has a key impact on software development that is
noteworthy to mention. Most of the project fails because of poor requirement management.
By using proper engineering methods, the software can work efficiently and providing proper
user experiences to all of its users (Satyarthi & Pandey, 2017). Proper requirement
engineering will provide a low development cost of the app aiding in software development.
Requirement engineering is a very complex yet important for any software. Requirement
management is essential and necessary for the success of software that should be understood.
However, there are certain difficulties in this process. The stakeholders can be large in

6REQUIREMENT ENGINEERING
number, and their goals can conflict with each other depending on the perspectives of each
other.
Impact of poor requirement engineering in the process
Poor requirement engineering can influence the software massively. The problems, which
can occur in requirement engineering, is given below with the possible solutions.
 Poor requirement management can influence in the management process. Most of the
time, without proper requirement engineering, the maintenance, control and
automation of the software get difficult (Dick, Hull, & Jackson, 2017).
 Poor requirement engineering can lead to inadequate tool support for the software. It
gets challenging for the management to maintain the software adequately without
proper requirement engineering.
 The information about the software can be missing, therefore, making it difficult for
the management to trace the requirement of the software.
The possible solution for these problems is hiring an experienced requirement engineer
who has sufficient knowledge about requirement engineering.
Areas of Requirement engineering
ABC should understand the areas of requirement engineering before implementing
requirement engineering for their software (Laplante, 2017). ABC should imply Requirement
engineering by following certain requirement engineering steps which includes
 Requirement elicitation
 Requirement analysis
 Requirement Specification
 Requirement validation.

7REQUIREMENT ENGINEERING
Requirement elicitation
Being the first step of requirement engineering, requirement elicitations gathers the
data what exact requirement the software will fulfil. The primary purpose of requirement
elicitation is to identify the requirement of the software by gathering information from the
software (Milani, 2019). For the “App”, it will fulfil the need of their customers by providing
them trustworthy tradesman who will provide the repair services. Secondarily, the app will
provide their customers to find a trustworthy tradesman for their job. The tradespersons can
be able to find a job posted on the app including heating and cooling services, airport pickup
and delivery, garbage removal and other handyman jobs. Requirement elicitation has primary
two advanced methods that ABC should be advised to follow.
Brainstorming
This group approach evaluates the exact requirement from the customer. For this, an
effective session is conducted, which gathers and documents their ideas. After the session is
complete, a detailed report is prepared, and the document will be prepared, which have the
list of requirements and the priorities (Przybyłek & Zakrzewski, 2018). For successful
elicitation, various stakeholders are selected thereafter the session is conducted. The
requirement and priorities of this software is given below which will aid ABC to understand
what should be their priorities and what are the requirements from the customers and
stakeholders.
Requirements
 The software should be able to provide a secure interface through proper methods of
identification of their users.
 The software should be able to work 24*7 without any crash in the system.
 The software should behave secure payment option through in-app portals.

8REQUIREMENT ENGINEERING
 All types of job profiles of the tradesman should be available in the app.
 The customers should be able to find their tradesman effortlessly through the app and
contact them through in-app messenger.
Priorities
Understanding the above requirements, ABC should priorities the requirements as follows
1. The software should have safety and security, providing the best services to their
customers.
2. The software should have all types of job profiles of their tradesman.
3. The software should provide a smart and secure user interface, which should have
proper identification of their customers.
4. The software should work 24*7, providing best and fast service to its customers.
Facilitated Application Specification Technique (FAST)
FAST aids the management team by identifying and solving the problems of the
software (Thew & Sutcliffe, 2018). ABC is advised to identify and solve the problems of the
software before introducing them to the market. Here are some possible problems of the
software along with the solution to the problems.
Problems
 Regular crash of the interface.
 Payment issues.
 Security errors.
 Identification errors.
Solutions

9REQUIREMENT ENGINEERING
 Regular security check of the software for any bloatware or virus causing the crash or
payment errors.
 Provide more user-friendly UI to the software.
 Save the credentials of the users, therefore, solving the identification and security
problem of the software.
Other than these two methods, there are other methods of requirement elicitation, which
ABC can follow to make the software more effective.
Quality Function Deployment
This method identifies the types of requirements documents them. Each of the
requirements is categorised by three requirements (Franceschini, 2016).
Normal requirement: The software should be able to restrict unauthorised access to
the software.
Expected requirement: The software will provide 24*7 uninterrupted access to the
users.
Exciting requirement: These requirements are beyond the expectation of the
customers and provides satisfaction to the customers. The software can provide all of the
important files to their users.
Delphi techniques
This technique provides sessions to all of the participants and makes a note of their
requirement that is needed in the software (Rai, Gupta & Kumar, 2017).

10REQUIREMENT ENGINEERING
Use case-based Requirement elicitation
This approach uses text and pictures to improve the understanding of the user
requirement (Dawson & Saad, 2017). This approach also aids the organization to understand
the requirement of their users.
Requirement analysis
Requirement analysis should be done after the requirement elicitation process, which
aids in the identification of risks associated with each requirement and analysis. Analysis
should include the development costs, efforts and development time in the analysis Geogy &
Dharani, 2016).
Requirement specification
After the requirement elicitation is done, this activity is done and analysed. The
requirements should be recorded in the form of charts, programs and written documents. This
program is known as the Software Requirement Specification (SRS) document. The issues of
the software function should be recorded in the SRS. SRS is a portable, maintainable and
secure document (Jindal, Malhotra & Jain, 2016).
Requirement validation
Requirement validation certifies the SRS document in an acceptable format; therefore,
the errors in the requirement process are identified and fixed. Requirement validation should
include various techniques such as review, distribution of the document, organise the meeting
and review the SRS document.
Software requirement
Primarily, there are two types of software requirement. Functional and non-functional
requirement.

11REQUIREMENT ENGINEERING
Functional requirement
The functional requirements should provide technical details and functionality of the
new software. The functional requirement should describe how the software would work on
the platform (Kurtanović & Maalej, 2017). The developers of the app should implement these
functions to enable users to accomplish their tasks. It describes how the software will perform
and what will be its functions. Functions include calculation of data, user interaction or other
specific functionality, which will aid the software to perform better in the system. Examples
of functional requirement include the color of the background of the software, validation
techniques of software, user interface, end-user agreement and information about revenue of
the worker, which the individual only can access. The app will hire a tradesperson to handle
their customers.
Non-functional requirement
Non-functional requirement defines the quality attribute of the software. Non-
functional requirement represents a set of standards that are evaluated to judge the operation
of the software. It is important in ensuring the usability and effectiveness of the software
system (Garg, & Singhal, 2017). User login, important information’s to the users, the privacy
of information’s are the examples of non-functional requirement. It also includes information
about pickup and delivery, heating and cooling user interface services and other tradesman
and handyman jobs.
Other than that, requirement engineering also includes business requirements.
Business requirement
The primary business requirement of this software is to generate revenue for ABC Pty
Ltd by connecting tradesman to its customers. This app will generate huge revenue by
following the requirement engineering process in the software. Other than that, ABC will also

12REQUIREMENT ENGINEERING
satisfy the needs of the customers by proving them best quality services through the app,
which will improve their relationship with the customers.
Final advice
ABC Pty should implement requirement engineering as it will provide them with
understanding the issues of the software as well as will aid them to identify the problems of
the software. After the requirement engineering is implemented, it is advised that ABC
should properly review the contracts of their stakeholders. ABC should understand the
enduring and volatile requirement of their software. The enduring requirement includes the
stable requirements of the software, which will drive them to relate directly to the system.
Volatile requirements are the changing requirements of the customers. These requirements
are volatile as it changes with environmental technology and customers’ expectations.
Conclusion
From the report, it signifies that requirement engineering has a notable impact on the
operation of the software. It is advised the ABC to implement requirement engineering
process before introducing their new software to the market which will improve its stability
as well as will aid ABC to generate their revenue from primary as well as from the secondary
activities. The impact of poor requirement engineering can also be observed from the report.
Therefore, it can be stated that requirement engineering should be implemented in every
organisation before introducing their software’s to their market.

13REQUIREMENT ENGINEERING
References
Fantechi, A., Ferrari, A., Gnesi, S., & Semini, L. (2018, August). Requirement engineering of
software product lines: Extracting variability using NLP. In 2018 IEEE 26th
International Requirements Engineering Conference (RE) (pp. 418-423). IEEE.
Sheikh, B. T. (2018). Interdisciplinary Requirement Engineering for Hardware and Software
Development-A Software Development Perspective.
Laplante, P. A. (2017). Requirements engineering for software and systems. CRC Press.
Pohl, K. (2016). Requirements engineering fundamentals: a study guide for the certified
professional for requirements engineering exam-foundation level-IREB compliant.
Rocky Nook, Inc..
Satyarthi, S., & Pandey, D. (2017). Framework for Requirement Management using
Requirement Traceability. International Journal of Advanced Research in Computer
Science, 8(5).
Osman, N. (2018). A Software Requirement Engineering Framework to Enhance Critical
Success Factors for ERP Implementation. International Journal of Computer
Applications, 180(10), pp-32.
Dick, J., Hull, E., & Jackson, K. (2017). Requirements engineering. Springer.
Milani, F. (2019). Requirement Elicitation Using Business Process Models. In Digital
Business Analysis (pp. 311-319). Springer, Cham.
Przybyłek, A., & Zakrzewski, M. (2018). Adopting collaborative games into agile
requirements engineering.

14REQUIREMENT ENGINEERING
Thew, S., & Sutcliffe, A. (2018). Value-based requirements engineering: method and
experience. Requirements engineering, 23(4), 443-464.
Franceschini, F. (2016). Advanced quality function deployment. CRC Press.
Rai, A., Gupta, G. P., & Kumar, P. (2017). Estimation of software development efforts using
improved delphi technique: A novel approach. Int. J. Appl. Eng. Res., 12(12), 3228-
3236.
Dawson, C. W., & Saad, A. (2017). Requirement elicitaton techniques for an improved case
based lesson planning system.
Kurtanović, Z., & Maalej, W. (2017, September). Automatically classifying functional and
non-functional requirements using supervised machine learning. In 2017 IEEE 25th
International Requirements Engineering Conference (RE) (pp. 490-495). IEEE.
Geogy, M., & Dharani, A. (2016). A scrutiny of the software requirement engineering
process. Procedia Technology, 25, 405-410.
Jindal, R., Malhotra, R., & Jain, A. (2016, September). Automated classification of security
requirements. In 2016 International Conference on Advances in Computing,
Communications and Informatics (ICACCI) (pp. 2027-2033). IEEE.
Garg, U., & Singhal, A. (2017, January). Software requirement prioritization based on non-
functional requirements. In 2017 7th International Conference on Cloud Computing,
Data Science & Engineering-Confluence (pp. 793-797). IEEE.