DEVELOPMENT OF LEGENDA ONLINE STUDENT TIME TABLE SYSTEM

FINAL YEAR PROJECT FINAL REPORT
ABUBAKAR MAGIRA TOM
U0957657

A thesis submitted in part fulfillment of the degree of B.sc (Hons.) In Software Engineering with the supervision of Dr. Mia Torrez and moderated by Mdm Teo Siew

School of Computer Science and Information Technology Linton University College In Collaboration with University of East London December 2012

DECLARATION
I Abubakar Magira Tom, hereby declare that the project work entitled “[LEGENDA ONLINE STUDENT TIME TABLE]” submitted to [LINTON UNIVERSTIY COLLEGE], is a record of an original work done by me under the guidance of [Dr. MIA TORREZ], and this project work has not performed the basis for the award of any Degree or diploma/ associate ship /fellowship and similar project if any.

___________________
[ABUBAKAR MAGIRA TOM]
Student
Date:

__________________ [Dr. MIA TORREZ]
Supervisor
Date:

___________________
Mdm TEO SIEW
Project Coordinator
Date:

ACKNOWLEDGEMENT
The special thank goes to my helpful supervisor, Dr Mia Torrez. The supervision and support that she gave truly help the progression and smoothness of my research topic. The cooperation is much indeed appreciated sir. My grateful thanks also go to both Mdm. TEO SIE. A big contribution and hard worked from both of you during the eight week is very great indeed. All projects during the program would be nothing without the enthusiasm and imagination from both of you. Not forget, great appreciation go to the rest of friends staff that help me from time to time during the project.
Special thanks also to my dad, ALH Magira Tom and my lovely mom Hajje Hadiza Magira tom for supporting me mentally and physically, I cannot go anywhere without your caring and love. Thank you very much……

ABSTRACT
LINTON UNIVERSITY COLLEGE (LEGENDA) is formally known as “Kolej Linton”. It was founded in 1985 in Ipoh, Perak Malaysia (LINTON, 2011). In 2005, the university started offering international students with degree and HND (higher national diploma) programs Linton University College comprises of local students (Malaysians) and international students (foreigners) from all over the world. Example includes China, Nigeria, Tanzania, Cameroon, Sudan, Persia, Bahrain, Iraq etc. This university basically offers program for foundation, diploma, degree and masters programs in collaboration with the University of east London (UEL, 2012), excel University (EXCELFOUNDRY, 2012) and Coventry University (COVENTRY, 2012) certifications. Currently, Linton University College has more than 5000 international students. In the year 2010, the universities is further upgraded from “Kolej Universiti” to “Linton University College” (LINTON, 2011); because of its academic achievements towards assuring parents that their products (students) will be up-to-date and meet-up the expectations of standardized companies and industries in the globe (world).
However, Linton University College faces the issues of generating accurate time table for Information Technology School (school of IT). One of the major issues faced is the manual generation of student time table. As students time tables are generated manually, it is almost impossible to for the IT SCHOOL or DEPARTMENT to provide students with accurate, reliable, consistent, complete and error free time tables without the clashing of venues, conflicting lecture time, late collection of student time table, waiting in the queue for hours etc. Therefore, for us to address the stated problems or issues, the proposed system “Legenda online student time table system” is the solutions to the stated problems.

TABLE OF CONTENT DEVELOPMENT OF LEGENDA ONLINE STUDENT TIME TABLE SYSTEM i DECLARATION ii ACKNOWLEDGEMENT iii ABSTRACT iv LIST OF TABLES xv CHAPTER 1 1 INTRODUCTION 1 1.1 INTRODUCTION 1 1.2 BACKGROUND OF STUDY 2 1.3 RATIONALE 3 1.4 PROBLEM STATEMENT 3 1.4.1 MANUAL SYSTEM 3 1.4.2 CLASHING LECTURE-VENUE 3 1.4.3 LATE COLLECTION OF TIME TABLE 4 1.4.4 DIFFICULTY IN TIME TABLE RETRIEVAL 4 1.5 AIM 4 1.6 OBJECTIVES 4 1.7 SCOPE 5 1.8 RESEARCH QUESTION 5 1.9 SUMMARY OF CHAPTERS 6 1.9.1 CHAPTER 1 6 1.9.2 CHAPTER 2 6 1.9.3 CHAPTER 3 7 1.9.4 CHAPTER 4 7 1.9.5 CONCLUSION 7 CHAPTER 2 8 LITERATURE REVIEW 8 2.1 INTRODUCTION 8 2.2 ONLINE STUDENT TIME TABLE 8 2.3 DEVELOPMENT METHODOLOGY 10 2.3.1 INFORMATION SYSTEM 10 2.4 SOFTWARE DEVELOPMENT METHODOLOGY (SDLC) 13 2.4.1 PLANNING 14 2.4.2 ANALYSIS 15 2.4.3 DESIGN 15 2.4.4 IMPLEMENTATION 15 2.4.5 SYSTEM MAINTAINANCE 15 2.4.6 WATERFALL METHODOLOGY 16 2.4.7 PARALLEL DEVELOPMENT 17 2.4.8 VIRAL MODEL (V-MODEL) 17 2.4.9 ITERATIVE DEVELOPMENT or PHASED DEVELOPMENT 18 2.4.10 SYSTEM PROTOTYPE 19 2.4.11 THROWAWAY PROTYPE 20 2.4.12 EXTREME PROGRAMMING 21 2.4.13 JUSTICATION OF SELECTED METHODOLOGY 22 2.5 DATABASE SYSTEM 23 2.5.1 MICROSOFT ACCESS 24 2.5.2 MYSQL SERVER R2 24 2.5.3 XML 25 2.5.4 JUSTIFCATION OF DATABASE TO BE USED 27 2.6 PROGRAMMING LANGUAGE 27 2.6.1 PHP 27 2.6.2 ASP.NET 28 2.6.3 JUSTIFICATION OF PROGRAMMING LANGUAGE 30 2.7 INTERFACE DESIGN 30 2.7.1 MICROMEDIA DREAMWEAVER 30 2.7.2 NETBEANS 31 2.7.3 FRONT PAGE 31 2.7.4 JUSTIFICATION 33 2.8 FACT FINDING TECHNIQUE 33 2.8.1 REQUIREMENT 34 2.8.2 REQUIREMENT GATHERING TECHNIQUE 34 2.9 REQUIREMENT ANALYSIS TECHNIQUES 38 2.9.1 BUSINESS PROCESS AUTOMATION 38 2.9.2 BUSINESS PROCESS REENGINEERING 38 2.9.3 BUSINESS PROCESS INPROVEMENT 38 2.9.4 JUSTIFICATION OF SELECTED ANALYSIS TECHNIQUE 39 2.10 NETWORK ARCHITECTURE 39 2.10.1 TWO-TIER ARCHITECTURE 40 2.10.2 THREE-TIER ARCHITECTURE 40 2.10.3 JUSTIFACTION OF SELECTED TIER ARCHITECTURE 41 2.11 MODELING TOOLS 41 2.11.1 RATIONAL ROSE ENTERPRISE EDITION 42 2.11.2 MICROSOFT VISIO 42 2.11.3 JUSTIFACTION OF MODELING TOOL TO BE USED 43 2.12 BENEFITS OF LEGENDA ONLINE STUDENT TIME TABLE SYSTEM 44 2.12.1 Organization 44 2.12.2 Student Sectioning 44 2.12.3 Simplicity 44 2.12.4 Swift Access 44 2.12.5 User friendly 44 2.13 EXISTING SYSTEM 45 2.14 RELETED SYSTEMS 45 2.14.1 MIMOSA SOFTWARE 45 2.14.2 VICTORIA UNIVERSITY MELBOURNE, AUSTRALIA 47 2.14.3 COMPARISON BETWEEN OF RELATED SYSTEMS 48 2.15 SUMMARY 50 CHAPTER 3 51 METHODOLOGY 51 3.1 INTRODUCTION 51 3.2 PROBLEM STATEMENT 51 3.2.1 MANUAL SYSTEM 52 3.2.2 LATE COLLECTION OF TIME TABLE 52 3.2.3 DIFFICULTY IN TIME TABLE RETRIEVAL 52 3.2.4 CLASHING LECTURE VENUE 52 3.3 SOLUTIONS TO THE PROBLEMS 53 3.3.1 MANUAL SYSTEM 53 3.3.2 LATE COLLECTION OF TIME TABLE 53 3.3.3 CLASHING LECTURE VENUE 53 3.3.4 EASY RETRIEVAL OF TIME TABLE 53 3.4 RESEARCH METHOD 54 3.4.1 AWARENESS OF PROBLEMS 54 3.4.2 SUGGESTION 55 3.4.3 DEVELOPMENT OF ARTIFACT 55 3.4.4 EVALUATION 56 3.4.5 CONCLUSION 56 3.5 SOFTWARE DEVELOPMENT LIFR CYCLE (SDLC) 57 3.5.1 CHOSEN METHODOLOGY 58 3.5.2 STAGES INVOLVED IN THROWAWAY PROTOTYPING 59 3.6 FACT FINDING TECHNIQUE 63 3.6.1 INTERVIEW 63 3.6.2 QUESTIONNAIRE 64 3.7 DATABASE 64 3.8 ETHICAL ISSUES 65 3.8.1 PRIVACY 65 3.8.2 ACCESSIBILITY 66 3.8.3 DATA FUSION 66 3.8 CONCLUSION 67 CHAPTER 4 68 ANALYSIS 68 4.1 INTRODUCTION 68 4.2 REPORT OF QUESTIONNAIRES 69 4.3 ANALYSIS 77 4.3.1 ANALYSIS OF THE INTERVIEW SESSION 77 4.4 REQUIREMENT ANALYSIS 78 4.4.1 FUNCTIONAL REQUIREMENTS 78 4.4.2 NON-FUNCTIONAL REQUIREMENT 81 4.4.3 HARDWARE REQUIREMENT 84 4.4.4 SOFTWARE REQUIREMENT 86 4.4.5 NETWORK REQUIREMENT 87 4.4 CONCEPTUAL DATA MODEL 90 4.4.1 NORMALISATION 91 4.4.2 LOGICAL DATA MODEL 96 4.4.2 PHYSICAL DATA MODEL 97 4.5 NAVIGATIONAL CHART 99 4.5.1 NAVIGATIONAL CHART 100 4.6 FLOW CHART 101 4.6.1 FLOW CHART 102 4.7 CONCLUSION 105 CHAPTER 5 106 DESIGN 106 5.1 INTRODUCTION 106 5.2 USE CASE 106 5.3 REQUIREMENT DESCRIPTION TABLE 111 5.3.1 ADD LECTURER 112 5.3.2 ADD STUDENT 113 5.4 CLASS DIAGRAM 114 5.4.1 ASSOCIATION 114 5.4.2 INHERITANCE/GENERALISATION 114 5.4.3 DEPENDENCY 115 5.5 SEQUENCE DIAGRAM 117 5.7.1 SEQUNCE DIAGRAM OF LOGIN 118 5.7.2 SEQUENCE DIAGRAM OF ADD LECTURER 119 5.6 COLLABORATION DIAGRAM 121 5.6.1 COLLABORATION DIAGRM OF CREATE TIME TABLE 121 5.6.2 COLLABORATION DIAGRAM OF ADD LECTURER 122 5.6.3 COLLABORATION DIAGRAM OF ADD VENUE 123 5.7 ACTIVITY DIAGRAM 123 5.7.3 CHANGE PASSWORD ACTIVITY DIAGRAM 126 5.7.4 CREATE TIME TABLE ACTIVITY 127 5.8 STATE CHART DIAGRAM 128 5.8.1 A STATE 128 5.8.2 TRANSITION 128 5.8.3 INITIAL STATE 128 5.8.4 FINAL STATE 128 5.8.5 SYNCHRONIZATION 128 5.8.1 ADD LECTURER STATE CHAT 129 5.8.2 CREATE TIMIE TABLE STATE CHART DIGRAM 130 5.8.3 ADD VENUE STATE CHART DIAGRAM 131 5.9 STORY BOARD 132 5.9.1 LOGIN 133 5.9.2 ADMINISTRATOR PAGE 134 5.9.3 View Courses 135 5.9.4 Add Courses 136 5.9.5 Edit Courses 137 5.9.6 Delete Courses 138 5.9.7 ADD LECTURER 139 5.9.8 EDIT LECTURER 140 5.9.9 DELETE LECTURER 141 5.9.9 CREATE VENUE 142 5.9.10 EDIT VENUE 143 5.9.11 DELETE VENUE 144 5.10 DEPLOYMENT DIAGRAM 145 5.10.1 PROCESSOR NODE 145 5.10.2 DEVICE NODE 145 5.11 CONCLUSION 147 CHAPTER 6 148 IMPLEMENTATION 148 6.1 INTRODUCTION 148 6.2 DEVELOPMENT ENVIRONMENT 148 6.2.1 HARDWARE DEVELOPMENT ENVIRONMENT 149 6.2.2 SOFTWARE DEVELOPMENT REQUIREMENT 150 6.2.3 NETWORK DEVELOPMENT REQUIREMENT 152 6.3.1 INTERFACE VISIBILITY 154 6.3.2 CONSISTENT INTERFACE 155 6.3.3 SYSTEM COLOR 156 6.3.4 SYSTEM ARCHITECTURE 156 6.4 IMPLEMENTATION OF GUI 158 6.4.1 Add Course Page 158 6.4.2 CREATE TIMETABLE PAGE 160 6.4.3 Delete Course PAGE 162 6.4.4 VIEW TIMETABLE PAGE 164 6.5 DATABASE IMPLEMENTATION 166 6.5.1 SERVER 168 6.6 SUMMARY 169 CHAPTER 7 170 TESTING 170 7.1 INTRODUCTION 170 7.2 TEST PLAN 170 7.2.1 BLACK BOX TESTING 171 7.2.1.1 FUNCTIONAL TESTING 172 7.2.2 WHITE BOX TESTING 181 7.3 CONCLUSION 185 CHAPTER 8 186 CONCLUSION AND RECOMMENDATION 186 8.1 CONCLUSION 186 8.1.1 SUMMARY OF THE CHAPTERS 186 8.2 PROBLEMS ENCOUNTERED 188 8.3 STRENGTHS OF LEGENDA ONLINE STUDENT TIME TABLE SYSTEM 188 8.4 LIMITATIONS OF LEGENDA ONLINE STUDENT TIME TABLE SYSTEM 189 8.5 FUTURE ENHANCEMENT 189 8.6 LESSON LEARNT 190 8.7 REFLECTION 190 8.8 MILE STONE 191 ONLINE REFERENCE 196 B.3.8 Reflections, Feedbacks from Friends and Materials Studied In This Module 218 I1 LOGIN 270 I2 ADMINISTRATOR PAGE 271 I3 View Courses 272 I4 Add Courses 273 I5 Edit Courses 274 I6 Delete Courses 275 I7 ADD LECTURER 276 I8 EDIT LECTURER 277 I9 DELETE LECTURER 278 I10 CREATE VENUE 279 I11 EDIT VENUE 280 I12 DELETE VENUE 281
REFERENCE
APPENDIX A PROPORSAL
APPENDIX B PERSONAL DEVELOPMENT PLAN
APPENDDIX C INTERVIEW QUESTIONS
APPENDIX D USE CASE DESCRIPTION
APPENDIX E SEQUENCE DIAGRAM
APPENDIX F COLLABORATION DIAGRAM
APPENDIX G ACTIVITY DIAGRAM
APPENDIX H STATE CHART DIAGRAM
APPENDIX I STORY BOARD
APPENDIX J USER MANUAL
APPENDIX K LOG SHEETS
APPENDIX L GANTT CHART

LIST OF FIGURE Figure2.1: Software Development Life Cycle 14 Figure2.2: Waterfall Model 16 Figure2.3: Parallel Development 17 Figure2.4: Viral Model (V-Model) 18 Figure2.5: Iterative or Phased Development 19 Figure2.6: System Prototype 20 Figure2.7: Throwaway Prototype 20 Figure 2. 8: Extreme Programming 21 Figure 2. 9: Mimosa Software Graphical User Interface (GUI) 47 Figure 2. 10: Graphical User Interface of Victoria University Time Table System 48 Figure 3. 1: Ishikawa Diagram 57 Figure 3. 2: General Research Methodology 59 Figure 3. 3: Throwaway Prototype 62 Figure 4. 1: Analysis of Clashign Lecture Venue 71 Figure 4. 2: Analysis of Changed Lecturer Timetable 72 Figure 4. 3: Analysis of Rescheduled Lecture Time 73 Figure 4. 4: Analysis of Lecturer Venue 73 Figure 4. 5: Analysis of Collect Lecture Timetable 74 Figure 4. 6: Analysis of Collect Time Table Online 75 Figure 4. 7: Analysis of Time Table Format 75 Figure 4. 8: Analysis of Font Size 76 Figure 4. 9: Analysis of Time Table Color 77 Figure 4. 10: Navigational Chart 96 Figure 4. 11: Flow Chart 98 Figure 5. 1: Use case Diagram 103 Figure 5. 2: Class Diagram 109 Figure 5. 3: Sequence Diagram of Login 111 Figure 5. 4: Sequence Diagram of Register Lecturer 112 Figure 5. 5: Sequence Diagram of Register Student 113 Figure 5. 6: Collaboration Diagram of Adding Course to Lecturer 114 Figure 5. 7: Collaboration Diagram of Change Password 115 Figure 5. 8: Collaboration Diagram of Create Time Table 116 Figure 5. 9: Activity Diagram of Assign Course to Lecturer 118 Figure 5. 10: Change Password 119 Figure 5. 11: Create Time Table Activity Diagram 120 Figure 5. 12:Assign Course To Lecturer Activity 122

Figure 5. 13: Create Time Table Activity Diagram 123 Figure 5. 14: Delete Lecturer Activity 124 Figure 5. 15: Login storyboard 126 Figure 5. 16: Administrator Storyboard 127 Figure 5. 17: Register Lecturer Page Story Board 128 Figure 5. 18: Add Course Storyboard 129 Figure 5. 19: Add Course Storyboard 130 Figure 5. 20: Add Course Storyboard 131 Figure 5. 21: Deployment Diagram 133 Figure 6. 1: Three-tier Architecture 142 Figure 6. 2: GUI and Add New Course 143 Figure 6. 3: HTML and PHP code of Add course 144 Figure 6. 4: Create Timetable Page 145 Figure 6. 5: Code for Create Timetable Page 146 Figure 6. 6: Create Timetable Page 147 Figure6. 1: Three-tier Architecture 157 Figure6. 2: GUI and Add New Course 158 Figure6. 3: HTML and PHP code of Add course 159 Figure6. 4: Create Timetable Page 160 Figure6. 5: Code for Create Timetable Page 161 Figure6. 6: Create Timetable Page 162 Figure6. 7: Delete Course Page 163 Figure6. 8: GUI of View Timetable Form 164 Figure6. 9: p code to display Time Table 165 Figure6. 10: Database Implementation 166 Figure6. 11: Relationship between tables in the database 167 Figure6. 12: Php Server Connection Code 168 Figure 7. 1: Black box Testing 157 Figure 7. 2: White box Strategies and input 161
LIST OF TABLES Table2.1 : Comparison of TPS, MIS, DSS and ESS 12 Table2.2: Criteria for selecting Methodology 22 Table2.3: Comparison between MS access, Xml and MySQL database 26 Table2.4: Comparison between ASP.Net and Php programming language 29 Table2.5: Comparison between Micromedia Dreamweaver and Front Page 32 Table2.6: Comparison of requirement gathering techniques 37 Table2.7: Comparison between BPA, BPI and BPR 39 Table2.8: Comparison between two-tier and three-tier architecture 40 Table2.9: Comparison between Rational rose and Microsoft Visio 42 Table2.10: Comparison between related systems 48 Table4. 1: User requirements and System requirements of the proposed system 80 Table4. 2: Non-functional requirement 82 Table4. 3: Hardware requirement 84 Table4. 4: Software requirement 86 Table4. 5: Network requirement 88 Table5. 1: The Use Case Diagram Guide Lines 107 Table5. 2: Functions of the system 108 Table5. 3: Login Use Case Description 111 Table5. 4: ADD LECTURER Use case Description 112 Table5. 5: ADD STUDENT Use Case Description 113 Table5. 6: Class Diagram Guide Lines 115 Table6. 1: Hardware Development Requirement 149 Table6. 2: software development environment 151 Table6. 3: Network Development Requirement 152 Table6. 4: Usability Heuristics Table 154 Table7. 1: Black box testing (Functional Testing) 172 Table7. 2: white box For Login Function 181 Table7. 3: white box testing for Add Course 183

CHAPTER 1
INTRODUCTION
1.1 INTRODUCTION
Legenda Online Student Time Table System is a web-based time table system that will allow or help students to acquire their time table online (Download.cnet, 2012). This system is needed to provide student with appropriate time tables and will help the university or college “to do things right (i.e. efficiently) and “do the right thing” (i.e. effectively).
However, the proposed system is concerned with building and designing the user interface of “Legenda Online Student time table System”. Introducing human computer interactions (HCI), GUI (graphical user interface), psychology, ergonomic, graphical designers, human factors and user needs. This project is essentially concerned with the acceptance (understanding) of how people and computers interact and carry out tasks and how interactive computer systems are designed and maintained (Julie and Andrew, 2003). The proposed system “Legenda Online Student Time Table System” system is also concerned with the user interfaces (UI), GUI (Graphical User Interface); to know who are the users and then designing the system with suitable color, pictures, navigations and pages for students and Administrator.

1.2 BACKGROUND OF STUDY
LINTON UNIVERSITY COLLEGE (LEGENDA) is formally known as “Kolej Linton”. It was founded in 1985 in Ipoh, Perak Malaysia (Linton, 2011). In 2005, the university started offering international students with degree and HND (higher national diploma) programs Linton University College comprises of local students (Malaysians) and international students (foreigners) from all over the world. Example includes China, Nigeria, Tanzania, Cameroon, Sudan, Persia, Bahrain, Iraq etc. This university basically offers program for foundation, diploma, degree and masters programs in collaboration with the University of east London (UEL, 2012), excel University (Excelfoundry, 2012) and Coventry University (Coventry, 2012) certifications. Currently, Linton University College has more than 5000 international students. In the year 2010, the universities is further upgraded from “Kolej Universiti” to “Linton University College” (LINTON, 2011); because of its academic achievements towards assuring parents that their products (students) will be up-to-date and meet-up the expectations of standardized companies and industries in the globe (world).
However, Linton University College faces the issues of generating accurate time table for Information Technology School (school of IT). One of the major issues faced is the manual generation of student time table. As students time tables are generated manually, it is almost impossible to for the IT SCHOOL or DEPARTMENT to provide students with accurate, reliable, consistent, complete and error free time tables without the clashing of venues, conflicting lecture time, conflicting lecture-venue allocation, late collection of student time table, waiting in the queue for hours etc. Therefore, for us (the author) to address the stated problems or issues, the proposed system “Legenda online student time table system” should be implemented because it is the solutions to the stated problems and will make life easier for students and administrator.

1.3 RATIONALE
Nowadays, computer systems are used globally for different purposes. Universities and Colleges all over the world faces the issues of generating adequate, consistent and complete time table for their students and staffs. For us (the author) to address these problems, we must explore information technology (IT) to its fullest. The proposed system (i.e. Legenda Online Student Time Table system) will help administrator to efficiently create lecture time table as well as students to download or save the time table on their system. The system should allow students to login to the system and allow the administrator to create student lecture time table. Therefore, building an online student time table system that will allow its users “to do things right” efficiency and be “doing the right thing” effectiveness.
1.4 PROBLEM STATEMENT
To analyze and develop “Legenda online student time table system” that will unravel the difficulties and problems in assigning proper time table to students, late collection of time table and clashing of lecture venues due to the fault associated with the paper based system. The problems or issues include the following:-
1.4.1 MANUAL SYSTEM
The current system is a manual system. Time table for students is generated manually (i.e. on paper’s), which is tedious, complicated and time consuming. Thus, much time is needed to creating a simple time table for students and staffs. Due to the above issues, time tables are given to student couple (many) of time, all because of the inconsistencies of the “As-Is System” (i.e. the current system).
1.4.2 CLASHING LECTURE-VENUE
Lecture-venue is allocated to students randomly due to the fact that the current system is a paper based system (Manual System), where by clashing of venues occurs all the time. This will drastically affect student’s performance and discourage them from attending classes in the future, which are due to wrong lecture venue allocation.
1.4.3 LATE COLLECTION OF TIME TABLE
The paper based system of generating student time table is not reliable and easy to handle. It will take days or even weeks to schedule the semester time table for students, thereby making it hard (tedious) for the school management (administrator and students etc.) to complete the entire syllabus on the stipulated amount of time. This way, the school will be left behind and the students would not perform well in that semester and future semesters as well.
1.4.4 DIFFICULTY IN TIME TABLE RETRIEVAL
In the current system, students will wait in the queue for very long time in order to collect their lecture time table. Assuming that the school has more than 200 students, how much time is required to collect time table? Using such system is troublesome and time consuming to the students.
1.5 AIM
To design an online timetable system for student with simple and user friendly interface (UI).
1.6 OBJECTIVES
1.6.1 To compare related systems.
1.6.2 To provide students with lecture time table.
1.6.3 To provide system that will serve student satisfaction (i.e. easier to locate lecture venue). 1.6.4 To provide system that will facilitate students to print out or download time table. 1.6.5 To provide system that will have an improved user interface (UI) and graphical user interface (GUI) (i.e. following KISS principles, keep it simple and straight forward) (Mehmet Akşit, Mira Mezini, Rainer Unland, 2003). 1.6.6 To know the productivity tool (design tool) that will be used to build the system. 1.6.7 To know the database tool that will be used to design and store data in the system. 1.6.8 To document the development of whole system so as to make it easy for future upgrade or improvement. 1.6.9 To implement the system (Online Student Time Table System). 1.6.10 To test the finished system (i.e. Online Student Time Table System). 1.6.11 To provide user manual for the system.
1.7 SCOPE
The scope of this project or research work is restricted to certain functionalities (features) which will be explained in details. The system will be an online system. It will provide its humble users with suitable login process for existing students, new students and administrator. The students don’t have to go to the information school (IT School) physically to collect their lecture time tables, the system will provide student with the function to collect their timetable online or send it to their email address. The administrator will be able to add students and staff into the database.
Moreover, the use of App server to run the program in the local host, MySQL server R2 for creation of database or xml (Extensible markup language) and Php (hypertext preprocessor) for the server site scripting, html (hypertext markup language) for design, Css (cascading style sheet) for design and lastly Dreamweaver or front page to build the complete system.
1.8 RESEARCH QUESTION
Research question is an organizing element for the topic under study (Santiago, 2009). The research question will guide you to complete your project. My project research question includes the following; 1.8.1 What do I want to know about my topic? 1.8.2 Can the system be of importance to its users? 1.8.3 Will the proposed system be completed on time and delivered to its users? 1.8.4 What if the system is rejected by its users? 1.8.5 In what ways is the system useful to its users? 1.8.6 How can the system be improved in the future? 1.8.7 What is the suitable database to be used? 1.8.8 What is the appropriate tool to develop the system? 1.8 SUMMARY OF CHAPTERS
Below are the summaries of chapters from chapter one to chapter five:
1.9.1 CHAPTER 1
The aim of this research (project) is to design and build useful and user friendly information system that will aid students and staff to do work efficiently and effectively. The system is a web based system. Thus, all the objectives of the system will be achievable by implementing the “Legenda online student time table system”. However, the system would be build using productivity software like; Php, xml, Microsoft access, MySQL Server R2, and Xampp server (used to run programs on the local host or computer system).
1.9.2 CHAPTER 2
In this chapter (chapter 2), we concentrate and emphasize more on literature review there by, generally criticizing the software or system development life cycle (SDLC), Requirement Gathering techniques (RGT) and the requirement analysis Techniques (RAT), database and the programming language that will be used to build the system. Software development life cycle comprises of technique, methods and stages that are involved in information system development (Searchsoftwarequality, 2012). Some of the SDLC techniques include; waterfall and its variants (viral model and parallel model), incremental model, rapid application development (RAD), prototyping, throwaway prototyping, and extreme prototyping (XP) respectively. The requirement gathering techniques include; questionnaire, observation, document analysis, interview and RAD (rapid application development) concurrently. The requirement analysis technique includes business process automation (BPA), business process improvement (BPI) and business process reengineering (BPR). However, all of the above listed with be explained in details in this chapter (chapter 2).

1.9.3 CHAPTER 3
Chapter three (3) is explicitly concerned with the study of the chosen methodology that shall be used in the development of the proposed system and the fact-finding techniques will be explained. However, the technique that will be used in developing the system is “PROTOTYPING”. Prototyping is the process of putting together a working model in order to test various aspects of a design, illustrate ideas, gather early user’s feedback and reduces the risk and cost of the system (Dotnetfunda, 2012). Thus, using this technique (prototyping model) all the user’s requirement will be identified, because most of the users do not know what they want. Prototyping gives room for all users (stake holders) to critically analyze and evaluate the system prototype (system sample) and provide corrective feedback.
1.9.4 CHAPTER 4
Chapter four (4) focuses on the analysis and design of the system. These include all of the UML notations, model or diagram. Sequence diagram, collaboration diagram, activity diagram, package diagram, deployment diagram, state diagram, class diagram, use case diagram and component diagram shall be discussed in detail and documented in this chapter (4). Also, the database structure and normalization will be documented as well. UML (Unified Modeling Language) is a complete language that is used to design, visualize, construct and document software. Uml follows object oriented (O.O) method or approach for delivering, building and maintaining software systems.
1.9.5 CONCLUSION
In conclusion, after critically analyzing and quantifying the main aim and objectives of the proposed system “Legenda Online Student Time Table System”, introducing the system, identifying the problem statements, the scope of the system, the research questions are all covered in this chapter. The system would be well documented in the coming chapters. That is, in chapter 1, 2, 3 and chapter 4, 5 and the conclusions (i.e. chapter 6) respectively.
CHAPTER 2
LITERATURE REVIEW
2.1 INTRODUCTION
In the literal sense, a review is the critical examining of a specific document on a research topic. Consequently, a review brings the background of the proposed study (Kohlbacher, 2006). Online timetable is the process of assigning events or activities to resources such as time (timeslots), space (rooms) and personnel (teachers and professors) which satisfies all the constraints (Safaai et.al, 2009).
However, (Özcan, Parkes and Alkan, 2012) stated that; the general task of solving the time table scheduling problems is iterative and time consuming. This implies that, the time table system have a very conflicting issues that includes the availability of venue and l students, which might lessen the students understanding and concentration via out the modules.
2.2 ONLINE STUDENT TIME TABLE
According to Scahaerf (2004), time table problem comprises of the issues or problems with the sequential meetings between students and lecturers in a stipulated period of time. These imply that, assigning correct and effective time table cannot be achieved. Thus, several techniques have been developed to automatically solve the problem (Boers, 2001). The optimal scheduling of time table to in high schools, universities and colleges is time consuming for the person(s) in charge of the planning activities. Therefore, timetabling solutions are highly dependent on institutions that organize the activities because each institution has its own platform (Sousa, 2008).
Timetable comprises of many issues from which most recognized institution and higher educational institute’s faces. Quite often, time table is generated manually (by hand) or times it involves re-using (editing and modifying) the previous time tables so that no clashing of venue and error will occur. Therefore, to tackle the above issues, a GENERIC ALGORITHMS (GA) must be must be used. According to Müller (2003), Generic Algorithm (GA) is an optimization techniques or tools that “models principles of evolution” and searching problems. Many Authors relates Generic Algorithm with Evolutionary Algorithms (EA). Evolutionary Algorithm provides improvements (solutions) to optimization techniques which includes; Mutation, Inheritance, Selection and Crossover. Costa (2003) conducted a research on Tabu search Algorithm for computing an operational timetable. Tabu Search is a general technique that will generate complete and comprehensive timetable. However, many researchers argue on which Generic Algorithm is the most suitable and simple for generating time table. For instance, Yang, Ding and Zhang (2010) stated that; Tabu search is used mainly for optimization, but it is not use for calculating time in the program.
However, Kendal (2005) stated that, many approaches and models are proposed to solving the constraints or difficulties associated with a variety of time table problems. There are a number of solutions growing rapidly with the advent and advancement of new technology in the world of Information Technology (Hew and Brush, 2007). A time table problem is a problem with four parameters, T is the limited set of “time”, R is the limited set of “resources”, M is the finite set of “meetings” and C is the limited set of “constraints” (Burke, Werra and Kingston, 2004). Time table problem deals with the assigning of lectures to specific time slots and room by “satisfying hard constraints and soft constraints”. “Hard constraints cannot be violated under any circumstances” and “soft constraints are desirable but not absolutely critical. Therefore, it is impossible to find feasible solution that will satisfy all of the software constraints.
Moreover, Nandhin (2009) conducted a survey on: A survey of Simulated Annealing Methodology for University Course Time Tabling system: stated that, time table issues are divided into three (3) main classes, i.e. school, university and time table system. In his survey, the problems are solved in AI (Artificial Intelligent) method, local search based techniques or simulated Annealing (S.A), Hill climbing, and graph coloring and variable Neighborhood search respectively. The time table problem may includes the following; the set of classroom, capacity of classroom and the availability of timetable. Each classroom will have a unique ID and a unique name, set of courses and the course code that goes with the sets of qualified lecturers and their field of specialty, the schedule timetable for lecturers that will require unique ID and a unique name. However, the lecture time must not overlap and the courses must not overlap as well. These are the some of the constraints that will be considered in preparing and designing the timetable (i.e. to say, the time for networking programming CN3044 and the Advance information system must not overlap). Thus, each and every subject has a unique name and id in the database.
2.3 DEVELOPMENT METHODOLOGY
A Methodology is a series of processes, methods, techniques and principles used to deliver software products. The processes are the steps; methods are the techniques and principles that should be applied when building any kind of information system. According to Bergmann (2002), a Methodology uses different methods or ways of guidance to the phases of the software development life cycle (SDLC). Quite often, a methodology shows the way (guide) or activities and methods that are involved to successfully build a certain system (product). However, Darwiesh (2008) said; methodology is a way of guiding the software development team by imposing discipline, guidelines, ethics and standards via out the phases of the software development cycle. A good methodology must comprise of project management, cost, time, project plan, procedures etc.
2.3.1 INFORMATION SYSTEM
Information system plays a vital role in the management of small, large and medium organizations. Information system refers to the collection of hardware, software, procedure, data, people and procedure that will support our basic and daily activities in an organization. Information system is an organized set of components or elements that collect input, process it, store and gives out information system. There are basically four major types of information system which includes; Transaction Processing System (TPS), Management information system (MIS), Decision Support System (DSS) and Executive Support System (ESS) respectively.
2.3.1.1 TRANSACTION PROCESSING SYSTEM
The Transaction processing system is used mainly at the operational level. Thus, often used for transaction and online processing, online ordering of laptops or buying a software package in Apple store. According to (Bernstein, Newcomer 2009), transaction processing is a way of intermingling between one person and another in exchange for something. Transaction processing system helps in creating scalable applications (in 3-tier architecture). Example of TPS includes paying employee, saving student’s record, keeping record of student’s tuition fee etc.
2.3.1.2 MANAGEMENT INFORMATION SYSTEM
Management information system (MIS) is used at the management level of the organization. According to Daft, Willmott (2010), management information system (MIS) gives information for decision making in an organization. Though, many organizations have their own ways of operations. Lucey (2004) stated that; MIS must be designed and generated in organizations so as to know the design, knowledge, management involvement and the technical factors as well. Management information system provides efficient way of coordinating departments (office) and managing daily business activities. Example includes; payroll system, managing accounts, stock control etc.
2.3.1.3 DECISION SUPPORT SYSTEM
A Decision Support System (DSS) is an information system that is at the management level of the organization. DSS uses the information provided by the Transaction Processing System (TPS), view and decide upon the improvement or drawbacks of some of the organizational departments (e.g. marketing department, manufacturing and production department, finance and accounting and lastly, human resources). DSS helps or provides flexibility to the decision-makings in an organization and provides valuable decisions that will make the organizations achieve their aim and objectives easily.
2.3.1.4 EXECUTIVE SUPPORT SYSTEM
The executive support system (ESS) supports the strategic level (senior level) of the organization. ESSES mainly view the company’s achievements and know what the organization will like or be in the next 5-10 years (i.e. in the future). ESS is involved in profit planning, personal planning, 5-10 years sales forecasting and 5-10 years’ operating plan.
Table2.1 : Comparison of TPS, MIS, DSS and ESS FACTORS | TPS | MIS | DSS | ESS | * LEVEL | * Serves at the operational level | * Serves at the management level | * Serves at the management level | * Serves at the strategic level | * INFORMAION | * Provides rich information to DSS and MIS | * Uses the information and analyze it | * Uses information and decide on what to be done | * Uses the information and take final decision | * PROBLEM TYPES | * Viewed as information system infrastructure | * MIS is used only with structured problems | * Good at handling un-structured problems that cannot be easily programmed | * Good at providing specialized decision to meet the needs of senior management | * SPEED | * Usually slow because it organize organization records daily (operations) | * Response is a bit faster than that of TPS | * It is flexible and can be easily implemented by users | * It is the fastest because, it doesn’t have to compile or gather information from scratch |
2.3.1.5 JUSTIFICATION OF SELECTED INFORMATION SYSTEM
The author would use Management Information System (MIS), as the proposed type of information system that will adopt in building the “Legenda Online Student Time Table System”. However, TPS (Transaction Processing System’s) are systems that are used on daily basis (daily) and on the operational level whereas; Management Information System (MIS) is used in the Managerial Level. The proposed information system is a managerial level system. MIS improves the efficiency in an organization. It expedites problems solving in an organization and however, MIS assembles, process, store and disseminates information. The proposed system is ONLINE STUDENT TIME TABLE, so MIS is the best information system that will be adopted in completing the system.
2.4 SOFTWARE DEVELOPMENT METHODOLOGY (SDLC)
A methodological review of past literature is an important effort for any academic research (Webster and Watson, 2010). According to Phillips (2010) software methodologies are concerned with the process of creating software. These simply imply that, the methodologies are the techniques, methods or steps that are followed and used in software or system development life cycle (SDLC). Software development life cycle can be defined as the method or process of developing an information system via some important or successful phases or stages of the SDLC. Hence, Peslak, Subramanian, Clayton, (2008) conducted a research on “The phases of ERP software implementation and maintenance” the software development life cycle is mainly based on the new software development. This includes the Planning phase, Analysis phase, design phase, Implementation phase and lastly Maintenance of the system after delivery of the finished product.
However, a single method or methodology cannot be always correct because every single methodology has its own strength and weakness. For example, the strength of waterfall methodology is “developing a reliable, quality system with excellent documentation” whereas prototyping (sample) has the weakness of “quick and dirty method of software development”. Therefore, no single methodology is perfect as software development life cycle is concerned. In a research conducted by Jianga et al. (2010) on “System analysts’ orientations and perceptions of system failure” it is not easy to quantify and select the appropriate methodology for system or software development life cycle. Many companies adapt their own model or methodology, but all have similar pattern. The diagram below will shade more light on the SDLC.

Identify, analyze, prioritize and arrange information system
Study and structure system
Design physical system, design architecture, design interface, interface prototype, de-normalization and database and file specification
Code, testing, install and support the information system
Systematically repair and improve the information system
Planning
Maintenance
Implementation
Design
Analysis
Identify, analyze, prioritize and arrange information system
Study and structure system
Design physical system, design architecture, design interface, interface prototype, de-normalization and database and file specification
Code, testing, install and support the information system
Systematically repair and improve the information system
Planning
Maintenance
Implementation
Design
Analysis

Figure2.1: Software Development Life Cycle
Figure2.1: Software Development Life Cycle (VADHE, 2010)
2.4.1 PLANNING
Planning is the first phase of the SDLC. In this phase, the author will plan the system “Legenda Online Student Time Table System”; know the reason of building the system and understand the reason of building the system. The planning phase the most important phase of the SDLC and focuses on the understanding of “why?” an information system “should be build” and going about building it (Dennis, Haley and Roti, 2008). The planning phase has many steps, which the author will consider: Identify opportunity, Analyze feasibility, Develop work plan, Staff project and Control and direct project. The planning phase also includes the following techniques: Technical feasibility, Economical feasibility, Organizational feasibility, Feasibility study, Gantt chart, pert chart, Scope management, Time boxing and, Risk management.
2.4.2 ANALYSIS
The analysis phase is the second phase of the software development life cycle. In this phase the author will analyze the system (current system). The project team (members) sits and does the analysis of the as-is system (current system), improvement and the to-be system. The main focus of this phase is to know the users of the system? (Actors), what are the functions embedded in the system (use cases)? What is the system capable of doing? Or what the system does? The analysis phase comprises of: requirement analysis techniques which are; business process automation (BPA), business process improvement (BPR) and business process reengineering (BPR). The requirement gathering techniques includes; interview, JAD session, Questionnaire, document analysis and observation respectively.
2.4.3 DESIGN
In this phase, the author will design the system “Legenda Online Student Time Table System” prototype and design database structure. Design is the longest, hardest and most expensive phase of the SDLC. It includes the design of the physical system, design strategy, architecture design, designing of the program and design database and file specification.
2.4.4 IMPLEMENTATION
In this phase, the author will implement the system “Legenda Online Student Time Table System” with suitable programming languages and database applications. This is the final phase of the SDLC. Implementation has to do with the Programming, installation of the finished product after the delivery of system to its final users.
2.4.5 SYSTEM MAINTAINANCE
This is the maintenance, upgrade or repair of the system (Legenda Online Student Timetable System) and improving the system in the future.
2.4.6 WATERFALL METHODOLOGY
Waterfall model is also known as “Traditional model of software development. It is a step-by-step or sequential approach to software development in which the planning phase, analysis, design, implementation and maintenance falls like water fall (rain fall). In this model, each phase must be perfected before moving to another phase, example; planning must be perfected before moving to the analysis, design and lastly implementation. Thus, it is possible to go back from one phase to another though, just imagine yourself moving from a water fall. However, water fall should be adopted or used when “cost and timing is not an issue” and it produces high quality system and proper documentation which is very crucial for the future upgrade of the systems. Most of the faults in the software are detected during the initial phase (Waterfall-Model, 2012). In waterfall development, there are basically two “variants” which includes; Parallel and Viral Model (V-Model). The diagram below shows all the phases of the waterfall model.
SYSTEM
PLANNING
ANALYSIS
DESIGN
IMPLEMENTATION
SYSTEM
PLANNING
ANALYSIS
DESIGN
IMPLEMENTATION

Figure2.2: Waterfall Model
(Dennis, Haley and Roti, 2008)

2.4.7 PARALLEL DEVELOPMENT
Many software projects in their early stages follows a stringent linear development in which each consecutive “subproject” or “version” of the software is derived from an increment of the later “subprojects”. Parallel development is adopted because it delivers system in break downs (that is; subprojects or versions) there by drastically reducing the time of delivering the finished product (system). However Armstrong, Kotler (2008) stated that; “regardless of company size or organization structure, income depends on the release of product, so release must occur”. Obviously, as software packages or products are released in subprojects or increments, the risk associated in building the system will reduce drastically and the income of the development team will be high.

Figure2.3: Parallel Development
Figure2.3: Parallel Development

(Dennis, Haley and Roti, 2008)
2.4.8 VIRAL MODEL (V-MODEL)
Viral model is a variant of waterfall methodology. Viral model focuses on the testing of the general system which includes: Unit testing, System testing, Integration test design and Unit testing and finally acceptance testing. According to Dennis, Haley and Roti (2008) viral model is easy, simple, and straight forward and improves the overall quality of the overall system because it pays more attention to testing. Coley (2012) stated that; “viral model gives itself to the idea of VV” Validation (are we building the right system?) and Verification (are we building the system right?). Below is the diagram of the Viral Model (V-Model).
ANALYSIS
DESIGN
IMPLEMENTAION (coding)
(CODING)
Acceptance test design
System test design
Integration testing plan
Unit test design
Acceptance testing
System testing
Integration testing
Unit testing
ANALYSIS
DESIGN
IMPLEMENTAION (coding)
(CODING)
Acceptance test design
System test design
Integration testing plan
Unit test design
Acceptance testing
System testing
Integration testing
Unit testing

Figure2.4: Viral Model (V-Model)
Figure2.4: Viral Model (V-Model) (Dennis, Haley and Roti, 2008)
2.4.9 ITERATIVE DEVELOPMENT or PHASED DEVELOPMENT
Iterative development is a rapid application (RAD) development that breaks the overall project or system into versions (iterations). The important functions or features are included in the first version of the release. The version (1) of the system is developed quickly by a mini waterfall process and delivered to the uses. Users interact with the prototype and provide corrective feedback that will be included in the subsequent release. The main disadvantage of Iterative Development is that uses willingly accept system that is not completed intentionally. Refer to Larman (2004); Iterative Development is an approach to developing software where by the overall system is released in iterations (that is; sub system). Below is the diagram of iterative development.

Figure2.5: Iterative or Phased Development
Figure2.5: Iterative or Phased Development
((Dennis, Haley and Roti, 2008)
2.4.10 SYSTEM PROTOTYPE
In this model, a quick system prototype (sample) is developed so that uses and all stake holders (uses, project manager, project champion etc.) will sit and analyze the system. If the system is not suitable, the project team will rebuild the system from the phases of planning, analysis, design implementation and lastly, the system prototype. Gary Armstrong, Philip Kotler (2008). Prototyping is an iterative (repeated) reproduction of mini system (with less functions or features) like the real product or system. Below is the diagram of the system prototype.

PLANNING
IMPLEMENTATION
DESIGN
ANALYSIS
SYSTEM PROTOTYPE
IMPLEMENTATION
SYSTEM
PLANNING
IMPLEMENTATION
DESIGN
ANALYSIS
SYSTEM PROTOTYPE
IMPLEMENTATION
SYSTEM

Figure2.6: System Prototype
Figure2.6: System Prototype

(Dennis, Haley and Roti, 2008) 2.4.11 THROWAWAY PROTYPE
Throwaway prototyping has a fairly thorough analysis phase that is used to gather requirements thoroughly and to develop ideas for the system concept. Many of the functions suggested by the users may not be understood when conducting JAD session because most of the users do not know what they want or what they need. Therefore, throwaway prototyping solve this problem by gathering the requirements thoroughly in the analysis phase. If users are not satisfied with the system, the development team will throw the prototype and redesign a new prototype (sample).

Figure2.7: Throwaway Prototype
Figure2.7: Throwaway Prototype

(Dennis, Haley and Roti, 2008)

2.4.12 EXTREME PROGRAMMING
PLANNING
IMPLEMENTATION
DESIGN
ANALYSIS
PLANNING
IMPLEMENTATION
DESIGN
ANALYSIS
The extreme programming emphasizes on customers satisfaction and team work (Dennis, Haley and Roti, 2008). XP is a software development methodology that used to improve quality of software and changing customers need. XP communication, feedback, team work and courage are center value. XP starts with user describing what they want the system to do. Normally XP (Extreme Programming) comprises of few programmers and not more than ten (10).

SYSTEM
SYSTEM

Figure2.8: Extreme Programming
Figure2.8: Extreme Programming (Dennis, Haley and Roti, 2008)

Table2.2: Criteria for selecting Methodology Usefulness inDevelopment System | Waterfall | Parallel | V-model | Iterative | System Prototype | ThrowawayPrototype | Extreme Programming | * With unclear user requirements | * Poor | * Poor | * Poor | * Good | * Poor | * Excellent | * Excellent | * With unclear user interfaces | * Poor | * Poor | * Good | * Poor | * Good | * Excellent | * Poor | * With Unfamiliar Technology | * Poor | * Poor | * Poor | * Good | * Poor | * Excellent | * Poor | * That are Complex | * Good | * Good | * Good | * Good | * Poor | * Excellent | * Poor | * That are reliable | * Good | * Good | * Excellent | * Good | * Excellent | * Good | * Excellent | * With short timeSchedule | * Poor | * Good | * Poor | * Excellent | * Excellent | * Good | * Excellent | * With schedule visibility | * Poor | * Poor | * Poor | * Excellent | * Excellent | * Good | * Good |

2.4.13 JUSTICATION OF SELECTED METHODOLOGY
Waterfall methodology and its variants (v-model, parallel model) are very good for large and expensive system. Waterfall model takes years to deliver system to its users. According to the requirements of the proposed system, the author shall use “Throwaway prototype” because it allows the development team and all the stakeholders to analyze the system and to develop and build a system prototype (sample) that users will evaluate and provide corrective feedback. This will give the users the knowledge as to understand what they want and the system development team to build the right system for them. Most users don’t know what they want (system functions) until they interact with the prototype to gain in-depth understanding of the actual system they require. However, systems can be developed and delivered to its uses in 6 months. For Online Student Time Table System, throwaway prototyping is the best methodology in designing and implementing the system.
2.5 DATABASE SYSTEM
Database is a collection of data and information that is organized in a particular fashion (ascending “A-Z” or descending order “Z-A”), so that, managing and retrieval of information from database will be easier and can be stored in different format e.g. audio, video, pictures and graphics (Searchsqlserver, 2012). A database can be thought of as a set of logically related files organized to facilitate access by one or more applications programs and to minimize data redundancy (Cl500, 2012). Today, most organizations, schools, companies, websites, uses electronic database as a medium of storage and retrieval of their record. With the advent of database, you can easily search many customers’ records within seconds and perform some operations.
However, there are many types of databases in the market today which includes; Relational data model, Hierarchical data model, Network data model and object oriented database model (OODBM) respectively. Alternatively, different types of databases are used in different ways for different functions or requirements. Again, there are many tools (productivity tools) that are used to create database, these includes:- 2.5.1 Microsoft Access. 2.5.2 My SQL Server R2. 2.5.3 XML (extensible markup language)
2.5.1 MICROSOFT ACCESS
Microsoft access is popularly known as Microsoft office, is a file sharing database system (that is; processing takes place at the client side). It uses “jet database engine” created by Microsoft. Microsoft access is a good database that can be used by maximum of 20 users concurrently. Example, standalone system and small websites use MS access for their storage. If many users are to interact with system that is built with MS access database, the system would be remarkably slow because “Microsoft jet is not meant to be used with high stress, high concurrency, 24/7 server application” e.g. web, commerce, messaging server and universities (Teamits, 2002).
Furthermore, the limitations of using access are many that you cannot possibly imagine. In MS access only limited number of concurrent users can access the system but “Microsoft has stated that access is able to support 225 concurrent users”. However, if users exceed 20, the performance and response time will reduce drastically (Sql-Programmers, 2009).
2.5.2 MYSQL SERVER R2
MySQL Server R2 is a relational database model (RDBM). MySQL Server R2 is named after MICHEAL WIDENUIS daughter “MY” and “SQL” stands for Structured Query Language. According to Harper (2009) MySQL Server R2 is popular and open source (i.e. free) and can be easily downloaded on the web; it runs on Linux/Unix platform, windows and Mac OS (operating system) respectively. Interacting with MySQL Server R2 is a bit complicated for novice users or beginners because; it is not built with WYSIWYG (what you see is what you get i.e. interface design). Most web programmers prefer to use MySQL Server R2 because it supports thousands of users without affecting the speed and performance of the system unlike Microsoft access. Using MySQL Server R2 you can easily access thousands of record and manipulate them as you wish or like. For example, most web programmers use it on the server site. It loads SQL queries fasters and reliable as well. MySQL can easily run with phpMyAdmin, for windows example WAMP SERVER, XAMPP SERVER, and APPSERVER. MySQL also gives powerful transaction because of its public acceptance globally. Most importantly, it is an open source (free) unlike Microsoft access.
However, the limitations of using access include; the maximum number of tables that can be referenced in s single join is “61”. There is also a limitation of 264 (1.8 * 1019) row in MYISAM table. The maximum number of columns per index is “16”. Again, MySQL Server R2 does not support customized (custom) data types. Last but not the least; MySQL Server R2 doesn’t support XML (extensible markup language) at the same time, it is the fastest database system. The maximum number of partitions for a given table is 1024.
2.5.3 XML
XML stands for Extensible Markup Language. It is simple and flexible to interact with. Xml was initially developed under the “auspices of the w3 consortium in 1996 by Jon Bosak chaired by chief computer engineer of sun Microsystems”. It is a hierarchical data model (for its format of storage). According to Hoffman, Watson and Watanabe (2009) most organizations use xml database for its flexibility to easily generate report (e.g. school, budget etc.). If you are a novice or beginner to xml, you will think that it is same as html (hypertext markup language) but it’s not. Thus, xml uses exact or same tag like the html e.g. <h1>. Xml is design to carry out data (W3school, 2012).
Furthermore, the limitations of xml are predefine i.e. (you must define your own tags). According to Diamond (2012), xml database runs slower compared to MySQL. Xml searches are slow because it has slow query and search functions. However, xml is widely accepted by people. Again, the data most be all be loaded before it can be viewed. Last but not the least, the major disadvantage of using xml is security, a registered user has can be able to view, edit, add, and delete all of the information in a container. Xml requires too many words to create tables. Below is the comparison between the three popular databases; Microsoft access, Xml and MySQL.

Table2.3: Comparison between MS access, Xml and MySQL database Microsoft Access | XML | MySQL SERVER R2 | * Maximum number of 20 concurrent users | * Supports thousands of users concurrently | * Supports thousands of users concurrently | * Jet engine cannot handle sophisticated users and stress | * Xml is mainly designed for the creation of free document | * Is design for creation of sophisticated databases | * Slow response time because of the limitations of the jet database engine | * Slow response time because all the record most be loaded before you can view the tables or record | * High response time, flexible and high performance in the server site | * It follows network data model | * It follows hierarchical data model | * It follows relational data model | * It is not an open source | * It is open source | * It is an open source | * It has less features and limited functionalities | * It has much functionalities and features | * It has much functionalities and features | * It is hard to use for novice programmers | * It is hard to use for novice programmers | * It is very easy and simple to interact with. It can also be used by other databases like Xampp server, Apps server and Wamp server correspondingly. |

2.5.4 JUSTIFCATION OF DATABASE TO BE USED
According to the above explanation and the comparison in table 2.0, the author recommends MySQL database to be used in build the database structure and the database of the proposed system because, MySQL runs on different platforms e.g. Windows and Linux operating system. However, it is fast and gives high performance to uses. Searching in MySQL database is easy because you can view record instantly.
Moreover, MySQL follows relational database model, since record can be easily related with the aid of PRIMARY KEY (PK, unique key in a table e.g. IC Number) FOREIGN KEY (FK is a primary key in another table and non-key in other table). It also works best in maintaining and managing sophisticated databases. Therefore, The Author will use MySQL in creating and building the proposed system.
2.6 PROGRAMMING LANGUAGE
Literally, a program is a piece of code and proper documentation that tells the computer system (commands) what to do and what not to do. It can be written in high level language (programming language) that a computer system understands. In this part, the author will discuss on some of the programming languages PHP (Hypertext preprocessor) and ASP.Net (Active Server Page), compare them and justify the suitable programming language for the proposed system.
2.6.1 PHP
PHP stands for hypertext preprocessor. It was created by Lerdorf in 1995 (Lerdorf, 2012). Php was originally derived from “personal home page tools” which is known now as “Php” (Searchenterpriselinux, 2012). According to Bradley (2012), Php is a scripting language which can be used with HTML (Hypertext Markup Language) to add some functions or features that html cannot perform alone. Since Php is a “server site scripting language” it is worldly accepted by programmers for its simplicity and easiness to edit and program. Most programmer prefer to use Php because it translates the scripts so that the compiler understand and can be connected to database to retrieve, add or update some of the content of the database. A Php page must be saved as “.Php” extension which also contains the opening (<? Php) and the closing tag are (?>). Php can be run on various platforms like Windows, and Linux. Php is the fastest compared to other languages and it gives high performance. Lastly, Php is an open source (free). Refer to Raj (2012), Php supports structural programming and object oriented programming.
2.6.2 ASP.NET
ASP.Net stands for Active Server Page. It was developed by Microsoft. ASP.Net was released with the “.Net framework 1.0” to the latest release of “.Net3.5 and .Net4.0 framework”. Despite the fact that ASP.Net is used to build sophisticated and dynamic websites, it is used because of its simplicity and easiness to program and write. ASP.Net has an inbuilt html tag and it follows the common language runtime (CLR), giving programmers the awareness that the can write ASP.Net using any programming language that supports .Net language. ASP.Net limits the number of code required to build large application. Thus, it is an event driven server site programming type or model. Unlike Php validation in ASP.Net is inbuilt in the sense; you can validate your forms without writing a single piece of code.

Table2.4: Comparison between ASP.Net and Php programming language FEATURES | ASP.NET | PHP | * Runtime | * Executes programs slower compared to Php because it makes use of memory space while executing the program. | * Executes faster because it uses the inbuilt memory space while executing. | * Compatibility | * ASP.Net runs on windows and Linux platform, but only runs on Microsoft servers. | * Php can run on windows and Linux platform. It is compatible with all servers e.g. app server, WampServer and XamppServer. | * Security | * It is more secured because of the complex security features or functions. | * Php is less secured than Asp.Net. | * Cost | * It a Microsoft product. So it is not free and you must buy it if you want to use it. | * It is an open source (Free) and can be easily downloaded and used. | * Simplicity | * It is complicated and hard to understand and use. | * It is simple and easy to understand and use. |

2.6.3 JUSTIFICATION OF PROGRAMMING LANGUAGE
The author prefers Hypertext Preprocessor (PHP), it is a free cross-platform and server-side html embedded scripting language that is used for creating dynamic web pages. Despite its limitations compared to ASP.Net in terms of security, it is free programming software that you can download online. The author chooses PHP because of its coding simplicity compared to ASP.Net. Above all, PHP is a multi-platform and can be run on Windows and Linux platform respectively.
2.7 INTERFACE DESIGN
Design of interface is a crucial and most significant in all software development life cycle. Just imagine using a system with a poor interface design. Any system with a poor interface design is of no value to the non IT (information technology) field. In software engineering, user interface must be design by following the KISS (keep it simple and straight forward) principles. Thus, most the system are developed for users from non-IT field, so design must be simple and all of JAKOB NEILSON’S rules must be followed to achieve a good usability engineering (suitable use interface, navigations, good colors etc.). There are many design tools in the market today, but for this research work. Only Macromedia Dreamweaver and front page will be compared to choose the most suitable design tool for developing the proposed system (LEGENDA ONLINE STUDENT TIMETABLE SYSTEM).
2.7.1 MICROMEDIA DREAMWEAVER
Macromedia Dreamweaver is a tool that many web developers and web designers use to develop sophisticated websites, and due to the fact that Dreamweaver provides visual designing of systems (websites) and the code can be easily edited. According to Sawyer (2010), Dreamweaver provides quick websites creation (design) and provides tools to manage design and provide to maintain websites. Most of the programmer and web developers prefer to use Dreamweaver because of its explicit feature that allows developers to constantly alter design due to customer’s requirements and ability to deliver system in the stipulated period of time.
However, the limitations of Dreamweaver are that, it does not edit or correct mistakes (in code) though; it highlights that very part of code that is not correct. One of the major limitation of Dreamweaver is the table sorting. According to Negrino, Smith (2008) Dreamweaver is not able to merge cell or sort some part of a table. However, sorting algorithm in Dreamweaver is done with numeric in a table. Dreamweaver will be able to sort rows only in a table. 2.7.2 NETBEANS
Netbeans started as a student project (originally called xelfi) in Czechoslovakia republic in 1996 (Netbeans, 2012). The goal of the project was to write a Delphi-like Java IDE (Integrated Development Environment). More so, Netbeans is a sophisticated integrated development environment that aims to help developers build any type of application. It was acquired by “sun Microsystems” and became an open source project (Leahy, 2012). Netbeans issues a modular IDE that supports Java, php, C++ and many others respectively (Techopedia, 2012).
However, Netbeans provides users with GUI. It also develops readymade windows forms for all the required buttons, labels, textboxes etc. database integration that Netbeans packs by providing a CRUD (Create, Read, Update and Delete) application shell (Bhat, 2012). It is easy to design using swing GUI using Netbeans IDE and pre-define update center and automatic update notification. It is very useful for programmers because it a modular application (i.e. to say, can support Java, php, C++, Html etc).
2.7.3 FRONT PAGE
Front page is a software design tool that programmers and web developers use to build to build sophisticated websites. The main advantages of front page are server side that is simple. Front page design and animation are built with the html (hypertext markup language) Hutchison (2008). Front page follows what you see is what you get (WYSIWYG) and code is inserted into hypertext markup language. One of the front page features is that you don’t need to learn HTML before creating your website, though; it is easy to create websites with Front page than Dreamweaver. A virtual directory can also be created in front page. The limitations of front page includes website web size disk usage and time out when publishing large pictures or have lots of pages in a sophisticated website is uploaded on the internet, it will be explicitly slow might show “HTML error or server has time out”.
Table2.5: Comparison between Micromedia Dreamweaver and Front Page SOFTWARE | STRENGTH | WEAKNESS | * Microsoft Front Page | * it is appropriate for text-heavy sites | * Lacks fusions pixel-level | | * it follows WYSIWYG (what you see is what you see) editors | * Have less powerful java scripts. | | * Mostly for novice (beginners) web developers | | * Micromedia Dreamweaver | * It is embedded with “round-trip HTML” editing | * Has less powerful power management feature * Not suitable for novice web developers | | * It is an extraordinary flexible site building package | * The interface is “cluttered” that is; separate windows with different functions. | | * Provide best support of JavaScript effects | | | * It is for expert users | | | * Good for creating rich graphics without much knowledge on the html tags or coding | | | * Mostly compatible with server site scripting languages (e.g. PHP hypertext pre-processor) | | * Netbeans | * It is for expert users or programmers | * It cannot be easily used by novice users. | | * It has database integration package for easy update, create, read and delete function. | * It is hard to interact with for its command line interface (CLI). | | * It increases programming skills | * No GUI due to its lack of interface (i.e. to say GUI design). | | * It’s an open source (i.e. free to download and use). | | | * It supports many programming language e.g. Java, pearl, php and etc. | | | * It also supports server site scripting language (e.g. php). | | | * It also supports many database application e.g. Microsoft access, Mysql server, Xampp server, Appserver, and WampServer respectively. | |
2.7.4 JUSTIFICATION
From the above comparison, the author will use Netbeans to design and implement the proposed system (Legenda Online Student Timetable System). Netbeans supports sophisticated web sites and many high level programming languages, it is also embedded with many feature of rich design and it is very flexible. Netbeans is compatible with server site scripting language (i.e. can be easily connected to database using the server site scripts to connect web pages and databases). Therefore, Netbeans is the best tool for designing the interface of the proposed system.
2.8 FACT FINDING TECHNIQUE
Fact Finding technique is the formal way of using research, interview, JAD sessions, observation, questionnaires and other requirement gathering techniques to gather important information about the as-is system (current) and used for the proposed system (future system), requirements and functions. Fact finding technique is also called information gathering technique.
2.8.1 REQUIREMENT
A requirement is simply a statement of what the system should do and the characteristics it must have. A requirement focuses mainly on the user requirements. According to Harwell (2001) all project started with a requirement definition or statement. Therefore, the proposed system, business requirement, how to build the system? System requirement (user requirements) shall be discussed in chapter 3. A requirement must be either functional or non-functional requirement. The functional requirements are the Login, register, add student, delete student etc. and the non-functional requirements are the requirements that affects the system as a whole e.g. security, usability, reliability, re-usability, operationability, simplicity, understandability etc. 2.8.2 REQUIREMENT GATHERING TECHNIQUE
Requirement gathering technique is an important technique that must be used in order to understand the future system (that is; user requirement and system requirement). The requirement gathering technique includes; interview, questionnaire, document analysis, observation and JAD (Joint Application Development) session. However, gathering information can be difficult for most system analyst because you must plan ahead of time to conduct any of the technique in gathering requirement. According to Wiegers (2009), lack of user input, incomplete requirement is the reasons why information system (IS) projects failed (in terms of budget, time and system delivery time).
2.8.2.1 INTERVIEW
According to Dennis, Haley and Roti (2008) interview is among the common requirement gathering technique that people used to gather rich information. It is obvious that, if you need information from someone, logically, you will need to ask them. Fontana, Prokos (2007) also stated that; interview is used in daily life (e.g. job interview) to acquire information from the interviewees. Interview is supposed to be one on one that is; face to face. Nonetheless, interview comprises of; conduction interview, selecting interviewees, organizing the interview questions, preparing the interview questions and lastly conducting the post interview follow up.
2.8.2.2 JAD SESSION
Joint Application Development (JAD) is a requirement gathering technique that allows users (all stake holders) to sit together and identify the entire important system requirement (functional requirement). International Business Machine (IBM) developed the JAD in 1970’s. Langer (2007) also stated that, Joint Application Development (JAD) is a way of conducting group work with all the stake holders and development team (in a U-Shape sitting) and listing out all the system requirement or functions. For a JAD session to be successful, all stake holders and development team must be committed to conducting the JAD session.
2.8.2.3 QUESTIONAIRE
A questionnaire is another requirement gathering technique (RGT) that is mainly used to get useful information from users. Normally, questionnaires are written and printed on paper or in an online system that users will fill up the form and give out there opinions and feedback. Questionnaire includes open ended questions and close ended questions. Refer to Brace (2008); most of the questionnaires used are open-ended questions. Open ended questions are; what are the problems faced with Linton University College students? While close ended questions are; how do students interact with lecturers in the class?
2.8.2.4 DOCUMENT ANALYSIS Document analysis is a technique that allows the project team to understand the current system (i.e. the as is system). Unfortunately, many systems that are developed using the Rapid Application Development method are poorly documented. Documentation must be produced throughout the development process (all the development phases should be documented properly) so that the analysis of the as-is system (current system) can be done in correct manner without failure.
2.8.2.5 OBSERVATION
Observation is a powerful tool that many authors suggested that it is the best requirement gathering technique. When observing something, you will see exactly what is going on the current system (as-is system) rather than collecting user view or opinion by either interviews or questionnaires. Pawar, Pawar (2004) said that; the strength of observation method is use to overcome the limitations and weakness of the other type of the requirement gathering technique e.g. questionnaire, document analysis, interview and JAD session respectively. Aparasu (2010) conducted a research on method of pharmaceutical practice and policy said the observer should remain hidden and observe what the other people are doing using technology means (video, audio etc.) to know exactly what the people are doing without distracting them.

Table2.6: Comparison of requirement gathering techniques FEATURES | INTERVIEW | JAD | QUESTIONNAIRE | DOCUMENT ANALYSIS | OBSERVATION | * Types of information | * As, improvement | * As, improvements | * As, improvements | * As-is | * As-is | * Depth of information | * High | * High | * Medium | * Low | * Low | * Breadth of information | * Low | * Medium | * High | * High | * Low | * Integration of information | * Low | * High | * Low | * Low | * Low | * User involvement | * Medium | * High | * Low | * Low | * Low | * Cost | * Medium | * Low-Medium | * Low | * Low | * Low-Medium |
2.8.2.6 JUSTIFICATION OF REQUIREMENT GATHERING TECHNIQUES
From the above comparison in Table 5.0, questionnaire is seen to provide high information and has less cost unlike the observation or the interview. Therefore the author shall use QUESTIONNAIRE and INTERVIEW to gather requirement of the as is system before moving to the improvement and then to the to-be system (future system). Using questionnaire, information can be easily collected form users (unlike JAD) and that’s why most system analyst prefer to use Questionnaire and Interview for their requirement gathering technique.

2.9 REQUIREMENT ANALYSIS TECHNIQUES
The requirement analysis technique is basically conducted to understand the as-is system (i.e. current system), improving the current system and writing requirements (functional and non-functional requirement) for the to-be system (proposed system). The requirement analysis technique includes; business process automation (BPA), business process improvement (BPI) and business process reengineering (BPR), which is discussed below:-
2.9.1 BUSINESS PROCESS AUTOMATION
Business process automation (BPA) is a requirement analysis technique that is used to know the business requirements in the system and using information technology in some major functions of the business leaving the other part of the business unchanged (i.e. using the local method). There are basically two types of business process automation which includes the following. According to Mohapatra (2009), business process automation (BPA) has help in increasing the efficiency (do the right thing) and the product quality of many organizations and industries in recent years.
2.9.2 BUSINESS PROCESS REENGINEERING
The business process reengineering (BPR) is a process in which organization completely alters the way it operates and using information technology to build system. Much time is spent in understanding the current system (as-is system) because, BPR makes use of new ideas, technology and ways of doing business. BPR has three major techniques; Outcome analysis, Technology analysis and Activity elimination.
2.9.3 BUSINESS PROCESS INPROVEMENT Business Process Automation (BPI) is the way of leaving the way in which organizations operates unchanged and exploring or copy what other companies (competitors) are doing. This analysis technique improves both efficiency (“do the things right”) and effectiveness (“doing things right) for an organization. BPI focuses on improving the overall business. Therefore, more time is allocated to the as-is system (current system). The three popular BPI techniques are; ABC (Activity Based Costing), Informal Benchmarking and Duration Analysis.
Table2.7: Comparison between BPA, BPI and BPR FEATURES | Business Process Automation(BPA) | Business Process Improvement(BPI) | Business Process Reengineering(BPR) | * Potential business value | * Low-moderate | * Moderate | * High | * Project cost | * Low | * Low/Moderate | * High | * Breadth of analysis | * Low | * Moderate | * Broad | * Risk | * Low | * Low/Moderate | * Very high |
2.9.4 JUSTIFICATION OF SELECTED ANALYSIS TECHNIQUE
According to the comparison of the requirements analysis technique in Table 6.0, the author recommends or shall use Business Process Automation (BPA) because the potential business value is low, project cost is low, breadth of analysis is low and the risk involved in the analysis of the as-is system, improvement and the requirements of the proposed to be system is low as well. Thus, BPA is good economically and gives best information when building a system. BPA shall be used in the proposed system.
2.10 NETWORK ARCHITECTURE
Network architecture refers to the design and the structure of a computer network making it possible for different computing devices to communicate. A client is applications that request service from sever. A server is a computer program that serves and provides information to clients. The network architecture includes; N-Tier architecture, One-Tier architecture, Two-Tier architecture and the Three-Tier architecture. The author will talk about only Two-tier and Three-tier architecture.

2.10.1 TWO-TIER ARCHITECTURE
Two-tier architecture is known as client/server architecture. If a request (performing a task) is sent to the server, the server will perform the task. Two-tier application provides an improved flexibility, usability and scalability of applications. Client/server architecture must separate the layers into client and server. Generally, two-tier architecture is designed for stand-alone system only (Example Visual Basic 6.0). Two-tier architecture supports only few users (restricted to certain number). Below is a diagrammatical presentation of the two-tier architecture.
2.10.2 THREE-TIER ARCHITECTURE
Three-tier architecture is popularly known as multi-tier architecture. It consists of 3 tiers that have its own functionalities each. It comprises of data server (business server/client) presentation logic and middle tier server (business rule). Some of the advantages of using 3-tier includes; easy modification and replacement of single tiers without affecting the other tiers. Application can easily be separated (i.e. separating applications and database) there by making it possible for many users to have access concurrently. It is mainly developed to overcome the weakness of two-tier architecture in terms of security, performance, scalability and simplicity. Three-tier architecture is used mainly for web based applications e.g. face book, yahoo etc.
Table2.8: Comparison between two-tier and three-tier architecture FEATURES | TWO-TIER | THREE-TIER | * Simplicity | * It has easy structure, setup and simple to maintain and use. | * More complex structure, setup and maintenance. | * Performance | * Performance reduces as the number of concurrent users exceeds one hundred (100). | * Higher performance due to the fact that it supports thousands of concurrent users. | * Portability | * It is not portable to other servers because it is stand-alone (client and server). | * It is portable to other database servers and platforms. | * Security | * Web servers communicate with database servers directly. Thus, leaving it vulnerable for attacks. | * Security is high because uses can restrict or communication from your web server to only the application server. | * Maintainability | * It is easier to maintain. | * It is mainly designed to tackle the weakness of two-tier architecture. | * Support | * It is mainly for stand-alone system. | * It is mainly for web based applications. |
2.10.3 JUSTIFACTION OF SELECTED TIER ARCHITECTURE
In accordance with the comparison of the two-tier and three tier architecture in the above table, the author shall use three –tier architecture to build the proposed system. Performance, support, security is high in three-tier architecture. Therefore, three-tier is the best network architecture for the proposed system (i.e. Legenda Online Student Timetable System).
2.11 MODELING TOOLS
Modeling tools are the tools that are used for the main design of the proposed information system. Modeling tools like Rational Rose Enterprise Edition and Microsoft Visio will be used to create the use cases, class diagrams, sequence diagrams, activity diagrams, collaboration diagram and activity diagrams concurrently. Rational Rose Enterprise Edition and Microsoft Visio will be discussed be the author below:-
2.11.1 RATIONAL ROSE ENTERPRISE EDITION
Rational rose is a commercial software tools that is used in software engineering and computer science in general. Rational rose comprises of two elements in modern software engineering. The modern software engineering includes; component based development and controlled iterative development. It is also easy to install and interact with (Uimonen 2000). Again, Charvat (2002) states that; Rational Rose facilitates object oriented analysis and design. It also makes it easier for engineers and system analyst to manipulate and modify elements in UML (Unified Modeling Language). The most popular features of rational rose enterprise edition are its ability to provide iterative development and round-trip engineering (Searchcio, 2012). Rational rose is good modeling tools in software development.
2.11.2 MICROSOFT VISIO
According to English 2012, Microsoft Visio is a popular modeling tool that is used to create business layouts and blue prints. Thus, Microsoft 2010 includes advanced template called “Microsoft share point work flow”. Microsoft Visio is a diagramming tool that is used to create software models, layouts and blue prints (i.e. in terms of technical and non-technical skills). Using Microsoft Visio, use cases, class diagram (UML) mainly for developing and building information system. The below table will show the differences and comparison of Microsoft Visio and Rational Rose Enterprise Edition.
Table2.9: Comparison between Rational rose and Microsoft Visio FEATURES | RATIONAL ROSE | MICROSOFT VISIO | * USABILITY | * Rational rose is more simple because it follows object oriented analysis and design. It also have nice Logical view of models or diagrams | * Microsoft Visio is easy to use. It also follows Object oriented analysis and design but, its usability is not very user friendly | * SUPPORT | * It is good for large and complex systems | * It is good for systems plans and layout | * COST | * Cost is high because it is not a free ware | * Cost is high because it is not a free ware | * SUPPORT LIMITATIONS | * It can be used to create all the UML models | * It can be used to create some of the UML models | * SPEED (load time) | * Load time is slow because it is a complex software | * Load time is faster compared to rational rose | * SIMPLICITY | * It is simple and easy to understand | * It is less simple and a bit complicated to interact with | * GUI | * It has very nice user interface | * The interface is not very user friendly like that of rational rose enterprise edition | * UNDERSTANDABILITY | * It is simple to use and understand | * It not easy to use and not simple to understand |

2.11.3 JUSTIFACTION OF MODELING TOOL TO BE USED
This justification is based on the research and comparison in table 9. The author strongly suggests using Rational Rose enterprise edition because, it supports all the modeling tools (e.g. class diagram, use case diagram, activity diagram, deployment diagram, collaboration diagram and sequence diagram). It also provides users with good user interface compared to Microsoft Visio. Microsoft Visio is mostly used to create layout, plan and blue prints. Though, it does not support all of the UML (unified modeling language) models or diagram. Thus, it is also a good modeling tool. Therefore, the author will use Rational rose enterprise edition to model the proposed system “Legenda Online Student Time Table System”.
2.12 BENEFITS OF LEGENDA ONLINE STUDENT TIME TABLE SYSTEM
If the proposed system “Legenda online student time table system” is implemented successfully, the following benefits could be achieved:
2.12.1 Organization
One of the major advantage or benefit of the proposed system is its ability to organize the student lectures and tackle the issues of improper organizing of lectures. That is; the clashing of the timing schedule will be addressed easily.
2.12.2 Student Sectioning It is necessary to divide or split the number of students into sections or group (Group1 and Group 2 correspondingly) if the number of students exceeds or reach a certain point.
2.12.3 Simplicity
The proposed system will be very simple to interact with because of the simple procedures or steps in login, generating of time table, registering users and lastly printing or sending time table to email address.
2.12.4 Swift Access
The speed of interacting and downloading of time table is at its peak. That is; it is very fast to interact with some functions and do some work.
2.12.5 User friendly
The design and structure of the system will be very simple (following the KISS (keep it simple and straight forward method). The usability engineering will be provided by following JAKOB NEILSON’S rules.

2.13 EXISTING SYSTEM
The existing system in LEGENDA EDUCATION GROUP is a manual system and work is done manually (i.e. on paper). 65% of work is done manually and 25% of work is done using some productivity tool like Microsoft access, Microsoft excel, Microsoft Visio, Rational rose enterprise edition, Microsoft word and other types productivity tools respectively. The time table is handled by the coordinator BUSINESS INFORMATION SYSTEM and the coordinator of SOFTWARE ENGEINEERING of Legenda Education Group, so that clashing of venues or assigning a lecturer to different department’s faults will be limited to certain percentage without changing the student time table daily or weekly. In as much as the errors that happen in the system, Legenda information technology department did not trust the system completely due to the problems and limitations that are associated with the manual system. In Legenda education group, Timetable is generated on daily basis due to errors, lack of comprehensive and standard time table software system.
2.14 RELETED SYSTEMS
The below system (stand alone and web based) are system that are related to the proposed system, that is; LEGANDA ONLINE STUDENT TIME TABLE SYSTEM that will be compared below with the aid of a suitable table.
2.14.1 MIMOSA SOFTWARE
MIMOSA is an al purpose application with a wide range of users from all school types and universities. MIMOSA University or School time table can be used for co-coordinating four elements that is; Student, Teachers, Rooms and times (period) (Mimosasoftware, 2012). Mimosa systems can be easily used for many purposes like Conferences, Organizations, Business and TV stations.
However, Mimosa’s primary goal is providing solutions to the clashing of lecture-venue allocation and students sectioning (Grouping). Mimosa software has functions or features compared to Legenda education group manual system (i.e. paper based system). Using Mimosa Software, users (students) can print as many time tables as they want without error and report can be easily generated so that the administrator can view how the system is helping his students and their department in general (mainly, using Spread shit and charts) either showing the growing up of the organization using the software or the draw backs of the organization. Mimosa Software can be used to create Class-Teaching time table, Course timetable, student grouping (sectioning) and assigning of class rooms to students e.g. BKA1/1 (Database).
Mimosa Software comprises of simple design (simple user interface), easier to move data to numerous applications by the aid of text file conversion tools. Thus, many schools or universities prefer to use Mimosa Software time table generating software because of its diverse features (functions) and simple user interface. Below is Mimosa Software graphical user interface (GUI).
Figure 2. [ 9 ]: Mimosa Software Graphical User Interface (GUI)
Figure 2. [ 9 ]: Mimosa Software Graphical User Interface (GUI)
(URL: http://www.mimosasoftware.com/mimosa.html)
2.14.2 VICTORIA UNIVERSITY MELBOURNE, AUSTRALIA
Victoria University Melbourne “is a multi-sector institution” higher education that provides many services that includes teaching, training, research and scholarships (VU, 2012). Victoria University has their own time tabling system that students can either view and download or send it to their various email address (i.e. after login to the system).
The university’s time table comprises of many departments, each department with its own personal. The system provides online access to the student time table. It is mainly used by higher education students and vocational students. One of the important features (functions) of Victoria’s time table is that, you can browse for available time slots, specify your preferences and to create error-free (clash free) time table no matter how many times students change their preferences on the lecture time and venue. Victoria University Melbourne, Australia can be accessed globally (i.e. it’s a web base application. Below is the graphical user interface of Victoria University.

Figure2.10: Graphical User Interface of Victoria University Time Table System
Figure2.10: Graphical User Interface of Victoria University Time Table System

Figur(URL:http://www.google.com.my/imgres?q=victoria+university+melbourne+%2B+time+table+sample&um=1&hl=en&biw=1280&bih=699&tbm=isch&tbnid=IE9wRyA_CHp5TM:&imgrefurl=http://www.monash.edu.au/lls/llonline/download-tab.php%3Ftutorial%3Dquickrefs&docid=j3HEWVH0-lzhgM&imgurl=http://www.monash.edu.au/lls/llonline/assets/images/qrefs/qref02-image1.gif&w=614&h=407&ei=NflbT9qwGIirrAemqKGmDA&zoom=1)

2.14.3 COMPARISON BETWEEN OF RELATED SYSTEMS
The table below shows the comparison of related system and two of the above listed system (Mimosa Software and Victoria University Melbourne, Australia).
Table2.10: Comparison between related systems FEATURES | EXISTING SYSTEM | MIMOSA SOFTWARE | VICTORIA UNIVERSITY MELBOURNE, AUSTRALIA | PROPOSED SYSTEM | * System Type | * It is a manual system that cannot be accessed online | * It is a Standalone system that cannot be accessed online | * It is an Online system that can be accessed online | * The proposed system is intended to be an online information system where students can view and interact with the time table system | * Mode Of Operation | * The manual system is operated for a specific period of time by Legenda education group staff that is; 8am-5pm to be specific | * It can be operated within certain range of computer system (e.g. 10 computers) can be accessing the application at the same time without affecting the performance of the system | * It can be operated online and students can interact with the system 24/7, because it is a web based application | * The proposed system would be operated 24/7 as well, so as to increase students and administrators satisfaction | * Simplicity | * The manual system is rough to interact with because it is a paper based way of operation | * It provides simple database system (Microsoft access) which is limited to certain number of students | * It has simple design structure and also has a simple user interface for easy interaction | * The proposed system would be very simple, interface design and excellent navigation to guide the users on what they are doing and doing it right | * Security | * It has no security and records can be misplaced easily | * It provides simple database system which is limited to certain number of students | * It has a good security feature as it is designed basically to allow users to login to the system before accessing the system | * The proposed system would have enhanced security features and will allow users and administrators to login to the system. however, there are constraints on how users access records | * GUI Design | * It has no user interface because it is a manual system | * It has a good user interface | * It has a good user interface | * The proposed system would have an excellent user interface because it would be built by following the KISS principles (Keep It Simple And Straight Forward) | * Accessibility | * Accessibility of records usually takes long periods of time as a result consuming the time which is required for the administrators, lecturers and students | * This system provides search engine features and quick links to provide easy and quick access to specific information | * This system provides search engine features and quick links to provide easy and quick access to specific information, but the search speed is limited | * The proposed system provides search engine features and quick links to provide easy and quick access to specific information. Thus, the search speed would be very fast |

2.15 SUMMARY
In this chapter (chapter 2), the author concentrates and emphasizes more on literature review there by, generally criticizing the software or system development life cycle (SDLC), Requirement Gathering techniques (RGT) and the requirement analysis Techniques (RAT), database and the programming language that will be used to build the system. Software development life cycle comprises of technique, methods and stages that are involved in information system development (Searchsoftwarequality, 2012). Some of the SDLC techniques include; waterfall and its variants (viral model and parallel model), incremental model, rapid application development (RAD), prototyping, throwaway prototyping, and extreme prototyping (XP) respectively. The requirement gathering techniques include; questionnaire, observation, document analysis, interview and RAD (Rapid Application Development) concurrently. The requirement analysis technique includes business process automation (BPA), business process improvement (BPI) and business process reengineering (BPR). However, in the next coming chapter (chapter 3), all the selected requirements gathering technique, problems statements and their proposed solutions, chosen the fact finding technique, conducting interview and questionnaire, chosen software development methodology technique will be discussed in details in the coming chapter.
CHAPTER 3
METHODOLOGY
3.1 INTRODUCTION
In this chapter, the author will explore about research methodology, requirement gathering technique (to understand the as-is system) and the requirement analysis technique. Fact finding technique; the selected qualitative analysis (questionnaires) and quantitative analysis will be elaborated in details. Software development life cycle (SDLC) will be discussed and how the SDLC phases are applied in building the proposed system in this chapter as well.
3.2 PROBLEM STATEMENT
To analyze and develop “Legenda online student time table system” that will unravel the difficulties and problems in assigning proper time table to students, late collection of time table and clashing of lecture venues due to the fault associated with the paper based system. The problems or issues include the following:-
Late Collection of Timetable
PROBLEM STATEMENTS
Manual System
Difficulty in Timetable Retrieval
Clashing Lecture Venue
Late Collection of Timetable
PROBLEM STATEMENTS
Manual System
Difficulty in Timetable Retrieval
Clashing Lecture Venue

Figure3.1: Ishikawa Diagram
Figure3.1: Ishikawa Diagram

3.2.1 MANUAL SYSTEM
The current system is a manual system. Time table for students is generated manually (i.e. paper based), which is tedious, complicated and time consuming. Thus, much time is needed to creating a simple time table for students. Due to the above issues, time tables are given to student couple (many) of time because of the inconsistency of the “As-Is System”.
3.2.2 LATE COLLECTION OF TIME TABLE
The paper based system of generating student time table is not reliable. It will take weeks to schedule the semester time table for students, thereby making it hard for the school management (administrator, staffs etc) to complete the entire syllabus on the stipulated time. This way, the school will be left behind and the students would not perform well in that semester.
3.2.3 DIFFICULTY IN TIME TABLE RETRIEVAL
In the current system, students will wait in the queue for very long time in order to collect their lecture time table. Assuming that the school has more than 200 students, how much time is required to collect time table? Using such system is time consuming to the students.
3.2.4 CLASHING LECTURE VENUE
The current system is in-consistent because students collect time table at their perspective schools without critically inspecting and confirming that the timing schedules are right. Therefore, makes it trickier for students and lecturers to apprehend the clashing of students lecture venues.

3.3 SOLUTIONS TO THE PROBLEMS
The solution to the problems or issues of the proposed system includes; manual system, late collection of time table, proper lecture-venue allocation, clashing of venue and easy time table retrieval.
3.3.1 MANUAL SYSTEM
Using paper based system in the 21st century is not always a good option; the proposed system (online student time table system) will drastically reduce the difficulties associated with the current system (i.e. traditional system).
3.3.2 LATE COLLECTION OF TIME TABLE
The proposed system will help address the issues of late collection of student time table by providing student with complete, error free and reliable lecture time table at the first week of resumption.
3.3.3 CLASHING LECTURE VENUE
The proposed system will solve the difficulties of providing students with accurate lecture venue. Thus, providing correct and dependable venues to enhance and make the classes motivating to student.
3.3.4 EASY RETRIEVAL OF TIME TABLE
The online student time table system make it easy and simple for students to either print, save or send their time tables to their personal email address instantly.

3.4 RESEARCH METHOD

Awareness of problems

Developments

Awareness of problems

Developments

KNOWLEDGE FLOWS PROCESS STEPS OUTPUTS
Performance Measures
Performance Measures
Artifact
Artifact
Proposal
Tentative Design
Proposal
Tentative Design
Conclusion
Conclusion
Evaluation
Evaluation

Suggestions
Suggestions

Circumscription
Circumscription

Operation and Goal Knowledge
Operation and Goal Knowledge

Results
Results

Figure3.2: General Research Methodology
Figure3.2: General Research Methodology

3.4.1 AWARENESS OF PROBLEMS
The fundamental in methodology is to know and understand the objectives, scope and problems of “Legenda online student time table system” Many systems analysts also quite give less attention to see the awareness of problems and understanding the concept of awareness of problems in software engineering (development). Requirements are the root of any successful software project. The author will be aware of the problems associated with Legenda Online Student Time table system, In terms of security, ethical issues, design and privacy. The problems are to be known because, of the requirement gathering technique (interviews and questionnaires) that will be conducted in this chapter. The analysis of the system as-is system (current system), identify the problems and propose solutions for the to-be system. The author is partially aware of the problems or issues in the current manual system. Thus, the proposed system will add more business values and business needs to LEGENDA EDUCATION GROUP and Information technology to be precise. The design and research sometimes called “improvement research” and how the author will emphasize on problem solving in the to-be system (proposed system).
3.4.2 SUGGESTION
The suggestion phase follows immediately after the awareness of problems with the dotted lines around the proposal and tentative design (Zeyad, Mohammad and Al-Zoubi, 2011). Suggestions is an important step in this research methodology because, new functions (of Legenda Online Student Time Table System) evolve in the tentative design of the proposed system. Suggestions are made after the awareness of problem phase (i.e. after the identification of the problem phase). The author will write the suggestions of solutions for Legenda online student time table system and the features that will help LEGENDA EDUCATION GROUP in doing their work efficiently and effectively (i.e. do thing right and doing the right thing). The author’s suggestions are gathered from the knowledge base for the problems. Suggestions are normally made to reduce the risk of system failure. The author again, needs to ensure that relevant issues “Legenda online student time table system” would be covered in implementation. The scope of this research work (proposal) is the implementation of Legenda online student time table system whereby suitable interface design and customization will be exploited.
3.4.3 DEVELOPMENT OF ARTIFACT
The prototype (Legenda online student time table system) is developed using Netbeans. The development of artifact makes easy for the interaction between uses and the prototype, users will have comprehensive knowledge of the requirements (because, most of the users do not know what they want or need), after users analyze the prototype “Legenda online student time table system” and provides corrective feedback, the author will use their valuable information in implementing the proposed system. The development of artifact (sample) of Legenda online student time table system, after the problems are identified and the suggestions (proposal) is accepted. Although, the development of artifact is straight forward, thus, the tentative design is implemented for developments of Legenda online student time table; an algorithm (genetic algorithm) is required to develop the system. The suggestions and implementation phase is successful because, a successful design decision is an output product (Vaishnavi and Kuechler, 2004).
3.4.4 EVALUATION
In the evaluation phase, the artifact is evaluated according to the criteria of the requirements in the awareness of the problems phase (where problems of the systems are identified). Qualitative and quantitative (interviews and questionnaire) are used to and are explained clearly. During the evaluation phase, the prototype “Legenda online student time table system” will be evaluated after the development phase is done via the interview and questionnaires users give out their opinions or suggestions, after all, the system is built for the users, so their evaluation and feedback is very crucial in either to drop the proposal or continue with the actual development and implementation of the proposed system. The author will explicitly evaluate the artifact according to development criteria’s that are made in the proposal (awareness of problem phase). The output is a feedback to other suggestions.
3.4.5 CONCLUSION
The conclusion will give a clear picture of the artifact or result. The operation and goal of knowledge of the artifact, for this research involving Legenda online student time table system was the implementation of the problems development, design of work break down and the actual design of the proposed system.

3.5 SOFTWARE DEVELOPMENT LIFR CYCLE (SDLC)
A methodological review of past literature is an important effort for any academic research (Webster and Watson, 2010). According to Phillips (2010) software methodologies are concerned with the process of creating software. These simply imply that, the methodologies are the techniques, methods or steps that are followed and used in software or system development life cycle (SDLC). Software development life cycle can be defined as the method or process of developing an information system via some important or successful phases or stages of the SDLC. Hence, Peslak, Subramanian, Clayton, (2008) conducted a research on “The phases of ERP software implementation and maintenance” the software development life cycle is mainly based on the new software development. This includes the Planning phase, Analysis phase, design phase, Implementation phase and lastly Maintenance of the system after delivery of the finished product.
However, a single method or methodology cannot be always correct because every single methodology has its own strength and weakness. For example, the strength of waterfall methodology is “developing a reliable, quality system with excellent documentation” whereas prototyping (sample) has the weakness of “quick and dirty method of software development”. Therefore, no single methodology is perfect as software development life cycle is concerned. In a research conducted by Jianga et al. (2010) on “System analysts’ orientations and perceptions of system failure” it is not easy to quantify and select the appropriate methodology for system or software development life cycle. Many companies adapt their own model or methodology, but all have similar pattern. The diagram below will shade more light on the SDLC.

3.5.1 CHOSEN METHODOLOGY
The most appropriate methodology for developing this system is “THROWAWAY PROTOTYPING” as shown in the diagram below. Figure 1.0 Throwaway prototyping has a fairly thorough analysis phase that is used to gather requirements thoroughly and to develop ideas for the system concept. Many of the functions suggested by the users may not be well understood when conducting JAD session because most of the users do not know what they want or what they need. Therefore, throwaway prototyping solve this problem by gathering the requirements thoroughly in the analysis phase and the other subsequent phase of development. The system that is developed using this methodology is likely to require several prototypes during the analysis and design and prototyping phases concurrently. Each of the prototypes is used to minimize the risk associated with the system confirming that important requirements are understood before the real system is built but since most of the users do not understand how to interact with the prototype authors add the design phase to show the real user interfaces that can make the customer satisfy and the developers will manage to design the interfaces easily using HTML and it will not cost them anything (free). Below is the diagrammatical representation of throwaway prototyping.

Figure3.3: Throwaway Prototype
Figure3.3: Throwaway Prototype (Dennis, Haley and Roti, 2008)
3.5.2 STAGES INVOLVED IN THROWAWAY PROTOTYPING
The stages involved in throwaway prototyping includes; Planning, Analysis, design, implementation, design prototype and the implementation of the final system after the system is accepted by its users. Thus, all of the stages that are involved in building the system will be discussed below in details
3.5.2.1 PLANNING
Planning is the first phase of the software development life cycle. The author will plan and understand why “LEGENDA ONLINE STUDENT TIME TABLE SYSTEM” is needed and what achievements will the system provide INFORMATION TECHNOLOGY DEPARTMENT and LEGENDA EDUCATION group in general. The author will serve as the project manager because the author creates the work break down and plan the project. The technical feasibility (i.e. can the author built the system), is the author familiar with the appropriate technology to develop the proposed system, the project size is also considered as to know what and what to plan in the project breakdown of the system. The author will surely create the Gantt chart and show the work breakdown structure and identify the risks that are likely to arise in the designing and the implementation of the proposed system (Legenda Online Student Time Table system). Planning is the first phase of the throwaway prototyping. In the planning phase, the author plans and understands (find out) the reasons why an information system should be built. List the problem statements, defining its aim and objectives; develop work plan, control and direct project. Gantt chart is used in the system to plan the project, system request and feasibility studies in the planning phase.
3.5.2.2ANALYSIS
The analysis phase is the second phase of the software development life cycle. The author will analyze the system (current manual system, its improvements and the required functions for the to-be system) and identify the functions of the system, where will the system be used (e.g. Malaysia) and when will the system be delivered to its humble users. Requirement gathering techniques, which are questionnaire and interview, will be conducted so that the author will know exactly what the users want in the system. However, requirements will be well understood by the author(s). Database design and the use cases (actors and their functions) will be created in this chapter. In this phase, the author proposed the system (system proposal), develop analysis strategy (business process automation, business process improvements and business process re-engineering). It enables the users understand why? Building system and to determine how the project team will built it. The author also did the requirement definition (i.e. interview, JAD session and observation). Use cases and data models are also done in this phase. This phase answers the question that, who will use the system? What the system will do? Where and when the system will be used? It has three steps: analysis strategy, requirements gathering and system proposal. The author also conducted interview in this phase which will be attached to the appendix in the final submission of the final documentation of the system.
3.5.2.3 DESIGN PROTOTYPE
Design is the most expensive, longest and the third phase of the software development life cycle. The author will know how the system will be designed (i.e. in terms of the hardware and software specification, interface design and software specification and the network infrastructure). The design strategy will be provided as to know how the system will be built (that is; either by programmers, outsourcing from other firms or buying already made existing system). The author will also design and develop the database and file specification and know what data should be stored in the database. The design prototype is like the JAD (Joint application development) session because the SYSTEM ANALYST and all the stake holders (uses of the system) will sit and analyze the system prototype (sample). The author will show the system prototype to its uses, though most of the important requirements are embedded in the first design of the prototype (Legenda Online Student Time table system). If the users are satisfied with the prototype design, the author will continue with the actual design. The main advantage of throwaway prototype is the design prototype that is used to create some part of the system.
3.5.2.3 DESIGN
In this phase, the author (project team) will design the actual design, design of the physical system, designing of the systems interface, designing of programs and database. The hardware, software and network specifications are also conducted in this phase. Design is the hardest part of the SDLC. It elaborates more on how the system will operate in terms of hardware, software, and network infrastructure that will be in place, the user interface, forms, database and files that will be used. Design is the most expensive, longest and the third phase of the software development life cycle. The author will know how the system will be designed (i.e. in terms of the hardware and software specification, interface design and software specification and the network infrastructure). The design strategy will be provided as to know how the system will be built (that is; either by programmers, outsourcing from other firms or buying already made existing system). The author will also design and develop the database and file specification and know what data should be stored in the database. The design may include; sequence diagram, activity diagram, use case diagram, class diagram, collaboration diagram, state chart diagram, deployment diagram, Gantt chart and navigational chart respectively.
3.5.2.5 IMPLEMENTATION
Implementation is the last stage of the software development life cycle. The author will conduct the software testing, validation testing, unit testing, integration testing and acceptance testing concurrently. The overall system documentation in lenient terms user manual, will be provided in the end of the implementation, to help users understand and know how interact with the system. This is the coding part of the system (programming). The author did the testing and validation of the system (test plan), the documentation of the whole system and the performance testing. Implementation is the final stage of the SDLC; this is where the system is implemented. Implementation is the longest and most expensive part of the SDLC. It has three steps: construction, installation and support plan. The diagram below elaborates more on SDLC (Dennis, Haley and Roti, 2008).
3.5.2.6 SYSTEM
This is the final system after the implementation phase. The system will be delivered to its actual users.
3.5.2.6 JUSTIFICATION OF THROWAWAY PROTYPE
Waterfall methodology and its variants (v-model, parallel model) are very good for large qualitative and expensive system. Waterfall model takes more than a year to deliver system to its users. However, viral model (variant of waterfall) gives high priority to testing that includes, the unit testing, system testing, integration testing and acceptance testing concurrently. Viral model increases the quality of the overall system because it pays explicit attention in testing of the whole system. Parallel model on the other hand strives to solve (address) the limitations of waterfall model because it allows part of the system to be delivered in increments (i.e. sub project 1, subproject2, subproject…….n concurrently). However, it suffers greatly from the issues caused by vast (voluminous) deliverables of the proposed system, thereby adding more functions and new problems or issues in implementing systems.
RAD (Rapid Application Development) emerges due to the weakness of waterfall and its variants (i.e. viral model and parallel model respectively). Rapid application development emphasizes explicitly on the JAD sessions because it allows users to evaluate the “Legenda Online Student Time Table System” prototype (sample) so that, the can evaluate and provide important and corrective feedback that will be used in future design and implementation of the system. Thus, the process of evaluation of the system will be continued for ever otherwise known as scope creep. Due to the requirements of the proposed system, the author shall use “Throwaway prototype” because it allows the development team and all the stake holders to analyze the system and to develop and build a system prototype (sample) that users will evaluate and provide corrective feedback. Thus, Throwaway prototyping is a good development method to be used when the user requirement is not clear, when the development teams are not familiar with technology (e.g. latest technology), when building a reliable system (throwaway prototyping is excellent), when building complex system throwaway is excellent and delivering system to the users within a short time schedule.
3.6 FACT FINDING TECHNIQUE
Fact finding techniques are the techniques that are used to understand the as-is system, improvement and the proposal of the to-be system. Fact finding techniques includes; interview, questionnaire, observation, document analysis and the JAD (joint application development) respectively. The fact finding technique helps the author to gather user requirements and know exactly what features or functions that will be embedded in the Legenda online student time tables system.
3.6.1 INTERVIEW
In the interview session, the author will interview the co-coordinator of IT department (Mdm. Teo Siew and Mr. Kannan) and other IT staff that interact with the current paper based timetable so that, the author will get in-depth knowledge on how student time table is generated. However, the author will understand what and how to go about building the proposed system (that is; system requirements and the user’s requirements). Interview will be conducted within Legenda information technology department (IT), and then it would be easier for the author to design the interview questions for the system users (mostly, students).
3.6.2 QUESTIONNAIRE
The questionnaire is normally prepared for a specific number of people; the author knows that the system is intended for Legenda Information Technology department. For questionnaire to be successful, the author will analyze and quantify the number of students and their races (e.g. if 60% of students are Africans, 10% Chinese, 5% Bahrain, 5%Australians and 20% Malaysians). The questions that will likely to be asked includes open ended and close ended questions. Example; what are the issues associated with time table retrieval or collection (open ended). How many hours do you spend surfing the internet (close ended questions). Questionnaire is seen to provide high information and has less cost unlike the observation or the interview. Therefore the author shall use QUESTIONNAIRE to gather requirement of the as is system before moving to the improvement and then to the to-be system (future system). Using questionnaire, information can be easily collected form users (unlike JAD) and that’s why the author prefer to use Questionnaire for their requirement gathering technique.
3.7 DATABASE
The author will use MySQL because of its dynamic features and its simplicity. Interacting with MySQL is a bit complicated for novice users or beginners because; it is not built with WYSIWYG (what you see is what you get i.e. interface design). Most web programmers prefer to use MySQL because it supports thousands of users without affecting the speed and performance of the system unlike Microsoft access. Using MySQL you can easily access thousands of record and manipulate them as you wish or like. For example, most web programmers use it on the server site. It loads SQL queries fasters and reliable as well. MySQL can easily run with phpMyAdmin, for windows example WAMP SERVER, XAMPP SERVER, and APPSERVER. MySQL also gives powerful transaction because of its public acceptance globally. Most importantly, it is an open source (free) unlike Microsoft access. Moreover, MySQL follows relational database model, since record can be easily related with the aid of PRIMARY KEY (PK, unique key in a table e.g. IC Number) FOREIGN KEY (FK is a primary key in another table and non-key in other table). It also works best in maintaining and managing sophisticated databases. Therefore, The Author will use MySQL in creating and building the proposed system.
3.8 ETHICAL ISSUES
The Internet and computers did not invent or even cause privacy issues. The issues existed long before the creation of computers and Internet. The existence of Internet, computer and large data storage make it possible to collect process and transmit large volume of data, including personal data. Today, the study of privacy usually involves different dimensions: laws, ethics and information technology. As network applications and services become more ubiquitous, many different ways of collecting and accessing user private information have emerged, making people’s lives more convenient. At the same time, however, users are often forced to provide their private or sensitive information to service providers. Due to many technical and administrative reasons, user’s private information is often poorly managed by service providers and sometimes abused, resulting in serious privacy violations. To give end users privacy they can totally control for the dynamic, pervasive computing environments becomes a major research challenge.
Ethical issues plays a vital role in software development because, some software plays role in many facet of life. Alternatively, this raises the issues of ethics and responsibility for correct execution of software as well as its fitness in any setting becomes increasingly complex, especially when the software impacts a life and death. The ethical issue includes the following;
3.8.1 PRIVACY
The use of privacy comprises of freedom from intrusion, control of personal information and freedom from surveillance. The freedom from intrusion refers to the right to be left alone. Improper access to personal information is the issue that privacy usually brings to mind. In this section, privacy is examined from the standpoint of data fusion, location privacy, public information, and Internet technologies. Each creates unique problems for software design, development, and deployment.
3.8.2 ACCESSIBILITY
Components to use a system, a person must have access to the required hardware and software technology, must be able to provide any required input, and must be able to comprehend the information presented. For example, for a Web based system, the user must have a reliable connection to the Internet, as well as the appropriate connection speed. The end-user must also have a browser compatible with the material sent to it (i.e. including such things as the appropriate Java classes for use with applets) and any helper applications or browser plug-ins for viewing and hearing content. If the audience is in a developing country, or in a remote area such technological issues may be critical for this reason, when a system is developed, its implementation should be part of an integrated process that includes alternative knowledge elicitation and knowledge delivery methods that are appropriate to the full range of affected individuals. This may include specifying duties for a range of ‘actors’ such as technology transfer officers or field personnel.
3.8.3 DATA FUSION
Any unauthorized access to information can be an invasion of privacy. However, even authorized access may lead to privacy concerns, when access to separate data sources is used to combine information. For example, one institution may record an individual’s name and employee number, while another may be authorized to store employee number and health insurance claims, but the combination of the individual’s name and the health insurance claims may be an invasion of privacy. This is not yet a major issue in system development for natural resources and agriculture. However, as environmental databases increase in size, complexity, and connectivity, software projects that involve combining data or knowledge sources must consider the ethical implications of those activities.

3.8 CONCLUSION
In conclusion, the author understands the reasons of selecting the appropriate methodology compare between waterfall model and its variants (i.e. viral model and parallel model), compare between throwaway, prototyping and extreme programming (Xp). Again, the author choose the best and most reliable fact finding techniques which are interview and questionnaires, the questionnaires where been passed out to students to evaluate and provide important feedbacks on what they want to be embedded in the proposed system “Legenda Online Student Time Table System”. However, the interview was conducted with Mr. Kannan, Madam Teo Siew all of information technology department (IT department). Thus, the research method is also conducted in this chapter there by allowing the author to get a clear picture of the requirements of the proposed system.
Moreover, the next chapter (chapter 4) the analysis chapter will consist of the requirements analysis table, the functional and the non-functional requirements, the hardware and the software requirements and last but not the least, the network requirements. The author will analyze the system as- is system, identify the improvements and then proposed solutions for the to-be system.

CHAPTER 4
ANALYSIS
4.1 INTRODUCTION
In this chapter, the author will conduct the analysis of the as-is system, improvements and the proposed requirements of the to-be system. Requirements specification includes the functional requirement (user requirements) and the non-functional requirement (system requirement). Again, the required hardware and software to run the system will be discussed in detail below. The analysis of the result of the interview and questionnaires shall also be discussed and showed in a diagrammatical manner with the aid of pie chart, Gantt chart, bar chart etc.

4.2 REPORT OF QUESTIONNAIRES
The analysis and result of questionnaires conducted for “Legenda Online Student Time Table System” are shown below with the aid of Pie chart. Sixty (60) questionnaires were given out to students for evaluation and feedback. Additionally, out of the sixty questionnaires given out to students for evaluation and feedback, only 22 questions are recovered but the remaining questionnaires are not answered well, some are not recovered and some are disregarded due to wrong answers provided.
However, the questionnaires are given out to Software Engineering students and Business Information System students respectively, for evaluation and feedbacks due to the fact that the system is build for them. Below are the analysis of all the questionnaires given out to students and are elaborated with the aid of pie chart and a summary description of the questionnaire. Analysis of Clashing Lecture Venue
Figure4.1: Analysis of Clashing Lecture Venue
Figure4.1: Analysis of Clashing Lecture Venue

The above question is very crucial in identifying requirements of the system for it is among the most important problems in the current system (i.e. paper based system). From the above pie chart, you can easily see that clashing of lecture venue occurs regularly. The number of students that choose “once” is 88%, “2-3 times” are 5%, “more than 4 times” are 6% and “never” is 1% respectively. This question will tell the author (developer) of Legenda Online Student Time Table System the problems that Legenda IT student feel about the current manual system. So the author will provide solutions to the above problem by designing and building an online system (Legenda Online Student Time Table System) that will eradicate the occurrences of clashing lecture venue concurrently. Analysis of Changed Lecture Timetable

Figure4.2: Analysis of Changed Lecturer Timetable
Figure4.2: Analysis of Changed Lecturer Timetable

The above question will help the author (system developer) to identify the problems with the manual paper-based system in order to provide alternatives or rather solutions to Legenda School of Information Technology in other to do the right thing (i.e. effectively) and provide student with an error free lecture time table repeatedly. This question will tell the author exactly the problems and limitations of current manual system (i.e. using excel to organize and generate student lecture time table).
However, from the above analysis, we can see that the number of students that selects “once” is 20%, “2-3 times” is 50%, “more than 3 times” is “35%” and “never” is 5% respectively. The 50% response for 2-3 times change in timetable only shows that half of the population asked experienced a correction of their timetable twice in a semester. Therefore, the current paper-based timetable system is not trustworthy and reliable. The proposed system “Legenda Online Student Time Table System” will help in providing solutions to the issues of wrong timetable faced.
Analysis of Rescheduled Lecture Time

Figure4.3: Analysis of Rescheduled Lecture Time
Figure4.3: Analysis of Rescheduled Lecture Time

This question will give the author the impression of the inconsistencies faced in the current system when providing students with error free lecture timetable in a semester. This question will help the author in providing a function for the lecture time that will be stored in the database with an ID that will not allow administrator to have same lecture time for a specific subject. More so, the analysis of this question shows that 20% of students choose “once”, 30% of students choose “more than 2 times”, 30% of students choose “more than 3 times” and 20% of students choose “never”. From the analysis of student’s feedback, we can assume that most of IT students face problem of rescheduled lecture time more than 2 times or more than four times in a semester. The proposed system “Legenda Online Student Time Table System” will provide solutions to the above inconsistencies of the manual system.

Analysis of Lecture Venue
Lecture Venue
Lecture Venue

Figure4.4: Analysis of Lecturer Venue
Figure4.4: Analysis of Lecturer Venue

The above question is very crucial in identifying the requirements of the system so that the author (i.e. system developer) will know what the users (students) want and the functions needed in the proposed system (i.e. Legenda Online Student Time Table System). However, the number of students that choose “once” is 10%, “more than 2 times” is 40%, “more than 3 times” is 45% and “never” is 5% respectively. From the analysis, the highest percentage of students believes that the lecture venue is changed more than 3 times in a semester, all these inconsistencies occur in the current system. Therefore, the proposed system “Legenda Online Student Time Table System” will provide solution to the above named problems faced in the paper based system (i.e. using Microsoft excel to design and provide lecture time table for students).

Analysis of Collect Lecture Timetable

Figure4.5: Analysis of Collect Lecture Timetable
Figure4.5: Analysis of Collect Lecture Timetable The above question is one of the most important questions in requirement gathering technique (i.e. questionnaires) because it tells the author (i.e. developer) the length of time that students receive their timetable in the current manual based system. The author will provide a function that will ease the problems faced in collecting timetable. As you can see from the above analysis of this question, 60% of students said that the collection of lecture time takes “1-2 days”, 10% of students choose “More than 3 days”, 25% of students choose “more than a week” and 5% of students choose “2 weeks”. However, the current paper based system is not reliable because it cannot provide students will lecture timetable instantly. So, the proposed system “Legenda Online Student Time Table System” will be provide students with a function to download their lecture time table when logged in to the system.

Analysis of Collect Time Table Online

Figure4.6: Analysis of Collect Time Table Online
Figure4.6: Analysis of Collect Time Table Online

The above question will allow the author to gather the requirements on how users (students) want the system. The analysis of the above question shows that 90% of student said, “yes” whereas 20% of students said “no” to the above question. From the above answers, the students prefer online collection of their timetable as it is more convenient to them. We can now see that the proposed system must have an online function that will allow the students to access their lecture time table online thereby saving the students time and effort. Legenda Online Student Time Table System will provide students with user login and password that will enable them to collect their timetable via the Internet by logging to the proposed system.

Analysis of Time Table Format

Figure4.7: Analysis of Time Table Format
Figure4.7: Analysis of Time Table Format This very question is important for it allows the author (developer) of “Legenda Online Student Time Table System” to identify what format of the time table is to be produced. Many respondents prefer to the timetable to be in PDF (Portable Document Format), some respondent chooses DOC (Document) while others chose other format. However, the above analysis shows that 10% of respondents choose “others”, 20% of respondents choose “Doc” and 70% of respondents choose “Pdf”. The analysis shows that the developer (the author) will create the lecture timetable in a pdf (i.e. printable document format) to allow students to download or save the lecture timetable on their system (pdf).
Analysis of font size

Figure4.8: Analysis of Font Size
Figure4.8: Analysis of Font Size

The above question will help the software developer (i.e. the author) in identifying the actual font size that the respondents will require or like to see in the printable lecture timetable. Font size is very crucial as far as timetable is concern, because when the font size is clear enough and readable, it would help students with eye problems to read and know their lecture timetable. As you can see form the pie chart above, 14% of respondents choose “10”, 33% of respondents choose “12”, 48% of respondents choose “14” and 5% of respondents choose “16”. From the above analysis, we can assume that the highest number of respondents prefers 14-size font size timetable. The author will use 14-font size for building the timetable system (i.e. built-in in Legenda Online Student Time Table System).
Analysis of Time Table Color

Figure4.9: Analysis of Time Table Color
Figure4.9: Analysis of Time Table Color

The analysis of the above question will be used in providing a suitable background color of the timetable for students. The author uses this question to get a valuable feedback from the correspondents on the background color of the student lecture timetable. The proposed system Online Student Time Table System will provide students with suitable back ground color depending on the user’s feedback. The above analysis shows that 30% of the correspondents choose “blue”, 30% of the correspondents choose “pink”, 10% of the correspondents choose “green” and 10% of the correspondents choose “others”. From the above analysis, the author will build the system using either blue or pink as the back ground color of the timetable in Legenda Online Student Time Table System.
4.3 ANALYSIS
The analysis phase is conducted so as to gather requirements (functional requirement) and to understand how the current system is working, identifying the improvement of the current system and then proposing solutions for the to-be system (proposed system). The analysis based on the requirements gathering techniques. That is; questionnaires and interview. Thus, the author interviewed some staffs of Legenda Information technology department (IT department) and the questionnaires were given out to students to evaluate and provide valuable feedback. By conducting the interview and questionnaires accordingly, the author will understand what exactly the users want and then building the right system for the humble users (base on the user’s requirements).
4.3.1 ANALYSIS OF THE INTERVIEW SESSION
The interview is conducted on the 22nd of March, 2012. The author went to Legenda Information Technology School (IT school) and conducted an interview session with Mr. Kannan; the coordinator of software engineering (S.E) and Mdm. Teo Siew the coordinator of Business Information System (BIS) in Legenda Education Group. The reason behind interviewing the above gentle man and woman is to know how the current system works (as-is system) and understands the ways, procedures and the constraints that are involved in generating a good and standard student lecture time tables.
However, some of the issues or problems faced are earlier discussed in chapter one (i.e. the problem statements) in this research work. After holding the interview session, the author identified some valuable information that will aid in developing and implementing the proposed system. Thus, allowing the author to understand more on how the proposed system will be like.
Moreover, based on the information gathered from the above gentle and humble Legenda Information Technology personnel’s, several requirements were identified as well as the features of the current system, and what are the expected functions that the proposed system should provide. Thus, allowing the author to understand more on how the proposed system will be like.
4.4 REQUIREMENT ANALYSIS
A requirement is simply a statement of what the system should do and the functions it should have or perform. According to Tsui and Karam (2009), a requirement comprises of a set of statements that describes or explains the user’s needs and desires. Requirement in software engineering is nothing but a statement of what the system should do and the functions it should have. Requirement includes functional (User requirements) and non-functional requirement (System requirement).
4.4.1 FUNCTIONAL REQUIREMENTS
According to Zain, Mohd, El-Qawasmeh (2011), functional requirement identification is a high priority phase because; it allows the development team (the author) to understand and know the functions of the system (e.g. login, search, logout etc.). A functional requirement represents the abstraction and the behavior of a particular system (O'Sullivan, 2002). However, functional requirement specifications are based on the use cases (Amyot and Williams 2005). Functional requirement of the proposed system is classified in to two (2) which are; User requirements and system requirements. Functions of the proposed system “Legenda Online Student Time Table System” will be discussed below:-
4.4.1.1 USER REQUIREMENTS
The user requirement of a system must describe the functional and non-functional requirements so that, system users can understand the system without much technical knowledge. The user requirement of the proposed system will be written in simple English language by the author without using technical terms that the users might not understand. The user requirement of the proposed system will be in the table 4.1.
4.4.1.2 SYSTEM REQUIREMENTS
“System requirement is an extended version of the user requirements that are used by software engineers as the starting point for the system design” (Sommerville, 2007). It normally adds a detailed description on how user requirements should be provided by the system. The reasons behind conducting System requirements are to simply describe the behavior (external) of the system and its constraints. The table 1.0 below will give a clear picture of the user and system requirements of the proposed system.
4.4.1.3 ACTORS OF THE SYSTEM
An actor or actors in Unified Modeling Language (UML) specifies the role played by actors (users) of the system or the external system that interact with the system or other external systems that interact with the system. A unified modeling language may represent human being, other systems and external hardware (e.g. banks).
4.4.1.4 IDENTIFICATION OF ACTORS
The actors of the proposed system (i.e. Legenda Online Student Time Table System) include the following:- * Students * Administrator
4.4.1.5 DESCRIPTION OF ACTORS
Below is the description of actors of the proposed system. It includes the following:- 4.4.1.5.1 STUDENTS
The proposed system is mainly built for students. So, a student plays a vital function in the proposed system (i.e. Legenda Online Student Time Table System) because, it allows students to login to the system, download time table, send time table to their email address, and upload file on the proposed system. 4.4.1.5.2 ADMINISTRATOR
The administrator is the key user of the proposed system. He adds lecturers to the system, adds students, adds course to the system, assign course to lecturers, generate student time table, update students and lecturer’s information, delete students and lecturers from the system’s database respectively.
Table4. 1: User requirements and System requirements of the proposed system SYSTEM ACTORS | USER REQUIREMENT | SYSTEM REQUIREMENT | * Student and Administrator | * Users (Students and Administrator) should be able to Login to the system | * The system should display login page * The system should display (*) for important fields or text boxes. * The system should confirm and verify the user credentials from the database * The system must display home page (index page) after Login to the system | * Administrator | * Administrator should be able to register students to the system * Administrator should be able to add and delete students and lecturers * Administrator should be able to update students and lectures information respectively * Administrator should be able to assign courses to lecturers * Administrator should be able to add venue to the timetable * Administrator should be able to create Student Time Table * Administrator should be able to assign password to student and lecturers | * The system should validate email address * The system should prompt the users if an important field is left blank or skipped. * The system should display user registration page * The system should display a successful message if a user is registered (added to the database) * The system should be able to display un-successful message if the user registration is un-successful * The system should be able to encrypt users password in the database (md5 encryption) method or technique | * Student | * Student should be able to login to the system * Student should be able to save lecture Timetable * Student should be able to download time table * Student should be able to view time table | * The system should display timetable page * The system should allow users to save file and view it in pdf format * The system should allow students to download file * The administrator and the student who uploaded the file should be able to delete the file | 4.4.2 NON-FUNCTIONAL REQUIREMENT
The non-functional requirements are the requirements that affect the computer as whole. Non-functional or quality requirements are those requirements that are not concerned with the functions of a system (Aurum and Wohlin, 2005). So, non-functional requirements are specifically used in the system quality and way harder than functional requirements. Nonfunctional requirements deals with system quality issues in particular software and describes different attributes in that particular system. The non-functional requirements attribute accuracy, security, usability requirements, performance and system reliability (Tsai and Li, 2001). However, non-functional requirements are the constraints on the functions of the system which includes “timing constraints, development process constraints and standards” (Sommerville, 2007). According to Wysocki, (2011), non-functional requirements are associated with performance that sets the way of how the system will function. Though, non-functional requirement affects the system as a whole. The non-functional requirement of the proposed system includes the following:-
Table4. 2: Non-functional requirement NON-FUNCTIONAL REQUIREMENT | DESCRIPTION | * Performance requirements | * For the proposed system, performance requirement is very crucial. Performance allows the author to know how the system performs in terms of “response time”, “throughput” and “concurrency”. Concurrency how many users can access the proposed system simultaneously. How many request can the proposed system handle? How fast can the system handle individual request (e.g. print time table). However, performance is a very delicate matter and must be critically analyzed and implemented for the proposed system | * Security requirements | * Security requirement is an important nonfunctional requirement. Nobody will like to use intentionally use a system that is not secured. The proposed system is much secured to the extent that if user enters wrong password more than three times, he will have to wait for three minutes and then try again. Security requirement also helps in securing important files and documents from unauthorized access. However, Legenda Online Student Time Table System uses md5 encryption to encrypt user password in the proposed system | * Reliability requirements | * Reliability is an important nonfunctional requirement and tells the author how reliable the system is in terms of operation and workload. The propose system should work for 24/7 (twenty four hours a day/ seven days a week) so that, users can access the system easily. Though, the system can be able to tolerate fault and the system ability to work even after failure (i.e. access data). | * Interface requirements | * The interface requirement is all the usability of the system. The proposed systems HCI (human computer interaction) will be organized and designed. The interface color of the system will not be more than three colors so that, users can find it suitable and easy to interact with the system. The interface design of the proposed system will be built with suitable navigation, pictures, buttons and simple animation. | * Maintainability requirements | * The proposed system should be easily maintained as well as easy to upgrade. Thought, a quality documentation (documentation of the planning phase, analysis, design and implementation phase respectively) must be provided for the system to be upgraded in the feature | * Simplicity requirements | * The proposed system will be very simple and have simple interface structure. The system will be very simple there by allowing its users to easily interact with the system. | * Privacy requirements | * The proposed system should be able to keep lecturers and students record without given out their privacy to the public. E.g. date of birth. Legenda Online Student Time Table system will be able to protect users privacy from un-authorized and must be kept confidential |

4.4.3 HARDWARE REQUIREMENT
Hardware requirement is the hardware (physical component of computer) of the computer systems. Bhardwaj (2000) states that; hardware requirement determines and tells the author what hardware is required for the proposed system. For example, the hard disk size, the RAM size etc. The table below will describe all the hardware that is required to build and implement Legenda Online Student Time Table System.
Table4. 3: Hardware requirement HARDWARE | MINIMUM | RECOMMENDED | DESCRIPTION | * Random access memory (RAM) | * 1GB RAM | * 1GB RAM | * Used to save temporary data. It is also used to when running large programs to speed up system’s performance | * Hard Disk | * 80GB | * 80GB | * It is a permanent mode of storage in the computer system. The operating system of the computer system is saved in the hard disk | * Mouse | * Laser mouse | * Optical mouse | * The pointer device that will be used in the proposed system | * Processor | * Pentium 4 processor | * Intel dual core processor or higher processor | * It is a logical circulatory that responds to and processes the basic instructions that drive a computer system | * Keyboard | * Dvorak Simplified Keyboard | * QWERTY keyboard | * This is a standard keyboard that will be used for the proposed system | * Monitor | * 15” inch monitor | * 15” or higher inch screen | * This is used to view or display in the proposed system | * Scanner | * Flatbed scanner | * Ngenuity 9125DC | * It is used to scan documents faster and easier | * Printer | * Inkjet printer | * Laser printer | * It is an output device that produces text and graphics on paper |

4.4.4 SOFTWARE REQUIREMENT
According to Richard (2007), software requirement process is the first step in most software development process because; it allows the development team to determine if the system can be built and delivered in the stipulated time of delivery. Thus, software requirement helps in knowing how to build the proposed system (Legenda Online Student Time Table System) without further delay. The table below shows the software requirements in details.
Table4. 4: Software requirement SOFTWARE | MINIMUM | RECOMMENDED | DESCRIPTION | * Database | * MySQL Server | * MySQL Server R2 | * MySQL is a server software that is used to store record in an information system | * Mac OS | * Mac OS X | * Mac OS X | * An operating system that the system will run on | * Windows Operating System (OS) | * Windows Xp | * Windows vista or windows 7 | * This is the operating system that the system will run on | * Design Tool | * Macromedia Dreamweaver, Netbeans and front Page 2003 | * Netbeans | * A software tool used to create and edit sophisticated websites | * Microsoft office | * Microsoft office 2003 | * Microsoft office 2007/2010 | * Software package | * UML tool | * Rational Rose Enterprise Edition 98 | * Rational Rose Enterprise Edition 2003 | * Rational rose is a modeling tools that is used to create use case, class diagram, activity diagram etc. | * Programming Language | * Php | * Php | * Php is a server-side language that the compiler understands when creating and running sophisticated and simple WebPages. E.g. running website in Google chrome | * XAMPP Server | * WAMP Server Version 2.0 | * WAMP Server Version 5.0 | * XAMPP Server is a server site tool that is used to connect web pages to database and run on the web browsers | * Anti-virus | * MacAfee Anti-virus 2010 | * MacAfee Anti-virus 2012 | * A virus detecting and removal tool. It also warns against malware and Trojans |

4.4.5 NETWORK REQUIREMENT
Network requirement defines what the wireless network needs to do. The network requirements include all the requirements that must be used to connect the proposed system to the internet. The network requirement of the proposed system includes the following: -

Table4. 5: Network requirement SOFTWARE | MINIMUM | RECOMMENDED | DESCRIPTION | * Switch | * Cisco 8-port Standard 10/100 Network Switch (SD216TUK) | * Cisco 16-port Standard 10/100 Network Switch (SD216TUK) | * It is a computer networking device which will connect network segments | * Bridge | * Cisco Linksys Dual- Band N bridge with 4-port Switch (WES610N) | * Cisco Linksys Dual- Band N bridge with 4-port Switch (WES610N) | * Filters data traffic at a network which is very crucial for the proposed system | * Network card | * D-Link N150mbps Wireless N PCI Adapter Card (DWA-525) | * D-Link N150mbps Wireless N PCI Adapter Card (DWA-525) | * It is an expansion card that enable computer to physically connect LAN (local area network) | * Wireless Modem | * TP-Link N300mbps High Gain Wireless N USB Adapter (TL-WN822N) | * TP-Link N300mbps High Gain Wireless N USB Adapter (TL-WN822N) | * It is a wireless connection to the internet. Thus, It connects to a wireless networks. | * Router | * HuaWei E583X MIFI 3.5G Portable router for Galaxy/Playbook/Ipad E585 E... | * HuaWei E583X MIFI 3.5G Portable router for Galaxy/Playbook/Ipad E585 E... | A device that forwards data packets between telecommunications networks | * Network cable | * RJ45 | * RJ45 | A cable that is used for LAN and WAN connection and can be connected to all computer system is network port | * Server | * HP Proliant DL140 G3 Server (1U rack mount) | * HP Proliant DL140 G3 Server (1U rack mount) | To be used to host Legenda Online Student Time Table |

4.4 CONCEPTUAL DATA MODEL
Adds
Adds venue venue capacity id users fullname course type matric_id username semester timetable_group password id academic_year semester course id year lecturers id name email passport department qualification phone t1
Academic_year
m1 timetable w1 th1 mv1 f1 s1 tv1 wv1 thv1 fv1 sv1 mg1 tg1 wg1 thg1 fgv1 sag1 id
Creates
courses id course
Course_code
semester lecturer year class Adds
Adds
Adds venue venue capacity id users fullname course type matric_id username semester timetable_group password id academic_year semester course id year lecturers id name email passport department qualification phone t1
Academic_year
m1 timetable w1 th1 mv1 f1 s1 tv1 wv1 thv1 fv1 sv1 mg1 tg1 wg1 thg1 fgv1 sag1 id
Creates
courses id course
Course_code
semester lecturer year class Adds

Adds
Adds

4.4.1 NORMALISATION 1. users – venue (1: M) UNF users (venue, capacity, id {fullname, type, course, matric_id, username, semester, timetable_group, password, id}) venue (venue, capacity, id) Un-Normalized Form 1NF users (id, fullname, type, course, matric_id, username, semester, timetable_group, password) venue(id, id, venue, capacity) Partial Dependency (Primary key determines a non-primary key) 2NF users (fullname, type, id, course, matric_id, username, semester, timetable_group, password,) venuser (id, id) venue (id, venue, capacity) Transitive Dependency (Non-key Determines a Non-key) 3NF users (fullname, type, id, course, matric_id, username, semester, timetable_group, password,) venuser (id, id) venue (id, venue, capacity) Full Dependency

2. users – lecturers (1 : M) UNF users (fullname, type, course, matric_id, username, semester, timetable_group, password, id {id, email, department, phone, name, passport, qualification}) Un-Normalized form 1NF users (id, fullname, type, course, matric_id, username, semester, timetable_group, password) lecturers (id, email, department, phone, name, passport, qualification) Partial Dependency (Primary key Determines a Non-key) 2NF users (id, fullname, type, course, matric_id, username, semester, timetable_group, password) lecusers (id, id) lecturers (id, email, department, phone, name, passport, qualification ) Transitive Dependency (Non-key Determines a Non-key) 3NF users (id, fullname, type, course, matric_id, username, semester, timetable_group, password) lecusers (id, id) lecturers (id, email, department, phone, name, passport, qualification ) Full Dependency

3. users – courses (1 : M) UNF users (fullname, type, course, matric_id, username, semester, timetable_group, password, id {id, course_code, semester, course, lecturer, class, year}) Un-Normalized form 1NF users (id, fullname, type, course, matric_id, username, semester, timetable_group, password) courses (id, course_code, semester, course, lecturer, class, year) Partial Dependency (Primary key determines a non-key) 2NF users (id, fullname, type, course, matric_id, username, semester, timetable_group, password) cousers (id, id) courses (id, course_code, semester, course, lecturer, class, year) Transitive Dependency (Non-key Determines a Non-key) 3NF users (id, fullname, type, course, matric_id, username, semester, timetable_group, password) cousers (id, id) courses (id, course_code, semester, course, lecturer, class, year) Full Dependency

4. users – academic_year (1 : M) UNF users (id, fullname, type, course, matric_id, username, semester, timetable_group, password {id, year, semester, course}) Un-Normalized form 1NF users (id, fullname, type, course, matric_id, username, semester, timetable_group, password) academic_year(id, year, semester, course id) Partial Dependency (Primary key Determines a non-key) 2NF users (id, fullname, type, course, matric_id, username, semester, timetable_group, password) acausers (id, id) academic_year(id, year, semester, course id) Transitive Dependency (Non-key Determines a Non-key) 3NF users (id, fullname, type, course, matric_id, username, semester, timetable_group, password) acausers (id, id) academic_year(id, year, semester, course id) Full Dependency

5. users – timetable (1 : M) UNF users (id, fullname, type, course, matric_id, username, semester, timetable_group, password {id, academic_year, m1, t1, w1, th1, f1, s1, mv1, tv1, wv1, thv1, fv1, sv2, mg1, tg1, wg1, thg1, fg1, sag1}) Un-Normalized form 1NF users (id, fullname, type, course, matric_id, username, semester, timetable_group, password) timetable (id, academic_year, m1, t1, w1, th1, f1, s1, mv1, tv1, wv1, thv1, fv1, sv2, mg1, tg1, wg1, thg1, fg1, sag1) Partial Dependency (Primary key determines a Non-key) 2NF users (id, fullname, type, course, matric_id, username, semester, timetable_group, password) academicusers (id, id) timetable (id, academic_year, m1, t1, w1, th1, f1, s1, mv1, tv1, wv1, thv1, fv1, sv2, mg1, tg1, wg1, thg1, fg1, sag1) Transitive Dependency (Non-key Determines a Non-key) 3NF users (id, fullname, type, course, matric_id, username, semester, timetable_group, password) academicusers (id, id) timetable (id, academic_year, m1, t1, w1, th1, f1, s1, mv1, tv1, wv1, thv1, fv1, sv2, mg1, tg1, wg1, thg1, fg1, sag1) Full Dependency

4.4.2 LOGICAL DATA MODEL

venue venue capacity id users fullname course type matric_id username semester timetable_group password id lecturers id name email passport department qualification phone t1
Academic_year
m1 timetable w1 th1 mv1 f1 s1 tv1 wv1 thv1 fv1 sv1 mg1 tg1 wg1 thg1 fgv1 sag1 id
Creates
courses id course
Course_code
semester lecturer year class Adds academic_year semester course id year venue venue capacity id users fullname course type matric_id username semester timetable_group password id lecturers id name email passport department qualification phone t1
Academic_year
m1 timetable w1 th1 mv1 f1 s1 tv1 wv1 thv1 fv1 sv1 mg1 tg1 wg1 thg1 fgv1 sag1 id
Creates
courses id course
Course_code
semester lecturer year class Adds academic_year semester course id year Adds
Adds
Adds
Adds

4.4.2 PHYSICAL DATA MODEL users
(id int (11),
Username Varchar (200),
Password Varchar (200),
Type Varchar (200),
Matric_id Varchar(200),
Fullname Varchar(200),
Course Varchar (5),
Year int (11),
Semester int(11);
PRIMARY KEY (id); venue (venue text ();
Capacity int (11);
PRIMARY KEY (id)); timetable (academic_year text (); m1 text (), t1 text (), w1 text (), th1 text (), f1 text (), s1 text (), mv1 text (), tv1 text (), wv1 text (), thv1 text (), fv1 text (), sv1 text (), mg1 text (), tg1 text (), wg1 text (), thg1 text (), fg1 text (), sag1 text (),
PRIMARY KEY (id));
Lecturers table
(name Varchar (200),
Passport Varchar (200),
Country Varchar (200),
Email Varchar (200),
Department Varchar (200),
Phone Varchar (200),
Qualification Varchar (200),
PRIMARY KEY (id)); courses table
(course text(),
Course_code varchar (200),
Lecturer text()
Year int (11),
Semester int (11),
Class varchar (200),
PRIMARY KEY (id));
Academic_year
year varchar (200), semester varchra (200), course varchar (50),
PRIMARY KEY (id));

4.5 NAVIGATIONAL CHART
The navigational chart of the proposed system “Legenda Online Student Time Table System” shows the navigations between pages (i.e. how users navigate and move to other pages easily). Navigational chart sometimes referred to as nautical charts essential tool for sailors. Navigational chart is a process of monitoring and controlling the movements of craft or vehicle (objects) from one place to another. Note: your navigation should always appear in every page of your site or standalone system and the basic structure should be same throughout the site. The purpose of Navigational chart is to help the readers get where they want to go easily, it also strives to make sure that users understand the system “Legenda Online Student Time Table System’. However, with the aid of navigational chart, the proposed system will be simple, and easy to interact with. The navigational chart of the proposed system “Legenda Online Student Time Table System” will be shown below:-

Login
Start
Forget Password
Home Page
Home
About Us
Help
Contact Us
Student
Administrator
Profile
View Timetable
View Courses
Logout
Save/Download Timetable
Profile
Courses
Student
Academic Year
Lecturer
Logout
Search
Add Course
View Timetable
Create Timetable
Upload Timetable
Save Timetable
Login
Start
Forget Password
Home Page
Home
About Us
Help
Contact Us
Student
Administrator
Profile
View Timetable
View Courses
Logout
Save/Download Timetable
Profile
Courses
Student
Academic Year
Lecturer
Logout
Search
Add Course
View Timetable
Create Timetable
Upload Timetable
Save Timetable
4.5.1 NAVIGATIONAL CHART

Figure4. 10: Navigational Chart
Figure4. 10: Navigational Chart

4.6 FLOW CHART
The flow chart of the proposed system “Legenda Online Student Time Table System” shows the users of the system the processes that are involved, directions and the arrows that link the processes. A flow chart is a graphical or symbolic representation of a process. Flow charts are linked with arrows showing all the processes of flow direction. However, flow chart is a diagram that shows the steps in a process. Basic flow charts are easy, simple and interesting to create. The purpose of creating flow chart is to explain how the system works with the aid of a diagram, visually display the sequence of activities in a process, detailed explanation of how the system works with the aid of diagram, and it also helps in designing and documenting complicated and complex systems. The flow chart of the proposed system will be shown below:-

Lecturer#19
Login#7
Start#0
Forget Password#2
Home Page#1
Home#3
About Us#4
Contact Us#5
Help#6
Student#8
Administrator#9
Profile#10
View Timetable#11
View Courses#12
Save/Download Timetable#13
Logout#14
Profile#15
Courses#16
Student#18
Academic Year#20
Logout#21
Search#22
Add Course#17
View Timetable#23
Create Timetable#24
Upload Timetable#25
Save Timetable#26
Lecturer#19
Login#7
Start#0
Forget Password#2
Home Page#1
Home#3
About Us#4
Contact Us#5
Help#6
Student#8
Administrator#9
Profile#10
View Timetable#11
View Courses#12
Save/Download Timetable#13
Logout#14
Profile#15
Courses#16
Student#18
Academic Year#20
Logout#21
Search#22
Add Course#17
View Timetable#23
Create Timetable#24
Upload Timetable#25
Save Timetable#26
4.6.1 FLOW CHART

Figure4. 11: Flow Chart
Figure4. 11: Flow Chart

Table4. 6: Flow Chart Description Table S/N | MODULE NAME | BRIEF DESCRIPTION | 0 | Start | Getting system to start | 1 | Home Page | This is the Home page of the system | 2 | Change password | Enable Student to recover or Change forgotten password | 3 | Home | This module will quickly return users to the home from other pages of the system | 4 | About Us | This module tells the University i.e. Legenda Education Group | 5 | Contact Us | This module enables Visitors to easily contact Legenda Via email address, fax or phone number. | 6 | Help | This module guides the student if they face any difficulties in the system. | 7 | Login | This module allows Students and Administrators to Login to the system (i.e. to say by entering user name and password) | 8 | Students | This module Students login to Legenda Online Student Time Table System. | 9 | Administrator | This module enables Administrator Login to the system | 10 | Profile | This module Student to enter profile | 11 | View Timetable | This module allows Students to View Timetable | 12 | View Course | This module allows Students to View Courses | 13 | Save/Download Timetable | This module allows Students to Save or download lecture timetable | 14 | Logout | This module allows users to exit the system | 15 | MyProfile | This module Administrator to view Profile | 16 | Courses | This Module allows Administrator to add Course to the system | 17 | Add Course | This module allows Administrator to add course to the system | 18 | Student | This module allows Administrator to Register Student to the system | 19 | Lecturer | This Module Allows Administrator to Register Lecturer in to the system | 20 | Academic Year | This module allows Administrator to View Courses Added | 21 | Search | This Module Allows administrator to search Users in the system | 22 | View Timetable | This module allows Administrator to View Timetable created | 23 | Create Timetable | This Module allows Administrator to create Timetable for students | 24 | Upload Timetable | This module allows Administrator to Upload the student time table | 25 | Save Timetable | This Module allows Administrator to Save Timetable in to the system | 26 | Logout/End | This ends the activities and takes administrator to the Home page of Legenda Online Student Timetable System |

4.7 CONCLUSION
In conclusion, the author shows the results of the questionnaires and their reports, interview reports, requirement analysis which includes functional and non-functional requirements (System and user requirements). The hardware requirements, software requirement and the network requirements are conducted in this phase. The functional of the system and its entire actor where described in details and their functions, the non-functional requirements includes the security aspect of the system, usability, understandability, reliability and maintainability of Legenda Online Student Time Table System after delivery to its users.
Moreover, in the up-coming chapter (i.e. chapter 5) the use cases of Legenda Online Student Time Table System will be shown, the use case specifications and description, sequence diagrams, class diagrams, collaboration diagram, deployment diagram and activity diagram respectively. All of the modeling tools will be shown in chapter 5 and their explanation because it will give the author a clear picture of the systems design, interface and the graphical user interface of the system.

CHAPTER 5
DESIGN
5.1 INTRODUCTION
This chapter is the design and last chapter of this research work. Use case diagram, class diagram, activity diagram, and sequence diagram of the proposed system “Legenda Online Student Time Table System”. However, the story board of the proposed system will be covered in this chapter as well. Design chapter allows the author to give a clear picture of what the system will be like and going about building the system.
5.2 USE CASE
A use case is a methodology used in system analysis to identify, clarify and organize system requirement, the interaction between systems and users (actors) in a particular environment is called use case (Searchsoftwarequality.Techtarget, 2011). A use case describes a sequence of interactions between users and website, without specifying the user interface (Usability, 2011). According to Bittner, Spence (2003), a use case helps to create the understanding and awareness of the project team understanding the functions that the system must provide for its stake holder (users). A use case plays a vital role for the analyst (author) which knows the requirement of the system to provide good and better solutions. Rosenberg, Stephens (2007) said that; A use case can be used to create a set of behavioral requirements (use cases) that can help the author creates high level, preliminary design. Thus, use cases describe the way in which users interact with the system and the way the system responds. Actors are always mentioned where ever a use case exists. Actors represent the people or things that interact in some way or directly with the computer system or software. Though, actors are outside the system. Actors have a name and a short description. However, the actors are associated with the use cases with which they interact with. The use case diagram serves as an overview or the summary of the system. Rosenberg, Stephens (2007) outlines ten (10) guide lines to do an effective and correct use case diagram which will be listed below:-

Table5. 1: The Use Case Diagram Guide Lines USE CASE DIAGRAM GUIDE LINES | * Write your use case using a noun-verb phrase sentence structure. * Identify who is going to be using the website (or other piece of software). * Pick one of those actors. * Define what that actor wants to do on the website. Each thing the actor does on the website becomes a scenario of use. * For each scenario of use, decide on the normal course of events when that actor is using the site. * Describe the basic course in the description for the scenario of use. Describe it in terms of what the actor does and what the system does in response that the actor should be aware of. * When the basic course is described, consider alternate courses of events and add those to “extend” the scenario of use. * Look for commonalities among the scenarios of use. Extract these and note them as common course scenarios of use. * Repeat the steps 2 through 7 for all other actors. * The results will give you a basis for deciding what the user interface design should be like and what needs it will have to satisfy. |

No | Table5. 2: Functions of the system
Table5. 2: Functions of the system
Requirements/Functions | Requirement Description | Priority | 1 | Log In | This function would enable the registered user to login sign in into the system | M | 2 | Logout | This function would enable the registered users to logout of the system | | 3 | Add Student | This function would enable an Administrator Add student into the system | M | 4 | Add Lecturer | This function would enable an Administrator Add Lecturer into the system | M | 5 | My Profile | This enables Administrator and Students to view their Profile | M | 6 | Add Course | This function allows Administrator to Add a course in the system | M | 7 | Edit Course | This function allows Administrator to Edit course in the system | M | 8 | Delete Course | this function allows the Administrator to Delete Course in the system | M | 9 | Edit Lecturer | This function allows the Administrator to Edit Lecturer in the system | O | 10 | Delete Lecturer | This function would enable the administrator to delete Lecturer from the database | M | 11 | Add Venue | This function allow Administrator to Add Venue in the system | M | 12 | Edit Venue | This function allows Administrator to Edit Venue in the system | M | 13 | Delete Venue | This function allows Administrator to Delete Venue from the system | O | 14 | Academic Year | This function will enable the Administrator to View the students time table according to department e.g. SE or BIS | O | 15 | View Timetable | This function allows Administrator to view timetable in the system | O | 16 | Create Timetable | This function will enable the Administrator to Create Timetable for students | O | 17 | Delete Timetable | This function will enable Administrator to Delete Timetable in the system | O | 18 | Print Timetable | This function enables the Administrator to Print Timetable in the system | M | 19 | View Details | This function allows Students to view their details | O | 20 | Download Timetable | This function will allow Students to Download Timetable | O | 21 | Upload Timetable | This function will allow Administrator to Upload Timetable | M | 22 | Home | This function will allows Students, Lecturers and Administrator to view Home page of the system | O | 23 | About Us | This function allows all actors to view about the system | O | 24 | Contact Us | This function allows all actors to view contact us details | O | 25 | Help | This function will allow Users to interact with the system | O | 26 | Forget Password | This function will allow students to change passwordM = MANDATORY O=OPTIONAL | O |

Legenda Online Student Time Table System
Legenda Online Student Time Table System

Figure5. 1: Use case of Legenda Online Student Time Table System

5.3 REQUIREMENT DESCRIPTION TABLE
Table5. 3: Login Use Case Description | Function Name | LOGIN | Actors | Administrator/Student | Description | This use case will allow Administrator and students to Log In to the system. | Primary Actors | Registered Administrator and Student. | Output | Nil | Pre-Condition | Administrator and students must be registered. | Post-Condition | Users must be logged in to the system. | Constraints | User name and password must be valid. | FLOW OF EVENTS | Basic Flow | * The use case begins when user runs the website or system (index). * The user must key in user name * User keys in password. * User clicks on Login Button. * System would verify information * System must redirect the users to their profile | Alternative Flow | * A1: N/A | Exceptional Flow | * E1: Please enter a username and password. Please wait * E2: that user does not exist. Please wait * E3: Incorrect username and password |

5.3.1 ADD LECTURER
Table5. 4: ADD LECTURER Use case Description | Function Name | Add Lecturer | Actor | Administrator | Description | This use case will allow administrator to register students to the system. | Primary Actors | Administrator. | Output | Nil | Pre-Condition | Nil | Post-Condition | Administrator must be logged in to the system. | Constraints | Administrator must be logged in the system | FLOW OF EVENTS | Basic Flow | * The use case begins when Administrator clicks on Lecturer button on the home page (index). * System displays Add New Lecturer form. * The administrator keys in passport. * The administrator must select country. * The administrator must key in email address. * The administrator must key in phone number. * The administrator will key in qualification. * Administrator clicks on Create Button. * System displays “Lecturer successfully added. Click here to refresh”. | Alternative Flow | * A2: Clear Field | Exceptional Flow | * E1: Fill in the details. Please wait |

5.3.2 ADD STUDENT
Table5. 5: ADD STUDENT Use Case Description | Function Name | Add Student | Actor | Administrator | Description | This use case will allow administrator to Add Students into the system | Primary Actors | Administrator. | Output | Nil | Pre-Condition | Student must be enrolled in Legenda Education Group. | Post-Condition | Administrator must be logged in to the system. | Constraints | Student must be enrolled in Legenda Education Group. | FLOW OF EVENTS | Basic Flow | * The use case begins when Administrator clicks on Student button on My Profile page (index). * System displays Student form. * The administrator keys in first name. * The administrator keys in last name. * The administrator keys in UEL ID * Administrator keys in Password * The administrator re-enters Password * The administrator keys in Email * The administrator keys in Department * The administrator selects Sex * The administrator selects Country * Administrator clicks on Create Button * System displays “Successfully added”. | Alternative Flow | * A1: Cancel | Exceptional Flow | * E1: Fill in all details. Please wait * E2: Email Address is not entered correctly. Please wait |

5.4 CLASS DIAGRAM
Class diagram are the foundation of object oriented analysis and design. A class diagram shows the classes of the system and their interrelationships (e.g. Inheritance, Aggregation and Association) and the “operations” and “attributes” of the class (Agilemodeling, 2011). Class diagram is used for both conceptual or domain modeling and detailed design. A class is simply a rectangle divided into three compartments that is; the first compartment is the class, the second/middle compartment is the attribute (variables) and the third/last compartment is the operations (member functions). The diagram below describes more on a class, attributes and functions. Class Attributes Operations
Note: A class must be a Verb Noun Phrase
Class diagram consists of Composition, Association or Aggregation, Inheritance and Dependency relationship respectively.
5.4.1 ASSOCIATION
An association is a relationship between two classifiers, such as classes or use cases that describe the relationship and the rules that govern the relationship (Publib, 2005).
5.4.2 INHERITANCE/GENERALISATION
In Uml, generalization is similar to the object oriented concept of sub classing; it shows the relationship between a general case and one with more specific cases (Vtc, 2011).
5.4.3 DEPENDENCY Dependency relationship indicates that a change to class (supplier) might change in the other classes (client). The supplier is independent because a change in the consumer does not affect the supplier.
However, Rosenberg, Stephens (2007) outlines ten (10) guide lines to do an effective and correct Class diagram which will be listed below:-
Table5. 6: Class Diagram Guide Lines CLASS DIAGRAM GUIDE LINE | * Do not put screens and other GUI (Graphical User Interface) classes to your model * Do not expect your final class diagram to precisely match your domain model, but it must have resemblance to the classes. * Do your initial domain models before you write your use cases in order to lessen or avoid name ambiguity. * Use domain model as a project glossary. * Do not confuse an object (that represents a single inheritance with a database model * Do not mistake your domain model for a data model. * Organize your classes around key abstraction in the problem domain. * Limit your initial domain modeling effort to a couple of hours. * Use generalization (is-a) and aggregation (has-a) relationship to show how the objects relate to one another. * Focus on real world objects. |

The diagram below shows the class diagram of the proposed system (Legenda Online Student Time Table System),
Figure5. 2: Class Diagram
Figure5. 2: Class Diagram
LEGENDA ONLINE STUDENT TIME TABLE CLASS DIAGRAM

5.5 SEQUENCE DIAGRAM
According to Larman (2002), a sequence diagram illustrates the interactions of objects in a kind of fence format, whereby, each object is added to the right hand side. The sequence diagram includes actor, boundary, entity and control that show the sequence of the activities used in achieving a goal (e.g. Login, Delete User etc). The strength of sequence diagram is that, it shows clearly the sequence or time ordering messages and it also uses simple notations. Sequence diagram shows the vibrant collaboration of objects in a sequential order (Unhelkar, 2005). Hence, sequence diagram shows not only the behavior of objects but also how the objects and actors are involved in their behaviors. Sequence diagram shows the message flow exactly between the actor and the system. However, sequence diagram is more dynamic compared to activity diagram, collaboration diagram and the use case diagram. The term interaction diagram generally involves the sequence diagram and the collaboration diagram respectively. Typically, a sequence diagram shows the behaviors of objects in a given scenario (Fowler, 2004). Rosenberg, Stephens (2007) outlines ten (10) Guide lines to developing or designing Sequence diagram which will be shown in table 2.0 below:-
Table 5.7: Sequence Diagram Guide Lines SEQUENCE DIAGRAM GUIDE LINES | * Understand why you draw a sequence diagram. * Draw sequence diagram for every use case. * Start sequence diagram from the boundary classes, entity classes, actors and use case text. * Use the sequence diagram to show the behavior of the use case. * Make sure your use case text maps to the message being passed on the sequence diagram. Line up the text and message arrow. * Don’t spend too much time worrying about focus of control. * Assign operations to classes while drawing message. * Review your class diagrams frequently while you are assigning operations to classes. * Pre-factor your design on sequence diagram before coding. * Clean up the static mode before proceeding to the CDR. |

5.7.1 SEQUNCE DIAGRAM OF LOGIN
Figure5. 3: Sequence Diagram of Login

5.7.2 SEQUENCE DIAGRAM OF ADD LECTURER
Figure5. 4: Sequence Diagram of Register Lecturer
Figure5. 4: Sequence Diagram of Register Lecturer

5.7.3 SEQUENCE DIAGRAM OF CREATE TIME TABLE

Figure5. 5: Sequence Diagram of Create Timetable
Figure5. 5: Sequence Diagram of Create Timetable

5.6 COLLABORATION DIAGRAM
A collaboration diagram also called a communication or interaction diagram is an illustration of the relationships and interactions among software objects in Unified modeling language Interaction diagram, like sequence diagram, it shows how objects interact over the course of time. However, after showing the sequence of events by layout diagram, collaboration diagram shows the sequence by numbering the messages on the diagram (VISUALCASE, 2011). The collaboration diagram of the proposed system (Legenda Online Student Time Table System) will be shown below:-
5.6.1 COLLABORATION DIAGRM OF CREATE TIME TABLE
Figure5. 6: Collaboration Diagram of Create Time Table
Figure5. 6: Collaboration Diagram of Create Time Table

5.6.2 COLLABORATION DIAGRAM OF ADD LECTURER

Figure5. 7: Collaboration Diagram of ADD LECTURER

5.6.3 COLLABORATION DIAGRAM OF ADD VENUE
Figure5. 8: Collaboration Diagram of ADD VENUE
Figure5. 8: Collaboration Diagram of ADD VENUE

5.7 ACTIVITY DIAGRAM
Activity diagram is a simple and intuitive illustration of what happens in a workflow, what activities can be done in parallel and whether there are alternative paths through the work flow (IBM, 2011). Activity diagram consist of Note, Anchor to note item, State, Activity start state, End state, State transition, Transition to self, Horizontal synchronization, Vertical synchronization, Decision and Swim lane respectively. Below are the activity diagrams of the proposed system (Legenda Online Student Time Table System):-

5.7.1 ACTIVITY DIAGRAM OF ADD COURSES

Figure5. 9: Activity Diagram of Add Courses

5.7.2 ACADEMIC YEAR ACTIVITY DIAGRAM

Figure5. 10: Academic year Activity Diagram

5.7.3 CHANGE PASSWORD ACTIVITY DIAGRAM

Figure5. 11: Change Password Activity Diagram
Figure5. 11: Change Password Activity Diagram

5.7.4 CREATE TIME TABLE ACTIVITY

Figure5. 12: Create Time Table Activity Diagram
Figure5. 12: Create Time Table Activity Diagram

5.8 STATE CHART DIAGRAM
As the name suggests, a state chart describes different states of a component in a system. The states are specific to a component or object (Tutorialspoints, 2011). It shows the state of objects e.g. a lifter have five states which are; idle state, open, close, start and stop respectively. However, state chart diagram shows the behavior of classes to external stimuli (Smartdraw, 2011). State chart models the dynamic flow of control from state to state with the system. A state chart diagram comprises of the following;
5.8.1 A STATE
A state refers to situations during the life of an object.
5.8.2 TRANSITION Transition is a solid arrow which represents the path or way different state of an object.
5.8.3 INITIAL STATE A black circle followed by an arrow to represent object at initial stage.
5.8.4 FINAL STATE
An arrow pointing at a big filled black and white circle nested inside other circles that represent final stage.
5.8.5 SYNCHRONIZATION
It represents synchronization of control. Below are the State chart diagrams of the proposed system (Legenda Online Student Time Table System):-

5.8.1 ADD LECTURER STATE CHAT

Figure5. 13: Add Lecturer State Chart Diagram
Figure5. 13: Add Lecturer State Chart Diagram

5.8.2 CREATE TIMIE TABLE STATE CHART DIGRAM

Figure5. 14" Create Timetable Activity Diagram
Figure5. 14" Create Timetable Activity Diagram

5.8.3 ADD VENUE STATE CHART DIAGRAM

Figure5. 15: Add Venue Activity Diagram

5.9 STORY BOARD
A story board is sequential description of events. It is an outline that is used in the planning of a television show, movie, commercials and websites. Storyboards are graphical organizers such as a series of illustrations or images displayed e.g. motion pictures, animation etc. Story board is used to describe and present flow of events in an easy manner. It also describes in detail how the end product (system) would be.
The diagrams below are the story board of the proposed system (Legenda Online Student Time Table System):-

5.9.1 LOGIN Title #1: Legenda Online Student Time Table System

Logo
Home
Submit
Username
Password
Forget password
Footer
About
SLIDING PICTURE
Title #1: Legenda Online Student Time Table System

Logo
Home
Submit
Username
Password
Forget password
Footer
About
SLIDING PICTURE
Contact Info.
Contact Info.
Help
Help
Courses
Courses |

Figure5. 16: Login storyboard

Logout
Logout
Academic Year
Academic Year
Venues
Venues
Student
Student
Lecturers
Lecturers
Courses
Courses
My Profile
My Profile
Logo
Logo
Title #1: Legenda Online Student Time Table System
Title #1: Legenda Online Student Time Table System
Footer
Footer |
5.9.2 ADMINISTRATOR PAGE

Figure5. 17: Administrator Storyboard

5.9.3 View Courses Logo
Logo
Title #1: Legenda Online Student Time Table System
Title #1: Legenda Online Student Time Table System
Courses
Courses

Add Course
Add Course Select a course by the left to preview here
Select a course by the left to preview here
Picture
Picture
Footer
Footer |

Figure5. 18: View Courses Story Board

5.9.4 Add Courses Logo
Logo
Title #1: Legenda Online Student Time Table System
Title #1: Legenda Online Student Time Table System
Courses
Courses

Add Course Button
Add Course Button
Create Button
Create Button
Add New Course
Add New Course
Text Box
Text Box
Title
Title
Dropdown Box
Dropdown Box
Lecturer
Lecturer Dropdown Box
Dropdown Box
Dropdown Box
Dropdown Box
Dropdown Box
Dropdown Box
Text Box
Text Box
Class
Class
Semester
Semester
Year
Year
Course Code
Course Code
Footer
Footer | Figure5. 19: Add Course Storyboard

5.9.5 Edit Courses Logo
Logo
Title #1: Legenda Online Student Time Table System
Title #1: Legenda Online Student Time Table System
Courses
Courses

Delete Button
Delete Button
Save Button
Save Button
Information System Information System

Add Course Button
Add Course Button
Text Box
Text Box
Title
Title
Dropdown Box
Dropdown Box
Lecturer
Lecturer Dropdown Box
Dropdown Box
Dropdown Box
Dropdown Box
Dropdown Box
Dropdown Box
Text Box
Text Box
Class
Class
Semester
Semester
Year
Year
Course Code
Course Code
Footer
Footer | Figure5. 20: Add Course Storyboard

5.9.6 Delete Courses Logo
Logo
Title #1: Legenda Online Student Time Table System
Title #1: Legenda Online Student Time Table System
Courses
Courses
Edit Button
Edit Button
Delete Button
Delete Button

Information System Information System

Text Box
Text Box
Lecturer
Lecturer
Course Code
Course Code
Text Box
Text Box Text (Link)
Text (Link)
Text
Text
Class
Class
Semester
Semester
Year
Year
Text Box
Text Box
Text Box
Text Box
Text Box
Text Box
Footer
Footer |

Figure5. 21: Delete Course Storyboard

5.9.7 ADD LECTURER Logo
Logo
Title #1: Legenda Online Student Time Table System
Title #1: Legenda Online Student Time Table System
Courses
Courses
Create Button
Create Button

Add Course Button
Add Course Button
Text Box
Text Box
Name
Name
Passport
Passport
Text Box
Text Box Text
Text
Qualification
Qualification
Phone
Phone
Email
Email
Country
Country
Drop Down
Drop Down
Text Box
Text Box
Text Box
Text Box
Footer
Footer | Figure5. 22: Add Lecturer Storyboard

5.9.8 EDIT LECTURER Logo
Logo
Title #1: Legenda Online Student Time Table System
Title #1: Legenda Online Student Time Table System
Lecturers
Lecturers
Edit Button
Edit Button
Delete Button
Delete Button

Save Button Save Button

Text Box
Text Box
Lecturer
Lecturer
Passport
Passport
Text Box
Text Box Text (Link)
Text (Link)
Qualification
Qualification
Phone
Phone
Email
Email
Country
Country
Text Box
Text Box
Text Box
Text Box
Text Box
Text Box
Footer
Footer |

Figure5. 23: Edit Lecturer Story Board

5.9.9 DELETE LECTURER Logo
Logo
Title #1: Legenda Online Student Time Table System
Title #1: Legenda Online Student Time Table System
Lecturers
Lecturers
Edit Button
Edit Button
Delete Button
Delete Button

Save Button Save Button

Text Box
Text Box
Lecturer
Lecturer
Passport
Passport
Text Box
Text Box Text (Link)
Text (Link)
Qualification
Qualification
Phone
Phone
Email
Email
Country
Country
Text Box
Text Box
Text Box
Text Box
Text Box
Text Box
Footer
Footer | Figure5. 24: Delete Lecturer Story Board

5.9.9 CREATE VENUE

Logo
Logo
Title #1: Legenda Online Student Time Table System
Title #1: Legenda Online Student Time Table System
Venues
Venues
Create Button
Create Button

Save Button Save Button

Text Box
Text Box
Venue
Venue
Capacity
Capacity
Drop Down
Drop Down Footer
Footer
| Figure5. 25: Create Venue Storyboard

5.9.10 EDIT VENUE Logo
Logo
Title #1: Legenda Online Student Time Table System
Title #1: Legenda Online Student Time Table System
Venues
Venues
Edit Button
Edit Button

Delete Button Delete Button

Text Box
Text Box
Venue
Venue
Capacity
Capacity
Drop Down
Drop Down Footer
Footer
|

Figure5. 26: Edit Venue Storyboard

5.9.11 DELETE VENUE

Logo
Logo
Title #1: Legenda Online Student Time Table System
Title #1: Legenda Online Student Time Table System
Venues
Venues
Delete Button Delete Button Edit Button
Edit Button

Text Box
Text Box
Venue
Venue
Capacity
Capacity
Drop Down
Drop Down Footer
Footer
| Figure5. 27: Delete Venue Storyboard

5.10 DEPLOYMENT DIAGRAM
The Collaboration diagram of the proposed system “Legenda Online Student Time Table System” is shown below with the aid of a diagram and how the proposed system supports the hardware and Operating System (i.e. the software). Deployment diagram depicts a static view of the run time configuration of processing node and the components that on those nodes (Agilemodeling, 2011). Deployment diagram shows the hardware for your system, the software that is installed on that hardware and the middle ware (e.g. if you buy a new printer, you must installed the printer’s driver before you can connect It to your computer system, so that driver acts as a middle ware of your system). The most important use of deployment diagram is to explore the architecture of the system showing how the hardware and software components work together. Some of the notations of deployment diagram include the following;
5.10.1 PROCESSOR NODE
This node is used to show a system or software in used (i.e. the type of operating system that the system will run on).
5.10.2 DEVICE NODE
This node is used to either represent a device of a system or an interface (i.e. the interface of the proposed system and how it will work). However, the deployment diagram of the proposed system “Legenda Online Student Time Table System” will be shown below with the aid of a diagram:-

Figure5. 28: Deployment Diagram

5.11 CONCLUSION
In this chapter, all the UML (Unified Modeling Language) are covered. Use case of the whole system, sequence diagram, class diagram, deployment diagram, activity diagram and state chart diagram is covered in this chapter as well. The story board of the system is covered in this chapter as well.
In the upcoming chapter (I.e. chapter 6), the summary of all chapters, findings and results, reflections, problems encountered, lesson learnt and future work of the Legenda Online Student Time Table System will be discussed in details.

CHAPTER 6
IMPLEMENTATION
6.1 INTRODUCTION
Implementation is the final stage of the software or system development life cycle (SDLC). This phase usually gets the most attention for it is the most expensive and the largest phase in the software development process. There are three steps in this phase; system construction is the first step, the system will be tested so that it performs as designed. More so, most organizations spend a lot of time and attention in testing, then writing the program in the first place. Installation where by the old system is turned off and the new system is turned on (Barbara, 2008) and support plan includes a formal or informal post-implementation review as well as the systematic way for installing major and minor changes needed for the system.
Moreover, in this development phase, the author will implement the GUI (Graphical User Interface) of the system, implement the database, analyze and describe the hardware and software requirement of the system, system implementation, interface visibility, consistent interface, color used and the system architecture (i.e. 3-tier architecture).
6.2 DEVELOPMENT ENVIRONMENT
Development environment is an environment that is used for programming or software development process. Development environment is a set of processes and tools that are used to develop source code or program (Techopedia, 2012). The term is used IDE (Integrated development environment) that is to say, a software development tools that is used to write, build, test and debug a program.
However, the author will discuss about the hardware and software requirements of the proposed system (i.e. Legenda Online Student Time Table System) in details below:-

6.2.1 HARDWARE DEVELOPMENT ENVIRONMENT
Hardware requirement is the hardware (physical component of computer) of the computer systems. Bhardwaj (2000) states that; hardware requirement determines and tells the author what hardware is required for the proposed system. For example, the hard disk size, the RAM size etc. The table below will describe all the hardware requirements of Legenda Online Student Time Table System.
Table6. 1: Hardware Development Requirement HARDWARE | MINIMUM | RECOMMENDED | DESCRIPTION | * Random access memory (RAM) | * 1GB RAM | * 2GB RAM or above | * Used to save temporary data. It is also used to when running large programs to speed up system’s performance | * Hard Disk | * 80GB | * 320GB or above | * It is a permanent mode of storage in the computer system. The operating system of the computer system is saved in the hard disk | * Mouse | * Laser mouse | * Optical mouse | * The pointer device that will be used in the proposed system | * Processor | * Pentium 4 processor | * Intel dual core processor | * It is a logical circulatory that responds to and processes the basic instructions that drive a computer system | * Keyboard | * Dvorak Simplified Keyboard | * QWERTY keyboard | * This is a standard keyboard that will be used for the proposed system | * Monitor | * 15” inch monitor | * 17-21 inch screen | * This is used to view or display in the proposed system | * Scanner | * Flatbed scanner | * Ngenuity 9125DC | * It is used to scan documents faster and easier | * Printer | * Inkjet printer | * Laser printer | * It is an output device that produces text and graphics on paper | 6.2.2 SOFTWARE DEVELOPMENT REQUIREMENT
According to Richard (2007), software requirement process is the first step in most software development process because; it allows the development team to determine if the system can be built and delivered in the stipulated time of delivery. Thus, software requirement helps in knowing how to build the proposed system (Legenda Online Student Time Table System) without further delay. The table below shows the software requirements in details

Table6. 2: software development environment SOFTWARE | MINIMUM | RECOMMENDED | DESCRIPTION | * Database | * MySQL Server | * MySQL Server R2 | * MySQL is a server software that is used to store record in an information system | * Windows Operating System (OS) | * Windows Xp | * Windows vista or windows 7 | * This is the operating system that the system will run on | * Mac OS | * Mac Os | * Mac Os X | * This is a Linux operating system that the system can be accessed on. | * Design Tool | * Netbeans | * Netbeans | * A software tool used to create and edit sophisticated websites | * Microsoft office | * Microsoft office 2003 | * Microsoft office 2007/2010 | * Software package | * UML tool | * Rational Rose Enterprise Edition 98 | * Rational Rose Enterprise Edition 2003 | * Rational rose is a modeling tools that is used to create use case, class diagram, activity diagram etc. | * Programming Language | * Php | * Php | * Php is a server-side language that the compiler understands when creating and running sophisticated and simple WebPages. E.g. running website in Google chrome | * WAMP Server | * WAMP Server Version 2.0 | * WAMP Server Version 5.0 | * WAMP Server is a server site tool that is used to connect web pages to database and run on the web browsers | * Anti-virus | * MacAfee Anti-virus 2010 | * MacAfee Anti-virus 2012 | * A virus detecting and removal tool. It also warns against malware and Trojans | 6.2.3 NETWORK DEVELOPMENT REQUIREMENT
Network requirement defines the network tool need in order to use the system. The network requirements include all the requirements that must be used to connect the proposed system (i.e. Legenda Online Student Time Table System) to the internet. The network requirement of the proposed system includes the following:-
Table6. 3: Network Development Requirement SOFTWARE | MINIMUM | RECOMMENDED | DESCRIPTION | * Switch | * Cisco 8-port Standard 10/100 Network Switch (SD216TUK) | * Cisco 16-port Standard 10/100 Network Switch (SD216TUK) | * It is a computer networking device which will connect network segments | * Bridge | * Cisco Linksys Dual- Band N bridge with 4-port Switch (WES610N) | * Cisco Linksys Dual- Band N bridge with 4-port Switch (WES610N) | * Filters data traffic at a network which is very crucial for the proposed system | * Network card | * D-Link N150mbps Wireless N PCI Adapter Card (DWA-525) | * D-Link N150mbps Wireless N PCI Adapter Card (DWA-525) | * It is an expansion card that enable computer to physically connect LAN (local area network) | * Wireless Modem | * TP-Link N300mbps High Gain Wireless N USB Adapter (TL-WN822N) | * TP-Link N300mbps High Gain Wireless N USB Adapter (TL-WN822N) | * It is a wireless connection to the internet. Thus, It connects to a wireless networks. | * Router | * HuaWei E583X MIFI 3.5G Portable router for Galaxy/Playbook/Ipad E585 E... | * HuaWei E583X MIFI 3.5G Portable router for Galaxy/Playbook/Ipad E585 E... | A device that forwards data packets between telecommunications networks | * Network cable | * RJ45 | * RJ45 | A cable that is used for LAN and WAN connection and can be connected to all computer system is network port | * Server | * HP Proliant DL140 G3 Server (1U rack mount) | * HP Proliant DL140 G3 Server (1U rack mount) | To be used to host Legenda Online Student Time Table |

6.3 SYSTEM IMPLEMENTATION
The system implementation is the process of building and implementing the functions of the system. Legenda Online Student Time Table System’s print screen will be shown below. However, there are certain factors that would be considered in building the implementation of the system. This includes; Interface Visibility, Consistent Interface and the Color used in implementing the system.
6.3.1 INTERFACE VISIBILITY User interface is only valued when the system users interactions achieve their purpose (Vishal, 2011). The elements of user interaction are what users see. Visibility is nothing but how clearly the users “see” the interface and how they feel about it. Online Student Time Table System is built based on the Ten Usability Heuristics principles by Jakob Neilson.
Table6. 4: Usability Heuristics Table USABILITY HEURISTICS | EXPLAINING | * Visibility of System Status | * Legenda Online Student Time Table System keeps users informed about what is going on by providing appropriate feedback and place holder in the textboxes. | * Match Between System and Real World | * The system is built using “simple English grammar” and font-family is very clear to provide information in a natural and logical order. | * User Control and Freedom | * Legenda Online Student Time Table System tells users about where they are and how to exit the system in emergency cases. | * Consistency and Standard | * The system is built using “platform conventions” to have simple English words to make the system easy for users. | * Error Prevention | * The system provides good error messages and allows users to confirm any action they tend to make or took with the aid o Place holder in the text boxes. | * Recognition Rather Than Recall | * The system is built by following K.I.S.S principles (i.e. Keep It Simple and Straight Forward. | * Flexibility and Efficiency of Use | * The system can be used by both novice users and sophisticated users because of its flexibility and efficiency. | * Aesthetic and Minimalistic Design | * Legenda Online Student Time Table System does not contain irrelevant information, thereby keeping the systems design simple. | * Help Users Recognize, Diagnose and recover from errors | * The system contains error messages written in plain English language not Code, that indicates the problem and constructively suggest solution. | * Help and Documentation | * The system has a help function that tells the users what to do and the documentation of the whole system is provided for future upgrade and usage. |

6.3.2 CONSISTENT INTERFACE
Consistency in the interface allows people to transfer their knowledge and skills from one application to another (Developer, 2012). If a User Interface (UI) of a system is not consistent or un-attractive, convoluted or illogical, it can make even a good application or system seem like chore to use. Legenda Online Student Time Table System UI is designed in a simple and logical manner by following the K.I.S.S principles (i.e. to say Keep It Simple and Straight Forward).
6.3.3 SYSTEM COLOR
The system color refers to the range of colors used in designing the system. Choosing the right color is not an easy task because, age matters when providing color to the system. E.g. users above 50 years may need a black and white system due their aging and won’t like a system with much color or very bright color. Again, users between 40-50 years will prefer to use different color than users of 20-30 years of age. Choosing system (i.e. web pages) color depends on the users of the system.
However, Legenda Online Student Time Table System comprises of mainly few color, which will be listed below: * White * Whitesmoke * Dodgerblue * Gainsboro
6.3.4 SYSTEM ARCHITECTURE
Three-tier architecture is popularly known as multi-tier architecture. It consists of 3 tiers that have its own functionalities each. It comprises of data server (business server/client) presentation logic and middle tier server (business rule). Some of the advantages of using 3-tier includes; easy modification and replacement of single tiers without affecting the other tiers. Application can easily be separated (i.e. separating applications and database) there by making it possible for many users to have access concurrently. It is mainly developed to overcome the weakness of two-tier architecture in terms of security, performance, scalability and simplicity. Three-tier architecture is used mainly for web based applications e.g. face book, yahoo etc.
Again, Legenda Online Student Time Table System is going to be implemented using three tier architecture because it is an online system and there is a communication between the client, server and the system’s database concurrently. One of the primary advantages of three-tier architecture is that, as your data storage keep on pilling (adding) up, you can change the way data is stored without affecting your clients (i.e. client are systems that rely on the server to perform activities). The middle layer of the system commonly referred to as the application server, can thus concentrate on centralizing business rule processing. (I.e. to say Business rule processing is the processing of data going to and from clients in a way that is common to all clients). Below is the diagram of three tier architecture:-

Figure6. 1: Three-tier Architecture

6.4 IMPLEMENTATION OF GUI
Below are the lists of Graphical User interface (GUI) of the Legenda Online Student Time Table System. Thus, some of the vital GUI of the system will be displayed below:
6.4.1 Add Course Page

Figure6. 2: GUI and Add New Course
Figure6. 2: GUI and Add New Course

Figure6. 3: HTML and PHP code of Add course
Figure6. 3: HTML and PHP code of Add course
The above code shows the php script and the html tags all together because, the author wants to limit the line of code in the system. The above code is to add course in the course table as well as GET a specific row from the course table. The combo box buttons are created using html. All the text fields and their validations are done in this page. However, certain CSS designs (i.e. cascading style sheet) are called using “<include>” statement and the connection to database as well.

Figure6. 4: Create Timetable Page
Figure6. 4: Create Timetable Page
6.4.2 CREATE TIMETABLE PAGE

Create Timetable Php code
Create Timetable Php code
Figure6. 5: Code for Create Timetable Page
The above php code is to create the lecture timetable for the students by the administrator. The statement if (is set ($_POST[‘create_timetable’])) is used to post each and every field in the database. Each and every dropdown menu has a unique ID in the database and the php script. The administrator can easily choose from the drop down menu, lecture venue and course name. Likewise, when administrator uses the dropdown menu, it calls all the details saved in the database and call the details instantly from the database.

6.4.3 Delete Course PAGE
Figure6. 6: Create Timetable Page
Figure6. 6: Create Timetable Page

Display successful message
Display successful message
Delete Course code
Delete Course code
Figure6. 7: Delete Course Page
Figure6. 7: Delete Course Page
The above delete code starts with the php tag (?php). It is used in the system to delete a specific course by using the foreign key id in the course table the php script i.e. mysql_query ("DELETE FROM courses WHERE id='$fk_id'"); is the delete statement used to delete all the details of a particular row in the Course Table in the Timetable database of Legenda Online Student Time Table System. The echo statement is used to output the either error message or successful message in the course page of the system. The above php code ends with the closing php tag (?>).
6.4.4 VIEW TIMETABLE PAGE
Figure6. 8: GUI of View Timetable Form
Figure6. 8: GUI of View Timetable Form

Figure6. 9: p code to display Time Table
Figure6. 9: p code to display Time Table
The above code is used to select all records in the course table and choosing the specific year and semester and class from the database. The while loop is used to fetch the rows in the course table, all the php codes in the curly bracket are used to call those specific rows from the course table. The echo (display/output) shows the link of course page. More so, the second form is to link to timetable.php in the form, the input type and the php code to echo the foreign key of $FK_id and the closing of php tag.

6.5 DATABASE IMPLEMENTATION
Figure6. 10: Database Implementation
Figure6. 10: Database Implementation

Figure6. 11: Relationship between tables in the database
Figure6. 11: Relationship between tables in the database

The above relationships Diagram shows the Entity Relation Ship Diagram (ERD) of Legenda Online Student Time Table System. The author will describe the relationship between two tables in Legenda Online Student Timetable System. The relationship between Courses and Academic_year is that, the primary key (PK) in the courses table is a foreign key (FK) in the Academic_year table. Foreign key means a primary key (PK) in a table and a non-key in other table. However, all the details in the course table can be easily accessed or called in the Academic_year table. Primary key refers to the unique identifier for the table. However, all the above tables have their own unique primary keys in their tables. 6.5.1 SERVER
XAMPP Server is a server site tool that is used to connect web pages to database and run on the web pages on the web browsers. Xampp is used to connect the web pages of Legenda Online Student Time Table System to the database concurrently. Below is the php code to connect the database server. The figure below is to show the php code that connects the system to the MySQL Database for communication.

Figure6. 12: Php Server Connection Code

The above code <?php is to start the php and tell the server that it’s a php script. The $error shows weather the connection to the MySQL database is successful or not. The $connect is to connect to MySQL using the Localhost, root and password if any or will display error. The mysql_select_db is to select a database according the name given in the quotation “”. The last php tag ?> is to end the php code.

6.6 SUMMARY
This chapter emphasizes on the implementation of Legenda Online Student Time Table System. The aim of this chapter is to implement the above named system, the development environment which comprises of hardware development requirements, software development requirements and network development requirements required for the development of the proposed system is described in details. Moreover, the actual system implementation factors which includes the interface visibility, consistent interface and the color used in building or designing the above named system. The GUI (i.e. Graphical User Interface) of the most vital functions of the system are documented and described as well as the architecture of the system (i.e. three tier architecture).

CHAPTER 7
TESTING

7.1 INTRODUCTION
Testing refers to the process of exercising or evaluating a system or a system’s components by manual or automated means to check, verify and confirm that it satisfies requirements. It also refers to the way or process of executing a system or program with the intention of finding errors. Testing is the implementation phase. The testing will be conducted in this phase; it will include all the types of testing (i.e. unit testing, acceptance testing, integration testing, functional testing and regression testing). Black box and white box testing will also be provided or rather conducted in this phase. Testing is very crucial in any type of system before the delivery of the complete or finished product.
7.2 TEST PLAN
A software test plan is a document describing the testing scope and activities. It is the basis for formally testing any software or product in a project (Softwaretestingfundamentals, 2012). A test plan is a document describing the scope, approach, resources and schedule of intended test activities. However, software testing is the process of analyzing software to identify or detect software bugs (i.e. errors). Software testing is an activity that should be done throughout the whole system development process. The software testing includes verification and validation. Verification (V) is the way of evaluating a system or a component to identify or verify that the system satisfies the conditions at the beginning of the phase. Validation refers to the process of evaluating a system or components during or at the end of the system development process to determine whether it satisfies specified requirements. There major type of testing includes: - * Black box Testing * White Box Testing
However, the white box and black box testing can be further sub-divided in to the following below: - * Unit testing (white box testing) * Integration testing (black box and white box testing) * Functional and system testing (black box testing) * Acceptance testing (black box testing) * Regression testing (black box and white box testing) * Beta testing (black box testing)
However, only three types of testing will be conducted in this work. The type of testing includes, acceptance testing, unit testing and functional resting concurrently.
7.2.1 BLACK BOX TESTING
Black box testing is the kind of testing you can do when you do not have the source code, just the executable code in hand (Everett and McLeod, 2007). Black box testing or functional testing is the type of testing that ignores the internal mechanism of software or components and solely focuses on the output generated to selected outputs and execution (Williams, 2006). Black box testing takes only the input and output of the software without concentrating or emphasizing on the programming side (i.e. to say, the code). The below diagram will shade more light on
Input
Execute Program
Input
Black box Test
Input
Execute Program
Input
Black box Test

Figure7. 1: Black box Testing
Figure7. 1: Black box Testing

(Williams, 2006)
7.2.1.1 FUNCTIONAL TESTING
A functional testing is concerned with testing the specifications or the software components that are subject to testing. It is basically conducted by providing input data to test for expected or required output. The functional testing involves ensuring that the functionalities specified in the requirements specification are achieved. The table below shows the black box testing (functional testing) of the LEGENDA ONLINE STUDENT TIME TABLE SYSTEM
Table7. 1: Black box testing (Functional Testing) Test ID | Description | Input | Actual Result | Expected Result | Status | 1 and 2 | Function Name:LoginPrecondition: User must be registered in the databaseActor:Administrator and Student | Empty Fields (i.e., Username and Password) | Error message “Please Enter a Username & Password. Please wait” | System displays error message “Please Enter a Username & Password” | Pass | | | Correct Username but wrong Password | Error Message “Please Enter a Username & Password. Please wait” | System displays error message “Please Enter a Username & Password” | Pass | | | Incorrect Username but correct Password | Error Message “That user does not exist. Please wait” | System displays error message “That User does not exist. Please wait…” | Pass | | | Correct Username and Password | Successful message “Welcome, Tom!” | System displays successful message “Welcome, Tom!” | Pass | 1 | Function Name:Add CoursePrecondition: Administrator must be registered in the databaseActor:Administrator | Empty fields (i.e., Title and Course Code) | Error message “Fill in all details. Please wait” | System displays error message “Fill in all details. Please wait” | Pass | | | Empty Title but correct Course Code | Error message “Fill in all details. Please wait” | System displays error message “Fill in all details. Please wait” | Pass | | | Correct Title but empty Course Code | Error message “Fill in all details. Please wait” | System displays error message “Fill in all details. Please wait” | Pass | | | Wrong Title (e.g. 111111111111) and correct Course Code | Successful message “Course successfully added. Click here to refresh” | System should display error message “Title cannot be numeric only” | Fail | | | Correct Title but same Course Code (i.e. duplicate course code) | Error message “Course code already exists for another course. Please wait” | System displays error message “Course code already exists for another course. Please wait” | Pass | | | Correct Title and Course Code | Successful message “Course successfully added. Click here to refresh” | System displays successful message “Course successfully added. Click here to refresh” | Pass | 1 | Function Name:Edit CoursePrecondition: Administrator must be registered in the databaseActor:Administrator | Empty Course Code but correct input for the textboxes | Error message “Fill in all details. Please wait” | System displays error message “Fill in all details. Please wait” | Pass | | | Correct Course Code but same Course Code (i.e. duplicate course code) | Error message “Course code already exists for another course. Please wait” | System displays error message “Course code already exists for another course. Please wait” | Pass | | | Correct Course Code, Lecturer, year, semester and class | Successful message “Course successfully updated. Please wait” | System displays error message “Course successfully updated. Please wait” | Pass | 1 | Function Name:Delete CoursePrecondition: Administrator must be registered in the databaseActor:Administrator | Click on Delete button | Successful message “Course successfully deleted. Click here to refresh | System displays successful message “Course successfully added. Click here to refresh” | Pass | 1 | Function Name:Add VenuePrecondition: Administrator must be registered in the databaseActor:Administrator | Empty field (i.e., Venue) | Error message “Fill in all details. Please wait” | System displays error message “Fill in all details. Please wait” | Pass | | | | | | |

7.2.1.2 USER ACCEPTACE TESTING
The user acceptance testing is given out to students inform of questions after the users interact with the actual system. The user acceptance testing questions will be given out to ten (10) evaluators so that they will fill up the form and express how they feel about the system “LEGENDA ONLINE STUDEN TIME TABLE SYSTEM”. The user acceptance testing is written below:-
Refer to appendix
7.2.1.3 ANALYSIS OF USER ACCEPTANCE TESTING
The analysis and result of User Acceptance Testing conducted for LEGENDA ONLINE STUDENT TIME TABLE SYSTEM are shown below. The User Acceptance testing was given out to students to evaluate and provide feedback on the performance, interface, usability and navigation of the Time Table System. Below are the analyses of User Acceptance Testing of the above named system:

Analysis of Graphical User Interface

Figure7. 2: Analysis of Graphical User Interface

The above question is very crucial for the author (system developer) to understand and know how the Actors (Users of the system) feel about Legenda Online Student Time Table System. The analysis of the Graphical User Interface comprises of system’s color, pictures used and the navigation of the system. This user acceptance question is very important in Legenda Online Student Time Table System.
Analysis of System Understandability

Figure7. 3: Analysis of System Understandability
The above chart shows the analysis of how a user understands the system and how long (i.e. minutes) it takes them to understand and interact with the system. However, we can see that the percentage of evaluators that chooses “1-5” minutes (mins) is 30%, “6-10” are 60 percent, the number of evaluators that chooses “11-15” mins are 10% and 20 mins is zero percent. The above analysis clearly show that, LEGENDA ONLINE STUDENT TIME TABLE SYSTEM is very user friendly because the author strictly adhere to the heuristics law by Jacob Neilson and following the KISS principles (Keep It Simple and Straight Forward).
ANALYSIS OF SYSTEM RESPONSE TIME

Figure7. 4: Analysis of Systems response time
The above report shows the analysis of the System Response time based upon the evaluation of Systems acceptance testers (i.e. to say, the system actors). The percentage of users that rates the system response, as Excellent are time are “60%” percent. The evaluator that rates the system response time as Good are “30%”. Again, the percentage of evaluators that rates the system as Fair are “10%” and last but not the least, the number of evaluators that rates the system as Poor are “0%”. It is obvious that, LEGENDA ONLINE STUDENT TIME TABLE SYSTEM’s response time is excellent based on the above analysis of the systems actors.

ANALYSIS OF SYSTEMS USABILITY

Figure7. 5: Analysis of System’s Usability
The analysis of the above user acceptance-testing question shows how systems actors feel about the system’s usability (i.e. to say, the simplicity and the understandability of Legenda Online Student Time Table System). The percentages of users that rate the systems usability as Excellent are “40%”, the percentage of users that rates the system as Good are “60%”, the percentage of users that rates the system usability as Fair are “10%” and the number of users that rates the system as Poor are “0%”. The analysis of the above question clearly shows that Legenda Online Student Time Table System’s Usability is good.

ANALYSIS OF SYSTEM’S FUNCTIONALITY

Figure7. 6: Analysis of System’s Functionality
The above chart shows the analysis of the functionalities of the system. The completeness of a system depends on the functions the system provides. The percentages of users or evaluators that rates the system’s function as Excellent are “30%”, the percentage of Users that rates the system’s functionality as Good are “60%”, the percentage of users or evaluators that rates the system’s functionality as Fair are “10%” and the number or users that rates the systems functionality as Poor are “0%”. Clearly, we can say that, the system’s functionality is good based upon the above analysis report.

ANALYSIS OF SYSTEM’S SECURITY

Figure7. 7: Analysis of System’s Security
The above analysis of the above user acceptance testing is to know how users (actors) feel about the system’s security. The number of percentages of users that rates the system’s security as Excellent are “33%”, the percentages of users that rates the system’s security as Good are “56%”, the percentage of users that rates the system’s security as Fair are “11%” and the percentage of evaluators that rates the system’s security as Poor “0%”. Consecutively, we can assume that the system’s security is good.

ANALYSIS OF SYSTEM’S FLEXIBILITY

Figure7. 8: Analysis of System’s Flexibility
The above question will show the analysis of system’s flexibility. The number of users or evaluators that choose Excellent are “40%”, the percentages of users that rates the system as Good are “50%”, the number of users that rates the system as Fair are “10%” and the percentages of users that rates the system as Poor are “0%”. From the above analysis, the author will assume that Legenda Online Student Time Table System as Flexible and easy to interact with.

7.2.2 WHITE BOX TESTING
White box testing also known as clear box testing is a technique where an understanding of the software internals is key to creating the test plan approach (Loveland et. all, 2004). Saleh 2009 states that; white box testing is also referred to as structural testing. White box testing performs the white box testing or quality assurance relies on the examination of the code without executing it.
Source Code
Functional Specification
White box-based test generation
Source Code
Functional Specification
White box-based test generation

Figure7. 9: White box Strategies and input
(Saleh, 2009)

Table7. 2: white box For Login Function Line NO | Description | Valid Test Cases | Invalid Test Cases | | (if(isset($_POST['login'])) { $username= $_POST['username'];$password= $_POST['password']; | Input | Result | Input | Result | 8-9 | | Username: TomPassword: 12345 | Line number 17-34 | Username:EmptyPassword: empty | 17-28 and 55-58 | PRINT SCREEN OF CODE OF THE SYSTEM |

Table7. 3: white box testing for Add Course Line NO | Description | Valid Test Cases | Invalid Test Cases | | if(isset($_POST['create_course'])){ $title = $_POST['title']; $lecturer = $_POST['lecturer']; $course_code = $_POST['course_code']; $year = $_POST['year']; $semester = $_POST['semester']; $class = $_POST['class']; | Input | Result | Input | Result | 3-13 | | Title: MathsLecturer: Mr Marshal AlqudahCourse Code: CN3044Year: 1Semester: 2Class: BIS | Line number 3-13 | Title: EmptyCourse Code: exist in the database (i.e. two same course code)Text boxes: Empty | 28- 33 and 32-41and 36-41 | 14-25 | if($title&&$course_code) { $query = mysql_query("SELECT * FROM courses WHERE course_code='$course_code'"); $t = mysql_num_rows($query); | Title: MathsLecturer: Mr Marshal AlqudahCourse Code: CN3044Year: 1Semester: 2Class: BIS | Line number 14-25 | Title: Course title exist in the databaseCourse Code: exist in the database (i.e. two same course code | 28 – 33 and 32-41 | 25-29 | if($t<=0) { $queryd = mysql_query("SELECT * FROM courses WHERE course='$title'"); $ts=mysql_num_rows($queryd); | Title: Maths | Line Number 25-29 | Title: selected course | 25-29 | | if($ts<=0) { mysql_query("INSERT INTO courses VALUES('','$title','$course_code','$lecturer','$year','$semester','$class')");here to refresh</a></p></div> </div>"; } | Title: MathsLecturer: Mr Marshal AlqudahCourse Code: CN3044Year: 1Semester: 2Class: BIS | 36-41 | Title: EmptyCourse Code: exist in the database (i.e. two same course code)Text boxes: Empty | 28- 33 and 32-41and 36-41 | PRINT SCREEN OF CODE OF THE SYSTEM | |

7.3 CONCLUSION
In conclusion, the type of testing covered in this chapter comprises of black box testing (functional testing and user acceptance) and white box testing (unit testing). Testing is very crucial in verification and validating the Legenda Online Student Time Table System, the functional testing is done in validating LEGENDA ONLINE STUDENT TIME TABLE SYSTEM.

CHAPTER 8
CONCLUSION AND RECOMMENDATION
8.1 CONCLUSION
In conclusion, like most projects is challenging as well as research and fact finding technique. The chapter summarizes all the chapters (i.e. chapter 1-7) in this research work (project). The proposed Legenda Online Student Time Table system was designed and implemented successfully base upon the user requirements of the systems actors (i.e. Users); Legenda Online Student Time Table system will replace the current Legenda Time Table System that operates manually using Microsoft Excel to create students time table manually (i.e. paper-based) system used by Linton University College in order to serve as a means of interaction and communication between the school and its alumni and to keep the bond between alumni. The objectives of the proposed system are achieved; the features and functionalities proposed were implemented and tested to ensure the efficiency and effectiveness of the system. However, the author will further discuss the problems encountered, strengths of the proposed Legenda Online Student Time Table System, limitations, future enhancements and the lessons learnt and self appraisal. 8.1.1 SUMMARY OF THE CHAPTERS Chapter 1: INTRODUCTION This chapter gives the general overview of Legenda Online Student Time Table system, the problem statements, aim and objectives, scope and rationale of the time table system. The purpose of this chapter is to review and to have a clear picture of the current system and to identify and define the scope of the proposed system (i.e. Legenda Online Student Time Table System). Chapter 2: LITERATURE REVIEW This chapter is aimed at the literature review of current and the proposed system, the background and operations of the current system, review on other similar existing systems and the review of tools and technologies used in developing the proposed system (i.e. Legenda Online Student Time Table System). Chapter 3: METHODOLOGY In this chapter, the fact finding techniques, requirements analysis technique, steps phases to be used in conducting the research and system development methodology in order to develop the proposed system efficiently and effectively. Chapter 4: ANALYSIS In this chapter, the analysis of the current and new system, analysis of fact finding techniques, the functional and non functional requirements, hardware, software requirements and the network requirements of Legenda Online Student Time Table System, and UML (Unified Modelling Language) diagrams that gives the blue print of the features and functions of the new system Chapter 5: DESIGN This chapter describes the design phase of the software development life cycle, the requirements gathered, the reports on the analysis of the system, in analysis phase which are used for development of the proposed system as well as the processes involved in the building the proposed system. Chapter 6: IMPLEMENTATION The chapter is aimed to perform the final system implementation and coding based on the final prototype. Hardware and software development tools and technologies, system architecture, implementation of database and connection to the database will be described in the implementation phase. Chapter 7: TESTING The purpose of this chapter is to perform the system testing and the functional testing of the software to access the new system’s functionalities in other to explicitly avoid mistakes and errors to ensure the system features and functionalities meet the initial requirements.
8.2 PROBLEMS ENCOUNTERED The following highlights the problems encountered during the research and the system development:- * Time management: it is difficult to manage time due to other module the author had taken and the learning of some parts of the system implementation from others; this took quiet a long time but fortunately the problem was overcome with hard working and prayers. * In the fact finding phase the personnel to gather the information from were very busy with work, as a result the analysis phase was delayed for more weeks * Because, the author learnt a new programming language (php) and the front end tool (Netbeans). I would say, a net bean is among the design tool that does not support GUI (Graphical User Interface) which makes it interesting to program but its time consuming.
8.3 STRENGTHS OF LEGENDA ONLINE STUDENT TIME TABLE SYSTEM The system’s strengths are the features and functions of the system that meets the initial user requirements. The following highlight the strengths of the new OWBAS * SYSTEM INTERFACE: the GUI is well designed and comprises of interesting and interactive features and functionalities. * SECURITY FEATURE: login security feature was implemented to protect the system and provides access to only authorized users. * TIMETABLE FUNCTION: The timetable function is very interesting because, it allows administrator to create timetable for different groups of students which is classified into group one, two and three respectively. * Displaying of error messages: the system displays error messages to wrong input by users and also for invalid entry. * PRINT FEATURE: This function is very important because, it allows both the students and administrator to print lecture time table based on the group of the student. E.g. group1, 2 or 3. * Update USERNAME and PASSWORD FEATURE: This function allows students and administrator to quickly update their details in the system * Forum: the system enables alumni to post in the forum page and to view post by others
8.4 LIMITATIONS OF LEGENDA ONLINE STUDENT TIME TABLE SYSTEM The Limitations of Legenda Online Student Time Table System includes the following:- * The system don’t not send forgotten password to email address and the time table creation part is not validated. * The system does not provide time table for lecturers and it also does not provide lecturers with any function. * The system does not allow students to delete timetable and doesn’t provide a function validate some text fields. E.g. add venue.
8.5 FUTURE ENHANCEMENT The feature enhancement of Legenda Online Student Time Table System includes the following:- * Supports students and lecturers: this function will be implemented to support multiple languages. * The system should be able to provide lecturers with lecture time table. * Online chatting: the online chatting should be between students and lecturers in case if the lecturer is on MC (medical leave). * Create multiple timetable at a time * Allows all IT school , that is to say, the HND students, degree students, part time students and phd students to acquire their lecture timetable online.
8.6 LESSON LEARNT This section provides the overview of the lessons learnt by the author, the project developed was quiet challenging and motivating at the same time; this is because it required lots of research and findings of new skills, this resulted in enhancing the author’s research skills, critical and analytical thinking. The following highlights the lessons learnt: * A strong knowledge on exploration and conducting research. * Good time management. * Good understanding on software development methodologies and development tools and techniques. * Strong knowledge in analyzing business environments * Ability to document project of any size. 8.7 REFLECTION
There are many problems or obstacles encountered in this project, which are numerous and challenging. One of the major problems encountered is the analysis phase which requires the author to have an in-depth knowledge on how to plan the project (project plan) and to know the reason of building the information system. Moreover, the analysis phase is also challenging especially when conducting the interview sessions and questionnaire. Lastly, the implementation of the final system is done using suitable programming language
The literature review is very complicated and confusing. Finding the right research topic is time consuming and troublesome. Selecting the appropriate development model is difficult as well because, you must research and compare all of the software development life cycle.
The author achieved almost all the future plan in the personal development plan (PDP) that is to say, the author is now proficient in Php (hypertext pre-processor), MySQL server, c++ programming and good understanding of how to use Micromedia dream weaver to design the interface of the system using CSS (Cascading Style Sheet) concurrently.
8.8 MILE STONE
Apparently the development of the system “Legenda Online Student Time Table” can be termed as a success, as most of the objectives stated out by the author are to an extent achieved considerably well. With this development, the author believes that Legenda Online Student Time Table System will have its information management problems reduced to a large extent and will contribute immensely to the success of the IT department and Legenda Education Group in general.
However, due to limitations on research exposure and time constraints, certain possible features of the system could not be achieved but are hereby recommended as possible future enhancement of the system as stated above

REFERENCE
9.1 REFERENCE
BOOKS
Arthur M. L., (2007). Analysis and design of information systems. 3rd ed. London: Springer. P29-31.
Amyot D., Williams A. W., (2005). System analysis and modeling: 4th international SDL and MSC workshop, SAM 2004, Ottawa, Canada, June 1-4, 2004: revised selected papers. London: Springer. P1-5.
Aurum A., Wohlin C., (2005). Engineering and managing software requirements. Germany: Springer. P130-131.
Andrea F., Anastasia H., Prokos, (2007). The interview: from formal to postmodern. United States: Left Coast Press. P9-13.
Alan D., Barbara H. W., and Roti R M., (2008). Project Management. In: WILEY Systems Analysis and Design. 4th ed. NewYork: mcGraw-Hill . p47-56.
Bergmann R., (2002). Experience management: foundations, development methodology, and Internet-based applications. London: Springer. P34-38.
Bernstein P A., Newcomer E., (2009). Principles of transaction processing. 2nd ed. United States: Morgan Kaufmann. P1-4.
Charles H., Liv W., and Eiichi W., (2009). XBRL for Dummies. New York: John Wiley & Sons. P34-39.
Constantinos J. S., (2004). System Development Life Cycle. Encyclopedia of Information Systems. 30 (3), p329-344.
Craig L., (2002). Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and the Unified Process. 2nd ed. New York: Prentice Hall Professional. P197-205.
Daft J. M., Willmott H., (2010). Organization theory and design. 10th ed. London: Cengage Learning EMEA. P34-39.
Doug Rosenberg, Matt Stephens (2007). Use case driven object modeling with UML: theory and practice Apress Series Books for professionals by professionals Expert's voice in UML modeling. 2nd ed. London: Apress. P6-10.
Egbert J., Boers W., (2001). A constructive evolutionary approach to school timetabling. London: Addison Weseley. p101-106. \ Fowler M., (2004). Uml Distilled: A Brief Guide to the Standard Object Modeling Language Addison-Wesley Object Technology Series Object Technology Series. 3rd ed. London: Addison-WesleyProfessional. P53-58.
Graham K., (2005). Multidisciplinary scheduling: theory and applications : 1st International Conference, MISTA '03 : Nottingham, UK, 13-15 August 2003 : selected papers. London: Springer. p163-164.
Gary A., Philip K., (2008). MARKETING: AN INTRODUCTION MyMarketingLab Series. 9th ed. United States: Pearson Prentice Hall. P101-104.
Harper S., (2009). Oracle SQL Developer 2.1 From technologies to solutions. London: Packt Pub.. P14-19.
Hutchison T., (2008). Web Marketing for the Music Business. London: Elsevier. P68-70. http://books.google.com.my/books?id=SvFZVPas-mYC&pg=PA96&dq=to+do+things+right%E2%80%9D+(efficiency)+and+%E2%80%9Cdo+the+right+thing%E2%80%9D+(effectiveness)&hl=en&sa=X&ei=FC8aT-XvI4n5rQfkw8nLDQ&sqi=2 (2010). Community Policing: Partnerships for Problem Solving. 6th ed. LONDON: Delmar C. Learning. p96-98.
Ian B., (2008). Questionnaire Design: How to Plan, Structure and Write Survey Material for Effective Market Research. 2nd ed. London: Kogan Page. P2-4.
Julie A. J., Andrew S., (2003). The Human-Computer Interaction Handbook: Fundamentals, Evolving Technologies and Emerging Applications. 3rd ed. Mahwah, NJ: Lawrence Erlbaum Associates. p1172-1174.
Karl E. W., (2009). Software Requirements. 2nd ed. London: O'Reilly Media, Inc. P10-20. McFarland D S., (2010). Dreamweaver CS5: The Missing Manual. USA: O'Reilly Media, Inc.. P37-40.
Kurt Bittner, Ian Spence (2003). Use Case Modeling The Addison-Wesley Object Technology Series. London: Addison-Wesley Professional. P1-5.
Mehmet A., Mira M., and Rainer, U., (2003). Objects, components, architectures, services, and applications for a networked world. NEW YORK: Springler-Verlag Berlin Heidelberg. p87-88.
Manohar P., Manohar S. Pawar., (2004). Data collecting methods and experiences: a guide for social researchers. New Delhi: Sterling Publishers Pvt. Ltd. P18-20.
Moeen D., (2008). Pattern recognition software development methodology (PRSDM) based on design pattern recognition techniques and agile methodologies. London: ProQues. P1-6.
Rajender A., (2010). Research Methods for Pharmaceutical Practice and Policy. London: Pharmaceutical Press. P148-150.
Microsoft® SharePoint® 2010 (2010). Bill English. London: O'Reilly Media, Inc. P100-105.
Negrino T., Dori S., (2008). Dreamweaver CS4 for Windows and Macintosh. 3rd ed. London: Peachpit Press. P294-296.
O'Sullivan B., (2002). Constraint-aided conceptual design. London: John Wiley and Sons. P44-46.
Pawan K. Bhardwaj (2000). MCSE Windows 2000 professional study guide (exam 70-210). London: McGraw Hill Professional. P76-78.
Richard W. Selby (2007). Software engineering: Barry W. Boehm's lifetime contributions to software development, management, and research Practitioners Series. United Stats: Wiley-IEEE. P367-369.
Sommerville I., (2007). Software Engineering . 8th ed. London: ADDISON WESELY. P118-125.
Sanjay M., (2009). Business Process Automation. New Delhi: PHI Learning Pvt. Ltd.. P29-30.
Tsai J. J. P., Li B., (2001). Hybrid parallel execution model for logic-based specification languages Volume 10 of Series on software engineering and knowledge engineering. New York: World Scientific.P185-188.
Tsui F., Karam O., (2009). Essentials of Software Engineering. 2nd ed. United Stats: Jones & Bartlett Learning. P140-143.
Terence L., (2004). Management information systems. 9th ed. United Kingdom: Cengage Learning EMEA. P2-5.
Uimonen T., (2000). Case: Rational Rose 81940 A Seminar on Reverse Engineering Software Systems Laboratory Tampere University of Technology Fall. London: Springer. P12-14.
Wysocki R. K., (2011). Effective Project Management: Traditional, Agile, Extreme. 5th ed. London: John Wiley & Sons. P98-102.
Zain M J., Mohd W M W., El-Qawasmeh E., (2011). “Software Engineering and Computer Systems, Part 3: Second International Conference”, ICSECS 2011, Kuantan, Pahang, Malaysia, June 27-29, 2011, Proceedings, Volume 3. 3rd ed. Malaysia: Springer.P147-149.
Unhelkar B., (2005). Practical Object Oriented Analysis. Australia: Cengage Learning Australia. P141-149.

JOURNAL ARTICLE
Alan R P., Girish H S., George E C., (2008). “The phases of ERP software implementation and maintenance: A model for predicting preferred ERP use”. Journal of Computer Information Systems. Vol.48 no.2, P25-33.
Costa D., (2003). “European Journal of Operational Research”. A tabu search algorithm for computing an operational timetable. 76 (1), p98-110.
Florian K., (2006). “Forum, Qualitative Social Research”. The Use of Qualitative Content Analysis in Case Study Research. Vol.7 no.1, P117-109.
Hew K., and Brush T., (2007). “Integrating Technology into K-12 teaching and learning: current knowledge gaps and recommendations for future research”. Educational Technology Research and Development. Vol.55 no.3, p223-252.
Harwell R., (2001). “What Is A Requiremesnt? “. Proceedings of the Third International Symposium of the NCOSE. Vol.2 no.5, P56-58.
Jianga J J., Kleinb G., Ballounc J L., Crampton S M., (2010). “System analysts’ orientations and perceptions of system failure”. Information and Software Technology. Vol.41 no.2, P101-106.
Müller T., (2003). “Evolutionary Design of Microwave Circuits”. Evolutionary Design of Microwave Circuits. Vol.2 no.2, P2-3.
Nandhin M., (2009). “A Survey of Simulated Annealing Methodology for University Course Timetabling”. International Journal of Recent Trends in Engineering. Vol.1 no.2, p255-256.
Özcan E, Parkes A J., Alkan A., (2012). “The Interleaved Constructive Memetic Algorithm and its application to timetabling”. Computers and Operations Research. Vol.39 no.39, P394-401.
SAYKO M., (2004). “Parallel Software Development is the New Normal”. [Online]Available: http://www.cmcrossroads.com/cm-journal-articles/6746-parallel-software-development-is-the-new-normal . Last accessed 20th Feb 2012.
Schaerf A., (2004). “A Survey of Automated Timetabling”. Dipartimento di Informatica e Sistemistica Universit. Vol.16 no.4, p1-2.
Safaai D., Omatu S., Ohta H. and Samat A. P., (2009). “Object-oriented constraints logic programming for timetable planning”. International Journal of Systems Science. Vol.28 no.10, p987-999.
Vaishnavi V., and Kuechler W., (2004). “Design Science Research in Information Systems” January 20, 2004, last updated March 8, 2012. URL: http://desrist.org/desrist
Yang N., Ding B., Zhang J., (2010). “Improved Sampling Importance Resambling Particle Filter Optimisation by Tabu Search”. Artificial Intelligence and Computational Intelligence (AICI). Vol.1 no1, P359-363.
Zeyad M. A., Mohammad A., Al-Zoubi S., (2011). “MOBILE E-TICKETING RESERVATION SYSTEM FOR AMMAN INTERNATIONAL STADIUM IN JORDAN”.INTERNATIONAL JOURNAL Of ACADEMIC RESEARCH. Vol.3 no.3, p844-849.
ONLINE REFERENCE techopedia (2010). Development Environment. [Online]Available: http://www.techopedia.com/definition/16376/development-environment. Last accessed 28th Sept 2012.
Vishal Metha. (2011). Visibility Principle in User Interfaces. [Online]Available: http://idyeah.com/blog/2011/03/visibility-principle-in-user-interfaces/. Last accessed 30th Sept 2012
Developer. (2012). iOS Human Interface Guidelines. [Online]Available: http://developer.apple.com/library/ios/#documentation/userexperience/conceptual/mobilehig/Principles/Principles.html. Last accessed 30th Sept 2012.
George Reese. (2012). Client/Server Fundamentals .[Online] Available: http://www.google.com.my/imgres?q=three+tier+architecture+diagram+php&hl=en&sa=G&biw=1280&bih=552&tbm=isch&tbnid=M0V36ux-vxUWxM:&imgrefurl=http://www.webbasedprogramming.com/Java-Unleashed-Second-Edit. Last accessed 04th Oct 2012. softwaretestingfundamentals. (2012). Test Plan. Available: http://softwaretestingfundamentals.com/test-plan/. Last accessed 22nd Oct 2012.
Laurie Williams (2006). A (Partial) Introduction to Software Engineering Practices and Methods. 5th ed. New York: Addison-Wesley. P35-45.
Scott Loveland, Michael Shannon, Geoffrey Miller, Richard Prewitt (2004). Software Testing Techniques: Finding the Defects That Matter. Illustrated ed. New York: Cengage Learning. P27-29.
Kassem A. Saleh (2009). Software Engineering. Illustrated ed. Canada: J. Ross Publishing. P224-227.
Gerald D. Everett, Raymond McLeod, Jr. (2007). Software Testing: Testing Across the Entire Software Development Life Cycle. USA: John Wiley & Sons. P67-68.
Netbeans. (2012). What is the NetBeans Project?. [Online] Available: http://netbeans.org/welcome.html. Last accessed 17th Sept 2012.
Paul Leahy. (2012). What Is Netbeans?. [Online]Available: http://java.about.com/od/netbeans/p/whatisnetbeans.htm. Last accessed 17th Sept 2012.
Techopedia. (2012). NetBeans. [Online]Available: http://www.techopedia.com/definition/24735/netbeans. Last accessed 17th Sept 2012.
Kiran Bhat. (2008). Netbeans – Two real advantages. [Online]Available: http://mynetbeansxperience.blogspot.com/2008/04/netbeans-two-real-advantages.html. Last accessed 17th Sept 2012.
Agilemodeling. (2011). UML 2 Class Diagrams. [Online]Available: http://www.agilemodeling.com/artifacts/classDiagram.htm#Disclaimer. Last accessed 26th Mar 2012.
Bradley A., (2012). What are PHP and MySQL. [Online]Available: http://php.about.com/od/phpbasics/ss/php_mysql_2.htm. Last accessed 19th Feb 2012.
Cl500. (2012). What is Database. [Online]Available: http://www.cl500.net/. Last accessed 17th Feb 2012.
Charvat J. P., (2002). Rational Rose simplifies software development. [Online]Available: http://www.techrepublic.com/article/rational-rose-simplifies-software-development/1049781. Last accessed 20th Mar 2012.
Coventry., (2012). COVENTRY UNIVERSITY. [Online]Available: http://wwwm.coventry.ac.uk/Pages/index.aspx. Last accessed 6th Jan 2012.
Cerejo L., (2010). Design Better And Faster With Rapid Prototyping. [Online]Available: http://www.smashingmagazine.com/2010/06/16/design-better-faster-with-rapid-prototyping/. Last accessed 21st Feb 2012.
Coley P., (2012). V-Model Development. [Online]Available: http://www.coleyconsulting.co.uk/v-model.htm. Last accessed 20th Feb 2012.
Download.cnet., (2012). Online Course Registration System. [Online]Available: http://download.cnet.com/Online-Course-Registration-System/3000-2056_4-10738433.html. Last accessed 17th Jan 2012.
Dotnetfunda. ,(2012). What is Prototyping?. [Online]Available: http://www.dotnetfunda.com/interview/exam78-what-is-prototyping.aspx. Last accessed 3rd Feb 2012.
Diamond S., (2012). How to Convert XML to Access Database. [Online]Available: http://www.ehow.com/how_6925528_convert-xml-access-database.html. Last accessed 1st Feb 2012.
Excelfoundry., (2012).EXCEL UNIVERSITY. [Online]Available: http://www.excelfoundry.com/careers/excel-university. Last accessed 6th Feb 2012.
Google., (2012). Preparing a Study Timetable. [Online]Available: http://www.google.com.my/imgres?q=victoria+university+melbourne+%2B+time+table+sample&um=1&hl=en&biw=1280&bih=699&tbm=isch&tbnid=IE9wRyA_CHp5TM:&imgrefurl=http://www.monash.edu.au/lls/llonline/download-tab.php%3Ftutorial%3Dquickrefs&docid=j3HEWVH0-lzhgM&imgurl=http://www.monash.edu.au/lls/llonline/assets/images/qrefs/qref02-image1.gif&w=614&h=407&ei=NflbT9qwGIirrAemqKGmDA&zoom=1. Last accessed 11th Mar 2012.
Htmlhelp., (2012). CSS Structure and Rules. [Online]Available: http://htmlhelp.com/reference/css/structure.html. Last accessed 1st Feb 2012.
Ibm. (2011). UML basics: The sequence diagram. [Online]Available: http://www.ibm.com/developerworks/rational/library/3101.html. Last accessed 26th Mar 2012.
Linton., (2011). About Linton University College. [Online]Available: http://www.linton.edu.my/en/about/. Last accessed 31st Jan 2012.
Lerdorf., (2012). Rasmus Lerdorf. [Online]Available: http://lerdorf.com/bio.php. Last accessed 19th Feb 2012.
Larman C., (2004). Software Development: Iterative & Evolutionary.[Online] Available: http://www.informit.com/articles/article.aspx?p=102256. Last accessed 21st Feb 2012.
Mimosasoftware., (2012). Mimosa Scheduling Software features. [Online]Available: http://www.mimosasoftware.com/mimosa.html. Last accessed 11th Mar 2012.
Mysql., (2012). Why MySQL?. [Online]Available: http://www.mysql.com/why-mysql/. Last accessed 1st Feb 2012.
Php., (2012). What is PHP?. [Online]Available: http://www.php.net/. Last accessed 1st Feb 2012.
Phillips A., (2010). Software Development Methodologies. [Online]Available: http://www.codeproject.com/Articles/124732/Software-Development-Methodologies. Last accessed 7th Feb 2012.
Publib.Boulder.Ibm. (2005). Relationships in deployment diagrams.[Online] Available: http://publib.boulder.ibm.com/infocenter/rtnlhelp/v6r0m0/index.jsp?topic=%2Fcom.ibm.xtools.modeler.doc%2Ftopics%2Fcassn.html. Last accessed 26th Mar 2012.
Raymondlewallen., (2005). systems development life cycle (SDLC). [Online]Available: http://codebetter.com/raymondlewallen/2005/07/13/software-development-life-cycle-models/. Last accessed 14th Feb 2012.
Raj R A., (2012). What is PHP and its advantages and disadvantages.[Online] Available: http://www.techaspirant.com/what-is-php-and-its-advantages-and-disadvantages/. Last accessed 19th Feb 2012.
Searchsqlserver., (2012). database. [Online]Available: http://searchsqlserver.techtarget.com/definition/database. Last accessed 17th Feb 2012.
Searchsoftwarequality., (2012). systems development life cycle (SDLC) . [Online]Available: http://searchsoftwarequality.techtarget.com/definition/systems-development-life-cycle. Last accessed 3rd Feb 2012.
Sousa F., (2008). Fully heuristic timetabling driven by students' feedback on availability. [Online]Available: http://bibliotecadigital.ipb.pt/handle/10198/1124. Last accessed 9th Feb 2012.
Searchcio. (2012). Rational Rose. [Online]Available: http://searchcio-midmarket.techtarget.com/definition/Rational-Rose. Last accessed 20th Mar 2012.
Sql-programmers., (2009). Disadvantages of Using Access. [Online]Available: http://www.sql-programmers.com/DisadvantagesofAccess.aspx. Last accessed 17th Feb 2012.
Searchenterpriselinux., (2012). PHP (Hypertext Preprocessor). [Online]Available: http://searchenterpriselinux.techtarget.com/definition/PHP. Last accessed 18th Feb 2012.
Slepi., (2009). System Development Life Cycle (SDLC) Methodologies.[Online] Available: http://www.slepi.net/blog/system-development/system-development-life-cycle-sdlc-methodologies.html. Last accessed 21st Feb 2012.
Santiago N., (2009). What is a research question?. [Online]Available: http://www.examiner.com/scholarly-research-in-san-jose/what-is-a-research-question. Last accessed 19th Jan 2012.
Searchsoftwarequality.Techtarget. (2011). use case.[Online] Available: http://searchsoftwarequality.techtarget.com/definition/use-case. Last accessed 26th Mar 2012.
Teamits., (2002). Q: What are the limitations of using Microsoft Access® as your web site's database?.[Online]Available: http://www.teamits.com/internet/support/nt/msaccess_limitations.html. Last accessed 17th Feb 2012.
Uel., (2012). welcome to the university of east london. [Online]Available: http://www.uel.ac.uk/. Last accessed 6th Feb 2012.
Umdrive.memphis., (2012). ICL 7992: Master's Project Sample Research Questions. [Online] Available: https://umdrive.memphis.edu/g-actres/www/mptopics.html. Last accessed 19th Jan 2012.
Usability. (2011). Use Cases.[Online] Available: http://www.usability.gov/methods/usecases.html. Last accessed 26th Mar 2012.
Vtc. (2011). UML Tutorials. [Online]Available: http://www.vtc.com/products/UML/UseCaseDiagrams/66837. Last accessed 27th Mar, 2012.

Vadhe P., (2010). SYSTEM DEVELOPMENT LIFE CYCLE (PLANNING, ANALYSIS, DESIGN, IMPLEMENTATION, TESTING AND MAINTENANCE.). [Online]Available: http://www.softwaretestingdiary.com/2010_08_26_archive.html. Last accessed 2nd Feb 2012.
Visualcase. (2011). Collaboration Diagram. [Online]Available: http://www.visualcase.com/kbase/visual_case.htm#collaberation_diagram.htm. Last accessed 26th Nov 2011.
Walsh N., (2010). A Technical Introduction to XML. [Online]Available: http://www.xml.com/pub/a/98/10/guide0.html?page=2. Last accessed 18th Feb 2012.
Walsh N., (1998). A Technical Introduction to XML. [Online]Available: http://www.xml.com/pub/a/98/10/guide0.html. Last accessed 1st Feb 2012.
Webster and Watson., (2010). Analyzing the Past to Prepare for the Future: Writing a Literature Review.[Online]Available:http://chitu.okoli.org/research-reviews/webster-and-watson-2002.html. Last accessed 11th Feb 2012.
W3school., (2012). HTML Introduction. [Online]Available: http://www.w3schools.com/html/html_intro.asp. Last accessed 1st Feb 2012.
Waterfall-model., (2012). Waterfall Model ADVANTAGES, EXAMPLES, PHASES AND MORE ABOUT SOFTWARE DEVELOPMENT. [Online]Available: http://www.waterfall-model.com/. Last accessed 15th Feb 2012.
Wordpress., (2010). Metodologi Pengembangan Sistem. [Online]Available: http://danxer.wordpress.com/category/komputer/. Last accessed 20th Feb 2012.
APPENDIX A
PROJECT PROPORSAL
A.1 INTRODUCTION
Legenda Online Student Time Table System is a web-based time table system that will allow or help students and lecturers to acquire their time table online (Download.Cnet, 2012). This system is needed to provide student with appropriate time tables and will help the university or college “to do things right (i.e. efficiently) and “do the right thing” (i.e. effectively).
However, the proposed system is concerned with building and designing the user interface of “Legenda Online Student time table System”. Introducing human computer interactions (HCI), GUI (graphical user interface), psychology, ergonomic, graphical designers, human factors and user needs. This project is essentially concerned with the accepting (understanding) of how people and computers interact and carry out tasks and how interactive computer systems are designed and maintained (Julie and Andrew, 2003). The proposed “Legenda Online Student Time Table System” system is also concerned with the user interfaces (UI), GUI; know who are the users and then designing the system with suitable color, pictures, navigations and pages for students, Administrator and staffs.

A.2 BACKGROUND OF STUDY
LINTON UNIVERSITY COLLEGE (LEGENDA) is formally known as “Kolej Linton”. It was founded in 1985 in Ipoh, Perak Malaysia (Linton, 2011). In 2005, the university started offering international students with degree and HND (higher national diploma) programs Linton University College comprises of local students (Malaysians) and international students (foreigners) from all over the world. Example includes China, Nigeria, Tanzania, Cameroon, Sudan, Persia, Bahrain, Iraq etc. This university basically offers program for foundation, diploma, degree and masters programs in collaboration with the University of east London (Uel, 2012), excel University (Excelfoundry, 2012) and Coventry University (Coventry, 2012) certifications. Currently, Linton University College has more than 5000 international students. In the year 2010, the universities is further upgraded from “Kolej Universiti” to “Linton University College” (LINTON, 2011); because of its academic achievements towards assuring parents that their products (students) will be up-to-date and meet-up the expectations of standardized companies and industries in the globe (world).
However, Linton University College faces the issues of generating accurate time table for Information Technology School (school of IT). One of the major issues faced is the manual generation of student time table. As students time tables are generated manually, it is almost impossible to for the IT SCHOOL or DEPARTMENT to provide students with accurate, reliable, consistent, complete and error free time tables without the clashing of venues, conflicting lecture time, conflicting lecture-venue allocation, late collection of student time table, waiting in the queue for hours etc. Therefore, for us (the author) to address the stated problems or issues, the proposed system “Legenda online student time table system” should be implemented because it is the solutions to the stated problems and will make life easier for students, lecturers and administrator.

A.3 RATIONALE
Nowadays, computer systems are used globally for different purposes. Universities and Colleges all over the world faces the issues of generating adequate, consistent and complete time table for their students and staffs. For us (the author) to address these problems, we must explore information technology (IT) to its fullest. Therefore, building an online student time table system that will allow its users “to do things right” efficiency and be “doing the right thing” effectiveness.
A.4 PROBLEM STATEMENT
To analyze and develop “Legenda online student time table system” that will unravel the difficulties and problems in assigning proper time table to students, late collection of time table and clashing of lecture venues due to the fault associated with the paper based system. The problems or issues include the following:-
A.4.1 MANUAL SYSTEM
The current system is a manual system. Time table for students is generated manually (i.e. on paper’s), which is tedious, complicated and time consuming. Thus, much time is needed to creating a simple time table for students and staffs. Due to the above issues, time tables are given to student couple (many) of time, all because of the inconsistencies of the “As-Is System” (i.e. the current system).
A.4.2 IMPROPER LECTURE-VENUE ALLOCATION
Lecture-venue and time is allocated to students randomly because of the paper based system. This will discourage students from attending classes in the future, which are due to wrong timing schedules.
A.4.3 LATE COLLECTION OF TIME TABLE
The paper based system of generating student time table is not reliable. It will take weeks to schedule the semester time table for students, thereby making it hard (tedious) for the school management (administrator, staffs etc.) to complete the entire syllabus on the stipulated time. That way, the school will be left behind and the students would not perform well in that semester and future semesters as well.
A.4.4 DIFFICULTY IN TIME TABLE RETRIEVAL
In the current system, students will wait in the queue for very long time in order to collect their lecture time table. Assuming that the school has more than 200 students, how much time is required to collect time table? Using such system is troublesome and time consuming to the students.
A.4.5 THE CLASHING OF VENUES
The current system is in-consistent because students collect time table at their perspective schools without critically inspecting and confirming that the timing schedules are right. Therefore, makes it trickier for students and lecturers to apprehend the clashing of students lecture venues.
A.5 AIM
To design an online timetable system for student with simple and user friendly interface (UI).
A.6 OBJECTIVES * To provide students with an online time table system for semester(s). * To provide system that will serve student and staff satisfaction (i.e. easier to locate lecture venue). * To provide system that will facilitate students to print out or send time table to their email address. * To provide system that will have an improved user interface (UI) and graphical user interface (GUI) (i.e. following KISS principles, keep it simple and straight forward) (MEHMET AKŞIT, MIRA MEZINI, RAINER UNLAND, 2003). * To provide system that will enable administrator to assign course to lecturers. * To know the productivity tool (design tool) that will be used to build the system. * To provide users with user manual after delivering the finished product (system). * To document the development of whole system so as to make it easy for future upgrade. * To compare related system (online time table system).
A.7 SCOPE
The scope of this project or research work is restricted to certain functionalities (features) which will be explained in details. The system will be an online system. It will provide its humble users with suitable login process for existing students, new students and administrator. The students don’t have to go to the information school (IT School) physically to collect their lecture time tables, the system will provide student with the function to collect their timetable online or send it to their email address. The administrator will be able to add students and staff into the database.
Moreover, the use of App server to run the program in the local host, MySQL server R2 for creation of database or xml (Extensible markup language) and Php (hypertext preprocessor) for the server site scripting, html (hypertext markup language) for design, Css (cascading style sheet) for design and lastly Dreamweaver or front page to build the complete system.

A.8 RESEARCH QUESTION
Research question is an organizing element for the topic under study (Santiago, 2009). The research question will guide you to complete your project. My project research question includes the following; * What do I want to know about my topic? * Can the system be of importance to its users? * Will the proposed system be completed on time and delivered to its users? * What if the system is rejected by its users? * In what ways is the system useful to its users? * How can the system be improved in the future? * What is the suitable database to be used? * What is the appropriate tool to develop the system?
Table A.1 Hardware and software requirement SOFTWARE REQUIREMENT | HARDWARE REQUIREMENT | Microsoft SQL server 2008 R2Web application PHPMAC OS X IBM Rational Rose 2010Microsoft | Key boardPrinterScannerMouse |

Student Name Supervisor’s Name
……………………... ……………………
Student Signature Supervisor’s Signature
………………….. …………………….

APPENDIX B
PERSONAL DEVELOPMENT PLAN
B.1 INTRODUCTION
The author is currently a Software Engineering student in Linton University College, Malaysia in collaboration with University Of East London UK. The author choose to pursue Software Engineering to strive and gain knowledge in ethics, programming, java, oracle, visual studio.net (V.B Net) to help create software’s for business processes like Banks, Online Banking Sites like (EBay, Barnes and Noble). The author should also be able to make a peculiarly delicate investigation on identifying requirements and proposing solutions, the author will also dedicate himself to make systems like yahoo.com, online reservation system, tracking system, Google earth etc. as far as I am concerned, software engineering is certainly one of the most flourishing fields nowadays, and most productive to the society and the globe in general.
B.2 INTRODUCTING THE RESEARCH TOPIC
Legenda Online Student Time Table System is a web-based time table system that will allow or help students and lecturers to acquire their time table online (Download.Cnet, 2012). This system is needed to provide student with appropriate time tables and will help the university or college “to do things right (i.e. efficiently) and “do the right thing” (i.e. effectively).
However, the proposed system is concerned with building and designing the user interface of “Legenda Online Student time table System”. Introducing human computer interactions (HCI), GUI (graphical user interface), psychology, ergonomic, graphical designers, human factors and user needs. This project is essentially concerned with the accepting (understanding) of how people and computers interact and carry out tasks and how interactive computer systems are designed and maintained (Julie and Andrew, 2003). The proposed “Legenda Online Student Time Table System” system is also concerned with the user interfaces (UI), GUI; know who are the users and then designing the system with suitable color, pictures, navigations and pages for students, Administrator and staffs. B.3 SWOT ANALYSIS
SWOT Analysis is a critical and the most strategic way used by personnel’s or people to evaluate their Strength, Weakness or Limitations, Opportunity and Threats of a certain individuals (personal development plan) of an organization. Normally, a SWOT analysis table involves specifying the objectives of the projects, identifying the internal and external factors that are easy and hard to achieve. The strength here refers to the positive aspects of one’s self and his current position or level. The weakness refers to the negative aspects of one’s self and present position or levels. Whereas, opportunity includes the aspects of the present situations, that the author will use to his or her advantage (e.g. studying at LINTON UNIVERSITY COLLEGE MALAYSIA, IN COLBORATION WITH UNIVERSITY OF EAST LONDON UEL UK). Below is the SWOT analysis of the author:-
Table B.1: My SWOT analysis STRENGTHS | WEAKNESS | * Understand quickly * Programming in Visual Basic * Modeling tool like Rational Rose Enterprise Edition * Microsoft Project * Microsoft office * Front Page * MySQL Server R2 * WAMP Server * Participate in class * Reading for exams * Tutorials * Presentations * Debate * Guiding my junior students | * C# and Java * Shy person * lack of confidence * Can’t speak fluently in public * Girls (breaking up) * Money * Marriage * Playing Xbox 360 (Games) | OPPOURTUNITY | THREATS | * Studying with friends * Online tutorials * Group tutorials * Discussing with lecturers on certain field of study * Accessing book stores * Internet * Online libraries * Books, magazines, novels * Hand book or Notes * Programming languages * Attending formal classes for Programming languages like VB, Java, Oracle, and Php, .Net, C #and database management systems. | * Cannot speak English fluently in public a times * Other programming languages like C++ and database management systems * Languages like C# and Pearl |

B.4 REQUIREMENT
A requirement is simply a statement of what the system should do and the functions it should have or perform. According to Tsui and Karam (2009), a requirement comprises of a set of statements that describes or explains the user’s needs and desires. Requirement in software engineering is nothing but a statement of what the system should do and the functions it should have. Requirements includes functional and non-functional requirement, which will be described below.
B.3.1 HARDWARE REQUIREMENTS
Hardware requirement is the hardware (physical component of computer) of the computer systems. Bhardwaj (2000) states that; hardware requirement determines and tells the author what hardware is required for the proposed system. For example, the hard disk size, the RAM size etc. The table below will describe all the hardware that is required to build and implement Legenda Online Student Time Table System.

Table B.2: Hardware Requirement of the proposed system HARDWARE | DESCRIPTION | AVAILABLE | NOT AVAILABLE | Computer System | A computer system that will help in viewing the proposed system | | | Laser Printer | A printer that can be used to print time and handouts table for student | | | Monitor | It is used to display video, pictures on the screen. | | | Scanner | It is used for scanning hardcopy files to digital copy. | | | Minimum 2GB RAM | Used to save temporary data. It is also used to when running large programs to speed up system’s performance | | | Intel Dual core Processor | It is a logical circulatory that responds to and processes the basic instructions that drive a computer system. | | | 80GB Hard Disk | The Minimum hard disk size that is required for the proposed system | | | Optical Mouse | The pointer device that will be used for the proposed system | | | QWERTY keyboard | This is a standard keyboard that will be used for the proposed system | | | B.3.2 SOFTWARE REQUIREMENT
According to Richard (2007), software requirement process is the first step in most software development process because; it allows the development team to determine if the system can be built and delivered in the stipulated time of delivery. Thus, software requirement helps in knowing how to build the proposed system (Legenda Online Student Time Table System) without further delay. The table below shows the software requirements in details.

Table B.3: Software requirements of the proposed system SOFTWARE | DESCRIPTION | AVAILABLE | NOT AVAILABLE | MySQL | MySQL is a server software that is used to store record in an information system | | | Php | Php is a server-side language that the compiler understands when creating and running sophisticated and simple WebPages. E.g. running website in Google chrome | | | C# | C# is a system development tool mostly for standalone systems. it is a Microsoft registered software | | | Micromedia Dream Weaver CSS5 | A software tool used to create and edit sophisticated websites | | | Cascading Style Sheet (CSS) | A software tool used mainly for design of system interface of websites. | | | Photoshop | A software tool that will be used to create the Logo of the proposed system | | | Windows 7 or Windows Vista | An operating system that the proposed system will run on | | | MacAfee Anti-virus | A virus detecting and removal tool. It also warns against malware and Trojans. | | | Browsers (Google Chrome, Internet explorer and opera | This is a tool used for browsing and surfing the internet. | | | WAMP Server | WAMP Server is a server site tool that is used to connect web pages to database and run on the web browsers | | | Microsoft project | Used to generate Gantt chart, pie chart after conducting the interview to know certain percentage | | | Microsoft office | Software package | | | Rational Rose Enterprise Edition | Rational rose is a modeling tools that is used to create use case, class diagram, activity diagram etc. | | | Microsoft Visio | Microsoft Visio is a modeling tool that is used to create use case, class diagram, collaboration diagram etc. | | |
B.3.3 NETWORK REQUIREMENT
Network requirement defines what the wireless network needs to do. The network requirements include all the requirements that must be used to connect the proposed system to the internet. The network requirement of the proposed system includes the following:-
Table B.4: Network requirement of the proposed system NETWORK | DESCRIPTION | AVAILABLE | NOT AVAILABLE | Switch | Is a computer networking device which will connect network segments | | | Bridge | Filters data traffic at a network which is very crucial for the proposed system | | | Network card | Is an expansion card that enable computer to physically connect LAN (local area network) | | | Wireless Modem | It connects to a wireless networks. | | | Router | A device that forwards data packets between telecommunications networks. | | | B.3.4 SOFTWARE SKILLS
In this context, a software skill refers to the level of the author’s skills that is needed to attain the implementation of the proposed system “Legenda Online Student Time Table System”. The table below illustrates more on the author’s technical skills.

Table B.5: Software Skills Rating SOFTWARE SKILLS | SKILL RATING | | Very poor | Poor | Average | Good | Very good | Microsoft Office | | | | | | Microsoft Project | | | | | | MySQL | | | | | | Rational Rose Enterprise Edition | | | | | | Microsoft Visio | | | | | | Php | | | | | | C# | | | | | | Micromedia Dream Weaver CSS5 | | | | | | Photoshop | | | | | | WAMP Server | | | | | |

B.3.5 TECHNICAL SKILLS RATING
The technical skill is a rating that the author will in a tabular format, show as to help the author to know what he already know and what is suppose to be studied and known by the author. The table below shows the technical skills to attain the implementation of the proposed system.
Table B.6: Technical Skills Rating TECHNICAL SKILLS | SKILL RATING | | Very poor | Poor | Average | Good | Very good | Local Area Network (LAN) | | | | | | Lan Troubleshooting | | | | | | Speaking | | | | | | Writing | | | | | | Reading | | | | | | Interpersonal Skills | | | | | |

B.3.6 ACTION PLAN
Action plan refers to the action that the author will take in order to effectively and comprehensively determine the best actions to improve him (the author) in the field that needs adjustments or bridging the knowledge gap in the future. The below table describes more on the author’s action plan.
Table B.7: Action Plan SKILLS | CURRENT RATING DURATION TO HIT THE TARGET | | Poor | Average | Good | Date Start Learning | Date Finish Learning | Duration | HTML | | | | 04-25-2012 | 05-10-2012 | 16 DAYS | CSS | | | | 04-25-2012 | 05-10-2012 | 16 DAYS | Php | | | | 05-10-2012 | 05-12-2012 | 219 DAYS | MySQL | | | | 05-10-2012 | 05-30-2012 | 20 DAYS | Dreamweaver | | | | 05-10-2012 | 05-12-2012 | 219 DAYS | Rational Rose | | | | 04-25-2012 | 05-10-2012 | 16 DAYS | C# | | | | 05-10-2012 | 08-10-2012 | 92 DAYS | Microsoft Access | | | | 04-25-2012 | 05-10-2012 | 16 DAYS | Microsoft word | | | | 05-10-2012 | 05-20-2012 | 10 DAYS |

B.3.7 PERSONAL DEVELOPMENT PLAN FOR THE FUTURE Goals | Action Plan | Start Date | End Date | Remarks | Improve My programming languages skills | - Practice C++, VB all the time- Read programmingBooks and online tutorials. | Today | December 2012 | Short term goal | improve English language, vocabulary and spelling | - Read literature in English books, Newspapers, novels, magazines.- speak English to everyone | Today | Ending of November 2012 | Short term goal | I want to be an intelligent programmer | - know the latest programming languages - read books relating to software engineering (S.E)- practice line of codes regularly | 2012 December | 2013 June | Long term goal | want to finish my masters in time | - improve my research skills- study hard- Focus on studies. | 2012 | 2014 | Long term goal | I want to be amicable | - calm- friendly- active and willing to learn from mistakes made - be patient- be a father some days | Today | - | Long term goal | Finish university on time | - Be punctual - Attend class’s- Read hard- ensure to pass all subjects | Today | November Ending 2012 | Short term goal | Time Management | - Schedule time table.- Do my Assignment on time- sleep before 12:00AM- wake up at 6:00AM | Today | December 2012 | Long term goal | Shy Person | - Make more friends- talking in public places like the lobby- be active | Today | - | Long term goal | Lack of confidence | - practice and make it as habit- try to be my self- believe in own ability. | Today | December 2012 | Long term goal | Girls | - mingle less with girls- No room for LOVE | Today | December 2012 | Long term goal | Money | - To be spending little on daily basis- To go for outing during HOLIDAYS only.- To be wise and act wisely-Spend appropriately-Avoid luxurious items. | Today | December 2012 | Long term Goal |
Table 7.0: Personal Development Plan for the Future

B.3.8 Reflections, Feedbacks from Friends and Materials Studied In This Module
Figure B.9: Reflections, Feedback from Friends and Materials Studied In This Module Reflection Of Experience | Feedback From Friends | - I have experience in C++,Web design,Rational rose enterprise edition, Front page, Micro soft word, Excel and Visual studio (V.B.Net). all this is in my First Year (University of East London) | - they think I am good- they say Girls are my major weakness- I like Argument- And I am hot tempered- spend a lot- talk a lot- they said I am also smart - I am intelligent- a well behaved person - very religious- and lastly, I respect the elderly | Improving my Feedback From Friends | Materials Studied In This Module | - Always be good to others (Treat others as you want to be treated)- I will go for girls only after my degree program.- Try to be more cool and less talkative- Try to be maintaining my temper and talk in a cool voice. | - I learn how to write CV (curriculum vitae), Cover letter.- I also learn how to behave ethically i.e. know the consequences for what i have done.- To know how to dress, talk in public and presentations. | Practical Implication Of Continuing Pursuit In Information Technology Field | The practical implication of this area of computing after education is that, with time new technologies are invented and you need to go for short courses e.g. for six months, and make yourself updated with new technology. One of the most implications is that you must keep learning as far as information technology is concerned or else you will be of less importance in the information technology society. | APPENDIX C
INTERVIEW LETTER/ QUESTIONAIRE QUESTIONS

APPENDIX D
USE CASE SPECIFICATION/ DESCRIPTION
D.0 CHANGE PASSWORD
Table 4.0: Change Password | Function Name | Register Lecturer | Actor | Student | Description | This use case will allow Student to change their password. | Primary Actors | Student. | Output | Nil | Pre-Condition | Student must have a valid user name. | Post-Condition | Student must be logged in to the system. | Constraints | Student must be registered in the system. | FLOW OF EVENTS | Basic Flow | * The use case begins when Student clicks on Change password button on the home page (index). * System displays Change Password form. * Student keys in his User name. * Student keys in his email address. * Student keys in new password. * Student re-enter password. * Student clicks on Change Password Button. * System would verify information. * System displays Password Changed Successfully. | Alternative Flow | * A1: Cancel | Exceptional Flow | * E1: fill in details. Please wait * E2: Password did not match, please try again. | D.1 UPDATE STUDENT DETAILS
Table 5.0: Update Student Details | Function Name | Update Student Details | Actor | Administrator | Description | This use case will allow Administrator to update student details in the system. | Primary Actors | Administrator. | Output | Nil | Pre-Condition | Administrator must be registered in the system. | Post-Condition | Administrator must be logged in to the system. | Constraints | N/A (Not Applicable) | FLOW OF EVENTS | Basic Flow | * The use case begins when Administrator clicks on Update Student Details button on the home page (index). * System displays Update Student form. * Administrator keys in Student Matrix card number. * Administrator clicks on Search button or enter button. * System displays student information or details. * Administrator will update student details. * Administrator clicks on Update Student Details Button | Alternative Flow | * A1: Cancel * A2: Clear Field | Exceptional Flow | * E1: Textboxes cannot be empty. * E2: Matrix card number does not exist. * E3: No user found, please try again. | D.2 UPDATE LECTURER DETAILS
Table 6.0: Update Lecturer Details | Function Name | Update Lecturer Details | Actor | Administrator | Description | This use case will allow Administrator to update Lecturer’s details in the system. | Primary Actors | Administrator. | Output | Nil | Pre-Condition | Administrator must be registered in the system. | Post-Condition | Administrator must be logged in to the system. | Constraints | N/A (Not Applicable) | FLOW OF EVENTS | Basic Flow | * The use case begins when Administrator clicks on Update Lecturer button on the home page (index). * System displays Update Lecturer form. * Administrator keys in Lecturer’s Passport Number. * Administrator clicks on Search button or enter button. * System displays Lecturer information or details. * Administrator will update Lecturer details. * Administrator clicks on Update Lecturer Details Button. * System would verify information. * System displays “Lecturer’s details successfully updated”. | Alternative Flow | * A1: Cancel * A2: Clear Field | Exceptional Flow | * E1: Textboxes cannot be empty. * E2: Matrix card number does not exist. * E3: No user found, please try again. |

D.4 CREATE TIME TABLE
Table 8.0: Create Time Table | Function Name | Create Time Table | Actor | Administrator | Description | This use case will allow Administrator clicks on create time table button on the home page. | Primary Actors | Administrator. | Output | Nil | Pre-Condition | Administrator must be logged in to the system. | Post-Condition | N/A (Not Applicable) | Constraints | N/A (Not Applicable) | FLOW OF EVENTS | Basic Flow | * The use case begins when user’s clicks on Create time table Button on the home page. * System displays Create time table form. * User keys in Course * User keys in venue location. * User key in group * Administrator clicks on Create time table Button. * System would verify information. * System display “Time table successfully created”. | Alternative Flow | * A1: Cancel. * A2: Clear Field. | Exceptional Flow | N/A |

D.5 DELETE STUDENT
Table 9.0: Delete Student | Function Name | Delete Students | Actor | Administrator | Description | This use case will allow Administrator to delete students. | Primary Actors | Administrator. | Output | Nil | Pre-Condition | Administrator must be logged in to the system. | Post-Condition | N/A (Not Applicable) | Constraints | N/A (Not Applicable) | FLOW OF EVENTS | Basic Flow | * The use case begins when user’s clicks on Delete Student on the home page (index). * System displays Delete Student form. * Administrator selects student * Administrator clicks on Delete Student Button. * System would verify information. * System displays Student Deleted Successfully. | Alternative Flow | * A1: Cancel. * A2: Clear Field. | Exceptional Flow | * E1: Textboxes cannot be empty. * E2: Matrix card number does not exist. * E3: No user found, please try again. | D.6 DELETE LECTURER
Table 10.0: Delete Lecturer | Function Name | Delete Lecturer | Actor | Administrator | Description | This use case will allow Administrator to delete Lecturer. | Primary Actors | Administrator. | Output | Nil | Pre-Condition | Administrator must be logged in to the system. | Post-Condition | N/A (Not Applicable) | Constraints | N/A (Not Applicable) | FLOW OF EVENTS | Basic Flow | * The use case begins when user’s clicks on Delete Lecturer button on the home page (index). * System displays Delete Lecturer form. * Administrator selects student * Administrator clicks on Delete Student Button. * System would verify information. * System displays Student Deleted Successfully. | Alternative Flow | * A1: Cancel. * A2: Clear Field. | Exceptional Flow | * E1: Textbox cannot be empty. * E2: no user found, please try again * E3: Matrix card number does not exist. |

D.9 VIEW INFORMATION
Table 13.0: View Information | Function Name | View Information | Actor | Lecturer | Description | This use case will allow Lecturer to view their information. | Primary Actors | Lecturers | Output | Nil | Pre-Condition | Lecturers must be logged in to the system. | Post-Condition | N/A (Not Applicable) | Constraints | Lecturers must be logged in to the system. | FLOW OF EVENTS | Basic Flow | * The use case begins when Lecturer clicks on View Information Button on the Home page. * System displays Lecturers information form. * Lecturer keys in Matrix Card Number. * Lecturer clicks on Search button or Enter Button. * System displays Lecturers details. * System would verify information. * System display’s Lecturer’s information. | Alternative Flow | * A1: Cancel. * Clear Field. | Exceptional Flow | * E1: Textbox cannot be empty. * E2: Matrix Card Number does not exist. |

APPENDIX E
SEQUENCE DIAGRAM
E.1 Sequence Diagram of Legenda Online Student Time Table System

Figure 1.0: Academic Year Sequence Diagram

E.2 Sequence Diagram of Add course sequence diagram

E3 Add Lecturer Sequence diagram

E5 Add Venue Sequence Diagram

E6 Change Password Sequence Diagram

E7 Delete Lecturer Sequence Diagram

E7 Edit Course Sequence diagram

E9 Edit Lecturer Sequence diagaram

E9 Edit Timetable Sequence Diagram

E10 Edit Venue Sequence Diagram

E11 Login Sequence Diagram

E12 Print Timetable Sequence Diagram

E.13 SEQUENCE DIAGRAM OF UPDATE LECTURER
Figure 5.0: Sequence diagram of Update Lecturer

E.4 SEQUENCE DIAGRAM OF UPDATE STUDENT DETAILS
Figure 6.0: Sequence diagram of Update Student Details

E.15 SEQUENCE DIAGRAM OF VIEW INFORMATION
Figure 8.0: Sequence diagram of View Information

E.16 SEQUENCE DIAGRAM OF ASSIGN COURSE TO LECTURER
Figure 9.0: Sequence diagram of Assign Course To Lecturer

E.17 SEQUENCE DIAGRAM OF CHANGE PASSWORD
Figure 10.0: Sequence diagram of Change Password

APPENDIX F
COLLABORATION DIAGRAM
F1 Login Collaboration Diagram

F2: Add Course Collaboration Diagram

F3 Add Lecturer Collaboration diagram F4 Add Venue Collaboration diagram

F5 Change Password Collaboration diagram

F6 Delete Course Collaboration diagram

F8 Delete Lecturer Collaboration Diagram

F9 Delete Venue Collaboration diagram

F10 Edit Course Collaboration diagram

F11 Edit Lecturer Collaboration diagram

F12 Edit Timetable Collaboration diagram

F13 Edit Venue Collaboration diagram

F14 MyProfile Collaboration diagram

F15: Create Timetable Collaboration diagram

APPENDIX G
ACTIVITY DIAGRAM G.0 DELETE STUDENT ACTIVITY

Figure 4.0: Delete Lecturer Activity Diagram

G.1 LOGIN BUTTON ACTIVITY
Figure 5.0: Delete Student Activity D

G.2 REGISTER LECTURER ACTIVITY Figure 7.0: Register Lecturer Activity diagram

G.3 REGISTER STUDENT ACTIVITY

Figure 8.0: Register Student Activity diagram

G.4 SEND TO EMAIL ACTIVITY
Figure 9.0: Send to Email Activity diagram

G.5 UPDATE LECTURER ACTIVITY
Figure 9.0: Update Lecturer Activity diagram

G.6 UPDATE STUDENT ACTIVITY
Figure 10.0: Update Student Activity diagram

G.7 UPLOAD FILE ACTIVITY
Figure 11.0: Upload File button Activity diagram

G.7 VIEW INFORMATION ACTIVITY
Figure 12.0: View Information Activity diagram

G.8 DELETE LECTURER ACTIVITY
Figure 13.0: Delete lecturer activity diagram

APPENDIX H
STATE CHART DIAGRAM

H.1 DELETE STUDENT ACTIVITY

Figure 4.0: Delete Student Activity diagram

H.2 ADD LECTURER STATE CHART

Figure 4.0: ADD Lecturer State chart diagram

H.3 ADD STUDENT STATE CHART DIAGRAM

Figure 5.0: ADD Student State chart diagram

H.4 CHANGE PASSWORD STATE CHART DIAGRAM

H.5 ADD LECTURE STATE CHART DIAGRAM

H6 Add Venue State chart diagram

H7 Change Password State Chart Diagram

APPENDIX I
STORY BOARD
I1 LOGIN Title #1: Legenda Online Student Time Table System

Logo
Home
Submit
Username
Password
Forget password
Footer
About
SLIDING PICTURE
Title #1: Legenda Online Student Time Table System

Logo
Home
Submit
Username
Password
Forget password
Footer
About
SLIDING PICTURE
Contact Info.
Contact Info.
Help
Help
Courses
Courses |

Figure5. 16: Login storyboard

Logout
Logout
Academic Year
Academic Year
Venues
Venues
Student
Student
Lecturers
Lecturers
Courses
Courses
My Profile
My Profile
Logo
Logo
Title #1: Legenda Online Student Time Table System
Title #1: Legenda Online Student Time Table System
Footer
Footer |
I2 ADMINISTRATOR PAGE

Figure5. 17: Administrator Storyboard

I3 View Courses Logo
Logo
Title #1: Legenda Online Student Time Table System
Title #1: Legenda Online Student Time Table System
Courses
Courses

Add Course
Add Course Select a course by the left to preview here
Select a course by the left to preview here
Picture
Picture
Footer
Footer |

Figure5. 18: View Courses Story Board

I4 Add Courses Logo
Logo
Title #1: Legenda Online Student Time Table System
Title #1: Legenda Online Student Time Table System
Courses
Courses

Add Course Button
Add Course Button
Create Button
Create Button
Add New Course
Add New Course
Text Box
Text Box
Title
Title
Dropdown Box
Dropdown Box
Lecturer
Lecturer Dropdown Box
Dropdown Box
Dropdown Box
Dropdown Box
Dropdown Box
Dropdown Box
Text Box
Text Box
Class
Class
Semester
Semester
Year
Year
Course Code
Course Code
Footer
Footer | Figure5. 19: Add Course Storyboard

I5 Edit Courses Logo
Logo
Title #1: Legenda Online Student Time Table System
Title #1: Legenda Online Student Time Table System
Courses
Courses

Delete Button
Delete Button
Save Button
Save Button
Information System Information System

Add Course Button
Add Course Button
Text Box
Text Box
Title
Title
Dropdown Box
Dropdown Box
Lecturer
Lecturer Dropdown Box
Dropdown Box
Dropdown Box
Dropdown Box
Dropdown Box
Dropdown Box
Text Box
Text Box
Class
Class
Semester
Semester
Year
Year
Course Code
Course Code
Footer
Footer | Figure5. 20: Add Course Storyboard

I6 Delete Courses Logo
Logo
Title #1: Legenda Online Student Time Table System
Title #1: Legenda Online Student Time Table System
Courses
Courses
Edit Button
Edit Button
Delete Button
Delete Button

Information System Information System

Text Box
Text Box
Lecturer
Lecturer
Course Code
Course Code
Text Box
Text Box Text (Link)
Text (Link)
Text
Text
Class
Class
Semester
Semester
Year
Year
Text Box
Text Box
Text Box
Text Box
Text Box
Text Box
Footer
Footer |

Figure5. 21: Delete Course Storyboard

I7 ADD LECTURER Logo
Logo
Title #1: Legenda Online Student Time Table System
Title #1: Legenda Online Student Time Table System
Courses
Courses
Create Button
Create Button

Add Course Button
Add Course Button
Text Box
Text Box
Name
Name
Passport
Passport
Text Box
Text Box Text
Text
Qualification
Qualification
Phone
Phone
Email
Email
Country
Country
Drop Down
Drop Down
Text Box
Text Box
Text Box
Text Box
Footer
Footer | Figure5. 22: Add Lecturer Storyboard

I8 EDIT LECTURER Logo
Logo
Title #1: Legenda Online Student Time Table System
Title #1: Legenda Online Student Time Table System
Lecturers
Lecturers
Edit Button
Edit Button
Delete Button
Delete Button

Save Button Save Button

Text Box
Text Box
Lecturer
Lecturer
Passport
Passport
Text Box
Text Box Text (Link)
Text (Link)
Qualification
Qualification
Phone
Phone
Email
Email
Country
Country
Text Box
Text Box
Text Box
Text Box
Text Box
Text Box
Footer
Footer |

Figure5. 23: Edit Lecturer Story Board

I9 DELETE LECTURER Logo
Logo
Title #1: Legenda Online Student Time Table System
Title #1: Legenda Online Student Time Table System
Lecturers
Lecturers
Edit Button
Edit Button
Delete Button
Delete Button

Save Button Save Button

Text Box
Text Box
Lecturer
Lecturer
Passport
Passport
Text Box
Text Box Text (Link)
Text (Link)
Qualification
Qualification
Phone
Phone
Email
Email
Country
Country
Text Box
Text Box
Text Box
Text Box
Text Box
Text Box
Footer
Footer | Figure5. 24: Delete Lecturer Story Board

I10 CREATE VENUE

Logo
Logo
Title #1: Legenda Online Student Time Table System
Title #1: Legenda Online Student Time Table System
Venues
Venues
Create Button
Create Button

Save Button Save Button

Text Box
Text Box
Venue
Venue
Capacity
Capacity
Drop Down
Drop Down Footer
Footer
| Figure5. 25: Create Venue Storyboard

I11 EDIT VENUE Logo
Logo
Title #1: Legenda Online Student Time Table System
Title #1: Legenda Online Student Time Table System
Venues
Venues
Edit Button
Edit Button

Delete Button Delete Button

Text Box
Text Box
Venue
Venue
Capacity
Capacity
Drop Down
Drop Down Footer
Footer
|

Figure5. 26: Edit Venue Storyboard

I12 DELETE VENUE

Logo
Logo
Title #1: Legenda Online Student Time Table System
Title #1: Legenda Online Student Time Table System
Venues
Venues
Delete Button Delete Button Edit Button
Edit Button

Text Box
Text Box
Venue
Venue
Capacity
Capacity
Drop Down
Drop Down Footer
Footer
| Figure5. 27: Delete Venue Storyboard

APPENDIX J
USER MANUAL

USER MANUAL

J.1 USER MANUAL
The proposed system is an Online Timetable System “Legenda Online Student Timetable System” that will be hosted on the internet (online) for Legenda IT Students Only. The above named system will help Legenda IT Students to acquire their Timetable Online by providing their authentication (Username and password). This system makes it easier for students to interact with by the aid of the simple and user friendly interface that are in-built in the system. The User Manual is nothing but a guide for system users (i.e. Administrator and Students) on the flow of the system and how the system functions and how to resolve issues when faced in the system. However, the author shall describe the minimum hardware and software requirements for Legenda Online Student Timetable System.
J.2 HARDWARE REQUIREMENTS
Hardware requirement is the hardware (physical component of computer) of the computer systems. Bhardwaj (2000) states that; hardware requirement determines and tells the author what hardware is required for the proposed system. For example, the hard disk size, the RAM size etc. Below are the lists of the minimum hardware requirement for Legenda Online Student Timetable System, they include:-
Table1. 1: Hardware requirement HARDWARE | MINIMUM | RECOMMENDED | DESCRIPTION | * Random Access Memory (RAM) | * 1GB RAM | * 1GB RAM | * Used to save temporary data. It is also used to when running large programs to speed up system’s performance. | * Hard Disk | * 80GB | * 80GB | * It is a permanent mode of storage in the computer system. The operating system of the computer system is saved in the hard disk. | * Mouse | * Laser mouse | * Optical mouse | * The pointer device that will be used in the proposed system | * Processor | * Pentium 4 processor | * Intel dual core processor or higher processor | * It is a logical circulatory that responds to and processes the basic instructions that drive a computer system. | * Keyboard | * Dvorak Simplified Keyboard | * QWERTY keyboard | * This is a standard keyboard that will be used for the proposed system. | * Monitor | * 15” inch monitor | * 15” or higher inch screen | * This is used to view or display in the proposed system. | * Scanner | * Flatbed scanner | * Ngenuity 9125DC | * It is used to scan documents faster and easier. | * Printer | * Inkjet printer | * Laser printer | * It is an output device that produces text and graphics on paper. |

J.3 SOFTWARE REQUIREMENT
According to Richard (2007), software requirement process is the first step in most software development process because; it allows the development team to determine if the system can be built and delivered in the stipulated time of delivery. Thus, software requirement helps in knowing how to build the proposed system (Legenda Online Student Time Table System) without further delay. Below are the software requirements for Legenda Online Student Timetable System:-
Table1. 2: Software requirement SOFTWARE | MINIMUM | RECOMMENDED | DESCRIPTION | * Database | * MySQL Server | * MySQL Server R2 | * MySQL is a server software that is used to store record in an information system | * Mac OS | * Mac OS X | * Mac OS X | * An operating system that the system will run on | * Windows Operating System (OS) | * Windows Xp | * Windows vista or windows 7 | * This is the operating system that the system will run on | * Design Tool | * Macromedia Dreamweaver, Netbeans and front Page 2003 | * Netbeans | * A software tool used to create and edit sophisticated websites | * Microsoft office | * Microsoft office 2003 | * Microsoft office 2007/2010 | * Software package | * UML tool | * Rational Rose Enterprise Edition 98 | * Rational Rose Enterprise Edition 2003 | * Rational rose is a modeling tools that is used to create use case, class diagram, activity diagram etc. | * Programming Language | * Php | * Php | * Php is a server-side language that the compiler understands when creating and running sophisticated and simple WebPages. E.g. running website in Google chrome | * XAMPP Server | * WAMP Server Version 2.0 | * WAMP Server Version 5.0 | * XAMPP Server is a server site tool that is used to connect web pages to database and run on the web browsers | * Anti-virus | * MacAfee Anti-virus 2010 | * MacAfee Anti-virus 2012 | * A virus detecting and removal tool. It also warns against malware and Trojans |

J.4 NETWORK REQUIREMENT
Network requirement defines what the wireless network needs to do. The network requirements include all the requirements that must be used to connect the proposed system to the internet. The network requirement of the proposed system includes the following: -
Table1. 3: Network requirement SOFTWARE | MINIMUM | RECOMMENDED | DESCRIPTION | * Switch | * Cisco 8-port Standard 10/100 Network Switch (SD216TUK) | * Cisco 16-port Standard 10/100 Network Switch (SD216TUK) | * It is a computer networking device which will connect network segments | * Bridge | * Cisco Linksys Dual- Band N bridge with 4-port Switch (WES610N) | * Cisco Linksys Dual- Band N bridge with 4-port Switch (WES610N) | * Filters data traffic at a network which is very crucial for the proposed system | * Network card | * D-Link N150mbps Wireless N PCI Adapter Card (DWA-525) | * D-Link N150mbps Wireless N PCI Adapter Card (DWA-525) | * It is an expansion card that enable computer to physically connect LAN (local area network) | * Wireless Modem | * TP-Link N300mbps High Gain Wireless N USB Adapter (TL-WN822N) | * TP-Link N300mbps High Gain Wireless N USB Adapter (TL-WN822N) | * It is a wireless connection to the internet. Thus, It connects to a wireless networks. | * Router | * HuaWei E583X MIFI 3.5G Portable router for Galaxy/Playbook/Ipad E585 E... | * HuaWei E583X MIFI 3.5G Portable router for Galaxy/Playbook/Ipad E585 E... | A device that forwards data packets between telecommunications networks | * Network cable | * RJ45 | * RJ45 | A cable that is used for LAN and WAN connection and can be connected to all computer system is network port | * Server | * HP Proliant DL140 G3 Server (1U rack mount) | * HP Proliant DL140 G3 Server (1U rack mount) | To be used to host Legenda Online Student Time Table |

J.5 INSTALLATION INSTRUCTION
Below are the instruction of how to install XAMPP Server for the communication between the WebPages and the server.
Download XamppServer at http://www.apachefriends.org/en/xampp-windows.html * Download the zip folder. * Open and extract the folder * Save it in your desktop * Run the “.EXE” folder by double clicking on it.
Perform the following below:-
Installing XAMPP
Run the installer, eventually you will be presented with an option about where to install the package. We told it to install it in a new folder called C:\X_server, which XAMPP will create. You could use the browse button to point to a location.

Continue with the installation, this will take a while!

http://docs.moodle.org/23/en/File:Xampp3.gif
Installation info screen
Eventually you will be presented with the option to install Apache, MySQL, Filezilla and Mercury as a service.

It’s probably best to choose “No” for now. You can always enable these as services later.
Next you’ll be asked if you want to start the XAMPP Control Panel.

* Click the “No” button. J6 SCREEN SHOTS OF USING LEGENDA ONLINE STUDENT TIME TABLE SYSTEM
The below screen shots will guide the users of the system (Administrator and Students) in operating or interacting with Legenda Online Student Time Table System. This includes the following: -
Table J. 1: Home Page (Login) Screen Shot PAGE: 1 | HOME PAGE SCREEN SHOT | Description | The below picture is the first page of the system. It comprises of the User name and Password (for Administrator and students) in the system. Steps * Admin Username: Tom * Password: confirmSTUDENT * Student matrix ID: USE4-12/09-00099 * Password: TOMNote: Authentication must be provided before accessing system. | |

Username/Matrix ID
Password
Click on “Submit Button”
Username/Matrix ID
Password
Click on “Submit Button”

Table J. 2: My Profile (Administrator) Screen Shot PAGE: 2 | MY PROFILE SCREEN SHOT | Description | Administrator is the actor in this page. All the details saved in the database (i.e. Courses, Lecturers and Students) are displayed in the system.Administrator can be able to view time table in the system Steps * Select year from Drop Down Menu. * Select Semester from Drop Down Menu. * Select Course from Drop Down Menu. * Click on Submit Button.Note: only to view availability of Timetable in the system | |
Select Year
Select Semester
Select Course
Click on “Submit Button”
Select Year
Select Semester
Select Course
Click on “Submit Button”

Table J. 3: Add Course (Administrator) Screen Shot PAGE: 3 | ADD COURSE SCREEN SHOT | Description | Administrator is the actor in this page. All the details saved in the database (i.e. Courses, Lecturers and Students) are displayed in the system.Administrator can be able to view time table in the system Steps * Click on Add Course Button. * Fill up the Add Course Form. * Click on Create Button.Note: this function is to ADD COUSE to the database | | Fill up Form
Click on Create Button

Fill up Form
Click on Create Button

View list of Courses
View list of Courses

Table J. 4: EDIT COURSE (Administrator) Screen Shot PAGE: 4 | EDIT COURSE SCREEN SHOT | Description | Administrator is the actor in this page. The Administrator can easily EDIT course in the system.Steps * Select Course from the List of courses at the left hand side of the page. * Click on Edit Button * Edit Details * Click on Save Button.Note: function to edit a course in the system | |
Fill up Form
Click on Save Button

Fill up Form
Click on Save Button

Table J. 5: DELETE COURSE (Administrator) Screen Shot PAGE: 5 | DELETE COURSE SCREEN SHOT | Description | Administrator is the actor in this page. The Administrator can easily Delete course in the system.Steps * Select Course from the List of courses at the left hand side of the page. * Click on Edit Button * Edit Details * Click on Delete Button.Note: function to Delete a course in the system | |

Select Course
Click on “Delete Button”
Select Course
Click on “Delete Button”

Table J. 5: ADD STUDENT (Administrator) Screen Shot PAGE: 3 | ADD STUDENT SCREEN SHOT | Description | Administrator is the actor in this page. All the details saved in the database (i.e. Courses, Lecturers and Students) are displayed in the system.Administrator can be able to view time table in the system Steps * Click on Add Student Button. * Fill up the Add Student Form. * Click on Create Button.Note: this function is to ADD STUDENT to the database | |

Fill up Form
Click on Create Button
System adds student

Fill up Form
Click on Create Button
System adds student

View list of Courses
View list of Courses

Table J. 5: EDIT STUDENT (Administrator) Screen Shot PAGE: 4 | EDIT STUDENT SCREEN SHOT | Description | Administrator is the actor in this page. The Administrator can easily EDIT Student in the system.Steps * Select Student from the List of courses at the left hand side of the page. * Click on Edit Button * Edit Details * Click on Save Button.Note: function to edit a course in the system | | Fill up Form
Click on Save Button

Fill up Form
Click on Save Button

PAGE: 5 | DELETE STUDENT SCREEN SHOT | Description | Administrator is the actor in this page. The Administrator can easily Delete Student in the system.Steps * Select Student from the List of courses at the left hand side of the page. * Click on Edit Button * Edit Details * Click on Delete Button.Note: function to Delete a course in the system | |
Select Course
Click on “Delete Button”
Select Course
Click on “Delete Button”

Table J. 6: ADD LECTURER (Administrator) Screen Shot PAGE: 6 | ADD LECTURER SCREEN SHOT | Description | Administrator is the actor in this page. The Administrator will be able easily ADD Lecturer in the systems database.Steps * Click on Add Lecturer Button * Fill up form * Click on Create ButtonNote: function to Delete a course in the system | | Click on Add Lecturer Button
Fill up Form
Click on “Create Button”
Click on Add Lecturer Button
Fill up Form
Click on “Create Button”

View list of Lecturers
View list of Lecturers

Table J. 7: EDIT LECTURER (Administrator) Screen Shot PAGE: 7 | EDIT LECTURER SCREEN SHOT | Description | Administrator is the actor in this page. The Administrator can easily Edit Lecturer in the system.Steps * Select Course from the List of Lecturers at the left hand side of the page. * Click on Edit Button * Edit Details * Click on Save Button.Note: function to Edit a Lecturer in the system | | Select Lecturer
Click on Edit Button
Edit Lecturer’s Details
Click on “Save Button”
Select Lecturer
Click on Edit Button
Edit Lecturer’s Details
Click on “Save Button”
View list of Lecturers
View list of Lecturers

Table J. 8: DELETE LECTURER (Administrator) Screen Shot PAGE: 8 | DELETE LECTURER SCREEN SHOT | Description | Administrator is the actor in this page. The Administrator can easily Edit Lecturer in the system.Steps * Select Course from the List of Lecturers at the left hand side of the page. * Click on Edit Button * Edit Details * Click on Save Button.Note: function to Edit a Lecturer in the system | | Select Lecturer
Click on Edit Button
Edit Lecturer’s Details
Click on “Save Button”
Select Lecturer
Click on Edit Button
Edit Lecturer’s Details
Click on “Save Button”
View list of Lecturers
View list of Lecturers

Table J.9: ADD VENUE (Administrator) Screen Shot PAGE: 9 | ADD VENUE SCREEN SHOT | Description | Administrator is the actor in this page. The Administrator will be able easily ADD Venue in the systems database.Steps * Click on Add Venue Button * Fill up form * Click on Create ButtonNote: function to Add a Venue in the system | | Click on Add Venue Button
Fill up Form
Click on “Create Button”
Click on Add Venue Button
Fill up Form
Click on “Create Button”
View list of Lecturers
View list of Lecturers

Table J.10: EDIT VENUE (Administrator) Screen Shot PAGE: 10 | EDIT VENUE SCREEN SHOT | Description | Administrator is the actor in this page. The Administrator will be able easily EDIT Venue in the systems database.Steps * Select a Venue * Click on EDIT Button * Click on Save ButtonNote: function to Edit a Venue in the system | |
View list of Venues
View list of Venues Click on Add Venue Button
Fill up Form
Click on “Create Button”
Click on Add Venue Button
Fill up Form
Click on “Create Button”

Table J.11: DELETE VENUE (Administrator) Screen Shot PAGE: 11 | DELETE VENUE SCREEN SHOT | Description | Administrator is the actor in this page. The Administrator will be able easily DELETE Venue in the systems database.Steps * Select a Venue * Click on Delete ButtonNote: function to Delete a Venue in the system | |
Click on Edit Venue Button
Fill up Form
Click on “Delete Button”
Click on Edit Venue Button
Fill up Form
Click on “Delete Button”
View list of Venues
View list of Venues

Table J.12: ACADEMIC YEAR (Administrator) Screen Shot PAGE: 11 | ACADEMIC YEAR SCREEN SHOT | Description | Administrator is the actor in this page. The Administrator will be able easily ACADEMIC YEAR in the systems database.Steps * Click on Academic Year button. * Click on User list button. * Click on View Timetable Button. * Click on Create Timetable ButtonNote: function to Delete a Venue in the system | |
Select Course
Select Venue
Select Group
Click on “Create Timetable Button”
Select Course
Select Venue
Select Group
Click on “Create Timetable Button”

Table J.13: ACADEMIC YEAR (Administrator) Screen Shot PAGE: 13 | TIMETABLE SCREEN SHOT | Description | Administrator is the actor in this page. The Administrator will be able easily TIMETABLE in the systems database.Steps * View created TimetableNote: function for create Timetable creates 3 groups in the system. | |
Timetable for Group One
Timetable for Group One

Table J.14: DELETE TIMETABLE (Administrator) Screen Shot PAGE: 14 | DELETE TIMETABLE SCREEN SHOT | Description | Administrator is the actor in this page. The Administrator will be able easily DELETE TIMETABLE in the systems database.Steps * Click on Academic Year * Select a course and year (e.g. Year1 sem1, BIS) * Click on View Timetable * Click on Delete ButtonNote: function for create Timetable creates 3 groups in the system. | |
Click on Delete Timetable Button
Click on Refresh Button
Click on Delete Timetable Button
Click on Refresh Button

Table J.15: MY PROFILE (Student) Screen Shot PAGE: 15 | MY PROFILE TIMETABLE SCREEN SHOT | Description | Student is the actor in this page. The Student will be able easily View MYPROFILE in the systems database.Steps * After login to the system. * System will redirect students to the MYPROFILE page. * Student will view his details * Student will also view LecturersNote: function My Profile in the system. | |

Table J.16 MY SETTINGS (Student) Screen Shot PAGE: 16 | MY SETTINGS TIMETABLE SCREEN SHOT | Description | Student is the actor in this page. The Student will be able easily View MYSETTINGS in the systems database.Steps * Click on MY Settings Button * Update Username * Update Current Password * Confirm New Password * Click on Update ButtonNote: function My Profile in the system. | |

Update Username

Update Username

Enter Current Password
Enter New Password
Confirm New Password
Enter Current Password
Enter New Password
Confirm New Password

Table J.17 MY TIMETABLE (Student) Screen Shot PAGE: 17 | MYTIMETABLE SCREEN SHOT | Description | Student is the actor in this page. The Student will be able easily View MYTIMETABLE in the systems database.Steps * Click on MY Timetable Button * System Displays Timetable (based on the group you are in). * Click on Print Button.Note: function allows students to print timetable based on their group | |

APPENDIX K
LOG SHEETS

APPENDIX L
GANTT CHART

L.1 CHAPTER 6 GANTT CHART

L.2 CHAPTER 7 GANTT CHART

L.3 CHAPTER 8 GANTT CHART