Department Of Information and Communication Technology

Copperbelt University

Table of contents

Chapter 1: INTRODUCTION

1.1 ABSTRACT ..............................................................1

1.2 Introduction...............................................................2
1.3. Problem Statement.................…………..................3
1.4 Goals...........................................................................4
1.5 Objective....................................................................5
1.6 Scope of the Project...................................................6
1.7 MODULES.................................................................6

Chapter 2: DESIGN
2.1 SYSTEM DESIGN:............................................7
2.1.1 INTRODUCTION TO UML................................8
2.2 UML Approach.........................................................9
2.5 Sequence diagram.....................................................10
2.6 Activity diagram.......................................................11
2.7 Deployement diagram..............................................12
Chapter 3 : ANALYSIS

3.1 EXISTING SYSTEM................................................13

3.2 PROPOSED SYSTEM..............................................14
3.3 FEASIBILITY STUDY.............................................15
3.3.1 Economic Feasibility..............................................16
3.3.2 Technical Feasibility...............................................17
3.3.3 Operational Feasibility............................................18

NAMES GROUP 5 SIN/No.

1. Lusoke Christopher : 22111753

2. Muwowo Marvis : 22179298
3. Sakala Eric : 22105408
4. Makumba Steven : 22112845
5.Malama Evaristo : 22106524

1
 CHAPTER 1
INTRODUCTION

1.1 ABSTRAC

Toll Gate System is an organized computerized system designed and programmed to deal
with day to day operations and management of the toll gate activities. The program can
look after vehicle categories. It will be keeping all necessary records in a particular
month.

2
 1.2 Introduction:
The E M S E C Tollgate Management System is a system designed to streamline the
recording, searching, and display of tollgate records for small, medium, and large
vehicles. The system provides a user-friendly interface for managing monthly tollgate
data, allowing users to input new records, search for specific months, and view a
comprehensive display of existing records.

1.3 Problem Introduction:

The Tollgate Management System addresses the challenges associated with manually
managing tollgate records and provides an efficient solution for overseeing and
analyzing toll collection data. The system aims to alleviate common problems
encountered in traditional tollgate management processes:

1.4 Goals
1-User friendly
2-Simple fast
3-Low cost and effective
4-It deals any type of vehicle

1.5 Objective:-

The E M S E C Tollgate Management System is designed with specific objectives in

mind, aiming to address key challenges associated with traditional tollgate record
management. The system's objectives encompass various aspects of data accuracy,
efficiency, user accessibility, and overall improvement in tollgate operations. The
primary objectives include:

1. Automate Tollgate Data Recording:

 Objective: To automate the process of recording tollgate data for each month.
 Rationale: Automation reduces the likelihood of human errors in data entry, ensuring accuracy
and consistency in the recorded information.
2. Facilitate Efficient Data Retrieval:
 Objective: To provide users with a quick and efficient means of retrieving tollgate records
based on specific months.
 Rationale: Efficient data retrieval enhances the system's responsiveness, allowing users to
promptly access the information they need for analysis or reporting.
3. Enhance Data Analysis Capabilities:
 Objective: To enable users to analyze tollgate data easily and extract meaningful insights.
3
 Rationale: By facilitating data analysis, the system empowers users to make informed decisions,
identify trends, and assess the performance of the tollgate.
4. Ensure Accuracy in Revenue Calculation:
 Objective: To automate the calculation of total revenue from toll collections based on
predefined toll rates.
 Rationale: Automated calculations reduce the risk of errors, ensuring accurate and reliable total
revenue figures.
5. Improve Record Accessibility and Transparency:
 Objective: To provide a user-friendly display function for transparent access to all existing
tollgate records.
 Rationale: Improved accessibility enhances transparency, allowing users to easily review
historical records and gain insights into tollgate operations.
6. Track Record Numbers Systematically:
 Objective: To maintain a systematic record number tracking mechanism.
 Rationale: Systematic tracking ensures organization and provides a reference point for users,
preventing confusion and data mismanagement.
7. Implement File Handling Best Practices:
 Objective: To implement robust file handling mechanisms for proper storage and retrieval of
tollgate records.
 Rationale: Proper file management ensures data integrity, security, and adherence to best
practices in handling file operations.
8. Offer a User-Friendly Interface:
 Objective: To provide a user-friendly interface that is intuitive and accessible.
 Rationale: A user-friendly interface promotes ease of use, encourages user adoption, and
enhances overall user experience with the system.
9. Ensure System Reliability and Error Handling:
 Objective: To design the system with reliability in mind, incorporating effective error handling
mechanisms.
 Rationale: Ensuring system reliability and robust error handling enhances the system's stability
and user confidence.

By achieving these objectives, the CS130 Tollgate Management System aims to

streamline tollgate operations, improve data accuracy and accessibility, and pro

1.6 Scope of the Project:

The System outlines the boundaries and limitations of the system, defining
what is included and excluded from its functionality. It provides a clear
understanding of the system's focus and the areas it aims to address. The
scope includes:

4
 Inclusions:
1. Tollgate Data Management:
 The system covers the recording of tollgate data for small, medium, and large
vehicles.
 It includes the calculation of total revenue based on predefined toll rates.
2. User Interaction:
 The system provides a user-friendly interface for users to interact with various
functions.
 Users can input new tollgate data, search for records, and display existing
records.
3. Data Retrieval and Analysis:
 The system includes features for efficient retrieval of tollgate records based on
specific months.
 It supports basic data analysis capabilities to help users extract meaningful
insights.
4. File Handling:
 The system utilizes file handling mechanisms for storing and retrieving
tollgate records.
 It includes the maintenance of a "tracker.txt" file to keep track of the current
record number.
5. Error Handling:
 The system incorporates error handling mechanisms to ensure reliability.
 It aims to provide informative error messages to users in case of unexpected
situations.
6. Documentation:
 The system includes documentation to guide users on how to interact with
the program.
 Documentation covers an overview of the program, function details, and
usage instructions.
Exclusions:
1. Real-Time Integration:
 The system does not include real-time integration with external systems or
databases.
5
 It operates independently without immediate connections to external sources.
2. Advanced Data Analysis:
 Advanced statistical or complex data analysis features are not within the
scope.
 The system focuses on basic data analysis capabilities for general insights.
3. User Authentication:
 The system does not include user authentication mechanisms.
 It assumes a single-user environment without user-specific access controls.
4. Extensive Reporting:
 The system does not generate extensive reports beyond basic data display.
 Reporting features are limited to displaying existing tollgate records.
5. Integration with External Devices:
 Integration with external tollgate devices or hardware is outside the scope.
 The system assumes manual input of tollgate data by the user.
6. Predictive Modeling:
 The system does not include features for predictive modeling or forecasting.
 It focuses on recording and presenting historical tollgate data.
Future Enhancements:
1. Multi-User Support:
 Future versions of the system could incorporate multi-user support with
authentication mechanisms.
2. Advanced Analytics:
 Advanced analytics and reporting features may be considered in future
iterations.
3. Integration with External Systems:
 Integration with external systems for real-time data exchange could be
explored in the future.
4. Mobile Application:
 A mobile application version could be developed to provide users with on-
the-go access to tollgate data.

By clearly defining the scope, the Tollgate Management System aims to meet
specific user needs while providing a foundation for potential future
6
enhancements. This scope ensures a focused and manageable development
effort while delivering valuable tollgate management features to users.
.

1.14 Toll agent module:

 Search for record

 View available record
 Getting input from user

7
 CHAPTER 2
DESIGN

8
 2.1 SYSTEM DESIGN:

2.1.1 INTRODUCTION TO UML:

UML Design
The Unified Modeling Language (UML) is a standard language for
specifying, visualizing, constructing, and documenting the software system and its
components. It is a graphical language , which provides a vocabulary and set of semantics
and rules. The UML focuses on the conceptual and physical representation of the system.
It captures the decisions and understandings about systems that must be constructed. It is
used to understand, design, configure, maintain, and control
information about the systems.
The UML is a language for:
Visualizing
Specifying
Constructing
Documenting
Visualizing
Through UML we see or visualize an existing system and ultimately we visualize
how the system is going to be after implementation. Unless we think, we cannot
implement. UML helps to visualize, how the components of the system
communicate and interact with each other.

Specifying
Specifying means building, models that are precise, unambiguous and complete
UML addresses the specification of all the important analysis design,
implementation decisions that must be made in developing and deploying a
software system.

Constructing
UML models can be directly connected to a variety of programming language
through mapping a model from UML to a programming language like JAVA or
C++ or VB. Forward Engineering and Reverse Engineering is possible through
UML.

Documenting
The Deliverables of a project apart from coding are some Artifacts, which are
critical in controlling, measuring and communicating about a system during its
developing requirements, architecture, desire, source code, project plans, tests,
prototypes releasers, etc...

9
 2.2 UML Approach

UML Diagram

A diagram is the graphical presentation of a set of elements, most often

rendered as a connected graph of vertices and arcs . you draw diagram to visualize a system
from different perspective, so a diagram is a projection into a system. For all but most
trivial systems, a diagram represents an elided view of the elements that make up a system.
The same element may appear in all diagrams, only a few diagrams , or in no diagrams at
all. In theory, a diagram may contain any combination of things and relationships. In
practice, however, a small number of common combinations arise, which are consistent
with the five most useful views that comprise the architecture of a software-intensive
system. For this reason, the UML includes nine such diagrams:
1. Object diagram
2. Sequence diagram
3. Collaboration diagram
4. State chart diagram
5. Activity diagram
6. Component diagram
7. Deployment diagram

10
 2.5 Sequence diagram:
A Sequence Diagram is an interaction diagram that emphasis the time ordering of
messages; a collaboration diagram is an interaction diagram that emphasizes the
structural organization of the objects that send and receive messages. Sequence diagrams
and collaboration diagrams are isomorphic, meaning that you can take one and
transform it into the other.

11
12
 2.6 Activity diagram:
A Activity diagram is another important behavioral diagram in UML diagram to describe
dynamic aspects of the system. Activity diagram is essentially an advanced version of flow
chart that modeling the flow from one activity to another activity.

13
 2.7 Deployement diagram:
A Deployment Diagram shows the configuration of run-time processing nodes and the
components that live on them. Deployment diagrams address the static deployment view
of architecture. They are related to component diagrams in that a node typically encloses
one or more components.

14
 desktop Client Printer

Command prompts

Text file

CHAPTER 3
ANALYSIS

15
 3.1 EXISTING SYSTEM:
Tollgates currently use a manual system for the management and maintenance of critical
information. The current system requires numerous paper forms, with. Often information is
incomplete or does not follow management standards. Forms are often lost in transit
between departments requiring a comprehensive auditing process to ensure that no vital
information is lost. Multiple copies of the same information exist in the department of
National Road Fund Agency and may lead to inconsistencies in data in various data stores.

3.2 PROPOSED SYSTEM:

The Tollgate Management System is designed for any toll-road under NRFA to replace
their existing manual paper based system. The new system is to control the information of
all different vehicles passing through any tollgate. Quick processing, staff and operating
schedules and vehicles invoices. These services are to be provided in an efficient, cost
effective manner, with the goal of reducing the time and resources currently required for
such tasks .

3.3 FEASIBILITY STUDY

The feasibility of the project is analyzed in this phase and business proposal is put
forth with a very general plan for the project and some cost estimates. During system
analysis the feasibility study of the proposed system is to be carried out. This is to ensure
that the proposed system is not a burden to the company. For feasibility analysis, some
understanding of the major requirements for the system is essential.

Three key considerations involved in the feasibility analysis are:

3.3.1 Economic Feasibility

This study is carried out to check the economic impact that the system will
have on the organization. The amount of fund that the company can pour
into the research and development of the system is limited. The
expenditures must be justified. Thus the developed system as well within
the budget and this was achieved because most of the technologies used are
freely available. Only the customized products have to be purchased.

16
 3.3.2 Technical Feasibility

This study is carried out to check the technical feasibility, that is,the
technical requirements of the system. Any system developed must not have
a high demand on the available technical resources. This will lead to high
demands being placed on the client. The developed system must have a
modest requirement, as only minimal or null changes for the implementing
this system.

3.3.3 Operational Feasibility

The aspect of study is to check the level of acceptance of the system

by the user. This includes the process of training the user to use the
system efficiently. The user must not feel threatened by the system,
instead must accept it as a necessity. The level of acceptance by the
users solely depends on the methods that are employed to educate the
user about the system and to make him familiar with it. His level of
confidence must be raised so that he is also able to make some
constructive criticism, which is welcomed, as he is the final user of
the system.

17