CHAPTER FOUR
SYSTEM IMPLEMENTATION AND DOCUMENTATION
4.0 INTRODUCTION
This chapter focuses on the system implementation. It consists of the
system design diagram, choice of programming language, analysis of
modules, programming environment, hardware and software
requirements as well as system testing and implementation.
4.1 System Design Diagram
LOGIN
MAIN MENU
REGISTRATION EDIT RECORDS QUIT
SAVE UPDATE PRINT
CLOSE CLOSE CLOSE
Fig 4.1: System Design Diagram
4.2Choice of the Programming Language
The programming language used for implementing this research work is
Visual BASIC. NET. This programming language helps to develop
program that runs in all platform with a user friendly interface.
4.3 Analysis of Modules
MODULE 1 (Registration): This module allows new allocation of
course and time table to be registered in the database.
MODULE 2 (Edit order): This module allows for modifying and
updating in the database.
MODULE 3 (View database): This module allows lecturer’s
information to be viewed and printed.
MODULE 4 (Quit): This module enables the user to quit the system or
application.
4.4 PROGRAMMING ENVIRONMENT
The programming environment used for the development of the system is
Windows 7 operating system.
4.4.1 Hardware Requirements
Table 4.1: Hardware Requirement
Component Requirement
RAM 512MB of RAM
Hard disk 10GB of hard disk space
Processor 333Hz or higher
UPS A functional one
Keyboard A functional one
Mouse A functional one
Computer system Pentium iv
4.4.2 software Requirements
Table 4.2: software Requirement
Component Requirement
Operating system Windows 7
Memory 128MB or higher
Database Microsoft Access 2003
Programming Language Microsoft Visual Basic 6.0
4.5 System Implementation
This software will be implemented by system designer and programmer.
This is done in order to select and debug errors.
Thus the phase is also called system testing. The users of the software
may design a system prototype in order to consider the new and the old in
contrast.
4.6 Software Testing
The system was tested at every stage of its development in order to be
able to detect errors and remove them immediately. The testing was done
in two phases as discussed below:
Modular Testing: all the modules of the system were independently
tested to ensure that they are working properly.
System Testing: in this phase all the modules are integrated and the
system with all its modules is tested to identify and remove errors that
may arise as a result of the integration.
CHAPTER FIVE
SUMMARY, CONCLUSION AND RECOMMENDATIONS
5.0 Introduction
This chapter focuses on summary, constraints of the study, conclusion
and recommendations for the users and future researchers who may want
to review this work.
5.1 Constraints of the Study
The problems I encountered during the course of carrying out this
research project include:
Time: Time for the research project was too short coupled with
researcher’s academic time table.
Fund: There was limited fund to take care of the research properly
in terms of transportation and other expenses especially when
visiting attraction sites.
Research Materials: Lack of access to research materials on the
topic in the school library and even public libraries were also major
constraint in the cause of this project.
5.2 Summary
Automated Course allocation and timetable system help the management to
handle and ease the job of course allocation for the lecturers. The system
will help lecturers to be allocated with different courses based on their field
of expertize. The new system would be very easy to use because of its
accuracy and reliability, information about the lecturer’s and the courses
allocated can be promptly assessed easily.
5.3 Conclusion
This project has successfully developed an automated course allocation
and timetable system using computer science department, as case study.
The work will go a long way to offer a lasting solution to the problem of
manual course allocation and timetable in FCAH&PT
5.4 Recommendations
Having designed, tested and implemented the new system, the following
must be put in place to fully achieve the objective of which the software
is designed for:
1. Maintenance: the system needs to be maintained. This implies that
any fault detected should be reported to the programmer for
correction at point in time.
2. Research: More research should be conducted on the topic to
assess it effectively.
3. The staff should be computer literate and competent enough to
manipulate the system.
4. There should be constant power supply to keep the system active.
