Logistics Management Analysis and Design

8/3/2019 Logistics Management Analysis and Design

1/58

INTRODUCTION


2/58

Logistics is the . . . process of planning, implementing, and controlling the

efficient, effective flow and storage of goods, services, and related information

from point of origin to point of consumption for the purpose of conforming to

customer requirements.

Logistics is the management of the flow of goods, information and other

resources, including energy and people, between the point of origin and the point

of consumption in order to meet the requirements of consumers.

Logistics involves the integration of information, transportation, inventory,

warehousing, material-handling, and packaging, and occasionally security.

The logistics and transportation activities are moving towards the centre stage

world around and becoming the most critical business function in todays world of

immense competition. Today, quickest and efficient supply chain management is

the key success factor for many business sectors.

Surface transport still rules as the most widely used mode of logistics in our

country. Its high time; the transportation companies switch to futuristic

technology solutions to manage the ever growing industry requirements and never

ending customer demands. The solutions that move beyond just logics, towards

being efficient, cost effective and quick.

The goal of the entire solution is to work as a mini ERP solution for the haulage

business entities with minimum investment and maintenance costs. The benefits

arent cost alone, it will benefit you to stay ahead by offering high visibility of


3/58

consignments to your entire team and for the clients. Also assures customer

satisfaction, transparency and effective control for the business.


4/58

SYSTEM ANALYSIS


5/58

Existing System

There is no computerized provision in the company to maintain all the trip details

that are taking within the company. All the customer order are being handled

manually.

A customer has to come up to the company personally to book an order. All the

order details are also being maintained manually.

The labor work is too much and no proper maintenance is taking place in the

existing system.

Problems in Existing System

A considerable amount of effort, time and resources are involved due tomanual processing can be achieved.

No proper control over collection of data.


6/58

Proposed System

The proposed system is an online sales system which will help the company to sell

all their products online.

When a customer requires a product or multiple products, he issues an order for

the products. The proposed system will display an order form, which can be filled

by the customer. The proposed system will record the order details as well as the

customer details, and generate an appropriate Invoice to be presented to the

Customer for order confirmation.

Whenever an order is confirmed, then once the payment is done by the customer

the product has to be delivered to the customer.

The appropriate transport facilities must be set. The proposed system displays all

the vechicles information that are available for delivery. It then allows the Admin

to select the vehicle for the door delivery and records all the information regarding

the Trip. The proposed system displays a Door Delivery form in which the

administrator can add all the information regarding the vehicle, and the customer

details to whom the product has to be delivered.

They are a number of vehicles that are used in the company to deliver the order

given by the customers. The proposed system will display a vehicle processing

form, where the admin can add all the vehicle details that are available. Also it

will add the information of which vehicle has devliered what products and other

related information by using the vehicle delivery record form.


7/58

FEASIBILITY STUDY


8/58

Feasibility studies aim to objectively and rationally uncover the strengths and weaknesses of the

existing business or proposed venture, opportunities and threats as presented by the environment,

the resources required to carry through, and ultimately the prospects for success.

In its simplest term, the two criteria to judge feasibility are cost required and value to be attained.

As such, a well-designed feasibility study should provide a historical background of the business

or project, description of the product or service, accounting statements, details of the operations

and management, marketing research and policies, financial data, legal requirements and tax

obligations. Generally, feasibility studies precede technical development and project

implementation.

They are 3 types of Feasibility

Technology and System feasibility

The assessment is based on an outline design of system requirements in terms of Input, Processes,

Output, Fields, Programs, and Procedures. This can be quantified in terms of volumes of data,

trends, frequency of updating, etc. in order to estimate whether the new system will perform

adequately or not.

Technological feasibility is carried out to determine whether the company has the capability, in

terms of software, hardware, personnel and expertise, to handle the completion of the project

Whether the required technology is available or not Whether the required resources are available Manpower- programmers, testers & debuggers Software and hardware

Once the technical feasibility is established, it is important to consider the monetary factors also.

Since it might happen that developing a particular system may be technically possible but it may


9/58

require huge investments and benefits may be less. For evaluating this, economic feasibility of the

proposed system is carried out.

Operational Feasibility

Operational feasibility is mainly concerned with issues like whether the system will be used if it

is developed and implemented. Whether there will be resistance from users that will affect the

possible application benefits? The essential questions that help in testing the operational

feasibility of a system are following.

Does management support the project? Are the users not happy with current business practices? Will it reduce the time (operation) considerably? If yes, then they will welcome the

change and the new system.

Have the users been involved in the planning and development of the project? Earlyinvolvement reduces the probability of resistance towards the new system.

Will the proposed system really benefit the organization? Does the overall response increase? Will accessibility of information be lost? Will the system effect the customers in considerable way?

Economic FeasibilityFor any system if the expected benefits equal or exceed the expected costs, the system can be

judged to be economically feasible. In economic feasibility, cost benefit analysis is done in which

expected costs and benefits are evaluated. Economic analysis is used for evaluating the

effectiveness of the proposed system.


10/58

In economic feasibility, the most important is cost-benefit analysis. As the name suggests, it is an

analysis of the costs to be incurred in the system and benefits derivable out of the system.
http://www.freetutes.com/systemanalysis/sa3-cost-benefit-analysis.htmlhttp://www.freetutes.com/systemanalysis/sa3-cost-benefit-analysis.html


11/58

SOFTWARE REQUIREMENTS

SPECIFICATION


12/58

SOFTRWARE REQUIREMENTS SPECIFICATION:

A Software Requirements Specification (SRS) - a requirements specification for a

software system - is a complete description of the behavior of a system to be developed.

It includes a set of use cases that describe all the interactions the users will have with the

software. Use cases are also known as functional requirements.

Functional Requirements:

Customer Order Processing

Add Order Details Add Customer Details Generate Order Report Maintain Orders Search Datewise Orders

Vehicle Maintenance Processing

Input New Vehicle Information View Trips Manage Door Pickup and Delivery Details Input Customer Details

Accounts Processing

Adding various Branch Details View Payment Information View/Manage Pending Payments Invoice Controlling

Online Trips Processing


13/58

Maintaing Branch Details View Customer Information Temporary Trips Management


14/58

User Interfaces:

User interface is the space where interaction between humans and machines occurs. The

goal of interaction between a human and a machine at the user interface is effective

operation and control of the machine, and feedback from the machine which aids the

operator in making operational decisions.

The Proposed system provides very interactive user interfaces through which the user

will be easily able to access and navigate all operations.

Analysis Objects

1. Interface Objects:

Interface objects represent the interface between the system and the user. They are

identified from the use cases and usually represent the user interface. They do not

represent layout information or user interface details such as menus and buttons. Instead

interface objects represent concepts such as windows, forms or hardware artifacts such as

work stations.

2. Control Objects

Used to model behavior that is not naturally placed in either of another two objects

(interface and entity). Typically acts as glue which unites the other objects normally

found directly from the use cases. In the preliminary draft, assign one control object foreach use case. Deviation from the initial approach can be made for several reason:

In the case where there is no behavior in the use case left to model, then the control

object is not needed.

In the case of a very complicated behavior, the functionality may be divided into several

control objects

3. Entity Objects

Used to model the information that the system will handle over a longer period of time.

The information should be kept even if the use case has been complete Also used to

allocate the behavior that naturally belongs to this information Entity objects use

attributes to store Information


15/58

Identified from the use case description Most are found early and obvious Its easy to

find entity object, but more difficult to identify its operations and attributes In nomal

case, operations are not identified in the analysis model (but later in the design model)

Customer Order Invoice Admin Branch


16/58

Inputs

The following inputs are collected for proposed system during the requirements

specification

1. Customer Orders

When a customer requires a product or multiple products, he issues an order for

the products. The proposed system will display an order form, which can be filled by the

customer. The proposed system will record the order details as well as the customer

details, and generate an appropriate Invoice to be presented to the Customer for order

confirmation.

2. Trips Input Process

Whenever an order is confirmed, then once the payment is done by the customer

the product has to be delivered to the customer.

The appropriate transport facilities must be set. The proposed system displays all

the vechicles information that are available for delivery. It then allows the Admin to

select the vehicle for the door delivery and records all the information regarding the Trip.

The proposed system displays a Door Delivery form in which the administrator can add

all the information regarding the vehicle, and the customer details to whom the product

has to be delivered.

3. Vehicles Management Processing

They are a number of vehicles that are used in the company to deliver the order

given by the customers. The proposed system will display a vehicle processing form,

where the admin can add all the vehicle details that are available. Also it will add the

information of which vehicle has devliered what products and other related information

by using the vehicle delivery record form.


17/58

Outputs

The following outputs are collected for proposed system during the requirements

specification

1. Delivery Invoice

The company receives an invoice regarding the delivery of the appropriate

product. This Invoice will be signed by the customer and a confirmation note that the

product has been received. These details will be recorded by the proposed system by

using the Invoice form.

2. Order Report

Whenever the customer wants to send an order, he fills the order form and sends it

to the company. The company then records all the order form, and the proposed system

which generate an order report. This report will be sent to the store department for

verification of the stock and if the stock is availbale the order will be confirmed.

3. Customer Report

It is very important to maintain all the details of customers, along with the orders

being issued. The customer report will provide the company will all the details of

customer, with which they can make modifications or even delete the details of the

customers that are not required.

4. Trips Report

The Trips report will provide the details of the door delivery, as well as the

vehicle details that have delivered the product and customer details to whom the product

was delivered.


18/58


19/58

Non Functional Requirements:

Environment Requirement:

1. Choice of Operating system: The Operating used for the proposed systemis Windows XP Operating System. As the software is developed to be

implemented by multi-users so the above specified Operating system is

chosen.

2. Choice of Platform: Java is a general-purpose, concurrent, class-based,object-oriented language that is specifically designed to have as few

implementation dependencies as possible. It is intended to let application

developers "write once, run anywhere". Java is currently one of the most

popular programming languages in use, and is widely used from application

software to web applications.

Performance Requirements:

1. Error Handling: The system should be able to manage any error without theusers finding difficult to access the system. Any user input error should be

handled carefully and presented to the user.

2. Quality Issues: The system shall use continuous improvement techniques toestablish, maintain and improve quality. These techniques will be used in

all stages of product life (i.e., design, qualification, ongoing production, and

end of life production). The list of techniques will vary depending upon the

stage of product life and quality performance.


20/58

3. Security Issues: Security is one of the biggest issues when it comes to theproposed sytem

a. The admin should be able to track each and every mail to providesecurity to company data

b. All users must have username and password verifiable login system


21/58

ANALYSIS


22/58

Introduction to UML

Unified Modeling Language is the one of the most exciting tools in the world of system

development today. Because UML enables system builders to create blue prints thatcapture their visions in a standard, easy to understand way and communicate them to

others. The UML is brainchild of Grady Brooch, James Rumbaugh and Ivar Jacobson.

Components of UML:

The UML consists of a number of graphical elements that combine to form

diagrams. Because its a language, the UML has rules for combining these elements. The

purpose of the diagrams to present multiple views of the system, and this set of multiple

views is called a Model. A UML Model of a system is something like a scale model of a

building. UML model describes what a system is supposed to do. It doesnt tell how to

implement the system.


23/58

Introduction to UML

Unified Modeling Language is the one of the most exciting tools in the world of system

development today. Because UML enables system builders to create blue prints thatcapture their visions in a standard, easy to understand way and communicate them to

others. The UML is brainchild of Grady Brooch, James Rumbaugh and Ivar Jacobson.

Components of UML:

The UML consists of a number of graphical elements that combine to form

diagrams. Because its a language, the UML has rules for combining these elements. The

purpose of the diagrams to present multiple views of the system, and this set of multiple

views is called a Model. A UML Model of a system is something like a scale model of a

building. UML model describes what a system is supposed to do. It doesnt tell how to

implement the system.


24/58

Use Case Diagram:

A Use-Case is a description of a systems behavior from a users stand point. For

system developer this is a valuable tool: its a tried-and-true technique for gathering

system requirements from a users point of view. A little stick figure is used to identify

an actor the ellipse represents use-case functions.

Notations of Use Cases

Use cases. A use case describes a sequence of actions that provide something of

measurable value to an actor and is drawn as a horizontal ellipse.

Actors. An actor is a person, organization, or external system that plays a role in one or

more interactions with your system. Actors are drawn as stick figures.

Associations. Associations between actors and use cases are indicated in use case

diagrams by solid lines. An association exists whenever an actor is involved with an

interaction described by a use case. Associations are modeled as lines connecting use

cases and actors to one another, with an optional arrowhead on one end of the line. The

arrowhead is often used to indicating the direction of the initial invocation of therelationship or to indicate the primary actor within the use case. The arrowheads are

typically confused with data flow and as a result I avoid their use.


25/58

System boundary boxes (optional). You can draw a rectangle around the use cases,

called the system boundary box, to indicates the scope of your system. Anything within

the box represents functionality that is in scope and anything outside the box is not.System boundary boxes are rarely used, although on occasion I have used them to

identify which use cases will be delivered in each major release of a system.


26/58

Class Diagrams:

Class diagrams describe the structure of the system in terms of classes and objects.

Classes are abstractions that specify the attributes and behavior of a set of objects. Objects are

entities that encapsulate state and behavior. Each object has an identity: It can be referred

individually and is distinguishable from other objects.

Basic Class Diagram Symbols and Notations

Classes represent an abstraction of entities with common characteristics.

Associations represent the relationships between classes.

Illustrate classes with rectangles divided into compartments. Place the name of

the class in the first partition (centered, bolded, and capitalized), list the attributesin the second partition, and write operations into the third.

Active Class

Active classes initiate and control the flow of activity, while passive classes store

data and serve other classes. Illustrate active classes with a thicker border.

Visibility

Use visibility markers to signify who can access the information contained within

a class. Private visibility hides information from anything outside the class

partition. Public visibility allows all other classes to view the marked information.


27/58

Protected visibility allows child classes to access information they inherited from

a parent class

Associations

Associations represent static relationships between classes. Place association

names above, on, or below the association line. Use a filled arrow to indicate the

direction of the relationship. Place roles near the end of an association. Roles

represent the way the two classes see each other.

Note: It's uncommon to name both the association and the class roles.

Multiplicity (Cardinality)

Place multiplicity notations near the ends of an association. These symbols

indicate the number of instances of one class linked to one instance of the other

class. For example, one company will have one or more employees, but eachemployee works for one company only.


28/58

Composition and Aggregation

Composition is a special type of aggregation that denotes a strong ownership

between Class A, the whole, and Class B, its part. Illustrate composition with a

filled diamond. Use a hollow diamond to represent a simple aggregation

relationship, in which the "whole" class plays a more important role than the

"part" class, but the two classes are not dependent on each other. The diamond

end in both a composition and aggregation relationship points toward the "whole"

class or the aggregate.

Generalization

Generalization is another name for inheritance or an "is a" relationship. It refers

to a relationship between two classes where one class is a specialized version of

another. For example, Honda is a type of car. So the class Honda would have a

generalization relationship with the class car.


29/58

Sequence Diagrams

Sequence diagrams describe interactions among classes in terms of an

exchange of messages over time.

Basic Sequence Diagram Symbols and Notations

Class roles

Class roles describe the way an object will behave in context. Use the UML

object symbol to illustrate class roles, but don't list object attributes.

Activation

Activation boxes represent the time an object needs to complete a task.

Messages

Messages are arrows that represent communication between objects. Use half-

arrowed lines to represent asynchronous messages. Asynchronous messages

are sent from an object that will not wait for a response from the receiver before


30/58

continuing its tasks.

Lifelines

Lifelines are vertical dashed lines that indicate the object's presence over time.


31/58

State Chart DiagramsA statechart diagram shows the behavior of classes in response to external

stimuli. This diagram models the dynamic flow of control from state to state within

a system.

Basic Statechart Diagram Symbols and Notations

States

States represent situations during the life of an object. You can easily illustrate a

state in SmartDraw by using a rectangle with rounded corners.

Transition

A solid arrow represents the path between different states of an object. Label the

transition with the event that triggered it and the action that results from it.

Initial State

A filled circle followed by an arrow represents the object's initial state.


32/58

Final State

An arrow pointing to a filled circle nested inside another circle represents the

object's final state.

Synchronization and Splitting of Control

A short heavy bar with two transitions entering it represents a synchronization of

control. A short heavy bar with two transitions leaving it represents a splitting of

control that creates multiple states.


33/58

Activity Diagrams

An activity diagram illustrates the dynamic nature of a system by modeling the

flow of control from activity to activity. An activity represents an operation on

some class in the system that results in a change in the state of the system.

Typically, activity diagrams are used to model workflow or business processes

and internal operation. Because an activity diagram is a special kind of statechart

diagram, it uses some of the same modeling conventions.

Basic Activity Diagram Symbols and Notations

Action states

Action states represent the noninterruptible actions of objects. You can draw an

action state in SmartDraw using a rectangle with rounded corners.

Action Flow

Action flow arrows illustrate the relationships among action states.

Object Flow

Object flow refers to the creation and modification of objects by activities. An

object flow arrow from an action to an object means that the action creates or


34/58

influences the object. An object flow arrow from an object to an action indicates

that the action state uses the object.

Initial State

A filled circle followed by an arrow represents the initial action state.

Final State

An arrow pointing to a filled circle nested inside another circle represents the final

action state.

Branching

A diamond represents a decision with alternate paths. The outgoing alternates

should be labeled with a condition or guard expression. You can also label one of

the paths "else."


35/58

Synchronization

A synchronization bar helps illustrate parallel transitions. Synchronization is also

called forking and joining.


36/58

Collaboration Diagrams

A collaboration diagram describes interactions among objects in terms of

sequenced messages. Collaboration diagrams represent a combination of

information taken from class, sequence, and use case diagrams describing both

the static structure and dynamic behavior of a system.

Basic Collaboration Diagram Symbols and Notations

Class roles

Class roles describe how objects behave. Use the UML object symbol to

illustrate class roles, but don't list object attributes.

Association roles

Association roles describe how an association will behave given a particular

situation. You can draw association roles using simple lines labeled with

stereotypes.

Messages

Unlike sequence diagrams, collaboration diagrams do not have an explicit way to

denote time and instead number messages in order of execution. Sequence

numbering can become nested using the Dewey decimal system. For example,

nested messages under the first message are labeled 1.1, 1.2, 1.3, and so on.

The a condition for a message is usually placed in square brackets immediately

following the sequence number. Use a * after the sequence number to indicate a


37/58

loop.


38/58

DESIGN


39/58

A software design document (SDD) is a written description of a software product, that a

software designer writes in order to give a software development team an overall

guidance of the architecture of the software project.

An SDD usually accompanies an architecture diagram with pointers to detailed feature

specifications of smaller pieces of the design. Practically, a design document is required

to coordinate a large team under a single vision.

A design document needs to be a stable reference, outlining all parts of the software and

how they will work. The document is commanded to give a fairly complete description,

while maintaining a high-level view of the software.

The SDD contains the following documents:

1. Architecture Design2. User Interface Design3. Data Design


40/58

System/Architecture Design

3 Tier ArchitectureThree-tier[2] is a clientserver architecture in which the user interface, functional

process logic ("business rules"), computer data storage and data access are developed and

maintained as independent modules, most often on separate platforms. It was developed

by John J. Donovan in Open Environment Corporation (OEC), a tools company he

founded in Cambridge, Massachusetts.

The three-tier model is a software architecture and a software design pattern.

Apart from the usual advantages of modular software with well-defined interfaces, the

three-tier architecture is intended to allow any of the three tiers to be upgraded or

replaced independently as requirements or technology change. For example, a change of

operating system in the presentation tier would only affect the user interface code.

Typically, the user interface runs on a desktop PC or workstation and uses a standard

graphical user interface, functional process logic may consist of one or more separatemodules running on a workstation or application server, and an RDBMS on a database

server or mainframe contains the computer data storage logic. The middle tier may be

multi-tiered itself (in which case the overall architecture is called an "n-tier architecture").

Three-tier architecture has the following three tiers:


41/58

Presentation tierThis is the topmost level of the application. The presentation tier displays information

related to such services as browsing merchandise, purchasing, and shopping cart contents.

It communicates with other tiers by outputting results to the browser/client tier and all

other tiers in the network.

Application tier (business logic, logic tier, data access tier, or

middle tier)The logic tier is pulled out from the presentation tier and, as its own layer, it controls

an applications functionality by performing detailed processing.

Data tier

This tier consists of database servers. Here information is stored and retrieved. This

tier keeps data neutral and independent from application servers or business logic. Giving

data its own tier also improves scalability and performance.

Deployment DiagramsDeployment diagrams depict the physical resources in a system including nodes,

components, and connections.

Basic Deployment Diagram Symbols and Notations

Component

A node is a physical resource that executes code components.

Learn how to resize grouped objects like nodes.

Association
http://www.smartdraw.com/resources/tutorials/Objectshttp://www.smartdraw.com/resources/tutorials/Objectshttp://www.smartdraw.com/resources/tutorials/Objects


42/58

Association refers to a physical connection between nodes, such as Ethernet.

Learn how to connect two nodes.

Components and Nodes

Place components inside the node that deploys them.
http://www.smartdraw.com/resources/tutorials/Lineshttp://www.smartdraw.com/resources/tutorials/Lineshttp://www.smartdraw.com/resources/tutorials/Lines


43/58

Sample Screen Shots


44/58


45/58


46/58


47/58


48/58


49/58


50/58


51/58


52/58


53/58


54/58


55/58


56/58


57/58


58/58

Logistics Management Analysis and Design

Documents

Transcript of Logistics Management Analysis and Design