MIS604 Requirement Engineering Report: On-Demand Handyman Service App

This report presents a Software Requirements Specification (SRS) for an on-demand trades and handyman service application. The report begins with an introduction outlining the purpose, scope, and document conventions. It describes the product perspective, user classes, operating environment, design constraints, and assumptions. Key system features are detailed, including use case diagrams, specifications for selected use cases, swimlane diagrams, state-transition diagrams, and dialog maps. Data requirements, including logical data models and data dictionaries for customers, tradespersons, and administrators, are also provided. Furthermore, the report covers external interface requirements, quality attributes (usability, performance, and security), and concludes with a discussion of nontrivial and valid requirements. The application aims to connect customers with skilled tradespeople, facilitating job postings, reservations, and management functionalities through a distributed database and client-server architecture.

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

6
MIS604 REQUIREMENT ENGINEERING
be provided to the user based on the location of the user and the nearby trades man registered.
Support is provided to the user based on their type, functionality and privileges (Deocadez,
Harrison & Rodriguez, 2017). The tradesman are grouped as employees and the user seeking to
get the jobs done from the tradesperson are grouped as customers. The customer is provided the
access of the customer functionality and tradesperson finding function. They are needed to do the
following functionality:
o Search for tradesperson
o Chat with tradesperson
o Post their Job
o Make reservation
 Flexible Time and date
 Confirmation
o Cancel existing reservation
o View itinerary
The tradesperson is needed to have the management functionality as follows:
 Customer functionality
o Get the details of the customer posted job
o Get the customer contact information
o View scheduled work
 Administrative functionality
o Add/delete skills
o Update rate

7
MIS604 REQUIREMENT ENGINEERING
o Update location address
o Update personal information
Each of the tradesperson should be assigned jobs in a queue such that they does not miss
the deadline of a previously assigned job. When the customer seeks for a tradesperson they can
seed the registered tradesperson and if the tradesperson is engaged with another customer it is
displayed to the customer. The customer can book the tradesperson based on his/her rating if he
is engaged the customer can add him to queue for getting the work done from the tradesperson
later on.
2.3 Operating environment
The operating system environment for on demand trades and handyman service app is listed
below:
 Client Server architecture
 Operating system: Windows Server 2016
 Database: SQL server 2007
 Platform: vb.net/Java/Php/Android/IOS
 Distributed database
2.4 Design and implementation constraints
For the development of the design of the app there are different constraint that are needed to
be eliminated such that the efficiency of the application can be improved. The following are
some of the identified constraint found in design and implementation:
 Global schema, allocation schema and fragmentation schema
 SQL commands for generating query for the above schema and application

8
MIS604 REQUIREMENT ENGINEERING
 Combining the fragments such that they can be used for responding to the complex query
of the user (Brouwers et al., 2018).
 Implementation of database and use it as a centralized database management system.
The virtualization of multiple providers and offloading the end user request from primary
providers based on performance, cost and load. Since the CDN have the proprietary nature
limited information is available for the individual and it is important to retain a load balancing
control in the in-house web server. An implementation model is needed to be prepared such that
CDN peering can be enabled depending on the combination of attributes e.g. Web server
response time and load, expected delay of the network, geographical location (Ali & Xiaoling,
2019). The potential may also vary according to time and no repository is there for listing the
attribute value or expected delay for the interconnected system.
2.5 Assumptions and dependencies
For the development of the application some assumptions are made that would help in
reducing the development time of the application. The product is needed to be developed
leveraging the existing system and the related system is needed to be evaluated such that the
current needs of the system can be clarified. The application of the design and implementation
approach would help in getting a clear guideline about the intended prototype that is needed to be
developed. The software product is needed to be developed and an user manual is needed to be
written that would help in understanding the methodology used for developing the prototype of
the application (Dakic et al., 2018). The system features and the major services that are needed to
be implemented and the features that are dependent on each other is also needed to be evaluated
for identification of the dependency. The modules are needed to be developed and integrated
with each other such that the expected output is generated from the application.

9
MIS604 REQUIREMENT ENGINEERING
3. System features
The system features are used for the identification of the major services and the
functional requirements of the product. The on demand trades and handyman service application
maintains information about the tradesperson i.e. skill, contact details, name, address,
experience, etc. and the customer details such as name, contact details, address, job posted, etc.
The project has the priority since it is difficult for the user to reach the different tradesperson
from remote location and made reservation for getting their job done.
 Simulation and response sequence –
o Search for handyman for getting the job done by tradesperson
o Displaying the detailed list of available tradesperson and make reservation or
engage them to get the job done
o Cancel of the existing reservation or reschedule the date due to unavailability
Functional Requirement
Distributed database – It implies that the application is able to operate transparently on
data spreading across different variety of database and is connected by the means of
communication network.
Client server system – It is used for creating a logical division of the responsibility and
the client is the application running as front end and the server is DBMS forming the back end of
the application. In the client server system some of the sites acts as client sites and the rest are
the server sites. Most of the data resides on the server sites and the applications are executed on
the client sites.

10
MIS604 REQUIREMENT ENGINEERING
3.1 Use case diagram
3.2 Specification for selected use cases
ID and Name User Management
Created By Student Name Date Created 31/07/2019
Primary Actor Admin Secondary Actors Customer and
Tradesperson
Description The admin manages the tradesperson and user
accounts
Trigger User needs to resister with the system with

11
MIS604 REQUIREMENT ENGINEERING
their personal details
Preconditions All the information about the user is needed
to be available
Normal Flow The Admin can add, modify or delete the
client records
Alternative Flows If the user is found as a defaulter the admin
can suspend the account
Exceptions The admin can do nothing if all the data is
valid
Priority Medium
Frequency of Use Used every day
Business Rules The user management is necessary for
keeping all the information validated and
eliminating the risk of unauthorized user
Other Information The user management helps in removal of the
inactive accounts from the system and
increase the response and usability.
Assumptions It is assumed that the users registered with the
system would be able to use the system
wisely.