Project Report On Time Table

Time table Management System
Department of Information Technology, SSBTs COET, Jalgaon 1

CHAPTER 1
INTRODUCTION
Time table of a Department is the backbone for organizing classes. Creating a
Time table with no clashes of subjects and faculty members is really a tough job while
doing manually. It is very complex and time consuming job.
So we have developing the software Time table Management System. It will
help to automatically generate Time table for all classes. This system consists of list of
faculty members, subjects of all classes, which subject will be taught by which faculty
member, how many class rooms and labs available and how much load for each faculty
member. After providing such information, Time table will be generated automatically by
TMS. Hence it will avoid the tedious manual calculations.
TMS will generate:
Class Time table
Time table of various classes i.e. SE, TE and BE will be generated.
Lab Time table
Time table of all 10 labs will be generated. i.e. Lab1, Lab2, Lab3 etc.
Faculty Time table
Time table of each Faculty member will be generated.
Master Time table
It includes Time table of all 3 classes, all 10 labs, all class rooms, and all
faculty.
Class Room Time table
Time table of class rooms which are available i.e. room no.311, 312 will
be generated.
TMS is developed using C# .NET as a front end language and SQL Server 2008
as a backend. The basic inputs are obtained from the user and the inputs are processed
and the Time table is generated accordingly.



CHAPTER 2
STUDY OF EXISTING SYSTEM
2.1 PRESENTLY AVAILABLE SYSTEM
At present Department is using manual calculations to allocate classes and labs to
various faculty members. So the main objective of this application is to reduce the time
taken for allocation of classes which is presently being done by tedious manual
calculations and it also serves the need of both faculty members and students in looking
up their Time table frequently.
.
2.2 NEED FOR THE NEW SYSTEM
In Departmental work after every semester, so many time-consuming tasks are
present. It includes creation and proper management of class Time table, lab Time table,
master Time table, staff Time table etc. The Department is using manual working for
generation, so there are so many drawbacks of presently available system.
Time-consuming processes
Monotonous Process
Manual Labor
Less Flexibility
To remove these drawbacks we have developed the TMS. In our software, there
is a centralized control by authenticated user i.e. administrator, because of this no one can
alter the data. Thus in this software the Time table will be automatically generated
depending on the data given by faculty members and on the availability of the subjects.
Following figure shows Report of Time table which is generated manually.
Figure 2.1 Manual Report of Time table


CHAPTER 3
PROJECT PLANNING AND SCHEDULING
3.1 TIMELINE CHART
When creating a software project schedule, the planner begins with a set of tasks
(the work breakdown structure). If automated tools are used, the work breakdown is input
as a task network or task outline. Effort, duration, and start date are then input for each
task. In addition, tasks may be assigned to specific individuals.
As a consequence of this input, a timeline chart, also called a Gantt chart, is
generated. A timeline chart can be developed for the entire project. Alternatively,
separate charts can be developed for each project function or for each individual working
on the project.



Figure 3.1: Timeline Chart


3.2 PROJECT TABLE
Table 3.1: Project Schedule
Work Task Plan Start
Actual
Start
Plan
Complete
Actual
Complete

Assigned
Person
Efforts
Allocated
1.Search Project
Topic
15/1/2014 15/1/2014 21/1/2014 22/1/2014
Nikita,
Prajakta
Nikita,
Prajakta
2.Analysis &
Problem Definition
21/1/2014 22/1/2014 24/1/2014 24/1/2014
Nikita,
Prajakta
Nikita,
Prajakta
3.Define Desired
Function of project
24/1/2014 24/1/2014 30/1/2014 31/1/2014
Nikita,
Prajakta
Nikita,
Prajakta
4.Selection of
Process Model
1/2/2014 1/2/2014 7/2/2014 7/2/2014
Nikita,
Prajakta
Nikita,
Prajakta
5.Requirement
Gathering
7/2/2014 7/2/2014 12/2/2014 14/2/2014
Nikita,
Prajakta
Nikita,
Prajakta
6.Designing Of ER
Diagram
13/2/2014 15/2/2014 16/2/2014 17/2/2014
Nikita,
Prajakta
Nikita,
Prajakta
7.Design Of Data
Flow Diagram
16/2/2014 17/2/2014 19/2/2014 22/2/2014
Nikita,
Prajakta
Nikita,
Prajakta
8.Designing of
UML Diagram
19/2/2014 22/2/2014 28/2/2014 29/2/2014
Nikita,
Prajakta
Nikita,
Prajakta
9.Coding of User
Interface Form
29/2/2014 1/3/2014 12/3/2014 15/3/2014
Nikita,
Prajakta
Nikita,
Prajakta
10.Database
Connectivity
13/3/2014 15/3/2014 20/3/2014 22/3/2014
Nikita,
Prajakta
Nikita,
Prajakta
11.Coding Project
Modules
20/3/2014 23/3/2014 28/3/2014 28/3/2014
Nikita,
Prajakta
Nikita,
Prajakta
12. Testing 29/3/2014 29/3/2014 5/4/2014 5/4/2014
Nikita,
Prajakta
Nikita,
Prajakta
12. Cost
Estimation
5/4/2014 5/4/2014 6/4/2014 8/4/2014
Nikita,
Prajakta
Nikita,
Prajakta
13.Define Future
Scope
6/4/2014 8/4/2014 10/4/2014 10/4/2014
Nikita,
Prajakta
Nikita,
Prajakta



3.3 COST ESTIMATION
We used the COCOMO Model to estimate the cost of our project. As, the system
is for small scaled organization we used organic type for estimating cost for our system.
So, we calculated it as:

Effort Applied (E) = 2.4*(3.1)
1.05
= 7.87(man-months)
Development Time (D) = 2.5*(7.87)
0.38
= 5.48(months)
People required (P) = 7.87/5.48 =1.44=2(number of persons)
Salary of 1 member = Rs.5000 per month
Salary of 2 members= (2*5000) = Rs. 10,000/- per month
Documentation charges = Rs.1000/-
Total salary for duration (D) = (5000*2)*5.48=Rs.54800
Total cost = (E*Total salary) + Documentation charges
= (7.87*54800) +1000
= Rs.432276/-
Finally the estimated cost of the software on the basis of KLOC will be Rs.432276/-.



CHAPTER 4
PROBLEM DEFINITION
Basically syllabus in colleges follow semester pattern so that after every semester
it is headache to the faculty members to manually prepare and properly manage the Time
table, and it requires too much efforts and also it is time consuming .
So, an application system named Time table Management Systemis one which
atomizes the task of subject allocation for the Faculty member of department. Through
this system, Time table for individual faculty and each class can be generated
automatically after entering all the inputs which will avoid the tedious manual
calculations.



CHAPTER 5
PROPOSED SYSTEM
The Time table will be automatically generated depending on the options given by
faculty and on the availability of the subjects. This will avoid tedious manual calculations
involved to generate the Time table as well as various errors due to manual calculations.
Following are functions of TMS
Class Time table
Time table of various classes i.e. SE, TE and BE will be generated.
Lab Time table
Time table of all 10 labs will be generated. i.e. Lab1, Lab2, Lab3 etc.
Faculty Time table
Time Table of each Faculty member will be generated.
Master Time table
It includes Time table of all 3 classes, all 10 labs, all class rooms, and all
faculty.
Class Room Time table
Time table of class rooms which are available i.e. room no.311, 312 will
be generated.



CHAPTER 6
SOFTWARE ENGINEERING PROCESS MODEL
In order to solve actual problem in an industry, a software engineer or a team of
engineers must incorporate a development strategy that encompasses the process, method
and tools layers and the generic phases. This strategy is often referred to as a process
model or a software engineering paradigm. A process model for software engineering is
chosen based on the nature of the project and application, the methods and tools to be
used, and the controls and deliverables that are required.
In our project we have used Incremental Model for developing the project.
6.1 INCREMENTAL MODEL
The Incremental model combines elements of the linear sequential model (applied
repetitively) with the iterative philosophy of prototyping. The incremental model applies
linear sequences in a staggered fashion as calendar time progresses. Each linear sequence
produces a deliverable Increment of the software. It should be noted that the process
flow for any increment can incorporate the prototyping paradigm. When an incremental
model is used, the first increment is often a core product. That is, basic requirements are
addressed, but many supplementary features (some known, others unknown) remained
undelivered. The core product is used by the customer (or undergoes detailed review). As
a result of use and/or evaluation, a plan is developed for the next increment. The plan
addresses the modification of the core product to better meet the needs of the customer
and the delivery of additional features and functionality. This process is repeated
following the delivery of each increment, until the complete product is produced.
We apply the incremental model for Time table Management System as it goes
from certain iterations as the first iteration gives us a core product which doesnt contain
the basic requirements hence we gather the basic requirements like hardware and
software requirements [1].
The Incremental model is divided into a number of framework activities, also
called Task-regions. Typically, there are 4 task-regions.



Figure 6.1: Incremental Model [1]
Requirement Analysis: In this section, we gather all the structural, behavioral,
functional requirements of the proposed system in each phase. In requirements analysis,
we collect the information regarding class Time table sheets, master Time table sheet, lab
Time table sheet, staff Time table sheets, personal Time table sheet, supporting
softwares like Microsoft Visual Studio 2012, Microsoft SQL Server 2008 and all
information required to develop TMS.

Design: The design phase gives us the basic ideas about how our TMS will look like. We
have created a design are: Data Flow Diagram, Entity Relationship Diagram and UML
Diagrams such as Class Diagram, Use Case Diagram, Sequence Diagram, Collaboration
Diagram.

Coding: After finalizing the design, coding came to the picture for physical
implementation. In coding, we have planned to develop the coding for creating the forms,
buttons, and database connectivity according to the functionality of the TMS.

Testing: Tasks required building one or more representations of the application. The task
is divided into the number of sub-tasks for testing. The testing will be done several
phases like Unit Testing. It removes the bugs and errors.



CHAPTER 7
REQUIREMENT ANALYSIS AND SPECIFICATION
7.1 REQUIREMENT ANALYSIS
Requirement Analysis is the phase in which the entire requirement related to
software are collected which helps the designer to design the actual system. Requirement
analysis enables the system engineer to specify software function and performance
indicates softwares interface with other system elements and establish constraints that
software must meet [1].
Thus in this way, we have collected various requirements of our project. Such as
Database requirement:
Faculty Details.
Subject Details.
No. of Class rooms available.
No. of labs available.
Batch Details of each class.
7.1.1 Problem Recognition
In our department, Time table incharge generates Time table manually. So our
main aim is to develop system which will reduce manual work of our Department and
saves time of Time table incharge.
7.1.2 Evaluation and Synthesis
Problem evaluation and solution synthesis is the next major areas of effort for
analysis. The analyst must define all extremely observable data objects, evaluate the flow
and contents of information, define and elaborate all project functions, understand its
behavior in the context of events that affect the system, establish the system interface
characteristics , and uncover additional design constraints. Each of these tasks serves to
describe the problem so that an overall approach or solution may be synthesized.
In this way, we evaluated requirements and define various functions of our system
and divided TMS in various modules such as:
Class Time table.
Class Room Time table.
Lab Time table.


Master Time table.
Faculty Time table.
7.2 REQUIREMENT SPECIFICATION
The term specification means different things to different people. A specification
can be written document, a graphical model, and a formal mathematical model, collection
of using scenario, a prototype, or any combination of these states. The system
specification is the final work product produced by the system and requirements
engineer.

7.2.1 Hardware Requirements
Processor : Dual Core
Hard Disk : Minimum 80 GB
Memory : Minimum 1 GB RAM

7.2.2 Software Requirements
Operating System : Windows 9X
Front End : C# .Net(Microsoft Visual Studio 2012)
Back End : Microsoft SQL Server 2008



CHAPTER 8
DESIGN
8.1 DATA DESIGN
Data Design is first of the four activities that are conducted during software
engineering. The impact of data structure or program structure and procedural complexity
causes data design to have profound influence on software quality. The concept of
information hiding and data abstraction provide the foundation for an approach to data
design. The structure of data has always been important part of software design.
8.1.1 Class Diagram

Figure 8.1: Class Diagram
In TMS, Time-Table is the main class and which is inherited by various child
classes such as Class_Wise, Faculty, Class-Room, Lab, Load_Management etc.
Load_Management Class is used to get and store subject detail such as theory subjects
and practical subject, batch details of each class.


8.2 ENTITY RELATIONSHIP DIAGRAM
ER Diagram is used to show relationship between various entities present in
database. Entities are nothing but the various tables which we have created in the
database. The following diagram shows the ER-Diagram of our project.

Figure 8.2: Entity Relationship Diagram
Here we have created the various entities such as Admin, Faculty, Subject Data
and Batch_Detail_Data.
Admin entity has two attributes: username and password.
Faculty entity has two attributes: name and contact_no.
Batch_Detail_Data and Subject_Data references Class entity.



8.3 DATA FLOW ARCHITECTURES
This architecture is applied when input data are to be transformed through a series
of computational and manipulative components into output data. A data flow diagram is a
graphical representation that depicts information flow and the transforms that are applied
as data move from input to output. The basic form of a data flow diagram, also known as
a data flow graph or a bubble chart, A level 0 DFD, also called a fundamental system
model or a context model, represents the entire software element as a single bubble with
input and output data indicated by incoming and outgoing arrows, respectively.

Figure 8.3: DFD Level 0
TMS will take following input:
Faculty Details.
Subject Details of each class.
Batch Details of each class.
Class Room Details.
Lab Details.
And after processing input, TMS will generate following output:
Report of Class Time table.
Report of Class Room Time table.
Report of Faculty Time table.
Report of Lab Time table.
Report of Master Time table.


Figure 8.4: DFD Level 1
8.4 UML DIAGRAMS
8.4.1 Use Case Diagram
Following figure shows Use case of TMS.
There are three actors:
Admin
Faculty
Student
Admin can Manage Load, view Faculty Time table, view Lab Time table, view Master
Time table, and view Class Room Time table.


Figure 8.5: Use Case Diagram
Faculty can view Class and Lab Time table.
Student can only view Class Time table.
8.4.2 Sequence Diagrams

Figure 8.6: Sequence Diagram (Student)
Above figure shows sequence diagram of TMS for student.
Firstly, student will select class whether he is from SE, TE or BE. After selecting class,
Frontend will generate Time table for specified class after retrieving Time table from
database.


Figure 8.7: Sequence Diagram (Admin)
Above figure shows sequence diagram of TMS for Admin.
Admin will enter username and password, frontend will send specified field to database.
Database will check whether specified fields are correct or not. If fields are correct.
Frontend will send Welcome Admin message to admin.
8.4.3 Collaboration Diagrams

Figure 8.8: Collaboration Diagram (Student)


Above figure shows collaboration diagram of TMS for student.
Firstly, student will select class whether he is from SE, TE or BE. After selecting class,
Frontend will generate Time table for specified class after retrieving Time table from
database.

Figure 8.9: Collaboration Diagram (Admin)
Above figure shows collaboration diagram of TMS for Admin.
Admin will enter username and password, frontend will send specified field to database.
Database will check whether specified fields are correct or not. If fields are correct.
Frontend will send Welcome Admin message to admin.



CHAPTER 9
TESTING
9.1 TESTING
Software Testing is a critical element of software quality assurance and represents
the ultimate review of specification, design, and code generation. Once source code has
been generated, software must be tested to uncover (and correct) as many errors as
possible before delivery to customer. Your goal is to design a series of test cases that
have a high likelihood of finding errors. These techniques provide systematic guidance
for designing tests that:
1. Exercise the internal logic of software components.
2. Exercise the input and output domains of the program to uncover errors in
program function, behavior and performance.
9.2 UNIT TESTING
Each module in the project is tested unit wise. The project on completion is tested
and verified with all the constraints.
The initial unit is the input of all the data. The data is inputted as per the required
class allotments. Insufficient of faculty members would lead to generating incorrect Time
table as many periods would remain unallocated. The faculty and corresponding subject
which they are willing to teach for each section is taken as input. All the inputs are stored
in corresponding databases so that it could be retrieved for later use.
The next unit to be tested is allotment of lab slots. For lab allotment, the designed
system is programmed in such a way that no two classes have same lab slot for same lab
subject.
9.3 TEST CASES
The following are some of the tests that were conducted to find out the errors and
bugs. These test cases are run by us to know whether our modules are running as stated or
not.



Table 9.1: Test for Login
Sr.
No.
Test Case Expected Result Actual Result
Test
Result
1
If the user name or
password not
specified.
The system should
through message that
User Name and
Password cannot be
blank
The system through
message that User
Name and Password
cannot be blank

Pass

2
If the user name
and password
entered do not
match with the
stored user name
and password.
The System should
through message
Incorrect Username
or Password
The System through
message Incorrect
Username or
Password

Pass

Table 9.2: Test for Time table Generation
Sr.
No.
Test Case Expected Result Actual Result
Test
Result
1
If class, subject,
theory or practical
is not specified.
The System should
through message
Please specify class,
subject, theory or
practical properly.
The System will
through message
Please specify class,
subject, theory or
practical properly.

Pass

2
While click on
show Time table
report button.
The system should
generate report of
Time table.
The system generates
report of Time table.

Pass



CHAPTER 10
RESULTS
Now here are the snapshots of our project. In this chapter, we will go through
some of the snapshots of our project, Time table Management System.

Figure 10.1: Main Form
The above figure 10.1 shows the main form of our project. This form allows you
to view Class room Time table, lab Time table, faculty Time table, year wise Time table,
master Time table, etc.


Figure 10.2: Faculty Detail Form
The above figure 10.2 shows the Form which will take Faculty detail as a input.
By clicking on Next Button, new Faculty records can be inserted and after clicking on
Submit Button following form will be shown.

Figure 10.3: Subject Detail Form


The above figure 10.3 shows form, which will take subject details of B.E as input.
User can specify whether name of subject which is specified is theory or practical by
clicking on checkbox of theory and practical. By clicking on Next Button, No. of subjects
can be inserted and stored in database. After clicking on Submit Button, following form
will be shown.

Figure 10.4: Batch Detail Form
The above figure 10.4 shows the form which will take Batch Detail as input,
firstly user will enter no. of batches of B.E class and after specifying no. of batches user
will enter no. of student in each batch.

The below figure 10.5 is the report of Time table of B.E theory subjects.



Figure 10.5: Report of Time table of B.E Theory Subjects
Figure 10.6: Report of Time table of Faculty
The above figure 10.6 is the report of Faculty Time table.


Figure 10.7: Report of Class Room Time table
The above figure 10.7 is the report of Time table of Class Room.
Figure 10.8: Report of Lab Time table
The above figure 10.8 is the report of Lab Time table.



CHAPTER 11
ADVANTAGES AND DISADVANTAGES
11.1 ADVANTAGES
Time Saving :
Creating a Time table with no clashes of subjects and faculty is really a
tough job while doing manually.
Through this system, Time table for individual faculty and each class can
be generated automatically after entering all the inputs which will avoid
the tedious manual calculations.
Generate various sets of Time table :
Class Time table.
Faculty Time table.
Class Room Time table.
Lab Time table.
Master Time table.
Secure :
Modification can be done by only one authenticated user i.e. admin.
Accessing capability :
This software provides fast searching methods and easy way to access
information.

11.2 DISADVANTAGES
Difficult to maintain :
Load of Faculty cannot be shared during semester.
If any data concern with faculty changes, whole Time table schedule will
collapse.
Platform Dependent:
This system can run only on Windows environment.



CHAPTER 12
APPLICATIONS
Time table Management System can be adopted by various Departments of
Colleges such as:
Computer Science
Art and commerce
Engineering
Medical
Management of Business Administration etc.



CONCLUSION AND FUTURE WORK
Generating Time table manually is very tedious job. In this project we have tried
to atomize this system at some extent. This will be helpful for every Department.
In Future we can make this Time table Management System as an Web Based
Application.



REFERENCES
[1] Roger Pressman, Software engineering A Practitioners Approach, 5
th
Edition,
Tata McGraw Hill International Edition, pp. 215-217.
[2] C# 2012 and .NET 4.5, Author : Christian Nagel.
[3] www.microsoft.com/en-in/server-cloud/products/sql-server
[4] http://www.w3schools.com/sql/default.asp
[5] http://www.microsoft.com/NET

Project Report On Time Table

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Project Report On Time Table

Uploaded by

Copyright:

Available Formats

Time table Management System

Department of Information Technology, SSBTs COET, Jalgaon 1

You might also like