MIS604 Requirement Engineering: PersonalRepairman Application Report

This report presents a Software Requirements Specification (SRS) for the "PersonalRepairman" application, developed for ABC Pty Ltd. The report outlines the application's purpose, which is to connect customers and tradespersons for repair jobs. It details the product perspective, user classes, operating environment (iOS, Android, and web browsers), and design constraints. The SRS includes a use case diagram and specifications for selected use cases, a swimlane diagram, a state transition diagram, and a dialog map to visualize system features. Data requirements are addressed through a logical data model and data dictionary. External interface requirements, including user, software, and hardware interfaces, are also specified. Furthermore, the report covers quality attributes such as usability, performance, and security. The document includes an introduction, overall description, system features, data requirements, external interface requirements, quality attributes, other requirements, and references, providing a comprehensive overview of the application's requirements and design considerations.

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
Purpose.......................................................................................................................3
Document conventions...............................................................................................3
Project scope..............................................................................................................4
2) Overall description...............................................................................................4
Product perspective....................................................................................................4
User classes and characteristics.................................................................................4
Operating environment...............................................................................................5
Design and implementation constraints.....................................................................5
Assumption and dependencies...................................................................................5
3) System features....................................................................................................6
Use case diagram........................................................................................................6
Specification for the selected use cases.....................................................................6
Swimlane diagram....................................................................................................18
State transition diagram............................................................................................19
Dialog map...............................................................................................................19
4) Data requirements..............................................................................................20
Logical data model...................................................................................................20
Data dictionary.........................................................................................................20
5) External interface requirements.........................................................................21
User interface...........................................................................................................21
Software interface....................................................................................................26
Hardware interface...................................................................................................27
6) Quality attributes................................................................................................27
Usability...................................................................................................................27
Performance.............................................................................................................27
Security....................................................................................................................27
7) Other requirements.............................................................................................28
8) References..........................................................................................................28

2
MIS604 REQUIREMENT ENGINEERING
1) Introduction
This report aims to provide the brief description of the application
“PersonalRepairman” for the ABC Pty Ltd. that would be efficiently used by the customers
and the tradespersons for various kinds of repairing jobs and do business. This application
would possess the appropriate platform and the functionality that would help with the
integration of all the tradespersons along with the customers on single platform and
interaction would be extensively simplified.
Purpose
The basic intention of this SRS document is providing the ABC Pty Ltd. with the
detailed specification of the application that is being developed in the company. The team
that has been hired for developing this application would be provided with the SRS document
that would clearly specify the major features and the characteristics of the application. After
the analysis of all the features and the characteristics of the application, the development of
the application would be initiated. This analysis would help with the ensuring that all the
major requirements of the business and the customers are considered appropriately to ensure
that none of the requirements have been overlooked.
Document conventions
The document has been highlighted in some of the sections that illustrates the
development team the sectors that are required to be placed under the additional analysis as
these sections are the major requirements of the customers and the business. The standards
that are required to be followed during the stage of the development of the application has
been clearly mentioned in this document. These standards are required to be followed
appropriately by the development team so that the proper compliance is ensured with the
government rules and the regulations.

3
MIS604 REQUIREMENT ENGINEERING
Project scope
The “PersonalRepairman” that is being developed by the development team for the
ABC Pty Ltd. would include the scope of allowing the customers with the placing of various
kinds available jobs, the tradespersons viewing the list of the jobs and then completing the
jobs, the manager with generating the financial report for analysis of the performance of the
organisation and the system administrator with the functionality of the updating the database
of the organisation and generating various kinds of reports that are required for the
management of the organisation. The customers and the tradespersons would not be allowed
to access any of the internal features of the application and the system admin plus the
manager would be allowed to make any changes in the application with proper authorisation.
2) Overall description
Product perspective
The creation of the application would be done as a open source application that could
be downloaded any of the users by simplifying the app store in iOS or even Play Store in
Android. “PersonalRepairman” would include the significantly high ability of
accommodating the number of the users who need the access to the respective portal for
using several functionalities of the application (Kaufmann, 2016).
User classes and characteristics
The users who would be primarily using this application would be considered to be in
the range of over 18 to 50 years of both the gender who would be needing various kinds of
the repair job in their home (Souza & Stadzisz, 2016). Sometimes the users could be the
senior citizens who would be needing various kinds of repair jobs in their home and they
could use this application for calling the tradespersons in their home for executing any
particular kind of the repair job (Peixoto et al., 2019). The primary requirement from the

4
MIS604 REQUIREMENT ENGINEERING
users who would be using this application is that they should have the proper understanding
and the knowledge of how to work in any mobile application (Susilowati & Kusuma, 2019).
Operating environment
The operating environment where this application would be performing efficiently are
the iOS and the Android platform (Ramdhani et al., 2018). The designing of the application
would be done according to the working of both the platforms so that the users of both these
kinds of devices could easily download the application and then avail the benefits of the
various functionalities that are provided by the application (Ito, 2016). The application would
also be available on the browsers such as the Google Chrome, Firefox and Safari for the PC
users who would be able to browse to the website of the company and then login using their
respective credentials (Feno et al., 2018).
Design and implementation constraints
The designing of the application must be conducted in the proper manner that the
users of all the classes are easily able to view the information and understand what the
application is displaying (Zainuddin et al., 2017). The main constraint that could be faced
while the designing of this application is that when the senior citizens are using this
applications, they might need the magnifier for improving the visibility of the application and
it could not be provided in the application as it is not supported in the mobile devices where
the application would be downloaded (Audytra, Hendradjaya & Sunindyo, 2016).
Assumption and dependencies
The main dependency of the application is on the customer who would be using this
application for posting various kinds of jobs that are required by them (da Silva, Paiva & da
Silva, 2018). And the tradespersons viewing the details of the jobs and then visiting the
appropriate customers for their repair job.

5
MIS604 REQUIREMENT ENGINEERING
3) System features
Use case diagram
Specification for the selected use cases
Use case name Generate weekly report
ID 5
Primary actor Manager Secondary actor System admin
Description The manager logs in into the system using the credentials that have
been created during the registration stage. The manager is provided
with the login confirmation and the homepage of the application has

6
MIS604 REQUIREMENT ENGINEERING
been provided. The manager could view the details of the customers,
the details of the tradespersons and also the financial status of the
company. The data of the performance of the company are provided to
the manager on a weekly basis and it would be allowed to generate in
the report. The manager views the data and then selects the option of
generate report and prints the report for analysing the data.
Trigger The manager logs in into the system and then chooses the option
“Generate report”
Precondition The manager has to be successfully logged in into the system
Post condition The manager will be displayed with the data of the performance of the
company that would be used for generating the report.
Normal flow 1. The manager inputs the login
information in login form
displayed by the system after
visiting the website.
2. When these login credentials
are entered by the manager in
the “PersonalRepairman”
system, the login credentials
are verified by the system and
then access is offered to the
manager
3. When access has been granted
to the manager, the manager
selects the option of viewing
1. The credentials that are
provided as the input in the
system are effectively verified
by the system
2. The browser displays the
homepage of the manager
portal to the manager
3. The system then displays the
various filters that could be
used for selecting the range of
the data that are required to be
viewed.
4. The system provides the list
of all the data of the company

7
MIS604 REQUIREMENT ENGINEERING
data of the company.
4. Upon verification of the data
of the company the manager
selects the option of printing
report of the data
and prints report of the data if
the manager has requested the
printout of the data.
Alternative flow 1. The manager has lost their
login credentials and the
password that has been
entered in the system is not
valid.
2. The manager is provided with
the option of generating OTP
in the entered number during
the time of registration.
3. The password has been reset
by the manager and the login
form has been provided again.
4. The manager inputs the login
information in login form
displayed by the system after
visiting the website.
5. When these login credentials
are entered by the manager in
the “PersonalRepairman”
system, the login credentials
1. The system verifies the
provided login credentials to
be invalid.
2. The system provides the
screen of entering the
recovery password mode to
the manager.
3. System allows the manager to
create their new password and
then saves the new password
in the system.
4. The credentials that are
provided as the input in the
system are effectively verified
by the system
5. The browser displays the
homepage of the manager
portal to the manager
6. The system then displays the
various filters that could be

8
MIS604 REQUIREMENT ENGINEERING
are verified by the system and
then access is offered to the
manager
6. When access has been granted
to the manager, the manager
selects the option of viewing
data of the company.
7. Upon verification of the data
of the company the manager
selects the option of printing
report of the data
used for selecting the range of
the data that are required to be
viewed.
7. The system provides the list
of all the data of the company
and prints report of the data if
the manager has requested the
printout of the data.
Exceptions Manager would not be provided with the details of the customer and
the tradesperson if the manager has selected the option of generating
the financial information.
Priority High
Frequency of use High
Business rules Manager should be successfully registered in company system
Other
information
Manager should logout after the data has been viewed and report has
been generated
Assumptions Data has not been updated.
Use case name Provide the job description
ID 8

9
MIS604 REQUIREMENT ENGINEERING
Primary actor Customer Secondary actor System admin
Description The customer has logged in into the system using the provided login
credentials by the system. When the login has been completed
successfully by the customers, the system would display the homepage
of the customer portal to the customer. On the left side of the screen,
various options would be provided to the customers that would be
used for interacting with the system. The customer has selected the
option of post job. Then the customer is provided with the job screen
where the job type, and the description of the job is required to be
posted. The customers post the brief description of the kind of the job
that is required by the customer.
Trigger The customer selects the option of provide description of the posted
job.
Precondition The customer must have posted the name of the job that is required to
be completed.
Post condition The description of the job has been provided for the job in detailed
manner.
Normal flow 1. The customer inputs the login
information in login form
displayed by the system after
visiting the website.
2. When these login credentials
are entered by the customer in
the “PersonalRepairman”
system, the login credentials
1. The credentials that are
provided as the input in the
system by the customer are
effectively verified by the
system
2. The browser displays the
homepage of the customer

10
MIS604 REQUIREMENT ENGINEERING
are verified by the system and
then access is offered to the
customer
3. The customer selects the
option of posting the job that
is required by them.
4. When the name of the job has
been posted by the customer,
the system provides the form
of posting the brief
description of the job that is
required
5. When the description has
been provided on the form,
the customer selects the
option of post the job on the
portal.
portal to the customer
3. The system provides the post
job screen to the customer
4. The system confirms the
selection of the job that has
been selected by the customer
5. System accepts the job
description provided by the
customer and then posts the
job on the customer portal and
the tradesperson portal.
Alternative flow 1) The customer has lost their
login credentials and the
password that has been
entered in the system is not
valid.
2) The customer is provided with
the option of generating OTP
in the entered number during
1) The system verifies the
provided login credentials to
be invalid.
2) The system provides the
screen of entering the
recovery password mode to
the customer.
3) System allows the customer to

11
MIS604 REQUIREMENT ENGINEERING
the time of registration.
3) The password has been reset
by the customer and the login
form has been provided again.
4) The customer inputs the login
information in login form
displayed by the system after
visiting the website.
5) When these login credentials
are entered by the customer in
the “PersonalRepairman”
system, the login credentials
are verified by the system and
then access is offered to the
customer
6) The customer selects the
option of posting the job that
is required by them.
7) When the name of the job has
been posted by the customer,
the system provides the form
of posting the brief
description of the job that is
required
8) When the description has
create their new password and
then saves the new password
in the system.
4) The credentials that are
provided as the input in the
system by the customer are
effectively verified by the
system
5) The browser displays the
homepage of the customer
portal to the customer
6) The system provides the post
job screen to the customer
7) The system confirms the
selection of the job that has
been selected by the customer
8) System accepts the job
description provided by the
customer and then posts the
job on the customer portal and
the tradesperson portal.

12
MIS604 REQUIREMENT ENGINEERING
been provided on the form,
the customer selects the
option of post the job on the
portal.
Exceptions The job description could not be entered in the system without
selecting the type of the job that is required.
Priority High
Frequency of use High
Business rules Customer should be successfully registered in company system
Other
information
Customer should logout after posting the job in the portal
Assumptions Data has not been updated.
Use case name View list of tradesperson with pending payment
ID 7
Primary actor System admin Secondary actor Tradesperson
Description The system admin of the company logs in into the system with the
help of the credentials that are provided to the admin by the company.
When the system admin has successfully logged in into the system, the
admin portal is provided to the admin. The admin selects the option of
viewing the option of the list of the tradespersons who are registered
in the system. The admin then selects option of viewing the payment

13
MIS604 REQUIREMENT ENGINEERING
history of the tradesperson and the system provides all the details of
the payment history of the tradesperson. The admin sorts the list of the
payment of the tradesperson by pending payment and the system
provides the list of the tradespersons whose payment for the jobs are
still pending.
Trigger The system admin selects the option of sort the tradesperson according
to pending payment.
Precondition The system admin should sort the list correctly in ascending order of
the payment
Post condition The list of the pending payment of the tradesperson is provided to the
system admin and the system generates the report of the pending
payments.
Normal flow 1) The system admin inputs the
login information in login
form displayed by the system
after visiting the website.
2) When these login credentials
are entered by the system
admin in the
“PersonalRepairman” system,
the login credentials are
verified by the system and
then access is offered to the
system admin
3) The admin selects the option
1) The credentials that are
provided as the input in the
system by the system admin
are effectively verified by the
system
2) The browser displays the
homepage of the admin portal
to the system admin
3) The system confirms the
selection of the tradesperson
list by the admin
4) The system sorts the list of the
tradesperson based on the

14
MIS604 REQUIREMENT ENGINEERING
of viewing the list of the
registered tradesperson in the
company
4) The admin then selects the
option of sort tradesperson
according to the pending
payments.
5) The list of the tradespersons
whose payment for their jobs
are pending are printed in the
report format for the
management.
option of pending payments.
5) The complete list is provided
to the system admin in the
form of the report.
Alternative flow 1. The system admin has lost
their login credentials and the
password that has been
entered in the system is not
valid.
2. The system admin is provided
with the option of generating
OTP in the entered number
during the time of registration.
3. The password has been reset
by the system admin and the
login form has been provided
again.
1. The system verifies the
provided login credentials to
be invalid.
2. The system provides the
screen of entering the
recovery password mode to
the system admin.
3. System allows the customer to
create their new password and
then saves the new password
in the system.
4. The credentials that are
provided as the input in the

15
MIS604 REQUIREMENT ENGINEERING
4. The system admin inputs the
login information in login
form displayed by the system
after visiting the website.
5. When these login credentials
are entered by the system
admin in the
“PersonalRepairman” system,
the login credentials are
verified by the system and
then access is offered to the
system admin
6. The admin selects the option
of viewing the list of the
registered tradesperson in the
company
7. The admin then selects the
option of sort tradesperson
according to the pending
payments.
8. The list of the tradespersons
whose payment for their jobs
are pending are printed in the
report format for the
management.
system by the system admin
are effectively verified by the
system
5. The browser displays the
homepage of the admin portal
to the system admin
6. The system confirms the
selection of the tradesperson
list by the admin
7. The system sorts the list of the
tradesperson based on the
option of pending payments.
8. The complete list is provided
to the system admin in the
form of the report.

16
MIS604 REQUIREMENT ENGINEERING
Exceptions List would only be provided in the pdf format
Priority High
Frequency of use Medium
Business rules System admin is required to be registered in system of the company
Other
information
The list should be properly sorted by the tradesperson for
appropriately displaying the list of the tradespersons
Assumptions No pending payments so list is empty

17
MIS604 REQUIREMENT ENGINEERING
Swimlane diagram

18
MIS604 REQUIREMENT ENGINEERING
State transition diagram
Dialog map

19
MIS604 REQUIREMENT ENGINEERING
4) Data requirements
Logical data model
Data dictionary
Attribute name Type Size Description Format
Manager_firstname Varchar 20 Mandatory input String
manager _lastname Varchar 20 Mandatory input String
Manager _ID Number 20 Assigned as the 000

20
MIS604 REQUIREMENT ENGINEERING
primary key for
this table and no
duplicate data is
allowed
Tradesperson_ID Int 10 Assigned as the
foreign key of the
table
000
manager mobile
number
Number 10 Mandatory made
manager mobile
number
00-0000-0000
Manager address Varchar 50 Mandatory input Building number,
locality, street,
area code
5) External interface requirements
User interface
The standards of the User interaction and the User interface design has been followed
for ensuring that the interface of this application has the ability of providing the various users
with the required types of tasks and ensure that all the data is being accurately accepted by
the application (del Sagrado & del Aguila, 2018).

21
MIS604 REQUIREMENT ENGINEERING

22
MIS604 REQUIREMENT ENGINEERING

23
MIS604 REQUIREMENT ENGINEERING

24
MIS604 REQUIREMENT ENGINEERING

25
MIS604 REQUIREMENT ENGINEERING
Software interface
 iOS operating system
 Android operating system
 Browser of chrome, firefox and the Safari

26
MIS604 REQUIREMENT ENGINEERING
Hardware interface
 Android devices
 iOS devices
 PC
 laptop
6) Quality attributes
Usability
The application would be design for working appropriately in the various devices that
are compatible with the latest technology (Sanyal & Ghoshal, 2018). With the accessing of
the application once by the users, the users would gain the proper knowledge of working with
the application without the issue of needing to read the instructions again (SABRIYE &
ZAINON, 2018). All the information would be provided on the homepage of the application
and it would provide the clear display of all the errors that are made by the users while
accessing the application (Susilowati, Ahsan & Kurniawan, 2019).
Performance
This application “PersonalRepairman” would be designed for being available to any
of the manager, the system admin, the customers and the tradesperson at all times and the
users could easily login into the system using the provider credentials and the use the
application and its various functionalities easily (Beck, 2017). It would provide the users with
the ability of executing various tasks but the payment module would be available for the
customers during the range of 12:00 A.M. to 8 P.M (Park, 2019).
Security
The application would include the high level of the security that would ensure that all
the data of the organisation is maintained with the proper application of the security protocols

27
MIS604 REQUIREMENT ENGINEERING
that are essential for ensuring that none of the data is being misused by any of the
unauthorised users (Sabriye & Zainon, 2017).
7) Other requirements
The application should be designed for displaying the extensive reliability to the users
(Ali, Ahmed & Shafi, 2018). When any of the data is been provided in the application it
would ensure that the data is accepted in the first attempt without having the users to provide
the data again and the search results should display the appropriate results of the search and
no data should be provided as duplicate unless it is required (Osman & Zaharin, 2018).
8) References
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).
del Sagrado, J., & del Aguila, I. M. (2018). Stability prediction of the software requirements
specification. Software Quality Journal, 26(2), 585-605.
da Silva, A. R., Paiva, A. C., & da Silva, V. E. R. (2018). Towards a Test Specification
Language for Information Systems: Focus on Data Entity and State Machine Tests.
In MODELSWARD (pp. 213-224).

28
MIS604 REQUIREMENT ENGINEERING
Zainuddin, F. B., Arshah, R. B. A., Mohamad, R. B., & Mokhtar, R. B. (2017). Human factor
of formal engineering methods in validating requirement specification. Advanced
Science Letters, 23(6), 5481-5486.
Feno, M. R., Martin, P., Daille-Lefevre, B., Etienne, A., Marsot, J., & Siadat, A. (2018).
Safety of machinery: requirement specification based on functional need and work
situations analysis. International Journal on Interactive Design and Manufacturing
(IJIDeM), 12(3), 943-953.
Ramdhani, M. A., Maylawati, D. S. A., Amin, A. S., & Aulawi, H. (2018). Requirements
elicitation in software engineering. International Journal of Engineering &
Technology (UEA), 7(2.19), 772-775.
Susilowati, M., & Kusuma, A. A. (2019). Software Requierement Specification Sistem
Informasi Manajemen. SMARTICS Journal, 5(1), 27-33.
Souza, R. G. M., & Stadzisz, P. C. (2016). Problem-Based Software Requirements
Specification. Revista Electronica de Sistemas de Informaçao, 15(2), 1.
Peixoto, M., Silva, C., Lima, R., Araújo, J., Gorschek, T., & Silva, J. (2019, September).
PCM Tool: Privacy Requirements Specification in Agile Software Development.
In Anais Estendidos da X Conferência Brasileira de Software: Teoria e Prática (pp.
108-113). SBC.
Kaufmann, A. (2016). Validating Requirements Specification Using Surveys (Doctoral
dissertation, Friedrich-Alexander University Erlangen-Nürnberg).
Ito, M. (2016, September). Cardion. spec: an approach to improve the requirements
specification written in the natural language through the formal method. In European
Conference on Software Process Improvement (pp. 58-69). Springer, Cham.

29
MIS604 REQUIREMENT ENGINEERING
Audytra, H., Hendradjaya, B., & Sunindyo, W. D. (2016, October). A proposal for quality
assessment model for software requirements specification in Indonesian language for
e-Government. In 2016 International Conference on Data and Software Engineering
(ICoDSE) (pp. 1-6). IEEE.
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.
Ali, S. W., Ahmed, Q. A., & Shafi, I. (2018, February). Process to enhance the quality of
software requirement specification document. In 2018 International Conference on
Engineering and Emerging Technologies (ICEET) (pp. 1-7). 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.
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.