CHAPTER FOUR

SYSTEM IMPLEMENTATION

4.1 INTRODUCTION

In this chapter, the development and implementation of the new system were

discussed, included in this chapter were the change over method adopted, the

choice of programming languages used in designing of the program and

minimum system requirements for the hardware and software for proper

functionality of the program.

4.2 SYSTEMS REQUIREMENTS

This application may not run effectively if the minimum system

specification is not met therefore, there is need to install a proper system

hardware and software required for the application to meet up the objective

as stated.

4.2.1 Hardware Requirements

Processor : Intel Core Duo 2.0 GHz or more

RAM : 1 GB or More

Harddisk : 80GB or more

Monitor : 15” CRT, or LCD monitor

Keyboard : Normal or Multimedia

Mouse : Compatible mouse

4.2.2 Software Requirements

Front End : Python for the server-side implementation.

Back End : my SQL

Operation System : Windows 7 and above

4.3 SYSTEM CONTROL

System Flow:

1. System Initialization: The system initializes, and the Maintenance

Scheduler creates a schedule based on system resources and

configuration.

2. System Monitoring: The System Monitor continuously monitors

system performance, detecting potential issues.

3. Task Scheduling: The Maintenance Scheduler schedules maintenance

tasks based on system resources, usage patterns, and priority.

4. Task Execution: The Task Executor executes scheduled maintenance

tasks.
 5. Notification: The Notification Manager sends notifications about

upcoming maintenance, completed tasks, or issues detected.

6. System Update: The system updates its configuration, schedules, and

performance data in the database.

System Components:

1. Maintenance Scheduler: A module that schedules maintenance tasks

based on system resources, usage patterns, and priority.

2. Task Executor: A module that executes scheduled maintenance tasks,

such as software updates, disk cleanups, and performance monitoring.

3. System Monitor: A module that continuously monitors system

performance, detecting potential issues and triggering maintenance

tasks as needed.

4. Notification Manager: A module that sends notifications to system

administrators or users about upcoming maintenance, completed

tasks, or issues detected.

5. Configuration Manager: A module that allows administrators to

configure maintenance settings, such as scheduling, task

prioritization, and notification preferences.

4.5 SYSTEM INTERFACE

1. Login Screen: A simple login screen for system administrators to

access the system.

2. Dashboard: A dashboard displaying system performance metrics,

upcoming maintenance schedules, and recent task history.

3. Maintenance Scheduling: A page for scheduling maintenance tasks,

selecting tasks, and setting priorities.

4. Task History: A page displaying completed maintenance tasks,

including details and logs.

5. System Monitoring: A page displaying real-time system performance

metrics and potential issues.

6. Configuration: A page for configuring system settings, such as

notification preferences and maintenance schedules.

7. Notification: A page displaying notifications about upcoming

maintenance, completed tasks, or issues detected.

4.5.2 System Testing

There is need to ensure that the individual website have been correctly

written and that the system will be error-free during execution. This is

achieved by provision of test data for program testing and procedure testing.
The general testing includes:

1. UNIT TESTING

This involves breaking down the program into its individual units and

testing it to see if units functions as intended. The various subroutines

and modules that are involved in writing the program individually

tested and correction made as well.

2. INTEGRATION TESTING:

This is the second step that is involved in testing the program. It

involves bringing together the various individual modules involved in

the program and testing them to see how well they interact with one

another in terms of data transfers and processing. This involves testing

the program as to see if it functions in order.

3. VALIDATON TESTING:

In this case, the testing attention is one the program as a whole and it

is tested, according to the specification of the program so given. Date

time, valid and invalid data are introduced into the program and their

result is examined to see if the system is working properly.

Generally, the test data for the program testing is designed into ensure that

all parts of the system are put together as expected. It involves the clerical

procedures such as input, processing and output. Also under security at this

state is the expected volume of data efficiently.

4.5.3 Training and Re-Training of Staff

The training of staff use the proposed new system effectively solely depends

on the quality of staff available and the skills they already had. This is

necessary to ensure that all persons involved in the implementation of the

new system are capable of making it operationally successful. This can be

advanced through, handbooks developed from the system specification,

course full-time or part time often number by the computer manufacturer

and lecturer.

4.5.4 File Conversion

This involves the conversion of old file into the form required by the new

system since the overall objectives of the system implementation is to ensure

more and orderly change over from the old to the new system.
4.5.5 Changeover Procedure

There are two method of changing over of new system they are:

i) Parallel change over techniques

ii) Direct change over techniques.

In the parallel technique, the old and new system runs concurrently utilizing

the same inputs. The outputs are correlated for the purpose of resolving any

differences that is noticed unit the system attains perfection.

In the direct system change over techniques, the old system is discontinued

summarily while the new system is made operational immediately. The

parallel change over technique is chosen, for this project, as a changeover

technique can be easily assimilated.

4.5.7 Maintenance Details

The system and application installed cannot function effectively forever

without maintenance and update. This is to say in effect that the system from

time to time needs proper maintenance such as cleaning up the different

parts and removing away dust particles, changing old and worn out
components of the system. Software maintenance and update is not left out

as IDE all known that things change innovations; such becomes imperative

that the software needs updating so as to accommodate innovation. This can

easily be updated by the programmer (researcher) periodically for the

following reasons:

1. To deal with unforeseen problem ensuring in operation, example

program may need to be modified to deal with unforeseen

circumstance.

2. To confirm that the planned objective are being met and to take

action if they are not

3. To ensure that the system is able with the changing requirements

of business.

To confirm the realization of the set objective as a guide to future system

analysis and design assignments. Exercise that needs to be carried upon the
system always fro effective and accurate output.