Get Physical Trainer

Software Requirements Specification

Version 1.0

  

Group Id: F200285A81 (BC150401311,BS160401475)

Supervisor Name:Ahmed Hannan

 Revision History
Date Version Description Author
(dd/mm/yyyy)
12-18-2020 1.0 Get Physical Trainer is an online Bc150401311
portal which will help Users to Bs160401475
search, join and keep in touch
with trainers online.

Table of Contents

1. Scope (of the project)

 2. Functional RequirementsNon-Functional requirements

3. Use Case Diagram

4. Usage Scenarios

5. Adopted Methodology

6. Work Plan (Use MS Project to create Schedule/Work Plan)

SRS Document

Scope of Project:
Get Physical Trainer is an online portal which will help Users to search, join and keep in
touch with trainers online. Trainers will get registered on the portal with the required
information. Users will be able to search a trainer through different filters like fee,
location, experience and timings.

User will be able to sort the trainers through their ratings. User can contact a trainer
through built in system chat so they will be able to communicate without the involvement
of other applications. User will also get benefit of receiving physical health tips from
their trainers. Administrator of the application will have an overview of all the system.

Functional and Non Functional Requirements:

Functional Requirements

Administrator:
1. Administrator will have an overview of all system through dashboard.
2. Administrator will be able to update and delete registered trainers/Users.

Trainers:
1. Register in the portal with their personal details and some other information like
their fee, location, experience and working hours.
2. Update their information.
3. List of their joined Users.
4. Send physical health tips to all joined Users.
5. Contact their joined Users through chat system.

Users:
1. Register in the portal with personal information.
2. See a list of trainers depending upon fee, location, experience and working hours.
3. Contact a trainer through chat system.
4. Join a trainer.
5. Give and update review for their trainer.
6. Update their information.
7. Receive physical health tips from their trainer.

Non-Functional Requirements:

1. System should be usable for the Users with least computer literacy.
2. System should not take more than 3 seconds to load a page.
3. Software should be User friendly for all type of Users.
4. It will be windows supported like window 98, window XP, window Vista,
window 7, and window 8.
5. The back-end database will be MYSQL server and the front-end will be
developed in Visual Studio and language will be PHP.
 6. It will be a Web based application and care will be taken to keep it compliant with
most common browsers used in the country.
7. The things which would be in User use should be properly defined.

Use Case Diagram(s):

Usage Scenarios:

Use Case Title Register

Use Case Id 1
Requirement Id 3,8
Description: This use case is about registration of Users/trainer

Pre-Conditions: All compulsory information about new User/trainer should be available

Database should be online.
Task Sequence Exceptions
1. User/Trainer opts to create a new account
2. System asks for necessary information
3. User/Trainer enters information and opts to complete the
operation
4. Some information is not correct and needs correction
User corrects the information and continues from
5. System creates new account
6. System displays success message
Post-Conditions: A new User/Trainer account is created
Authority:
1. User
2. Trainer

Modification history: 1.0

Author: BC150401311,BS160401475

Use Case Title Login

Use Case Id 2
Requirement Id
Description: This use case is about logging in of Admin/User/Trainer

Pre-Conditions: Person logging in must be registered with system

Task Sequence Exceptions
1. Admin/User/Trainer If user is Admin, he
opens the login page should go to admin
login page
1. System asks for user ID /Password
2. User enters credentials
4. System verifies credentials
5. If credentials are correct Admin/User/Trainer is logged in else error
message is displayed
Post-Conditions: Admin/User/Trainer is logged in to the system
Authority:
1. Admin
2. Trainer
3. User

Modification history: 1.0

Author: BC150401311,BS160401475

Use Case Title View List of Trainers

Use Case Id 3
Requirement Id 9
Description: This use case is about viewing list of trainers
Pre-Conditions:User/Admin/ must be logged into the system
Database is online
Task Sequence Exceptions
1. User/Admin opts to view list of trainers
3. User/Admin provides some information and opts to complete
operation
4. System displays the result at screen
Post-Conditions:Display list of trainers
Authority:
1. User
2. Admin
Modification history: 1.0
Author: BC150401311,BS160401475

Use Case Title Join trainer

Use Case Id 4
Requirement Id 11
Description: This use case is about User join trainer

Pre-Conditions:User must be logged into the system

Database is online
Task Sequence Exceptions
1. User opens the login page
3. User enters some necessary information
4. System save information in the database
Post-Conditions: User join trainer
Authority:
1. User
Modification history: 1.0
Author: BC150401311,BS160401475

Use Case Title Update information

Use Case Id 5
Requirement Id 2,3,13
Description: This use case is about updating information
Pre-Conditions:User/Trainer/Admin must be logged in
User/Trainer/Admin must exist in system
Database is online
Task Sequence Exceptions
1. User/Trainer/Admin opts to update their information
2. System asks for necessary information
3. User/Trainer/Admin provides the information and opts to
complete operation
4. System updates the information in the database
5. System displays success message
Post-Conditions: Information in database changed successfully
Authority:
1. User
2.Trainer
3.Admin
Modification history: 1.0
Author: BC150401311,BS160401475

Use Case Title View List of Users

Use Case Id 6
Requirement Id 5
Description: This use case is about viewing List of their joined Users
Pre-Conditions:Trainer/Admin must be logged into the system
Database is online
Task Sequence Exceptions
1. Trainer opts to view list of their joined Users
3. Trainer provides some information and opts to complete
operation
4. System displays the result at screen
Post-Conditions:joined User list is displayed.
Authority:
1. Trainer
2. Admin
Modification history: 1.0
Author: BC150401311,BS160401475

Use Case Title Delete User/Trainer

Use Case Id 7
Requirement Id 2
Description: This use case is about removing a User/Trainer account from the system
Pre-Conditions:Admin is logged in
An account exists in the system
Database is online
Task Sequence Exceptions
1. Admin opts for deleting a User account
2. System asks for confirmation
3. User opts yes If User opts no, User will be deleted and
admin is redirected to switchboard.
4. System deletes that account from the system
5. System displays a success message
Post-Conditions: Account successfully deleted from system
Authority:
1. Admin

Modification history: 1.0

Author: BC150401311,BS160401475

Use Case Title Chat System

Use Case Id 8
Requirement Id 7,10
Description: This use case is about chat between trainer and User
Pre-Conditions:Trainer/User must be logged into the system
Database is online
Task Sequence Exceptions
1. Trainer/User opts to chat each other
2. System asks specific User/Trainer
3. User/Trainer selects person for chat
Post-Conditions:Chat between trainer and User
Authority:
1. User
2. Trainer
Modification history: 1.0
Author: BC150401311,BS160401475

Use Case Title Health Tips

Use Case Id 9
Requirement Id 6,14
Description: This use case is about send and recive physical health tips trainer to User

Pre-Conditions:trainer/User must be logged into the system

Database is online
Task Sequence Exceptions
1. Trainer opts to send physical health tips to User
2. System asks for necessary information
3. Trainer Physical Health Tips and opts to complete operation
Post-Conditions:Send/recive physical health tips trainer to User
Authority:
1. Trainer
2. User
Modification history: 1.0
Author: BC150401311,BS160401475
Use Case Title Review
Use Case Id 10
Requirement Id 12
Description: This use case is about User give review for their trainer

Pre-Conditions:User must be logged into the system

Database is online
Task Sequence Exceptions
1. User opt to give review to trainer
4. Users take training from trainer, After training they give review
3. Review will be display on trainer profile
Post-Conditions:User give review to trainer
Authority:
1. User
Modification history: 1.0
Author: BC150401311,BS160401475

Use Case Title Logout

Use Case Id 11
Requirement Id
Description: This use case is about logging the Admin/Trainer/User out from system.
Pre-Conditions: Admin/Trainer/User must be logged in
Task Sequence Exceptions
1. Admin/Trainer/User opts for logout
2. System logs out the Admin/Trainer/User
3. System displays the logout message
.
Post-Conditions:
Authority:
1. Admin
2. Trainer
3. User
Modification history: 1.0
Author: BC150401311,BS160401475

Adopted Methodology

VU Process Model
 It is decided to select VU process Model that is a Combination of Water Fall
model and Spiral Model.

Essentially, Water Fall Model is a framework for software development in which

development proceeds sequentially through a series of phases, starting with system
requirements analysis and leading up to product release and maintenance, whereas the
key characteristics of spiral model is risk management at regular stages in the entire
software development cycle. In VU Process Model we will be working in phases to
complete our given project.

Reasons for Choosing VU process Model.

1. This model provides the benefits of both spiral and water fall model.
2. It is sequential model with backward repetition.
3. We want to achieve the linear nature of waterfall and iterative plus risk reduction
nature of spiral model.
4. In this model work is done in phases to complete the given project.
5. If we want to make any changes at any stage than this model provides us with
flexibility to do so.
Waterfall Model:

This is the traditional life cycle model. It assumes that all phases in a software
project are carried out sequentially and that each phase is completed before the next is
taken up. It was a great step forward in software development as an engineering
discipline. The figure also depicts the single-level feedback paths that were not part of the
original model but that have been added to all subsequent improvements of the model;
they are described here. The original waterfall model had little or no feedback between
stages, just as water does not reverse or flow uphill in a cascade but is drawn ever
downward by gravity. This method might work satisfactorily if design requirements
could be perfectly addressed before flowing down to design creation, and if the design
were perfect when program implementation began, and if the code were perfect before
testing began, and if testing guaranteed that no bugs remained in the code before the users
applied it, and of course if the users never changed their minds about requirements.
The Spiral Model:

Another evolutionary life cycle model that combines the linear nature of the
Waterfall model and the iterative nature of the Prototyping model is the spiral model. The
project life cycle is divided into phases, and each phase is executed in all of the iteration
of the Spiral Model.
The radial coordinate in the diagram represents the total costs incurred till date. Each
loop of the spiral represents one phase of the development. The model is divided into four
quadrants, each with a specific purpose. Each spiral represents the progress made in the
project. In the first quadrant, objectives, alternative means to develop product and
constraints imposed on the product are identified. The next quadrant (right upper) deals
with identification of risks and strategies to resolve the risks. The third bottom right
quadrant represents the Waterfall model consisting of activities like design, detailed
design, coding and test. With each phase after customer evaluates the product,
requirements are further refined and so is the product. It is to be noted that number of
loops through the quadrants are not fixed and vary from project to project.

Spiral model is also termed as process model generator or Meta model. For example, if
any project requirements are not clear models like Prototyping or Incremental can be
derived from the spiral model.

Advantages:

1. The model tries to resolve all possible risks involved in the project starting with
the highest risk.
2. End users get a chance to see the product early in life cycle.
3. With each phase as product is refined after customer feedback, the model ensures
a good quality product.
4. The model makes use of techniques like reuse, prototyping and component based
design.

Disadvantages:

1. The model requires expertise in risk management and excellent management

skills.
2. The model is not suitable for small projects as cost of risk analysis may exceed
the actual cost of the project.
 3. Different persons involved in the project may find it complex to use.

Work Plan (Use MS Project to create Schedule/Work Plan)