MIS604 Requirement Engineering

Running head: MIS604 REQUIREMENT ENGINEERING
MIS604 Requirement Engineering
Name of the Student
Name of the University
Author’s Note

1
MIS604 REQUIREMENT ENGINEERING
Table of Contents
1. Introduction..................................................................................................................................2
1.1 Purpose..................................................................................................................................2
1.2 Document conventions..........................................................................................................2
1.3 Project Scope.........................................................................................................................3
2. Overall description.......................................................................................................................4
2.1 Product perspective................................................................................................................4
2.2 User classes and characteristics.............................................................................................4
2.3 Operating environment..........................................................................................................6
2.4 Design and implementation constraints.................................................................................6
2.5 Assumptions and dependencies.............................................................................................7
3. System features............................................................................................................................8
3.1 Use case diagram...................................................................................................................9
3.2 Specification for selected use cases.......................................................................................9
3.3 Swimlane diagram...............................................................................................................11
3.4 State-transition diagram.......................................................................................................12
3.5 Dialog map...........................................................................................................................13
4. Data requirement.......................................................................................................................14
4.1 Logical data model..............................................................................................................14
4.2 Data dictionary.....................................................................................................................14

2
MIS604 REQUIREMENT ENGINEERING
5. External interface requirements.................................................................................................17
5.1 User interfaces.....................................................................................................................17
5.2 Software interfaces..............................................................................................................18
5.3 Hardware interfaces.............................................................................................................19
6. Quality attributes.......................................................................................................................19
6.1 Usability...............................................................................................................................19
6.2 Performance.........................................................................................................................19
6.3 Security................................................................................................................................20
7. Nontrivial and valid requirements.............................................................................................20
8. References..................................................................................................................................22

3
MIS604 REQUIREMENT ENGINEERING
1. Introduction
1.1 Purpose
The main purpose of the report is to develop a software requirement specification for the
development of an application that would provide handyman and on demand service to the
customers. The document helps in collection and analyzing the assorted idea of the founder of
the company for defining the application, its requirement with respect to the customers. A
prediction is made on the usage of the application and the expectation of the user is evaluated for
meeting the user objectives and get better understanding about the project (Kaur & Kaur, 2018).
The concept of the application is outlined in the document with the ideas that can be discarded
during the application development.
The purpose of the document is to provide an overview of the application that is needed
to be developed for ABC Pty Ltd. Along with the goals and parameters. The targeted audience is
described in the document and its user interface, hardware and functionality. It also defines the
functionality of the product as needed by the targeted audience. The document help the
developer to get an assistance in the SDLC phase.
1.2 Document conventions
The following conventions are used in the document:
DB Database
DDB Distributed database
ER Entity Relationship
UC Use Case

4
MIS604 REQUIREMENT ENGINEERING
DD Data Dictionary
CRM Customer Relationship Management
FAQ Frequently Asked Questions
RAID 5 Redundant Array of Inexpensive Disk/Drives
CDN Content Delivery Network
1.3 Project Scope
The main scope for the development of the app providing on demand trades and
handyman service to the customer. The focus is given on the company, application of the
stakeholders and application that allows registering with their specialization skills and
requirement, reach to more number of users.
The main aim of the software requirement specification is to specify the requirement of
the software that is needed to be developed and its application is assisting the selection of in
house developer and purchasing of commercial software products. The document is also used for
describing the targeted audience of the project along with the user interface, software and
hardware requirements (Bhatia, Kumar & Beniwal, 2018). The document also defines the
procedure followed by the client, team and the targeted group of user for analyzing the product
and its functionality. It also helps the designer and the development team to getting assistance in
the SDLC model.

5
MIS604 REQUIREMENT ENGINEERING
2. Overall description
2.1 Product perspective
A distributed demand trade and handyman services to the customer is needed to store the
following information:
Trade person details – It include the details of the handyman who registers with the app
with their name, address phone number, skills and needed to be inputted in the application along
with availability and area served by the tradesmen for increasing transparency of the application.
Customer Details – The customer needs to input the details such as customer name,
address, phone number for registering with the application. The record are needed to be kept
secured and a spate login account is needed to be created such that they can login into the
account for searching for trade’s person.
Reservation Description – the customer can search from the list of service they require
and select the handyman registered with the app for chatting directly with the tradesman and
appoint him for the specified job. For the reservation the customer is needed to be registered with
the system and a reservation code is generated with the details such as date of booking and time
provided by the tradesman for solving the problem of the customer.
2.2 User classes and characteristics
The users are those people registered with the app and able to login using the app for
retrieving booking information and the previous jobs done from the database connected with the
application. The details of the handyman is needed to be provided with the skills and
specialization such that it can be used for assigning them to a specific group and increases the
usability of the customer such that they can reach the tradesman easily. Suggestion is needed to