Mobile App Development: Requirements Engineering Report Analysis

Verified

Added on  2023/01/12

|8
|1052
|84
Report
AI Summary
This report examines the requirements engineering process for a mobile application developed by a start-up tech company. It begins with an executive summary outlining the key aspects, objectives, and outputs of the engineering process. The introduction highlights the company's goal of connecting customers and tradesmen through an app to generate revenue and business opportunities. The main body details the requirements engineering process, including descriptions of each process, objectives, activities, stakeholders, and outputs. The report also includes a requirement elicitation plan, using interviews and observations to identify user needs. It identifies business, functional, and non-functional requirements for the proposed mobile application, such as audit tracking, registration, login, and security. The conclusion reiterates the report's focus on the start-up company's mobile app development and the identification of key requirements. The report references relevant books and journals to support its findings.
Document Page
Requirements Engineering
1
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
EXECUTIVE SUMMARY
The report has been summarised about the requirements of engineering process, key
stakeholders, objectives and output of each process. Furthermore, it has developed or create
requirement elicitation plan for identifying the techniques. The report has concerned about the
mobile that has built a connection with customers, tradesmen. Furthermore, it also identified the
business, functional as well as non-functional requirement of proposed app.
2
Document Page
Contents
EXECUTIVE SUMMARY.............................................................................................................2
INTRODUCTION...........................................................................................................................4
MAIN BODY..................................................................................................................................4
CONCLUSION................................................................................................................................7
REFERENCES................................................................................................................................8
3
Document Page
INTRODUCTION
The report is based on the start-up tech company which are currently seeking to develop
mobile application that provide the better services of customer. The primary objective of
application is to connect with customers, tradesmen. In order to increase revenue stream of
company and also generate business opportunities in global world. The report will describe about
the requirements of engineering process, key stakeholders, objectives and output of each process.
Furthermore, it will create requirement elicitation plan for identifying the techniques. It will
identify the non-functional, business and functional requirements of mobile application
development.
MAIN BODY
1).
a). Description of each requirements engineering process.
As per case study, it has proposed the continuous requirement engineering process for
mobile application development project. It mainly focused on the design time and run time
issues. Start-up company consider design time as time when user interface that created
application and perform activities (Kästner and Kang, 2020). On the other hand, run-time as
when application is actually running and used in marketplace.
The requirement engineering is mainly concerned about the Lifecyle of mobile
application development. it is similar to the software development life cycle that support for
executing different phases in step by step manner. For instance, Developer will be selecting the
software model such as agile, spiral and waterfall. The selection of methodology depend on the
project of application. Furthermore, it should be considered the essential characteristics which
are undertaken in the project.
Consider user requirement
Develop in short time intervals
Emphasis the more on user interface.
4
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
b). Objectives, main activities, key stakeholders and output of each process.
Objective
The primary objective is to build a connection between customer, tradesmen while
increasing overall productivity and profitability in marketplace.
Main activities
Customer can access mobile app to search information through tradesperson profile and
also trying to contact. In most cases, they are instantly sending message.
Tradesperson can put the profile on app if in case any job available, customer contact
through in app instance messenger (Kopczyńska, Ochodek and Nawrocki, 2020).
If the job completed move to the transaction process, it will be done by using application
due to secure sensitive information. Afterwards, customer also seen the review and rate
of tradesperson through application.
Key stakeholders
Customer
Tradesmen
Employee
Manager
Output of process
It provides the facility to access information at any place by using mobile application. In
order to show accurate result or outcome.
2) Create plan for requirement elicitation activities
The requirement elicitation is a process for measuring the overall software project. In this
way, it is important phase in mobile application development to identify user interact. As per
case study, it has proposed the evaluation that used to elicit requirements. The nature of mobile
application become user-friendly which easier for customer or tradesmen to access information
in proper manner (Patkar, Ghafari and Hotomski, 2020).
The requirements elicitation is the best practice of researching and discovering the
requirement of mobile application from stakeholder, users and customers. In mobile application
project, it will use two technique of requirement elicitation such as interviews and observations.
These are commonly used method in requirement elicitation which help for identifying
5
Document Page
requirement of client. Afterwards, designing application so that they can fulfil demand of
customers.
Interview process: it is based on multi-stage process for identifying the opinion of
manager where how they can implement new idea within app development (Patkar,
Ghafari and Hotomski, 2020).
the start-up company conduct interview so that it can be identified as follows:
Interviews: Manager
Interviewer: Project Analyst
Interview Question:
How mobile application is effective for communication?
How it is beneficial for customers?
What are advantages of mobile app in the business growth and development?
3)
a. Business requirements
it is identified the business requirements.
Audit tracking
Reporting requirement
b. Functional requirements
It can be identified functional requirements of proposed mobile application.
Administrative function
Registration
Login
Transaction process
Confirmation
Master form
c. Non-functional requirements
It can be identified non-functional requirements of proposed mobile application.
Security
Reliability
Scalability
6
Document Page
CONCLUSION
From above discussion, it concluded that the report is focused on the start-up tech
company which are currently seeking to develop mobile application that provide the better
services of customer. It has summarised about the requirements of engineering process, key
stakeholders, objectives and output of each process. Furthermore, it can be determined
requirement elicitation plan for identifying the techniques. It will identify the non-functional,
business and functional requirements of mobile application development.
7
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
REFERENCES
Book and Journals
Kästner, C. and Kang, E., 2020. Teaching Software Engineering for AI-Enabled Systems. arXiv
preprint arXiv:2001.06691.
Kopczyńska, S., Ochodek, M. and Nawrocki, J., 2020. On importance of non-functional
requirements in agile software projects—a survey. In Integrating Research and Practice
in Software Engineering (pp. 145-158). Springer, Cham.
Patkar, N., Ghafari, M. and Hotomski, S., 2020. Caveats in Eliciting Mobile App
Requirements. arXiv preprint arXiv:2002.08458.
8
chevron_up_icon
1 out of 8
circle_padding
hide_on_mobile
zoom_out_icon
[object Object]