Академический Документы
Профессиональный Документы
Культура Документы
A final project Report submitted to the faculty of computing information sciences in partial
fulfillment of requirements for the award of Bachelor degree in Information System and
Management.
Supervisor:
TURIHO Jean Claude
2
DECLARATION
I, IRADUKUNDA Louis Pacifique, hereby declare that the project entitled “LESSON
SCHEDULING AND TIMETABLING SYSTEM” case study “UNIVERSITY OF LAY
ADVENTISTS OF KIGALI” submitted in partial fulfillment of the requirements for the award
of Bachelor’s degree in INFORMATION SYSTEMS AND MANAGEMENT is a record of
Bonafide project work carried out by myself under the guidance of Jean Claude TURIHO
I declare that the work reported in this dissertation has not been submitted, either in part or in
full, for the award of any other degree or diploma in the University of Lay Adventists of Kigali
or in other UNIVERSITIES in Rwanda.
Date……………………... Signature………………………
3
ACCEPTANCE SHEET
This dissertation entitled Lesson Scheduling and Timetabling System (LSTS), Written and
submitted by IRADUKUNDA Louis Pacifique in partial fulfillment of the requirements for the
Bachelor’s Degree of Science in Information System and Management. Is hereby accepted
and approved by:
(Supervisor’s name)
TURIHO Jean Claude
Date Signed
(Dean’s Name)
TURIHO Jean Claude
Dean of Faculty of Computing and Information Sciences
4
Date Signed
ACKNOWLEDGEMENT
I appreciate the care and assistance of the COMPUTING INFORMATION SCIENCE Lecturers
who lectured me with skills needed to complete my Dissertation. My thanks go to my precious
friend UWASE Jokebed for her Assistance while doing this project. I also acknowledge the
Computing Information Science Faculty Students (September intake promotion of 2015) for their
active verbal participation and suggestions towards the evolvement of this project work.
5
TABLE OF CONTENTS
DEDICATION................................................................................................................................ii
DECLARATION.............................................................................................................................ii
ACCEPTANCE SHEET.................................................................................................................ii
ACKNOWLEDGEMENT...............................................................................................................ii
TABLE OF CONTENTS................................................................................................................ii
LIST OF FIGURES.........................................................................................................................ii
LIST OF TABLES..........................................................................................................................ii
ABSTRACT....................................................................................................................................II
1.0 Introduction.......................................................................................................................................2
1.4. Motivation........................................................................................................................................2
1.7. Challenges........................................................................................................................................2
2.1. Introduction......................................................................................................................................2
6
2.2.1. Online........................................................................................................................................2
2.2.4. Website......................................................................................................................................2
2.2.5. Lecturing....................................................................................................................................2
2.2.7. Lecturer......................................................................................................................................2
2.2.8. Faculty.......................................................................................................................................2
2.2.9. Department................................................................................................................................2
2.2.10. Course......................................................................................................................................2
2.4.1. Strength......................................................................................................................................2
2.3.2. Weaknesses................................................................................................................................2
2.3.3. Similarities.................................................................................................................................2
2.3.4. Differences.................................................................................................................................2
2.6. Conclusion........................................................................................................................................2
3.1. Introduction......................................................................................................................................2
3.3. Vision...............................................................................................................................................2
3.4. Mission.............................................................................................................................................2
3.5.1 Timetable....................................................................................................................................2
3.5.2 Timetabling.................................................................................................................................2
7
3.5.3. Timetable Generation................................................................................................................2
4.1. Introduction......................................................................................................................................2
4.5.1. Life Cycle of Developing Lesson Scheduling and Time Tabling System..................................2
5.1. Introduction......................................................................................................................................2
5.2.1 JavaScript...................................................................................................................................2
5.2.2. HTML........................................................................................................................................2
5.2.3. PHP............................................................................................................................................2
5.2.4. Sublime......................................................................................................................................2
8
5.2.5. Click chart Diagram Flow Chart Software.................................................................................2
5.3.1. Programming.............................................................................................................................2
6.1 Conclusion.........................................................................................................................................2
6.2 Recommendation...............................................................................................................................2
REFERENCES................................................................................................................................2
APPENDIX......................................................................................................................................2
LIST OF FIGURE
9
Figure 1database..............................................................................................................................2
Figure 2: A Table............................................................................................................................2
Figure 3: A Class.............................................................................................................................2
Figure 4: Water Fall Model.............................................................................................................2
Figure 5: Use Case Diagram............................................................................................................2
Figure 6: E-R Diagram....................................................................................................................2
Figure 7: Class Diagram..................................................................................................................2
Figure 8: Sequence Diagram For Admin Signin.............................................................................2
Figure 9: Sequence Diagram For Adding Course Timetable..........................................................2
Figure 10: Giving Course To A Class.............................................................................................2
Figure 11: Adding A Lecturer.........................................................................................................2
Figure 12: Physical Data Model......................................................................................................2
Figure 13: Home Page.....................................................................................................................2
Figure 14: Adding A New Lecturer.................................................................................................2
Figure 15: Admin's Dashboard........................................................................................................2
Figure 16: Worked Hours By Lecturers..........................................................................................2
Figure 17: Timetable Generation.....................................................................................................2
Figure 18: Class Report...................................................................................................................2
10
LIST OF TABLES
Table 0-1: Advantage And Disadvantage........................................................................................2
Table 0-2: Lecturer Table................................................................................................................2
Table 0-3: Course Table..................................................................................................................2
Table 0-4: Room Table....................................................................................................................2
Table 0-5: Class Table.....................................................................................................................2
Table 0-6: Assessment Table...........................................................................................................2
Table 0-7: Timetabling Table..........................................................................................................2
11
LIST OF SYMBOLS AND ABBREVIATIONS
12
ABSTRACT
Basically, it can be discovered that the H.O.D has a lot of work while allocating lecturers and
knowing courses done and not done by different studying years and levels and use of paper files
in the Head of Computing and Information Science Faculty, this slows down his work, making
the place untidy and even frightening him from tasks to be accomplished, but it should not be so
in this era or period of paperless and portable office brought in the use of computer system.
Firstly, we have taken the share of untidiness by developing designing an application that would
aid him in allocation of course to the different programs that are offered in Computing and
Information Sciences.
Consequently, our project is restricted to department courses allocation in CIS faculty and their
time table where research show that some courses are allocated on the first semester and second
semester respectively depending on the program whether morning or evening. The electronic
document system is ideal for voluminous data such as those found in the office of the Dean of
Faculty of Computer and Information Sciences at UNIVERSITY OF LAY ADVENTISTS OF
KIGALI (UNILAK), UNILAK is where this research work is embarked on as the case study.
13
CHAPTER 1: GENERAL INTRODUCTION
1.0 Introduction
Over the years allocation of course their credit units and departmental timetable have been
growing from one stage to another and similarly, the procedures and routine embarked on every
semester coupled with the departmental growth compounded the problem of manual allocation
of course their units and thereby delays the registration procedures because some students never
know which courses are allocated while they didn’t reach to school and what lesson is being
studied and the one will be next and some of them get the information very late, computerization
or automation of course and their credit units allocation and departmental time provide the
most effective reliable and quickest services required by the students. Basically, before the
invention of computers, computation was done manually and in the case of the departmental
course, their credit units and departmental timetable, it has caused accelerated progress
especially the automation of department course their credit units and departmental time table.
Computer technology has been accepted as an indispensable innovation in most fields of human
Endeavour in which departmental courses is not an exception.
Hence, the efficiency of the Computing and Information Sciences would be achieved if they shift
from using Microsoft office Excel to the use of computer-based system. However, using the
computer based system in place of the Existing system. It will make the practical insinuation of
high technology upgraded. This will enflame the time needed for processing of departmental
course and attend to other subsequent information needed by the management system. The
important of this research is so prominent with the current of processing the departmental course
and suggest a complete efficient and reliable approach that will be of immense benefit to most
higher institutions in general especially to UNIVERSITY OF LAY ADVENTISTS OF KIGALI
(UNILAK).
1
1.1. Statement of the Problem
And another problem was late allocation of course and credit units to enable the students finish
their registration process and have foresight of what the semester would look like. It was studied
and discovered that automation of departmental course and the manual system of allocation
course, their credit unit usually waste a lot of time and paper can be reduced on the process of
arranging it and also improves on removing such problems. Below are some of the problems in
this system.
Knowing the availability of Lecturers when are they available or not available.
Problem of knowing what lessons have been covered by Levels and different intakes.
Students who miss class without being if the lesson has been covered or not.
The main objective of this Project is to develop a Timetabling System that will be used in
Computing and Information Sciences to help in course allocation in different intakes and Levels.
Meanwhile to the general objective, this system will be involving some of Specific Objective
listed as follow:
Provide quicker and more efficient services i.e. course allocation using automated
system.
Design interface where students can view lesson which being lectured with its starting
period and the ending period.
Creating a database that will store all information that will be inserted by the H.O.D.
Definitely, the complete implementation of this work will be introduced as a trend in the present
method of allocating course their credit units and departmental time table, the change would in-
doubt make the management and students happier, such changes envisage will include the
following:
This research will be a source of information for other researchers who will be interested
in this topic of Lesson Plan to improve on something that I may have forgotten to do.
The time involved in allocating and reallocating which normally results to delay will be
reduced.
Students would then know courses taught wherever they would be according to their
campuses of course.
Automated System would also serve as a reference file for the students and staff since the
course, credit units’ time table will be shown to them.
Lecturers will also know the course to lecture via notification sent to them via email.
1.4. Motivation
By doing this project I was motivated by helping our University and to facilitate H.O.D,
Lecturers and its student especially for COMPUTING AND INFORMATION SCIENCES
3
Faculty for better management and completion of course for the given academic year using this
system.
The interest of this project is that UNILAK will benefit from using an automated system that will
quickens the services rendered by the Department from the HOD’s office at timely basis.
This project will be a mean to demonstrate my learning outcome I gained from UNILAK over
3years period of studying with the aid of my Lecturers.
This study is aimed at finding out how the use of automated system can help in course allocation
in the computing and information science Faculty of UNIVERSITY OF LAY ADVENTISTS OF
KIGALI (UNILAK).
The study will cover only the Faculty of Computing and Information Sciences and its Lecturers
due to some limitations of the researcher to extend the research to other Faculties within the
Campuses of UNILAK (RWAMAGANA, NYANZA, and KIGALI).
Leaving alone other institution’s Faculties and other constraints are as follows:
Time Constraints: Due to the required completion, time of this research work, it was not possible
to extend the research to other departments.
Complexity: Meanwhile extending the research to all departments within institution would lead
to completion and complication resulting to liability of research.
1.7. Challenges
Challenges to bring this work to an end may be defined as difficulties which can prevent the
system working as it is expected. As developers developing a computerized system is not a
simple task, even for a small organization it requires a kind attention and having enough time for
studying about its functionalities and designing it. The process demands to be very attentive and
4
experience in order to meet environment needs. Some of the challenges that I faced in bringing
accurate solution for UNILAK CIS’s faculty problems are the short time allocated to the work
completion and the moderate experience in developing such system.
This Project work is subdivided into six chapters listed as follow from the first chapter to the last
one:
CHAPTER 1
Entitled introduction, we talked about the background of the study, problem statement,
motivation of the work and objective of our project, scope of our study, and interest of study
significance of the project that we hope to reach at the end of this work.
CHAPTER 2
Literature review; I am going to deal with the terminologies, analysis and design methodology
for the proposed system. We will show the methodology used, the system analysis, and the
detailed system design to solve the problem.
CHAPTER 3
The existing system will discuss on with are principle of the existing system, problem found,
proposed solutions.
5
CHAPTER 4: ANALYSIS AND DESIGN OF THE PROPOSED SYSTEM
Here, the new system will focus on the implementation of the system, technologies and the
results obtained as well as the testing of the system.
CHAPTER 6
This is the last chapter in this project. It concludes the project achieved and it states some
recommendations for future work and enhancement.
6
CHAPTER 2. LITERATURE EVIEW
2.1. Introduction
This chapter is all about literature review of a selected topic related to my Project therefore a
literature review is an evaluative report of information found in the literature related to my
selected area of study. The review should describe, summarize, evaluate and clarify this
literature. We will also look at the general terminologies used in this Dissertation and Database
concepts.
2.2.4. Website
A website is a collection of related web pages, including multimedia content, typically identified
with a common domain name, and published on at least one web server. A website may be
accessible via a public Internet Protocol (IP) network, such as the Internet, by referencing a
uniform resource locator (URL) that identifies the site.[ CITATION DrT05 \l 1033 ]
2.2.5. Lecturing
Profession of those who give instruction, especially in an elementary university. [ CITATION
Col14 \l 1033 ]
7
2.2.6. Time table
Any schedule or plan designating the times at or within certain things occur or are scheduled to
occur.[ CITATION Muh10 \l 1033 ]
2.2.7. Lecturer
A person who is in charge of giving a lecture. An academic rank given in colleges and
universities to a teacher ranking below assistant professor[ CITATION Col14 \l 1033 ]
2.2.8. Faculty
One of the departments of learning in a university.[ CITATION Col14 \l 1033 ]
2.2.9. Department
One of the sections of a school or college dealing with a particular field of knowledge: the
Marketing department.[ CITATION Col14 \l 1033 ]
2.2.10. Course
A program of instruction as in a college or university: a course computer science. [ CITATION Col14
\l 1033 ]
8
Figure 1Database
3. Table: table is a set of data elements (values) using a model of vertical columns (identifiable
by name) and horizontal rows, the cell being the unit where a row and column intersect. A table
has a specified number of columns, but can have any number of rows.[ CITATION Dav11 \l 1033 ]
Table name
1 Row
2 Row
3 Row
Figure 2: a table
4 Row
Column
4. Field: a field is an area of database records, or graphical user
interface form, into which a particular item of data is entered.[ CITATION Dav11 \l 1033 ]
5. Record
Record is an ordered set of fields, usually stored contiguously in the database. [ CITATION Col14 \l
1033 ]
9
6. Index
Index: index is a number used to select an element of a list, vector array or other sequence or an
index can be a list of names, subjects and others with references.[ CITATION Pet13 \l 1033 ]
7. An entity
An entity is an object that exists. In database administration, an entity can be a single thing,
person, place, or object. Data can be stored about such entities.[ CITATION Pet13 \l 1033 ]
8. Data security
Data security is the system, processes and procedures that protect a database from unintended
activity.[ CITATION Dav11 \l 1033 ]
9. Data modeling
Data modeling is a process used to define and analyses data requirements needed to support the
business processes within the scope corresponding information systems in an organization.
It is a technique for organizing and documenting a system’s data. Sometimes it is called database
modeling because it is eventually implemented as a database.[ CITATION Dav11 \l 1033 ]
10
11. Database management system
Database Management System (DBMS) consists of an integrated set of computer software that
allows users to interact with one or more databases and provides access to all of the data
contained in the database (although restrictions may exist that limit access to particular data).
[ CITATION Pet13 \l 1033 ]
Database Administrator (DBA) is the expert person to whom responsibility for database system
is assigned. Database administrators (DBAs) use specialized software to store and organize data. [
CITATION urk17 \l 1033 ]
The metadata are the data that describe the properties or characteristics of other data. It provides
information about a certain items contents[ CITATION urk17 \l 1033 ]
14. Relationship
Relationship is an association among the instance of one or more entity types that is of interest to
the organization. Relationship uses arrows to interact one entity and another as data flows from
one entity to another. A relationship, in the context of databases, is a situation that exists between
two relational database tables when one table has a foreign key that references the primary key of
the other table. Relationships allow relational databases to split and store data in different tables,
while linking disparate data items.[ CITATION urk17 \l 1033 ]
15. Cardinality
11
In the context of databases, cardinality refers to the uniqueness of data values contained in a
column.[ CITATION urk17 \l 1033 ]
Data dictionary is a set of information describing the contents, format, and structure of a
database and the relationship between its elements, used to control access to and manipulation of
the database.[ CITATION Him09 \l 1033 ]
12
17. Database connection
18. Attributes
20. Class
13
Is a type of static structure diagram that describes the structure of a system by showing the
system’s classes, their attributes, operations (or methods), and the relationships among objects.
ClassName
-Attribute 1
-Attribute 2
-Attribute 3
+Operation 1()
+Operation 2()
+Operation n()
Figure 3: A Class
There are many researchers who made research on topic mentioned above and they just defined
it in their own terms. According to [ CITATION Lin16 \l 1033 ] defined Timetable Management
System (TMS) as a system of developing the Timetable Management System is to have a quality
and feasible timetable which is to improve the current system by using electronic device for
allocating the plan of work in the enterprise.
According to [ CITATION Mic17 \l 1033 ] they defined Efficiency of routing and scheduling
system (ERSS) as system that accumulates vehicle location data in a central server and uses it to
generate traffic information. Test simulations using a grid network demonstrate the effects of
utilizing and sharing vehicle location data on delivery efficiency.
On The Timetable Management System (TMS) in the Topics mentioned above. It purposes
was to ensure that the enterprise Time Table system is as a very useful system for workers, Work
Department & Administrator through which workers can get the information about them and
their schedule.[ CITATION Muh10 \l 1033 ]
14
This is also useful for working department through which they can view when the work is
planned and how long it will take to finish. Administrator can add, allocate or remove workers
with very less effort also it can assign different jobs to different working department.
On the other side I found that my system was not designed by any researcher as how it is
expected to work.
I compared my system with Teaching and timetable Management System which was designed by
UMUTONI Chantal, a UNILAK student in 2011.
Her system of giving the time table used at UNILAK in CIS Faculty, the system of managing a
college timetable was done by entering courses to be studied in and print the paper and hang it in
the notice board. All the schedules of students’ departments and allocating subjects, classes, time
had to be managed on paper. So if there were any changes to be made in the timetable it had to
be reprint the new one. There was lot of efforts needed in this process knowing the availability of
lecturer, knowing the courses done by different Levels and intakes. Thus the manual work was
more, checking the availability of Lecturers the system was complex.
Then desktops or laptops were used to generate timetables which were produced by making
tables consisting of particular course, levels, time and Departments required. This reduced the
use of paper but the manual work was yet to be improved. At a place where there was any
change in the schedule of faculty, Lecturers or adding any new Department, subject it has to be
changed manually where it was hanged thus consuming a lot of time of the H.O.D.
Thus in my project the work of manually adding the course, level, Department and time has been
erased due to the use of automated timetable generation which will be produced by giving
courses, Department and time as inputs and generating a timetable as output. And whenever
there will be any change in the schedule or there are any proxies the changes will be visible to
everyone who access the system designed. In our project we will solve the problems and clashes
generated between students, levels thus saving time and HOD’s work.
15
2.4.1. Strength
The strength of Teaching and timetable Management System was that the time table was
generated and the students and Lecturers had a plan of when lesson is starting and where to study
on the time basis specified on the written timetable from the department.
In this system the lecturers were allocated to their courses collect and all of them had to teach
his/her course in hours given or planned.
And the time table was everywhere i.e. notice boards where everyone would see it and he/she
collect the information she/he needs to know at that time.
These were some of the strengths of the traditional college time table system I’ve identified from
the study I just made on my own.
2.3.2. Weaknesses
Mainly paper work is not in line with the advancement of technology today so here there some of
the weakness found about using traditional college time table system.
The H.O.D to know the course covered he had to ask the class representative in each session i.e.
day and evening what course they have learned in order to know what course will be next to
lecture.
Checking the availability of the lecturer was to call the lecturer or to go and take a look on the
timetable hanged in the notice board and check whether is giving a lecture or not this consumed
a lot of time of the H.O.D.
2.3.3. Similarities
16
2.3.4. Differences
Checking the availability of the lecturer and display his availability in the system.
Display courses covered and courses not yet covered by different years and intakes while
in her system H.O.D had to ask the class representatives.
Counting lecturer’s time for lecturing and the overtime of the lecturer whereas in her
system H.O.D had to fill the hours manually.
We have different scope our system is based in three campuses whereas her system was
for only Kigali Campus.
I have used HTML, PHP code and JavaScript while she used C#.Net.
Our contribution is to reduce much effort spent on checking the courses to be studied by every
class and the available lecturer to lecture the course and know their total hours give lecture and
the overtime worked basing on their type i.e. Part time lecture and full time lecturer. and develop
a system that will reduce the HOD’ s time of knowing the availability of the lecturer and
knowing covered courses by different levels of studying and calculate the total hours for every
lecturer who taught a lesson.
2.6. Conclusion
The Literature review on Lesson Scheduling and Timetabling System has been useful in the
development of this system. When the project completed I will provide an efficient way to
organize the Computing and information Sciences Faculty and organize data collect.
An automated timetabling system is very useful to teachers as a tool to generate and manage the
time table for 3 UNILAK – CAMPUSES in Faculty of CIS. It saves a lot of workload and time
for timetabling process. It allows the data to be saved, stored, retrieved and reused in case
needed.
Therefore, it is worth to develop and be used widely in our University i.e. (UNILAK).
After the research I made to UNIVERSITY OF LAY ADVENTISTS OF KIGALI I noticed that
lesson plan and management has always been facing some difficulties. Example:
Knowing the lesson will be taught next and a lecturer who will give lecture.
17
Knowing the exact number of course covered and those which are not yet completed
according to intakes according to levels and sessions.
Therefore, this system will provide a solution for these shortcomings mentioned above.
18
CHAPTER 3: EXISTING SYSTEM ANALYSIS
3.1. Introduction
The development of a system is a work which requires a full attention. It is successful when the
company is interested with the software and meets with their needs of its users. System analysis
and design is a proven methodology that helps both large and small businesses to achieve the
rewards of utilizing information to its full capacity. Design is the process of defining the
architecture, components, modules, interfaces, and data for a system to satisfy specified
requirements
This chapter will present first the organization structure and historic of the case study of
UNILAK KIGALI Campus then after the practices or structures to work on for improvement.
Briefly here must be clear presented in a practical and technical way. The solutions proposed to
the problems found in UNILAK will be presented in this chapter.
1. APACE,
2. APADE,
3. APADEK,
4. APADENYA,
19
5. APAER,
6. APARPE,
7. APARUDI,
8. ASPEJ,
9. UMWUNGERI,
10. APADEM,
11. APAPEN.
UNILAK was approved through the Convention No 001 of 03 February1997, which was signed
between the Government for the Republic of Rwanda, and FAPADER. The Institute obtained
legal identity as nonprofit association under Rwandan through the Ministerial Order No 002/09
of 09/04/2009.
The University’s Headquarters are located in the City of Kigali, Gasabo District, Remera Sector
where it owns a land of about 10 hectares hosting its administrative and academic buildings
The campuses are made up of four Faculties with different Departments, which offer various
National diploma (Bachelor’s Degree) and Higher National diploma (Master’s Degree) accepted
in Rwanda due to excellence of UNILAK in the country with its motto of providing
KNOWLEDGE AND WISDOM.
The case study was on Computing and information Sciences Faculty in UNILAK. Hence, the
case study is chosen so that any successful achievement records on this work (research) can
easily be transferred to its departments within the Campuses. The organizational chart of
Computing and Information Sciences Faculty comprise of the following members.
3. Lecturers.
20
3.3. Vision
Contribute to the national development by providing well-educated citizens capable of handling
developmental challenges, with much emphasis on quality education both on moral and
intellectual basis grounded in Christian values.
3.4. Mission
The mission of UNILAK is to promote integral education, scientific and technological research,
community service and any other thing that may directly or indirectly contribute to the real
development of Rwanda.
3.5.2 Timetabling
Timetabling refers to scheduling something to happen or to do something at particular time.
[ CITATION Col14 \l 1033 ]
On the timetable generated there are main information considered that include Course, level
(classes), Lecturer, Total hours and Start and ending studying dates.
21
published the Class representative goes in the department to ask for what lesson to study and the
lecturer to lecture it.
Knowing the exact time, the lecturers are available and knowing the contact hours of
every lecturer.
It consumes a lot of time to the H.O.D identify the remaining courses by Different levels.
Tracking the course ending period and notifying the Lecturer by counting days on the
Calendar it is tiresome for the H.O.D.
Skipping the days of weekend and remove them in Studying days and calculate
remaining days.
It is tiresome for the Class Representative when he/she doesn’t know the lesson to be
taught next due to students stress him/her asking which lesson to study.
The system will be an online system accessed by everyone according to his/her privileges
there will be no use of papers.
22
Each Campus will have its own time table of courses allocated.
Lecturers will know the class where to give lecture and the campus and the session
between day and night.
The time table will be generated very fast online which will raise the level of awareness
even to those students who are absent at school will suddenly know what course is being
thought currently.
3.8. Methodology Used in Research and Technological Tools
Methods refer to the body of systematic techniques used by a particular discipline, especially a
scientific one.
Scientific method is the process of events in which people try and understand both the physical
and mental aspect of sciences through and experience
To achieve these objectives above, the following methods and research techniques are used:
a) Documentation
Documentation is referring to the books, internet websites and memories related to the subject of
the project.[ CITATION IAS13 \l 1033 ]
b) Interview
An interview is to gain information from different concerned people i.e. Dean of faculty, HOD,
students and Lecturers in this project information was gathered from UNILAK.[ CITATION IAS13 \l
1033 ]
c) Observation
23
Observation will give clear overview on how the Faculty of CIS uses in order to generate the
timetable of Lessons.[ CITATION IAS13 \l 1033 ]
1. Xampp.
2. Browser (Yandex, Google Chrome, Mozilla Firefox) to view the progress.
3. Sublime Text Editor 3 to manipulate and editing code.
4. E-Draw Max for designing graphs.
24
CHAPTER 4: ANALYSIS AND DESIGN OF THE NEW SYSTEM
4.1. Introduction
This chapter highlights the method used in designing the new system and its analysis; it will also
look at the tools used in designing and necessary requirements needed. System design is the
specification or construction of a technical, computer-based solution for the business
requirements identified in system analysis. It gives the overall plan or model of a system
consisting of all specification that give the system its form and structure (i.e. the structural
implementation of the system analysis).
Systems are created to solve problems that an organization faces and simplify the activities to be
done in a short period of time. Simply the System Analysis and Design mainly deals with the
software development activities and this system analysis and design help us to analyze the
system and analysis of phases of system developments life cycle
What is a System?
A system can be defined as a group of components consisting of sub system or procedures that
works in a coordinated fashion to achieve said objective.
The relationship among entities and information flows within the organization is very important;
in a nutshell, system investigation and analysis is the study of an existing system with the view
of improving on it or developing an entirely new system to replace the existing one.[ CITATION
urk17 \l 1033 ]
System life cycle is an organizational process of developing and maintaining systems. It helps in
establishing a system project plan, because it gives overall list of processes and sub-processes
required developing a system.
25
System development life cycle means combination of various activities.
We shall explain the OOADM (Object Oriented Analysis and Design Method) which have been
chosen among other as the software development methodology.[ CITATION Dav11 \l 1033 ]
Introduction
Object-oriented analysis and design (OOAD) is a popular technical approach for analyzing
and designing an application, system, or business by applying object-oriented programming, as
well as using visual modeling throughout the development life cycles to foster better stakeholder
communication and product quality.
According to the popular guide Unified Process, OOAD in modern software engineering is best
conducted in an iterative and incremental way. Iteration by iteration, the outputs of OOAD
activities, analysis models for OOA and design models for OOD respectively, will be refined and
evolve continuously driven by key factors like risks and business value.
Relationships
26
Relationships are the connection between things. The four types of relationships that can be
represented in UML are
Dependency: This is a semantic relationship between two things such that a change
in one thing brings a change in the other. The former is the independent thing, while
the latter is the dependent thing.
Realization: This is a semantic relationship between two or more classifiers such that
one classifier lays down a contract that the other classifiers ensure to abide.
27
following structured analysis.
Table 0-1: Advantage and Disadvantage
28
4.4. Functions of the Personnel
H.O.D: He is the head of the department. He plans and assigns work schedule for each staff and
students, and he oversees their duties.
LAB ASSISTANT: The lab assistant is in charge of taking care of the laboratory.
The software development methodology that I used is the waterfall model. This is a sequential
software development model of four phases which are: requirements analysis, system and
software design, implementation and unit testing, integration and system testing.
The Waterfall methodology also known as the Waterfall Model is a sequential software
development process, where progress flows steadily toward the conclusion (like a waterfall)
through the phases of a project (that is, requirements, system and Software design,
implementation, verification, and maintenance).
29
Figure 4: Water Fall Model
30
E-R Diagram
Class diagram
Sequence diagram
In this project, the Use case diagram, Class diagram, Sequence diagram, Activity diagram and
E-R diagram will be used for system modeling.
31
USE CASE Diagram
for Lesson Plan and
Time tabling System
Lecturer
Create Class
Create Intakes
Insert Lecturers
Admin/ Department
Insert Courses
LOGIN
VIEW TIMETABLE
Insert Rooms
32
User Case: Creating Timetable
Actor’s goal: to generate timetable
Short Description: This use case describes how H.O.D makes timetables.
Post-Conditions: The new scheduled course appears to the system and accessible by everyone.
Main Flow:
1. The H.O.D creates class, Room, Intake.
2. The H.O.D inserts courses and lecturers.
3. The H.O.D select course.
4. The system displays courses of the class to be studied.
5. The H.O.D select lecturer.
6. The system displays available lecturer.
7. The H.O.D specifies starting period and ending time saves.
8. The system displays the scheduled course.
Alternate Flow(s):
1. Incomplete information
The H.O.D should fill all fields in case of empty fields the system does not validate
information.
2. The H.O.D repeat the steps mentioned above to try again otherwise use case end.
33
User case: view timetable
Actor’s Goal: Lecturer and Student needs to see the generated timetable.
Post-Conditions: If the student viewed lesson he should go to attend class and lecturer lecturers
the courses.
Main Flow:
Alternate Flow(s):
1. The student tries again in case there is change in timetable otherwise use case end.
34
4.5.2.2. E-R Diagram
Course_Name Class_id
Year/Level
Room Intake
Class Department
Level Course Scheduleded Time table
Scheduled
N,1
1,N
Manage 1,1
Department
1,1 Studied
1,1
Status ROOMS
Lecturing in Lecturer Names
Room_name
Status
35
Figure 6: E-R Diagram
36
4.5.2.4. SEQUENCE DIAGRAM OF ADMIN SIGNIN
37
4.5.2.5. SEQUENCE DIAGRAM OF ADDING FEATURES ON TIME TABLE
Sequence
Diagram
forGenerating
finalTimetable
Admin
InputLevel
InputCourse
Generate
Timetable
InputLecturer SetAllocation
InputSession
InputRoom
InputCourse
Select
starting
Time
Addinputs
Select
EndTime SendGenerated
timetable
Select
Department
Publish
thetimetable
38
4.5.2.6. SEQUENCE DIAGRAM OF GIVING COURSE TO A CLASS
SEQUNCES DIAGRAM (ADD Timetable)
SELECT Lecturer,Period,
Session & Room
SEND FIELDS
SUCCESSFULY
RECORDED DATA VALIDATION
39
4.5.2.7. SEQUENCE DIAGRAM OF ADDING A LECTURER
SEQUNCES DIAGRAM FOR
REGISTERING LECTURER
ADMIN LSTS DATABASE
Un-successful
ERROR MESSAGE Validation
Successfully saved
40
Here are the steps for designing logical model:
41
4.5.3.1. The logical model of my database:
Admin (Id,User_name, Names, password).
Lecturer (lect_id, fname, lname, email, phone, profession, faculty, worked_hours, availability).
Timetabling (id, Campus, level_id, course_id, lecturer_id, room_id, start_date, end_date, progress, status).
42
4.5.3.2. The Physical Data Model of My Database:
43
Table of lecturers
Table of Courses
44
Table of Room
Table of Assessment
Attributes Types Size Constraints Description
Assessment_id Int 50 Primary key Assessment identification
Class_id Varchar 20 Not null Class (level)
Course_id Varchar 20 Not null Course
Lecturer_id Varchar 20 Not null Lecturer
45
Assessment Date date 6 Not null Date of Assessment
Status Varchar 50 Not null Class faculty
Table 0-6: Assessment table
Table of timetable
DATABASE : MySQL
46
4.7.2. Hardware Requirements
Hardware : Intel i3
Ram : 4 GB
Hard disk : 60 GB
User requirement are statement in natural language plus diagrams of the services the system provides and its operational constraints.
Those statements are written for customers.
User requirements should describe functional and non-functional requirements so that they are understandable by system users who
don’t have detailed technical knowledge.
Functional requirements are statements of services the system should provide, how the system should react to particular inputs and
how the system should behave in particular situations.
The HOD of department will login/logout using user name and password created.
The Lecturers staff should visit the system seeking for lesson given to them and in which session at which campus
Students will visit to system to see (view) what lesson they will study and who the Lecturer to lecture them is.
System will manage and control lesson plan in CIS faculty.
47
4.7.3.2. Non-functional requirement
Non–functional requirements define system properties and constraints. They are not directly concerned with specific services to be
delivered by the system. Lesson scheduling and timetabling system are:
A programming tool or software development tool is a computer program software developers use to create, debug, maintain, or
otherwise support other programs and applications.
48
5.2.2. HTML
Hypertext Markup Language (HTML) is the standard markup language for creating web pages and web applications. With Cascading
Style Sheets (CSS) and JavaScript it forms a triad of cornerstone technologies for the World Wide Web. Web browsers receive HTML
documents from a web server or from local storage and render them into multimedia web pages. HTML describes the structure of a
web page semantically and originally included cues for the appearance of the document.[ CITATION Ler94 \l 1033 ]
5.2.3. PHP
PHP is a server-side scripting language designed primarily for web development but also used as a general-purpose programming
language. Originally created by [ CITATION Ler94 \l 1033 ], the PHP reference implementation is now produced by The PHP
Development Team. PHP originally stood for Personal Home Page, but it now stands for the recursive acronym PHP: Hypertext
Preprocessor.PHP code may be embedded into HTML or HTML5 markup, or it can be used in combination with various web
template systems, web content management systems and web frameworks.
PHP is able to perform a number of tasks including printing data, making numeric calculations, making comparisons and making
simple Boolean choices. From this you can create more complex loops and functions to make your page generate more specialized
data. And because PHP is executed on the Server, the client cannot view the PHP code. PHP can perform any task that any CGI
program can do, but its strength lies in its compatibility with many types of database. Also, PHP can talk across networks using IMAP,
SNMP, NNTP, POP3, or HTTP.[ CITATION Ler94 \l 1033 ]
49
5.2.4. Sublime
Sublime Text is a proprietary cross-platform source code editor with a Python application programming interface (API). It natively
supports many programming languages and markup languages, and functions can be added by users with plug-in, typically
community-built and maintained under free-software licenses.
50
5.3. Implementation Method
This is concerned with the way the system will be implemented. The activities involved in system implementation and programming,
testing the system, training of operators and conversion from the old system to the new system.
5.3.1. Programming
The conversion of the design specification into computer readable language is performed here. Subsystem modules were developed
and compiled to produce the new system. Many frameworks were employed to build the web application backend.
Direct Changeover Method This is mainly used where there is a strong confidence in the design and implementation of the new
system. It involves complete changeover of the old system when the new system has been implemented.
51
Pilot Changeover Method This involves pre-testing the new system in a separate or isolated testing environment using the
same form of data. This method provides an opportunity of testing the systems operational reliability and risk of changing
everything at once.
Phased Changeover Method Here, conversion is carried out gradually until the entire conversion is completed. This is used
when the old and new systems look alike.
Due to numerous advantages offered to this new system through its index sequential method of file accessing, file maintenance
operations are easily done.
52
5.4. Software Presentation Interface (Screenshots)
This section highlights the results of the implementation of the designed system
The image below is the home page which is the back end, the home page of Lesson Scheduling and Timetabling System.
53
5.4.1. Home Page
54
5.4.2. Adding a new Lecturer
55
5.4.3. Admin Dashboard
56
5.4.4. Worked Hours by Lecturer
57
5.4.5. Generating the Time Table
58
5.4.6. Report of the class courses
My approach of developing timetabling system was proved successful and practical as well as it demonstrated its suitability for
solving the CIS’s course timetabling problem. I have also shown that how I can fit our timetabling system on my Internet Application.
From this timetabling system, we are able to obtain useful information for future work. Further development includes expanding
algorithm for solving timetabling problem of more than one department at same time. Also improving problem modeling and search
59
technique, reducing execution time and enhancing graphical user interface. More research is needed to complete my interactive,
Lesson Scheduling and Timetabling system. The method, techniques and concepts developed will be tested on more datasets and
application.
The main purpose of my Application is to help UNILAK’s CIS Faculty to improve its performance in management of teaching and
quickening the Activities, and I am sure that the use of this software will enhance the Activities of managing class activities.
6.2 Recommendation
I do recommend that:
I recommend to the future researchers interested in this project to implement another version of this application that can implement
further aspects that I may have forgotten to mention.
Having understudied the challenges that are contained in the manual timetable system, the following are recommended:
1. The timetable system developed should be broadened to accommodate the timetable management of the entire department
(academic) in higher institution and made open to all students.
2. Further works on developing a timetable system should be based this research work so as to utilize the incremental model of
software development.
3. A collaborative model of timetabling system which utilizes mobile operating systems should be built i.e. a mobile android app.
REFERENCES
1. Dictionary, Collins. Grammar Dictionary. New York, 2014.
60
3. Linda. Timetable Management System. London: UK Researchers, 2016.
4. Michael G.H. Bell and Tomio Miwa. Efficieny of Routing and Scheduling System. 23 vols. Sydney: Published Online, 2017.
6. urke E.K., Eliman D.G. and Weare R.F. A Generic Algorith for UNIVERSITY Exam Timetabling. Vol. Vol.26. Leeds: AISB,
1994.
7. Zeechan, Muhamad. Timetable Management System. ALIGRH -INDIA: ALIGARH MUSLIM UNIVERISTY, 2009 - 2010.
8. ARIADNE TRAINING CORPORATE (2001).UML Applied-Object oriented analysis and design using the UML, Somerset
UK.
9. Aurum, A., Jeffery, R., Wohlin, C., & Handzic, M. (Eds) (2013). Managing software engineering knowledge. Spring Science
& Business Media.
10. Bennett, S., McRobb, S., & Farmer, R. (2005). Object-oriented systems analysis and design using UML. McGraw Hill Higher
Education.
11. Dennis, A., Wixom, B. H., &Tegarden, D. (2015). Systems Analysis and Design: An Object-oriented approach with UML.
John Wiley & Sons.
12. Geary, D &Horstmann, C. (2007). Core java server faces, Second Edition, Indiana-USA.
13. Mann, K. D. (2005). Java Server Faces in Action. Dreamtech Press, 2005.
14. Manning, L. (2010). Itext in Action, third Edition, NEW YORK, USA
61
15. Training A. (2001). UML applied-object oriented Analysis and Design using the UML. Ariadne training Limited.
16. Tutorial Point (2015). System Analysis and Design
Websites
1. www.timesmet.com/literature%20review.pdf
2. http://En.wikipedia.org/wiki/supply_chain_management
3. http://encyclopedia2.thefreedictionary.com
4. Michael Lachmann. (2015) On the advantages of information sharing Retrieved April 4, 2018, from
http://rspb.royalsocietypublishing.org/content/267/1450/1287
5. Simon Sinek Quotes. (n.d.). BrainyQuote.com. Retrieved April 4, 2018, from BrainyQuote.com Web site:
https://www.brainyquote.com/quotes/simon_sinek_568162
62
APPENDIX
<html>
<head>
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>Unilak Timetabling</title>
<script type="text/javascript" src="js/jquery.min.js"></script>
<script type="text/javascript" src="js/bootstrap.min.js"></script>
<script type="text/javascript" src="js/index.js"></script>
63
<li><a href="#">Home</a></li>
<li><a href="#">About</a></li>
</ul>
</div>
</div>
</div>
<p><br></p>
<p><br></p>
<p><br></p><br>
<div class="container-fluid">
<div class="row">
<div class="col-md-3">
<div style="height: 500px;overflow: scroll;position: fixed;left:0;right: 75%;">
<div class="row">
<div class="panel panel-default">
<div class="panel-heading" style=" Coppler Plate Gothic Bold;">
<b style="font-family: Cambria; font-size: 1.5em;color:#80bdff;">Unilak Timetabling</b>
</div>
64
<div class="panel-body">
<div id="loginError"></div>
<form class="well">
<label for="uemail">User E-mail</label>
<input type="email" name="uemail" id="uemail" class="form-control" placeholder="E-mail">
<label for="upass">Password</label>
<input type="password" name="upass" id="upass" class="form-control" placeholder="Password"><br>
<button class="btn btn-success" id="adminLogin">Login</button>
</form>
</div>
<div class="panel-footer">
</div>
</div>
</div>
</div>
</div>
<div class="col-md-9">
<div >
<div class="row">
<div class="col-md-12">
</div>
</div>
65
<div id="timetableDisplay">
</div>
</div>
</div>
</div>
</div>
<footer class="container-fluid">
<center><p>©<? php echo date("Y");?> IRADUKUNDA Louis Pacifique</p></center>
</footer>
</body>
</html>
66