TABLE OF CONTENT

1. INTRODUCTION TO THE STUDY

1.1 Introduction………………………………………………..……
1.2 Definition of the Problem ……………….……………………..
1.3 Drawbacks Of Current Manual- System …………….…………
1.4 Established the need of new System………………..…….……..
1.5 Proposed system…………..………………………………….…
1.6 Need…………………………………………………………….
1.7 Software and hardware requirements………………….………..

2 AIMS & OBJECTIVES OF THE STUDY

2.1 Objective………………………………………………………..
2.2 Aims……..………………….…………………………….…….
2.3
3 LITRATURE REVIEW……………………………………………

4 RESEACH METHODOLOGY…………………………………….

5 SYSTEM ANALYSIS

5.1 Principles of System Analysis……………………………………

5.2 Feasibility Study…………………………………………………
5.3 Cost and Benefit Analysis…………………..…….……………..
5.4 Technical Feasibility…………………………….………………
5.5 Operational Feasibility……………………………..……………..
5.6 Project Plan
5.7 Schedule Representation
5.8 System Life Cycle………………………………………...………

1
5.9 Identification of Need……………………………………………..
5.10 Fact Finding Techniques……………………………………....…..
5.11 Software Requirement Specification………………………….…..
5.12 ACD (Architectural Context Diagram)…………………………...
5.13 Pert Chart………………………………………………………….
5.14 ER-Diagram……………………………………………………….
5.15 Data Flow Diagram……………………………………………..…

6 SYSTEM DESIGN
6.1 System Design………..…………………...……………………..
6.2 Data Modeling……………………………………………..…….
6.3 Scheduling ….……………………………………………………

7 Deliverable (User Interface Design)

7.1 Story Boards
Home page
Online appointments form
Admin login
Admin dashboard
Add patients
8 TESTING
8.1 Testing phase…………………………………………………….
8.2 Levels of testing………………………...……………………….
8.3 Verification And Validation (V&V)……..………………………

9 SYSTEM IMPLEMENTATION
9.1 System Implementation Maintenance and review……………….
9.2 Hardware Evaluation Factors………….…………………………
9.3 Software Evaluation Factors………….……………………….…

2
10 SECURITY MEASURES………………………….……………..……

11 FURTHER SCOPE OF THE PROJECT……………………………..

12 CONCLUSION…………………………………………………….……

BIBLIOGRAPHY……………………………………………………………….…....

3
 CHAPTER – 1

INTRODUCTION TO THE STUDY

Introduction:

Online Attendance Management System is a web based application developed for

daily student attendance in university, colleges and institutes. If facilitates to access
the attendance information of a particular class. The information is sorted by the
admin, which provided with the admission detail. This system will also help in
evaluating attendance eligibility criteria of a student. Each teacher will shows up the
classes assigned to him.
Attendance is a basic and most important criteria needed in all the education system.
Attendance is used as a record to assess student consistency in participate the class.
Therefore, student is required to attend all teaching activities held by the institutions.
Once attendance is below the required policy, the student will be subjected to further
action or suspended from taking the final exam depend on the respective institutions they
are in.

Educational Institutions in Pakistan

Still being a developing nation Pakistan has seen a tremendous growth of the education
sector in the field of research as well as in the field of development of numerous large
and small scale education institutions still lacking in inter-structure facilities. Government
of Pakistan has still aimed at providing educational facilities by establishing colleges,
schools and universities. The basic working of various education in Pakistan is still on
paper as compared to education in European countries where computers have been put in
to assist the educational personals their work. The concept of automation of the
administration and management of education is now being implemented in Pakistan also,
with large School, Colleges and Universities.

4
PUPOSE:
Student Attendance Management System is a project developed to record and manage
daily student attendance. Currently many universities are still practicing old method to
take the student attendance which is by giving out attendance sheet to be sign by student.
As a result, it is time consuming, increase number of works of the lecturer and prone to
human error as it is difficult to ascertain whether the calculation made was correct.
Moreover, student needs to spend unnecessarily time during class session to sign on the
attendance sheet. This also disturbing and student may lose focus when the attendance
sheet is passing around during the class session.
Therefore, Student Attendance Management System is proposed to help or reduce
lecturer’s work. This system facilitates to access or manage the attendance information of
all the classes.
Hence, this system provides a tedious work in maintaining attendance records besides
saving time to analyze every attendance list and assuring the calculation made was error-
free.

DRAWBACKS OF CURRENT MANUAL- SYSTEM

1. The current manual system has a lot of paper work and it does not deal with old and

new car purchase and sale.

2. To maintain the records of sale and service manually, is a Time-consuming job.

3. With the increase in database, it will become a massive job to maintain the database.

4. Requires large quantities of file cabinets, which are huge and require quite a bit of

space in the office, which can be used for storing records of previous details.

5. The retrieval of records of previously registered patients will be a tedious job.

6. Lack of security for the records, anyone disarrange the records of your system.

5
7. If someone want to check the details of the available doctors the previous system

does not provide any necessary detail of this type.

ESTABLISH THE NEED OF NEW SYSTEM

1. Problem of Reliability: Current system is not reliable. It seems to vary in quality from

one month to the, next. Sometimes it gives good output, but some times the output is

worst.

2. Problem of Accuracy: There are too many mistakes in reports.

3. Problem of timeliness: In the current system the reports and output produced is

mostly late and in most of the cases it is useless because it is not on time.

4. Problem of Validity: The output and reports mostly contains misleading information.

The customer's information is sometimes not valid.

5. Problem of Economy: The current system is very costly. We have to spend lots of

money to keep the system up and going, but still not get the desired results.

6. Problem of Capacity: The current system is suffering from problem of capacity also.

The staff for organization is very less and the workload is too much. Few peoples

cannot handle all the work.

PROPOSED SYSTEM

l. Teacher Details: The new proposed system stores and maintains all the teachers
details.
2. Calculations: The new proposed system calculates expenses and income tax
automatically and it is very fast and accurate.

6
3. Registers: There is no need of keeping and maintaining expenses and employee
register manually. It remembers each and every record and we can get any report related
to employee and expense at any time.
4. Speed: The new proposed system is very fast with 100% accuracy and saves time.
5. Manpower: The new proposed system needs less manpower. Less people can do the
large work.
6. Efficiency: The new proposed systems complete the work of many patients in less
time.
7. Past details: The new proposed system contains the details of every past doctor and
patients for future assistance.
8. Reduces redundancy: The most important benefit of this system is that it reduces
the redundancy of data within the data.
9. Work load: Reduces the work load of the data store by helping in easy updates of
the products and providing them with the necessary details together with financial
transactions management.
10. Easy statements: Month-end and day-end statement easily taken out without
getting headaches on browsing through the day end statements.

NEED:

The following steps that give the detailed information of the need of proposed system are:

Performance:
During past several decades, Online attendance system is supposed to maintain manual
handling of all the College student’s daily activities. The manual handling of the record is
time consuming and highly prone to error. To improve the performance of the online
attendance system, the computerized online attendance system is to be undertaken.
Efficiency:
The basic need of the project is efficiency. The project should be efficient so that
whenever a new patient is admitted, and automatically a room is assigned and also a
student is assigned to the teacher according to the student’s class.

7
Control:
The complete control of the project is under the hands of authorized person who has the
password to access this project and illegal access is not supposed to deal with. All the
control is under the administrator and the other members have the rights to just see the
records not to change any transaction or entry.
Security:
Security is the main criteria for the proposed system. Since illegal access may corrupt the
database and it will affect not only the college, School or University but also it also
affects the student’s life. So security has to be given in this project.

SOFTWARE & HARDWARE REQUIREMENTS:

Hardware Requirements

Processor RAM Disk Space

Pentium II, Pentium III, 64 Mb or Higher 130 Mb

Pentium IV or higher

Software Requirements

Operating System Database

Win-98, Win-XP, Linux or any other higher My Sql

version

8
MY SQL:

Introduction

My SQL is an application used to create computer databases for the Microsoft Windows
family of server operating systems. It provides an environment used to generate databases
that can be accessed from workstations, the web, or other media such as a personal digital
assistant (PDA). MY SQL is probably the most accessible and the most documented
enterprise database environment right now. This also means that you can learn it a little
quicker than most other database environments on the market

What is SQL Used for:

Using SQL one can create and maintain data manipulation objects such as table, views,
sequence etc. These data manipulation objects will be created and stored on the server's
hard disk drive, in a table space, to which the user has been assigned.
Once these data manipulation objects are created, they are used extensively in
commercial applications.

DML, DCL, DDL:

In addition to the creation of data manipulation objects, the actual manipulation of data
within these objects is done using SQL.
The SQL sentences that are used to create these objects are called DDL's or Data
Definition Language. The SQL sentences used to manipulate data within these objects are
called DML's or Data Manipulation Language. The SQL sentences, which are used to
control the behavior of these objects, are called DCL's or Data Control Language.

9
 CHAPTER – 2

Project development approach

Software Process Model:

To solve actual problems in an industry, software developer or a team of

developers must incorporate a development strategy that encompasses the
process, methods and tools layers and generic phases. This strategy is often
referred to as process model or a software developing paradigm. A process model
for software developing is chosen based on the nature of project and application,
the methods and tools to be used, and the controls and deliverables that are
required. All software development can be characterized as a problem solving
loop in which four distinct stages are encountered: Status quo, Problem definition,
technical development and solution integration. Regardless of the process model
that is chosen for a software project all of the stages coexist simultaneously at
some level of detail.

Our Project Follows the Waterfall Model:

10
  The Waterfall Model:

The steps of the typical Waterfall Model are:

1. Requirement Definition.

2. System & Software Design.

3. Implementation.
4. Integration & System Testing.
5. Operation and Maintenance.

11
 Timeline Chart

Week 1
Work Task D1 D2 D3 D4 D5
Analysis
 Get project title
 Discuss about
project’s
functionality with
project guide.

Week 2
 Make the System
Flow Diagram.
 Make Data Flow
Diagram.
 Make
modifications in
System Flow Dia.
And DFD.

Week 3
 Make the Data
Dictionary related
to project
requirement.
 Identify features
and functionality
to be added.
 Visit related sites l

12
 and do the
compartmentalizat
ion
Milestone
Analysis is Complete

13
 Week 4
Work Task D1 D2 D3 D4 D5
Design
 Design home,
login, and logout
forms.
 Designing of
Statements
related pages,
Mini Statement
and Full
Statement.
Week 5
 Design of
Departmental
form for the user
or customer.
 Design of Update
citizens forms for
inter and intra
transferring of
data.
Week 6
 Design of Sports
Department
forms of user or
customer.
 Design of
Request to access
the data.
 Design of form
for changing the
Parent Field.
Milestone
Design is Complete.

14
 Week 7
Work Task D1 D2 D3 D4 D5
Coding
 Coding of home,
login, and logout
forms.
 Coding of
Statements
related forms.

Week 8
 Coding of
Sports
Department
 Coding of data
accessing from
the citizens
master table to
the sports
department.

Week 9
 Coding of data
transfer forms.
 Coding of forms
for data
transferring
between intra
and inter
department.

15
 Week 10
Work Task D1 D2 D3 D4 D5
Coding
 Coding of
Education
department
forms for the
government.
 Coding of
Request to
administrator
form.
 Coding of the
page for
blocking the data
access.
.
Week 11
 Coding of the
form for
changing the pin
value of the
customer or user.
Mile
Stone
Coding is Complete

16
 Week 12
Work Task D1 D2 D3 D4 D5
Testing
 Testing of home,
login, and logout
forms and made
changes.
 Testing of
accessing of
citizens data by
the various
departments
using the
specific search
Week 13
 Testing
departmental
transfer of data
between the
various
departments and
made changes.

17
 Week 14
 Testing of Data
Transfer forms
for inter and
intra department.
 Testing of
accessed data
forms of user or
customer and
Request form
and made
changes.

Week 15
 Testing of
blocking data
forms and form
for changing the
accessing of the
data and made
changes.
Mile
Stone
Testing is Complete.

18
 CHAPTER – 4

RESEARCH METHODOLOGY

The project ‘Online Attendance Sstem’ is based on the database, object oriented and
networking techniques. As there are many areas where we keep the records in database
for which we are using MY SQL software which is one of the best and the easiest
software to keep our information. This project uses PHP as the front-end software which

19
is an Object Oriented Programming and has connectivity with MY SQL. It is a web based
application in which number of clients can also access with a server.

HARDWARE

Processor : Pentium 2.4 GHz or above

Memory : 256 MB RAM or above

Cache Memory : 128 KB or above

Hard Disk : 3 GB or above [at least 3 MB free space required]

Pen Drive : 5 GB

Printer : Laser Printer

SOFTWARE

Operating System : Windows XP (Professional).

Font-End Tool : PHP, HTML, CSS, Bootstrap Java Script

Back-End : My Sql

FRONT END

We have implemented PHP for all the Client side validations. Client side JavaScript is
designed to reside inside HTML document & ensure they run properly. It is object based,
event driven, platform independent. These are important parts of any Web application to
implement Client side Validations and the invalid data is not submitted. The form is not
submitted until user fills in correct data. It is extremely useful to restrict mistakes by user.

BACK END

20
We have used My Sql. My Sql provides efficient/effective solution for major database
tech.
- Large database and space management.
- Many concurrent database users.
- High transaction processing requirement
- High Availability
- Industry accepted standards
- Manageable security
- Portability

21
 CHAPTER – 5

SYSTEM ANALYSIS

PRINCIPLES OF SYSTEM ANALYSIS:

PRINCIPLES:

 Understand the problem before you begin to create the analysis model.

 Develop prototypes that enable a user to understand how human machine

interaction will occur.

 Record the origin of and the reason for every requirement.

 Use multiple views of requirements like building data, function and behavioral

models.

 Work to eliminate ambiguity

System Analysis is a separation of a substance into parts for study and their
implementation and detailed examination.

Before designing any system it is important that the nature of the business and the way
it currently operates are clearly understood. The detailed examination provides the
specific data required during designing in order to ensure that all the client's
requirements are fulfilled. The investigation or the study conducted during the analysis
phase is largely based on the feasibility study. Rather it would not be wrong to say that
the analysis and feasibility phases overlap. High-level analysis begins during the
feasibility study. Though analysis is represented as one phase of the system
development life cycle (SDLC), this is not true. Analysis begins with system
initialization and continues until its maintenance. Even after successful implementation
of the system, analysis may play its role for periodic maintenance and up gradation of

22
the system. One of the main causes of project failures is inadequate understanding, and
one of the main causes of inadequate understanding of the requirements is the poor
planning of system analysis.

Analysis requires us to recall the objectives of the project and consider following three
questions:

• What type of information is required?

• What are the constraints on the investigation?

• What are the potential problems that may make the task more difficult?

Keeping the above questions in mind and considering the survey conducted to
determine the need of the system; the total system was designed and can be described
as under:

FEASIBILITY STUDY:

The feasibility study proposes one or more conceptual solution to the problem set of the
project. In fact, it is an evaluation of whether it is worthwhile to proceed with project or
not.

1. Evaluation of feasibility of such solutions. Such evaluation often indicates

shortcomings in the initial goals. This step is repeated as the goals are adjusted and
the alternative solutions are evaluated.

Feasibility analysis usually considers a number of project alternatives, one that is chosen
as the most satisfactory solution. These alternatives also need to be evaluated in a broad
way without committing too many resources. Various steps involved in feasibility
analysis are:

23
2. To propose a set of solution that can realize the project goal. These solutions are
usually descriptions of what the new system should look like.

Four primary areas of interest in feasibility study are:

Economic Feasibility: An evaluation of development cost weighed against the ultimate

income of benefit derived from the development system of product. In economic
feasibility, cost benefit analysis is done in which expected cost and benefits are evaluated.

COST AND BENEFIT ANALYSIS:

Developing an IT application is an investment. Since after developing that application it

provides the organization with profits. Profits can be monetary or in the form of an
improved working environment. However, it carries risks, because in some cases an
estimate can be wrong. And the project might not actually turn out to be beneficial.

Cost benefit analysis helps to give management a picture of the cost, benefits and risks. It
usually involves comparing alternate investments.

Cost benefit determines the benefits and savings that are expected from the system and
compares them with the expected costs.

In performing cost and benefit analysis it is important to identify cost and benefits
factors. Cost and benefits can be categorized into the following categories:

1. Development Costs – Development costs is the costs that are incurred during the
development of the system. It is one time investment.
2. Operating Costs – Operating Costs are the expenses required for the day to day
running of the system. Examples of Operating Costs are Wages, Supplies and
Overheads.

24
3. Hardware/Software Costs – It includes the cost of purchasing or leasing of
computers and it’s peripherals. Software costs involves required S/W costs.
4. Personnel Costs – It is the money spent on the people involved in the development
of the system.
5. Facility Costs – Expenses that are incurred during the preparation of the physical site
where the system will be operational. These can be wiring, flooring, acoustics,
lightning, and air-conditioning.
6. Supply Costs – These are variable costs that are very proportionately with the
amount of use of paper, ribbons, disks, and the like.
 BENEFITS

We can define benefits as

Profit or Benefit = Income – Costs

Benefits can be accrued by:

 Increasing income, or
 Decreasing costs, or
 Both

TECHNICAL FEASIBILITY:

Technical Feasibility includes existing and new H/W and S/W requirements that are
required to operate the project using PHP. The basic S/W requirement is J2EE in which
the front end of the online hospital management project has been done. The basic entry
forms are developed in PHP and the data is stored in the MY SQL.

OPERATIONAL FEASIBILITY:

Operational feasibility is mainly concerned with issues like whether the system will be
used if it is developed and implemented. Whether there will be resistance from users that

25
will affect the possible application benefits? The essential questions that help in testing
the technical feasibility of a system are following:

 Does management support the project?

 Are the users not happy with current business practices? Will it reduce the time
considerably? If yes, then they will welcome the change and the new system.
 Have the users involved in the planning and development of the project? Early
involvement reduced the probability of resistance towards the new system.
 Will the proposed system really benefit the organization? Does the overall response
increase? Will accessibility of information be lost? Will the system affect the
customers in considerable way?

Legal Feasibility:

A determination of any infringement, violation, or liability that could result from

development of the system. Legal feasibility tells that the software used in the project
should be original purchased from the legal authorities and they have the license to use it
or the software are pirated.

Alternatives:
An evaluation of alternative approaches to the development of system or product.

SYSTEM LIFE CYCLE:

System life cycle is an organizational process of developing and maintaining systems. It

helps in establishing a system project plan, because it gives overall list of processes and
sub-processes required for developing a system.
System development life cycle means combination of various activities. In other words
we can say that various activities put together are referred as system development life
cycle. In the System Analysis and Design terminology, the system development life cycle
means software development life cycle.

26
Following are the different phases of software development cycle:
• System study
• Feasibility study
• System analysis
• System design
• Coding
• Testing
• Implementation
• Maintenance

The different phase of software development life cycle is shown below.

27
28
29
IDENTIFICATION OF NEED:

We have designed the given proposed system in the PHP to automate the process of news
sites. Many different people use Usenet, for many different reasons, ranging from
discussions of various topics, requests for help or to trade media, which is often seen as
the ‘dark side’ to Usenet — the abuse of public news groups to trade copyrighted or
offensive material. Thankfully however, those that use Usenet responsibly far out weight
the few who use it as a tool for piracy etc.

Many of the people using and contributing to Usenet are people who work with computer
technology. These people often use Usenet to seek help with a piece of software or
suggest improvements, indeed one of the early functions of Usenet was to help users
identify and report bugs found in software.

Unfortunately, the massive growth seen within Usenet has also made it a difficult
medium to keep track of, the great variety and number of articles can take considerable
time to filter through in order to find those of interest. There have been a variety of
software applications created to help deal with this problem and many are freely available
for personal use.

The following steps that give the detailed information of the need of proposed system are:

Performance: During past several decades, the records are supposed to be manually
handled for all activities. The manual handling of the record is time consuming and
highly prone to error. To improve the performance of the Company system, the
computerized system is to be undertaken. The computerized project is fully computerized
and user friendly even that any of the members can see the report and status of the
company.

Efficiency: The basic need of this website is efficiency. The website should be efficient
so that whenever a new user submit his/her details the website is updated automatically.
This record will be useful for other users instantly.

30
Control: The complete control of the project is under the hands of authorized person who
has the password to access this project and illegal access is not supposed to deal with. All
the control is under the administrator and the other members have the rights to just see
the records not to change any transaction or entry.

Security: Security is the main criteria for the proposed system. Since illegal access may
corrupt the database. So security has to be given in this project.

31
E-R- DIAGRAM

32
SYSTEM DEVELOPMENT LIFE CYCLE
User Revised Requirement
Requirement Specification

Requirement Initial
Determinatio Feasibi
Requirement
n lity
Decision to Investigatio
Analys
n
Design Information is
System

Feasibility
Test Plan Study
.

Logical System Design Functional Spec.

System
Specific
System ation
System
Design Analysi
Implementation
s
Physical
Requirement
System Configuration
Data
Schedule Budget

System Hardware
Evaluation Study

System Modification Improved System

Maintenance

33
Class diagram
Its also known as relational table. Its shows up the relation between tables which represent all
relations. A UML class diagram is a list of what you think should get collected in a database table. A
relational database is a database that is composed of a bunch of linked tables. A table is just like a
spreadsheet, and in UML, we refer to tables as classes

34
 System flow diagram:

Data flow diagrams.

LEVEL-0:-

35
Admin:

Input:
1 Login with the authorized identification username and password
2 Add necessary information like student, teacher, subject or assign class.
Output:
3 Required Registration details.
Online Attendance System:
The system will save the edition and their details.
Input:
4 Manages the Details of students.
Output:
5 Delivers the details for the specified teacher.
My SQL Database:
This will stores each and every information that is saved by the admin whether it is the new class or an old
one. The modification or the updating of the registration is also very quickly and efficiently updated in the
database.
Input:
6 Saves the details of all the students as well as their information.
Output:
Gives the details of the students requested by the user.

LEVEL-1 DFD for User

36
Level-2 update

CHAPTER – 6

37
 SYSTEM DESIGN

System Design:

The design document that we will develop during this phase is the blueprint of the
software. It describes how the solution to the customer problem is to be built. Since
solution to complex problems isn’t usually found in the first try, iterations are most likely
required. This is true for software design as well. For this reason, any design strategy,
design method, or design language must be flexible and must easily accommodate
changes due to iterations in the design. Any technique or design needs to support and
guide the partitioning process in such a way that the resulting sub-problems are as
independent as possible from each other and can be combined easily for the solution to
the overall problem. Sub-problem independence and easy combination of their solutions
reduces the complexity of the problem. This is the objective of the partitioning process.
Partitioning or decomposition during design involves three types of decisions: -
Define the boundaries along which to break;
Determine into how money pieces to break; and
Identify the proper level of detail when design should stop and implementation should
start. Basic design principles that enable the software engineer to navigate the design
process suggest a set of principles for software design, which have been adapted and
extended in the following list:
Free from the suffer from "tunnel vision." A good designer should consider alternative
approaches, judging each based on the requirements of the problem, the resources
available to do the job.

The design should be traceable to the analysis model. Because a single element of the
design model often traces to multiple requirements, it is necessary to have a means for
tracking how requirements have been satisfied by the design model.
The design should not repeat the same thing. Systems are constructed using a set of
design patterns, many of which have likely been encountered before. These patterns

38
should always be chosen as an alternative to reinvention. Time is short and resources are
limited! Design time should be invested in representing truly new ideas and integrating
those patterns that already exist.

The design should "minimize the intellectual distance" between the software and the
problem as it exists in the real world. That is, the structure of the software design should
(whenever possible) mimic the structure of the problem domain. The design should
exhibit uniformity and integration. A design is uniform if it appears that one person
developed the entire thing. Rules of style and format should be defined for a design team
before design work begins. A design is integrated if care is taken in defining interfaces
between design components.

The design activity begins when the requirements document for the software to be
developed is available. This may be the SRS for the complete system, as is the case if the
waterfall model is being followed or the requirements for the next "iteration" if the
iterative enhancement is being followed or the requirements for the prototype if the
prototyping is being followed. While the requirements specification activity is entirely in
the problem domain, design is the first step in moving from the problem domain toward
the solution domain. Design is essentially the bridge between requirements specification
and the final solution for satisfying the requirements.

The design of a system is essentially a blueprint or a plan for a solution for the system.
We consider a system to be a set of components with clearly defined behavior that
interacts with each other in a fixed defined manner to produce some behavior or services
for its environment. A component of a system can be considered a system, with its own
components. In a software system, a component is a software module. The design process
for software systems, often, has two levels. At the first level, the focus is on deciding
which modules are needed for the system, the specifications of these modules, and how
the modules should be interconnected. This is what is called the system design or top-
level design. In the second level, the internal design of the modules, or how the

39
specifications of the module can be satisfied, is decided. This design level is often called
detailed design or logic design. Detailed design essentially expands the system design to
contain a more detailed description of the processing logic and data structures so that the
design is sufficiently complete for coding.

Because the detailed design is an extension of system design, the system design controls
the major structural characteristics of the system. The system design has a major impact
on the testability and modifiability of a system, and it impacts its efficiency. Much of the
design effort for designing software is spent creating the system design.

The input to the design phase is the specifications for the system to be designed. Hence,
reasonable entry criteria can be that the specifications are stable and have been approved,
hoping that the approval mechanism will ensure that the specifications are complete,
consistent, unambiguous, etc. The output of the top-level design phase is the architectural
design or the system design for the software system to be built. This can be produced
with or without using a design methodology. A reasonable exit criteria for the phase could
be that the design has been verified against the input specifications and has been
evaluated and approved for quality.

System design

40
DATA MODELING:

Admin

Field Type Constraint

Username Char (50) Not Null
Password Char (50) Not Null

lecture table

Field Type Constraint

lecture_id int (100) Primary key
teacher_id Char (100) Not Null
subject Char (100) Not Null
class_id Char(100) Not Null
date Char (100) Not Null
start_time Char(100) Not null
end_time Char (30) Not null
postedDate Date Not null

teacher_assigned_classes
Field Type Constraint
teacher_id int(22) Primary key
class_id int(22) Not null
subject Char(100) Not null

login

Field Type Constraint

id id(10) Primary key
username Char (100) Not null
password Char (100) Not null
status int (2) Not null

41
lecture_id int(22) Not null

subjects

Field Type Constraint

subject_id int(22) Primary key
subject_name Char(200) Not null
teacher_id int(11) Not null

class

Field Type Constraint

class_id int(22) Primary key
class_name Char(200) Not null
class_session Char(100) Not null

teachers

Field Type Constraint

teacher_id int(22) Primary key
teacher_name Char(200) Not null
loginStatus int(2) Not null

students

Field Type Constraint

student_id Char(100) Primary key

42
student_name Char(200) Not null
class_id Char(100) Not null

attendance

Field Type Constraint

student_id Char(100) Primary key
attendance Char(20) Not null
lecture_id Char(100) Not null

INPUT DESIGN
Input design is part of overall system design that requires special attention designing
input data is to make the data entered easy and free from errors. The input forms are designed
using the controls available in .NET framework. Validation is made for each and every data
that is entered. Help information is provided for the users during when the customer feels
difficult.
Input design is the process of converting the user originated inputs to a computer based
format. A system user interacting through a workstation must be able to tell the system
whether to accept the input to produce reports. The collection of input data is considered to be
most expensive part of the system design. Since the input has to be planned in such a manner
so as to get relevant information, extreme care is taken to obtain pertinent information
This project first will entered to the input of allocation forms it will be created on student
details form and subject entry form, time table form .it will helps to calculate subject wise
attendance system. next one if u want any verification on your data’s also available in details
show forms. Attendance to entered single subject wise or all subject wise attendance system
available in this project.

5.6.4 OUTPUT DESIGN

Output design this application “Student Attendance management system”
generally refers to the results and information that are generated by the system for many end-

43
users; output is the main reason for developing the system and the basis on which they
evaluate the usefulness of the application.

The output is designed in such a way that it is attractive, convenient and informative.
Forms are designed with various features, which make the console output more pleasing.

As the outputs are the most important sources of information to the users, better
design should improve the system’s relationships with us and also will help in decision
making. Form design elaborates the way output is presented and the layout available for
capturing information.

One of the most important factors of the system is the output it produces. This system
refers to the results and information generated. Basically the output from a computer system is
used to communicate the result of processing to the user.
Attendance management system to show the report subject wise attendance
maintaining by staffs. Taken as a whole report obtain on a administrator privileges only. this
forms will show weekly report and consolidate report generated date, batch, and class wise to
our end user. we want to change our report to convert Excel format .if you want change any
modification.

CHAPTER – 7
Project Interface

Login

44
Admin Dashboard

Add Class

45
Add teacher

Add subject

46
Add student

47
Class subject and teacher

Teacher login

48
49
 Update subject or teacher

Select class for update

50
Update subject, class or teacher

Search

51
 CHAPTER – 8

TESTING PHASE

One of the purposes of the testing is to validate and verify the system. Verification means
checking the system to ensure that it is doing what the function is supposed to do and
Validation means checking to ensure that system is doing what the user wants it to do.

52
No program or system design is perfect; communication between the user and the
designer is not always complete or clear, and time is usually short. The result is errors and
more errors. Theoretically, a newly designed system should have all the pieces in working
order, but in reality, each piece works independently. Now is the time to put all the pieces
into one system and test it to determine whether it meets the user's requirements. This is
the best chance to detect and correct errors before the system is implemented. The
purpose of system testing is to consider all the likely variations to which it will be
subjected and then push the system to its limits. If we implement the system without
proper testing then it might cause the problems.

1. Communication between the user and the designer.

2. The programmer's ability to generate a code that reflects exactly the system
specification.
3. The time frame for the design.

Theoretically, a new designed system should have all the pieces in working order, but in
reality, each piece works independently. Now is the time to put all the pieces into one
system and test it to determine whether it meets the requirements of the user. The process
of system testing and the steps taken to validate and prepare a system for final
implementation are:

LEVELS OF TESTING:

The different types of testing are as follows:

53
 UNIT TESTING

VALIDATION

INTREGRATION
N
SYSTEM

1. Unit Testing:

This is the smallest testable unit of a computer system and is normally tested using
the white box testing. The author of the programs usually carries out unit tests.

2. Integration Testing:

In integration testing, the different units of the system are integrated together to form the
complete system and this type of testing checks the system as whole to ensure that it is
doing what is supposed to do. The testing of an integrated system can be carried out top-
down, bottom-up, or big-bang. In this type of testing, some parts will be tested with white
box testing and some with black box testing techniques. This type of testing plays very
important role in increasing the systems productivity. We have checked our system by
using the integration testing techniques.

3. System Testing:

A part from testing the system to validate the functionality of software against the
requirements, it is also necessary to test the non-functional aspect of the system. Some
examples of non-functional tools include tests to check performance, data security,

54
usability/user friendliness, volume, load/stress that we have used in our project to test the
various modules.

System testing consists of the following steps:

1. Program(s) testing.
2. String testing.
3. System testing.
4. System documentation.
5. User acceptance testing.

4. Field Testing:
This is a special type of testing that may be very important in some projects. Here the
system is tested in the actual operational surroundings. The interfaces with other systems
and the real world are checked. This type of testing is very rarely used. So far our project
is concerned, we haven't tested our project using the field testing.

1. Acceptance Testing:
After the developer has completed all rounds of testing and he is satisfied with the
system, then the user takes over and re-tests the system from his point of view to judge
whether it is acceptable according to some previously identified criteria. This is almost
always a tricky situation in the project because of the inherent conflict between the
developer and the user. In this project, it is the job of the bookstores to check the system
that whether the made system fulfills the goals or not.

Why System Testing?

Testing is vital to the success of the system. System testing makes a logical assumption
that if all the parts of the system are correct, the goal will be successfully achieved.
Inadequate testing results in two types of problems:

55
1. The time lag between the cause and the appearance of the problem.
2. The effect of system errors on the files and records within the system.
Another reason for system testing is its utility as a user-oriented vehicle before
implementation.

Activity Network for System Testing

The test plan entails the following activities:

1. Prepare test plan.
2. Specify conditions for user acceptance testing.
3. Prepare test data for program testing.
4. Prepare test data for transaction path testing.
5. Plan user training.
6. Compile/assemble programs.
7. Prepare job performance aids.
8. Prepare operational documents.

Prepare Test
A workable test plan must be prepared in accordance with established design
specifications. It includes the following items:
• Outputs expected from the system.
• Criteria for evaluating outputs.
• A volume of test data.
• Procedure for using test data.
• Personnel and training requirements.
Specify Conditions for User Acceptance Testing
Planning for user acceptance testing calls for the analyst and the user to agree on
conditions for the test.

56
Prepare Test Data for Program Testing
As each program is coded, test data are prepared and documented to ensure that all
aspects of the program are properly tested.

Prepare Test Data for Transaction Path Testing

This activity develops the data required for testing every condition and transactions to be
introduced into the system. The path of each transaction from origin to destination is
carefully tested reliable results.

Plan User Training

User training is designed to prepare the user for testing and converting the system. User
involvement and training take place parallel with programming for three reasons:
• The system group has time available to spend on training while the programs are
being written.
• Initiating a user-training program gives the systems group a clearer image of the
user's interest in the new system.
• A trained user participates more effectively in system testing.

The training plan is followed by preparation of the user training manual and other text
materials.

Compile / Assemble Programs

All programs have to be compiled / assembled for testing.
Prepare Job Performance Aids
In this activity the materials to be used by personnel to run the system are specified and
scheduled. This includes a display of materials.

Prepare Operational Documents

57
 During the test plan stage, all operational documents are finalized including copies of the
operational formats required by the candidate system.

Systems testing
The computer department to ensure that the system functions as specified does this testing. This
testing is important to ensure that a working system is handed over to the user for acceptance
testing.

Acceptance testing.
The user to ensure that the system functions, as the user actually wanted performs this testing.
With prototyping techniques, this stage becomes very much a formality to check the accuracy
and completeness of processing. The screen layouts and output should already have been
tested during the prototyping phase.

An error in the program code can remain undetected indefinitely. To prevent this from
happening the code was tested at various levels. To successfully test a system, each
condition, and combinations of conditions had to be tested. Each program was tested
and linked to other programs. This unit of program is tested and linked to other units and
so on until the complete system has been tested.

The purpose of testing is to ensure that each program is fully tested. To do so a test plan
had to be created. The test plan consists of a number of test runs such as the valid paths
through the code, and the exception and error handling paths. For each test run there is a
list of conditions tested, the test data used and the result expected. The test plan was then
reviewed to check that each path through the code is tested correctly. It is the
responsibility of the programmer to collect the data that will produce the required test
condition.

VERIFICATION AND VALIDATION (V&V):

58
The objectives of verification, validity activities are to assess and improve the quality of
the work products generated during development and modification of the software.
Quality depends upon the various attributes like correctness, completeness, consistency,
reliability, usefulness, usability, efficiency and conformance to standards.

The terms verification and validation are used synonymously. These are defined as
under: -
Verification: “Are we building the product right?”
Validation: “Are we building the right product?”

Verification activities include proving, testing, and reviews. Validation is the process of
evaluating software at the end of the software development to ensure compliance with the
software requirements. Testing is a common method of validation. Clearly, for high
reliability we need to perform both activities. Together, they are often called V&V
activities.

The major V&V activities for software development are inspection, reviews, and testing
(both static and dynamic). The V&V plan identifies the different V&V tasks for the
different phases and specifies how these tasks contribute to the project V&V goals. The
methods to be used for performing these V&V activities, the responsibilities and
milestones for each of these activities, inputs and outputs for each V&V task, and criteria
for evaluating the outputs are also specified.

The two major V&V approaches are testing and inspections. Testing is an activity that
can be generally performed only on code. It is an important activity and is discussed in
detail in a later chapter. Inspection is a more general activity that can be applied to any
work product, including code. Many of the V&V tasks are such that for them, an
inspection type of activity is the only possible way to perform the tasks (e.g. trace ability
and document evaluation). Due to this, inspections play a significant role in verification.

59
6: SYSTEM IMPLEMENTATION

System Implementation Maintenance and Review

As we know, creating software is one thing and the implementation of the created
software is another. The process of implementing software is much difficult as compared
to the task of creating the project. First we have to implement the software on a small
scale for removing the bugs and other errors in the project and after removing them we
can implement the software on a large scale. Before we think in terms of implementing
the Software on a large basis, we must consider the Hardware requirements.

Whenever we develop software or project a certain hardware and software is being used
by the programmer for developing the project. The hardware and software to be used by
the programmer for developing the project should be such that it would result in the
development of a project, which would satisfy all the basic needs for which the project
has been created by the programmer. The Hardware should be such that cost constraints
of the Client should also be taken into account without affecting the performance.

HARDWARE EVALUATION FACTORS:

When we evaluate computer hardware, we should first investigate specific physical and
performance characteristics for each hardware component to be acquired. These specific
questions must be answered concerning many important factors. These hardware evaluation
factors questions are summarized in the below figure.

Notice that there is much more to evaluating hardware than determining the fastest and
cheapest computing device. For e.g. the question of possible obsolescence must be addressed
by making a technology evaluation. The factor of ergonomics is also very important.
Ergonomics is the science and technology that tries to ensure that computers and other
technologies are "user-friendly", that is safe, comfortable and easy to use. Connectivity is

60
another important evaluation factor, since so many computer systems are now interconnected
within wide area or local area telecommunications networks.

HARDWARE EVALUATION FACTORS:

1) Performance
2) Cost
3) Reliability
4) Availability
5) Compatibility
6) Modularity
7) Technology
8) Ergonomics
9) Connectivity
10)Environmental requirements
11)Software
12)Support

SOFTWARE EVALUATION FACTORS:

Software can be evaluated according to many factors similar to the hardware

evaluation. Thus the factors of performance, cost, reliability, compatibility, modularity,
technology, ergonomics, and support should be used to evaluate proposed software
acquisitions. In addition, however, the software evaluation factors are summarized in
below figure. For e.g. some software packages require too much memory capacity and
are notoriously slow, hard to use, or poorly documented. They are not a good selection
for most end users, even if offered at attractive prices.

1) Efficiency: is the software a well-written system of computer instructions that does

not use much memory capacity or CPU time?

61
2) Flexibility: can it handle its processing assignments easily without major
modifications?
3) Security: does it provide control procedures for errors, malfunctions and improper use?
4) Language: do our computer programmers and users write it in a programming
language that is used?
5) Documentation: is the s/w well documented? Does it include helpful user instructions?
6) Hardware: does existing hardware have the features required to best use this software?
7) Other characteristics of hardware such as its performance, what about the cost, how
much is reliable and etc.

SECURITY MEASURES

Security Performed In HOSPITALManagement System

User Name & Password security implemented so that no unauthorised person
can handle any operation without username and Password.
 Only authorized person can log-on the system.
 Only authorized person can update the records.
 Only authorized person can handle the reservation.

It has two kinds of users:

1. Administrator
2. User1
Administrator: He has complete authority (Read, Add, Modify) of operating the
software. The User Name and Password provided to the Administrator in this project is:

User Id: Admin

Password: admin123

FURTHER SCOPE OF THE APPLICATION

62
1. Though maximum efforts have been put in to make this report authentic in all aspects
and to take all necessary presentation to ensure that the information gathered is true,
some uncomfortable factors may have crept in.
2. Some of the respondents were reluctant to part with certain information on the pretext
of the sensitivity of the information. Also some facts of figures were not divulged as
the company policy came in the way for free revelation of the desired input.
3. An element of bias might have crept in from the side of the official interviewed. This
could also have resulted in some kind of modification of the information divulged.
4. Through an attempt was make to collect information from the
best possible source in the company, it was difficult to meet the top officials due to
their busy schedules.
5. Most of the analysis and interpretations, made for this report, are based on secondary
data obtained. This data could have some inherent mistakes and errors.
6. Finally, although due care has been taken those can be typing and compilation errors
in the report itself.
The tasks specified were not well defined because nothing was mentioned regarding
validations in the project. Though we gave maximum effort to check the software with
different validation tests, a few of them might be present in this version.

 Due to limited time available survey could not be undertaken for intended 20
consumers and thus had to be limited to 10.
 Communication gaps exist between employees and management, as seniors don't
share problem with subordinates resulting in violation of psychological contract.
 Poor rewarding system(slow)
 Poor working conditions

The limitations may be many and the magnitude of the influence of these limiting factors
may have a bearing on the report, but it in no way alters the ultimate aim of the project

63
and because it's highly USER FRIENDLY, it would be the choice of all kinds of
personnel.

CONCLUSIONS

This project has been a rewarding experience in more than one way. The entire project
work has enlightened us in the following areas.

a) We have gained an insight into the working of the HOSPITAL. This represents a
typical real world situation.

b) Our understanding of database design has been strengthened this is because in

order to generate the final reports of database designing has to be properly followed.

c) Scheduling a project and adhering to that schedule creates a strong sense of time
management.

d) Sense of teamwork has developed and confidence of handling real life project
has increased to a great extent.

e) Initially, there were problem with the validation but with discussions, we were
to implement validations.

BIBLIOGRAPHY

[1] Herbert Scheldt, PHP Complete Reference, Fifth Edition, Tata McGraw Hill Edition.

[2] Phil Hanna, Java script: The Complete Reference, Tata McGraw Hill Edition, 2003.

64
[3] Elmarsi and Navathe, Fundamentals of Database System (Third Edition), Addision
Wesley.

[4] Ian Somerville, Software Engineering, Third Edition, Pearson Education.

[5] Ali Bahrami, Object-Oriented System Development, Third Edition, Tata McGraw
Hill Edition.

[6] Ivan Bayross, SQL, programming language , Second Edition, BPB Publication.

WEB REFERENCES

[1] www.google.com
[2] www.htmlcodetutorial.com

65