Mis604 Requirement Engineering

Running head: MIS604 REQUIREMENT ENGINEERING
MIS604 REQUIREMENT ENGINEERING
Name of student
Name of university
Author’s note:

1
MIS604 REQUIREMENT ENGINEERING
Table of Contents
1. Introduction..........................................................................................................3
1.1 Purpose.............................................................................................................3
1.2 Document conventions.....................................................................................3
1.3 Project Scope....................................................................................................3
2. Overall description...............................................................................................4
2.1 Product perspective..........................................................................................4
2.2 User classes and characteristics........................................................................5
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..............................................................................................8
3.2 Specification for selected use cases..................................................................8
3.3 Swimlane diagram..........................................................................................11
3.4 State-transition diagram..................................................................................12
3.5 Dialog map.....................................................................................................12
4. Data requirement................................................................................................13
4.1 Logical data model.........................................................................................13
4.2 Data dictionary...............................................................................................13
5. External interface requirements.........................................................................14
5.1 User interfaces................................................................................................14
5.2 Software interfaces.........................................................................................15
5.3 Hardware interfaces........................................................................................15
6. Quality attibutes.................................................................................................16
6.1 Usability.........................................................................................................16
6.2 Performance....................................................................................................16
6.3 Security...........................................................................................................16
7. Other requirements.............................................................................................16
8. References..........................................................................................................17

2
MIS604 REQUIREMENT ENGINEERING
1. Introduction
1.1 Purpose
The implementation of the innovative technologies is being done in the major
businesses for improving the methods by which the products as well as the services are
provided to the customers and the clients. This Software Requirement Specification
document has been developed for providing the complete overview of the “Your handyman”
app for the ABC Pty Ltd that would provide the customers and the tradesperson with the
effective platform for posting jobs and executing jobs respectively. This software requirement
specification document provides the clear description of the how the application would work
and the working of the application has been illustrated using the UML diagrams and the user
interfaces.
1.2 Document conventions
As development team is mainly responsible for this SRS document, no kind of
ambiguity arises from the usage. There is extensive distinction, moreover, among the
utilisation of the words “Customer” and the “Tradesperson”. The customer is interacting with
the application for posting any job requirements and browsing through the profile of any
registered tradesperson and then contact with the tradesperson using the instant messaging
facility in the application (Ali et al., 2018). The tradespersons are interacting with the
interface for registering themselves and then browsing through the various job available and
then make the contact with the customers using the in-app instant messenger. This document
would be printed on proper A4 paper in the Times New Roman font. The normal size of the
text used in this document would be 12 black, and the headings would be 13 size in the Times
New Roman font.

3
MIS604 REQUIREMENT ENGINEERING
1.3 Project Scope
The project of the “Your handyman” app would be initiated after proper planning has
been completed. Initially, the team would properly analyse the tasks and then deliver the
minimal needed project management documentation, the estimates as well as the list of
various risks as well as the milestone chart. The “Your handyman” app version 2.0 would be
rolled out after conducting the analysis of any bugs found in the initial version of this app.
For the Apple issues, the workaround would be probable for implementation with the
reasonable amount of the efforts as well as the risks. The main constraints of this project is
that there might a slight chance that the QA workload on various other products might affect
the schedule of the “Your handyman” app. The additional requests for the update to the
website of the ABC Pty Ltd might extensively influence the schedule of “Your handyman”
app.
2. Overall description
2.1 Product perspective
It is the web based system that would implement the client-server model where the
clients would be allowed to interact with the server of the organisation and gain important
data from the servers. The “Your handyman” app provides the simple mechanism for the
users and the tradesperson to interact with each other and provide various services along with
payments (Osman & Zaharin, 2018).
The following could be considered as the major features that would be included in the
“Your handyman” app:
 Cross platform assistance: Provides the required operating support for majority of
the known as well as the commercial operating systems

4
MIS604 REQUIREMENT ENGINEERING
 User account: The system permits the users with creating their respective accounts
in this system and then provides the main features of easily updating as well as
viewing the profiles of the tradespersons (Sabriye et al., 2017).
 Number of users supported at one time: Even though number of the users that are
using the system could not be determined precisely but it could be considered that
the system would possess the ability of supporting significantly large number of
the online users at one time.
 Search: The search is implemented for the users to find the tradesperson and the
search function would be directly linked with the tradesperson database. The
search function would return the list of neighbouring list of the tradesperson who
are available (Beck, 2017).
 Instant messaging: It would provide the users with the effective platform for
conducting discussion among the customers and the tradesperson and book the
tradesperson upon satisfaction.
 Booking system: Permits the users in submitting their request of any kind of job
that is available and wait for acceptance of the job by any of the skilled registered
tradesperson.
 FAQs section: The Frequently Asked Section in the application would contain all
the answer to the problems that are frequently posted on any handyman app.
2.2 User classes and characteristics
The users of the application would be the adults and the senior citizens of the both the
gender who would need any handyman for the jobs in their homes. It is considered that the
users would have the fundamental knowledge of properly using the application and would
gain the access to the application by registering themselves using the correct details (Park,
2019). The administrator of the application is predicted to the extensively familiar with

5
MIS604 REQUIREMENT ENGINEERING
proper working of the interface of tech support system. The administrator would possess the
ability of updating the database of the application and manage all the information of the
customers and tradespersons.
2.3 Operating environment
The “Your handyman” app that is being developed for ABC Pty Ltd. would be the
web based system and would need the operating environment for the client as well as the
server GUI. The application would be properly operating in the Android and the iOS
operating systems. The 128 bit SSL encryption environment would be enabled in the
application for allowing the secured transactions with the PCI-DSS compliance (Sanyal &
Ghoshal, 2018). The specifications that have been considered for the software, the technology
and the hardware are:
 Capability of providing services when connected over WiFi or any mobile
network
 Capability of allowing data access of any secured network
 Keypad and touchscreen are provided for using according to the convenience to
the users
 Processor providing over 500 MHz speed (Vaish & Sharma, 2018)
 Consistent supply of power
 Can use the microphone, the camera and the gallery
 Users can provide the input in the forms
2.4 Design and implementation constraints
Create the account in the application by entering the personal details such as the
name, address, phone, email along with the option of saving the payment card details
 In any situation where network is not accessible:

6
MIS604 REQUIREMENT ENGINEERING
o If the application is not able to exchange the data over network, the
application would provide the notification "Connection not available"
 In situation when the application is not able to access the services of the
mobile hardware:
o For example, the camera is not working for taking pictures, the
application would provide the notification “Cannot access camera”
 Lock account
o If the user has failed following the policies of the application
o In the situation where there is spamming by over 8 users
o Maintain the consecutive marked spam center
o Increment the spam centre (Sabriye & Zainon, 2018)
o Deactivate any account when the spam number has reached over 5
2.5 Assumptions and dependencies
 Power supply
 Data and the network availability
 Improved connection for efficiently exchanging the data over any network
 Availability of the mobile services (Hassan & Hassan, 2016)

7
MIS604 REQUIREMENT ENGINEERING
3. System features
3.1 Use case diagram
3.2 Specification for selected use cases
Use case name Post a job in the “Your handyman” app
ID 2
Primary actor Customer Secondary actor Tradesperson

8
MIS604 REQUIREMENT ENGINEERING
Description The customer makes an account in the application by registering the
application. Then the customer searches for the nearby handyman. The
customer then creates a job that is required urgently in their homes.
The various details such as the name of the job, address, phone, email
and the payment details of provided in the application. After the
system verifies all the information then the customer is asked with the
option of making the payment for the job before the completion of the
job or pay for the job after the job has been completed.
Trigger Customer selects the option “Post job”
Precondition Customers should be registered in the system of the organisation
Post condition The job has been successfully posted in the system
Normal flow 1. Customer clicks on register
button
2. Customer enters all the details
in the registration form and
then click on proceed
3. Customer provides the
specification of any job that is
available
4. Customer gains the
notification of confirmation of
job creation
1. System provides the
registration form
2. Information is verified by the
system and customer is
registered
3. System checks the availability
of job and then approves the
creation of the job
Alternative flow 1. Customers already registered
in the system
2. Customer enters their login
1. System provides the login
form
2. Login credentials is verified

9
MIS604 REQUIREMENT ENGINEERING
credentials
3. Customer provides the
specification of any job that is
available
4. Customer gains the
notification of confirmation of
job creation
by the system and customer is
allowed access
3. System checks the availability
of job and then approves the
creation of the job
Exceptions Job is not available
Priority High
Frequency of use High
Business rules Customers should provide the valid address of the jobs that are created
Other
information
Customers should provide the accurate phone numbers and alternative
numbers for contacting by the tradesperson
Assumptions Customer forgot username

10
MIS604 REQUIREMENT ENGINEERING
3.3 Swimlane diagram

11
MIS604 REQUIREMENT ENGINEERING
3.4 State-transition diagram
3.5 Dialog map

12
MIS604 REQUIREMENT ENGINEERING
4. Data requirement
4.1 Logical data model
4.2 Data dictionary
Attribute name Format Type Size Description
Customer name String Varchar 40 First name is
“Mandatory”
Customer ID 00-00 Number 10 Made primary
key and it
would not
contain
duplicate values
job ID Number 20 Mandatory

13
MIS604 REQUIREMENT ENGINEERING
Customer
address
Building
number,
locality, street
name, Zip code
State,
Character 70 Customer
address has
been made
mandatory
Customer phone
number
State code-
phone Number
Number 10 Optional phone
number
Customer lname String Character 50 Last name has
been made
“Mandatory”
Mobile number 00-0000-000 Number 10 Mandatory
5. External interface requirements
5.1 User interfaces
The standards that are to be followed are:
 Visibility of the system status
 Match among the system as well as the real world
 User control and significant freedom (Zainuddin et al., 2018)
 Consistency as well as the standards
The screen size should be made with accordance to the standard devices of Android
and iOS. The homepage and the payment page would include the shortcut for
travelling between the app quickly. The error messages would be displayed instantly
whenever any user has entered the wrong details. Vb.net version has been used as the
front-end software and the SQL+ has been used as the back-end software (Susilowati,

14
MIS604 REQUIREMENT ENGINEERING
Ahsan & Kurniawan, 2019). The data validation guidelines that would be followed
are:
 The name field in the registration form should not contain any number
 The complete email address has to be provided in the email address
 The created password would only be authenticated when the password
strength has been determined to be strong (Kong, 2016)
 Job description should include a brief description of the job that is required.
5.2 Software interfaces
Software used Description
Operating system Windows operating system has been chosen
Database For saving the customer, tradesperson the
SQL+ database has been chosen
VB.Net Vb.Net is used as the interactive support in
implementing this project
5.3 Hardware interfaces
Hardware should have the following specifications:
 Ability of reading the gallery
 Ability of exchanging the data over network
 Touch screen for convenience
 Constant power supply

15
MIS604 REQUIREMENT ENGINEERING
6. Quality attibutes
6.1 Usability
The customer should be allowed to create their account by entering the personal
details in the registration form. The job would be accepted by the system when the
description has been provided by the customers. The tradesperson should be provided with
the list of the nearby jobs that are scheduled in a day when the tradesperson enters their login
credentials.
6.2 Performance
The system should be available at all times for accepting the job booking of the
customers. It should be available for the tradesperson 24X7 for checking the upcoming jobs
that are required to be completed.
6.3 Security
Encryption is used in the payment interface for ensuring the encrypted transactions of
the customers. The database that is to be chosen for storing all the data should contain all the
security protocols for ensuring that no unauthorised access is gained in the database by any of
the unauthorised users.
7. Other requirements
If there is any kind of significant damage to the vast portion of the database because
of any catastrophic failure, the past copy of all the data would be recovered using the
recovery methods.

16
MIS604 REQUIREMENT ENGINEERING
8. References
Ali, I., Asif, M., Shahbaz, M., Khalid, A., Rehman, M., & Guergachi, A. (2018). Text
categorization approach for secure design pattern selection using software
requirement specification. IEEE Access, 6, 73928-73939.
Beck, R. J. (2017). The Software Requirement Specification as a Tool for Software
Quality. Software Quality Professional, 19(3), 47.
Park, S. (2019). Software Requirement Specification Based on a Gray Box for Embedded
Systems: A Case Study of a Mobile Phone Camera Sensor
Controller. Computers, 8(1), 20.
SABRIYE, A. O. J. A., & ZAINON, W. M. N. W. (2018). AN APPROACH FOR
DETECTING SYNTAX AND SYNTACTIC AMBIGUITY IN SOFTWARE
REQUIREMENT SPECIFICATION. journal of theoretical & applied information
technology, 96(8).
Zainuddin, F. B., Arshah, R. B. A., Mohamad, R. B., Mokhtar, R. B., Hamid, R. B. A., &
Ahmad, N. A. B. (2018). Reviewing the Challenge and Practices of Human Factor
Involvement in Requirement Specification Validation. Advanced Science
Letters, 24(10), 7322-7327.
Kong, M. Y. (2016). Software Requirement Specification Tool (Doctoral dissertation,
UTAR).
Hassan, T., & Hassan, S. (2016, September). Notice of Removal Design Semantic
Framework for Software Requirement Specification. In 2016 6th International
Conference on IT Convergence and Security (ICITCS) (pp. 1-5). IEEE.

17
MIS604 REQUIREMENT ENGINEERING
Sabriye, A. O. J. A., & Zainon, W. M. N. W. (2017, May). A framework for detecting
ambiguity in software requirement specification. In 2017 8th International
Conference on Information Technology (ICIT) (pp. 209-213). IEEE.
Osman, M. H., & Zaharin, M. F. (2018, June). Ambiguous software requirement specification
detection: an automated approach. In 2018 IEEE/ACM 5th International Workshop on
Requirements Engineering and Testing (RET) (pp. 33-40). IEEE.
Sanyal, R., & Ghoshal, B. (2018, June). Automatic Extraction of Structural Model from Semi
Structured Software Requirement Specification. In 2018 IEEE/ACIS 17th
International Conference on Computer and Information Science (ICIS) (pp. 543-58).
IEEE.
Vaish, N., & Sharma, A. (2018, November). Semi-Automated System Based Defect
Detection in Software Requirements Specification document. In 2018 5th IEEE Uttar
Pradesh Section International Conference on Electrical, Electronics and Computer
Engineering (UPCON) (pp. 1-5). IEEE.
Susilowati, M., Ahsan, M., & Kurniawan, Y. (2019, December). What does the software
requirement specification for local E-Government of citizen database information
system? An analysis using ISO/IEC/IEEE 29148–2011. In Journal of Physics:
Conference Series (Vol. 1402, No. 2, p. 022087). IOP Publishing.