CHAPTER 5: DEVELOPMENT OF TIMETABLE MANAGEMENT SYSTEM USING GENETIC ALGORITHM

5.1 Introduction This chapter describes the technology and methodology used in developing the web based known as Timetable Management System. This chapter describes the system overview, system objective, system scope, how the system works, software and hardware considerations, the system development methodology used and finally the limitations and future enhancements of the system. Requirements are addressed and justifications on any decisions made are documented.

5.2 System Overview Timetable Management System is a web based system which is developed for lecturers and students of FCSIT as their online timetable. It would contain three modules: administrator module, lecturer module and student module. The functions of the

administrator module are to handle the entire administrator task. Administrator has to register the entire FCSIT student for the first time. Administrator also has to handle the additional, editing and deleting classes and subject as well.

For the lecturer module it contains the function to view timetable for the specific lecturer and the master timetable for that semester. Lecturer can inquire for the class available and can book for the free classes. Students module contains the functionality of add and drop subject. Students can view and get the registration slip from the system.

Timetable Management System also contains a database, which stores the lecturers and students personal details. Only the administrator can view, add and delete the data in the timetable.

68

5.3 System Objective The main objective of developing the Timetable Management System is to have a quality and feasible timetable which is to improve the current system that FCSIT is using. Another objective is the system should be user-friendly and easy to maintain. The system produced should be easily modified to address any form of constraints in an actual situation. The system should also be robust and produce a feasible solution for any big problem.

5.4 System Scope The scope of this system is to develop FCSIT timetable management system, which can improve the current manual system that FCSIT is using. In order to achieve the objectives, due to the time constraints, the scope of the timetable system covers the following features and functions: An administrative Section which includes the following:Manage students’ profiles Manage lecturers’ profile Manage the username, password and change password Manage the add, drop subject Manage the add, edit and delete class Creation of Master Timetable A lecturers’ Section which includes the following:View and print their own timetable View and print master timetable for one semester Query on the class availability Booking the class Creation of lecturer’s timetable

69

A students’ Section which includes the following:Add and drop subject View, print their timetable and registration slip Change password Creation of student’s timetable

5.5 Software, Hardware and technology considerations In order 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 development tools for the Timetable Management System using Genetic Algorithm.

The following Sections discuss the scripting language, graphic design tool, database technology, web development tool, and the server technology used to develop the timetable system. In order to develop a better website with the latest technology, the researcher went for a few training sessions to learn about the newest technology, software and languages.

5.5.1

Programming / Scripting Language

PHP Programming PHP originally stood for “Personal Home Page” as it was created in 1994 by Rasmus Lerdorf to track the visitors to his online resume. As its usefulness and capabilities grew, it came to mean “PHP: Hypertext Preprocessor” (Ullman, 2003). PHP can be interspersed within Hypertext Markup Language (HTML), which makes developing dynamic websites more accessible.

70

PHP was selected to develop the Timetable Management System because it is a serverside, cross-platform technology. Server-side actually refers to the fact that everything PHP does occurs on the server instead of the client’s site. Its cross-platform means that PHP runs on most operating systems, including Windows, UNIX, and Macintosh. More importantly is that PHP written on one server will normally work on another with little or no modifications. Besides that, when it comes to developing dynamic websites, PHP is better, faster and easier to learn than the alternatives. Of course, the main reason for PHP being chosen to develop the website is it comes at no cost (PHP is open source).

5.5.2

Graphics’ Design Tools

Adobe Photoshop CS Adobe Photoshop was chosen to be used as one of the graphic editing software because it is professional image-editing software which provides a comprehensive toolset, and powerful creative options to help people create professional-quality images for web, print, and other emerging media.

Macromedia Fireworks MX 2004 Fireworks MX was chosen to be used as the other graphic editing software, because it is an increasingly approachable application with enhanced power to create graphics and interactivity for websites.

5.5.3

Web Development Tool

Notepad Microsoft Notepad version 5.1 was chosen as the text editor to develop the website as well since the researcher is more familiar with using the text editor to develop a website.

71

that are stored and kept organized by the DBMS (Ullman. be it text. 2003).5 Hardware Requirements Below is the list of hardware requirements for the personal computer to develop the Timetable Management System:Intel Pentium IV 500MHz processor or higher 128MB DDR-Ram (256MB is recommended) 10GB Hard-disk space or higher 72 . MySQL is an RDBMS). a database being a collection of interrelated data.5. rapid web application development and extensive code editing support. portability and reliability. MySQL offers excellent performance. MySQL was selected to develop the database for this web based system because like PHP. build and manage a website.Macromedia Dreamweaver MX 2004 Macromedia Dreamweaver MX 2004 was chosen as the web development tool because it can work in a single integrated environment to create. or binary files.5.4 Database and Technology MySQL MySQL is a database management system (DBMS) for relational databases (therefore. 5. Dreamweaver MX uses user-friendly visual layout tools. 5. Besides that. another reason for it being chosen is PHP has good support for MySQL. numbers. with moderate learning curve at little to no cost because MySQL is the world’s most popular open source database. which is easier to learn and use.

The goal of this analysis stage is to truly understand the requirements for the new system and develop a system concept that addresses them. The second category would be the students who want to add and drop the subject. The third category would only contain the administrator. identifying its strengths and problems. They also can have their timetable and registration slip. who would be 73 . The current timetable always change and involved many lecturer to handle it. The analysis that will be done would be on how a current system works and the new requirement to improve the timetable system. 5. In the current case.6 System Analysis System analysis. The conclusion is they need a system to help and improve the process of preparing the timetable.6. is the process of gathering information about the current system. there is a current system that used in FCSIT. sometimes called requirement analysis. and analyzing them to produce a concept for the new system. They also want to enquire if the class is available or not to do the additional or replacement class and can book the class straight away. The first category would be the lecturers who need their own timetable and master timetable for the semester. 5.40x CD-ROM 15” Monitor (can support up to 1024X768 Resolution) 56Kbps Modem Keyboard and Mouse 5.6. This manual system will make sure there are no clashes for the every timetable produced. It’s taking too much of their time.1 Current Timetable System The current manual timetable system is use by postgraduate and undergraduate.2 User Analysis The users of this system are divided into three categories.

6.3 Content Acquisition The contents of Timetable Management System. 5. Graphics As graphics plays an important role to attract browser attention. Text Most of the text content are look and feel used in Timetable Management System is taken from a few scraped ideas and going through reference materials during the literature review and research studies. creative and nice graphics are needed. 5. Three use case diagrams have been created for timetable system: one for the lecturer.6.4 Use Case UML use case diagrams are used to describe the main processes and functionality of the Timetable Management System. The purpose of having use case diagram is to identify the scope of the system. which include text and graphics. 74 .able to monitor and control the Timetable Management System. which includes the lecturers and students ‘data. The logo and banner are created using Adobe Photoshop. students and the administrator. Most of the graphics are downloaded from the Internet and further modified using either Adobe Photoshop of Macromedia Fireworks. would be acquired from the following sources described below.

using their usernames and passwords. system displays a message indicating that the username or password is invalid.1: Lecturer’s Section Use Cases Lecturer can log-in to Timetable Management System. 75 . he or she can perform the processes (use cases) like view class. inquiry class available. view timetable. view master timetable. System displays the main menu if log-in is successful. Once the lecturer logs in. class booking and change password. If the username and password are not accepted.Figure 5.

All lecturers can book class if they want to do the additional class. All lecturers are allowed to inquire the class available for the semester. credit hour. class. by using this function they can see the subject code. Lecturer can view their timetable by using this function Lecturer can view the master timetable for the semester. day and time.2: Student’s Section Use Cases 76 .1: Lecturer’s Section Use Cases Description Use Case Log-in View Class View Timetable View Master Timetable Inquiry Class Available Class Booking Change Password Description Lecturer need to log in using the username and password giving by the administrator Lecturer can view class.Table 5. Lecturers can change password if necessary Figure 5.

2: Student’s Section Use Cases Description Use Case Log-in Add Subject Drop Subject View Timetable View Registration Slip Change Password Description Student need to log in using the username and password they have registered when they first time use the system Student can add subject with regards to the subject suggestion by the Dean. Student can also drop the subject if unnecessary Student can view the timetable for the semester. If the username and password are not accepted. view timetable. Once the student logs in. system displays a message indicating that the username or password is invalid. System displays the main menu if log-in is successful. drop subject. view registration slip and can change password. Student can view and print the registration slip for the semester.Student can log-in to Timetable Management System. Table 5. using their usernames and passwords. Student also can change password if necessary 77 . he or she can perform the processes (use cases) like add subjects.

add subject. edit class. lecturer registration. Besides logging in. as his or her username and password is fixed in the database. 78 . edit subject and delete subject.Figure 5.3: Administrator’s Section Use Cases The administrator does not need to register. delete class. add class. the seven main use cases for the administrator are student registration. The administrator needs to log in to Timetable Management System in order to manage the system.

The administrator is allowed to delete the class if the class is no more to use.Table 5. The administrator is allowed to edit the subject if necessary. a window will prompt out to ask for delete confirmation. class code. The administrator is allowed to delete subject.6. After that the registered student can use this system The administrator has to key in the lecturer’s profile and can proceed to register the subject The administrator can add the new class by insert information about the class description. and it can show the paths within the use case as well as other use cases. An activity diagram is needed because the researcher wants to model the workflow of a use case. the researcher will be able to illustrate where functionality exists in the system and how the functionality coordinates with the functionality of other pieces of the system. A brief description will be given to each of the activity diagram in the following pages.5 Work Flow Modeling Activity diagrams are used here to model the flow between the different components.3: Administrator’s Section Use Cases Description Use Case Student Registration Lecturer Registration Add Class Description The administrator has to key in the student’s profile. 79 . With activity diagrams. Edit Class Delete Class Add Subject Edit Subject Delete Subject 5. The administrator is allowed to add subject if the subject is new subject for the semester. class capacity and class location Administrators can edit the current and new class if necessary. After pressed delete. The researcher has developed ten activity diagrams for this system.

The system will validate the username and password. the administrator’s menu page will be displayed. 80 .4: Activity diagram for Log-in Figure 5. the lecturers.Log-in Validate (user. First. an error message will be displayed and the lecturer or student or administrator can try to log in again. If log in is successful. else the lecturer or student menu’s page will be displayed. student or an administrator. If the person logs in as administrator. password) Validate Display Log-in Error Message [failure] [success] [administrator] Display Administrator Menu (lecturer/student) Display Lecturer/student Menu Figure 5. If the password or username is invalid. the system will identify the user as a lecturer.4 above shows the activity diagram for Log-in. students and administrator need to log in using the username and password that was created during registration.

timetable and master timetable for lecturers.Select from lecturer’s view Read input (view class) Read input (view master timetable) Choose Class (view timetable) View Class Read input View Timetable View Master Timetable Figure 5. If the lecturers want to print their timetable or their master timetable they can click on the button “PRINT”. 81 .5 above shows the activity diagram for View class. Timetable or Master Timetable Figure 5.5: Activity diagram for View Class. The lecturers can click on the view class or timetable or master timetable menus and the specific information will be loaded.

82 . a message error will also displayed.6 shows the activity diagram for the Inquiry class available for lecturers.6: Activity diagram for Inquiry Class Available and Class Booking Figure 5. the message successful page will be displayed.Inquiry Class Available Read input Display Success Result (available) Booking Class (not available) Read input Display Not Available Class Message (success) (not success) Figure 5. To inquire whether a class is available. the system will check the query. lecturer can go to booking class menu to book the class. Then if the class is available. If inquiry is successful. The message “successful booking” of the class is displayed and if the booking failed the message will also be displayed. If fails. the lecturers have to select the class based on the list in the system. Once the submit button has been clicked.

the student can choose to either view their timetable or their registration slip. Figure 5. the output will come out. 83 .7: Activity diagram for View Timetable and Registration Slip Figure 5.7 shows the activity diagram for the view timetable and registration slip for students. Firstly. When the student clicks either one.Select View Timetable / Registration Slip Read input (view timetable) Read input (view registration slip) View Timetable Read input View Registration Slip .

the error message will be displayed on the web page as well. student need to click on the add subject button. 84 .8: Activity diagram for Add Subject Figure 5.Add Subject Read input (success) Read input (not success) Display Register Subject Figure 5.8 shows the activity diagram for add subject for the student. Then. If the add subject is successful the message will display subject is add successful. Students need to select the subject to register. Besides that.

student need to click on the delete subject button. the error message will be displayed on the web page as well. Students need to select the subject to drop. Then. If the delete subject is successful the message will display subject is delete successful. 85 .9: Activity diagram for Drop Subject Figure 5.9 shows the activity diagram for drop subject for the student. Besides that.Drop Subject Read input (success) Read input (not success) Display Drop Subject Successfully . Figure 5.

10: Activity diagram for Change password Figure 5. 86 . If the validation of the new password is successful the message will displayed successful. System will ask for the second time for the new password. the error message will be displayed. If not. and then to enter the new password. by choosing the change password function. They have to key in the old password.10 shows the activity diagram for student to change their password. They can change their password.Figure 5.

11: Activity diagram for Registration Student Figure 5. Validation of the form will be carried out before the data is stored in the database. After the administrator finish fill in the form. the administrator has to fill in the details of student’s information. the administrator have to click on save button. First.Student Registration Load Application Form Fill in Form Submit Form Display Error Message Validate Form (failure) (success) Display Application Success Figure 5.11 above shows the activity diagram for registration student. Upon successful 87 .

Both screens are the same. Upon successful adding the subject or class. Then click on the next button. a successful application page will be display.12 shows the activity diagram for add subject and class. If validation failed. he or she has to fill in the form the subject or the class information. 88 . Figure 5. an error message window will pop up.12: Activity diagram for Add Subject or Class Figure 5. If validation failed. Validation of the form will be carried out before the data is stored in the database. a successful application page will be display. an error message window will pop up and the user will need to fill in the field(s) with error(s).registration. If the administrator wants to add the subject or the class.

13: Activity diagram for Edit Subject or Class Figure 5. he or she have to click on the update subject or class before the data is stored in the database. If validation failed. he or she has to select the subject or the class they want to edit. 89 .13 shows the activity diagram for edit subject and class. Then click on the next button. If the administrator wants to edit the subject or the class. a successful application page will be display. Upon successful editing the subject or class. After the system show the new information of the editing. an error message window will pop up. Both screens are the same.Figure 5.

14 shows the activity diagram for delete subject and class. System will ask if he or she want to proceed with the delete function or not.14: Activity diagram for Delete Subject or Class Figure 5. Then click on the delete button. If the administrator wants to delete the subject or the class.5. Upon successful deleting the subject or class. 90 . he or she has to choose which subject or class they want to delete. an error message window will pop up. If validation failed. Both screens are the same. a successful application page will be display.

As described earlier. It can be used to describe the system being developed. UML Sequence diagrams are used to show the interaction between objects and to illustrate the activities that are performed in Timetable Management system and how data moves around in this system. The General tasks of lecturer. There are so many different process modeling techniques.2 and Figure 5. Each category of user can perform only certain tasks as fixed by the system.6. The researcher used Unified Modeling Techniques (UML) for the process modeling.6 Process Modeling The process model is used to describe how the system operates.3. Figure 5.5. student and administrator are shown in the use case diagram in Figure 5. The following sequence diagrams show the interaction between objects arranged in time sequence.15: Sequence diagram for lecturer/student/administrator Login 91 . the users of Timetable Management System are divided to three categories: Lecturer.1. Student and Administrator. Figure 5. It illustrates the business processes or the activities that are performed and how data moves among them.

a query result will be returned by the web server and a profile page will be displayed by the browser. Figure 5. 92 . the server will send an error login page to the monitor.Figure 5.15 above shows a sequence diagram for the use case Login. the lecturer/student /administrator need to key in their username and password. and the server will display the Main Menu page according to the user type. Then the browser will send the information to the web server and validate the information with the database. student and administrators will need to log in to the Timetable Management System. After the lecturer requests to view class or timetable or master timetable. In order to log in. Lecturer. Successful validation will be sent to the web server. The vertical dimension represents time and all objects involved in the interaction are spread horizontally across the diagram. Timetable or Master Timetable Figure 5. As for unsuccessful validation.16: Sequence diagram for the use case View Class.16 shows a sequence diagram for the use case view class or timetable or master timetable.

If the lecturer wants to book the class. the lecture will inquiry for the available class and then the browser will inquiry the URL for the class available from the server. all the information are sent to the web server for booking validation. If the booking validation fails.Figure 5.17 shows a sequence diagram for the use case inquiry class available and booking class. the query will pass to the database and after the data is stored successfully. he or she has to fill the information. If validation is successful. 93 . First. After that. the web server will send the HTML and display the result. an application successful webpage will be display. a window will pop out to show the error message and request the lecture to fill in the information again.17: Sequence diagram for the use case inquiry class and booking class Figure 5.

The browser will send a request to the web server and it will return the subject information page.19: Sequence diagram for the use case Add Subject Figure 5. The browser will send the query to the web server. The query result will be returned to the web server and the view page is sent to the browser to be displayed. Student can request to view the timetable or registration slip. If validation is successful.Figure 5. the query will be passed to the database and after the data is stored successfully.19 above shows a sequence diagram for the use case Add Subject. The student will send in the Section information form. Figure 5.18: Sequence diagram for the use case View Timetable or Registration Slip Figure 5.18 shows a sequence diagram for the use case view timetable or registration slip. and the web server will pass the query to the database. the message will 94 .

the browser will send the request to web server and it will return the drop subject page. Figure 5. The student will request the system to drop the subject. a window with an error message will pop out.20 above shows a sequence diagram for the use case Drop Subject. If validation is successful. After the data is stored successfully. The student will choose the drop subject and send. a window with the error message will pop out. If the form validation failed.20: Sequence diagram for the use case Drop Subject Figure 5. If the form validation failed.be displayed. the product page will be displayed. 95 . the query to store the data will be passed to the database.

message will appear.21: Sequence diagram for the use case Change Password Figure 5. The student will request for the change password. The browser will send the request to the web server and will store in the database. The student will fill the new password and the confirmation the new password.22 above shows a sequence diagram for the use case Student Registration.Figure 5. The browser will send back the successful result or if error. Figure 5. The browser will send a request to the web server and it will return the form of student 96 . The browser will send the request to the web server and will return the page change password.22: Sequence diagram for the use case Student Registration Figure 5.21 above shows a sequence diagram for the use case Change Password.

The browser will send a request to the web server and it will return the subject or class information page. Figure 5. If validation is successful.registration. If the page validation failed. the form will be passed to the database and after the data is stored successfully. the message board will be displayed. If the form validation failed.23: Sequence diagram for the use case Add Subject or Add Class Figure 5. If validation is successful. the message will be displayed. a window with the error message will pop out. the information will be passed to the database and after the data is stored successfully. The administrator will send in the form.23 above shows a sequence diagram for the use case Add Subject or Add Class. The administrator will send in the information page. a window with the error message will pop out and request the user to fill in the form again. 97 .

25 above shows a sequence diagram for the use case Delete Subject or Delete Class.Figure 5. If validation is successful. The browser will send a request to the web server and it will return the subject or 98 .24: Sequence diagram for the use case Edit Subject or Edit Class Figure 5. Figure 5. If the page validation failed.25: Sequence diagram for the use case Delete Subject or Delete Class Figure 5. The administrator will fill the editing page. The browser will send a request to the web server and it will return the subject or class editing page. a window with the error message will pop out and has to fill in the editing page again. the message will be displayed.24 above shows a sequence diagram for the use case Edit Subject or Edit Class. the information of the editing will be passed to the database and after the data is stored successfully.

the information will be passed to the database and after the data is stored successfully.26 above shows a sequence diagram for the use case Delete Subject or Delete Class. If validation is successful.class deleting page. a window with the error message will pop out and has to fill in the editing page again. The browser will send a request to the web server and it will return the subject or class editing page. If the page validation failed. The administrator will fill the editing page. Figure 5. the message will be displayed. the message will be displayed.26: Sequence diagram for the use case Delete Subject or Delete Class Figure 5. If validation is successful. the message will be displayed. the information of the editing will be passed to the database and after the data is stored successfully. If the page validation failed. The administrator will do the deleting function and send it. 99 . a window with the error message will pop out. a window with the error message will pop out. If the page validation failed. If validation is successful.25 above shows a sequence diagram for the use case Edit Subject or Edit Class. The administrator will do the deleting function and send it. Figure 5. The browser will send a request to the web server and it will return the subject or class deleting page. the information will be passed to the database and after the data is stored successfully.

29: Student Section Structure Design 100 .5.7 System Design 5.27: Main Structure Design of Timetable Management System Administration Module Administration Login Student Registration Add Class Edit Class Delete Class Add Subject Edit Subject Delete Subject Figure 5.28: Administrator Section Structure Design Student Module Student Login Add Subject Drop Subject View Timetable View Registration Slip Change Password Figure 5.30 shows the structure of the webpage clearly.7. Timetable Management System Administration Module Lecturer Module Student Module Figure 5.27 to 5.1 Structure Design The structure charts in Figures 5.

All the main database tables and functions are described in Table 5.7. It also stores administrators Username and Password. Lecturer can only view the class details through the class links. which include Username and Password. day and period Class Table Booking Table Subject Table Registration Daytime Table 101 .4. while administrators can insert. update and delete the data in the tables. Store subject registration details. time.Lecturer Module Lecturer Login View Class View Timetable View Master Timetable Enquiry Class Available Class Booking Change Password Figure 5. Store all the class details of. updating and delete the subject Store the daytime. All the tables design with field types are attached in Appendix C. Only the administrators are allowed to insert. Table 5. date and period. Lecture can only view the subject registration while administrator can insert. time. Lecturer can only insert and view the booking class.2 Database Design The database design phase shows how data will be stored in a file or a database table.4: Database Tables Tables Lecturer and Student Table Description Store lecturer and student details. day. lecturer id. updating and delete the booking class.30: Lecturer Section Structure Design 5. The database was created using MySQL. view. view. while the administrator can update and delete all the lecturer and student details. update and view own details. Lecturer and student will be able to insert. Store all booking class.

Besides that. There are minimum graphics so they won’t clutter the page design and to ensure that the website will load at the shortest possible time frame because most Internet users are put off by sites that takes “years” to load. Timetable Management System is a web base that allows the interaction between Internets users. 102 . therefore their needs are of the utmost importance. the web based uses the technology of hyperlinks.7.3 Screen/Interface Design The purpose of the user interface is to provide users with a comfortable and convenient means of accessing the website.5. interface consistency is maintained throughout the site so that there is uniformity in the website that will not cause confusion to the users. The flexibility and convenience of the interface is a major factor determining the overall success of the website. Therefore. Below will be the screen design of Timetable Management System. Timetable Management System web based’s interface design will be made up of simple but effective presentations that can attract the Internet users’ attention. buttons and navigation bars which the majority of Internet users are familiar with. This means that Internet users can easily access information with just a click of a mouse button.

32: adminmainframe.php/studentmainframe.Text Timetable Management System top.php Graphic Initial page ->mainframe.php/lecturemainframe.php/lecturermainframe.php Screen Design Text Timetable Management System Log-in section Navigation Graphic Post and Reset Button Text Welcoming mesage Text Timetable Management System Figure 5.31: adminmainframe.php Figure 5.php (Timetable Management System logo) Text Welcoming mesage bottom.php Screen Design 103 .php/studentmainframe.

Month.Month. time List Of Menu Class Subject Other Link Text box Welcoming to administrator module Text Box News Info Text Administrator Profile Text Timetable Management System Figure 5.php Screen Design 104 .php Screen Design Text Timetable Management System Text Day.year.33: adminsuccess.34: studentreg.year.Text Timetable Management System Text Day. time List Of Menu Class Subject Other Link Text Student information form Navigation Save button Text Administrator Profile Text Timetable Management System Figure 5.

php /adminaddsubject.Text Timetable Management System Text Day.php Screen Design 105 .36: adminaddclass.year. time List Of Menu Class Subject Other Link Text Student information form Text Message success/failed Text Administrator Profile Text Timetable Management System Figure 5.php Screen Design Text Timetable Management System Text Day. time List Of Menu Class Subject Other Link Text class information form Navigation Next button Text Administrator Profile Text Timetable Management System Figure 5.Month.year.35: studentregsuccess.Month.

php/admineditsubject. time List Of Menu Class Subject Other Link List Box Text Delete action Text Administrator Profile Text Timetable Management System Figure 5.php Screen Design Text Timetable Management System Text Day.year.37: admineditclass.php Screen Design 106 .year.38: admindeleteclass.Month.Month. time List Of Menu Class Subject Other Link List Box Select class to edit Navigation Next button Text Administrator Profile Text Timetable Management System Figure 5.php/admindeletesubject.Text Timetable Management System Text Day.

php Screen Design 107 .php Screen Design Text Timetable Management System Text List Of Menu Subject Registration View Other Link Text Day. time Navigation Add Subject Text List of Subject Text Administrator Profile Text Timetable Management System Figure 5.year.Text Timetable Management System List Box List Of Menu Subject Registration View Other Link Text Day.Month.year.Month.39: studentaddsubject.40: studentaddsuccess. time Radio Button Section Information Navigation Register Text Administrator Profile Text Timetable Management System Figure 5.

php Screen Design 108 .Text Timetable Management System Text Day.year.Month.41: studentdropsub.year.Month. time Table Indicvation Text Administrator Profile Text Timetable Management System Figure 5.42: studentview.php Screen Design Text Timetable Management System Table List Of Menu Subject Registration View Other Link Student Timetable Text Day. time List Of Menu Class Subject Other Link List Box Text List of Subject Button Action Delete Text Administrator Profile Text Timetable Management System Figure 5.

year.Month. time Text Administrator Profile Text Timetable Management System Figure 5.Month. time Student Change Password Navigation Change Password Text Administrator Profile Text Timetable Management System Figure 5.php Screen Design 109 .year.44: studenchangepass.Text Timetable Management System Table List Of Menu Subject Registration View Other Link Student Registration Slip Text Day.43: studentregslip.php Screen Design Text Timetable Management System Table List Of Menu Subject Registration View Other Link Text Day.

year. time Navigation View Subject Text List of Subject Text Administrator Profile Text Timetable Management System Figure 5.Month.php Screen Design 110 . time Table Indication Text Administrator Profile Text Timetable Management System Figure 5.Month.php Screen Design Text Timetable Management System Table List Of Menu View Inquiry Other Link Lecture Timetable Text Day.45: lectureview.Text Timetable Management System List Box List Of Menu View Inquiry Other Link Text Day.year.46: lectureviewtimetable.

year.php Screen Design Text Timetable Management System List Box List Of Menu View Inquiry Other Link Class Inquiry Available Text Day.Month.php Screen Design 111 . time Table Result Class Information Text Administrator Profile Text Timetable Management System Figure 5.year.Text Timetable Management System Table List Of Menu View Inquiry Other Link Master Timetable Text Day. time Text Administrator Profile Text Timetable Management System Figure 5.48: classavailable.47: mastertimetable.Month.

Text Timetable Management System List Box List Of Menu View Inquiry Other Link Booking Class Text Day. Most activities in the development phase addresses the computer programs that make up the system. The activities in the development phase translate the system design produced in the design phase into a working system (web based). The development phase includes activities for developing the system. and to ensure the system functions satisfy the functional process requirements. testing the system.49: classbooking.php Screen Design 5. 112 . but this phase also puts in place the hardware. time Table Result Booking Class Text Administrator Profile Text Timetable Management System Figure 5. and communications environment for the system and other important elements of the overall system.year. At the end of this phase.Month. the system will be ready for the activities of the testing phase. software.8 System Development The objective of the development phase is to convert the deliverables of the design phase into a complete system.

Some of the graphics. such as some buttons and the logo are designed by the researcher from scratch. 5. 5. and MySQL database. buttons. the development is divided into three main sessions which are explained in the Sections below. thus significantly reducing storage place. background wallpapers and pictures are needed.The Timetable Management System web base was developed after the system analysis and system design phases.8. Each webpage is developed according to the design from the design phase. These two software were chosen to be used to design. 5. the researcher converts the deliverables of the web design into a complete website using Macromedia Dreamweaver MX. 113 . when uploading the website.8. create and edit the graphics because the researcher found them easy to be learn and quite powerful in the sense that they have a lot of features. All the tables as described in Section 5. Some of the pictures were downloaded from other websites and edited using Macromedia Fireworks MX or Adobe Photoshop 8.2 Database Development The Timetable Management System used a relational database in its database implementation because it can support multiple tables that store each item only once. logos. The database was created and using MySQL.1 Graphic Development In order to develop a nice and attractive web site a lot of graphics.3 Website Development In this stage.8. such as banners.2 are developed on localhost and export to domain host using myPHPadmin. PHP programming.8. After gathering data from the system analysis stage and designing the web base. which is a GUI Client that works alongside MySQL Database server.

and scripts that not run properly.9 Testing The objective of this testing phase is to prove that the developed system (Timetable Management System) satisfies the requirements defined earlier. there might be browser compatibility problems because a project may run perfectly on one browser but may not display properly on another browser. 114 . Besides that.php for the purpose of the dissertation. The website was developed and tested on a local host first before it’s uploaded to a domain host. at least one web development tool such as Macromedia Dreamweaver or Microsoft Front Page. Testing is an important phase of system development because it can ensure the system matches the specifications. testing also ensures that the system functions in the correct and proper manner with the minimum amount of errors. links that go to the wrong page. However. such as broken links. but a lot of the back end processing still need to be hard coded using PHP programming. video and audio that not play properly.Although Macromedia Dreamweaver is used as the main tool to develop Timetable Management Syatem. Several types of tests will be conducted in this phase. Besides that. 5. in order to view the source code. Websites are susceptible to bugs and malfunctions. Timetable Management System can be accessed temporarily through http://localhost/subjectTT/mainframe. The source code for the web portal is not printed out in this documentation because there are too much of codes for all the pages. or a word editor is needed.

It was checked to ensure that it works perfectly once it’s uploaded to the server. All the buttons.1 Unit Testing Unit testing reveals syntax and semantic errors from the smallest programming unit. 5.3 System Testing A system test was carried out to test the web base as a whole when the entire website is finish and uploaded. Due to the dynamic nature of testing. Individual objects will be tested in isolation using unit testing and gradually integrated for the higher-level integration testing and system testing. unit testing is used to test each individual webpage. Errors that are found in a particular page of the website are thoroughly debugged and removed before starting to develop another webpage. Failed components will be migrated back to the development phase for rework. In this thesis. Integration testing was mainly conducted in “Administrator Module” Section “Lecturer Module” and “Student Module” Section. hyperlinks and navigation bars were tested. 5.Bottom-up testing strategy is used in this system to avoid unnecessary duplication of effort.2 Link /Integration Testing When each webpage of a particular Section in the Timetable Management System passed the unit testing.9. 115 . integration test was carried out to ensure that pages are linked in the correct flow and integrate properly into the entire website. It also tested whether there are any broken links in the entire website since it’s transferred from the local host to another domain hosting company. Please refer to Appendix E for test results. and components that work properly will migrate ahead for implementation. 5.9. there is no proper testing documentation created.9.

Therefore user testing for this system is tested on the researcher’s laptop with a personal web server.5.5 below. The users’ feedback is summarized in Table 5. 116 . users tested the Timetable Management System and were required to fill in the system evaluation form as shown in Appendix F. involved two timetable committee members of FCSIT.9. one lecturer FCSIT and one assistant registrar FCSIT to confirm that the developed system meets the user requirements.4 User Testing For the user testing. During the user testing stage. User testing shall be done in a simulated “real” user environment with the users using simulated or real target platforms and infrastructures.

Therefore it can be summarized that this system is easy to use All respondents agreed and stated that the user interface and layout of the design are good. All stated good Overall. All respondents were satisfied with the text style and size is good because the text is easy to read. the respondents rated that the system is good. and post implementation review. Could the system avoid any clashing between subjects? Could the system avoid any clashing between lecturers? Could the system avoid any clashing between times? Could the system avoid any clashing between venues? 5. Two respondents stated that the user friendliness of this system is good and two stated that it is average.10 System Implementation In this phase. This is because the navigation bars and buttons provided are very clear. Please rate your overall view for the Timetable Management System. while another stated that it is excellent. the system or system modifications are installed and made operational in a production environment. Three of the respondent stated that the contents of Timetable Management System is average.Table 5. The system implementation phase is initiated after the system has been tested and accepted by the user. data entry or conversion. All respondents agreed that the color combination of Timetable Management System is good. Please rate the usefulness of the Timetable Management System.5: Summary of User Feedback Question How user friendly is the application? Feedback The respondents agreed that this system is easy to use. Activities in this phase include notification of implementation to end users. All respondents stated that the loading time is good and still acceptable for them as the processor that they are using is quite fast. The respondents agreed that the system can avoid any clashing between subjects The respondents agreed that the system can avoid any clashing between lecturers The respondents agreed that the system can avoid any clashing between times The respondents agreed that the system can avoid any clashing between venues How is the user interface and layout design? How is the color combination of Timetable Management System? How is the text style and text size? Was it easy to read? How is the navigation structure in the Timetable Management System? What do you think about the contents in Timetable Management System? Please rate the efficiency of the webpage loading time. execution of the previously defined training plan. Two respondents stated that the navigation structure in the system is good and two respondents stated average. Please rate the efficiency of the data processing time. All of the respondents agreed that the system is useful for FCSIT to have the systematic timetable system. Timetable Management System 117 . All respondents stated that the processing time is average. It is pleasant to view because of the soft green and yellow color scheme.

12 Future System Enhancement The Timetable Management System can be further enhanced by adding the following:Linking to the ISIS database. the University has one reference database. All the basic requirements of a timetable such as timetable for student and lecturers. Besides that. Therefore. the usage can be increased to any faculties instead of FCSIT only. 5. there is no proper documentation for this phase. This is because the student data is taken from the ISIS database. 5. this system can be considered a useful system since it helps the lecturer to improve their process of preparing the timetable. the task for the administrator is less.is only a system developed for this dissertation. So that. Administrator has to key in the data and lecturer for the first time registration. enquiry for free classes and booking for the free classes are available. With the linking to ISIS database.11 Limitation Of The System Timetable Management System was created for the use of FCSIT. master timetable for lecturers. By providing support through the Timetable Management system. 5. The main limitation with Timetable Management System is that it is not linking to the current student database. 118 . This is because if the system connects to the current database the requirement for the hardware and software is higher. another limitation is that the FCSIT must have a permanent administrator to maintain the database in the system.13 Conclusion Generally.

to assist administrator. a user manual for lecturer is included in Appendix C and user manual for student is included in Appendix B. a user manual for administrator is included in Appendix A. 119 . lecturer and student on how to use the system. If the system is successfully upload to host.Timetable Management System is not yet uploaded to the host.

Sign up to vote on this title
UsefulNot useful