SCOPE OF THE PROJECT

1.SCOPE

Timetable Management System is a fast and friendly computer program,based on many years of timetabling experience and carefully designed to help you to schedule your timetable quickly and accurately. Developing a timetable generator for college is supposed to make a timetable for each semester,which used to be very tedious and pain staking job.This system makes timetable generation activity much faster,easier at the same time avoiding conflicts.This software can relieve you of much of the donkey-work of timetabling,leaving you with more time to apply your skills and judgment where they are needed.

INTRODUCTION

2.INTRODUCTION

Timetable management system has a powerful effect on the life of a school or college,and if you are a timetabler you carry heavy responsibilitiy.modern software can relieve you of much of the donkey-work of timetabling,leaving you with more time to apply your skills and judgment where they are needed. Timetable management system is a fast and friendly computer program carefully designed to help you to schedule your timetable quickly and accurately. Timetable management system will help you to deal efficiently with: -the scheduling of part time teachers, -option patterns, -staggered lunch-breaks, -split-site schools -consistently-setted blocks

2.1.Existing system
Existing system has no facility to provide the fast view of data. In this system we maintain the records manually across the files. Maintaining and writing the timetables is done manually .

2.2.Problem statement
In this system we maintain the records manually as files. The data can be change or loss Designing timetable manully is a time consuming job. As for every modification timetable has to be redesigned,even a small modification takes more time.

2.3.Proposed system
It generates timetable for every class It provides labs subject information according to selected class. Provides details about the faculty and students Generates individual timetable for faculty Retrieval of information is very easy Admin module:admin provide the courses information,view the courses information,add different subjects to a course,register lecturers. Lecturer module:view the student information,his timetable Student module:view timetable information,view all the courses The students and lecturers can only view the data but cannot modify them.only administrator can modify the data. Every user i.e.,student and lecturer will be provided with unique usernames and passwords.to view the information they first need to login and then view the timetable.

REQUIREMENT ANALYSIS

3.REQUIREMENT ANALYSIS

3.1.Functional requirements: 3.1.1.Admin Module:

Admin provide the courses information and he can view the courses information Admin adds different subjects to course Admin registers the lecturers View the lecturers available information View the student details Provide information to the system for timetable generation Access the registered student details and approve them

3.1.2.Lecturer Module
Login into the system View student details View the courses information View the timetable information View the course particular lab and subject details

3.1.3.Student Module
Login into the system View academics information View course information View timetable information 7

3.2.Non-functional requirements
Secure access of data Better component design to get better performance at peak time Flexible service based architecture will be highly desirable for future extension

3.3.Software requirements
Operating Systems Interface Client-side Scripting Programming Language Web Applications Database Server Deployment : : : : : : : Windows XP/2003 or Linux HTML,CSS Javascript Java JDBC,Servlets,JSP Oracle Tomcat5.x

3.4.Hardware Requirements
Processor Hard Disk RAM : : : Pentium IV 40GB 512MB or more

FEASIBILITY STUDY

4.FEASIBILITY STUDY

4.1.Technical feasibility
Evaluating the technical feasibility is the trickiest part of a feasibility study.This is because,at this point in time,not too many detailed design of the system,making it difficult to access issues like performance,costs etc.A number of issues have to be considered while doing a technical analysis. Understand the different technologies involved in the proposed system:Before commensing the project,we have to be very clear about what are the technologies that are to be required for the development of the new system. Find out whether the organization currently possesses the required technologies:Is the required technology currently available with the organization?If so is the capacity sufficient? For instancewill the current printer be able to handle the new reports and forms required for the new system?

10

4.2.Operational feasibility User-friendly

The forms and reports used in the system must be in such a way that they are easily understandable by user and make the user feel comfortable in using the system.

Reliability
The package will pick up current transactions on line.regarding the old transactions,user will enter them into the system.

Portability
The application will be developed using standard open source software like jav,tomcat webserver,internet explorer browser etc.so,portability problems will not occur.

Maintainability
This system uses 2 tier architecture.1st tier is the GUI,2nd tier is the database which uses sql as back end.The front end can run on different system.The database will be running at the server.users access these forms by using the user ids and passwords.

4.3.Economical feasibility
Economical feasibility attempts to weigh the costs of developing and implementing a new system,against the benefits that would accrue from having the new system in place.This feasibility study gives the top management the economic justification for the new system. A simple economic analysis which gives the actual comparison of costs and benefits are much more meaningful in this case.In addition,this provides to be a useful point of reference to compare actual costs as the project progresses.There could be various types of intangible benefits on account of automation.These could include increased customer 11

satisfaction,improvement in product quality,better decision making,timeliness of information,expediting activities,improved accuracy of operations,better documentation and record keeping,faster retrieval of information. This document play a vital role in the development life cycle as it describes the complete requirement of the system.It means for use by developers and will be the basic during testing phase.any changes made to the requirements in the future will have to go through formal change approval process.

12

SYSTEM ANALYSIS

13

5.1.Class diagram:

StudentMaster package Connection con=null package PreparedStatement ps=null package Statement st=null public boolean registerStudent(StudentMasterBean sbean) public ArrayList getStudentList() public StudentMasterBean getStudentByid(int id)

Lab package Connection con=null package PreparedStatement ps=null package Statement st=null public boolean addLab(LabBean lBean) public ArrayList getLabs() public LabBean getLabByid(int id) public String checkLab(String LabName)

ClassMaster package Connection con=null package PreparedStatement ps=null package Statement st=null package resultset rs=null public boolean addClass(ClassMasterBean cBean) public boolean addClassSubjects(ClassMasterBean cBean) public boolean addClassLabs(ClassMasterBean cBean) public String checkClass(String classname) public ArrayList getClasses() public ArrayList getClasseStudents(int id) public ArrayList getClassLabs(int id) public int getNoOfLAbs(int cid) public int getNoOfSubs(int cid) public String getClassName(int cid)

DbCon package Connection con=null package PreparedStatement pst=null public connection getconnection() public int getsequenceid(string tname,string tfield) public string logincheck(usermasterbean ubean) public int getLoginid(usermasterbean ubean) public boolean changePassword(usermasterbean ubean)

Subject package Connection con=null package PreparedStatement ps=null package Statement st=null public boolean addSubject(SubjectBean sBean) public ArrayList getSubjects() public SubjectBean getSubjectByid(int id) public String checkSubject(String labname)

Lecturer package Connection con=null package PreparedStatement ps=null package Statement st=null

public boolean registerlecturer(LecturerMasterBean sbean) public ArrayList viewLecturerList() public LecturerMasterBean getLecturerByid(int id)

ClassRoom package Connection con=null package PreparedStatement ps=null package Statement st=null Public boolean addClassRoom(ClassRoomMasterBean crBean) Public String checkClassRoom(String cname) Public ArrayList getClassRoom() public ClassRoomMasterBean getClassRoomByid(int id)

14

5.2.Sequence diagrams:

View timetable:faculty

Faculty Login detail

Login

Timetable Controller

TIMS

Validation&verification

Input screen

Start&end date Send for validation

Validation&verificatio n

Send for retrieval

Fetching the information Free slot +allocated slot time table

15

View timetable:student

Student Login details

Login screen

Timetable controller

TIMS

Verification&validatio n Input screen

Ssends branch,year Sends for validation

verification Sends for information

Fetching information Detail time table

16

View Timetable:Admin

Admin Login details

Login screen

Timetable controller

TIMS

Input screen

Verification&vaidatio n

Semester,year

Send for verification Verification&validation

Sends for information

Fetching information

Details about work load assignment and free and allocated class

17

5.3.Usecase diagram
View faculty details

student

View time able

Log out

Change password

login

Create faculty

Create student

Create user Give preference faculty View free slots

Add sub_to_pgm Admin

Create subject/remove subject

Add stud-to-pgm 18

SYSTEM IMPLEMENTATION

19

6.1.SAMPLE CODE

import java.io.*; 002 class staff {

003 String name[]=new String[100]; 004 String desi[]=new String[100]; 005 String sub1[]=new String[100]; 006 String sub2[]=new String[100]; 007 String lab[]=new String[100]; 008 } 009 class department { 010 String name []=new String [100]; 011 int year[][]=new int[100][]; 012 int days[][]=new int[100][]; 013 int periods[][]=new int[100][]; 014 String sec[][]=new String[100][100]; 015 String sub1[][]=new String[100][100]; 016 String sub2[][]=new String[100][100]; 017 String sub3[][]=new String[100][100]; 018 String sub4[][]=new String[100][100]; 019 String sub5[][]=new String[100][100]; 020 String sub6[][]=new String[100][100]; 021 String lab1[][]=new String[100][100]; 022 String lab2[][]=new String[100][100];

20

023 String lab3[][]=new String[100][100]; 024 String rooms[][]=new String[100][100]; 025 String lab[][]=new String[100][100]; 026 } 027 class inpu{ 028 public static void main(String args[]) 029 throws IOException 030 { 031 staff sf = new staff(); 032 department dp = new department(); 033 BufferedReader br =new BufferedReader(new InputStreamReader(System.in)); 034 String str[]=new String[100]; 035 String st; 036 int i,k=1,l,m=0,o=0,q,d,p; 037 System.out.println("\t Enter the total number of staff "); 038 st=br.readLine(); 039 i=Integer.parseInt(st); 040 for(int j=1;j<=i;j++) 041 { 042 043 System.out.println("\n \tEnter the staff" + k +" details"); 044 System.out.println("\n Enter the staff name"); 045 sf.name[j]=br.readLine(); 046 System.out.println("\n Enter the staff Designation"); 047 sf.desi[j]=br.readLine(); 048 System.out.println("\n Enter the subject1");

21

049 sf.sub1[j]=br.readLine(); 050 System.out.println("\n Enter the subject2"); 051 sf.sub2[j]=br.readLine(); 052 System.out.println("\n Enter the lab"); 053 sf.lab[j]=br.readLine(); 054 k++; 055 } 056 057 String dt,sb,yr,se,dy,pe; 058 System.out.println("\n \t Enter the total number of department"); 059 dt=br.readLine(); 060 l=Integer.parseInt(dt); 061 k=1; 062 for(int j=1;j<=l;j++) 063 { 064 065 System.out.println("\n \t Enter the department" + k +" details"); 066 System.out.println("\n Enter the department name"); 067 dp.name[j]=br.readLine(); 068 System.out.println("\n Enter the number of semester "); 069 yr=br.readLine(); 070 m=Integer.parseInt(yr); 071 for(int n=1;n<=m;n++) 072 { 073 System.out.println("\n \t Enter the " + n + " semester details "); 074 System.out.println("\n Enter the no. of sections ");

22

075 dp.sec[j][n]=br.readLine(); 076 System.out.println("\n Enter the subject1"); 077 dp.sub1[j][n]=br.readLine(); 078 System.out.println("\n Enter the subject2"); 079 dp.sub2[j][n]=br.readLine(); 080 System.out.println("\n Enter the subject3"); 081 dp.sub3[j][n]=br.readLine(); 082 System.out.println("\n Enter the subject4"); 083 dp.sub4[j][n]=br.readLine(); 084 System.out.println("\n Enter the subject5"); 085 dp.sub5[j][n]=br.readLine(); 086 System.out.println("\n Enter the subject6"); 087 dp.sub6[j][n]=br.readLine(); 088 System.out.println("\n Enter the lab1"); 089 dp.lab1[j][n]=br.readLine(); 090 System.out.println("\n Enter the lab2"); 091 dp.lab2[j][n]=br.readLine(); 092 System.out.println("\n Enter the lab3"); 093 dp.lab3[j][n]=br.readLine(); 094 System.out.println("\n Enter the no.of class rooms "); 095 dp.rooms[j][n]=br.readLine(); 096 System.out.println("\n Enter the no. of labs "); 097 dp.lab[j][n]=br.readLine(); 098 099 100

23

101 System.out.println("\n Enter the no.of working days "); 102 dy=br.readLine(); 103 d=Integer.parseInt(dy); 104 System.out.println("\n Enter the no.of periods "); 105 pe=br.readLine(); 106 p=Integer.parseInt(pe); 107 108 109 } 110 k++; 111 } 112 113 } 114 }

24

SYSTEM TESTING

25

7.SYSTEM TESTING

Testing:
The process of executing a system with the intent of finding an error. Testing is defined as the process in which defects are identified,isolated,subjected for rectification and ensured that product is defect free in order to produce the quality product and hence customer satisfaction Quality is defined as justification of the requirements Defect is nothing but deviation from the requirement Testing can demonstrate the presence of bugs not their absence

7.1.Testing methodologies: 1.Black box testing: It is the testing process in which tester can perform testing on an
application without having any internal structural knowledge of application. Usually test engineers are involved in the black box testing

2. White box testing: It is the process in which tester can perform testing on an
application with having internal structural knowledge. Usually developers are involved in the white box testing.

3. Unit testing: Unit testing is done on individual modules as they are complete and
become executable. It is confined only to the designers requirements.

4. Integration testing: Integration testing ensures that software and subsystems work
together a whole. It tests the interface of all the modules to make sure that the modules behave properly when integrated together.

26

5. System testing: It involves in-house testing of the entire system before delivery to
the user. Its aim is to satisfy the user and to show the system meets all requirements of the clients specifications.

7.2.Test planning:
1. Test plan is defined as a strategic document which describes the procedure how to perform various testing on the total application in the most efficient way. 2. This document involves the scope of testing 3. Objective of testing. 4. Areas that need to be tested. 5. Areas that should not be tested. 6. Scheduling resource planning. 7. Areas to be automated, various testing tools used.

7.3.Test development:
1. Test case development(check list) 2. Test preparation procedure(description of the test cases)

7.4.Result analysis:
1. Expected value: the expected behavior of the application 2. Actual value: the actual behavior of the application If the actual behavior is same as the expected behavior then the product is ready for release.

27

7.5.Test Case Document (TCD):

This is the sample test case document for the academic details of student project:

Test scope:
Test coverage is provided for the screen Academic status entry form of a student module of university management system application.

Test scenario:
When the office personals use this screen for the marks entry, calculate the status details, saving the information on students basis and quit the form.

Test procedure:
The procedure for testing this screen is planned in such a way that the data entry, status calculation functionality, saving and quitting operations are tested in terms of GUI testing, Positive testing, Negative testing using the corresponding GUI test cases, positive test cases, negative test cases respectively.

7.6Guide lines for test cases: 1. GUI Test Cases:

Total number of features that need to be checked Look&feel Look for default values if at all any Look for spell check

2.Positive test cases:

The positive flow of the functionality must be considered Valid inputs must be used for testing Must have the positive perception to verify whether the requirements are justified. 28

3.Negative test cases:

Must have negative perception Invalid inputs must be used for test.

29

SCREENS

30

Fig: Student Data Entry

31

Fig: Course Data Entrance

32

Fig: Course Registration Entrance

33

Fig: Resultant Timetable

34

CONCLUSION

35

CONCLUSION

The project is able to successfully incorporate all the requirements specified by the user. Proper care has been taken during database design to maintain data integrity Validation has also been done with most care by considering all the possibilities and requirements of different users to avoid data inconsistency. The project is designed and coded in such a way that further modifications that are needed in the future can be easily implemented without affecting the functionality of the system.

Limitations of the system:

Only the registered lecturers can access the system. Advanced techniques are not used to check the authentication.

Future enhancements:
It is not possible to develop a system that makes all the requirements of the system user.Usser requirement keep changing as the system is being used. Some of the future enhancements that can be to this system are As the technology emerges, it is possible to upgrade the system and can be adaptable to desired environment. Because it is based on object oriented design, any further changes can be easily adaptable. Based on the future security issues, security can be improved using emerging technologies. Sub admin module can be added.

36