A

Project Report
on
TIME TABLE MANAGEMENT

Submitted in
Partial fulfillment of award of
Degree of
Bachelor of Technology
In
Computer Engineering
From
Rajasthan Technical University, Kota
SUBMITTED BY
NEHA GUPTA (08EGJCS037)
VERSHA GUPTA (08EGJCS063)
Under the Guidance of
Mr. AMIT BHORA

DEPARTMENT OF COMPUTER ENGINEERING

GLOBAL INSTITUTE OF TECHNOLOGY, JAIPUR
[2010 – 2011]
 GLOBAL INSTITUTE OF TECHNOLOGY, JAIPUR
(Department Of Computer Science)

CERTIFICATE

This is to certify that the project entitled “COLLEGE TIME TABLE MANAGEMENT” has
been carried out by the under mentioned students under my guidance in partial fulfillment of
the degree of Bachelor of Technology in Computer Engineering of Rajasthan Technical
University, KOTA during the academic year 2010-2011 .

Team:

NEHA GUPTA
VERSHA GUPTA

Date: 3 January 2011

Place: Jaipur

Mr. Amit Bhora Prakash Ramani

Lecturer, CS&IT Department HOD, Computer Engineering and IT
 GLOBAL INSTITUTE OF TECHNOLOGY, JAIPUR
(Department of Computer Science)

ACKNOWLEDGEMENT

This is to thank and express my gratitude to Computer Science Department, for giving us an
opportunity to pursue and successfully complete our project.

Deepest and Sincere gratitude to our in-charge Mr. Amit Bhora for the countless patience and
guidance, without him successful completion of the target project would not have been
possible.

We would like to express our special gratitude to Mr. Prakash Ramani (H.O.D of Comp
Science dept. GIT college), Mr. Amit Bhora for their kind guidance, assistance and efforts in
the project.

We were thanks to all the teachers of Computer Science Department for their cooperation in
our project.

NEHA GUPTA
VERSHA GUPTA
 PAGE INDEX
S. No. TOPIC PAGE NO.
Abstract 1
1. Introduction 2
1.1. Need for the new system 2
1.2. Detailed problem definition 2
1.3. Project scope 3
1.4. Presently available system 3
for the same
1.5. Future prospects 4
1.6. Organization of the report 4
2. Analysis 6
2.1. Project plan 6
2.1.1. Task Identification plan 6
2.2. Feasibility study 7
2.2.1. Technical feasibility 8
2.2.2. Financial feasibility 8
2.3. Team Structure 9
3. Design 10
3.1 Software Requirement 10
Specification
3.1.1 Introduction 10
3.1.1.1 Purpose 10
3.1.1.2 Scope 10
3.1.1.3 Definitions, Acronyms and 11
Abbreviations:-
3.1.1.4 References 12
3.1.1.5 Overview 12
3.1.2 Overall Description 12
3.1.2.1 Product Perspective 12
3.1.2.2 Product Function: 14
3.1.2.3 User Characteristics 14
3.1.2.4 Principal Actor 14
3.1.2.5 General Constraints 14
3.1.3 Specific Requirements 15
3.1.3.1 Functional Requirement 15
3.1.3.2 Design Constraints 20
3.1.4 Future Extensions 20
3.2. Risk analysis 21
3.2.1. Performance risk 21
3.2.2. Schedule risk 21
3.3. UML Diagram 21
3.3.1. Use-Case Diagram 21
3.3.2. Activity Diagram 22
3.3.3 Sequence Diagram 31
3.3.4. DFD 32
 4 Coding 33
4.1 Coding Style Followed 33
5 Testing 34
5.1. Test plan 34
5.2. Test case and test result 36
6. Limitation and Scope 46
7. Snapshots 47
8. Conclusion 58
Bibliography 56
Table Index
Figure index
 ABSTRACT

College time table management system is a website which is developed for the global
institute of technology using PHP language and MySQL. This website is basically deals with
the automatic generation of the college time table for different branches and semesters. This
website can also be used by other colleges also.
First of all, any college who wants to use this website has to register themselves. The user can
login by entering the email id and password.
After login, the various forms are provided related to the college, teachers, branches and the
subject. Then they have filled all the entries related to the college, no of the shifts, timing of
every shift, how many departments are there etc.
Now all the entries related to the branches is filled like name of the branch, how many
subject, subject details and the professor details etc.
All the relevant data will be filled related to the labs, library and sports period.
After filling all the details, the automatic time table will be generated. After that the user will
print the table on clicking the print button.

The hardware requirements of our project are –

 Processor: Pentium II
 Hard disk space: 2GB(required) or more
 Memory: 64 MB RAM

The software requirements of our projects are –

 Tool: Dreamweaver and Notepad++

 Server: Xampp Server
 Database: MySql
 Language: PHP,CSS and HTML
 CHAPTER 1
1. INTRODUCTION
This defines the project being developed along with the description of existing systems of
similar type. Here the need for the new system, its future prospects and currently available
systems of similar types have been defined which therefore presents a brief overview of the
system being developed in terms of its differences with the previously available systems and
the newly embedded functionalities.

1.1 Need for the new system

Time table is a very important part of the college management system. It helps the college
management to maintain the discipline in the college premises. The time table creation is a
very old process in the college management. Till now, it is done manually. The college
management assigns one teacher for this purpose and his job is to create time table manually
for each branch of every semester.
As there are so many subject in each branch and there might be a case when same
professor will teaches different subjects in one semester. There might be case when some
collision will occur during assign the lectures manually. Also, the manual assignment of the
lectures is a very tedious and long process work.
In the existing system, the problem occurs when any teacher is on the leave and he will not
able to inform or inform it late than the manual assignment of substitute teacher is also a very
difficult job.
When the time table is generated manually, there is a case when the department head want
to makes some changes in the lectures. At this situation, the chances of the collision of the
period or assignment of the teachers will increase because it is not possible for one teacher to
remember all assignment done earlier. So the chance of the mistake will increase. These are
some of the mistakes which occur during developing the time table manually. The manual
maintenance of the databases of items, time table processing is a time taking process and
somehow erroneous. So there is a need for the new system to resolve such problems.
In our college time table management system we are trying to solve these problems and
along with that we try to provide the user friendly and efficient way to generate the time table
automatically. Our project is a web based system in which user has to fill some form related
to the college, subjects, labs, teachers and the branch and than our system will generate the
most possible time table.
1.2 Detailed Problem Definition
Our basic function is to create a time table for a college including different branches and
semester. The main problem that occurred during the project is to create and maintain the
databases of different entities involved in this process. The database contains the information
about the various semesters, subjects, lab, teachers etc. So maintain such a large database is a
big challenge for us. The problem we face during our project is how the collision of two
subjects or the teachers can avoid. Every project has some drawbacks. There is a chance
when the collision will occur when we generate more time tables for different branches. So,
these are some problem which we face in our project.

1.3 Project scope

The objective of the project is to create a web based time table management system to be
used by any college but basically it is created according to the needs of our college, Global
Institute of Technology. Its main is to perform the basic requirements of the college and to
maintain the databases of subjects, branches, semesters more efficiently.
As it is a web based system, the maintenance and working is somehow difficult from the
manual mode of approach. Till now, the time table making process is manual work. So
because of this the teacher has some difficulty to work on this.
They have to first login through their email id and then they have to fill all the details then
time table will be generated. But we have tried hard to make this system very user friendly
and easy to understand.
As this is web based project, it is easier to fetch the data from the database and remove the
unwanted data by just clicking the delete button. This project will limit the time and money
factor involve in the time table management system.
The maintenance of this web based is much easier and accurate than the existing manual
system. As this web based system, the security features are somehow higher than the manual
system.
In this system, there is less chance of mishandling of the data because only the
administrator will login through their login id and password and upload all the related data
and generate the time table. So there is no misuse of the data.
1.4 Presently Available Systems for the same
The time table management system is a very old process. In every schools and colleges, the
generation of the time table is required. Till now, all the processes are manually done in most
of the colleges because no one wants to spend the money on such process. Some time table
management system are available but some cost are charged for using them. The existing
systems are not user friendly because they require lots of data to generate. It is very hard to
handle the database in the presently available system because it is computer based
applications. In the existing system there is no option of the printing of the time table and also
there are no criteria of the leave management. There is no web based time table management
system available till now. So, all the features of the wed based applications are missing.
Security is main factor for any application. In the presently available system, the security
level is very low because there is no criterion of login id and password. Database
management is also very difficult in the desktop based application. To use this application the
expert is requires. In our system we have tried to solve all these problems.

1.5 Future Prospects

Many special features which we have not included now in our project will likely to be added
in the near future.
In our project, there is only administrator panel where the admin will upload all the data
related to the college, teachers, branches, subjects and labs.
Now in the future extension, we will assign the login id and password to all the teachers so
that they can be able to see their schedule and print the time table.
In the future, we also give the facility of the leave management. In the leave management
criteria, any teacher who wants to take the leave will inform the administrator by sending the
mail and then administrator will assign the lecture to another teacher by sending the mail and
by sending sms to the cell phone.
In the future, we will also give the facility of changing any lectures manually. It means if
anyone wants to exchange their lectures which are automatic generated by the system, then
he can able to change it manually. The will also give the alert if any collision will occur with
any other subject of the other branch. So these are some future prospects of our project which
we are going to implement later.
1.6 Organization of the Report

The organization of project report has been done in the form of chapters, each discussing
various aspects of project. The details of the chapters are given below:
 Chapter 1deals with the Project Introduction part that contrasts the need and scope for
the new system that is being designed. Also, Problem Definition has been discussed to
throw some light on the problem that the project is intended to solve. Finally, Future
prospect of the system is given.
 Chapter 2 deals with the Project Analysis part that consists of detailed information about
the various kinds of studies done for project feasibility. Starting with the Project plan,
then Feasibility study that say that the new system will prove feasible both technically
and financially. Then, Software Requirement Specification (SRS) is provided.
 Chapter 3 deals with the Project Design part that covers the design phase of the project
including details and diagrams about Database, Classes, etc. Various UML diagrams are
included like Activity diagrams, Use Case diagram and Data Flow Diagrams (DFD).
Also, Risk Analysis has been done to overall safeguard the design phase of the project.
 Chapter 4 deals with the Coding part of the project that consists of coding standard &
style followed in coding of the new system. Also, an abstract sample of project code is
also given.
 Chapter 5 deals with the Project Testing part that discusses first, the test plan carried out
in the testing phase of the project followed by the detailed test cases & results of various
modules of the system. The test cases and results are given in tabular form such that
interpretation of them comes out to be an easy task and confusion free.
 Chapter 6 deals with the Project Scope & its limitations part that tells the various
limitations/shortcomings of the system and considers its current scope. Also, it provides a
probable solution for overcoming the limitations.
 Finally, in the end Project Snapshots are provided that provides reader a practical
overview of the system and its working. After that, Conclusion, Bibliography,
&Appendices are been given.
 CHAPTER 2

2. ANALYSIS

2.1 Project Plan

It is a formal, approved document used to guide both project execution and project control.
The primary uses of the project plan are to document planning assumptions and decisions,
facilitate communication among stakeholders, and document approved scope, cost, and
schedule baselines.
The Project Plan is a relatively brief document that is addressed to a diverse audience. It
must communicate scope and resources to software management, technical staff, and the
customer. It defines risks and suggests risk aversion techniques. Also define cost and
schedule for management review. It provides an overall approach to software development
for all people associated with the project and outline how quality will be ensured and change
will be managed.
For our college time table project the project plan phase comprises of the identification of
different tasks.

2.1.1 Task Identification Plan

All the work needed to perform the project is analyzed and organized. The problem and value
proposition addressed by the project is described. Task performed to complete the work is
divided in the group of five, where each individual has to perform their own task and later we
have integrated the all the task. The timeline of the project is also decided from the
beginning.
It comprises of different modules of our project. Each module determines the following
task respectively as follows:-
Module I: Registration
Fill all the entries such as email id, password, phone no and address. Then, after filling all
the details correctly and press the submit button. All the entries stored in the database
Module II: Insertion of Details
 College details

 Teacher details
  Subjects, labs, seminar, project lab details

 Branch and shift details

Module III: Change password

Here, the user can change his password by entering the email id, old password and new
password. After filling the details, changes will be done in database.
Module IV: Time Table generation
After filling all the details, the time table will be generated.
Module V: Print Time Table
The time table can be printed directly from the website.

2.2 Feasibility study

The assessment is based on an outline design of system requirements in terms of Input,
Processes, Output, Fields, Programs, and Procedures. This can be quantified in terms of
volumes of data, trends, frequency of updating, etc. in order to estimate whether the new
system will perform adequately or not.
Due to the advent of various time table management systems, we need to analyze the
efficiency of user in implementing and using these functionalities. So a new time table
management system is developed which is feasible in all respect which would be time saving
and beneficial to the user.
We need to analyze the proposed system for its feasibilities. During the preliminary stage
of designing the system, the feasibility study for the system was undertaken and it was found
that the system was technically, financially and operationally feasible in nature. The
feasibility study can be categorized into:

2.2.1 Technical Feasibility

The technical issues usually raised during the feasibility stage of the investigation include the
following- Does the necessary technology exist to do what is suggested, Will the proposed
system provide the adequate response to the inquires and perform all the expected functions,
Can the system be upgraded if it is developed more in later and are they have technical
guaranty of accuracy, reliability, ease of access and data security.
The current system developed is very much technically feasible. It is web based systems
which provide the easy access to the users. The purpose of the database is to create, establish
and maintain a workflow among different entities like teachers, subjects and labs. Permission
to the users would be granted based on the roles specified. Therefore, it provides the technical
guarantee of accuracy, reliability and security.
The software and hardware requirement for the development of this project are not many
and they are available as free as open source. The work for this project is done with current
and existing web designing technology as PHP, MySql and tools like Dreamweaver. At the
user end, the need of good web browser that supports PHP5 and the fast internet connection
is required.

2.2.2 Operational Feasibility

Any system is beneficial if they can be turned out into information system. This will helps in
meeting the operating requirements of the organization. Operational feasibility aspects of the
project are to be taken as an important part of the project implementation.
Some of the important issues raised are to test the operational feasibility of a project
includes the following- Is there is sufficient support of the management from the users, will
the system be used and work properly if it is being developed and implemented and will there
be any resistance from the user that will undermine the possible application benefits.
Our system “college time table management” is in accordance with the above mentioned
issues. Beforehand, the management issues and user requirements have been taken into
consideration. So there is no question of resistance from the users that can undermine the
possible application benefits.
The well planned design will ensure the user for the optimal utilization of the computer
resources and will help in the improvement of performance status. Our system follows all the
standards given above. So, our system is operational feasible.

2.2.3 Financial Feasibility

A system can be developed technically and that can be used if installed but it will be
beneficial for the organization when it is financial feasible.
In the economic feasibility, the development cost in creating the system is evaluated
against the ultimate benefit derived from the new systems. Economical benefits must equal or
exceed the costs. Our system is economical feasible.
Our project does not need any high cost software and hardware. As our system is an online
based system. So the user needs only user friendly web browser and the high speed internet
and he should have good knowledge about how to use the internet services. There is a normal
expenditure and economic feasibility on the project.
This module is financially feasible because we are using existing tools and software to
develop it. We do not need to buy any other software. We are going to use following tools
and software.
 Dreamweaver and Notepad++
 Xampp Server
 Web browser-Google Chrome

2.3 Team Structure

The project team is consists of two members:-
 Neha Gupta
 Versha Gupta
 CHAPTER 3

3. DESIGN
The design of the project specifies the overall implementation of the project in terms of
Software Requirement Specification, UML diagrams, Sequence Diagrams, Activity
Diagrams. All these specify the overall functionality of the system which is being developed.

3.1 Software Requirement Specification

3.1.1 Introduction
3.1.1.1 Purpose

The purpose of this document is to present a detailed description of the Web based “college

time table management system”. It will explain the purpose and features of the system, the

interfaces of the system, what the system will do, the constraints under which it must operate

and how the system will react to external stimuli. The document also describes the

nonfunctional requirements such as the user interfaces. It also describes the design constraints

that are to be considered when the system is to be designed, and other factors necessary to

provide a complete and comprehensive description of the requirements for the software. The

software requirement specification captures the complete software requirements for the

system, or a portion of the system. Requirements described in this document are derived from

the vision document prepared for timetable management system.

3.1.1.2 Scope

It describes the scope of the software application to be produced. The description identifies

the software product; describe its functionality and application of the software. It includes the

description of the benefits, objectives and goals of the software. The scope of the system is to

generate time table for different branches according to the data entered. Forms are filled

according to the data. If anyone wants to view teacher load then also he can able to see. If the

user wants to print then also he can do.

3.1.1.3 Definations, Acronyms and Abbreviations

HTML: - Hyper Text Markup Language

CSS: - Cascading style sheet

PHP: - Hypertext Preprocessor

3.1.1.4 References
 Core PHP programming, Pearson edition
 Internet
 www.w3school.com

3.1.1.5 Overview

SRS will include two sections:

 Overall Description will describe major components of the system, interconnection
and external interfaces.
 Specific Requirements will describe the functions of actors, their role in the system
and constraints.

3.1.2Overall Description
Describe the general factors that affect the product and its requirements.

3.1.2.1Product Perspective

The whole document contains the following in the mentioned order:

 The user will login through their login id and password otherwise he will register

himself.

 The user fill all the details related to college, subjects and teacher.

 The user can see the teacher load and subject load.

 The user can change its password after login through their email id and old password.

 Time table generates according to the semester and branch.

 The user can print the time table.

3.1.2.2Product Function:

Print button Refer to the page where user will print the
time table

Reset Available information is reset.

Login Login through email id and password

Submit To submit the form

Print option To print the time table.

Log out Sign out from the user account

Table 3.1 Product Function

3.1.2.3User Characteristics

Head of Department or person appointed by H.O.D can do the work of Administrator.

The features that are available to the Administrator are:

 Administrator has a unique login id and password.

 Can insert the data related to the subjects, teachers, labs and the college.

 Can generate the time table according to the data entered.

 Can print the time table according to the branch and semester.

 Can see the schedule of any branch.

There is only one user i.e. Administrator. He should has

 Basic Experience with database administrator

 Basic background knowledge about the appointment of Faculties.

 Basic knowledge about the subject and the teacher who teaches these subjects.
3.1.2.4System assumptions, dependencies and constraints

 Assumptions

It describes the assumptions made that can affect the requirements of the SRS. The

assumption we made during our project is that the user has the good knowledge of the

database and he can do the work online. The internet speed at user side should be very

fast so that work will be done properly. All the software that are necessary for the

system should be installed at user computer.

 Dependencies

It describes each dependency that can affect the requirements specified in the SRS.

Our system only depends on the high speed connection of the internet. The latest

version of Web browser such as Mozilla Firefox, Google chrome should be available.

 Constraints

It describes the factors that limit the scope and functionality of the software. As our

project, is a web based system so its main requirement is the high speed internet

connection and latest version of the web browser that supports PHP5.

3.1.3 Specific Requirements

3.1.3.1 Functional Requirement

We describe the functional requirements by giving various use case:

1) Name of the Use Case: Home Window

Description: when user opens the website he will be provided with the home window.
Pre Conditions: Nil
Normal Flow of event:
 The user is required to open the website
 As per the user click home window shown.
 Alternative Flow of the event: Nil
2) Name of the Use Case: Registration

Description: the user can registered them to use the website

Pre Conditions: Nil
Normal Flow of event:
 The user is required to open the registration page.
 Fill all the details and then click on the submit button.
 Alternative Flow of the event: Nil

3) Name of the Use Case: Login

Description: the user can login through their login id and password
Pre Conditions: email id and password should be correct
Normal Flow of event:
 The user enters login id and password
 Press the submit button and user account will open.
 Alternative Flow of the event: Nil

4) Name of the Use Case: insertion of details

Description: All the details related to the subject, lab, college, teachers will be entered
Pre Conditions: Nil
Normal Flow of event:
 Fill the data in the related forms
 Submit the forms and database will update.
 Alternative Flow of the event: Nil

5) Name of the Use Case: Change Password

Description: User can change his password

Pre Conditions: Email id and old password should be correct
Normal Flow of event:
 The user is required to open change password page
 Enter the email id, old password and new password and submit the form.
 Alternative Flow of the event: Nil
6) Name of the Use Case: Generate the time table

Description: time table will be generated

Pre Conditions: all the detail should be filled
Normal Flow of event:
 After filling all the data, the time table will be generated.
 Alternative Flow of the event: Nil

7) Name of the Use Case: Print the time table

Description: user can print the time table

Pre Conditions: Nil
Normal Flow of event:
 The user is required to click on the print option
 Print out will come if the system is connected to the printer.
 Alternative Flow of the event: Nil

8) Name of the Use Case: Logout

Description: you can easily close your account .We can close the window by click
on the logout button.
Pre Conditions: Nil
Normal Flow of event:
 The user is required to close the window if he do not want to work on it..

Alternative Flow of the event: Nil.

9) Name of the Use Case: Reset

Description: The user can reset all values by clicking on reset button.
Pre Conditions: The window in which user provides input must be opened.
Normal Flow of event:
 The user is required to perform the reset operation if he wants.

Alternative Flow of the event: Nil.

3.1.3.2Design Constraints
 Usability: The system college time table website is worked should have the minimum
hardware requirements.
 Security: The project should be secure enough so that there should not be any mishandling.

3.1.4 Future Extensions

 The leave management system will be added.
 Manual changes can be done.
 Faculties will be provided with their login id and password so that they can view their time
table.

3.2 Database design

Table 1: Branch Detail

Description: this table is for maintaining the available branch

Column Name Data Type Null able Default Primary Key

branch_id number no - 1

branch_name Varchar yes - -

Col_id Varchar yes - -

Table 2: College Details

Description: this table is for maintaining the available colleges.

Column Name Data type Null able Default Primary Key

col_id Number No - 1

Col_name Varchar No - -

address Varchar No - -

phone_no Varchar No - -

work_day Number No - -

lecture_day Number No - -

span_day Number No - -

shift Number No - -

login_id Number No - -
Table 3: distribute teacher

Description: this table maintains the details how subjects are distributed among teachers.

Column Name Data type Null able Default Primary Key

Dist_id Number No - 1

Seminar_id Number Yes - -

Project_id Number Yes - -

Lab_id Number Yes - -

Subject_id Number No - -

Teacher_id Number no - -
Table 4: Login table

Description: This table maintains the login details.

Column Name Data type Null able Default Primary Key

Login_id Number No - 1
Mailed Varchar No - -
Password Varchar No - -
Phoneno Number No - -
addres varchar no - -

Table 5: Semester detail

Description: this table maintains the record of semester

Column Name Data type Null able Default Primary Key

Sem_id Number No - 1
Shift_name Number No - -
Which_sem Number No - -
Branch_name Varchar No - -
College_time Time No - -
After_break Number No - -
Col_id number no - -
Table 6: Subject details
Description: this table is for maintaining the subject details

Column Name Data type Null able Default Primary Key

Subject_id Number No - 1
Branch_name Varchar No - -
Subject_name Varchar No - -
Col_id Number No - -
Subject_load Number No - -
Table 7: Teacher details
Description: this table is for maintaining the teacher detail

Column Name Data type Null able Default Primary Key

Teacher_id Number No - 1
Name Varchar No - -
Type Varchar No - -
Mail_id Varchar No - -
Address Varchar No - -
Phoneno Number No - -
Degree Text No - -
Col_id Number No - -
count number No - -
3.3 Risk Analysis

A risk analysis involves identifying the most probable threats to an organization and

analyzing the related vulnerabilities of the organization to these threats. A risk assessment

involves evaluating existing physical and environmental security and controls, and assessing

their adequacy relative to the potential threats of the organization.

3.2.1 Performance Risk

The performance of the College Time Table Management system is based on implementing
various functionalities web based system. The performance risk associated with them is
analyzed.

3.2.2 Schedule Risk

It is the exposure to loss from a program not meeting its scheduled objectives. Level of
maintenance that requires planning, allocation of significant

3.3UML Diagram

3.3.1USE CASE Diagram

A use case diagram in the Unified Modeling Language (UML) is a type of behavioral
diagram defined by and created from a Use-case analysis. Its purpose is to present a graphical
overview of the functionality provided by a system in terms of actors, their goals (represented
as use cases), and any dependencies between those use cases.
Use Case Diagram 1

Actor: Administrator

Object: 1. Maintain Login Id and Password

2. Maintain Database

3. Maintain College Details

Use Case Diagram 2

Actor: Head of Department

Object: 1. Insert all details related to college, subject, labs and teachers.

2. Generate the time table.

3. Print Time Table according to branch.

3.3.2Activity Diagram

Activity diagrams are graphical representations of workflows of stepwise activities and

actions with support for choice, iteration and concurrency. An activity diagram shows the
overall flow of control.
Activity Diagram 1:

Validation of login Id and password

Activity Diagram 2:

Insertion of Details
Activity Diagram 3:

View the details and maintain teacher loads

Activity Diagram 4:

Generation of time table and you can take the print out
Activity Diagram 5:

Forgot password
Activity Diagram 6:

Change old password

3.3.3Data Flow Diagram

Level 0

College Time
Table
Administrator Database
Management
 Level 1

Administrator
Database

Admin
Administrator Login College
Validation Time Table
Login Id System
and
Password

Faculty
Details

Subjects
Detail

Faculty database

Subject Database
Level 2

New faculty Faculty database

Login Time table

Faculty or id management
User validation
HOD system
Passwo
rd

User area either

HOD or faculty
 CHAPTER 4

4. CODING
It describes the technology used for front end coding and the various features of coding
language used.

4.1 Coding Style Followed

For the development of this college time table management system the entire coding has been
done in PHP and HTML.

PHP and HTML has the following features:

 HTML used for designing of the web pages

 CSS is used for providing style to the web pages.
 Security
 Good performance
 Session declared for the security
 Validation is done by java script

In PHP, the coding is done along with HTML coding and CSS for the styling of the web
pages.
 CHAPTER 5
5. TESTING

Here various test plans and cases are described used in the testing of different modules and
the overall system.

5.1 Test Plan

A test plan is a procedure used to schematically analyze and find the shortcomings or
mistakes, if any, in a technical system or product. Through experimental runs of the unit, this
process is used to make sure that the unit can function to full capacity, both effectively and
efficiently, once it is in full operation. Therefore, the test plan clearly states how the unit or
the unit or system will be tested, what aspects of it will be tested, who will perform the tests,
where and for how long the testing will occur and the overall effectiveness of such testing.
Software Testing is an empirical investigation conducted to provide stakeholders with
information about the quality of the product or service under test, with respect to the context
in which it is intended to operate. Software Testing also provides an objective, independent
view of the software to allow the business to appreciate and understand the risks at
implementation of the software. Test techniques include, but are not limited to, the process of
executing a program or application with the intent of finding software bugs. It can also be
stated as the process of validating and verifying that a software program/application/product
meets the business and technical requirements that guided its design and development, so that
it works as expected and can be implemented with the same characteristics.
Software Testing is performed for each and every possible test case in our entire
project for checking the expected validations and correctness of flow of control from one
page to another as requirement of user.
Software Testing, depending on the testing method employed, can be implemented at
any time in the development process, however the most test effort is employed after the
requirements have been defined and coding process has been complete.
Testing can never completely identify all the defects within software. Instead, it
furnishes a criticism or comparison that compares the state and behavior of the product
against oracles—principles or mechanisms by which someone might recognize a problem.
These oracles may include (but are not limited to) specifications, contracts, comparable
Products, past versions of the same product, inferences about intended or expected purpose,
user or customer expectations, relevant standards, applicable laws, or other criteria.
Every software product has a target audience. For example, the audience for video
game software is completely different from banking software. Therefore, when an
organization develops or otherwise invests in a software product, it can assess whether the
software product will be acceptable to its end users, its target audience, its purchasers, and
other stakeholders, Software testing is the process of attempting to make this assessment.
A primary purpose for testing is to detect software failures so that defects may be uncovered
and corrected. This is a non-trivial pursuit. Testing cannot establish that a product functions
properly under all conditions but can only establish that it does not function properly under
specific conditions. The scope of software testing often includes examination of code as well
as execution of that code in various environments and conditions as well as examining the
aspects of code: does it do what it is supposed to do and do what it needs to do. In the current
culture of software development, a testing organization may be separate from the
development team. There are various roles for testing team members. Information derived
from software testing may be used to correct the process by which software is developed.

Types of Testing:
Black box testing- Internal system design is not considered in this type of testing. Tests are
based on requirements and functionality.

White box testing- This testing is based on knowledge of the internal logic of an
application’s code. Also known as Glass box Testing. Internal software and code working
should be known for this type of testing. Tests are based on coverage of code statements,
branches, paths, conditions.

Unit testing- Testing of individual software components or modules. Typically done by the
programmer and not by testers, as it requires detailed knowledge of the internal program
design and code may require developing test drive modules or test harnesses.

Incremental integration tests- Bottom up approach for testing that is continuous testing of
an application as new functionality is added; Application functionality and modules should be
independent enough to test separately done by programmers or by testers.
 Integration testing- Testing of integrated modules to verify combined functionality after
integration. Modules are typically code modules, individual applications, client and server
applications on a network, etc. This type of testing is especially relevant to client/server and
distributed systems.
5.2 Test Cases and Test Results

Test Test Test Test steps Test Test Test Defect

case case desc Step expected Actual case status prio- severit
id name status (P/F) rity -y

CTT01 Validat To verify Fill the If all the Coding P High High
e that form details
“Regist registrati which are filled
ration” on is has and
option. done fields email id
properly like is correct
or not email id, and not
passwor registere
d, retype d earlier
passwor then
d, phone form will
no and be
address submitte
d
CTT02 Validat To verify Enter If the Coding P High High
e that the login email id
“Login whether id and and
page” the login passwor password
id and d and is correct
password press the (if
is correct submit already
button registere
d) then
form will
be
submitte
d
CTT03 Validat To verify Enter If email Coding P High High
e that the login id and
“chang option is id, old old
e working passwor password
passwo correctly d and is correct
rd” new and also
option passwor fill new
d password
then
submit it
CTT04 Validat To verify Fill all If the Coding P Low Low
e that the user
“colleg option is details filled all
e entered related the
details or not to the mandator
college y details
and all then
fields form will
are submit
mandato
ry
CTT05 Validat To verify Select If all the Coding P High High
e that “Submit details
“Submi option is button” filled
t” working and then
button correctly check all submit
for when the button
each opened details works
form are filled properly
CTT06 Validat To verify If the After Coding P High High
e that user clicking
“logout “logout” wants to on logout
” option is logout button,
button working from his the user
correctly account. will sign
out and if
he clicks
on back
button he
will not
move to
his
account
directly.
CTT07 Validat To verify Reset all All the Coding P Med. Med.
e that the text text
“Reset” “reset” fields. fields are
button option is blank
working after
correctly reset
button is
clicked
CTT08 Validat To verify Fill all If the Coding P High High
e that the details
“subjec various details are filled
ts, form are and properly
teacher, working submit then
Labs, correctly the form form will
seminar submit
detail
CTT09 Validat To verify Executio Executio Coding P High High
e that n time is n time is
“genera option entered entered
te time when from properly
table closed is respecti for all
option working ve text the tasks.
correctly boxes.
CTT10 Validat To verify If the If printer Coding P High High
e that user is
“print option is click on attached
option working the print then the
correctly button time
when the table will
opened “print print.
dialog
“box
will
open
Table 5.1 Test Cases and Test Results
 CHAPTER 6
6. LIMITATIONS AND SCOPE

The limitations of our college time table management system are

 Faculty cannot able to see their own time table.
 Leave management process is not available.
 Manual changes in the time table is not allowed
 Subject load cannot exceed the number of working days.
 There is no option to find the availability of free faculties.
 Facility to send mail or sms when any teacher is on the leave is not available.

The scope of the college time table management system is

 Any number of colleges can registered themselves
 Time table can be generated according to the shift and branch
 Every faculty will be provided with their login id and password in the future
extension of this project.
 This software is easy to understand and it is very user friendly.
 User can directly print the time table after generation
 CHAPTER 7
7. SNAPSHOTS

1. Login Page
2. Registration Page
3. Forget Password
4. Change Password
5. College detail
6. Shift Detail
7. Branch Details
8. Semester Detail
9. Teacher Detail
10. Subject Detail
11. Seminar details
12. Project Detail
13. Lab Detail
14. Distribute teacher
15. View teacher load
16. Select branch for generation of Time Table
17. Time table
18. Time table to print
19. Print menu for printing time table
 CHAPTER 8
8. CONCLUSION

The college time table management is a web based system. It basic function is to generate the
time table according to the data filled. The user which has login id and password can login or
otherwise he can register himself. After login, he will fill all the details related to the college,
labs, teacher, seminar, and project and submit the related form. The user will distribute the
subject among the teacher. Then he can also view the teacher and subject load also. After
filling the entire data, time table will generates. The user can also print the time table from
the website only. Our system is very user friendly and it is secure enough.