Introduction

Requirements are a description of how a system should behave or a description of system

properties or attributes. It can alternatively be a statement of ‘what’ an application is expected to
do. Requirements Analysis is the process of understanding the customer needs and expectations
from a proposed system or application and is a well-defined stage in the Software Development
Life Cycle model.

Requirement analysis for web based transport

management system in Nepal
The transportation management system requires a large database to store all the information
detailing the company’s daily running. Following are the main areas of information :

1. Customer details: A company runs if he is able to hold the customer providing the
service satisfactorily.Customers are those who use the service provided by the Transport
company. So it requires keeping all the details such as customer name, customer
address, contact no,and the account information .A customer is distinguished as
consignee and consignor. The consignee is the person to whom the shipment is to be
delivered and the consignor is the person sending a shipment to be delivered.A customer
is able to track the cargo status based on the unique id called cargo id but any rights to
navigate the page are to be prohibited.
2. Driver details: Information regarding each employee (except office conducting staff) is
stored in the database. These include driver name, license details, address details, date
of joining, agreement details, payment details, and holidays.
3. Vehicle details: The database will furnish a list of assets owned and/or hired by the
company for the transportation purpose only. These includes trucks, trailers . In case of
hired vehicle not only the vehicles details other details such as owners details insurance
details , permit type and account information are also to be maintained.
4. Cargo details: Cargo information is the main part of the system as a single challan
allows a truck to transport different cargo from the different customer. As the system is
generic and available to any company which specializes in any product ,it is important to
store information such as such as no of articles ,description of articles, gross weight ,rate,
total cost for the transportation, consignee ,consignor ,final destination for each cargo.
This results in the generation of unique cargo no and cargo status for the customer at a
particular day. Generation of cargo no may be manual or system generated. All the
transportation services for the particular day for a customer should be included in the
same cargo no. The cargo no. for the same customer on the different day of service must
be different. As well different customer should have different cargo no. for a particular
day.Cargo status has four phase. First phase is "Ordered" which means consignor has
just delivered the cargo to the transport office.Second status is
called "Dispatched" meaning that cargo has been loaded and on the way.Transit is
intermediate place where cargo has been dropped to destine for required location.When
consignee received the cargo status of cargo is changed into Delivered.In case of
delivery the recipient information such as name and contact no is to be kept in the system
so that a customer can get the information while tracking the cargo status.
5. Challan details: Challan is summary report of goods that is to be transported and helps
the driver and other personnel to get the information regarding the goods in vehicles.
 Challan includes the information regarding cargo nos. weight ,truck no, truck driver . For
each shipment there should be unique challan no which should be auto generated by the
system on request.User of the system ,however,be able to make deletion of items from
challan so that the reason of removal is reflected in cargo status.
6. Workers details: Transport service requires a large volume of loaders/unloader.The
system keeps the information regarding workers such as name ,address and thier
account information.Workers have no authority to navigate the system web page.
7. Account information: These parts of the company contain very crucial and sensitive
data regarding all the financial transaction . It includes reason for the payment, payment
mode, total amount to be received or paid,any dues.In a transport company several kinds
of transaction occurs. A system provides the following account information.
o Customer account: It keeps and provides the information about customer
account.In a transport industry cargo service is paid to the service provider either
by conignee or by consignor . Both of these options are included in the system.
In either case system keeps all details of transaction.
o Drivers account: It keeps and provides the information regarding driver account.
o Workers account: It keeps and provides the information of Workers account.
o Truck account: It keeps all the details of truck account such as reason of
payment,date of payment ,amount paid ,dues ,name of the receiver .
o Tax information: Service charge and VAT are a fraction of amount to be paid to
Government as per the rule .The rule of charging the tax is variable. A System
provides the option for charging service tax as well as VAT against each cargo
for each customer. A transport company collects the tax from the customer for
each service and paid them to the Government at the end of each fiscal year. A
system maintains all such tax information and generates the report based on
duration generally monthly or yearly.A tax report consists of tax payable amount
for each customer for all cargo service during a time period and able to find the
total amount to be paid to the government during the entire period of time.
8. Invoice generation: System must be able to generate invoice for the shipment of each
cargo no . It must include total weight ,rate ,and total amount to be charged for the
service. In case of recipient payment mode, system generates just a invoice to be paid
and does not allow to print the recipient slip on destiny side until the due is cleared.The
system administrator on remote side ,however , able to generate the recipient slip by
posting service charge in due mode.
9. Loading slip: For each day user is able to generate Loading slip day wise.This slip
contains the information such as cargo no,Truck no destination address, driver details
and worker details.After generating the slip status of all cargo in a challan is to be
changed to Dispatched.
10. Recipient slip: When a person comes to collect the cargo user of the system checks the
option of payment and generates a slip which contains the information cargo no,item
name ,quantity, consignee ,consignor ,recipient name and contact no if and only if cargo
service charge has been paid by the consignor.In case of consignee mode payment user
is prompted to request the cargo service charge. This makes the change in cargo status
to Delivered.
11. Reports: System must be able to generate the following reports :
o Durational report of shipment for each customer based on cargo no. This report
should include cargo no ,shipment date, total weight, description of items, rate ,
total payment.
o Durational report of payment for each customer.It should lists paid amount
against each cargo no.
 o Total income during the period of time.
o Report regarding the cargo no that is carried by particular truck on a particular
day.
o A list of drivers on duty for the particular day. It should include the truck
no,challan no,destination address.
o Report of workers assigned for loading and unloading the cargo according to
challan no.
o Reports regarding tax payable to the government.
o Payable amount to truck owner .

Synopsis

The project is entitled as “Web based Transport management system". A Transport management
System (TMS) is a software system designed to manage transportation operations and will
streamline the services of any company carrying freight for clients, or supply companies
managing their own delivery systems.

The aim of this project is to design a system for use in the haulage industry that will allow the
customer to conduct their business of trans-Nepalese delivery as cost-effectively as possible.
Nepalese transport management is affected by existing topographical condition of the country.
Due to this only means of transport used in the country are road transport and air transport. The
project is basically based on the road transportation. There are many haulage firms based in
Nepal who would fit the bill of a perfect user of this system; small or large firms with contracts to
deliver a range of product types to varied Nepalese destinations and to a varied customer base.
The system will allow these firms to efficiently manage their deliveries in the knowledge that they
will be carried out as cost-effectively as possible by the most suitable driver, in the most suitable
vehicle. The project begins with the study conducted on other similar systems in order to glean
design ideas and functionality ideas.

The system will be able to manage transportation procedure service adopted by firm. The system
should manage not only the service but it should also keep the information regarding Truck
,Drivers ,cargo, New customer ,Account, reports , challan, workers(except office conducting
staffs) .From these information firm can estimate their profit margin, depending on the cargo and
the haulage rates which are implemented.

Functionality will be available to allow system administrators to carry out tasks such as adding
new system administrators, changing user access rights, and adding trucks information and driver
to the database. The user can access information about customers, challan, delivery schedules
and invoices, and assign a truck and driver to a particular delivery. Similarly Customers’ are also
provided a right to track their cargo based on tracking id generated for each cargo service.
Requirement analysis and documentation part is one of the major phase in the software
development. No customers come with complete sets of their requirement. Requirement may be
changed after the system is in use or while the system is in progress. In order to accommodate
such kind of customers behavior Agile software development methodology is used. Agile
Modeling (AM) is a collection of values, principles, and practices for modeling software that can
be applied on a software development project in an effective and light-weight manner where
requirements and solutions evolve through collaboration between self-organizing cross-functional
teams. Well managed project helps to complete the project effectively and efficiently. Scrum is an
iterative, incremental framework for project management and agile software development. For the
implementation of TMS system Scrum frame work is used.

The service software is the main element of the project and it will require the most programming.
Therefore it is necessary to choose a programming language and a programming environment
that would suit the parameters of the project and, equally as importantly, suit the programming
abilities and preferences of the group. The project will be implemented for Java enterprise
platform version 6 (JavaEE 6) using Java language. The choice of Java language and JavaEE
platform is decided for several reasons :

• Java is a matured, popular and industry standard object oriented language

• It is platform independent language
• Java was in IETE academic curriculum
• Java has rich community support and there are lots of free and open sourced
framework/library available to solve the problems.
• JavaEE is the only open standard enterprise platform to develop server side application
• JavaEE is matured and it is open sourced.
• JavaEE can be run on any platform including free Linux.
• JavaEE provides lots of platform services; for e.g persistency, transaction, web,
messaging, scheduling, security etc.

The Unified Modeling Language (UML) version 2 is an industry standard modeling tool for
validating and verifying project requirements, its design, implementation and deployments. So my
choice of UML for analysis and design was obvious.

Microsoft Project is used to manage the project plans. Microsoft Project gives the project team
control over the development of the project within a specified timescale. It outputs the project plan
in chart, graph and spreadsheet form and is easy to use.

As a requirement of one man team constraint, the complete TMS implementation is not feasible
within a given time-frame. So, only major product features will be implemented and remaining will
be left for future enhancement. This report will discuss the analysis and design of TMS system,
including what technologies and design methodology will be used, discuss elements of the project
design such as risk analysis, testing and time scale, and will include a brief look at other existing
systems on which the project team has based the system design concepts on. These will be
covered during the first phase of the project.