Project Name: Requirements Document (version 1.

1)

Real time vehicle load monitoring system: Requirements Document (version 1.1)
Project: real time vehicle load monitoring system
Date: December, 2014.
Prepared by: BSE15-10
Document status: final version

GROUP MEMBERS:

Names

Registration Number

Kemigisa Irene

11/U/9260/PS

Gumisiriza Brian

11/U/9290/PS

Nalwadda Dorothy

11/U/9316/PS

Mpiirwe Isaac

11/U/9239/PS

Signature

Project Name: Requirements Document (version 1.1)

Table of contents
1. Introduction. ............................................................................................................................................ 1
1.1

Purpose of This Document ......................................................................................................... 1

1.2 How to Use This Document .............................................................................................................. 1

1.2.1 Types of Reader and specific sections ......................................................................................... 1
1.2.2 Technical Background Required .................................................................................................. 2
1.2.3 Overview Sections ....................................................................................................................... 2
1.2.4 Section Order Dependencies ........................................................................................................ 2
1.3 Scope of the Product ......................................................................................................................... 2
1.4 Business Case for the Product.......................................................................................................... 2
1.5 Overview of the Requirements Document ...................................................................................... 3
2. General description ................................................................................................................................. 4
2.1 Product Perspective .......................................................................................................................... 4
2.2 Product Functions. ............................................................................................................................ 4
2.3 User Characteristics.......................................................................................................................... 5
2.4 General Constraints. ......................................................................................................................... 5
2.5 Assumptions and Dependencies. ...................................................................................................... 5
3. Specific requirements ............................................................................................................................. 6
3.1 User Requirements............................................................................................................................ 6
3.1.1 Functional requirements............................................................................................................... 6
3.1.2 Nonfunctional requirements ......................................................................................................... 6
3.2 Reporting Requirements. ................................................................................................................. 6
3.3 Security Requirements ..................................................................................................................... 7
3.4 User Interface Requirements ........................................................................................................... 7
3.4.1 Hardware Interfaces. .................................................................................................................... 7
3.4.2 Software Interfaces. ..................................................................................................................... 7
4. High-level technology architecture ........................................................................................................ 9
5. Customer support. ................................................................................................................................ 10
6. Appendices. ............................................................................................................................................ 11
6.1 Appendix a: Interview questions to vehicle owners ..................................................................... 11
6.2 Appendix b: Proposed budget........................................................................................................ 12
6.3 Appendix c: Proposed Work plan ................................................................................................. 12
7. Glossary of terms. ................................................................................................................................. 13

ii

Project Name: Requirements Document (version 1.1)

7.1 Acronyms ......................................................................................................................................... 13
7.2 Definitions ........................................................................................................................................ 13
8. References .............................................................................................................................................. 14

iii

Project Name: Requirements Document (version 1.1)

1. Introduction.
This document contains the system requirements for real time vehicle load monitoring system.
These requirements have been derived from several sources, including;
DHL
Sites of Aramex
Link couriers which are some of transportation companies that load vehicles for
transportation of goods from one place to another.
The internet

1.1 Purpose of This Document

This document is intended to guide development of real time vehicle load monitoring system. It
shall go through several stages during the course of the project:
1. Draft: The first version, or draft version, is compiled after requirements have been discovered,
recorded, classified, and prioritized.
2. Proposed: The draft document is then proposed as a potential requirements specification for
the project. The proposed document should be reviewed by several parties, who may comment
on any requirements and any priorities, either to agree, to disagree, or to identify missing
requirements. Readers include end-users, developers, project managers, and any other
stakeholders.
3. Validated: Once the various stakeholders have agreed to the requirements in the document, it
is considered validated.
4. Approved: The validated document is accepted by representatives of each party of
stakeholders as an appropriate statement of requirements for the project. The developers then use
the requirements document as a guide to implementation and to check the progress of the project
as it develops.

1.2 How to Use This Document

It is expected that this document shall be used by people with different skill sets. This section
explains which parts of this document should be reviewed by various types of readers.

1.2.1 Types of Reader and specific sections

Project managers shall read all the sections of the document, since they need to know all
processes that shall lead to the successful development of the system. Developers shall read 2,
3,4,5,6, and 7 because these sections provide system functionality that needs to be implemented
and sections 1, 8, and 9 can be skipped.

Project Name: Requirements Document (version 1.1)

Owners of vehicles can read 1, 2, 3, and 7 since they need to know why they need the system and
the different functions it shall perform and sections 4, 5, 6, 8, and 9 can be skipped by the vehicle
owners.

1.2.2 Technical Background Required

The readers to whom this document is directed are required to at least have the following
technical background in order to understand this document very well.
The readers should understand English language .
For section 4, the reader should have computer knowledge.

1.2.3 Overview Sections

These are the sections that give a reader the general understanding of the project without reading
through the whole document;
Section 1.4
This section shall give the reader the purpose of the system.
Section 2.2
This section explains what the system does and the activities it achieves.

1.2.4 Section Order Dependencies

Sections 1, 2, 5, 6, 7and 8 can be read independently as they depend on no other section.
Before reading section 3, the reader must first read section 2 since there is need for the reader to
first understand how the system shall function.
The reader must first read section 2 and 3 before reading section 4, because there is need to first
understand the general description of the system before knowing the technology to use.

1.3 Scope of the Product

The system shall enable automatic weighing of commercial cargo vehicles and when the
maximum allowed weight (Loading weight) is reached, it shall send messages to vehicle owners
informing them of the location of the vehicle and the weight of the load. When the vehicle is
offloaded, a message shall be sent again. The system shall be designed to use by DHL Company.

1.4 Business Case for the Product.

The system shall help vehicle owners to monitor their vehicles and the work that is going on.
This shall in turn increase their profits as the costs incurred due to overloading are reduced.

Project Name: Requirements Document (version 1.1)

The vehicles shall be maintained in good mechanical condition since they shall constantly be
monitored.

1.5 Overview of the Requirements Document

The system shall measure increase and decrease in the mass of the load of the vehicle.
The system shall detect offloading and if the maximum weight is exceeded, a message
shall be sent
The system shall send a message to the vehicle owner when the vehicle is loaded,
offloaded and overloaded.

Project Name: Requirements Document (version 1.1)

2. General description
This section gives the reader an overview of the project, including why it was conceived, what it
shall do when complete, and the types of people expected shall to use it. It also contains
constraints that may be encountered during development and assumptions that will be made so as
to proceed with the project.

2.1 Product Perspective

Commercial vehicle owners have challenges of monitoring the activity of their vehicles. It is
required that drivers return a given amount of money to the owners at the end of every day.
Unfortunately, they return less money or no money at all. Sometimes, workers claim that they
did not work.
Workers also normally overload the vehicles and this causes negative effects on the steering,
brakes and the speed control of the vehicle, thus incurring more costs on repairs and
maintenance.
Due to the challenges vehicle owners face this system shall be developed to help them know if
the vehicle was in use and also reduce on the costs incurred due to overloading.
With full development and implementation of this system, there shall be increased efficiency and
management of vehicles hence increasing on the profits.
The primary stake holders of the product include vehicle owners and System developers.

2.2 Product Functions.

The system shall provide the following functions:

The system shall keep track of the vehicle.

The system shall detect and notify the owners when the vehicle is being loaded and
offloaded.
The system shall also detect and notify the owners when the system is being overloaded
through sending messages.

Project Name: Requirements Document (version 1.1)

2.3 User Characteristics.

The system shall be used by vehicle owners to help them in monitoring their vehicles.
The system users are expected to have basic knowledge on phone usage and must be able to read
English.

2.4 General Constraints.

Time Scale constraints; the time allocated for the project is not enough for the developers
to come up with an expected functional project.
Technology constraints; the system shall be developed using embedded c.
Budget constraints; the funds might not be enough to fully finance the project over the
course of the project development.
Information and requirement gathering; the client might not explicitly state the
requirements and this often affect the development process and it might also be difficult
to determine the scope of the project.

2.5 Assumptions and Dependencies.

The system needs the use of mobile phones with registered SIM cards for full
functionality.
The system assumes whatever is being loaded on the vehicle are goods and not people.
The system assumes to have a functioning power source.

Project Name: Requirements Document (version 1.1)

3. Specific requirements
This section of the document lists specific requirements for real time load monitor system.
Requirements are divided into the following sections:
1. User requirements. These are requirements written from the point of view of end users, usually
expressed in narrative form.
2. Reporting requirements.
3. System and Integration requirements. These are detailed specifications describing the
functions the system must be capable of doing.
4. Security Requirements
5. User Interface requirements. These are requirements about the user interface, which may be
expressed as a list, as a narrative, or as images of screen mock-ups.
4. Security Requirements
5. User Interface requirements. These are requirements about the user interface, which may be
expressed as a list, as a narrative, or as images of screen mock-ups.

3.1 User Requirements

3.1.1 Functional requirements.

The system shall measure increase and decrease in the mass of the load of the vehicle.
The system shall detect offloading and if the maximum weight is exceeded, a message
shall be sent
The system shall send a message to the vehicle owner when the vehicle is loaded,
offloaded and overloaded.

3.1.2 Nonfunctional requirements

The system shall be error free

The system shall be available all the time
The system shall send the right information

3.2 Reporting Requirements.

The system shall notify the vehicle owner by sending an SMS whenever vehicle is being loaded
or offloaded and when its overloaded. The message containing Vehicle details, the time and the
quantity of the load will be sent to the vehicle owner.

Project Name: Requirements Document (version 1.1)

3.3 Security Requirements

SMS notifications shall only be received by the owners of the vehicles.

3.4 User Interface Requirements

3.4.1 Hardware Interfaces.

There shall be a hardware system that shall detect the weights being loaded on the
vehicles. The system shall have a weight sensor to detect the increase and decrease in
weight, a component to send the message
The customer shall use a mobile phones to be able to receive notifications of what is
happening on the vehicles

3.4.2 Software Interfaces.

UAW 241A
10:15am
Truck loaded: 100kg.

Figure 1: Message received when vehicle is loaded

Figure 1 above shows the message that will be received by the vehicle owner when it is loaded.
It shows the vehicle number plate, time when message was sent and the amount of weight loaded

UAW 255A
12:28pm
Truck is offloaded

Figure 2: Message received when vehicle is offloaded.

Figure 2 above shows the message that will be received by the vehicle owner when it is
offloaded. It shows the vehicle number plate, time when message was sent and the amount of
weight loaded.

Project Name: Requirements Document (version 1.1)

UAW 261A
4:25pm
Truck is overloaded

Figure 3: Message received when vehicle is overloaded.

Figure 3 above shows the message that will be received by the vehicle owner when it is
offloaded. It shows the vehicle number plate, time when message was sent and the amount of
weight loaded.

Project Name: Requirements Document (version 1.1)

4. High-level technology architecture

Load

Weight sensor.
Mobile Phone
Control system
GSM Modem

Figure 4: System communication

Figure 4 above shows how the weight sensor shall detect the weight of the load, the detected
weight shall be sent to the control system. The control system shall then command the GSM
modem to send the message to the mobile phone of the vehicle owner. The message shall
contain the detected weight, vehicle details, and time.

Project Name: Requirements Document (version 1.1)

5. Customer support.

A user manual shall be provided that help and guide on how to go about with the
different functions of the system.
Also additional services such as free software maintenance and update by the software
developers.

10

Project Name: Requirements Document (version 1.1)

6. Appendices.
6.1 Appendix a: Interview questions to vehicle owners
1. How do you normally monitor vehicles during transportation of cargo?

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------2. How do you determine the maximum weight to be loaded on the trucks?

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------3. Are there circumstances when there is need to carry more than the maximum allowed weight?

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------4. If you are to carry more than the allowed weight what measures do you take in order not to be arrested
and charged?

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

11

Project Name: Requirements Document (version 1.1)

6.2 Appendix b: Proposed budget.

Table 1: Proposed budget
ITEM

QAUNTITY

UNIT
PRICE(Ugx)
1,200,000

TOTAL
STATUS
PRICE/COST(Ugx)
4,800,000
Available

Laptop

Printing
Weight
1
sensor
GSM Modem 1

100 per paper

50,000

50,000
50,000

Not available
Not Available

650,000

650,000

Not available

Hardware

70,000

70,000

Not available

Transport

50,000

200,000

Not available

Airtime

20,000

80,000

Not available

5,828,000

TOTAL

6.3 Appendix c: Proposed Work plan

Table 2: Proposed work plan
Time

Item

Leader(s)

September to November, 2014

Proposal writing and delivery

Irene and Brian

November, 2014

Fieldwork/requirements
collection
Writing Requirements
specification and delivery

Isaac

January to February, 2015

Writing Design and delivery

Isaac and Irene

January to April, 2015

Implementation and coding

Dora and Brian

March to April, 2015

Testing and validation

Irene

April to May, 2015

Report writing

Dora

November to December, 2014

12

Dora and Irene

Project Name: Requirements Document (version 1.1)

7. Glossary of terms.
7.1 Acronyms
GSM.

Global System for Mobile.

SMS.

Short message service.

7.2 Definitions
SIM card.

A removable smart card for a mobile phone that stores service subscription
information and saved data such as phone numbers.

Load

Goods carried by a large vehicle.

SMS

a service for sending text messages on cellular phones

13

Project Name: Requirements Document (version 1.1)

8. References
[1] I. Somerville, Software Engineering, 8th ed. China: Pearson Education Limited, 2007, pp.
139-163.
[2] [Online]. Available: http://dictionary.reference.com/browse/weight
[3][Online]. Available: www.trucking truth.com.
[4] D. Hummels. (2009). International transport forum. [Online]. Available:
www.internationaltransportfoum.org
[5] [Online]. Available: http://www.cargoforce.co.uk/cheapest-cargo.html
[6] [Online]. Available: http://www.cargoforce.co.uk/road-freight.html
[7] Dhl. (2014, January.). International service price list. [Online]. Available:
http://www.dhl.com.pl
[8] [Online]. Available:
http://www.indianrailways.gov.in/railwayboard/view_section.jsp?lang=0&id=0,6,335,906,908
[9] U. Berli, and M. Bnzli. (1991, May.). Electronic weighing principles. [Online]. Available:
http://www.fisica.uh.cu/bibvirtual/vida%20y%20tierra/balanzas/Weighing_Principles.pdf
[10] [Online]. Available: http://science.howstuffworks.com/engineering/civil/question626.htm
[11] [Online]. Available: https://www.oxfordshire.gov.uk/cms/content/vehicle-overloading

14