Routine Management System

Chapter 1


1.1 Introduction:


Computer, the blessing of the modern world has been casing our day-to-day work in various ways. The new inventions of cutting-edge hardware making the computer system more powerful and computer software are utilizing this power to make things easier for modern world. With this flow of development and with the recent advent of the Internet and World Wide Web various institutions have promoted new technology to do their daily tasks. For this reasons our institution “University Of development Alternative (UODA)” want to make software, which is “University Automation for UODA”.

Now we are in the age of automation. In this age, we feel the importance of automation in all steps of daily jobs. We are trying to develop an automation system which will provide lots of facilities to our University. The total automation system divided into many modules , here our parts is “Routine Management Section” .This is a small part of total automation System but The Routine Management Section creates an environment which facilitate teachers, students and everybody by the management of time scheduling.

With the flow of development we are going to introduce an on line Routine Management System that can be helpful for our University. This online “Routine Management system” intended to be our final year project of University Of Development Alternative (UODA) under the integrated project name “University automation for UODA” in care of Mrs. Kazi Tareen Wali, lecturer, department of CSE, faculty of Engineering.


1.2 Project Life Cycle:


The project life cycle includes various development phases that occur in the life of project starting right from the inception of the project to its final development at the client’s end. The three development phases in a project life cycle are;


• Project initiation
• Project execution
• Project deployment



1.2.1 Project initiation:

The project initiation phase is fist phase of life cycle. This phase involves creating a complete plan for the project, specifying various activities that will be performed and assigning responsibilities to team members on the basis of their skill set.


1.2.2 Project execution:

After the project plan is made and the responsibilities assigned, the actual development of the project starts. The phase in which the actual development of the project takes place is known as the project execution phase. This is the most crucial phase of any project and is subdivided into the following phases;


1. system analysis


• Initial study
• Information gathering
• Feasibility study


2. System design
• Design standard
• High level design & design tools
• Database design
• Logical design
• Construction

3. System implementation


• integration & testing
• post implementation


1.2.3 Project development:

After the project execution phase, the final phase of a project life cycle is the project development phase. In this phase, the deployed at the client side. This phase also involves providing customer support to the client for some specified period of time.

When project is built it may possibly remain error les of more, because several type of modification can take place several times. So for the very first time when we run the database web site we found few problems in tools portions. We fixed this problem including some minor problems immediately, and afterwards the application runs properly.


1.3 Objective of the Module:

 To make a proper time schedule for each of the department of our University, Which is very much helpful for our teachers, students and all of the facilities?
 To make a fully dynamic Routine.
 To make a dynamic routine which is faster then the manual routine system?
 We tried to make a dynamic routine which is error free.
 We tried to make a dynamic routine which is user friendly.
 Understand ethical & professional issues, which are important for software engineering.
 To learned methods of producing software in organized way.
 Understand the concept of software process & software process module.
 Understand in outline, process module for software modules for software requirements engineering, software development, testing & evolution.
 Understand why project planning is essential in all software projects.
 Student can understand how can a software is developing in industrial environment


1.4 Methodology:

Methodology is a collection of procedure, techniques, tools and documentation aids that help the system development in their effort to implement a new information system.

The proposed methodology is planned to meet the objective of online Routine Management System of UODA in an effective way.


Chapter 2


Project Execution and Analysis

2.1 System Analysis:

In this part we discuss all of the query and problem of the routine Management system and try to finding the solution.

2.1.1 What is Routine Management?

Routine management simply means the proper management of any type of work or resource used in an organization, that means which way the organization run, which protocol it maintain and why, what is its time schedule etc.

Each and every Organization must follow a routine because, to complete their total tasks in a sequential way .This process make all types of work so much easier because it maintain a schedule. It makes all types of work faster.


2.1.2 Existing System:

Our existing routine management system is a manual system. The whole system is manually defined and it has some problems. The problems of existing systems are as follows:

1. It is very slow and takes many times.
2. It is very difficult to make a routine.
3. It is not error free.



2.1.3 Propose System:

But now we want to do it automatically. Which will be so easier for Whole University and it has some advantages as follows:


1. Dynamic System
2. Error free
3. User Friendly


2.1.4 Reasons of the changes and major expected benefits:

In our university the courses are fixed, it is not easy to make a routine properly because this process is done manually so it is not well developed and it is very slow, and lost many time to make a routine. And in this manual system we must consider all the information about our students, teachers and classrooms etc but when we try to get the information instantly about any thing like classroom availability or teacher’s availability is not easy.

So present Routine Management system has many obligations and it cannot be easy and time consume. If we can establish automation for Routine management system we can able to remove most of the problem.


2.2 Fact Finding Technique:

In order to develop the process model of the new system at first the system analysis the requirement analysis of the proposed system had to be done. During system analysis and requirement analysis of our Routine Management System we have taken the following fact finding Techniques

1. Interviewing
2. Questionnaires
3. Observation


2.2.1 Interviews Structures:

Our goal is to implement to a new system and to overcome the drawbacks of the existing system. That’s way we have to go through an interview process which will give necessary information about the project requirements and help to solve a problems as well as fulfill in the user requirements

For this purpose we have to select the project to be interviewed as an interviewer we must give priority to the users those who are involved with our Routine Management System. In this regard, we discussed with them about our proposed Routine Management System and wanted to know about the problems of existing Routine Management System. We will also try to collect their opinions about the development of our system, which will help us including new system or add new features.


2.2.2 Questionnaires:

Questionnaires provide an alternative to interviews for finding out information about a system. We would like to add following questions for gathering requirements:


What is your present system?

1. What kind of system you use at present?

 Manual  Automatic



2. Are you satisfied with your present system?

 Yes  No



3. Do you have any Paper or Document related to your present System with respect to your University?

 Yes  No

4. If there is no system then what kind of system you want?

 Manual  Automatic

5. If the system is Automatic then which one is used?

 Static  Dynamic

6. If the system is static then what kind of problem you face?





7. If the existing system is dynamic then how it works?

 Direct upload to the web page  First type the document or information, and then upload to the web page


8. If you want static, then why?




9. If the page upload automatically then what will be the file extension?

 .pdf  .doc  .ppt  .pdf & .ppt  .doc & .ppt

10. Who will update the page?

 Authority  Teacher  Student  Both

11. Upcoming Routine Management System and short description will be mentioned or not?

 Yes  No

12. Published Routine Management System can be updated after publishing or not?

 Yes  No



13. Will there any option to search the Routine Management System or not?

 Yes  No

14. How would you like to see the Routine Management System?

 World Wide Web (www)  Internal network



2.2.3 Observation:

AS the student of UODA we were already familiar with some existing procedure. Yet we communicated with the administrative level personnel to know all the specific activities as stated.


• How the information are stored
• How the teacher information are stored
• How the subject information are stored
• How they store multiple tasks information’s
• What type of permission exist among the relations


2.3 Project Phase analysis:

Project phases

We divided our whole work of the project into the following developing phases.

2.3.1 Phase 1: Analysis the requirements of the project.

In this phase we basically analysis the requirements and develop our knowledge on demand. We will sort out all the necessary tools that will be needed. We will grow up the technological background to make workable the software in all environment and network facilities.

2.3.1.1 Requirement Analysis:

We should need to analyze for the routine management the following things—

• A teacher can take only one class at a time.
• We must need to know the number of student for the individual Batch or Semester
• We need to consider how many class rooms are there and we must need to know the capacity of the room.
• We should need to arrange some common class which are similar for both (CSE & ETE)
• We should need to conscious about individual subjects credits which is not equal for the different subjects. (Such as 3 credit course, 2 credit course, 1 credit course).
• The time duration of the different class will be different for their varying different credit hours

2.3.1.2 The method of collecting requirements:

 Reading books & related reference book.
 Internet Browsing.
 Talking with the students, our friends who are interested to help us by giving information about routine.
 Talking with our supervisor & other teacher who are experienced to make routine and working with the automation.
 Talking with Programmer or experienced people who are working this type of related sector.



2.3.2 Phase 2: Module Analysis

In this phase we will analyses our module and fragment the overall module in some small modules. Which help us to complete total system easily.

2.3.3 Phase3: Develop Modules

We will make the task flow and code flow of each module in this phase. We will write the row code to build up the modules.


2.3.4 Phase 4: Integrate Modules

In this phase we will integrate all modules. The backbone of the software will stand up in this phase and the software will be useable.


2.3.5 Phase5: Test, bug finding and bug fixing

We will test the overall features of the software. By testing the features we will find out the bugs. After that all the bugs will be solved.

2.3.6Phase 6: Use of the software

This software will be use for Our University Automation System for routine management



Chapter: 3



3.1 System Design Model:

In our Routine Management System there are two types of User models are shown

These are:

1. Normal User
2. Administrator



3.1.1 Normal User:

A regular user is any kind of user like students, teachers or any body who uses the system and can see the routine and get some information about the routine or time schedule.



3.1.2 Administrator:

An admin user is a selected user who has the permissions to create a new routine or edit the routine. The admin user also viewing the routine and get some information.


3.2 Use case model
Overview of the use cases model of our proposed system” Routine Management System”.


Fig: 3.1 Use case diagram of proposed Routine Management System.


Chapter 4

Database Design

4.1 Normalization:

Data structure is refined through a process called normalization. Data are grouped in the simplest way possible so that later changes can be made with a minimum of impact on the data structure. When too many attributes are grouped together to from entities, some attributes are found to be entities themselves. Further Normalization of these entities into attributes linked by common data elements to from relationship improves the effectiveness of the DBMS.

We have decided to use MySql data base. Our database name is “result”. It consists of the following tables:

1. Routine
2. Department
3. Teacher
4. Subject
5. Login table
6. Room


4.2 Contents of the table:

4.2.1 Routine table:
It contains the several fields in routine table. These are:
• Department
• Semester
• Course code
• Teacher id
• Starting time of the class
• Ending time of the class

**In this table the above all fields are included for the routine format

Field Type Attributes Null Default

dept varchar(30) No

sem varchar(15) No

ccode varchar(15) No

teac_id int(11) No 0

teac_name varchar(40) No

st time No 00:00:00

et time No 00:00:00

room_no varchar(30) No

day varchar(20) No

Fig: 4.1 Fields of Routine Table




4.2.2 Department table:
In this table it contains only the department name.
Field Type Null Default

dept_name varchar(40) Yes NULL



Fig: 4.2 Field of Department Table

4.2.3 Subject table:
Subject table contains the following things. These are:
• Department
• Semester
• Subject name
• Credit
• Course code
**The subject table arrange with the above things
Field Type Null Default

dept_name varchar(40) Yes NULL

sem varchar(10) Yes NULL

sub_name varchar(40) Yes NULL

credit int(11) Yes NULL

ccode varchar(15) Yes NULL

Fig: 4.3 Fields of Subject Table






4.2.4 Teacher table:
Teacher table contains the following things. These are:
 Teacher name
 Teacher id
 Department name
**The function of the teacher table is arranging the schedule of the teacher with their teacher id
Field Type Null Default

teac_name varchar(40) Yes NULL

id int(11) Yes NULL

dept_name varchar(40) Yes NULL




Fig: 4.4 Fields of teacher Table

4.2.5 Room table:
Room table contain the following parts: these are
 Student Numbers
 Room number
Field Type Attributes Null Default

std_no int(11) Yes NULL

room_no varchar(30) Yes NULL



Fig: 4.5 Fields of room Table





4.2.6 Log in table:
The login table contains
• User id
• Password
Field Type Null Default

id Varchar(30) No

pass Varchar(70) No



Fig: 4.6 Field of log in Table


Chapter 5

5.0 Work plan:

**We are trying our best to complete our task within three months and complete the total task as follows:


Task ID Task Name Resources
01 Analysis the requirements of the project. Jashim Uddin
Palash Chandra Das
Syed Samsuzzoha
02 Module Analysis Jashim Uddin
Palash Chandra Das
Syed Samsuzzoha
03
Develop Modules Jashim Uddin
Palash Chandra Das
Syed Samsuzzoha
04 Integrate Modules
Jashim Uddin
Palash Chandra Das
Syed Samsuzzoha
05 Testing, bug finding and bug fixing
Jashim Uddin
Palash Chandra Das
Syed Samsuzzoha
06 Release the software and Reserve Jashim Uddin
Palash Chandra Das
Syed Samsuzzoha

Fig: 5.1 Complete task Table

5.1 Tools for design, analysis and Programming:


5.1.1 Design Tools Used:

HTML, HTML Editor, Browser (Internet Explorer, Netscape Navigator, Mozilla etc).

• Client Side and Server Side Scripting :
o PHP
o Javascript
o HTML

• Database Used as Back End:
o MySQL
• Web Server Used:
o Apache



5.1.2 About the Design Tools


5.1.2.1 What is PHP?
• PHP stands for PHP: Hypertext Preprocessor
• PHP is a server-side scripting language, like ASP
• PHP scripts are executed on the server
• PHP supports many databases (MySQL, Informix, Oracle, Sybase, Solid, PostgreSQL, Generic ODBC, etc.)
• PHP is an open source software (OSS)
• PHP is free to download and use
5.1.2.2 What is a PHP File?
• PHP files may contain text, HTML tags and scripts
• PHP files are returned to the browser as plain HTML
• PHP files have a file extension of ".php", ".php3", or ".phtml"




5.1.2.3 What is MySQL?
• MySQL is a small database server
• MySQL is ideal for small and medium applications
• MySQL supports standard SQL
• MySQL compiles on a number of platforms
• MySQL is free to download and use



5.1.2.4 PHP + MySQL
• PHP combined with MySQL are cross-platform (means that you can develop in Windows and serve on a Unix platform)
5.1.2.5 Why PHP?
• PHP runs on different platforms (Windows, Linux, UNIX, etc.)
• PHP is compatible with almost all servers used today (Apache, IIS, etc.)
• PHP is FREE to download from the official PHP resource: http://www.php.net/
• PHP is easy to learn and runs efficiently on the server side
5.1.2.6 What is Apache?

Apache is an HTTP server, originally designed for UNIX systems. This is the version of Apache for Microsoft Windows 2000, NT, 98, and 95 systems. Like the UNIX version, it includes many frequently requested new features, and has an API that allows it to be extended to meet users' needs more easily. It also allows limited support for ISAPI extensions.



Apache performs best, and is still most reliable on Unix platforms. Over time the performance, reliability and security for the Apache Win32 port has improved, and continues to improve. Folks doing comparative reviews of web server performance are still asked to compare against Apache running on a Unix platform such as Solaris, FreeBSD, or Linux.


5.1.2.7 What Is HTML?

The explosive growth of the World Wide Web is relatively unprecedented, although it resembles the desktop publishing revolution of the early and mid-1980s. As personal computers became more common in homes and offices, people began to learn to use them for document creation and page layout. Although early word processing programs were not terribly intuitive and often required memorizing bizarre codes, people still picked them up fairly easily and managed to create their own in-house publications.
Suddenly, the same kind of growth is being seen as folks rush to create and publish pages of a different sort. To do this, they need to learn to use something called the Hypertext Mark-up Language (HTML).
The HTML standard is maintained and debated by a group called the HTML Working Group, which, in turn, is a creation of the Internet Engineering Task Force. The Working Group was charged in 1994 with the task of defining the HTML standard that was in widespread use on the Web at the time (known as HTML 2.0), and then submitting proposals for future standards, including the HTML 3.0 standard.



5.2 Conceptual model of our proposed Routine Management system:





Fig: 5.2 Conceptual model of Routine Management System .



5.3 Consideration For essential factors:

With the respect of dependability the critical analysis is consists of the following parts:

1. Availability
2. Reliability
3. Time Scheduling
4. Teacher Schedule
5. Rooms facilities
6. Safety & Security


The critical analysis of Routine Management System is described below:

5.3.1 Availability: Though our system is fully an online system and automatic. That why any student and any person can see the system any time from any where by using internet.

5.3.2 Reliability: We will gather all the information’s by separating into different categories. All the advices will be discussed by the experts. So, users can get full reliability.

5.3.3 Teacher Schedule: We should need to maintain the all teacher schedule of his/her class in the proper way


5.3.4 Time Scheduling: When we start to make the Routine this time we should be sincere about the Teacher time schedule and the duration of the class.



5.3.5 Room’s facilities: We need the clear idea about every room accommodation and its capacities for distribute the proper class in the proper room.


5.3.6 Safety & Security: We will use the languages My SQL, HTML and PHP. The security level of our project-Routine Management System is very high. Because in this project the normal user only can see the routine of different semester and gather some information about our teachers that means anybody can see the teacher’s personal routine from module but they can’t change or update anything. But the administrator can do any thing. Administrator is the only person who can add department, add semester, add teachers, add subject and add rooms. He can also delete everything. Only he can create the new routine and drop update the routine.



Chapter 6


6.0 Software layout:

In this portion we describe the using process of the software.

6.1 How to Use

There are several options for using this web system

RMS Home page:



Inputs and Outputs

The Input and Output of the various pages on this web based project are given bellow:

1. LogIn
2. Category Search
3. Insert information
4. Update Information
5. Log out

6.2 LogIn

Input page:

6.2.1 Output page (if login success):



6.2 Steps: How to Use

6.2.1 Step 1:

After Signing in the administrator option the admin can do all type of access for editing or updating the routine.

6.2.1.1 Add Department:

Web Page for adding new Department


This page will be display when we want to add new Department in the database.


6.2.1.2 Add Subject:

Web Page for adding new subject:

This page will be display when we want to add new subject in the database.


6.2.1.3 Add new Teacher:

Web Page for adding Teacher:

This page will be display when we want to add new Teacher in the database.


6.2.1.4 Add new Room:

Web Page for adding new Room:

This page will be display when we want to add new Room in the database.


5.2.2 Step 2:

5.2.2.1 Make new Routine:


After completing the input Data an administrator easily can make a routine what he/she wants.


In this part the administrative user select those data which essential for particular department and particular semester which already inserted in data base.

And then submit the data. After submitting a routine will be shown below:

Show Routine:


5.2.3 Step 3:

In step 3 if the administrator thinks in the database there are some unnecessary information he/she can delete the information from the database by using the following steps:

5.2.3.1 Delete Subject:

Web Page for Delete Subject:

This page will be display when we want to delete subject from the database.


5.2.3.2 Delete Teacher:

Web Page for Delete teacher:

This page will be display when we want to delete teacher from the database


5.2.3.3 Delete Room:

Web Page for Delete Room:

This page will be display when we want to delete Room from the database


5.2.4 Step 4:

In this part if the administrators think there is some problem in any routine he/she easily can drop the routine for particular day or whole routine at a time.

5.2.4.1 Drop Routine:

Web page for drop routine:

After selecting the information what we want to drop from the routine then it will be show this page:
In this page there are two options for dropping routine one for dropping particular subject routine for particular day and another for dropping full routine


Chapter 6:



Chapter 7:


7.1 Limitation:

**We think There Are few limitation in our software
These are follows:

• We can’t divide the large semester
• We can’t make exam routine
• In our software we use Teachers id which will be difficult to remember



7.2 Post implementation

After implementing and testing the database web site we found that it almost fulfilled all of the requirements of our abstract and system designing considerations. The application is working smoothly for all its users, such as see the routine of any department for particular semester. Adding teacher information. In further we will try to solve our limitation and we are hopeful next time it will be a complete dynamitic Routine generating Software.


7.3 Discussion

To write discussion phase we should make on thing clear at the very beginning-although the l structure of a routine system is very complex, we took a professional approach, and designed the project in the best possible way so that it could be used instantly by any interested organization.



7.4 Conclusion


Website development is a continuous process. In near future there is a plan that this site will be a complete dynamic routine generating system. Ultimate destination for the user to get information about routine very easily.

At the end of this project we hardly request to the faculties of Computer Science and Engineering (CSE) to approve our project.