Logistics Page 61

3.2 SOFTWARE DESIGN SPECIFICATION

3.2.1 Introduction

3.2.1.1 Goals and Objectives
The main goals of the software development is to make the current
process simpler, easier to use and more efficient.
The software can store information for a large number of data
about the logistics processes. The application requires a computer with the
needed software loaded that can perform operations like storing and
retrieving data, updating stored information, and printing reports. It
reduces complexity because it does not require any more of a manual
process using pen and paper. It makes the work faster by the use of
computer as it generates reports and transactions easily.









Logistics Page 62

3.2.1.2 Statement of Scope
The Enterprise Operation System is software that allows handling
the Logistics Companys inventory and warehousing operations, as well as
safekeeping the records being maintained by the system. The different
items and functions under the system are identified by unique id.

Major Inputs:
Product name, product description, product quantity
Warehouse name, warehouse location, warehouse quantity storage
Inventory ID, inventory date,

3.2.1.3 Software Context
The software is an efficient application that maintains the database
of Logistics Enterprise Operation System.
It is also user friendly and costs less than any other software
applications available. The developers used Netbeans for front end and
MySQL for the database. The system will run on Windows OS from XP to
Windows 7. It also features an Android application for smart phones
running on Android Gingerbread and up.




Logistics Page 63

3.2.1.4 Major Constraints
The software is to run on a system with SQL therefore it should be
properly connected to the web server to access the database.




















Logistics Page 64

3.2.2 Data Design
To understand the data design of the Enterprise Operation System it is
important to have a look at the overall design of the application.
The application is built in Netbeans and MySQL. The overall application
design can be categorized into three parts based on the mentioned application
development languages.

1. Front End Graphical User Interface
Java Netbeans is being used for the development of the front end of
the user interface. The GUI components temporarily store the input of the
user until it is used for functional procedures.

2. Back End Data
The system is using MySQL as its database which stores all the
information being used in the form of tables. These tables will be globally
available to all the internal procedures. The DBMS system will be
available on the machine where the application is running. However the
same database can be accessed remotely as well
.
3. Internal Functional Structure
The internal functional procedures are the logical entities that carry out
different tasks of adding, updating, deleting, viewing or printing the
database contents.
Logistics Page 65


3.2.2.1 Internal Data Structure

3.2.2.2 Global Data Structure
The data available globally to the whole system is the database
itself stored in MySQL which will be fetched, updated, or deleted on the
system.

3.2.2.3 Temporary Data Structure














Logistics Page 66

3.2.2.4 Database Description
Below are the tables, their corresponding attributes and the
description of each attribute.

Table Name: Warehouse
Attributes: Warehouse ID, WarehouseName, Quantity Storage, Contact
Detail ID, Address ID
Description: Perform an array of functions that might include accepting
and processing incoming stock and materials, picking and filling orders
from stock, packing and shipping orders, or managing, organizing, and
retrieving stock in the warehouse. Primary key of this table is
warehouseID. Foreign key of this table is contact detail ID and AddressID.

Table Name: Inventory
Attributes: InventoryID, ProductID, ProductName, Quantity, BlockCell
Description: Receive, store, and issue materials, equipment, and other
items from stockroom, warehouse, or storage yard. Keep record and
compile stock reports. Primary key of this table is inventoryID. Foreign
key of this table is ProductID.




Logistics Page 67

Table Name: Request for P.O
Attributes: ProductID, Quantity, RequestDate, ReceivedDate
Description: This will forwarded to purchasing orders. Primary key of this
table is ProductID.

Table Name: Pick-Up for Delivery
Attributes: OderID, DeliveredDate, ReceivedDate
Description: to take the order to delivered. Foreign key of this table is
orderID.

Table Name: Back Order
Attributes: ProductID, BackOrderQuantity, Description
Description: returned products delivered to the Company. Primary key of
this table is ProductID.

Table Name: Monitoring
Attributes: ProductID and Raw MaterialID, Quantity, InventoryDate,
WarehouseNo., BadOrder, StockDate
Description: Order lead time, tracking orders for goods, controlling stock
movement such as: establishing minimum stock levels and monitoring the
same; goods receipt quantity inspections; physical stock control in the
warehouse; controlling Specialised Item; and releasing stock from storage
and goods despatch. Primary key of this table is warehouse No.
Logistics Page 68

Table Name: Bad Order
Attributes: ProductID and Raw MaterialID, BadOrderID,
BadOrderQuantity, BadOrderDescription
Description: Defected products brought to warehouse required return to
manufacturing. Foreign key of this table is BadOrderID.

Table Name: Critical Level
Attributes: ProductID, Quantity, WarehouseNo.
Description: A variable that has reached a sufficiently high or low value.
Primary key of this table is productID. Foreign key of this table is
WarehouseNo











.
Logistics Page 69

3.2.3 Architectural and Component Level Design

3.2.3.1 Architectural Diagram

3.2.3.2 Description of Components
3.2.3.2.1 Component

3.2.3.3 Dynamic Behaviour for Component
3.2.3.3.1 Interaction Diagrams














Logistics Page 70

3.2.4 User Interface Design

3.2.4.1 Description of the User Interface
1. Warehouse Management Module


2. Warehouse Management: Product In Module








Logistics Page 71


3. Inventory Monitoring Module








4. Inventory Details Module












Logistics Page 72

5. Manage Critical Module






















Logistics Page 73

3.2.4.2 Interface Design Rules
1. Strive for Consistency
Consistent sequences of actions should be required in
similar situations; identical terminology should be used in prompts,
menus, and help screens; consistent commands should be
employed throughout.

2. Enable Frequent Users to Use Shortcuts
As the frequency of use increases, so do the users desire to
decrease the number of interactions and to increase the pace of
interactions. Abbreviations function keys, hidden commands, and
macro facilities are very helpful to make the work easier.

3. Offer Informative Feedback
For every operator action, there should be some system
feedback. For frequent and minor actions, the response can be
modest, while for infrequent and major actions, the response
should be more substantial.





Logistics Page 74

4. Offer Simple Error Handling
As much as possible, design the system so the user cannot
make a serious error. If an error is made, the system should be able
to detect the error and offer simple, comprehensible mechanisms
for handling the error.

5. Permit Easy Reversal of Actions
This feature relieves anxiety, since the user knows that
error can be undone; it thus encourages exploration of unfamiliar
options. The units of reversibility may be a single action, a data
entry or a complete group of actions.

6. Support Internal Focus of Control
Experienced operators strongly desire the sense that they
are in charge of the system and that the system responds to their
actions. Design the system to make users the initiators of actions
rather than the responders.






Logistics Page 75

7. Reduce Short-term Memory Load
The limitation of human information processing in short-
term memory requires a displays be kept simple, multiple page
displays be consolidated, window-motion frequency be reduced,
and sufficient training time be allotted for codes, mnemonics, and
sequences of actions.

















Logistics Page 76

3.2.5 Restrictions, Limitations and Constraints
1. Only the admin and authorized users have the access to the system.
2. Only the admin can delete records in the system.
3. Every user of the system should have a username and password to
access the system.
4. The functions and data members of the component are called only when
the user requires manipulating the data of the component.
5. The application software is to run on a system with MySQL, therefore
the system should be properly connected to the server to access database.
6. The software should be designed in a way that the processing speed of
the operations should be high.
7. The application is to run on Windows OS and requires the programs of
Netbeans and MySQL.

3.2.6 Testing Issues
Test strategy and preliminary test case specification are presented in this
section. The various tests to be conducted to validate the software developed are
login test.