CHINHOYI UNIVERSITY OF TECHNOLOGY

DEPARTMENT OF ICT AND ELECTRONICS

BACHELOUR OF SCIENCE IN INFORMATION

TECHNOLGY

REG SURNAME NAME PROGRAM

NUMBER
C21146118N FONSO CALVIN M BSIT
C21145260U MUPINDU BLESSING J BSIT
C21146750M ZULU RONALD T BSIT
C21147478L MARERE CARLTON BSIT
C21146832C GOREDEMA AUDREY BSIT
C21145918K CHARI PATIENCE BSIT
C21146996P MARONGWE TINOTENDA BSIT
F.D.S ENROLLING
AND SCHEDULING
SYSTEM
Table of Contents
Introduction ................................................................................................................................................. 5
System Overview ......................................................................................................................................... 5
Design Considerations ................................................................................................................................ 5
Goals and Guidelines .............................................................................................................................. 5
General Constraints ................................................................................................................................ 5
Development Method .............................................................................................................................. 6
System Context ............................................................................................................................................ 6
System Architecture.................................................................................................................................... 6
Data Design .............................................................................................................................................. 6
Entity Relationship Diagram ............................................................................................................. 7
E.R.D. Descriptions ............................................................................................................................. 8
CLASS DIAGRAM ............................................................................................................................. 8
DATA DICTIONARY ...................................................................................................................... 10
Program Structure ................................................................................................................................ 11
Overall plan ....................................................................................................................................... 11
Overview of Program functionality and responsibilities ............................................................... 11
Detailed System Design............................................................................................................................. 12
Description of the User Interface ......................................................................................................... 12
1. Progress Report Form .............................................................................................................. 12
2. Enrolment Form........................................................................................................................ 13
3. Manager form............................................................................................................................ 14
4. Instructor’s form ....................................................................................................................... 15
Description for Components ................................................................................................................ 16
Restriction, Limitations and Constraints................................................................................................ 17
Software Design
Documentation
Project Name: F.D.S Enrolling and Scheduling System
Date: 05 December 2022
Arthurs: GOREDEMA AUDREY
FONSO CALVIN M
MARONGWE TINOTENDA H
ZULU RONALD T
MUPINDU BLESSING P
CHARI PATIENCE
MARERE CARLTON
Introduction
This documentation describes the design for Forecast Driving School’s Enrolling and Scheduling system
(F.D.S Enrolling and Scheduling System).

System Overview
The F.D.S Enrolling and scheduling system is a custom designed software application created for
Forecast Driving School. This system was built in order to replace the old system (manual system), which
caused many problem for all the employees at that company. The software will contain the following
functions:
1. User login verification function
2. Learner enrolment function
3. Report editing and viewing functions
4. Report editing and viewing functions

Design Considerations
Goals and Guidelines
The following requirements are for the new system:

 The new system should be more secure in managing student records and reliable enough to be
used in any condition.
 A system that is able to store information of learners, also the information is to be kept in a
logical manner in the database to avoid the mixing of data.
 For a system that can easily search for information about learners.
 A system that has a register in order to count down the number of lessons remaining for every
registered learner.
 A system that provides a progress report to learners and to the manager.
 Finally, it should prove cost effective as compared to the current system.
The following features of the new system were based on the demands of the clients and also, it was
designed in order to make life easy for them. The following features were added:
1. User-friendly
The proposed system is user-friendly since data is efficiently preserved and is quickly retrieved
and stored. Furthermore, the suggested system's interface makes it very simple for users to
interact with it.
2. Generation of reports
Reports can be easily generated in the proposed system so user can generate the report as per the
requirement (daily, weekly).
3. Secure passwords
The proposed system is ensuring that authorized users can access sensitive information regarding
lessons reviews, schedules and learners.

General Constraints
Time
We only have about a month to finish all documentation, software creation and enhancements. We have a
lot of ideas but cannot implement them due to time constraint.
Funding
To develop and implement the software application, we will need a lot of funding for this. Therefore, the
company must be have a reasonable budget should we decide to pursue this function.

Development Method
An agile development methodology will be used to produce the suggested system development for the
Enrolling and Scheduling system. Throughout the development lifecycle, the agile development process
offers opportunity to evaluate the course of a project. This is accomplished by teams presenting a
potentially shippable product increment at the conclusion of frequent work cycles known as sprints or
iterations. Agile methodology is characterized as "iterative" and "incremental" since it emphasizes both
the functional product they produce and the repeating of condensed work cycles. Development teams
working on waterfall projects only get one shot to get each project component properly. Every component
of development, including requirements, design, etc., is continuously reviewed throughout the lifecycle in
an agile paradigm. Every time we complete a cycle, we pause, test it with our client, and then solicit
feedback so we can adjust as necessary. Without it, the project won't proceed in the appropriate way. The
goal of our project is to create sub-systems depending on the requirements made by the user/client.

System Context
Eventually, multiple users will be using the product simultaneously. Therefore, the school will need to
acquire or buy quite a large number of laptops for implementation. Adding on, there should be at least one
employee that should always be ready to assist new learners who may need help with the system.

System Architecture
Data Design
Entity Relationship Diagram

SURNAME
NAME NEXT OF KEEN’S
CELL NUMBER

DATE
IS
LEARNER RECORDED
IN
GENDER

NEXT OF
CELL
KEEN
NUMBER
LESSON
NATIONAL INSTRUCTOR
ID PK NAME TIME

IS REGISTER
GIVEN
DATE

STUDENT STUDENT
TIME DURATION NAME SURNAME

STUDENT
PROGRESS
SURNAME
REPORT
COMPLETES
DATE COMMENTS

STUDENT
NAME
INSTRUCTOR

WRITES INSTRUCTOR

NAME
E.R.D. Descriptions

Progress
Learner Is given report

One learner is given one progress report and one progress report is assigned.

Progress
Instructor writes
report

One instructor can write many progress reports.

Instructor complete Register

One instructor completes many registers.

Learner Recorded Register

in

Many learners can be registered in one register.

CLASS DIAGRAM
LEARNER
NAME

SURNAME Records

NEXT OF KEEN

NEXT OF KEEN CELL

NUMBER REGISTER
GENDER INSTRUCTOR NAME

CELL NUMBER LESSON

NAT. ID NUMBER PK TIME

DATE

Is given LEARNER NAME

LEARNER SURNAME

PROCESS REPORT
LEARNER NAME

LEARNER SURNAME
Completes
COMMENTS

INSTRUCTOR

DURATION

TIME

DATE INSTRUCTOR
INSTRUCTOR NAME PK
Is written by
DATA DICTIONARY
NAME DESCRIPTION TYPE DATE
Learner A customer registering Entity 25/06/22
for driving lessons
Gender Sex of the learner Attribute 25/06/22
National ID A unique identification Key Attribute 25/06/22
of a learner
Cell phone number Contact number of Attribute 25/06/22
learner
Next of keen Guardian of a learner Attribute 25/06/22
Next of keen cell Contact of guardian Attribute 25/06/22
number
Date Date of learner’s Attribute 25/06/22
classes
Student surname Family name of learner Attribute 25/06/22
Student name A word by which a Attribute 25/06/22
learner is called
Register A record used to mark Entity 25/06/22
the attendance of
learners
Instructor name A word by which a Attribute 25/06/22
person who tutors a
learner is called
Time When the lesson takes Attribute 25/06/22
place
Lesson Subject study to be Attribute 25/06/22
carried out
Progress report A record with Entity 25/06/22
comments and progress
of learner’s performs
Instructor A person who tutors a Entity 25/06/22
learner
Comment Feedback on learner’s Attribute 25/06/22
performance
Duration Time taken to complete Attribute 25/06/22
one lesson
Program Structure
Overall plan

WELCOME
USER

EXIT MANGER INSPECTOR INSTRUCTOR LEARNER

LOGIN LOGIN LOGIN LOGIN

ENROLMENT PROGRESS REGISTER REPORT

FORM REPORT BOOK

TIMETABLE LOGOUT TIMETABLE LOGOUT

PROGRESS PROGRESS
REPORT REPORT

SETTINGS LOGOUT

LOGOUT

Overview of Program functionality and responsibilities

Welcome Page
When the system is starting, a splash screen is shown, with welcoming the user into the software
User-type Page
This is also the login form where the user is required to enter his/her credentials. By entering his/her
credentials, the software will automatically direct the user to the form that he/she is supposed to be shown
according to the user type of the user.
Manager’s Account
In this form, the manager will be able to view the enrolment form where he/she can be able to enroll new
learners, delete information about learners or those who are no longer attending lessons. The manager can
also view the schedule set by the instructors. Lastly, the manager is also able to view the progress report
set by the instructor. Making him/her able to follow up and monitor the progress of the learners.
Instructor’s Account
The instructor is able to confirm the attendance of learners by adding them in the register if they’ve
attended lessons. He/she is also the one who writes schedules lessons for learners to attend. Lastly, the
instructor writes progress reports based on the performance of the learners for both the learners and
manager to view.
Inspector’s Account
Since the main role of the inspector in this company is to monitor the work being carried out by the
instructors, his account only allows him to view progress reports written by instructors for him/her to be
able to monitor all the learners and instructors.
Learner’s Account
In this form, every learner will be able to view his/her progress report by entering his/her name on the
search textbox. His/her name, the date of when the lesson was carried out, the lesson carried out, and the
name of the instructor will show.

Detailed System Design

Description of the User Interface
Below are 2 form for the most crucial functions of the system. These are the Enrolment form which is a
form that can only be view by the manager in order to enroll new learners, and the Progress report form
which can only be viewed by instructors in order to record data on the lessons they carry out with
learners. The images of these forms are shown below:

1. Progress Report Form

This is used in producing a progress report for the learners, inspector and manager to see. The
progress report produced by the instructor containing the progress made by learners.
2. Enrolment Form
This is used to collect data from enrolling learners and keeps this information in a database where
information is stored more efficiently.
3. Manager form
The manager is the one of the people who performs many tasks in the company so the menu
has many single click commands which has forms that can be written. The enrolment form
is where he enters details of enrolling learners and the register button displays a form where
the manager is able to record the attendance of learners.
4. Instructor’s form
The instructor is the one who does the main work. It’s almost like the school is centered
on him. There are several buttons on the instructor’s form, buttons that lead other several
forms like progress reports and an appointment form.
Description for Components
Some of the components such as the ProgressReport have names of the form they will view when they are
clicked. Below are the functions of other the components found on the forms shown above:
Search
To search for information, user can enter the name of the individual in order to manipulate the data of that
particular individual. Once the user enters the name of the individual, the click Search button. All the
information about that individual will be filled in.
Save
When the Save button is clicked, new record will be generated if the same record ID does not exist in the
system, otherwise, current record will be updated.
Delete
The Delete button should be disabled unless no historical data have been found for the facility. The Delete
button will erase data from the system.
Add New
The Add New button will allow the user to record more than 1 record into the system at the same time,
one after the other. Once the user finishes saving data and saves it, he/she can click the Add New button
and will be presented with a new form to enter other details.
Exit
This button will close the current form and view the previous one.
Logout
When this button is clicked, it will exit the account it was logged into. Correct username and password
will be required to log back into the account again.

Restriction, Limitations and Constraints

Time
Time is so far the biggest restriction or constraint for our project as we only have around four weeks to
finish entire project. It is very important for us to watch the time we spend over every phase of the
software development project.
Teammates Skills
Our team’s programming and design skills is also one of the restriction. It does not have as big of an
impact on the project as time but it sure does limit us from doing more addition to the projects.
Insufficient Resources
Not having all the necessary instruments also is a problem for our software. We planned to use more
powerful machines for the project like core i5/i7 machines with bigger memory etc. for our project to run
smoothly, but we can’t afford such equipment for all of us so we had to abandon the plans.