1.

1DETAILED 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.2PROJECT 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.3PRESENTLY AVAILABLE SYSTEM 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.4FUTURE 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.6REQUIREMENT ANALYSIS
This gives minimum requirement your system should have inorder to make this
software work. This software works fine in any operating system in which the

developer tools or the user tools can be installed. Since we had limited resources
we could only test in Widows 7, Windows XP, Ubuntu 11.04, Ubuntu 10.10. So
usually the requirement specification will be same as that of the operating system.
So we are providing a standard specification.

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

1.7 ORGANIZATION OF REPORTS

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 Conclusion &Project Future Scope .Also, it provides
a probable solution for overcoming the limitations.After that, References are
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.2FEASIBILITY 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

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& 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.2 OVERALL DESCRIPTIONS

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

Refer to the page where user will

Print button

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.3 USER 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 DESIGN 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 ER- DIAGRAM FOR THE SYSTEM

3.3 SYSTEM ARCHITECTURE

Fig:Detailed Architecture of University Timetabling InformationSystem.

Once the student information system database is enriched with classified
data, it allows efficient administration of the university timetabling function as
well as generates timetable views. To further enhance the administration function,
these timetable views allow the information to be queried from various
perspectives namely: rooms, student, staff and courses. These views generate
manual and automated timetables and provide not only screen viewing but also the
ability to print hardcopies. Furthermore an ad hoc report generator, embedded in
the application, allows for the creation of management report from both the
Maintenance and Administration modules.
The above mentioned information system architecture was designed during
the requirement specification process. It entailed the detail view of the system,
which comprises of ERDs, data structures and Data Dictionary. These
components of the requirements specification document are illustrated and
discussed later in this chapter. Furthermore, the proposed output, derived from the
requirement specification was classified into manual as well as automated

timetables and management reports. Hence the requirements of the system entail a
relational database that allows the logical storage of data with minimal
redundancies. This will allow the university timetabling application to maintenance
data and provide information to management for university administration. The
system should also encapsulate a timetable generator that allows for both manual
and automated timetables. The outputs of the system are the various management
and timetabling reports.

The manual timetable generator creates timetables that assist administrators

in a decision support system capacity by the provision of informed information. It
allows the user to create timetables from the data in the student database system
and facilitates manual allocation. The core strategy adopted was developing an
application from an IS perspective to encapsulate key administrative functions and
enhancement of the overall timetable generation process. With manual timetable
generation that supports the core timetabling process, the system with its
automated timetable generator, acts as a support facility to the core process.
Furthermore the application encapsulates not only the manual and automated
timetable generators but also provide an integrated solution to the other
administrative functions of the university. Thus the system generates manual
timetables and management reports from the data stored in the database and
generates automated timetables using this data and a Dynamic Slot Table
Algorithm (DSTA). However, the focus of the university timetabling information
system is on decision based timetable generation as opposed to algorithm- based
generation

3.4UML DIAGRAM
3.4.1 USE CASE DIAGRAM

Use Case Diagram 1

Actor: Administrator
Object: 1. Maintain Login Id and Password
2. Maintain Database
3. Maintain College Details
System

MAINTAIN LOGIN ID AND PASSWORD

MAINTAIN DATABASE

MAINTAIN COLLEGE DETAILS

ADMINISTRATOR

CHECK VALIDATION

VIEW TIMETABLE 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.

System

INSERT COLLEGE DETAILS

INSERT TEACHERS DETAILS

INSERT SUBJECT DETAILS

INSERT LABS, ROOMS DETAILS

HOD

GENERATE TIMETABLE

PRINT TIMETABLE ACCORDING TO BRANCH

LOGIN ID AND PASSWORD

3.4.2 CLASS DIAGRAM

COLLEGE
+NAME

1..*
DEPARTMENT
+NAME
1
1

HAS

HAS

1..*
TEACHER
+ID
+NAME
+QUALIFICATION
+TYPE
+LECTURE
+ADD()
+DELETE()
+ASSIGN()

HAS

COURSE
*
TEACH
*

1..*
1..*

1..*

ROOM

+CCODE
+NAME
+LECT_PER_WEEK

+ROOM_ID
+LOCATION
+CAPACITY

+ADD()
+DELETE()
+ASSIGN()

+ADD()
+DELETE()
+ASSIGN()

1..*

1..*
ASSIGN

ASSIGN

ASSIGN

1
TIMETABLE
1
READER

PROFESSOR

LECTURER

GRADUATE

POST GRADUATE

OTHERS

+SID
+INSTRUCTOR
+ROOM
+MID
+CREATE()
+MODIFY()
+DELETE()
+SEARCH()

3.4.3 ACTIVITY DIAGRAM

LOGIN

VALIDATE(USER,PASSWORD)
DISPLAY LOGIN ERROR MESSAGE
VALIDATE

[FAILURE]

[SUCCESS]

DISPLAY ADMINISTRATOR MENU

(ADMINISTRATOR)

(LECTURER/STUDENTS)

DISPLAY LECTURER/STUDENT MENU

ACTIVITY DIAGRAM FOR LOGIN

Figure above shows the activity diagram for Log-in. First, the lecturers, students
and administrator need to log in using the username and password that was created
during registration. The system will validate the username and password. If the
password or username is invalid, an error message will be displayed and the
lecturer or student oradministrator can try to log in again. If log in is successful, the
system will identify theuser as a lecturer, student or an administrator.

SELECT MENU ADD CLASS

DISPLAY ERROR MESSAGE

READ INPUT

(FAILURE)
(ADD CLASS)

READ INPUT

ADD SUBJECT

(SUCCESS)

DISPLAY SUCCESS MESSAGE

DISPLAY ERROR MESSAGE

(FAILURE)
(SUCCESS)

REGISTER SUBJECT

ACTIVITY DIAGRAM FOR ADD SUBJECT OR CLASS

Above figure shows the activity diagram for add subject and class. Both screens
are the same. If the administrator wants to add the subject or the class, he or she
has to fill in the form the subject or the class information. Then click on the next
button. Validation of the form will be carried out before the data is stored in the
database. Upon successful adding the subject or class, a successful application
page will be display. If validation failed, an error message window will pop up.

INQUIRY CLASS AVAILABLE

READ INPUT
DISPLAY SUCCESS RESULT

(AVAILABLE)

BOOKING CLASS

READ INPUT
(SUCCESS)

(NOT AVAILABLE)

(NOT SUCCESS)
DISPLAY NOT AVAILABLE CLASS MESSAGE

ACTIVITY DIAGRAM FOR INQUIRY CLASS AVAILABLE

AND CLASS BOOKING
Figure above shows the activity diagram for the Inquiry class available for
lecturers. To inquire whether a class is available, the lecturers have to select the
class based on the list in the system. Once the submit button has been clicked, the
system will check the query. If inquiry is successful, the message successful page
will be displayed. If fails, a message error will also displayed. Then if the class is
available, lecturer can go to booking class menu to book the class. The message
successful booking of the class is displayed and if the booking failed the
message will also be displayed.

3.4.4 SEQUENCE DIAGRAM

USER/ADMIN

LOGIN

DATABASE

1 : USER NAME/PASSWORD()
2 : CHECK VALIDATION()

3 : VERIFY USER()
4 : MDI SCREEN()

5 : UNSUCCESSFUL VALIDATION()

6 : UNSUCCESSFUL VALIDATION()

SEQUENCE DIAGRAM FOR VALIDATION

Figure above shows a sequence diagram for the user validation. In order to log in,
the lecturer/student/administrator need to key in their username and password.
Then the browser will sendthe information to the web server and validate the
information with the database.Successful validation will be sent to the web server,
and the server will display the Main Menu page according to the user type. As for
unsuccessful validation, the server will send an error login page to the monitor.

ADMINISTRATOR

FRONTEND

DATABASE

1 : REQUEST ADD FUNCTION()

2 : DISPLAY ADD FUNCTION()

3 : INFORMATION FILLED()

4 : SENDS FIELD()

5 : DATA VALIDATION SUCCESSFULLY()

6 : MESSAGE DATA IS SAVED()

7 : UNSUCCESSFUL()
8 : ERROR MESSAGE()

SEQUENCE DIAGRAM (ADD TEACHER)

Figure above shows a sequence diagram for Adding teacher. The browser
will send a request to the web server and it will return the teacher information
page. The teacher will have to fill information form. If validation is successful, the
query will be passed to the database and after the data is stored successfully, the
message will be displayed. If the form validation failed, a window with the error
message will pop out.

ADMINISTRATOR

FRONTEND

DATABASE

1 : SELECT COURSE()

2 : SELECT WORKLOAD()
3 : ENTER TEACHER,ROOM AND COURSE()

4 : SENDS FIELD()

5 : DATA VALIDATION SUCCESSFULLY()

6 : MESSAGE SUCCESSFULLY ADDED()

7 : UNSUCCESSFUL()
8 : ERROR MESSAGE()

SEQUENCE DIAGRAM (ADD TIMETABLE)

Figure above shows a sequence diagram for adding Timetable. The browser will
send a request to the web server and it will return the information page which
include information to be filled related to teacher,subject, class,labs. After filling
these fields it is been send for validation. If validation is successful, the
information will be passed to the database and after the data is stored successfully,
the message will be displayed. If the page validation failed, a window with theerror
message will pop out.

3.4.5 DATA FLOW DIAGRAMS

The DFD is also known as the bubble chart. It is a simple graphical

formalism that can be used to represent a system in terms of the input data to the
system, various processing carried out in these data and the output data generated
by the system. Starting with a set of high-level functions that a system
performance of DFD model in hierarchically it represents various sub functions.
In a normal convention, logical DFD can be completed using only four notations:
Represents source or destination of data
Represents Data Flow
Represents a process that transforms incoming data into outgoing data
Represents Data Source

LEVEL 0
Level 0

Administrator

College Time
Table
Management

Database

LEVEL 1

Level 1

Administrator
Database

Admin
Administrator
Login Id
and
Password

Login
Validation

College Time
Table System

Faculty
Detail
Subjects
Detail

Faculty database

Subject Database

LEVEL 2

Level 2

New faculty

Faculty or
HOD

Faculty database

Login
id

User validation

Passwor
d

User area either

HOD or faculty

Time table
management
system

CHAPTER 4

4.1 CONCLUSION

Automatic Timetable Generator is a web based system for generating timetable

automatically. It is a great difficult task that to manage many Faculty's and
allocating subjects for them at a time manually. So proposed system will help to
overcome this disadvantage.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.

4.2 SUGGESTION FOR FUTURE WORK

The Automatic Timetable Generator is driven portal for educational

organization and is a web based application which will be helpful for creating
Timetabels . This project will be a great helpful for the institiutions because, It is a
great difficult task that to manage many Faculty's and allocating subjects for them
at a time manually and this project will help to manage it properly. This manage
timetable for faculty with considering maximum and minimum workload , and can
be managed easily .