2

INTRODUCTION



Technology makes liIestyle easier by providing better support to diIIerent
systems, better accuracy, better security options, easier maintenance, etc. Now
a day`s technology eventually means 'computers which is the greatest
achievements oI last century. Day by day computers are being more and more
popular because oI its Ieatures like ease oI work, ease oI learning, accuracy with
the least time consumption and the last but not i.e. ease oI maintenance with cost
eIIectiveness. So as a part oI these ongoing evolutionary approach traditional
systems are being computerized to make them more IruitIul than ever.
Time Table Management system is an automated system which manage time table
according to the data given by the user. The main requirement oI the application is
to provide the details about the branch, subjects, no. oI labs, total no. oI period and
details about the lab assistance. Then the application generates the time table
according to your need.


The basic project is to create a:-

1. Time Table Management System

2. To create Databases oI diIIerent entities involved in this process.

3. Maintaining database-containing inIormation about the various classes,
subjects, Labs, teachers periods etc.










3
Objective

As we discussed earlier that manual maintenance oI a Time Table Management
System is a tedious job. So to enhance the ease oI working we go Ior this package
.Manual maintenance oI databases oI items, time table processing is a time taking
process and somehow erroneous. To give more accuracy to the system i.e. rather
going manual modiIication we involve computer Ior accuracy. The least but most
important it saves time.

Main Objectives of the package are:-

1. Create a Time Table Management System to be used by University.

2. To perIorm the basic requirements oI the Iirm.

3. Maintaining databases oI subject, Class, semester`s details.
Scopes and boundaries oI the package

4. As it is a computer-based package so maintenance and working is somewhat
diIIicult Irom manual mode oI approach.

5. As it is not possible to associate each and every requirement oI the system so in
some way or other it will going to create problem at some stage oI execution (like
report generation).

6. As a computer based System it is easier to Ietch data Irom the database Ior
unsocial activities. Also easier to destroy the existing ones.

7. On implementing this package the Iirm will get error Iree data to analyze.

8. This package would limit the time and money Iactor involve in 'Time Table
Management System.

9. Maintenance is much easier and accurate than the existing manual system.

10. Security Ieatures are somewhat higher than that oI manual approach









4

1 1. .3 3 I In nt tr ro od du uc ct ti io on n t to o I In nf fo o. . T Te ec ch hn no ol lo og gy y. .

A Computer is also a system because it is a group oI integrated parts which are
used to solve any problem by executing a suitable program.
USES AND IMPACT OF COMPUTERS
SCIENCE AND TECHNOLOGY: Thousands oI scientiIic application are
processed daily, on the computers. One oI the most important daily activities is
weather Iorecasting, which involves solution oI mathematical equation using
worldwide data about air pressure, temp, humidity and other values. The daily
weather report on TV is the main day-to-day application given by a computer.
Commerce and IndustryIn business, computers are being used Ior many data
processing tasks such as word processing, Iiling, assembling number and Iacts
associated with general oIIice Iunction like accounting, payroll processing and
personnel record keeping.
HOSPITAL AND MEDICINE : Computer are also being used Ior planning and
control purposes by health-care proIessionals. Computer equipment is used to
monitor pulse rate , blood pressure and other vital signs. This leads to correct and
Iast diagnosis. Medical researchers are using computer as a tool in their search Ior
cures oI deadly diseases like cancer and AIDS.
EDUCATION: Education system is making use oI computer on large scale.
Computer bring to new technologies in the Iield oI education like audio, video,
speech recognition and internet.
InIormation Technology is not only used in commerce and industry, it has
crept into almost all the activities oI human liIe right Irom his personal liIe to
medicine, To entertainment, etc. where it has created a new world in itselI.
Computer education has gradually become part and parcel oI school education,
college education as well additional specialized proIessional qualiIication. Now, in


5
general we can call a person literate iI he knows computer and its usage else
illiterate, as such is the importance which InIormation Technology education
enjoys.
Components Of Information Technology
The use and implementation oI InIormation Technology involves various
components oI it namely:-
1. ardware
2. SoItware
3. Data
4. Users
5. Storage &
6. Communications
1. HARDWARE:- ardware are those tangible components oI a computer which
one can see and Ieel. It includes input and output devices, central processing
units etc., which can Ieel and see.
2. SOFTWARE:- SoItware are set oI instructions or programs which are given to
computer so that it works and does the task. These are those intangible
components oI a computer which makes the tangible components work.
3. DATA:- Data is the collection oI Iacts and Iigures, which has to be worked on
by the computer. It is the collection which is the basis Ior decision making one
does.
4. USERS:- Users are those people who directly or indirectly are beneIited by the
use oI computers. They are the users oI the Iinal output as well as the providers
oI computers.
5. STORAGE:-Storage component is the one which enables the data and soItware
component to make its place in the computer system by residing in various
types oI storage devices.
6. COMMUNICATIONS:-Communication is that component, which enables a
user to communicate with the computer as well as the computer to
communicate with other computer to get various tasks done.


6


1.4 Back End Tool ( Oracle )

We are using ORACLE as a back-end in our project. ORACLE is the most
popular database currently in use.
Various approaches to data management are:
O Manual methods oI data management
O Management oI data and inIormation
O Convenient and eIIicient retrieval
O Updating operations
O Limitation oI manual data management
O !hysical Volume oI data
O uman processing oI data
O Technological Advancement in data management
O Using computers to speed up processing oI data
O Advancement oI processing power
O igh speed storage devices
O Centralized to distributed databases
Database management : An Evolutionary !henomenon Drawbacks oI the prevalent
approach to data management
O Data redundancy
O Risk to data integrity
O Data isolation
O DiIIicult access to data
O UnsatisIactory security measures
O !oor support oI parallel access oI data


7
Concept oI a DBMS
A database is a collection oI interrelated data Irom which some inIormation
can be extracted. The collection oI data must be logically coherent with some
inherent meaning. A database is designed and Built Ior a speciIic purpose, keeping
in mind the needs oI the applications that are going to use it and the end users oI
those applications. It is managed by soItware package known as a database
management system(DBMS). Data is stored in the Iorm oI tables. Tables are then
connected with visual basic and through linking this Can be used in Iront end in the
project.




















8

1.5 Front End









































9




















1 1 S SD DL LC C

Developing a system is just like a manuIacturing unit where some raw material and
man power is used to produce the goods in computer system, the data and Iigures
are Ied to computer Ior processing. The results produced by computer is called
inIormation and have value oI its users. On the basic oI inIormation we can take
valuable decisions.
In the later 1980, this process it was known as Computerization, but in 1990s it`s
name is more popular under the title 'InIormation Technology. According to an
author !eter Norton, the amount oI inIormation we have produced Irom 1990 to till
today is much much more than what inIormation we have produced in last 3000
years. So like industrial revolution, milk revolution and green revolution there is
a revolution in Iield oI Computers so that`s why it becomes an technology called
'InIormation Technlogy.
A system is deIined as the organized collection oI components
works in a coordinated manner, to achieve an objective. There three main
implications oI a system i.e.
1. A system must have a predetermined objective(s).


10
2. There must be interrelationship and interdependence among the system
components.
3. The objective oI organization as whole has higher priority than the objective oI
an individual component.
Characteristics of a system :
1. Organization It means all the parts oI a soItware system must be properly
arranged in order and structure.
2. Interaction All the components oI a system must interact with other
components to achieve the objective.
3. Interdependence One part oI a system must depends upon other component
Ior proper working. It means the output oI one part may be Ieed to the other
component as input.
4. Integration It means holism; which means the collection oI all the
components.
5. Central Objective Each system must have one central objective.
Components of a system
1. Output and input The output are the outcomes oI a system and input are the
data, Iigures and raw material Ied into computer Ior processing.
2. Processor(s) It is the operational component oI a system. In an industry, plant
& machinery is used to convert the incoming material to the Iinished goods
but in a computer system; operating system, language & DBMS package helps
the user to convert the input data into output data.
3. Control It is the decision making subsystem oI a system. It deals with
management oI resources and other components; Operating system.
4. Feedback A Ieedback may be ve or ve. These Ieedback Iactors gives the
idea to improve the system.
5. Environment It is the supra system in which system operates; like users,
oIIices and labs.


11
6. Boundaries and interfaces It is the limit which help us to identiIy the system
components.
Stages of a life cycle
Like Nitrogen & !roduction cycle a SoItware system is just like a cycle which
passes the Iollowing stages like:
1. Recognition oI need.
2. Feasibility study.
3. Analysis.
4. Design.
5. Implementation & Maintenance
1. Recognition of need : This steps is to be taken by the authorities oI the
organization. The old system has many limitations, which will be discussed in the
system analysis part oI this project. The Initial Investigation mainly deals with
O Recognition oI need
O Ability oI users
O Finance involved
O Current system and how new system will rectiIy the problems oI old one.
O It is also possible that an old or computerized system can be replaced by
computerized in the SAD.











12









2 2. .2 2 D Da at ta a C Co ol ll le ec ct ti io on n T To oo ol ls s. .

Data Collection is very important Ior designing a system. To design a system we
must collect the inIormation about
InIormation about the organization:
!olicies
Goals
Objectives
Organization Structure
InIormation about the user staII who will use our project directly or indirectly:
Authority
Relationship
Job Iunctions
Interpersonal relationship
The inIormation about work:
Work Flow
Work methods and procedures
Work Schedules
To collect the inIormation, some data sources are required and they are :


13
INTERNAL TOOLs : - Which are used to collect the data Irom sources within
the organization and they are :-
1. Financial Reports
2. !ersonnel StaII
3. !roIessional staII
4. System documents and manuals
5. User staII.
EXTERNAL TOOLs : These are the outside tools used to collect the data Irom
the system Ior designing and they are
1. Vendors.
2 2. .3 3 T To oo ol ls s F Fo or r S St tr ru uc ct tu ur re ed d A An na al ly ys si is s

Structured analysis means tools used to understand the system easily and steadily.
These tools are
Data Ilow diagrams
Data Dictionaries
Structured English
Decision Trees
Decision Tables
ER Diagrams
DFD is a tool which show the actual data Ilow in the system. It show us various
points Irom where the data is Ilows to a new point and where the major
transIormation takes place. The DFD uses some symbols and they are
A Square represents the source or destination oI data.
A Circle represents the program name or process.
A Solid Arrow Line shows the data in Ilow or motion.
An Open Rectangle shows the data at rest.
Data Dictionaries : Although DFD represents the data Ilow and transIormation; but
still it does not indicate the Iull details oI the system. For getting more details; data


14
dictionaries is used. A DD represents data about data. It is a document which is
used Ior system documentation and reIerence. It contains all the details oI elements
oI DFD.
Structured English : This concept is borrowed Irom the structured programming. It
is collection oI imperative statements & processing statements. The imperative
stmt include iI then else where as processing statements includes the calculation
statements.
Decision Trees : A decision tree is easy to draw and Iollow in which each branch is
called a condition and a leave or terminal node is called a processing. The root oI
the tree is called problem name.
Decision Table : A decision table is the collection oI Iour quadrants; condition
stub, action stub, condition entries and action entries. In condition stub all the
condition are listed in simple English and Maths. In Action stub all the actions are
written, In condition entry the responses to the conditions are written in Y`& N`
Iorm. In Action entry all the action response is written as X & --. X` means action
taken and - means no action.
ERD : Entity Relationship Diagram is a tool used to represent the tables, their
attributes and relationship.















15












2 2. .4 4 P Pr re ev vi io ou us s S Sy ys st te em m. .

Fact Iinding means to trace the Iollowing Iactors in the Iield oI SYSTEM
ANALYSIS AND DESIGN. The Iact Iinding passes through the Iollowing stages.
1. To check the perIormance oI old system.
2. !roblems in the
3. Old system.
4. Recommendations which can rectiIy the problems.
5. The management biases.
6. The user limitations.
7. !resent hardware and soItware.

SYS1EM AAALYSIS AAD DESICAis just as a manuIacturing unit in which raw
material is entered as input, machine and plant work as process and
products/Iinished goods as output. In the SAD the raw data is the input, programs
is the processes and inIormation is output. Some time iI the inIormation is not up
to the standards then the output can be Ied to the system as input - It means it work
as a cycle. So that why SAD is also called SDLC i.e. System Development LiIe
Cycle. During the system analysis, it is Iound that the old system has Iollowing
disadvantages
1. Not up-to-date


16
2. Less security
3. Data duplicacy
4. Not centralized
5. Slow in process










2 2. .5 5 P Pr ro op po os se ed d S Sy ys st te em m

The new recommended is the computerized, which has many advantages over the
old one.
1. Since the overall system is under the control oI Data Base Administrator
(DBA) - hence the system us centralized one.
2. The security and privacy is more in case oI new system.
3. The long process can be shortened.
4. Easy to maintain the data.

















17















2 2. .6 6 C Ch ha an nc ce es s o of f p pr ro oj je ec ct t t te er rm mi in na at ti io on n. .

Since SDLC is a cycle. It is called cycle; because aIter some time your project may
be terminated and initial investigation is done again ( i.e. Iirst stage oI the SDLC ).
The project terminated in the Iollowing situations. So an analyst and programmer
must take care oI these Iactors:
* Changing objectives or requirements oI the user can not be met by the existing
design.
* BeneIits realized Irom the candidate system do not justiIy commitment to
implementation.
* There is a sudden change in the user`s budget or an increase in design cost
beyond the estimate made during the Ieasibility study.
* The project greatly exceeds the time and cost schedule.
* User requirements were not clearly deIined or understood.
* The user was not directly involved in the crucial phases oI system development.
* The analyst, programmer, or both were inexperienced.
* The systems analyst or the project team had to do work under stringent time
constraints.
* User training was poor.


18
* Existing hardware proved deIicient to handle the new application.
* The new system leIt users in other departments out oI touch with inIormation
that the old system had provided.
* The new system may not user-Iriendly.
* Users changed their requirements.
* The user staII was hostile.



2 2. .7 7 H Ha ar rd dw wa ar re e a an nd d S So of ft tw wa ar re e U Us se ed d
Core2Duo !rocessor
512 RAM
30 GB DD
!en Drive Ior Data Backup
132 DM!
S/W requirements
Core Java
Oracle 8
MS OFFICE
O!ERATING SYSTEM
Windows X! SEVICE !ACK 2







19
SYSTEM DESIGN

























20









3 3. .2 2 T Ta ab bl le e D De es si ig gn n


Employee

SR.No Name Data type Constraint Description
1. Empid Number !rimary key Employee ID
2. Fname varchar Not null First Name
3. Lname Varchar Not null Last Name
4. Jobtype Varchar Not null Type oI Job
5. BS Varchar Not null Basic Salary
6. depno Varchar Not null Department Number
7. Gender Varchar Not null Gender
8. emailid Varchar Not null EmailID
9. mstatus Varchar Not null Marigal Status
10. contno Varchar Not null Contact number
11. QualiIication Varchar Not null QualiIication
12. Experience Varchar Not null Experience







Subject



21


SR.No Name Data type Constraint Description
1. Subcode Number !rimary key Subject code
2. Sname varchar Not null Subject Name
3. Language Varchar Not null Language
4. !aper Number Not null Number oI paper










Periods



SR.No Name Data type Constraint Description
1. Day Varchar !rimary key Day
2. !num Number !rimary key !eriod Number
3. Tst Varchar Not null Time start
4. Ted Varchar Not null Time end
5. !type Varchar Not null !eriod Type






Classes

SR.No Name Data type Constraint Description
1. Ccode Number !rimary key Class code
2. Cname varchar Not null Class name
3. Section Varchar Not null Section
4. Cincharge Varchar Not null Class Incharge
5. Room Varchar Not null Room




LAB

SR.No Name Data type Constraint Description


22
1. Lcode Number !rimary key Labcode
2. Class varchar Not null class
3. Lname Varchar Not null Lab Name
4. Lincharge Varchar Not null Lab incharge
5. Lnumber Varchar Not null Lab number





23
Time_table


SR.No Name Data type Constraint Description
1. Tid Number !rimary key Teacher id
2. Name varchar Not null Name
3. Day Varchar Not null Day
4. !eriod Varchar Not null !eriod
5. Time Varchar Not null Time oI period
6. Class Varchar Not null Class name
7. Section Varchar Not null Section oI class
8. Lectype Varchar Not null Lecture type











































24




























































25




































3.3 Data Flow Diagrams





26






3.4 Modules Description

SrNo. Module
Name
Description
1. Splash To show some introductory inIormation about
project and project developers.
2. Login Allow the user to enter valid user name and
password.
3. Main Menu To show the main menu oI the project Irom
where user a select the choice(s)
4. Employee To enter the Employee details
5. Subjects To enter the Subjects details
6. Lectures To enter the lectures details
7. Classes To enter the classes details
8. Lab To enter the Lab classes details
9. Timetable To enter about the timetable details teacher wise

27

28
















































29
































4 4. .1 1 I Im mp pl le em me en nt ta at ti io on n T Te ec ch hn ni iq qu ue es s

There are three mainly used testing and implementation techniques
Direct, !arallel or !ilot.
In Direct conversion - on a particular day the old system is discarded and new one
is adopted. Although it is a Iast process but iI only system is to be consulted but
that is not available. In parallel model, the old system can run in parallel manner.
Both the system cab be tested and consulted Ior accuracy, but this system is costly


30
one - because it is required to run the system parallel which is a time consuming
and costly.
ence the third system is to be consulted in which the old system is to be
converted into new one phase by phase. In this project phased model is used. Here
we used the parallel implementation technique.























4 4. .2 2 T Te es st ti in ng g T Te ec ch hn ni iq qu ue es s
AIter the design, coding and implementation oI the system, testing is the most
important and the major phase in the system development liIe cycle. For the system to be
perIect and reliable, the testing must be done. Although all the veriIications and the
checking validations increase reliability, but the actual perIormance is measured Irom the
testing. The testing gives us the satisIaction about the perIormance oI the system that we
have designed.For the testing, we must have to use some steps Ior it:
Test !lan:


31
BeIore moving ahead, we made a plan in which it was tested. In that plan, we decide
which strategy is to be used to test the perIormance oI the system. We use some steps in
the test plan. Such as: -
Unit Testing:
In the unit testing, we test the each part oI the project individually. All
modules like customer, dealer, total stock, total sale made by salesman, order placed by
the agency etc. were tested Ior errors iI any. We tested it by selecting the customer detail,
dealer detail, order detail etc. Irom the database. It was soaking properly and smoothly.
Also test were perIormed on diIIerent Iunctions by adding the new entries, Iind the data
Irom the database, deleting the data Irom the database etc. all the Iunctions were
perIormed easily and smoothly. At last we Iound that there is no problem in the unit
testing process.
System Testing:
For the system testing the whole system was tested with one-month data
oI previous system. The test was perIormed to determine whether the new system is
working properly or not. Whether it is dealing with the diIIerent types oI entries or not.
We also did it to determine whether the requirements oI the user should be IulIilled or
not. Some calculations were made to check it and at last the system testing was
completed without problem and without Iacing any problem.
Result oI Testing:

User told me that the system was Iully satisIactory and all the
requirements were Iully met. The user enjoyed oI working on the new system.


4 4. .3 3 I In ns st ta al ll la at ti io on n o of f s so of ft tw wa ar re e

BeIore installation - please check - whether your !C has Core java and Oracle or
not ? II not- !lease install thru CD & then proceed to INSTALLATION.
1. Return to dos prompt C:\~
2. Insert the INSTALLATION DISK in CD drive G:
3. Type command C:\~ G: Enter G:\~


32
4. Type command INSTALL enter on G:\~
5. AIter 2-3 minutes the s/w will be loaded.

4 4. .4 4 C Co on nc cl lu us si io on n

ence to conclude we can say t hat t his project ai ms, basicall y

towards computerizing a inIormat ion system. It is concerned wit h all
aspects oI record management. To recognize all t he Iields involved i n
t he system we have to st udy t hrough t he system development li Ie st yle
oI t he project.


33
Any successIul organizat ions have a set oI well-deIined
protocols Ior t he runni ng oI t he organizat ion. The main object ive oI
any such organizat ion is t o achi eve cust omer sat isIact ion. This
strategy is common in al most all such organizat ion. Since we have
used CORE JAVA in t he development oI t his project as Iront end it
serves as power soIt ware. Its graphical interIace has a high-end
advant age. The Iorm designing is si mple to understand to work on.
Thus it enhances t he readabilit y oI t he program along wit h
understanding in visual environment . ThereIore t hroughout t he project
it has been our eIIort to design proIessional level.












4 4. .5 5 R Re ef fe er re en nc ce es s


1. JAVA SECRETS
2. TE JAVA ANDBOOK
3. TE JAVA AWT REFERENCE
4. JAVA COM!LETE REFERENCE
5. ORACLE INSIGTS
6. ORACLE COM!LETE REFERENCE
7. EX!ERT ORACLE


34







**** END OF PRO1ECT ****