Requirement Engineering Project: On-Demand Trades App Design

This project details the requirement engineering process for a mobile web application designed to connect customers with tradespersons for on-demand services. The project begins with an introduction outlining the purpose and scope, focusing on connecting tradesmen and customers to create revenue and business opportunities. The overall description covers product perspective, user classes, operating environment, and design constraints. The core of the project lies in the system features, including a use case diagram illustrating interactions such as login, browsing jobs, payment, and contact. Detailed specifications for selected use cases are provided in tabular format, followed by swim lane, state-transition, and dialog diagrams to visualize the job posting process and customer job requests. The project concludes with a bibliography of relevant references, providing a comprehensive analysis of the requirements and design elements for the proposed application. The project demonstrates a clear understanding of the requirements engineering process and its application in developing a mobile web app.

Running head: REQUIREMENT ENGINEERING
REQUIREMENT ENGINEERING
Name of the Student
Name of the University
Author Notes

1
REQUIREMENT ENGINEERING
1. Introduction
1.1 Purpose
The purpose of this project is to develop a mobile web application which will allow the
customers to create job posts on their account to get any job done. On the other hand,
tradesperson can select the jobs from the posts to do the job.
1.2 Document conventions
1.3 Project Scope
The main scope of the project is to connect tradesman and customers together by building a
greater revenue for the company. It will also ensure the business opportunities for the company
in this wide field.
2. Overall description
2.1 Product perspective
The product is a mobile based web application. The user can be able to log in to the system. A
customer user should be able to create job, contact tradesman and pay them after the job is
completed. Similarly the tradesperson user can search for the jobs, contact with the customer and
get paid for the job.

2
REQUIREMENT ENGINEERING
2.2 User classes and characteristics
The general users for this product will be the common peoples. Today, everyone have web
enabled mobile. The product can reach to the large number of common users. Anyone can use
the product who requires tradesman to get their job done.
2.3 Operating environment
The operating environment for the product is based on mobile user interface (MUI). The
platform or Integrated development environments (IDEs) can be used for proper functionalities.
2.4 Design and implementation constraints
1. The System shall be developed using the object oriented analysis and language.
2. The system shall be developed using open source tools.
2.5 Assumptions and dependencies
1. The system is available 24x7 for the users.
2. The system has the secure portal for payment.
3. The system is self-maintainable.
3. System features

3
REQUIREMENT ENGINEERING
3.1 Use case diagram
Figure 1: Use Case Diagram of Demand Trades & Handyman Services
Source: created by author

4
REQUIREMENT ENGINEERING
3.2 Specification for selected use cases
The Use case selected for the detailed descriptions are Login, browse job, pay and contact. The
fully developed descriptions are show below in tabular format.
Login
ID and Name Login
Created by Author
Date Created 19/4/2020
Primary Actor Customer and Tradesperson
Secondary Actors Null
Description It allows the customer and tradesperson to log into the system.
Trigger Need to use application
Preconditions Customer must exist.
Tradesperson must exist.
Post conditions Users should redirected to the main pages.
Normal Flow The user inputs login credentials.
System matches the credential with database.
System acknowledge with the result.
Alternative Flows Null
Exceptions Unregistered User
Priority High
Frequency of Use High
Business Rules Should allow to use system features.

5
REQUIREMENT ENGINEERING
Other information Null
Assumptions System is available 24x7
Contact
ID and Name Contact
Created by Author
Date Created 19/04/2020
Primary Actor Customer and Tradesperson
Secondary Actors None
Description Customer and tradesperson can contact to each other through an
instant messaging feature.
Trigger Customer finds tradesperson.
Tradesperson finds customer with job requirement.
Preconditions Customer must exist.
Tradesperson must exist.
Post conditions Customer and tradesperson should be directed to messaging section.
Normal Flow User finds the opposite party on browsing.
User clicks on contact.
Alternative Flows Null
Exceptions Null
Priority medium
Frequency of Use Medium
Business Rules System should allow the users to chat.

6
REQUIREMENT ENGINEERING
Other information Null
Assumptions Null
Browse Job
ID and Name Browse Job
Created by Author
Date Created 19/4/2020
Primary Actor Tradesperson
Secondary Actors None
Description Tradesperson can search the jobs in the system.
Trigger Tradesperson receive notifications of jobs.
Preconditions Tradesperson must exist.
Jobs must exist.
Post conditions Tradesperson should view all the available jobs.
Normal Flow Tradesperson input keywords.
System shows the results.
Alternative Flows Tradesperson can directly browse through all the available jobs.
Exceptions Null
Priority High
Frequency of Use High
Business Rules System should display available jobs to the tradesperson.
Other information null

7
REQUIREMENT ENGINEERING
Assumptions null

8
REQUIREMENT ENGINEERING
Pay
ID and Name Pay
Created by Author
Date Created 19/4/2020
Primary Actor Customer
Secondary Actors Tradesperson
Description Customers can pay the tradesperson after the job is done.
Trigger Job is completed.
Preconditions Customer must exists.
Tradesperson must exists.
Job must be competed.
Post conditions Invoice must receive by customer and tradesperson both.
Normal Flow Customer go to the job page.
Customer makes the payment for the job.
Alternative Flows Null
Exceptions Null
Priority High
Frequency of Use High
Business Rules System should allow the customer to pay the amount to the
tradesperson through a secure portal.
Other information null
Assumptions Customer have sufficient funds.

9
REQUIREMENT ENGINEERING
3.3 Swim lane diagram
Figure 2: Swimline Diagram of Job Posting Process
Source: Created by author

10
REQUIREMENT ENGINEERING
3.4 State-transition diagram
Figure 3: State-Transition Diagram of Customer Job Request
Source: Created by author

11
REQUIREMENT ENGINEERING
3.5 Dialog map
Figure 4: Dialog Map of Job Posting Process
Source: Created by author

12
REQUIREMENT ENGINEERING
Bibliography
Jeyaraj, A. N. A. N. D., & Sauter, V. L. (2014). Validation of business process models using
swimlane diagrams. J Inf Technol Manag, 25(4), 27.
Laplante, P. A. (2017). Requirements engineering for software and systems. CRC Press.
Rumpe, B. (2016). Modeling with UML. Language, Concepts, Methods. Springer
International, 4.
Trefi, S. (2017). Layout of use case diagram.