MIS604 Requirement Engineering

This report provides an overview of the software requirement specification for the development of an application that would provide handyman and on demand service to the customers. It includes the purpose, document conventions, project scope, overall description, system features, data requirement, and more.

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.

12
MIS604 REQUIREMENT ENGINEERING
3.3 Swimlane diagram

13
MIS604 REQUIREMENT ENGINEERING
3.4 State-transition diagram

14
MIS604 REQUIREMENT ENGINEERING
3.5 Dialog map

15
MIS604 REQUIREMENT ENGINEERING
4. Data requirement
4.1 Logical data model
4.2 Data dictionary
Customer
Sl. No. Name Type Description
1 Customer_ID Varchar2 Primary Key
2 Password Varchar2
3 F_Name Varchar2
4 L_Name Varchar2
5 Address Varchar2
6 ZIP Varchar2

16
MIS604 REQUIREMENT ENGINEERING
7 Email Varchar2
8 Phone_No Varchar2
Session Manager
Sl. No. Name Type Description
1 Session_ID Varchar2 Primary key
2 User_ID Varchar2 Foreign Key
3 Department_name Varchar2
Tradeperson
Sl. No. Name Type Description
1 Tradeperson_ID Varchar2 Primary key
2 Tradeperson_name Varchar2
3 Address Varchar2
4 Email Varchar2
5 PhoneNo Varchar2
6 Skill Varchar2
7 Specialization Varchar2
Administrator
Sl. No. Name Type Description
1 Admin_ID Varchar2 Primary Key
2 Admin name Varchar2

17
MIS604 REQUIREMENT ENGINEERING
3 Email Varchar2
Search Façade
Sl. No. Name Type Description
1 Façade_ID Varchar2 Primary Key
2 Get By specialization Varchar2
3 Get by Keyword Varchar2
Job
Sl. No. Name Type Description
1 Job_ID Varchar2 Primary Key
2 Date_created Varchar2
3 Deadline Varchar2
4 Customer_name Varchar2
5 Customer_ID Varchar2 Foreign key
6 Status Varchar2
7 Tradeperson_ID Varchar2 Foreign key
Engagement info
Sl. No. Name Type Description
1 Jobcard_ID Varchar2 Primary key
2 Job_Type Varchar2
3 Job_Cost Varchar2
4 Job_region Varchar2
Order Details

18
MIS604 REQUIREMENT ENGINEERING
Sl. No. Name Type Description
1 Order_ID Varchar2 Primary Key
2 Job_ID Varchar2 Foreign key
3 Job_Name Varchar2
4 Quantity Varchar2
5 unitCost Varchar2
6 SubTotal Varchar2
Job Set
Sl. No. Name Type Description
1 Set_ID Varchar2 Primary key
2 Job_ID Varchar2 Foreign Key
Recommendation
Sl. No. Name Type Description
1 Job_ID Varchar2 Foreign Key
5. External interface requirements
5.1 User interfaces
The characteristics of each of the interface between the application and the user is
described with the means of the user interface. The common GUI standards are needed to be
followed for the development of the interface design and it should have the presence of shortcuts,
display or error messages and use of standard buttons and images in each of the screens. The user
interface prepared for the application is needed to be compatible with different types of web

19
MIS604 REQUIREMENT ENGINEERING
browser and platform such as internet explorer, Mozilla Firefox, Netscape, Safari, etc. that can
be used for accessing the system (Haoues, Sellami & Ben-Abdallah, 2016). For the
implementation of the user interface different tool or software package can be used for example
MS front Page, EJB, Java Applet, etc.
5.2 Software interfaces
The on demand trades and handyman service application needs to communicate with the
configurator for identifying that all components needed for configuration of the application is
available. It also has the need to communicate with the content manager for getting the offerings,
promotions and specifications of the jobs posted by the customer. The application is needed to
communicate with the ebillPay system for identification of the payment methods available in the
system, validation of the payments and the payment processing. The application is needed to
communicate with the credit management system such that the different finance s supported by
the application (Band, 2019). The application is needed to communicate with the CRM system
such that the customers are provided support in case they face any issues with the service of the
tradesperson assigned to them. The application also needs to communicate with the sales system
for management of the jobs posted in the application. The application has the need to
communicate with the live tracking system for tracking the tradesperson assigned for the job and
find the estimated time the person would take to reach to him. The application is needed to
communicate with the external Tax system for the calculation of tax and service charges. SSL
connection from Verisign is needed to be used for allowing the use secured transactions and it
should be a third party software that is widely used over the internet.

20
MIS604 REQUIREMENT ENGINEERING
5.3 Hardware interfaces
The on demand trades and handyman service application runs over the internet and thus
the hardware that is needed for connecting with the internet acts as the hardware interface for the
system. The major interface of the system are the ADSL modem that acts as the link between the
user and the server (Nakagaki et al., 2016). The server can also be used as the hardware interface
since it is used for hosting the application and storing the database of the users registered with
the application.
6. Quality attributes
6.1 Usability
An usability testing is needed to be performed for measuring the interactive user
experience that is associated with the business system, mobile application and website. A focus
is needed to be given on the Human Factors Psychology and HCI fields. The usability is also
termed as the quality of the system which makes the system useful for the achievement of goals
and effectiveness and is easy to use. The usability of the system is tested by inviting a group of
users and provided with a series of task that is needed to be completed (Medeiros et al., 2016).
The facilitator gives assistance to the tester during the testing session and as each of the task is
completed the behavior of the user is documented inclusion of the confusion point, efficiency,
user performance and reactions. The test data is needed to be used for making the design changes
and improve the perfection in usability of the application.
6.2 Performance
The response time of the application should be minimum and the action is needed to be
completed within a certain time duration. The performance of the system should be able to meet

21
MIS604 REQUIREMENT ENGINEERING
the user expectation and no data should be lost while using the system. The error messages is
needed to be displayed to the user instantly such that the user is informed about the usability
(Husain & Beg, 2015). For increasing the performance of the information system virtualization is
needed to be used with load balancing such that data redundancy is improved and the
performance of the system is not affected with the increase in the number of users.
6.3 Security
The security refers to the mechanism that is used by the information system for keeping
the information residing in the system confidential and assure that integrity is maintained. Access
control is needed to be used for the prevention of the unauthorized access of the user and
protecting the information in the database. The security breached is needed to be identified and
the events are needed to be documented such that a security log is maintained (Unterkalmsteiner
& Gorschek, 2017). A planning is needed to be made for the management of business continuity
and eliminating the risk of any type of disaster such that the data can be recovered and allow the
business to continue its operation securely. A risk assessment and the vulnerability present in the
system is needed to be identified such that security precautions can be taken for handling the
risk.
7. Nontrivial and valid requirements
The on demand trades and handyman service application is needed to use HTTP protocol
for communicating with the use of internet and the intranet communication using the TCP/IP
protocol suite. It does not have the need of licensing and maintain a display with the use of
disclaimer, word mark, product warranties and trademark. The application is needed to be
developed based on the valid industry standard and allow multiple payment methods such that

22
MIS604 REQUIREMENT ENGINEERING
the user can select the method for completing the payment process (Zhang, Wan & Jin, 2016). A
confirmation email is needed to be sent to the customer on assigning a tradesperson for the
completion of the job and provide customer support. The system is needed to provide online
help, FAQ and sitemap options for supporting the customer. The type of support needed by the
customer is needed to be selected by the customer and the customer support contact information
is needed to be displayed at the bottom of the screen and it should also allow the customer to
enter their contact details such that the support person can directly reach the customer.

23
MIS604 REQUIREMENT ENGINEERING
8. References
Ali, K., & Xiaoling, X. (2019). A Reliable and an Efficient Web Testing System. International
Journal of Software Engineering & Applications (IJSEA), 10(1).
Band, J. (2019). Interfaces on trial: Intellectual property and interoperability in the global
software industry. Routledge.
Bhatia, M. P. S., Kumar, A., & Beniwal, R. (2018). Ontology Driven Software Development for
Automated Documentation. Webology, 15(2).
Brouwers, A. S., Kenbeek, M. M., Lifmann, A. R., de Vries, W. D., García, D. L., Traas, J. J., ...
& Zannone, N. (2018). Architectural Design Document.
Dakic, D., Stefanovic, D., Lolic, T., Sladojevic, S., & Anderla, A. (2018, March). Production
planning business process modelling using UML class diagram. In 2018 17th
International Symposium INFOTEH-JAHORINA (INFOTEH) (pp. 1-6). IEEE.
Deocadez, R., Harrison, R., & Rodriguez, D. (2017, September). Automatically classifying
requirements from app stores: A preliminary study. In 2017 IEEE 25th International
Requirements Engineering Conference Workshops (REW)(pp. 367-371). IEEE.
Haoues, M., Sellami, A., & Ben-Abdallah, H. (2016, November). Predicting the functional
change status in UML activity diagram from the use case diagram. In 2016 IEEE/ACS
13th International Conference of Computer Systems and Applications (AICCSA) (pp. 1-
8). IEEE.
Husain, S., & Beg, R. (2015). Advances in Ambiguity less NL SRS: A review. Proceedings of
ICETECH, 221-225.

24
MIS604 REQUIREMENT ENGINEERING
Kaur, A., & Kaur, K. (2018). Systematic Literature Review of Mobile Application Development
and Testing Effort Estimation. Journal of King Saud University-Computer and
Information Sciences.
Medeiros, J., Goulão, M., Vasconcelos, A., & Silva, C. (2016, September). Towards a model
about quality of software requirements specification in agile projects. In 2016 10th
International Conference on the Quality of Information and Communications Technology
(QUATIC) (pp. 236-241). IEEE.
Nakagaki, K., Dementyev, A., Follmer, S., Paradiso, J. A., & Ishii, H. (2016, October).
Chainform: A linear integrated modular hardware system for shape changing interfaces.
In Proceedings of the 29th Annual Symposium on User Interface Software and
Technology (pp. 87-96). ACM.
Unterkalmsteiner, M., & Gorschek, T. (2017, February). Requirements quality assurance in
industry: why, what and how?. In International Working Conference on Requirements
Engineering: Foundation for Software Quality (pp. 77-84). Springer, Cham.
Zhang, Y., Wan, C., & Jin, B. (2016, May). An empirical study on recovering requirement-to-
code links. In 2016 17th IEEE/ACIS International Conference on Software Engineering,
Artificial Intelligence, Networking and Parallel/Distributed Computing (SNPD) (pp. 121-
126). IEEE.