PRATICAL NO: 2

AIM : To Study and Create Software Requirement Specification document for CARGO MANAGEMENT SYSTEM

NAME: RAHUL SONTAKKE

ROLL NO: 61
REG NO: 21070052

sss
 Table Content

1. Introduction

2. Analysis
• System Analysis
• System Specification
3. Project Module

4. Design and Constraints

5. Tools Used

6.Evaulation and Testing

7. Conclusion

8. BIBILIOGRAPHY
 Introduction

This chapter provides a general introduction of the project. It includes some description of what the project is about, need for this project, scope, aims and

objectives which are to be achieved, user and system requirements and the structure of the dissertation.

Shipping Industry has become one of the most competent and changing industries throughout the
past years. Shipping companies are in a competition to cater their clients with effective and more
productive way rather than handling large numbers of documents/information back and forth with
the customers.
Information is very confidential, such as Payments, charges and most importantly their Agent's
Information. Because of that, companies are under increasing pressure to manage information
securely and in the meantime, provide a service in a productive way using limited resources.

CARGOMANAGER requires user entry of container and product dimensions, together with
information on weight and orientation constraints.In-builtdatabase facilities for up to 50containers
and 400 products are provided so that input into these screens can be carried out with minimal
effort. If information for a particular product code is already held in the 400 product database then
this is automatically entered into the appropriate fields.

The first of these will attempt to pack as much of the cargo using any of the packing methods
available to CARGOMANAGER This may be a loading from the floor or from the end of the
container" The second and third options are self explanatory and the one most appropriate to the
practical circumstances should selected.

Mission: “Provide comprehensive service to customer and shipping industry and achieve excellence
in customer satisfaction.”
Vision: “To become the most popular service provider of the shipping industry by meeting
everyone’s expectations.”
 Analysis

System Analysis
Software design phase is an iterative process in which requirements gathered in analysis are
translated into a “blueprint” for constructing the system. At first, the blueprint depicts a high-level
abstract view of the system. Afterwards this can be elaborated into detailed functional and non-
functional requirements.

The functional requirements of the system are the functionalities or services that should be included
in an information system in order to satisfy the business needs. Following are the functional
requirements of the project scope to achieve the objectives mentioned in introduction. The proposed
system consists of following main modules which consist of functional requirements described
below.

Reference data:
Reference module defines all the reference data which is needed in the system transactions.
Following data will be maintained here.
I. Categorization of Agents and Customers.
II. Define charges, services.
III. Defining Jobs
IV. Create Payment and Receipts

Job and Responsibilities:

The jobs and section is available for authorized system user to create and manage jobs and bill of
ladings under created jobs. Depending on the Job type and Bill of Lading type, system user can
select the relevant container and allocate goods

Payment Handling:
The way of handling each transaction is discussed here. Handling the Agents and Customers
payments and issuing of vouchers and receipts will be clearly defined. Payment for the Job and BL
is made at the company’s cashier. No online payment will be done.

Report:
Flexible reporting procedure has been introduced for the Shipping company. System is facilitated to
generate descriptive reports in daily and monthly basis as per the given access. These reports are
prepared for printable media in order to handover them to the respective personals.

Administration :
System should be accessed by the authorized parties and access rights for each user group will be
set by the system. The user login and user authorizations are created to enhance the security level of
the system. Each end-user, Manager, System User, Accountant and Employee, has their own access
level to cooperate with the system.
System Specification

Hardware Requirements:
 Processor: Minimum 1 GHz; Recommended 2GHz or more (Intel, AMD)
 Memory (RAM): Minimum 1 GB; Recommended 4 GB or above
 Hard Drive: Minimum 32 GB; Recommended 64 GB or more

Software Requirements:
 Database: Oracle, IBM Db2, Informix, Microsoft SQL
 Web Technologies: HTML, cascading style sheets (CSS)
Language: Java

Operating System:
 Windows: 7 or newer
 MAC: OS X v10.7 or higher


Design Module

Detailed plan of work for the rest of the project.

Phase 1:

Jobs, Bill of Ladings and necessary master details. After that Generating necessary documents like Manifest, Delivery Order, Bill of Lading and Cusdec file.

Phase 2:

Charges module needs to be incorporated in order to complete invoices and payments.

Employee Management, their leave management, needs to be developed.

Phase 3:

Agent Module which supports CRUD operations of agents and allocating charges for them, generate invoices and make payments need to be developed.

Phase 4:

Employee management and leave management module. This will be a separate module as there is no connection between system users and employees according to the

company specifications.

System was implemented to reduce paperwork and to provide efficient customer service to the customers of Shipping Industry and most importantly the employees of the

shipping industry. Thereby maintaining agents, jobs and bl records will be much easier and provide a fast-accurate customer service without any delay.
Design and Constraints

Cargo Manager is a comprehensive cargo management module, designed for addressing the areas of
General cargo, Bulk cargo operations. All the aspects of cargo like documentation handling,
movement, and storage are addressed in this module.
Key Features Include

- General Cargo Booking

- Storing of Cargo (weight, Volume etc.)
- Generating the gate pass for bringing the cargo into the warehouse
- Marking the cargo exit
- Delivery order for rejested or damaged cargo
- Generating gate pass for redelivery of cargo
- Querying facilities

Actors and their Use Case:

- Admin:Manage Customer, Manage Cargo, Manage Transaction, Manage Billing, Manage

Enquire, Manage Payment, Manage Goods, Manage Time of Delivery, Manage Cargo
Management Operations

- System user:Manage Customer, Manage Cargo, Manage Transaction, Manage Billing, Manage
Enquire, Manage Payment, Manage Goods, Manage Time of Delivery

- Customer:Request for Cargo Load, View Invoice, View receipts

, Make Payment, Payment history

- Loader: Check request, collect info, Manage load

 Use Case Diagram
Unified Modeling Language (UML), a use case diagram can summarize the details of your system's
users (also known as actors) and their interactions with the system. To build one, you'll use a set of
specialized symbols and connectors. An effective use case diagram can help your team discuss and
represent:

• Scenarios in which your system or application interacts with people, organizations, or external
systems

• Goals that your system or application helps those entities (known as actors) achieve

• The scope of your system

 Tools Used

• Star UML

StarUML is an open source software modeling tool that supports the UML (Unified Modeling
Language) framework for system and software modeling. It is based on UML version 1.4, provides
eleven different types of diagram and it accepts UML 2.0 notation. It actively supports the MDA
(Model Driven Architecture) approach by supporting the UML profile concept and allowing to
generate code for multiple languages.

There is however an active open source project called WhiteStarUML that is a fork of StarUML
5.0. It provides a number of bug fixes and an improved compatibility with the modern versions of
the Windows OS. Version Tested: StarUML version5.0.2.1570, tested on Windows XP in
September 2011

System Requirements: Windows 2000, Windows XP, or higher; Microsoft Internet Explorer 5.0 or
higher; 128 MB RAM (256MB recommended); 110 MB hard disc space (150MB space
recommended)

License & Pricing: Open Source

Support: User mailing list

Conclusion
This system was implemented to reduce paperwork and to provide efficient customer service to the
customers of Shipping Industry and most importantly the employees of the shipping industry.
Thereby maintaining agents, jobs and bl records will be much easier and provide a fast-accurate
customer service without any delay.

Idea of building a new system is to streamline the process of the workers and provide efficient
service to the end client. However, there is a list of areas where further improvements can be made.

In order to complete the system in a perfect way, requirement analysis was the critical part as
continuous meetings, clarifications of the requirements and getting the feedback of developed
sections from the end user. Because of the changing requirements, had to deal with system section
changes as well as database changes had to be incorporated.
Managing system developments with the office work was bit stress full as well as hard. Being a
software Engineer in full time, made me to achieve several deadlines with the projects and work
some late nights.
Authentication mechanism on Laravel was giving bit trouble and therefore had to upgrade the
system into Laravel and it caused some domino effect on few areas which already developed.

Most of the systems features which are available and ship track system is very much similar. But we
stand out of them because our system can be customized and there are less web based systems
available at the moment.
Future Enhancement

This system was built considering the requirements received from the client. The following is
amongst the future extensions that could be put into action.

V. Track ships real time in order to provide the exact location of end client’s goods.

VI. Once the goods arrive, track containers exact location.

Generate common documents for Port of Loading and Port of Departing agents.
Bibliography

• Google

• C++ cook book

• wrox Professional guide

• microsoft.com

• Scribd.com
VII.