Computerized Learning And Teaching Management System
[A CASE STUDY OF COMPUTER SCIENCE DEPARTMENT]

CHAPTER FOUR
4.0    SYSTEM IMPLEMENTATION AND DOCUMENTATION
4.1    SYSTEM IMPLEMENTATION
System implementation depicts all the procedures or activities that are carried out to put the computerized learning and teaching management system into use. Activities of this stage include identifying the hardware and software requirements, functional and non-functional requirements that is required to run the system smoothly.
4.1.1    OVERALL REQUIREMENTS OF THE SYSTEM
Several classifications of requirements are to be attained before the system can be fully implemented. Some of the classifications of the system requirements are explained below;
i.    Hardware Requirements
For this system to work effectively, hardware compatibility should be a major concern to look into. Below are the required hardware requirements to be used:
a.    Celeron M®, Processor(Intel Core(TM) Duo Core
b.    1GB of RAM(Random Access Memory)
c.    SuperVGA Colour Monitor(1280px * 800px)
d.    I/O Devices e.g Keyboard, Mouse etc.
e.    Uninterrupted Power Supply (UPS) & Stabilizer.
ii.    Software Requirements
a)    Windows XP & above
b)    WampServer(MySQL/Apache Server/PHP)
c)    Web Browsers (Google Chrome, Mozilla Firefox).
d)    Firewall Security like AVG Internet Security or Kaspersky Antivirus
iii.    Functional Requirements
It defines a function of a software system or its component. A function is described as a set of
inputs, the behaviour, and outputs (see also software). Functional requirements may be
calculations, technical details, data manipulation and processing and other specific functionality that define “what” a system is supposed to accomplish. Behavioural requirements describing all the cases where the system uses the functional requirements are captured in use cases. Functional requirements    are    supported    by non-functional    requirements (also    known    as quality requirements), which impose constraints on the design or implementation (such as performance requirements, security, or reliability). Generally, functional requirements are expressed in the form "system must do <requirement>", while non-functional requirements are "system shall be
<requirement>". The plan for implementing functional requirements is detailed in the system design. Below are some functional requirements of the system;
i.    The system shall keep track of all the details of registered students that will be required to have access to the learning resources.
ii.    The users (students) will be required to sign up as a member before they can have access to the learning resources.
iii.    Users are required to fill all information/fields provided on the signup page.
iv.    Each user shall have a primary key (matriculation number) which be required during the login stage.
v.    Each user shall supply his registration number and password upon request on the signing page.
vi.    Each user shall be allocated a session username using the Registration number supplied during login.
vii.    Each user will be able to change his/her password by supplying his/her registration number, old password and the new password.
viii.    Each user shall select his/her department in order to access the learning resources pertaining to the selected department.
ix.    Each user shall be able to view courses, course descriptions and outline, timetable after performing step viii. User can also save/download or print the resources after viewing or in case it has to be viewed later.
x.    Each user can also have access to other learning resources by selecting other departments.
xi.    Each user must log out after he/she is through to avoid illegal actions like password change or account update by an unauthorized users.
iv.    Non-functional Requirements
These are requirements that are not directly concerned with the specific functions delivered by the system. They may relate to emergent system properties such as reliability, response time and storage, reusability, etc. Alternatively, they may define constraints on the system such as the capabilities of I/O devices and the data representations used in system interfaces.
Non-functional requirements should be defined when you are also creating and writing functional requirements. These are requirements that discuss the constraints and quality standards that the system you are building should adhere to. Below are the examples of non- functional requirements that were given consideration: 
a.    Reliability: Reliability is the chance that the system processes work correctly without being aborted. The system shall be very reliability in terms of the functions is to perform.
b.    Reusability: The system can be reused in the sense that it will save the university the cost of re-designing and also reduces stress.
c.    Visibility: Visibility discusses how the system looks to user. The user interface shall also be interactive enough, a visible fonts and colour shall also be provided.
d.    Maintainability: Maintainability is a measure of how easy it is to correct defects in the software. The system shall also be maintained by the Administrator.