Professional Documents
Culture Documents
FITNESS CENTRE
ROLL NO :
CLASS : XII
PGT (CS)
FATEHGARH CANTT
FARRUKHABAD
UTTAR PRADESH
1
ARMY PUBLIC SCHOOL FATEHGARH
CERTIFICATE
subject Computer Science (083) laid down in the regulations of CBSE for the
(Mahesh Upadhyay)
PGT Comp Science
Examiner:
Name: _______________
Signature:
2
TABLE OF CONTENTS [ T O C ]
01 ACKNOWLEDGEMENT 04
02 INTRODUCTION 05
04 PROPOSED SYSTEM 06
07 FLOW CHART 15
08 SOURCE CODE 14
09 OUTPUT 20
10 TESTING 20
12 BIBLIOGRAPHY 24
3
ACKNOWLEDGEMENT
Apart from the efforts of me, the success of any project depends largely on
the encouragement and guidelines of many others. I take this opportunity to express
my gratitude to the people who have been instrumental in the successful completion
of this project.
I express deep sense of gratitude to almighty God for giving me strength for
the successful completion of the project.
The guidance and support received from all the members who contributed
and who are contributing to this project, was vital for the success of the project. I am
grateful for their constant support and help.
4
PROJECT ON FITNESS CENTRE
INTRODUCTION
This software is specially used to maintain any fitness centre where they can
Today one cannot afford to rely on the fallible human beings of be really wants to
stand against today’s merciless competition where not to wise saying “to err is
human” no longer valid, it’s outdated to rationalize your mistake. So, to keep pace
with time, to bring about the best result without malfunctioning and greater efficiency
so to replace the unending heaps of flies with a much sophisticated hard disk of the
computer.
One has to use the data management software. Software has been an ascent
markets, which have helped in making the organizations work easier and efficiently.
Data management initially had to maintain a lot of ledgers and a lot of paper work
has to be done but now software product on this organization has made their work
faster and easier. Now only this software has to be loaded on the computer and work
can be done.
This prevents a lot of time and money. The work becomes fully automated
and any information regarding the organization can be obtained by clicking the
5
SYSTEM DEVELOPMENT LIFE CYCLE (SDLC)
6
PHASES OF SYSTEM DEVELOPMENT LIFE CYCLE
INITIATION PHASE
7
SYSTEM CONCEPT DEVELOPMENT PHASE
8
PICTORIAL REPRESENTATION OF SDLC:
PLANNING PHASE
9
of operations, system security, verification and validation, and systems engineering
management planning.
This phase formally defines the detailed functional user requirements using
high-level requirements identified in the Initiation, System Concept, and Planning
phases. It also delineates the requirements in terms of data, system performance,
security, and maintainability requirements for the system. The requirements are
defined in this phase to alevel of detail sufficient for systems design to proceed. They
need to be measurable, testable, and relate to the business need or opportunity
identified in the Initiation Phase. The requirements that will be used to determine
acceptance of the system are captured in the Test and Evaluation MasterPlan.
Further define and refine the functional and data requirements and document
them in the Requirements Document,
Complete business process reengineering of the functions to be supported
(i.e., verify what information drives the business process, what information is
generated, who generates it, where does the information go, and who
processes it),
Develop detailed data and process models (system inputs, outputs, and the
process.
Develop the test and evaluation requirements that will be used to determine
acceptable system performance.
DESIGN PHASE
10
connections. Using a bottom-up approach, designers first identify and link minor
program components and interfaces, then expand design layouts as they identify
and link larger systems and connections. Contemporary design techniques often use
prototyping tools that build mock-up designs of items such as application screens,
database layouts, and system architectures. End users, designers, developers,
database managers, and network administrators should review and refine the
prototyped designs in an iterative process until they agree on an acceptable design.
Audit, security, and quality assurance personnel should be involved in the review
and approval process. During this phase, the system is designed to satisfy the
functional requirements identified in the previous phase. Since problems in the
design phase could be very expensive to solve in the later stage of the software
development, a variety of elements are considered in the design to mitigate risk.
These include:
11
DEVELOPMENT PHASE
12
Testing as a deployed system with end users working together with contract
personnel
IMPLEMENTATION PHASE
This phase is initiated after the system has been tested and accepted by the
user. In this phase, the system is installed to support the intended business
functions. System performance is compared to performance objectives established
during the planning phase. Implementation includes user notification, user training,
installation of hardware, installation of software onto production computers, and
integration of the system into daily work processes. This phase continues until the
system is operating in production in accordance with the defined user requirements.
13
FLOW CHART
START
SOURCE CODE
fit=sql.connect(host='localhost',user='root',passwd='admin@123
',database='fit_project')
if fit.is_connected():
print('connected')
print('')
print('')
print('WELCOME TO RAHI FITNESS CENTRE')
print('')
print('')
print('TO LOGIN PRESS :1
')
print('')
print('')
print('TO CREATE YOUR NEW ACCOUNT PRESS :2
')
print('')
print('')
print('TO EXIT PRESS :3
')
print('')
14
c=int(input('enter your choice'))
if (c==1):
print('')
print('to login please enter your user id and password')
print('')
user_id=input('enter your user id')
print('')
passwd=input('enter your password')
print('')
name=input('enter your name')
print('')
c1=fit.cursor()
c1.execute('select * from user_fitness_rahi1')
data=c1.fetchall()
count=c1.rowcount
15
print('to update new items press
:4 ')
print('')
c2=int(input('enter your choice'))
if (c2==1):
c1=fit.cursor()
c1.execute('select * from custmer')
data=c1.fetchall()
count=c1.rowcount
print('total custamer is',count)
for row in data:
print(row)
elif (c2==2):
print('')
print('to update costumer details please enter
the following details')
print('')
v_cusamer_id=int(input('inter castamar id (in
intiger) :'))
print('')
v_custamar_name=input('castamer name is
:')
print('')
v_camtamar_addras=input('enter addras of
castamer')
print('')
v_date_of_joined=input('camtamer joined data')
print('')
v_amt_paid=int(input('paid amuount'))
print('')
c1=fit.cursor()
#c1.execute('create table custmer(custmer
varchar(100) primary key,custmer_name
varchar(100),custmer_address varchar(1000),joined_date
varchar(100),amt_paid varchar(100))')
16
update_dtails="insert into custmer values("+
str(v_cusamer_id) +",'"+ (v_custamar_name) +"','"+
(v_camtamar_addras) +"','"+ (v_date_of_joined) +"',"+
str(v_amt_paid) +")"
c1.execute(update_dtails)
fit.commit()
print('costumer details succesully updated')
elif (c2==3):
print('FOLLOWING ITEMS RECTHERE IN',name
,'JIM')
c1=fit.cursor()
c1.execute('select * from jim_items')
data=c1.fetchall()
count=c1.rowcount
print('total jim item is',count)
for row in data:
print(row)
elif (c2==4):
print('to update new items enter the
following detils')
v_object_id=int(input('enter the object
code(in integer)'))
v_object_name=input('enter the name of jit
items')
v_date_of_purchase=input('enter the date og
purchase')
v_repairing_date=input('enter the date of
repair')
v_total_people_using=int(input('total
person'))
c1=fit.cursor()
updates2=("insert into jim_items values('"+
str(v_object_id) +"','"+ (v_object_name) +"','"+
(v_date_of_purchase) +"','"+ (v_repairing_date) +"','"+
str(v_total_people_using) +"')")
17
c1.execute(updates2)
fit.commit()
print('item updated')
else:
('something wemt wrong')
elif (c==2):
print('')
print('to create your account please enter your user id
and password')
print('')
c1=fit.cursor()
#c1=fit.cursor("('create table user_fitness_rahi1(user_id
varchar(100) primary key,password varchar(100),name
varchar(100))')
v_user_id=int(input('choose your user id (in integar)'))
print('')
v_passwd=int(input('create your password (in integar)'))
print('')
v_name=input('your full name')
print('')
c1=fit.cursor()
update=("insert into user_fitness_rahi1 values("+
str(v_user_id) +","+ str(v_passwd) +",'"+ (v_name) +"')")
c1.execute(update)
fit.commit()
print('account created')
elif (c==3):
18
print('vist again')
print('')
print('thank you')
else:
('something wemt wrong')
fit=sql.connect(host='localhost',user='root',passwd='admin@123',database='fit
_project')
if fit.is_connected():
print('connected')
c1=fit.cursor()
c1.execute('create table user_fitness_rahi(user_id varchar(10) primary
key,password varchar(11),name varchar(10))')
fit.commit()
print('table created')
fit=sql.connect(host='localhost',user='root',passwd='admin@123',database='fit
_project')
if fit.is_connected():
print('connected')
c1=fit.cursor()
c1.execute('create table jim_items(object_id int(225) primary
key,object_name varchar(65),date_of_parchase varchar(65),repairing_data
varchar(65),total_people_using int(65))')
fit.commit()
19
print('table created')
OUTPUT
Account created
20
21
22
23
24
25
TESTING
TESTING METHODS
Software testing methods are traditionally divided into black box testing and
white box testing. These two approaches are used to describe the point of view that
a test engineer takes when designing test cases.
SPECIFICATION-BASED TESTING
26
the output value (or behaviour), either "is" or "is not" the same as the expected value
specified in the test case. Specification-based testing is necessary, but it is
insufficient to guard against certain risks
The black box tester has no "bonds" with the code, and a tester's perception
is very simple: a code must have bugs. Using the principle, "Ask and you shall
receive," black box testers find bugs where programmers don't. But, on the other
hand, black box testing has been said to be "like a walk in a dark labyrinth without a
flashlight," because the tester doesn't know how the software being tested was
actually constructed.
That's why there are situations when (1) a black box tester writes many test
cases to check something that can be tested by only one test case, and/or (2) some
parts of the back end are not tested at all. Therefore, black box testing has the
advantage of "an unaffiliated opinion," on the one hand, and the disadvantage of
"blind exploring," on the other.
White box testing, by contrast to black box testing, is when the tester has
access to the internal data structures and algorithms (and the code that implement
these)
27
CODE COMPLETENESS EVALUATION
White box testing methods can also be used to evaluate the completeness of
a test suite that was created with black box testing methods. This allows the software
team to examine parts of a system that are rarely tested and ensures that the most
important function points have been tested.
28
HARDWARE AND SOFTWARE REQUIREMENTS
SOFTWARE REQUIREMENTS:
I. Windows OS
II. Python
III. mysql
29
BIBLIOGRAPHY
***
30