Women Centralized Timetable Management System (1) PDF

Preview

Summary

This is my personal assignment...

Description

WOMEN CENTRALIZED TIMETABLE MANAGEMENT SYSTEM

SUBMITTED BY:

Javeria Ahmad

BSIT-17-31

Ayesha Khalid

BSIT-17-19

Aqsa Bibi

BSIT-17-37

SUPERVISED BY:

Ms. Tanzeela Kausar

INSTITUTE OF COMPUTER SCIENCE & INFORMATION TECHNOLOGY (CS&IT) WOMEN UNIVERSITY,MULTAN PAKISTAN

Thesis Approval Form

This is to clarify that the work contained in this thesis entitled “WUM centralized timetable management system” carried by Javeria Ahmad, Ayesha Khalid, Aqsa Bibi in our opinion is fully adequate, in scope and quality, for the degree of BS Information Technology from Women University Multan (WUM).

Approved by:

Signature: Name: Ms. Tanzeela Kousar Women University, Multan Internal Examiner/supervisor

Signature: Name: Women University, Multan External Examiner Verified by: Signature: Name: Ms. Meherwar Fatima Head Of CS Department Women University, Multan

2

DECLARATION OF ORIGINALITY

We declare that this report entitled “WUM Centralized Timetable Management System” is our own work except as cited in the references. The report has not been written for any official or un-official usage and is not being submitted concurrently in candidature for any degree or other award.

Signature

: _________________________

Name

: _________________________

Date

: _________________________

DEDICATION

3

With due respect we dedicate our work to our “Parents” who bought us up in a way that we are able to learn skills and use our knowledge in a useful purpose and our “Teachers” who teach us the skills and leads us to use our knowledge in a right way.

ABSTRACT

4

Our Final Year Project WUM CENTRALIZED TIMETABLE MANAGEMENT SYSTEM is online web-based system for ease and assist to create precise timetable of the institute (different departmental classes) with respect to different aspects and requirements. Timetable is essential part of any educational institute, as without planning and scheduling no class can be organized in a proper way. Mostly timetables here are made manually that takes much more time energy and eventually they are never precise. Our work is to overcome these scheduling issue and generate an automatic timetable system that create and update the timetable by concerning all components that effect or are including in it. Our idea is to generate a system that will accept input of time, subject, session, room and other class details from faculty and admin to create error free, nonclashing timetable automatically and it will be displayed with different aspect as per need of the user.

ACKNOWLEGEMENT 5

 We would like to express my profound gratitude to Almighty Allah the Gracious and Merciful Who give me health and help me in every critical situation and provide me courage to face all ups and downs of life without losing heart. Allah never let effort go waste. Trust on Allah His Prophet Muhammad (Peace Be Upon Him) always bear fruit.  “We would like to express our special appreciation and thanks to Our Supervisor Ms. Tanzeela Kousar , who has guided us very well and has been a marvelous mentor for us. We would like to thank her for encouragement and cooperating attitude. ”  We offer our humble gratitude to our affectionate Mothers (Shahida Shafiq, Samina Kausar, Irshad bibi), Our Fathers (Rana Shafiq Ahmad Noon, Khalid Hussain, Muhammad Ismail), Our siblings Junaid, Umaima, Noor and other, all cousins specially Fakher Hussain, Palwasha Marium and all Our family members for their help, unlimited prayers and support that sustain me at many ordeals during my education carrier.

6

CONTENTS

TITLE PAGE………………………………………………….

Thesis Approval Form………………………………………… Declaration Of Originality……………………………………. Dedication……………………………………………………… Abstract………………………………………………………… Acknowledgements…………………………………………….. List of Figures…………………………………………………..

1. Chapter 1 : Introduction…………………………………………

1.1 Overview…………………………………………….. 1.2 Problem Statement…………………………………... 1.3 Purpose………………………………………………. 1.4 Scope………………………………………………… 1.5 Objectives……………………………………………. 1.6 Project Process………………………………………..

7

2. Chapter 2: Literature Review…………………………………….

2.1 Study of University Existing System…………………….. 2.2 Studies of Overall Existing Systems………………...…… 2.3 Outcomes of Existing Timetable Systems……………….. 2.4 Problems in Existing Timetable Systems…………………

3. Chapter 3 : Methodology…………………………………….…….

3.1 What is that methodology?........................................................... 3.2 Working of methodology?.................................................................. 3.3 When in this methodology used?........................................................... 3.4 Why is this methodology used?........................................................... 3.5 How is this methodology used?.............................................................. 3.6 Technologies Involved ..................................................................... 3.7 Hardware Requirement .................................................................... 3.8 Software Requirement......................................................................... 3.9 Feasibility Stud………………………………………………..

4. Chapter 4 Requirement specification.....................................................

4.1 Target user................................................... 4.2 Requirement Gathering ........................................................................ 4.3 Functional and Non-Functional Requirement ....................................... 8

5. Chapter 5 : Proposed System.............................................

5.1 Users ………………………………………………………………….. 5.2 Feature…………………………………………………………….. 5.3 Component……………………………………………………………… 5.4 Modules……………………………………………………….. 5.5 Functionalities for Admin and Department Admin ………………… 5.6 Working ……………………………………………………….

6. Chapter 6 : System Design..................................................

6.1 Activity Diagram………………………………………………………. 6.2 Data Flow Diagram .............................................................................. 6.3 System Core Diagram…………………………………………………. 6.4 Entity Relationship Diagram ............................................................. 6.5 Class Diagram………………………………………………………..

7. Chapter 7 : Interface...........................................................

7.1 Index…………………………………………………………… 7.2 Admin Panel……………………………………………………… 7.3 Department Admin panel…………………………………………. 7.4 Teacher panel………………………………………………………… 7.5Timetable panel………………………………………………… 9

8. Chapter 8 : System Implementation..................................

9. Chapter 9 : System Testing................................................

9.1 Unit Testing........................................................................................... 9.2 Functional Testing..................................................................................

10. Chapter 10 : Limitation and Future Enhancement

11. Chapter 11 : Conclusion

REFRENCES

TERMINOLOGY

WUM – women university Multan CTMS - centralized timetable management system

10

WUMCTMS - women university Multan centralized timetable management system FYP – final year project DB - database TMS – timetable management system ERD – entity relationship diagram DFD – data flow diagram UML – unified modeling language

LIST OF FIGURES

Figure 3.1……………………………………………………………….. 11

Figure 3.2……………………………………………………………….. Figure 6.1……………………………………………………………….. Figure 6.2……………………………………………………………….. Figure 6.3……………………………………………………………….. Figure 6.4……………………………………………………………… Figure 6.5………………………………………………………………… Figure 6.6……………………………………………………………… Figure 6.7……………………………………………………………… Figure 6.8………………………………………………………………… Figure 6.9………………………………………………………………….. Figure 6.10……………………………………………………………… Figure 6.11…………………………………………………………….. Figure 6.12………………………………………………………………. Figure 6.13………………………………………………………………

Chapter 1 : Introduction

1.1 Overview 12

Woman University Multan Centralized Timetable Management System (WUMCTMS) is a Web-based Open-Source system, which is built to automate timetable system using MySQL and PHP language. It provides high flexible features for managing the schedules of study for students in university. University timetable construction is hardworking and complicated task when there are large number of course arrays and limited resources. As a result, we tend to solve this issue manually even then results may not always fully optimal. In this project, we solve this problem by a framework of timetable management system to create timetable automatically. Our endeavor through the overall research was to develop an automated timetable management system for our - WOMAN UNIVERSITY MULTAN to overcome the scheduling issues. We conducted a preliminary study and hypothesized to convert the manual timetable creation and management to automatic system, by using different database queries, coding languages for internal and external programming, and solve the technical issues faces in automatic centralized timetable system. It enables users to see all their subject, classes, rooms, and timing in one place. The timetables are created automatically by the data given by the faculty. Administrative person of each department is given special permissions data in any uneventful condition specifically in all departments, and years of study.

1.2 Problem Statement

Timetable generation is tedious job for educationalist with respect to time and manpower. The difficulty faced during timetabling can be represented as a constraint satisfaction problem with loose parameters and many constraints. These 13

constraints can be replicated in a format which can be managed by the scheduling techniques in an organized manner. The scheduling involves allowing for a many a pair wise constraints using which tasks can be accomplished simultaneously.

1.3 Purpose The purpose of the project is to build program to reduce the manual work for managing the Timetable, Faculty, Semester, Subject. It tracks all the details about the Subject, Student, Course. The Timetable system is a very useful system for Students, Faculties & Administrator through which students/VC/parents can get the information about them/their schedule. This is also useful for faculties through which they can view when its classes are. Administrator can add remove data, faculties can adjust their subjects and timings as per their need.

1.4 Scope Providing an automatic timetable generator will help to generate timetable automatically. Proposed system of our project will help to generate timetable automatically and helps to save time. It avoids the complexity of setting and managing timetable manually. It Can be used in every educational institute as it is an essential part of educational system to schedule classes efficiently and view in all prospects on the university platform.

14

1.5 Objectives The main objective of developing this system is following: To generate feasible and quality timetable To make the system user-friendly To make the system easy to maintain. The system should be flexible enough that it can be modified in future to address any form of constraints in real time phenomenon.  Ensure robustness of system and provide a feasible solution to any big problem.  Manage the details of Timetable, Faculty, Subject, Student, Semester, Course.  The project is totally built at administrative end and thus only the administrator is guaranteed the access.     

1.6 Project Processes We used Incremental and Iterative Development process to create our project because as our system is generalized for all departments and session, it needs to be changed and updated every time till the product must be developed and this system suits the best for our Timetable creation through CTMS.

15

Chapter 2 Study on University Existing System

2.1 Study on University Existing System

16

There is no concrete timetable management system in Woman University Multan currently. University do not publish a master timetable online and even the timetable is created manually it takes so much time and effort, but the result is even not precise.

2.2 Studies on Overall Existing Systems

The existing systems are that are generated or introduced in the institutes are not fully automatic. Timetable Management System contains a database, which stores the staff and student’s personal details. Only the administrator can view, add, and delete the data in the timetable. The system introduced are not generator they more over accept input and show output in a particular programmed structure. More work is done by the user neither by the system.

2.3 Problem in Existing Systems

The existing TMS have following Inconsistencies: More work burden is on Administration Updating of schedule is manually replaced with detailing of faculty No Fully Automatic timetable generation No efficient capability of changings No error detection if some has error detection capability than that system cannot configure them  Database of departments are not connected  Some systems cannot manage external subjects and visiting faculty schedule.      

17

Chapter 3 Methodology

3.1 Chosen Methodology

18

The method we chose for developing the web-based application WUMCTMS is incremental and iterative software development process.

3.2 What is Incremental and Iterative development process ? Incremental :Incremental development is a development approach that slices the product into fully working slices that are called increments. Iterative: Iterative development is when teams gradually build up the features and functions but do not wait until each of these is complete before releasing.

FIGURE 3.1 – Concept of INCREMENTAL and ITERATIVE 3.3 Incremental – Iterative Approach

19

FIGURE 3.2- Processing of incremental and iterative approach

Iterative and Incremental development approach is a combination of both iterative design or iterative method and incremental build model for development. "During software development, more than one iteration of the software development cycle may be in progress at the same time." This process may be described as an "evolutionary acquisition" or "incremental build" approach." Iterative and incremental development models are complementary in nature, which is why they are often used together to boost their efficacy and achieve project deliverables.

3.3Working

20

In an Iterative Incremental model, initially, a partial implementation of a total system is constructed so that it will be in a deliverable state. Increased functionality is added. Defects, if any, from the prior delivery are fixed and the working product is delivered. The process is repeated until the entire product development is completed. The repetitions of these processes are called iterations. At the end of every iteration, a product increment is delivered.

3.4When incremental and iterative approach to use This model is most often used in the following scenarios :  Requirements of the complete system are clearly defined and understood.  Major requirements must be defined; however, some functionalities or requested enhancements may evolve with time.  There is a time to the market constraint.  A new technology is being used and is being learnt by the development team while working on the project.  Resources with needed skill sets are not available and are planned to be used on contract basis for specific iterations.  There are some high-risk features and goals which may change in the future.

3.6 Why is iterative and incremental development Approach used ?

The incremental and iterative development process enables project managers to reap the benefits of both incremental and iterative approaches. Incremental development ensures that developers can make changes early in the process rather than waiting until the end when the allotted time has run out and the money has been spent. 21

Iterative development means improvements are made on an ongoing basis, so the result is likely to be delivered on time and be of higher quality.

3.7 How can you benefit from an incremental – iterative approach ?

The complementary characteristics of the above approaches can make the development and release process more effective. Limited ‘Beta’ iterative releases are a way to get early feedback from the users before a full increment is released to all users. It is a good way of de-risking a release and getting early and frequent feedback from the users.

3.8 Technologies Used

 Hardware Requirements (For future implementations)  GSM module ( to send messages to faculty for the reminder of classes)  Software Requirements and Applications  For Coding  PHPstorm  Sublime text

 For Database  Xampp 22

 For Database Host  My PHPadmin

Languages

     

Front-End HTML CSS JAVA script Bootstrap Back-End

 PHP  Database  MySQL

3.9 Feasibility Study

Before beginning to develop this project, it is very important to calculate the feasibility of all aspects of the system, recognize all the constraints, understand the hazardous implications, if any, and return value.

3.10 Operational Feasibility

23

To develop a good web-based system, it is very important to choose the correct hardware, software, and technology, below are some explanations of the hardware software and technology chosen as the development tools for the TMS.

 The potential users of the system are students and university lecturers, administrations which are generally aware of site navigation and management, thus No or very little training level would be required.  The system will provide a simple interface for the users to operate. 3.11 Economic Feasibility

Reduction in manual work will reduce requirement of extra staff. Optimal resource utilization and reduction in wastage in case of class clash and whenever a class is cancelled.

3.12 Legal Feasibility

The proposed system is legally feasible and legal constraints encountered ahead of it will be negligible.

24

Chapter 4 Requirement Specifications

4.1 Target user:

The person who creates the timetable that can be  Faculty  Administration  Department’s administration (clerk) The person who wants to view Timetable with respect to any day, date, time, class, subject, session, program, department, Lecturer. That can be  Student  VC  Faculty  Administrations

4.2 Requirement Gathering

We use the following methods for gathering the requirements     

One to one Interview Group Interview Brainstorming Survey User Requirements

25

4.3 Functional Requirements

       

Automatic Creation of schedule Less data entry Less manual work Automatic detection of conflict Automatic debugging of error All possible data present in database Automatic data fetching from database related to the entry Search for related data required

4.4 Non-Functional requirements

 Security  Authority giv...