GYM MANAGEMENT SYSTEM

(WEB-BASED APPLICATION)

BY

REBECA JOSEPH

SOFTWARE ENGINEERING PROJECT

DEPARTMENT OF SOFTWARE ENGINEERING
ISBAT UNIVERSITY

A Technical Design Document submitted to ISBAT university

For the Study Leading to a Project in Partial Fulfillment of the

Requirements for the Award of the Certificate of Software Engineering of ISBAT

university.

Supervisor
Mr. Bulega Herbert Moses
Department of Software Engineering
Institution of Information Technology, ISBAT university.
[email protected], +256 782996265

i|Page
DECLARATION
I declare to the best of my knowledge that all the information contained herein this project design
document that it is out of my hard work and as a result of actual fieldwork carried out during the
course of the semester.

Sign:

……………………………………………………………………………

Date:

……………………………………………………………………………

Supervisor’s Approval

I……………………………………. being an ISBAT university supervisor, have supervised this

student during the production of their project ……………………………………………………...

Date ………………………………………………………………………………………….
Name of Supervisor …………………………………………………………………………
Signature …………………………………………………………………………………….

ii| P a g e
ACKNOWLEDGEMENT

This Project at ISBAT university has been a very memorial and unique experience for me. It
opened up new avenues of grabbing knowledge and skills through research which will certainly
stand as helpful in the years to come.

I would like further, to graciously thank my classmates for the support they have rendered to me
in the successful completion of this Project. Your efforts are highly appreciated and may God
richly bless you.

I am extremely indebted and thankful to my Project guide and Lecturer Mr. Bulega Herbert
Moses and Mr. Cornelius who has been very co-operative, encouraging and supportive
throughout this project. Without their initiative and constant support this Project wouldn’t have
been completed or a success and made me capable of being worthy of recognition.

Last but not the least I am very grateful to all advisors who took out some invaluable time out of
their busy schedule and responded to my questionnaires / queries and provided me with all the
valuable information.

iii | P a g e
PROBLEM STATEMENT

The existing gym management system in my area is time consuming and lacks features such as
enabling customers to select the items according to their preference. The system also has limited
resources and it is difficult to monitor data usage when using it.

iv | P a g e
OBJECTIVES OF THE PROJECT

My objective is to develop a gym management system that is easy to use, efficient, and
error-free. The system should be able to handle a large volume of products and users. I
aim to provide the following features:
 The application is being developed in-order to make interaction easier between buyers
and mainly drop-shippers
 Makes it easier for them to know the clients’ preferences to the products they need, and if
they’re preferences can be met.
 Personalization
 Convenience
 Diverse Product Range

v|Page
INTERESTS GAINED FROM THE PROJECT

 PERSONAL INTEREST

Providing solutions to practical problems using knowledge gained from software management
and design during my course in software engineering at ISBAT university.

 INSTITUTIONAL INTEREST

The implementation of the management system will be dispensed for any business with an online
perspective in Uganda to effectively manage resources in an efficient, effective, accountable and
professional manner.

vi | P a g e
SCOPE OF THE PROJECT

The scope of this project is focused mainly on the inventory users and users as most of the
modern need a system that will create an interaction between the users and the users. Although
this is a prototype, the project could be extended to a larger scale.

vii
METHODOLOGY

To develop this web based application I was required to carry out a survey of an online store to
determine the major problems or challenges faced and how best the system can help mitigate
them. This was achieved through:

 Providing questionnaires to the administration officers

 Carrying out one on one interviews to find out their thoughts on adopting to such a
system.

viii | P a g e
ABSTRACT
The creation of an application (web based application) with databases has potential and benefits
in all sectors in Uganda.

Most of the inventory stores in Uganda encounter many problems related to the management of
their inventory users. The inventory users need a lot of time to capture huge amounts of data
using MS Excel which is so hard to use, Where the user has to memorize all the features of the
tool which is cumbersome and thus could lead to mistakes that could cause delays in their work.
To carry out my research work, he had to resort to the model prototype which enabled me to
approach the various stages of the creation of a software namely the analysis, the conception, the
development and the test of the application.

At the end of this research I have proposed an application that will allow libraries to record
information, manage users and products to provide, to set reminders when products have been
borrowed and not returned on time. In other words this application will allow quick access and
use of information.

ix | P a g e
Requirement Specification:
The application is to be designed and developed based on the following requirements:

a) The application should have a login screen that fetches the login details of the admin and
other members from the database.

b) The admin should have unlimited access to all the features of the system. He should be
able to add, update and delete any other member.

c) The other members namely the store users have limited access to some of the features of
the system

Software Requirements:
• Psqlite3
• Text editor e.g PyCharm
• Operating system e.g Windows 7, 8, 8.1, 10 or higher .
• Browser e.g Firefox, Google chrome or internet explorer

List of Acronyms
CSS Cascading style sheets

HTML Hypertext markup Language

x|Page
 Table of Contents
DECLARATION............................................................................................................................ii
Supervisor’s Approval...................................................................................................................iii
ACKNOWLEDGEMENT..............................................................................................................iv
PROBLEM STATEMENT.............................................................................................................v
OBJECTIVES OF THE PROJECT................................................................................................vi
INTERESTS GAINED FROM THE PROJECT..........................................................................vii
SCOPE OF THE PROJECT.........................................................................................................viii
METHODOLOGY.........................................................................................................................ix
ABSTRACT....................................................................................................................................x
Requirement Specification:............................................................................................................xi
List of Acronyms...........................................................................................................................xii
Table of Contents.........................................................................................................................xiii
List of Figures................................................................................................................................xv
CHAPTER ONE..............................................................................................................................1
1.1 INTRODUCTION.................................................................................................................1
1.2 Purpose...................................................................................................................................1
1.3 Scope......................................................................................................................................2
1.3.1 Document scope..............................................................................................................2
1.3.2 System scope...................................................................................................................2
1.4 Benefits of the Project............................................................................................................3
1.5 Security Assessment..............................................................................................................4
CHAPTER TWO.............................................................................................................................5
2.1 System Overview...................................................................................................................5
2.2 System Components..............................................................................................................7
2.3 Component Diagram of the School Management System.....................................................9
2.4 System Architecture.............................................................................................................10
2.5 Presentation Tier Package (Object Diagram)......................................................................11
2.6 Deployment Diagram for application Tier...........................................................................12

xi | P a g e
 2.7 Flow chart for the School Management System..................................................................13
CHAPTER THREE.......................................................................................................................14
3.1 Data Design..........................................................................................................................14
CHAPTER FOUR.........................................................................................................................16
4.1 Component Description.......................................................................................................16
4.2 Component Identifier...........................................................................................................16
4.2.1 Type...............................................................................................................................16
4.2.2 Purpose..........................................................................................................................16
4.2.3 Interfaces.......................................................................................................................16
4.2.4 Resmyces.......................................................................................................................16
CHAPTER FIVE...........................................................................................................................17
5.1 Overview of the Meer Interface...........................................................................................17
5.1.1 System Administrator....................................................................................................17
5.1.2 Meers.............................................................................................................................17
5.2 Screen Shots.........................................................................................................................17
5.3 Implementation, Testing and Validation report for the School Management System.........23
5.4 Document Approval.............................................................................................................23
5.5 Software Traceability Matrix...............................................................................................24
CHAPTER SIX: SYSTEM VALIDATION..................................................................................25
6.1 Introduction..........................................................................................................................25
CHAPTER SEVEN.......................................................................................................................26
7.1 Testing and validation findings............................................................................................26
7.2 System life cycle activities..................................................................................................26
7.2.1 Requirements and system acceptance test specification...............................................26
7.2.2 Inspection and Testing...................................................................................................31
7.2.3 Precautions....................................................................................................................32
7.2.4 Installation and system acceptance test.........................................................................32
7.2.5 Conclmeion....................................................................................................................33

xii | P a g e
List of Figures
Figure 5.4: Admin Login............................................................................................................. 21
Figure 5.5: User Login...................................................................................................................
22 Figure 5.6: User
Registration…..................................................................................................... 23 Figure 5.7:
Dashboard................................................................................................................. 24 Figure 5.8:
Author Management Page........................................................................................... 25 Figure
5.9: Publisher Management Page....................................................................................... 25
Figure 5.10: Member Management Page.......................................................................................
26
Figure 5.10: View Products Page......................................................................................................
27
Figure 5.10: Products Issuing
Page………......................................................................................... 27
Figure 5.10: Products Inventory
Page................................................................................................. 28

xiii | P a g e
 CHAPTER ONE
1.1 INTRODUCTION

There’s no doubt that the information revolution is the largest and most innovative that marked
the life of mankind in this century. Indeed, passing by being a passing fad or a passing trend, the
computer was meant to bring us many advantages to our way of life. No area was a stranger to
this strategy that offers many services both for business and administration.

But beyond the use of the computer, it is especially the establishment of communication between
computers, which has helped to revolutionize the methods of work. Thus, I have witnessed the
emergence of networks.

This step provides new users with new tools and enables them to improve their profitability and
productivity.

Today, the business is done online worldwide, the management of institutions is done through
network technology, all the systems of information management have been digitized. All these
innovations have been made to simplify life by making a lot of things in a short time. Within this
framework of ideas of my project: “Design and implementation of a school management system”
which can be used by several schools countrywide.

1.2 Purpose
The sole and seemingly main purpose of this document is to objectively guide the software
development team responsible for the design and implementation of this School Management
System or web application.

The intended audience of this document includes the designers, developers and testers of the
system. However other users such as the maintenance team and the end users may find this
document instrumental in the deep understanding of the system design and outlay.

1|Page
1.3 Scope

1.3.1 Document scope

This document contains description of the School Management system Component.

1.3.2 System scope

This web based application is intended to accomplish the following:

 My Store is a web-based application developed using Python It is designed to

help inventory users manage the store’s collection of products, journals, and other
materials more efficiently. The system provides features such as suppliers, drops, orders,
delivery, and season sections.

2|Page
1.4 Benefits of the Project
The benefits of this Inventory Management System include the following:

This application will give the administration access to information about their products. This will
save them a lot of time as every product bought is entered into the system and so are the users of
the store. This information can also be accessed remotely meaning one doesn’t have to be inside
the system premises to access the information.

It will help the inventory department save time in recording or keeping track of the products in
regards with the ongoing transactions like the borrowing and returning of products done by the
different members.

It will ease the librarians’ ways of making keeping track of the products as the system
automatically generates overdue reminders and all the records of the products given away are
kept online.

It will also provide a very safe environment for data backup a since all the information is kept on
the cloud and hence is not susceptible to fire or theft. Data manipulation is also minimal as only
authorized users are given access to the system.

Uganda is shifting from traditional methods to computerized high technology methods and this
application will help embrace the change hence improving on the technological advancement of
Ugandans.

About convenience, This Application will be viewed on any device despite its sizes. This will
help even those students that cannot afford computers and better smart phones.

1.5 Security Assessment

The Application has an authentication mechanism whereby only registered users get to add and
access the information stored by the application. Only the admin has unlimited access to the
system and therefore only him can add or remove other users.

Privacy of the information entered or shared in the Application is ensured.

3|Page
 CHAPTER TWO
2.1 System Overview
This Inventory Management System is a web based application that consists of users like
librarians and Inventory users and details about them that could be needed by the top
management in the administration. This application will run on the Internet and without an
Internet connection, one will not be able to access it.

Users are required to register and a username and password are required of the respective users
and these are the credentials that they will be required to use so as to access the system.

Registered users (students) will be able to access the products available and view their profile as
well as be able to make changes to it.

Registered admins will be able to view the staff, publishers, Inventory users, products available
and the issued products.

All the information entered by the users is stored safely on the web server using a secure
database system (MY SQL). This information is dynamic meaning it can be edited, and deleted
but only by authorized users and in this case the admin. This information is also available any
time a user requests for it.

On the other hand the non-registered users can only view the homepage, about us page, terms
and conditions page, view the products available in the Inventory, login page and the sign up
page.

This system is managed by an administrator and the admin account exists by default but he can
add any other admin hence giving him similar permissions or rights. He can view, manipulate or
delete any existing data stored in the database if at all he suspects any security threat in the
information provided.

The administrator also ensures that the application is running smoothly, debugs the code of the
application if any error or inquiry arises. He is also responsible for the security on the server side
by regularly monitoring and encrypting server-side information in order to protect from hackers.

4|Page
This application is designed and developed using Bootstrap, Datatables, C#, HTML, javascript
and CSS and ASP.net as the framework for C#. This system can be viewed on all kinds of
devices including but not limited to Desktop computers, laptops, smart phones.

5|Page
2.2 System Components
The system is comprised of:

Login page: This is where registered users are supposed to fill in their security credentials
(username and password) if they are to gain access to the system.

Dashboard: The admin can add any newly introduced products into the system for members to
access. Outdated or unwanted products can be deleted from the system as they will be of no more
importance.

Staff: New staff can be added and assigned to respective products as a way of being organized

and keep good track of the developments in the respective fields of the Inventory products.

Publishers: New publishers can be added and assigned to respective products as a way of being

organized and keep good track of the developments in the respective fields of the Inventory

products.

Overdue reminders: Products borrowed by the members are kept track of using the date they

were issued and the due date set in order to set a reminder for the admin to see when a products

hasn’t been returned on time.

6|Page
2.3 Component Diagram of the Inventory Management System

Figure 2.1: Component Diagram

Administrator Component: This component provides information to the server, maintains and
updates data in the server. The administrator also has full control and access to the system.

Server Component: This component contains all the data that is being used in the system i.e.
users’ details, transactions, products stock.

Viewing Component: This component acts as a display interface that appears before and after
the user and the administrator have logged in.

7|Page
2.4 System Architecture

Internet Connection

Admin Computer Server

Tutors

Figure 2.2: System Architecture

The figure above shows a more detailed view of how the different components of the system do
interact to be able to have a complete meaning of the data stored in the system for the final user
to use.

8
2.6 Deployment Diagram for application Tier

Figure 2.4: Deployment Diagram

The figure above illustrates how the system will be deployed. The system will be able to run on
the server online meaning one should have access to internet in order to use the system. A smart
phone, laptop or desktop computer can be used to access the application through app launch
and http request respectively.
12 | P a g e
2.7 Flow chart for the Inventory Management System
START

Login Page

Yes Is No
Session
Admin

Admin panel

Yes Is No
session
meer

Meer panel

Log out (session close)

STOP

Figure 2.5: Flow chart diagram

11 | P a g e
 CHAPTER THREE
3.1 Data Design
Database diagram of the Inventory Management System

Psqlite3 was used as the server for the project so there isn’t any database design

14 | P a g e
13 | P a g e
 CHAPTER FOUR
4.1 Component Description
The following components are the various types of components entailing the Inventory
Management System.

4.2 Component Identifier

4.2.1 Type
The major component of the Inventory Management System is the server to which the
application component will be hosted. This is a major player in that all the users of the
application have to access the application when online.

4.2.2 Purpose
Being a web based application, the server serves as a storage for the information for which the
application is designed for and this information can be accessed by users according to the
authentication and permissions granted to them by the administrator.

4.2.3 Interfaces
The interfaces of this system are the database and the front-end user interface which the user
interacts with. The database is where the structure of the information that is uploaded to the
server is maintained. This information is already processed by the time of entry therefore it is
ready for use by other users.

4.2.4 Resources
The major resource of this system is internet since information that the user needs is hosted first
for all to access.

CHAPTER FIVE
5.1 Overview of the User Interface
Any user of this system will be able to perform activities depending on the access level. The
system will be accessed by using URL so it can be accessed only when there’s an internet
connection.

14 | P a g e
5.1.1 System Administrator
The administrator updates the application’s data in the database, deletes unwanted data and
manages the application. He also keeps track of the application’s performance and maintains the
system in case of any malfunction or breach into the system.

5.1.2 Users
Only registered users can have access to the system that is the admin, teachers and students and
different accounts have got certain rights or permissions granted to them by the system
administrator.

5.2 Screen Shots

Below are the screen shots of the Inventory Management System

Admin Login page

Figure 5.4: Admin Login Page

This page has got the login form where the user is required to enter their security credentials that
is user name and password of the admin in order to gain access to the admin panel of the
application. The details entered in the form are checked with the database and if they match then
the admin is granted access to the system. The credentials to access the admin’s details is
“Happy” as the username and “2023” as the password.

15 | P a g e
Dashboard page

Figure 5.5: Dashboard Page

This page has got the login form where the user is required to enter their security credentials that
is user name and password in order to gain access to the user panel of the application. The details
entered in the form are checked with the database and if they match then the admin is granted
access to the system.

16 | P a g e
Supplier page

Figure 5.6: Supplier list

This is where the user registers themselves and will be using the system. The information or data
entered is stored in the database once the user submits it.

Buyer’s page

Figure 5.7: Buyer’s list

Here a User can view their details after logging in.

17 | P a g e
Season’s page

Figure 5.8: Season’s list

All information about the author is gathered and entered into the system by the admin only.
The information can be retrieved and viewed from the database.

Drop list

Figure 5.9: Drop list

All information about the publisher is gathered and entered into the system by the admin only.
The information can be retrieved and viewed from the database.

18 | P a g e
Product list

Figure 5.10: Product list

All information about the members is gathered and entered into the system by the admin only.
The information can be retrieved and viewed from the database.

Order list

Figure 5.11: Order list

19 | P a g e
All information about the products entered into the system by the admin only can be viewed.
Delivery page

Figure 5.12: Delivery list

This is where the products are lent and borrowed from. The row turns red if the due date has been
exceeded.

Notification page

Figure 5.13: Notifications

20 | P a g e
 Profile page

Profile

All information about the products is gathered and entered into the system by the admin only.
The information can be retrieved and viewed from the database.

21 | P a g e
 CHAPTER SIX: SYSTEM VALIDATION
6.1 Introduction
Overview of the document
This document talks about the testing and the validation findings that will encompass this
application’s lifecycle activities, requirements and system acceptance test specifications, the
design and implementation process, inspections and testing, precautions, installation and system
acceptance test, performance servicing maintenance and phase out plus conclusions which will
encompass the user manual and where users will find it.

System overview

This document is intended towards users who intend to adopt the easier way of managing data in
education systems found in most of the parts of Uganda. For the success of this application the
active parties shall be registered users strictly.

 System end users: These are people who have access to the application especially
registered users. That is to say students and teachers.

 Project supervisor: These are those that manage the resources during the development of
this system.

 Domain Experts: These give essential background information about the application
domain.

CHAPTER SEVEN
7.1 Testing and validation findings

7.2 System life cycle activities

This section contains tables for documentation of the system validation activities. Each
subsection is numbered in accordance with the overview scheme above. The tables are filled in
with information about tasks to be performed, methods to be used, criteria for acceptance, input
and output required for each task, required documentation, the persons that are responsible for
the validation and any other relevant information for the validation process. Topics excluded
from being validated are explicitly marked as such.

22 | P a g e
7.2.1 Requirements and system acceptance test specification
Topics Requirement specification
Objectives A computer or a smart phone with internet access
Version requirements Preferably HTML5 enabled browser for full functionality

Input Both users and the administrator can enter information in the
system
Output Processed data is rendered according to users requests
Functionality Requests or response are instant according to the strength or
speed of the internet
Hardware Control Devices to access the application must have internet access
Limitations Limited only to registered users
Safety Unlimited user access

Version Control No update needed from the user

Dedicated platform Any platform which has access to internet
Installation Accessed user the provided URL
Special Requirements Should be registered and approved by the admin
Validation report This document will be validated to the architects, developers
and system integrators specifying the validation of the system.

Topics System Acceptance specification

Service and This document is created by the project manager concerning
Maintenance maintenance, future updates, problem solutions and requested
modifications to be used by the architects and developers

Errors and alarms Any types of errors, the system will be able to flag them

Objectives The operating environment is network enabled and the system

Scope The acceptance test encompasses the functionality, error handling

and version control
Input This is property and user information entered in the system
Output This is processed data viewed according to the user’s request
Functionality Supports multiple users at the same time

23 | P a g e
 Personnel Users and administrators
Errors and alarms Error messages are displayed according to the type of error

24 | P a g e
 Topics Design and development planning
Objectives The project has spanned for one month where successive prototypes Ire
produced and presented to the supervisor for feedback
Development Plan Development tools Ire Laravel 5.2
Platform: Windows 10
The team was comprised of two developers
Review and The design plan was reviewed by the supervisor and approved testing
Acceptance was done through careful configuration, building and release
preparation.

25 | P a g e
 Topics Design Output
Implementation (coding Development tools were Laravel 5.2,
and compilation) Platform: Windows 10
Version Identification This is the pioneer system so it’s version id 1.0
Good programming Source code is; Source Code is;
practice • Modulized • Commented
• Functionally divided • Readable
Windows Programming
Dynamic Testing  All statements have been executed at least once.
 All functions have been executed at least once.
 All case segments have been executed at least once.
Utilities for validation Survey forms are to be put in future releases so as to engage users
and testing to act as passive developers
Inactive Code JavaScript assisted inputs have been implemented e.g. date fields
so as to limit errors that may arise due to incorrect date inputs
Documents A technical design document was developed to cater for the design
output specifications
Review and Acceptance The consistency of all sections in the technical design document
was tested and validated.

Topics Design Verification

Review This system is in its final stages of development as testing and
validations is vigorously being carried out
Change plans If functionality wasn’t able to be implemented, the supervisor was
notified and functionality removed.

7.2.2 Inspection and Testing

Topics Inspection plan and performance Date/Initials
Design Output  Programming coding stricture and 15th September 2023
source code.
 Evidence of hood programming
practice
 Design verification and documented
reviews
Comments: There was evidence of good

26 | P a g e
 programming practice with properly verified
and documented reviews
Documentation  System documentation, flow charts 15th September 2023
etc.
Comments: There is sufficient
documentation as Ill.

Software  Data Integrity 15th September 2023

development  File storage
environment  Access rights
 Code protection

Comments: Inspected and approved

Result of Inspection  Inspection Approved 17th September 2023

Comments: The core functionality i.e.

performance, security, integrity Ire found to
be present
Topics Test Plan and Performance Date/Initials
Test Objectives To see how many users can operate on the 17th September 2023
application at the same time
Relevancy of Tests To see how many users an application will 17th September 2023
support before performance is compromised
Scope of Tests 4 Users Ire able to access the application 17th September 2023
without compromising the performance
Configuration of The application was cleaned up, debugging 17th September 2023
Tests and logging settings Ire removed
Special concerns System functionality is minimal and needs 17th September 2023
further enhancements
Acceptance Criteria The system is prepared for release, 17th September 2023
debugging and logging settings removed
and lastly the application is signed

Action or errors A patch will be released and better version 17th September 2023
uploaded on the server to correct the error
Result of Testing  Testing approved 17th September 2023

Comments: After a series of configuration

tests, regression tests and acceptance tests,

27 | P a g e
 the first version of release of the software
was released
7.2.3 Precautions
Topics Registered Anomalies
Operating System Some application’s system input features are still manual yet
there can be some easier way to enhance on this functionality
General precautions The application entirely depends on internet connection so it
is advised to be connected to internet to have access.
7.2.4 Installation and system acceptance test
Topics Installation summary
Installation Method No installation required
Installation Media Provided URL
Input files Processed data and user images
7.2.5 Conclusion
By the subjected signature, it becomes evident that all validation activities are documented and
approved

28 | P a g e