SOFTWARE REQUIREMENT
SPECIFICATION DOCUMENT
GetFit System
28 November 2020
Fedi Ghanmi
Aziza Ouali
Sophomore G9
CS200 Information System Design
1
Table Of Content
A. Section 1 -----------------------------------------------------------I – Introduction ---------------------------------------------------1.1 – Purpose --------------------------------------------------1.2 – Scope of project -----------------------------------------1.3 – Definition, Acronyms, and Abbreviations ----------1.4 – References -----------------------------------------------1.5 – Overview ------------------------------------------------B. Section 2 -----------------------------------------------------------II – General Description -----------------------------------------2.1 – Product Perspective -------------------------------------2.2 – Product Function ----------------------------------------2.3 – User Characteristics ------------------------------------2.4 – General Constraints -------------------------------------2.5 – Assumptions ---------------------------------------------C. Section 3 -----------------------------------------------------------III – Detailed Document for Users -----------------------------3.1 – Functional Requirement -------------------------------3.2 – Non-functional Requirement --------------------------D. System Models ---------------------------------------------------4.1 – Use Case Diagram -------------------------------------4.2 – Class Diagram ------------------------------------------
3
3
3
3
3
4
4
4
4
4
4
5
6
6
6
6
6
7
9
9
10
2
I – Introduction :
1.1 - Purpose of our document :
The purpose of this document is to present a detailed description of the GetFit System.
It will explain the features of the system, the interfaces of the system, what the system will do,
the constraints under which it must operate, and how the system will react to external stimuli.
This document is intended for managers, clerks, personal coaches, and clients.
1.2 - Scope of project :
The GetFit system is a system for a fitness club. It will facilitate authorization
methods. This system will boost the fitness club productivity by replacing the classic bookkeeping method. It will also provide secure online payment while connecting with other banks
to check for sufficient balance. Private accounts will be provided to clients once the payment
has proceeded. It will also provide a reduction for long period memberships. The software
assigns personal coaches to clients based on their chosen fitness programs. It will include a
forum dedicated to each coach and their respective clients. Secure and detailed data about
clients is available for managers. Keep track of clients’ progression and offer free
motivational quotes. Finally, clients have the ability to provide proper feedback.
1.3 - Definitions, Acronyms, Abbreviations :

BMI – Body Mass Index

OS – Operating System

SRS – Software Requirement Specification

C-Data – Cellular Data
3
1.4 - References :

Clerk – Personal Staff who is working in the Gym Reception.

Client – A potential member who is not yet registered in the system.

Member – A registered client for fitness courses.

Manager – A responsible for the Fitness Club.

Users – any individual with access to the system Interface.
1.5 - Overview :
Section 2 of the SRS, the overall description section, gives an overview of the
functionality of the product in general terms. The 3rd section, the Requirement Specification
Section, will provide a profound explanation describing the system for both users and
developers and describes in technical terms the details of the functionality of the product.
II – General description :
2.1 – Product Perspective :
The Getfit is a web-based system. It interacts with two other systems. The banking
system, the various users’ email system and the browsers used to log in. The web system
provides menus for fitness programs, as it will contain a secure environment for multiple
financial transactions and private data storing of clients' information.
2.2 – Product Functions :
The GetFit system allows clients to register for fitness programs. It will provide
strategies of health that clients can sign up for. After signing in, the client must pay program
fees. Once the payment has proceeded, the system will contain multiple functionalities for
registered clients and managers.
4
A member can keep track of his progress. His weight will be calculated after each session and
using a complicated algorithm, the system will lay out graphic analysis to try figuring out the
member body type in response to his habits. It will also notify respective members 2 hours
prior to their registered session.
The clerks of the GetFit Gym use the system to register clients, Make sure payment is
proceeded and hand new members their following accounts with their emails. They will
answer members’ questions in the system forum and forward their feedback to managers.
Personal coaches can modify their members’ information. They will store data about their
progression and organize further sessions.
The managers will collect data from the clerks and construct graphs and analysis in order to
remain cost-efficient. They will update the system with the appropriate settings for each
season. Managers will also have control over the clerks’ accounts. They can add or remove
certain accounts, and certain fitness programs.
2.3 – User Characteristics :
The three main groups of GetFit users are managers, members and Gym personnel.
Managers are at the top level. They have total control over system functionalities. The amount
of product training needed for managers can vary from 30 to 60 hours since the system
requires constant maintenance. The skills needed by a manager are strategic and commercial
awareness skills.
Members are individuals who register for fitness programs with the GetFit system. These
programs require no product training since the members’ expertise and educational
background is unknown. The only skill needed is the ability to browse a website or an
application.
Gym personnel are split into two groups: The clerk-level personnel and personal coaches.
The skill needed by clerk personnel is an interpersonal skill as they require from 10 to 20
5
hours of product training.
Personal coaches require at least a bachelor’s degree in physical education, fitness training,
coaching and sport science. They need flexibility and adaptability as a skill.
2.4 – General Constraints :
This system provides web access to all users functions.
The members and Personal coaches’ graphical interface will be easy to manipulate so that no
training is required.
The managers’ graphical interface requires certain manipulation training. due to its
complexity. Monitoring both the clerks’ and personal coaches’ activities and not vice versa.
All financial transaction, credentials data and member balance checking is done in a secure
and encrypted environment.
Membership data, Gym inventory and managers’ information are stored in a well-monitored
database that is only accessible by administrators.
2.5 – Assumptions and Dependencies :
This system will be available only on Android, iOS, and Microsoft Operating
systems. Other Complexe OS will not have access.
System updates are done with the presence of wifi or C-data connexion.
Low-level users are highly dependant on high-level users.
III – Detailed Documents for users :
3.1 – Functional Requirements :
1.1 – The system shall provide registration for clients to become members.
1.1.1 – The system shall assign an account for each member with a selected password.
1.1.2 – The system shall allow secure payment to be made for members.
6
1.3 – The system shall record members’ choice of fitness program.
1.4 – The system shall monitor members’ progress, estimate their body types
and give advice.
1.5 – The system shall lay out various fitness programs available for members.
1.5.1 – The system shall indicate the price for each program.
1.5.2 – The system shall create discounts for loyal members.
1.5.3 – The system shall indicate each program’s availability.
1.6 – The system shall guide members with diet and sleep strategies.
1.6.1 – The system shall calculate Body Mass Index of members
1.6.2 – The system shall keep track of members activity.
1.7 – The system shall notify members 2 hours prior to their session starts.
1.8 – The system shall allow coaches and their respective members to communicate.
1.9 – The system shall allow members to ask questions and provide feedback.
1.9.1 – The system shall permit clerks to answer members’ questions.
1.9.2 – The system shall authorize clerks to forward various feedbacks to managers.
1.10 – The system shall connect with the banking system.
1.10.1 – The system shall secure payments received by members.
1.10.2 – The system shall make encrypted payments to coaches and clerks.
1.11 – The system shall permit coaches to propose programs.
1.12 – The system shall provide managers with database management tools.
1.13 – The system shall allow the manager to add or remove programs.
3.2 – Non-functional Requirements :
2.1 - The system shall provide web-access for all its users.
2.2 - The system shall provide persistent storage of membership, clients’, managers’
data and gym inventory information.
7
2.3 - The system shall contain ads to catch system users’ attention to the new
programs offered.
2.4 - The system shall provide efficient data-collect and computations without errors
in an average amount of time.
2.5 - The system shall provide an intuitive interface very simple to understand.
2.6 - The system shall be protected from unauthorized access to its stored data and
against viruses and malware attacks.
2.7 - The system shall be reliable and shall complete operations correctly without
bugs in the code, hardware failures, or problems with other system components.
2.8 - The system should have a high performance in the responsiveness to various
user interactions.
2.9 - The system must provide a website attendance limit that is scalable enough to
support 300 users at a time.
2.10 - The system shall display notifications when some of its components experience
some availability problems during maintenance and it has to indicate when these components
are going to be up again.
8
IV – System Models :
4.1 – Use Case Diagram:
9
4.2 – Class Diagram :
10
CS200 SRS Project
GetFit
Thank you.
11