automation fitness center project synopsis
1
Project Synopsis
MCSP-060
“Automation System of
Fitness Center”
By
SHRUTI RANI
(182015660)
Under the guidance of
AMBIKESH
In partial fulfillment of the requirements for the award of the
degree
Master of Computer Applications (MCA)
January 2020
NAME : SHRUTI RANI
ENROLLMENT NUMBER: 182015660
PROGRAMME CODE : MCA
SEMESTER: 6th
STUDY CENTER CODE: 0769
STUDY CENTER NAME: SHYAM LAL COLLEGE
REGIONAL CENTER CODE : 29 (DELHI 2)
2
3
4
5
6
PROJECT
SYNOPSIS
7
Table of Contents
1. Introduction 9
1.1 Background 9
1.2 Objective 10
1.3 Purpose And Scope 11-12
1.3.1 Purpose 11
1.3.2 Scope 12
2. Input Of The Project 13
3. Output Of The Project 14
4. Servey Of Technologies 15
5. Requirements And Analysis 16-19
5.1 Problem Definition 16
5.1.1 Project Identification Of Need 16
5.1.2 Problem Statement 17
5.1.3 Existing System 17
5.1.4 Drawbacks Of Existing System 18
5.1.5 Proposed System 18
5.1.6 Advantages Of Proposed System 19
5.2 System Requirements Specification 20-21
5.2.1 Software 20
5.2.2 Front End 20
5.2.3 Backend 20
5.2.4 Hardware 21
5.3 Planning And Scheduling 21-22
5.3.1 Gantt Chart 22
5.4. Software And Hardware Requirements 23-23
5.4.1 Hardware 23-24
5.4,2 Software 24
5.5. Preliminary Product Description 24
5.6 Conceptual Model 24
5.6.1 Data Flow Diagrams 24-30
5.6.2 Entity Relationship Diagram (E-R Diagrams) 31-32
5.6.3 Tables 33-38
6. Scope Of Future Application 39
7. Components Of Proposed System 40
7.1 Main Components Of Proposed System Are Described 40
7.1.1 Administrator 40
7.1.2 Trainee 40
7.1.3 Instructor 40
8. System Study And Analysis 41
8.1 Introduction 41-42
8.2 System Analysis-Feedback Automation System 41
8.3 Identification Of Need 42
9. Feasibility Study 43-45
9.1 Technical Feasibility 43
9.2 Operational Feasibility 44
8
9.3 Economic Feasibility 45
10. Software Engineering Paradigram Applied 46-47
10.1 The Linear Sequential Model 46-47
11. System Designing 48-50
11.1 Introduction 48
11.2 Architectural Design 49-50
12. Optimization Of Code 51
13. Testing 52-55
13.1 Verification 53
13.2 Unit Testing 53
13.3 System Testing 53
13.4 Performance Testing 53
13.5 Multi-User Testing 53
13.6 Validation Check 54-55
14. Software Cost Estimation 56-57
15. Implementation 58
16. Maintenance 59-61
17. Limitation Of The Project 62
18. Conclusion 63
19. Bibliography 64
9
INTRODUCTION
India will be global InfoTech giant in near future. This project is being used to automate all
the phases of Fitness Center. This Project has helped to whole management in its smooth
management and increase in efficiency and effectiveness.
The present manual system requires daily updating of number of registers. Maintenance of
registers is also not done properly. It takes a lot of space to keep the records. If one is not very
careful then there is a possibility of issuing more then one schedule to a member. And
schedule problem all ways faced by members. Attendence all creates problem.
There is an increased risk of error in the manual system. Redundancy of data creeps in the
manual system and it becomes a time-consuming process to answer management queries and
prepare management reports. The manual registers and files to be maintained increases with
the increase in number of equipments & members.
1.1 Background
We have done a project on Automation system of Fitness Center and database
management and transactions. This system is proposed to be an automate database
management & transactions. This stores employee, customer, payroll, receipts, and
products information. It also provides the facility of search & advanced search for
searching the records efficiently & immediately.
10
1.2 Objectives
Reducing workload: In manual system there is lot of workload on the staff this can be greatly
reduced by developing this package.
Reducing Service Time: - With this package data can be easily accessed and in a very short
time, i.e.; to say the time taken to retrieve information is slashed to a large extent.
Data Accuracy: - As in this software, Computer handles all the data, so there are rare changes
of mistake.
Query Facility: - This Software provider the search operation on the basis of no of fields.
Better Communication with Management: - Accuracy of the information provides better
communication facility with the customer.
Report: - Report can be generated in a short time span and with accuracy.
The objective of the proposed system would be to overcome the problems faced in the manual
system. A unique code is generated for each; •exercise Equipment, transaction & member etc,
so that Data retrieval & access can be made much faster & easier.
11
In computerized system, the user can do things in a much easier way as compared to manual
system such as viewing, modification, searching, removal of data and generating important
reports etc.
Mathematical, accounting and logical errors would get automatically rectified in the proposed
system. Reports can be generated on the click of a button. Design of the proposed system
must take the following into consideration.
The software should have the provision to enter all the data regarding member coach and
equipments. Also a table should be created for entering the Payment of coach Fee of
members. It should also incorporate the information of all types of member transaction &
schedule of a particular member should be recorded so as to maintain a ledger of transactions
of member. On a search regarding the availability of the member, the database should be able
to represent accordingly. Each and every coach and member made their attendance daily.
1.3 Purpose And Scope
1.3.1 Purpose
The purpose or objective of this system is to digitalize and create an automated system. The
system will perform the task like adding the new member to the gym, removing the member
or keeping the payments records and other stuff required in managing the gym properly.
12
The present scenario in the gyms is that the records are kept by writing in a file on the paper.
Every management task is done manually. This creates a system unreliable and confusing to
keep the correct track of the records.
The maintenance of the system like this is hardly required until it needs to change any part of
the system. The information about the various things contained in the system are like
members, trainers, equipment can get by just a few clicks unlike the paper documents required
the serious reading for such information.
It helps in creating the various batch according to their preference or if they want a particular
trainer. It made easy to generate the reports of various operations performed in the gym are
like paying the fee it can be stored and later evaluated and get the list of members who did not
pay the fee.
1.3.2 Scope
This system does not only limit itself to the administration and but also helps the members of
the gym. The members can have options like attendance and fee payment change batch
request etc.
This will improve the transparency between the members which is always a good quality in
the system. It will also give the layer of security to the administration and the users that only
authorized users can access by their credentials.
Some major takeaways:
Online registration of the member
Issuing the timetable of batch on system
13
Increase transparency between stakeholders
Easy payment options
Standardization of the system.
INPUT TO THE PROJECT
Input design is the process of converting user-originated inputs to a computer-based format.
The goal of designing the input data is to make the data entry as easy. logical and free from
errors as possible. Inaccurate input data are the most common cause errors in data processing.
Errors entered by data entry operator can be controlled by input design. In entering the
operators need to know the
Following:
How to allocated space for each information.
Field sequence, which must match that in the source document.
The format in the data fields are entered for e.g. the data may be of different formats
but the user might be required to enter it only in one format. So, it is essential for him
to know the exact in which he should enter data so that later on working results are
not obtained after processing the data.
The ''Commercial Package" has input screen designed through VB forms. The forms and
reports are extremely user friendly and the major features of the screen are listed below.
14
Appropriate hints are provided on the field level in each form, which facilitates the
data entry operator when he/she is using the for data entry.
Lists of values are provided adequately as and when required, for the convenience of
the user.
For each of the options data entry is facilated through the use of single screen. This in
turn makes the data entry less cumbersome and less confusing for data entry operators.
OUTPUT TO THE PROJECT
Output is the most important and direct source of information to the user. Efficient,
intelligible output design should improve the system's relationships with the user and helps in
decision making. A form of output is a hard copy from the printer and can be displayed on the
terminal.
The general design principles used in designing output reports are:
The design must be such that it can be read from left to right and from top to bottom.
The most important item, such as key field, should be easily available.
All pages must have headings and page number. The date on which the report was
prepared should also be printed.
All columns must be labeled with meaningful labels.
Too many details should be avoided.
Control footing abstracts information about groups of detail lines must be effectively
used.
Similarly, page and report footings must be properly defined.
15
SERVEY OF TECHNOLOGIES
The present scenario in the Fitness Center is that the records are kept by writing in a file on
the paper. Every management task is done manually. This creates a system unreliable and
confusing to keep the correct track of the records.
The maintenance of the system like this is hardly required until it needs to change any part of
the system. The information about the various things contained in the system are like
members, trainers, equipment can get by just a few clicks unlike the paper documents required
the serious reading for such information.
16
REQUIREMENTS AND ANALYSIS
5.1 PROBLEM DEFINITIONS
The first step in planning a software project is to prepare in the customer's terminology a
concise statement of the problem to be solved and the constraints that exists for its solution.
The problem should include a description of the present situation and goals to be achieved by
the new system.
5.1.1 Project Identification Of Need
It helps in creating the various batch according to their preference or if they want a particular
trainer. It made easy to generate the reports of various operations performed in the Fitness
Center are like paying the fee it can be stored and later evaluated and get the list of members
who did not pay the fee.
It also helps the users in reducing the carbon footprint as the amount of paper used in
company reduces.
This also helps in keeping the standard width of the management system as if there is a case
where the administration involves more than one person to manage the Fitness Center.
17
5.1.2 Problem Statement
To automate the feedback system presently handled manual.
The feedback is just the performance evaluation sheet to be filled by the anyone against the
service provider. This is a sheet from which the "excellence level of the individual can be
estimated and therefore, the necessary action is taken by the management corresponding to
performance. The project of feedback automation is basically to develop a Computer
Controlled system where feedback is filled by anyone (trainee in this case) and is evaluated by
machine itself.
5.1.3 Existing System
The existing system is presently being handled manually.
In TICL the trainees undergoing their training fill the feedback form in order to help
management to evaluate the performance level of the instructors and to know the level of
infrastructure they are providing so that they can take necessary steps. The feedback from
contain different questions each having five options with unique numeric code as follows:
0- Unsatisfactory
1- Satisfactory
2- Good
3- Very good
4- Excellent
5- No comments
18
Multiplying each question number with its corresponding option marked by the trainee and
then taking the sum of all multiplications evaluate the form. The batch wise feedback is
evaluated by calculating the average of feedback form filled by all students of that batch. The
feedback form can be calculated on the following basis:
- Weekly
- Monthly
- Individually
- Course Batch
5.1.4 Draw Backs Of Existing System
- It is a mantlal system; each evaluation is done manually which is very time
consuming.
- There is no check on whether the trainee is filling the feedback for his own batch
instructor or not.
- In manual system the instructor can fill its own feedback form using student names.
- The filled back form is changeable.
5.1.5 Proposed System
The automated system has large benefits in case of record keeping and various other fields'.
No redundancy occurs due to normalized databases. For fast access, one can extract
information from the existing data. The important decisions are based on the information
available at any point of time. Beside data access, a computerized system also enables us to
19
manage data efficiently. Managing data involves storing, organizing, adding , deleting and
modifying data. A window program offers a high degree of user interaction using the
graphical elements that form the objects on the window the user sees thus providing good user
interface.
Further, the benefits of proposed system against the existing system includes .
It would be easy to evaluate the feedback form regardless of whether evaluated on
batch basis or on individual basis or some other one.
The student can fill the feedback form of his own instructor only the verification of
which is done by the system.
No instructor can fill the feedback form against any instructor himself.
Once the feedback form is filled it is only read only to the management.
5.1.6 Advantages Of Proposed System
It helps in creating the various batch according to their preference or if they want a
particular trainer. It made easy to generate the reports of various operations performed
in the gym are like paying the fee it can be stored and later evaluated and get the list of
members who did not pay the fee.
It also helps the users in reducing the carbon footprint as the amount of paper used in
company reduces.
This also helps in keeping the standard width of the management system as if there is a
case where the administration involves more than one person to manage the gym.
20
This system does not only limit itself to the administration and but also helps the
members of the gym. The members can have options like attendance and fee payment
change batch request etc.
5.2 SYSTEM REQUIREMENTS
5.2.1 Softwares
The softwares that would be used to develop this project is VB and SQL
SERVER
5.2.2 Front End
The VB will serve as front end in this project. The interaction between the user and system
will be done using VB. VB is used to design the graphical user interface from where the user
can handle and manipulate data.
5.2.3 Backend
The SQL SERVER will be serving as backend in the development of the project. All data
used in this project will be stored in the databases, which will contain information about the
trainee, instructor, feedback fill etc in the form of tables.
These tables will be used for manipulations.
21
5.2.4 Hardware
The hardware that would be used to develop this project
Any Pentium machine
Minimum 2Gb hard disk
64Mb RAM
Win9x
5.3 PLANNING AND SCHEDULLING
5.3.1 Gantt Chart
A timeline chart can be developed for the entire project. Alternatively, separate charts can be
developed for each project function or for each individual working on the project. When
multiple bars occur at the same time on the calendar, task concurrency is implied. The
diamonds indicate milestones.
Once the information necessary for the generation of a timeline chart has been input, the
majority of software project scheduling tools produce project tables—a tabular listing of all
project tasks, their planned and actual start- and end-dates, and a variety of related information
(Figure 1). Used in conjunction with the timeline chart, project tables enable the project
manager to track progress.
22
5.3.1 Gantt Chart
| Phases | 2/05/202 0 to 17/05/20 20 | 18/05/20 20 to 31/05/20 20 | 1/06/202 0 to 14/06/20 20 | 15/06/20 20 to 28/06/20 20 |
| 1,1.1to 1.3 | Yes | |||
| 2,3,4 | Yes | |||
| 5,5.1 to 5.6.3 | Yes | |||
| 6,7,7.1.1to 7.1.3,8,8.1 to 8.3,9,9.1 to 9.3 | Yes | |||
| 10,10.1,11,11.1,11.2, 12 | Yes | |||
| 13, 13.1 to 13.6,14,15,16,17,18, 19,20 | Yes |
REQUIREMENTS
5.4.1 Hardware
23
100 MBPS processor Intel Pentium III 1.GHz
RAM 128b MB
CACHE MEMORY 512 KB
HARD DISK 20 GB
MONITOR 15’’LG
KEYBOARD Multimedia + Internet
MOUSE Mechanical two buttons with
rolling boll
CD DRIVE 52X
LANCARD 10/100 MBPS
HUB 012
FLOPPY DRIVE 1.44 MB
CABLES Twisted Pair
OTHERS Speakers, Microphone etc.
SOFTWARE
OPERATING SYSTEM Window NT Server
FRONT END Visual Basic 6.0
RDBMS Microsoft SQL Server 7.0
Designing Ms paint, Photo shop
Word Processor Ms-Word
ARE YOU DOING THIS PROJECT FOR ANY CLIENT / INDUSTRY?
24
ANS:- No
5.5 PRILIMANARY PRODUCT DESCRIPTION
As modernizing is taking over all the systems and digitalizing helps them improve in so many
particular ways. The Automation System of Fitness Center is one of the systems which helps
the administration in speeding up the tasks at the same time reducing the complexity.
5.6 CONCEPTUAL MODEL
5.6.1 Data Flow Diagram
Data Flow Diagram (DFD) is a graphical tool used to describe and analyze the movement of
data trough a system - manual or automated including the process, stores of data and delays in
the system. They are central tools and the basis from which other components are developed.
It depicts the transformation of data from input to output through processes and the
interaction between processes.
Transformation of data from input to output through processes described logically and
independent of physical components is called logical DFD. Physical DFD show the actual
implementation and movement of data between people, departments and workstation.
DFDs are excellent mechanism for communicating with the customers during requirement
analysis and are widely used for representation of external and top-level internal design
25
specification. In the later situations, DFDs are quite valuable for establishing naming
conventions and names of system components such as subsystem, files and data links.
DFDs, also known as "BUBBLE CHART", thus, has the purpose of clarifying system
requirements and identifying major transformation that will become
programs in system design. So, it is starting point of design phase that functionally
decomposes the requirement specifications down to the lowest level of detail. A DFD consists
of series of bubbles joined by lines.
In a DFD, there are four components:
Sources or Destination of data such as humans, entities that interact with the system, outside
the system boundary, who forms the source and the recipient of information are depicted in
the form of closed rectangle.
Data Flow is packet of data. It identifies dataflow - dat a in motion. It is a pipeline through
which information flows. It is depicted in DGD as an arrow mark with the pointer pointing in
the direction of the data flow. This connecting symbol is present between an entity, process
and data stores.
This arrow mark also specifies sender and the receiver.
Process depicts the procedure, function or modules that transform input data into outputs.
They are depicted as a circle or a bubble with the procedure name and a unique number inside
the circle.
26
Data stores are the physical areas in the computer's hard disk where group of related data are
stored in the form of files. They are depicted as an open- edged rectangle. The data store is
used either for storing data into files or for reference purpose.
The DFD methodology is quite effective, especially when the required design is not clear. The
DFD is easy to understand after a brief orientation. The detailed DFDs for "FEEDBACK
AUTOMATION SYSTEM" are shown ahead:
The following rules govern construction of data flow diagrams(DFD):
1. Arrmvs should not cross each other.
2. Squares, circles. and tiles must bear names.
3. Decornposed data flows must be balanced (all data flows on the decomposed diagram
must reflect flows in the original diagram).
4. No two data flows, squares, or circles can have the same name.
5. Draw all data flows around the outside of the diagram.
6. Choose meaningful names for data flows, processes, and data stores. Use strong verbs
followed by nouns.
7. Control information such as record counts, passwords, and validation requirements are
not pertinent to a data-flow diagram.
27
If too many events seem to be occurring at o given point. an analyst can decompose a data
conversion (circle). The now data conversations from a parent-child relationship with the
original data conversion: the child circle.
Symbols Used DFD :
Square Source/Destination of Data
Bubble Process for Transformation of Data
Arrows Data in notions (Data now)
Rectangle Data at rest (Data Source)
28
5.6.1 Data Flow Diagram
Context level
| Groups |
| Memberdetails | |
| Existing Records of Member | New of Updated Records |
| Payment |
| Eqmaster |
| Equipment Details |
| Setdiet |
| Mematt |
| Member Attendance |
| Coachatt |
SYSTEM OF
FITNESS CENTER
| Dietdetails |
| Groups |
| Emaster |
Details
| Information of Groups |
| Diet Information for Member |
Groups
Setting of
Schedule
Diet
Coach
Attendance
Payment of
Given Coach
29
Verification
User
| UserId |
Records
User Name and
Enter of Password
| UserId |
Records If any
Master Entry
| Coach Master |
| Memberdetails |
| New Update of Records |
| Groups |
| Exercise |
| Eqmaster |
| Eqmaster |
| Exercise | E I | quipments nformation |
| MemberDetails |
| Groups |
Details
Member Records
Coach
Records
Equipments
Records
New Information
New Records
Exersice Detials
30
Attendance
Coach
Member
| CoachAtt |
Entry Of
Coach
Entry of
Members
Member
| MemAtt |
| Dietmaster |
| Setex |
| Setdiet |
| Memmast er |
| Exmaster |
Details
Setting Schedule of Diet
Setting
Schedule of
Exercise
Diet
Details
Member
Details
Schedule
31
5.6.2 Entity Relationship Diagram
E-R Diagram is a way to represent conceptual database tools. The overall logical structure of a
database can be expressed graphically by an ER diagram which consists of the following
components :
Entity
Attribute
Relationship
M : 1
1 : M
1 : 1
M : M
Derived Attribute
Multi-valued Attribute
Weak Entity
Weak Relationship
32
5.6.2 ER-DIAGRAM
M M
M M
M
1
1
1
| CUSTOMER |
CU_REGL
CU_ID
CU_NAME
COACH
COACH_ADD
COACH_NAME
GUIDE
CHECK
AVAILABILITY
WORK
ON
| FITNESS CENTER |
FIT_REG
FIT_CAT
FIT_FAC
EMPLOYEE
EMP_NO
EMP_ADD
MANAGE
UPDATE
STR_NO
STR_CAT
STR_LOC
| STORE ROOM |
CU_MOB
COACH_MOB
33
5.6.3 Tables
CREATE TABLE[master].[dbo].[CoachAtt]
(
[SlipNo] nvarchar(10) NULL,
[Id] nvarchar(10) Null,
[Name] nvarchar(50) NULL,
[AttDate] smalldatetime NULL
)
CREATE TABLE[master].[dbo].[Coachpay]
(
[SlipNo] nvarchar(10) NULL,
[Mem_Id] nvarchar(10) Null,
[Mem_Name] nvarchar(50) NULL,
[FeeDate] smalldatetime NULL,
[MemFee]int Null
)
CREATE TABLE[master].[dbo].[DietMaster]
(
[Dcode] nvarchar(10) NULL,
[Dname] nvarchar(30) NOT Null,
[DDesc] nvarchar(50) NULL
)
CREATE TABLE[master].[dbo].[EGroup]
34
(
[EGroup] nvarchar(75) NOT NULL
)
CREATE TABLE[master].[dbo].[Emaster]
(
[ECode] nvarchar(10) NULL,
[EGroup] nvarchar(30) NOT NULL,
[EDesc] nvarchar(50) NULL
)
CREATE TABLE[master].[dbo].[Emp_master]
(
[Emp_code] nvarchar(10) NULL,
[EmployeeName] nvarchar(45) NOT NULL,
[Address] nvarchar(50) NULL,
[Phone1] nvarchar(15) NULL,
[Phone2] nvarchar(15) NULL,
[FatherName] nvarchar(50) NULL,
[fAddress] nvarchar(50) NULL,
[fPhone1] nvarchar(15) NULL,
[fPhone2] nvarchar(15) NULL,
[Gender] nvarchar(7) NULL,
[MaritalStatus] nvarchar(15) NULL,
[DateOfBirth] smalldatetime NULL,
[Age] int NULL,
[Mobile] nvarchar(50) NULL,
35
[Email] nvarchar(50) NULL,
[Qualification] nvarchar(100) NULL,
[Designation] nvarchar(50) NULL,
[JoiningDate] smalldatetime NULL,
[Salary] int NULL
)
CREATE TABLE[master].[dbo].[Eqmaster]
(
[Ecode] nvarchar(10) NULL,
[Ename] nvarchar(30) NOT NULL,
[weight] int NULL,
[price] int NULL,
[Desc] nvarchar(50) NOT NULL
)
CREATE TABLE[master].[dbo].[MemAtt]
(
[slipNo] nvarchar(10) NULL,
[Id] nvarchar(10) NULL,
[Name] nvarchar(50) NULL,
[AttDate] smalldatetime NULL,
)
CREATE TABLE[master].[dbo].[MemberFee]
(
[SlipNo] nvarchar(10) NULL,
[Mem_Id] nvarchar(10) NULL,
36
[Mem_Name] nvarchar(50) NULL,
[FeeDate] smalldatetime NULL,
[MemFee] int NULL
)
CREATE TABLE[master].[dbo].[MemberMaster]
(
[Mem_ID] nvarchar(10) NULL,
[Mem_Name] nvarchar(50) NULL,
[Mem_Add] nvarchar(50) NULL,
[Mem_Loc] nvarchar(30) NULL,
[Mem_pin] nvarchar(6) NULL,
[Mem_phone] nvarchar(15) NULL,
[Mem_phone2] nvarchar(15) Null.
[Gender] nvarchar(6) NULL,
[Age] smallint NULL,
[Height] int NULL,
[Weight] int NULL
)
CREATE TABLE[master].[dbo].[MtyFee]
( [
SlipNo] nvarchar(10) NULL,
[Mem_Id] nvarchar(10) NULL,
[Mem_Name] nvarchar(50) NULL,
[FeeDate] smalldatetime NULL,
[MemFee] int NULL
37
)
CREATE TABLE[master].[dbo].[Setdiet]
( [
slipno] nvarchar(10) NULL,
[MCode] nvarchar(10) NULL,
[MName] nvarchar(50) NULL,
[DName] nvarchar(30) NOT NULL,
[DDesc] nvarchar(50) NULL
)
CREATE TABLE[master].[dbo].[SetEx]
(
[slipno] nvarchar(10) NULL,
[MCode] nvarchar(10) NULL,
[Mname] nvarchar(50) NULL,
[Dname] nvarchar(30) NOT NULL,
[DDesc] nvarchar(50) NULL,
[SetD] nvarchar(10) NULL
)
CREATE TABLE[master].[dbo].[Userid]
(
[cLoginID] nvarchar(50) NULL,
[cPassword] nvarchar(50) NULL,
[cAdmin] nvarchar(5) NULL,
[CAdd] nvarchar(5) NULL,
[cMod] nvarchar(5) NULL,
38
[cBack] nvarchar(5) NULL,
[cRestore] nvarchar(50) NULL,
[cDelete] nvarchar(5) NULL,
[dCreateDate] smalldatetime NULL
)
39
SCOPE OF FUTURE APPLICATION
Since this system has been generated by using fourth generation languages, as we know that 4
GL makes easy to learn and operate frequently because appearance of different form.
The future scope of this project is the we make some changes in this project and provide some
central connectivity and put it on the web then it will be very useful and can be used like a
centralized software for the accept feedback on any product.
40
COMPONENTS OF PROPOSED SYSTEM
7.1 Main Components Of Proposed System Are Described Below
7.1.1 Administrator
This is one of the most important component of the Project. It adds the profile of the new
trainee in the database & assigns him a unique id so that he can fill the feedback form. He is
responsible for the evaluating the feedback forms. He can make alterations in the batches.
7.1.2 Trainee
The trainee is the vital component of the system, which is responsible for filling the feedback
form against his instructor. Trainee has to log in it in order to fill the feedback form or to see
their profile or to change their password.
7.1.3 Instructor
Instructor fills the feedback against their trainees, which includes filling their test marks, their
score in the seminars & discipline.
41
SYSTEM STUDY AND ANALYSIS
8.1 INTRODUCTION
A system is a collaction of functionally dependent components interactively working together
to attain a predefined goal.
Analysis is the process of diagnosing situations, done with a defiant aim, with the boundaries
of a system kept in mind to produce a report based on the findings.
Analysis is a fact-finding technique where studies like the system requirements,
specifications, feasibility analysis and cost analysis and carried out.
System analysis is a process of gathering and interpreting facts, diagnosing problems and
using the införmation to recommend improvements to the system. It is an activity that
encompasses most of the task collectively called as a "Computer System Engineering".
This is the most important step in a software project where we get a general idea about the
needs of customers or end users by having man to man conversation with them and about the
various conditions and restrictions that have to be taken care of while developing the software.
8.2 SYSTEM ANALYSIS-FEEDBACK AUTOMATION SYSTEM
The system analysis was conducted with the following things in mind.
- Identify the user needs.
42
- Perform economic and technical analysis.
- Evaluate the system concept for feasibility.
- Allocate functions to hardware, software, people database and other system elements.
- Establish cost and schedule constraints.
- Create a system definition that forms the foundation for all the subsequent
engineering work.
8.3 IDENTIFICATION OF NEED
As a "tirst step in the analysis the end users of the proposed system were met to get a first
hand information regarding their needs and wants. Ideas from both sides were exchanged in
order to get a standard and satisfactory system. Once
overall goals are identified, a detailed analysis on the technology needed to make the system
functional was made.
43
FEASIBILITY STUDY
An Important outcome of the preliminary investigation is the determination that the system
requested is feasible. There are 3 aspects in the feasibility study.
9.1 TECHNICAL FEASIBILITY
This is concerned with specifying equipment and software that will successfully satisfy the
requirement. The technical needs of the system may vary considerably, but might include:
The facility to produce outputs in a given time.
Response time under certain conditions.
Ability to process a certain volume of transaction at a particular speed.
Facility to communicate data to distant location.
In examining technical feasibility, configuration of the system is given more importance than
the actual make of hardware. The configuration should give the complete picture about the
system's requirements like how many workstations are required, how these units are
interconnected so that they could operate and communicate smoothly. Specific hardware and
software products can then be evaluated keeping in view with the logical needs of the books
supply office.
At the feasibility stage it is desirable that two or three different configurations will be pursued
that satisfy the key technical requirements but which represent different levels of ambitions
and cost.
44
9.2 OPERATIONAL FEASIBILITY
It is mainly related to human organizational and political aspects. The points to be considered
are:
What changes will be brought with the system?
What organizational structures are distributed?
What new skills will be required? Do existing staff members have these skills? If not,
can they be trained in due course of time?
Generally project will not be rejected simply because of operational infeasibility but such
considerations are likely to critically affect the nature and scope of the eventual
recommendations. This feasibility study is carries out by a small group of people who are
familiar with information system techniques, who understand the parts of the business that are
relevant to the project and are skilled in system analysis and design process.
As far as this project is concerned the changes which we have to be brought depends upon
whether we are going to build a new project or we going to modify some establishment in the
late one first of all we have make a network environment i.e. establishment of a server is
must. Then our focus goes towards workstations. Keeping in view of their hardware
requirements like network interface card etc.
There is also another clause to check what skills are required?
45
By means to say whether the existing staff is capable
9.3 ECONOMIC FEASIBILITY
Economic analysis is the most frequently used technique for evaluating the effectiveness of a
proposed system. More commonly known as cost/benefit analysis; the procedure is to
determine the benefits and savings that expected from a proposed system and compare them
with costs. If benefits outweigh costs, a decision is taken to design and implement the system.
Otherwise, further justification or alternative in the proposed system will have to be made if it
is to have a chance of being approved. This is an ongoing effort that improves in accuracy at
each phase of the system life cycle. This feasibility also depends
upon quality of staff hired and the proposed duration of time taken in this project sometimes it
might be possible due to extension of time duration may fall the project under loss. The study
of feasibility changes from phase to phase of the project development.
In this project although this feasibility study doesn't matter much in the case new setup of
project because we start according to client specification but on the other hand if we have to
modify over existing system we must take care of our existing resources and must analyze
specially the working condition of hardware like server quality etc.
46
SOFTWARE ENGINEERING PARADIGM APPLIED
To solve actual problems in an industry setting, software engineer or a team of engineers must
incorporate a development strategy that encompasses the process, methods, and tools layers.
The strategy is often referred to as a process model or a software-engineering paradigm. A
process model for software engineering is chosen based on the nature of the project and
application, the methods and tools to be used, and the 'controls and deliverables that are
required.
There are numbers of paradigm available:
The Linear Sequential Model
The Prototype Model
The RAD Model
The incremental Model
The Spiral Model
The WINWIN spiral Model
The Component- based development Model
The Concurrent Development Model
The Formal Methods Model
The Fourth Generation Techniques Model
The Model. which has been applied in my Project, is:
47
10.1 THE LINEAR SEQUENTIAL MODEL
It is also called as the classic life cycle or the Waterfall Model, the linear sequential model
suggests a systematic, sequential approach to software development that begins at the system
level and progresses through Analysis, Design, Coding, Testing and Support.
System/Information Engineering
Modeled after a conventional engineering cycle, the linear sequential model encompasses the
following Activities.
System/ Information Engineering and Modeling.
Software Requirement Analysis.
Design.
Code Generation.
Testing.
Support.
| Analysis |
| Code |
48
SYSTEM DESIGNING
11.1 INTRODUCTION
In Waterfall model, Software design follows the analysis. Design is concerned with
identifying software components (functions , specifying software structure, maintaining
record of design decisions and providing a blueprint for the implementation phase.
Software design methodology changes continually as new methods better Analysis and
broader understanding evolve .Software Design methodology lacks the depth ,flexibility, and
quantitative nature that is normally associated with more classical engineering design
disciplines However , techniques for software exists ,criteria design quality is available and
design notation can be applied. Once software requirement has been analyzed and specified ,
Software Design leads the three technical activities — Design , Coding Testing that are
required for building and verifying structure . Each activity transforms information in a
manner that ultimately results in validation of computer software .
Design is the only the process that can accurately translate a customer 's requirements into a
finished product or system , without design , risk Of building unable system exist.
In software design ,there are three distinct types of activities:
External Design.
Architectural Design.
Detailed Design.
49
Architectural and detailed designs are collectively referred to as Internal Design.
External design of software involves conceiving, planning out and specifying the external
characteristics of a software product. These characteristics include user displays and report
formats and external data sources and data sinks and the functional characteristic,
performance requirements and high level process structure for the product .External design
begins during the analysis and continues into the design phase. The distinction between
Requirement definition and External design not sharp, but is a gradual shift in emphasis from
detailed "how".
Internal design involves conceiving, planning out and specifying the internal structure and
processing details of the software product. The goals of internal design are to specify internal
structure and processing details, to record design decisions and indicate why certain
alternatives and trade-off were chosen, to elaborate the test plan, and to provide blueprint for
implementation, Testing and Maintenance activities. The work products of internal design
include a specification of architectural structure, the details of algorithms and data structure
and the test plan.
11.2 ARCHITECTURAL DESIGN
Architectural Design involves identifying the software components, decoupling and
decomposing them into processing modules and conceptual data structures and specifying the
interconnection among components. Good notating can clarify the interrelationships and
interactions of interest, while poor notating can complicate and interface with good design
50
practice. The notations the shall be used to describe "Feedback Automation System" include
Data Flow Diagram (DFD).
51
OPTIMISATION OF CODE
The method is proposed to enable aggressive, inter procedural optimization in a setting where
code can be replaced at runtime. Code replacement involves both introducing a new module
into the system and reallocating old code. Code purging reallocates replaced code, which is
required in long running systems.
The approach, module merging, is simple and practical: we merge code modules and insert
code to check for code replacement at the appropriate points. We show how to preserve the
behavior of code purging. The net result is that merged modules preserve the original code
replacement behavior, while enabling optimization across code replacement boundaries.
52
TESTING
Software testing is the process of evaluation a software item to detect differences between
given input and expected output. Also to assess the feature of a software item. Testing
assesses the quality of the product. Software testing is a process that should be done during
the development process. In other words software testing is a verification and validation
process.
13.1 VERIFICATION
Verification is the process to make sure the product satisfies the conditions imposed at the
start of the development phase. In other words, to make sure the product behaves the way we
want it to.
The Smart Gym Management System was tested using the following two techniques of
application testing:
13.2 UNIT TESTING
In the line of strategy the entire individuals function and modules were put to test
independentally.
By following this strategy all the errors in coding were identified and corrected.
This method was applied in combination with the White Box and Black Box testing
53
Technique to find errors in each module
The effort of specific combination of data on system operation was tested.
The following were the testes carried out for Graphical User Interface (GUI).
It was seen that the pages opens properly based on related menu based commands.
It was tested whether all relevant menus, buttons, icons and other controls are
available and properly displayed.
13.3 SYSTEM TESTING
We use this testing method. System testing is the testing to ensure that by putting the
software in different environments (e.g., Operating Systems) it still works. System testing is
done with full system implementation and environment. It falls under the class of black box
testing.
13.4 PERFORMANCE TESTING
Performance testing is the testing to assess the speed and effectiveness of the system and to
make sure it is generating results within a specified time as in performance requirements. It
falls under the class of black box testing.
13.5 MULTI-USER SYSTEM TESTING
Database Locking Schemes: Whenever more than one person is accessing a record/s some
type of process must be used to prevent the outer users from attempting to update the same
54
record at the same time. This process is a locking scheme. In its simplest form, a locking
scheme allows only one user at a time to update information in the database.
13.6 VALIDATION CHECK
At the culmination of integration testing, software is completely assembled as a package,
interfacing errors have been uncovered and corrected, and a final series of software test -
Validation Testing - may begin. Validation can be defined in many ways, but a simple is that
validation succeeds when software functions in a manner that can be reasonably expected by
the customer.
Validation is an important characteristic of a good project because many times it has been
seen that running project may come to a halt stage or just because of ignorance of validation,
invalid or insufficient data may get enter in the database.
In this project I adopted many level of validations like in any entry form user is not supposed
to leave any field blank.
Then in the second level of validation I check individual fields like the Name can not be
numeric, Phone number should not contain any alphabet, if by mistake any alphabets are
entered then the message appears that phone number
should be in Digits and in the same context I applied the third level of validation that the
phone number should be between 7 to 10 digits and if user entered data in the number form
55
but not between in this range then the message splash that the number should between 7 to 10
digits.
56
SOFTWARE COST ESTIMATION
The software project management process begins with a set of activities that are collectively
called project planning. The first of these activities is ESTIMATION.
Whenever estimates are made, we look into the future and accept some degree of uncertainty
as a matter of course. Estimation of resources cost and schedule for a software development
effort requires experiences, access to good historical information, and the courage to commit
to quantitative measures when qualitative data are all that exist. Estimation carries inherent
risk that leads to uncertainty.
Project size is another important factor can effect the accuracy of estimates. As size an
increase, the interdependency among various elements of the software grows rapidly, time
also effect cost of the project.
Risk is measured by the degree if uncertainty in the quantitative estimates established for
resources, cost and schedule. If project scope is poorly understand or project requirements are
subject to change, uncertainty and risk factors become dangerously high. The software
planner should demand Completeness of function, performance and interface definitions. The
planner and the customer, should recognize that variability in software requirement means
instability in cost and schedule, a Project manager should not become obsessive about the
estimation; modern software engineering approaches take an iterative view of development. In
such approaches, it is possible to revisit the estimate and revise it when customer makes
changes to the requirements.
57
This project takes Four months for completion and takes around 10 to 15 thousand rupees to
complete whole application with its six year AMC.
58
IMPLEMENTATION
We know that software requirement analysis should focus on what the software is to
accomplish, rather than and on how processing will be implemented. However, the
implementation view should not be model representing the current mode of operation that is,
existing or proposed allocation for all system elements. Actually the implementation means
how we implement our project.
Implementation is categorized into three parts:
Training
Conversion
Post implementation review
This software module is available in CD media, which can be installed. After a short training
user can easily utilize the power of the application.
59
MAINTENANCE
The last part of the system development life cycle is system maintenance, which is actually
the implementation of the post implementation review plan.
When systems are installed they are generally used for long periods. The average life of a
system is 4 to 6 years with oldest application often in use for over 10 years. However, this
period of use brings with it the need to continually maintain the system. Programmers/analyst
sends sufficient time for maintaining programs. The study on the maintenance requirement for
the information system revealed that:
60-90 percent of the overall cost of the software during life of a system is spent on
maintenance.
In documented cases, cost of maintenance, when measured on the basis of writing each
instruction in coding form, is more than the 50 times the cost of developing a system.
The software demand is increasing at a faster rate than supply many programmers are
devoting more time on system maintenance than on a new software development. There is
backlog of new development work.
The maintenance can be classified as corrective, adaptation or prefecture. Corrective
maintenance means repairing, processing or performance failures or making alterations
because of previously ill-defined problems.
60
Adaptation maintenance means changing the program functions. Enhancing the performance
or modifying the programs according to user additional or changing needs are included in
maintenance the greatest amount of maintenance work is for user enhancement and improve
documentation of the system for better efficiency. More time and money are spent on
perfective than on corrective and adaptive maintenance together.
Maintenance covers a wide range of activities including correcting coding and design errors,
updating documentation and test data and upgrading user support. Many activities classified to
its original position. Unlike hardware, software does not wear out; it is corrected. In contrast
enhancement means adding, modifying or redeveloping the code to support changes in the
specifications.
The keys to reduce the need for maintenance while making it possible to carry on with
essential tasks more efficiently as follows:
More accurately defining the users requirement during system development.
Preparation of system documentation in a better way.
Using more effective ways for designing processing logic and communicating it to
project team members.
Making better use of existing tools and techniques.
Managing the systems engineering process effectively.
An addition factor in the success of the maintenance programmer is the work environment.
Maintenance programmers have generally been paid less amounts and receive less recognition
than other programmers.
61
Little attention has been paid to their training and career plans with the MIS functions.
Maintenance demands more orientation and training than any other programming activities,
especially for entry-level programmers. The environment must recognize the needs of the
maintenance programmer for tools, methods and training.
62
LIMITATION OF THE PROJECT
Some limitation of the project:-
This project has only suitable for fitness center, who keeps: Different record of
member.
It does not support Network Environment.
It is not suitable for online.
Not any sorting techniques used for fast access.
Required some basic training.
Less security of data is there.
63
CONCLUSION
The “AUTOMATION SYSTEM OF FITNESS CENTER” is successfully designed and
developed to fulfilling the necessary requirements, as identified in the requirements analysis
phase, such as the system is very much user friendly, form level validation and field level
validation are performing very efficiently. The old manual system was suffering from a series
of drawbacks. The present project has been developed to meet the aspirations indicated in the
modern age.
64
BIBLIOGRAPHY
Web-Site
www.microsft.com
vvww.vbguru.com
www.gurucode.com
www.planetsourcecode.com
Books
Date, C. J. An Introduction to Database System, 5/e
Elmasri, Ramez & Navathe, Shamkant B. Fundamental Of Database System, 2/e
Jalote, Pankaj An Integrated Approach To Software Engineering, 2/e
Pressman, Roger S. Software Engineering a practitioner's Approach, 4/e
[ALB83] Albreeht, A. J., and J. E. Gaffney, "Software Function, Source Lines of Code
and Development Effort Prediction: A Software Science Validation", IEEE Trans.
Software Engineering, November 1983. pp.639 - 648
[BOE81] Boehm B., Software Engineering Economics, Prentice — Hall 1981.
Peter Norton "Visual Basic 6.0"
65
[ALB83] Albreeht, A. J., and J. E. Gaffney, "Software Function, Source Lines of Code
and Development Effort Prediction: A Software Science Validation", IEEE Trans.
Software Engineering, November 1983. pp.639 - 648
[BOE81] Boehm B., Software Engineering Economics, Prentice — Hall 1981.
Peter Norton "Visual Basic 6.0"
[ALB83] Albreeht, A. J., and J. E. Gaffney, "Software Function, Source Lines of Code
and Development Effort Prediction: A Software Science Validation", IEEE Trans.
Software Engineering, November 1983. pp.639 - 648
[BOE81] Boehm B., Software Engineering Economics, Prentice — Hall 1981.
Peter Norton "Visual Basic 6.0"
[ALB83] Albreeht, A. J., and J. E. Gaffney, "Software Function, Source Lines of Code
and Development Effort Prediction: A Software Science Validation", IEEE Trans.
Software Engineering, November 1983. pp.639 - 648
[BOE81] Boehm B., Software Engineering Economics, Prentice — Hall 1981.
Peter Norton "Visual Basic 6.0"
[ALB83] Albreeht, A. J., and J. E. Gaffney, "Software Function, Source Lines of Code
and Development Effort Prediction: A Software Science Validation", IEEE Trans.
Software Engineering, November 1983. pp.639 - 648
[BOE81] Boehm B., Software Engineering Economics, Prentice — Hall 1981.
Peter Norton "Visual Basic 6.0"
[ALB83] Albreeht, A. J., and J. E. Gaffney, "Software Function, Source Lines of Code
and Development Effort Prediction: A Software Science Validation", IEEE Trans.
Software Engineering, November 1983. pp.639 - 648
[BOE81] Boehm B., Software Engineering Economics, Prentice — Hall 1981.
Comments
Post a Comment