It is the presentation on HandyMan for SRS.In slide we discover how to collect requirements from stakeholder,requirements,use case diagram,use case description(some),Activity diagram(only one),and RTM

1. One Platform, All Services

2. SRS Project
Final Presentation
Team Member
Abdullah An-Noor (ASH1825001M)
Fazle Rabbi (ASH1825004M)
Mahfujur Rahman (ASH1825024M)
Foyzul Karim Pathan (ASH1825033M)
Project Supervisor
Md Iftekhar Alam Efat
Lecturer,
IIT, NSTU
2

3. HandyMan! What is it?
 Your Helping Hand in your premises.
Instantly Get Access to anything, anywhere, anytime!
A modern digital platform where every services you need are in your hand
Just click and get everything you need
11/7/2019 3

4. Why HandyMan?
Scope?

5. Interview
Questionnaire
Requirement Elicitation
Requirements Elicitation is the practice of researching and discovering
the requirements of a system from users, customers, and other stakeholders
Mainly we’ve used following techniques for collecting the requirements:

6. Service Taker
Service Provider
Stakeholders
Who will take the service from Service Provider by our system
Who will provide the service directly to service taker

7. Work request
 User Interface
Payment system
Short description about
our project Goals and
Objectives
Registration process
•
•
•
•
•
•
•
•
Interview
 Security

8. What problems might they face
doing works gotten from online?
How it’ll be if they get work
from customers in online?
Do they provide home
service?
How many work they get in a
single day in average?
What kinds of services do
they provide?
With the
Service
Providers How much the work charges
would be/should be?
What should we do more to
make this more convenient for
them?
Questionnaire

9. How it’ll be if they can order for service in online?
Which payment system will be more convenient
for them mobile banking or direct?
When you want to search for a service, then what
type of information is important to know about
that service provider do you think?
What other features or facility do you
think should be added to this system?
Questionnaire
With the service takers

10. Notification
Popup
Boosting
System
Direct
Contact
Conflicting Requirements

11. Increasing Business
with least cost
New movement in
digitalization
Everything is at
doorstep
Positivity from Stakeholders

12. New System concept in the area
Tools problem for home servicing
Lack of Internet, Handset and proper
knowledge
Reluctance in home servicing from online
order
Negativity from Stakeholders

13. Experience of
Elicitation Process
Collecting requirements via fieldwork
Meeting many people with many minds
Technology freak and lacks

14. Functional Requirements
 R1. Service taker sets the Location
 R2. Service taker Searches for Service
 R3. Service taker chooses desired services
 R4. Service taker sees service provider list & profile
 R5. Service taker sends “Work Request” to service provider
 R6. Service taker cancels “Work Request”
 R7. Service taker gives rating to service provider
 R8. Service taker updates own profile
 R9. Service provider Accepts “Work Request”
 R10. Service provider cancels “Work Request”
 R11. Service provider updates own profile
 R12. Service provider changes Active Status
 R14. Data retrieve from cloud server
 R15. Service taker pays money

15.  The system shall input, process and output data types of integers,
strings, characters and real due to the variation of information
that will be stored
 The system shall have accurate and up-to date information
 The system shall handle information from various sources
Data Requirements

16.  Search must be faster
 Search Result must be Accurate
 The system Must be handled 100 thousands of data
Performances
Requirements
 The system must be Available on 24X7
 The system handles all user access without system errors
 System helps to update user profile
Dependability
Requirements

17.  Application must be useable for our user
Usability and Human-Interaction
Requirements
 Labels of mandatory fields must be bold
 Application must fill the full mobile Screen
 The appearance must be controllable using stylesheet file
Look and Feel
Requirements

18.  Service provider & service taker must sign up
 Email and NID card number Verification for Service provider
 Get access only verified and logged user(Service provider &
Service taker)
 Get & change information only logged user(Service provider &
Service taker)
 Password encrypted to hashed(MD5) password and store in
database and it is one way function
 Service provider /Service taker can log out from the system
Security Requirements

19. Requirements
Analyzing

20. Use Case Diagram

21. Use case Search Service
Goal Service taker can search any type service search and requested for service
Preconditions
Success End Condition Showing searching services
Failed End Condition
Primary Actors:
Secondary Actors:
Service taker
Trigger Typing in search option
Main Success Flows
Step Action
1 Typing in search option
2.1
2.2
Service taker clicks enter
Service taker clicks ‘search’ button
Alternative Flows
Quality Requirements
Use Case Description

22. Use case Send ‘work request’
Goal Service taker requested for work to service provider
Preconditions
Success End Condition Service provider receive a ‘work request’
Failed End Condition Service provider don’t receive a ‘work request’
Primary Actors:
Secondary Actors:
Service taker, Service provider
Trigger Select a “available Category” service
Main Success Flows
Step Action
1 Select a “available Category” service
2 Choose a service
3 Select a “service’
4 Clicks ‘next’
5 Choose a ‘service” provider
6 Sends a “work request” to service provider
7 Service provider receive a “work request
Alternative Flows
Step Branching Action
2a Choose multiple service
Quality Requirements
Step Requirements
6 The “work request” pop up message will stay no longer than 90 seconds after it is sent by the Service taker

23. Use case Pay Money
Goal For service, service taker billed for his order work
Preconditions Service provider Accept “work request”
Success End Condition Service taker paying the money
Failed End Condition Service taker not paying the money
Primary Actors:
Secondary Actors:
Service taker, Service provider
Bkash or DBBL org.
Trigger Select a “available Category” service
Main Success Flows
Step Action
1 Select a “available Category” service
2 Choose a service
3 Select a “service’
4 Clicks ‘next’
5 Choose a ‘service” provider
6 Sends a “work request” to service provider
7 Service provider receive a “work request
8 Service provider accept the request
9
9.1
Service taker paying bill
Using bkash or DBBL
Alternative Flows
Step Branching Action
2a Choose multiple service
8a Service provider cancel the request
Quality Requirements
Step Requirements
6 The “work request” pop up message will stay no longer than 90 seconds after it is sent by the Service taker

24. Use case Enable Contact
Goal Service taker can communicate with service provider
Preconditions Service taker paying the money
Success End Condition Service taker can communicate with service provider
Failed End Condition Service taker can not communicate with service provider
Primary Actors:
Secondary Actors:
Service taker, Service provider
Credit card Company, bank
Trigger Select a “available Category” service
Main Success Flows
Step Action
1 Select a “available Category” service
2 Choose a service
3 Select a “service’
4 Clicks ‘next’
5 Choose a ‘service” provider
6 Sends a “work request” to service provider
7 Service provider receive a “work request
8 Service provider accept the request
9
9.1
9.2
Service taker paying bill
Using bkash
Using DBBs
10.1
10.2
Communicate with Call
Communicate with message
Alternative Flows
Step Branching Action
2a Choose multiple service
8a Service provider cancel the request
Quality Requirements
Step Requirements
6 The “work request” pop up message will stay no longer than 90 seconds after it is sent by the Service taker

25. An Activity Diagram

26. Requirement
Traceability Matrix

27. BR# Business requirements
BR1 Allow to service taker to set location
BR2 Allow to service taker send “work request” to Service
provider
BR3 Allow to service taker to pay money
BR4 Allow to cancel the work request
BR5 Allow to service taker to give rating to service provider
BR6 Allow to update Service taker profile
BR7 Allow to update service provider profile
Business Requirements

28. Use Case Referrence
Use Case No Use case name
UC-1 Set location
UC-2 Search Service
UC-3 Select Service List
UC-4 Select Service Provider
UC-5 Send “Work Request”
UC-6 Cancel “Work request”
UC-7 Pay Money
UC-8 Give Rating
UC-9 Update profile
UC-10 See Notification
UC-11 Change Active Status
UC-12 Accept Request
UC-13 Cancel Request
UC-14 See notification
UC-15 Enable Contact
UC-16 Update Profile

29. Test case No Test case
TC1 Maijdee Bazar
TC2 Chowmohoni
TC3 AC Servicing
TC4 Computer Servicing
TC5 Verify if Service taker able to choose a service
TC6 Verify if Service taker able to choose multiple Service
TC7 Verify if service taker is able to choose service provider
TC8 Verify if service taker is able to send “work request” to service provider
TC9 Verify if service provider is able to accept the request
TC10 Verify if service taker is able to pay using Bkash
TC11 Verify if service taker is able to pay using DBBL
TC12 Verify if service taker is able to cancel the request
TC13 Verify if service provider is able to cancel the request
TC14 Verify if service taker is able to give rating to service provider
TC15 Verify if service taker is able to update information like name, email etc.
TC16 Verify if service Provider is able to update information like name, email etc.
TC17 OFF
TC118 ON
Test Case For RTM

31.  Day by day people’s business is increasing. Besides if our daily-used things like refrigerator, air
condition, gas stove and other things get wasted or any other problem occurs like those then it
becomes quite irritating and hard to carryout those somewhere to repair or to find correct mechanic to
repair. To remove this burden our online platform is here to provide quality service providers for almost
everything.
 It will not only provide service providers to people, but also provide job to the service providers.
 Now-a-days maximum of our population use smartphone and 90% of them are based on Android
operating system. So that our project HandyMan will be an android application to reach people widely
and easily.
Conclusion