CHAPTER-3.2 SOFTWARE DESIGN SPECIFICATION

3.2.1 Introduction

This chapter will indicate the aspects of user interface that displays the information of detailed understanding of user needs and requirements. This will discuss how the user will communicate with the system and the description of the user interface, how to integrated our system to another systems.

3.2.1.1 Goals and Objectives

The integrated inventory system is designed to provide a computer based system that will show all the reports and manage, minimize the hassle and solve it quickly under the enterprise operation system. All reports are in graphical representation to help the executive analyze and understand. With this the executive can easily see the progress per department and what is the field that is needed to address. This can be done by the executive anywhere and anytime by the use of mobile application, tablet application android and a web based application.

The system is integrated w/ the other department.

On time receiving of reports.

Quick viewing of reports.

3.2.1.2 Statement of Scope

Inventory system is creating a system that will handle all the inventory reports in all sub systems of enterprise operation system. And allow the user to put there personal details by use of there security before gaining access to the Integrated Inventory System (IIS) of the officer must enter an authentic username and password. The level of privileges differs to the position of the user. Integrated inventory officer has a full access to the system whereas Executive has a fewer access he/she can only browse and see the reports per department in real time everyday.

3.2.1.3 Software contextIntegrated Inventory System is many components but the ability of it will dictate how far it can stay in the business. The ability of the system is to view, all the reports in graphical form and displaying the top five issues. 3.2.1.4 Major Constraints

Every user should have a basic technical skills needed to operate the system.

The Integrated Inventory System will use JAVA which requires a MYSQL and XAMPP for database connection.

Specification of the computer hardware must be modified to the requirements of the system usage. The system must be perform very well.

3.2.2 Data Design

3.2.2.1 Internal Data Structure

Internal Data Structure is design to show the user and enhance the ability to view and generate the summary of all reports.

3.2.2.2 Global Data StructureThe Global Data Structure is globally design in whole system to store all data in Mysql.

3.2.2.3 Temporary Data StructureThe Inventory Deployment System is doesnt have a temporary data. Database is not included to our system. Hence no files or data structures are used.

3.2.2.4 Database DescriptionBelow are mentioned all tables, and there corresponding attributes and description.

Table Name: Customer

Attributes: Customer ID, Customer Last Name, Customer Middle Name, Customer First Name, Customer Address, Customer Type, Contact No.Description: It keeps all the general information of all customers in Customer Relationship Management by ordering products. Primary key of this table is Customer ID and the foreign key is Contact No. and Customer Address.

Table Name: Employee

Attributes: Employee Id, Employee Last Name, Employee Middle Name, Employee First Name, Employee Contact ID, Employee Address ID, Employee Department ID, Employee Position ID.

Description: It keeps all the general information of all employees in every designated department. Primary key of this table is Employee ID. Foreign key of this tables are Employee Contact ID, Employee Department ID and lastly the Employee Position ID.

Table Name: Department

Attributes: Department ID, Department Name, Department Description

Description: It keeps all the general information of every department. Primary key of this table is Department ID.

Table Name: Product

Attributes: Product ID, Product Name, Description, Category ID, Product Type ID, Product Supplier ID, Product Unit Price.

Description: It keeps all the general information of all products. Primary key of this table is Product ID. Foreign key of this table are Category ID, and Product Type ID.

Table Name: Warehouse

Attributes: Warehouse ID, Warehouse Name, Warehouse Quantity Storage, Warehouse Contact Detail ID, Warehouse Address ID.

Description: It keeps all the general information of the records in warehouse. Primary key of this table is Warehouse ID. Foreign key of this tables are Warehouse Detail ID, Address ID. Table Name: Log Vehicle Monitoring

Attributes: Monitoring ID, Vehicle ID, Deliver Name, Warehouse ID, Date In, Time In, Date Out, Park Location, Remarks, Status, Employee ID.

Description: It keeps all the general information of the records in Logistic Transportation. Primary key of this table is Monitoring ID. Foreign key of this table are Vehicle ID, Warehouse ID and Employee ID.

Table Name: Manufacturing Planning and Scheduling

Attributes: Schedule ID, Product ID, Batch ID, Quantity Quotes, Product Time Start, Product Time End.

Description: It keeps all the general information of the records in Manufacturing Planning and Scheduling. Primary key of this table is Schedule ID. Foreign key of this table is Product ID.

Table Name: Manufacturing Execution Quality Control Test

Attributes: Quality Control Test ID, Process ID, Test Status, Remarks, Test by employee ID, Test Date, Test Time.

Description: It keeps all the general information of the records in Manufacturing Execution. Primary key of this table is Quality Control Test ID. Foreign key of this table are Process ID and Employee ID.

Table Name: Purchase Order

Attributes: Purchase Order ID, Supplier ID, Employee ID, Order Date, Required Date, Item ID, Item Name, Quantity, Price, Amount.

Description: It keeps all the general information of the records in Purchasing Department. Primary key of this table is Purchase Order ID. Foreign Key of this table is Supplier ID.

3.2.3 Architectural and Component Level Design

3.2.3.1 Architectural DiagramThe Architectural Context diagram for the software is shown below. The various actors are the Integrated Inventory Staff and the Executive Officer which use the system. The back end software that used in the system is MYSQL and Java that need for testing and maintenance intention for the main purposes of our Inventory Deployment System.

Uses UsesFigure 1- Architectural Context DiagramArchitectural Context Diagram

For using the system the accounts need to be restricted for the administrator use only, for example the Administrator also is the Integrated Inventory Officer has the full access of the system. While the Executive can only view the reports.The call and return for the Inventory Deployment Software System is shown below (Using UML Component Diagram.

The Call and Return architecture Diagram

The Call and Return architectural diagram design classes are made, and the component level of designing is done. Under every component has a class, for example the Integrated Inventory Officer class bear name and position. Other similar content are elaborated. Each function is connected to one another to show the flow of the running systems.

3.2.3.2 Description of Components3.2.3.2.1 Processing narrative of component for Inventory DeploymentThe Inventory Deployment component consists of the design and operated in every department. It contains the attributes, which are the basic data of the system. The system will use java which requires a MYSQL for database connection. The design shows the user and enhances the ability to view and generate the summary of all reports. It shows all the reports and generate, under the enterprise operations system.3.2.3.2.2 Interface description of component for Inventory Deployment

The Inventory Deployment has an interface which consists of Customer Relationship Management and will keep all the general information of all customers in ordering products.

The employees designated in every department and the executive keeps all the general information and reports. The warehouse is responsible for keeping the raw materials use in producing a finish product.

Executive keeps all the general information of all records and reports.3.2.3.2.3 Algorithmic description of component for Inventory DeploymentComponent Inventory;

The intent of this component is to view and generate of all summary reports. Executive Dashboards Log on the System

Determine users authentication Executive log on as admin.

Select reports

View

End3.2.3.2.1 Design hierarchy of component Manager

Component Employees/Manager

The intent of this component of Inventory Deployment is to set the basic data of employees into the database and get the basic data from database.

StartDeclare the variables of the basic data of the Employees in Inventory Deployment

Set the basic data of the Employees in the database

Get the basic data from database

End3.2.3.2.2 Design hierarchy of component Customer Relationship Officer

Component Customer Relationship Officer

The intent of this component of Inventory Deployment is to set the basic data of the Customer Relationship Management into the database and get the basic data from database.

StartDeclare the variables of the basic data of the Customer Relations Officer in Inventory Deployment

Set the basic data of the Customer Relations Officer in the database

Get the basic data from database

End3.2.3.2.3 Design hierarchy of component Stockman Officer

Component Stockman Officer

The intent of this component of Inventory Deployment is to set the basic data of Stockman Officer into the database and get the basic data from database.

StartDeclare the variables of the basic data of the Stockman Officer in Inventory Deployment

Set the basic data of the Stockman Officer in the database

Get the basic data from database

End3.2.3.2.4 Design hierarchy of component Manufacturer Officer

Component Manufacturer Officer

The intent of this component of Inventory Deployment is to set the basic data of Manufacturer Officer into the database and get the basic data from database.

StartDeclare the variables of the basic data of the Manufacturer Officer in Inventory Deployment

Set the basic data of the Manufacturer Officer in the database

Get the basic data from database

End3.2.3.2.5 Design hierarchy of component Logistics Officer

Component Logistics Officer

The intent of this component of Inventory Deployment is to set the basic data of Logistics Officer into the database and get the basic data from database.

StartDeclare the variables of the basic data of the Logistics Officer in Inventory Deployment

Set the basic data of the Logistics Officer in the database

Get the basic data from database

End

3.2.3.2.6 Design hierarchy of component Purchasing Officer

Component Purchasing Officer

The intent of this component of Inventory Deployment is to set the basic data of Purchasing Officer into the database and get the basic data from database.

StartDeclare the variables of the basic data of the Purchasing Officer in Inventory Deployment

Set the basic data of the Purchasing Officer in the database

Get the basic data from database

End

3.2.3.3 Dynamic behavior for Component

3.2.3.4 Interaction Diagrams

System ready Password entered

Request lookup

Result

No. of tries > matries

Password correct

Give access to Executive officer

Executive views all the reports

For viewing X X XFigure (a)

This is a sequence diagram where the use case component is a CEO. The first event system ready, is derived from the external environment and channels behavior to CEO. The CEO enters a Username and password. A request lookup event is passed to system that looks up the password in the software system and returns a result (found or not found) to monitor. A valid password results in a password correct event to software system which then gives access to the CEO and the CEO views all the reports. And this data can view all the reports of the system. System ready

Password entered

Request lookup Result No of tries > maxtries Password correct

Gives access to Inventory Officer Inventory Manager views the reports For Viewing

X X XFigure (b)This is a sequence diagram where the use case component is an Inventory Officer/Manager. The first event system ready, is derived from the external environment and channels behavior to Inventory Manager. The Inventory Manager enters a password. A request lookup event is passed to system that looks up the password in the software system and returns a result (found or not found) to monitor. A valid password results in a password correct event to software system which then gives access to the Inventory Manager and the Inventory Manager views all the reports. And this data can view all the reports of the system.3.2.4 User Interface DesignThe application has a Graphical User Interface, which is completely connected in java. We have chosen a Java Net beans for enhancing the development and to use the efficient design in our Inventory Deployment System. To ensure also the good appearance, of our system.

3.2.4.1 Description of the User Interface3.2.4.1.1 Screen ImagesThe Graphical User Interface for the Executive has been kept, easy to use and it is a user friendly. They dont have required any expert people in computer literate to use this.

Below is detailed images and description of the Graphical User Interface. The Images and actions selected when you click them are also identified.

3.2.4.2 Interface Design RulesTo improve the usability of an application it is important to have well design interface. These Eight Golden Rules of Interface Design are a guide to good interaction design.

1.) Strive for consistency.

Consistent sequences of actions should be required in familiar situations; identical terminology should be used in prompts, menus, and help screens; and consistent commands should be employed throughout.2.) Enable frequent users to use shortcuts.

As the frequency of orders increase, so do the users desires to reduce the number of interactions and to increase the pace of interaction. Abbreviation function keys, hidden commands, and macro facilities are very helpful to an expert user.

3.) Offer informative feedback.

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

4.) Design dialog to yield closure.

Sequence of actions should be organized into groups with a beginning, middle, and end. The informative feedback at the completions of group of actions gives the operators the satisfaction of accomplishment, a sense of relief, the signal to drop contingency plans and options from their minds, and an indication that the way is clear to prepare for the next group of actions.5.) Offers simple error handling.

As much as possible, design the system does 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.

6.) Permit easy reversal of actions.

This feature relieves anxiety, since the user knows that errors 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.7.) Supports internal locus 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.

8.) Reduce short-term memory load.

The limitations of human information processing in short-term memory require that displays be kept simple, multiple page displays are consolidated, windows-motion frequency be reduced, and sufficient training time and allotted for codes, mnemonics, and sequence of actions.

3.2.4.3 Components AvailableThe component that we use in our system is JavaScript that display an appropriate response to an error or right access in the system. More components may be added in future if necessary. 3.2.4.4 UIDS Description

We have no development used in our Interface, and it is fixing for the user and for Executive officer only as to view a whole system. 3.2.5 Restriction, Limitations and Constraints

Only the Executive Officer can actually access and manage of the whole system.

All validate code shall be written in Java.

The system must be designed in such a way that will be easy to use and interactive. Two Selected admin can access to the system.

The characters of the password that the ADMIN can use are between 6 to 15 characters only.

The system can view reports by illustrating in graphical presentation. The system can integrate with the existing Wireless Connection.

The web server is the remote computer system that maintains the database and serves web pages to the system.

The system is created in code that is written in Net Beans IDE with the help of MySQL for running the system and database. 3.2.6 Testing Issues

Testing issues is an important stage in any system development cycle. Testing is the set of activities that can be planned in advance and conducted systematically. Different test conditions should be thoroughly checked and the bugs detected should be fixed. The testing strategies formed by the user are performed to prove that the software is free and clear from errors. To do this, there are many ways of testing the systems reliability, completeness and maintainability.Software validation will guarantee that the system responds according to the users expectations, for that reason it is essential that the end users will be involved in some phases of the test procedure. Unit testing will be conducted on all of software subsystems. Tests to be conducted to validate the software developed are login test, test patient, maintenance.

There are testing techniques that will be available in the system. Test cases for black box testing will be based on equivalence categories. These categories will include values that lie on and around the boundary values of a function. Acceptance testing will be conducted at the customers side.Unit testing will be conducted on all of software subsystems including

1. Logging on to the system

2. Database Security

3. Database Connection

4. Receiving and Releasing Products

5. Viewing and Printing Reports

7. Planning and SchedulingTABLE OF FIGURES

Figure 1: Architecture Context Diagram

Uses UsesFigure 2: Call and Return Architecture Diagram

Figure 3: Object Oriented Architecture Diagram

Figure 4: Sequential Diagram

System ready Password entered Request lookup Result No of tries > maxtriesPassword correct Gives access to Executive Officer Executive views all the reports For viewing

X X X

View reports

Locked

Inventory Deployment Software

Comparing

Reading

Monitor ready

CEO

Purchasing Department

Basic Information of Delivery Officer

Basic Information of Stockman Officer

Manufacturing Department

Logistics/Transportation Department

Logistics/Warehouse Department

Sign in/Sign Out

Users Basic Information

Customer Relationship Department

View Reports

Graphical User Interface (GUI)

External Communication Management

Main Inventory Deployment Software

Database (MYSQL)

Java (and JDBC Drivers)

Inventory Deployment System

Executive

Officer

Inventory Integrated Officer

Maintenance and self test

Basic Information of Purchasing Officer

Purchasing Department

Basic Information of Manufacturer Officer

Basic Information of Customer Relation Officer

Customer Relationship Department

Print/Display Reports

Basic Information of Delivery Officer

Basic Information of Stockman Officer

Manufacturing Department

Logistics/Transportation Department

Logistics/Warehouse Department

Sign in/Sign Out

Users Basic Information

Database (MYSQL)

Java (and JDBC Drivers)

Inventory Deployment System

Executive

Officer

Inventory Integrated Officer

Maintenance and self test

View reports

Locked

Inventory Deployment Software

Comparing

Reading

Monitor ready

Inventory Officer

View reports

Locked

Comparing

Reading

Monitor ready

CEO

Inventory Deployment Software

Inventory Integrated Officer

admin_id:int

password:int

first_name:varchar

middle_name:varchar

last_name:varchar

address:varchar

contact_no:int

set_admin_id()

set_password()

set_first_name()

set_middle_name()

set_last_name()

set_address()

set_contact_no()

get_admin_id()

get_password()

get_first_name()

get_middle_name()

get_last_name()

get_address()

get_contact_no()

Manufacturer

Officer

mo_id:int

password:int

first_name:varchar

middle_name:varchar

last_name:varchar

address:varchar

contact:int

set_mo_id()

set_password()

set_first_name()

set_middle_name()

set_last_name()

set_address()

set_contact_no()

get_mo_id()

get_password()

get_first_name()

get_middle_name()

get_last_name()

get_address()

get_contact_no()

User

user_id

password

first_name

middle_name

last_name

address

contact_no

main

Executive Officer

eo_id

password

first_name

middle_name

last_name

address

contact_no

view dashboard

Purchasing Officer

po_id

password

po_first_name

po_middle_name

po_last_name

address_id

contact_id

set_po_id()

set_password()

set_first_name()

set_middle_name()

set_last_name()

set_address_id()

set_contact_id

get_po_id()

get_password()

get_first_name()

get_middle_name()

get_last_name()

get_address_id()

get_contact_id()

Executive Officer

Person

getFirstname()

setFirstname()

Logistics Officer

lo_id

password

lo_first_name

lo_middle_name

lo_last_name

address_id

contact_id

set_lo_id()

set_password()

set_first_name()

set_middle_name()

set_last_name()

set_address_id()

set_contact_id

get_lo_id()

get_password()

get_first_name()

get_middle_name()

get_last_name()

get_address_id()

get_contact_id()

Executive Officer

Person

getFirstname()

setFirstname()

Manufacturer Officer

mo_id

password

mo_first_name

mo_middle_name

mo_last_name

address_id

contact_id

set_mo_id()

set_password()

set_first_name()

set_middle_name()

set_last_name()

set_address_id()

set_contact_id

get_mo_id()

get_password()

get_first_name()

get_middle_name()

get_last_name()

get_address_id()

get_contact_id()

Executive Officer

Person

getFirstname()

setFirstname()

Executive Officer

Person

getFirstname()

setFirstname()

Stockman Officer

so_id

password

so_first_name

so_middle_name

so_last_name

address_id

contact_id

set_so_id()

set_password()

set_first_name()

set_middle_name()

set_last_name()

set_address_id()

set_contact_id

get_so_id()

get_password()

get_first_name()

get_middle_name()

get_last_name()

get_address_id()

get_contact_id()

Customer Relationship Officer

crm_id

password

crm_first_name

crm_middle_name

crm_last_name

address_id

contact_id

set_crm_id()

set_password()

set_first_name()

set_middle_name()

set_last_name()

set_address_id()

set_contact_id

get_crm_id()

get_password()

get_first_name()

get_middle_name()

get_last_name()

get_address_id()

get_contact_id()

Executive Officer

Person

getFirstname()

setFirstname()

Logistics

Officer

lo_id:int

password:int

first_name:varchar

middle_name:varchar

last_name:varchar

address:varchar

contact:int

set_lo_id()

set_password()

set_first_name()

set_middle_name()

set_last_name()

set_address()

set_contact_no()

get_lo_id()

get_password()

get_first_name()

get_middle_name()

get_last_name()

get_address()

get_contact_no()

Purchasing

Officer

po_id:int

password:int

first_name:varchar

middle_name:varchar

last_name:varchar

address:varchar

contact:int

set_po_id()

set_password()

set_first_name()

set_middle_name()

set_last_name()

set_address()

set_contact_no()

get_po_id()

get_password()

get_first_name()

get_middle_name()

get_last_name()

get_address()

get_contact_no()

Manufacturer

Officer

mo_id:int

password:int

first_name:varchar

middle_name:varchar

last_name:varchar

address:varchar

contact:int

set_mo_id()

set_password()

set_first_name()

set_middle_name()

set_last_name()

set_address()

set_contact_no()

get_mo_id()

get_password()

get_first_name()

get_middle_name()

get_last_name()

get_address()

get_contact_no()

Stockman

Officer

so_id:int

password:int

first_name:varchar

middle_name:varchar

last_name:varchar

address:varchar

contact:int

set_so_id()

set_password()

set_first_name()

set_middle_name()

set_last_name()

set_address()

set_contact_no()

get_so_id()

get_password()

get_first_name()

get_middle_name()

get_last_name()

get_address()

get_contact_no()

Customer Relationship

Officer

crm_id:int

password:int

first_name:varchar

middle_name:varchar

last_name:varchar

address:varchar

contact:int

set_crm_id()

set_password()

set_first_name()

set_middle_name()

set_last_name()

set_address()

set_contact_no()

get_crm_id()

get_password()

get_first_name()

get_middle_name()

get_last_name()

get_address()

get_contact_no()

Inventory Integrated Officer

admin_id:int

password:int

first_name:varchar

middle_name:varchar

last_name:varchar

address:varchar

contact_no:int

set_admin_id()

set_password()

set_first_name()

set_middle_name()

set_last_name()

set_address()

set_contact_no()

get_admin_id()

get_password()

get_first_name()

get_middle_name()

get_last_name()

get_address()

get_contact_no()

View Reports

Graphical User Interface (GUI)

External Communication Management

Main Inventory Deployment Software

Basic Information of Purchasing Officer

Basic Information of Manufacturer Officer

Basic Information of Customer Relation Officer

Print/Display Reports

Employees/Manager

emp_id

emp_last_name

emp_first_name

emp_middle_name

contact_id

address_id

dept_id

emp_pos_id

set_id()

set_last_name()

set_first_name()

set_middle_name()

set_id()

set_address_id()

set_dept_id()

set_pos_id()

get_id()

get_last_name()

get_first_name()

get_middle_name()

get_id()

get_address_id()

get_dept_id()

get_pos_id()

Executive Officer

Person

getFirstname()

setFirstname()

Reports

view_reports

print_reports

select_type_reports

Purchasing

Officer

po_id:int

password:int

first_name:varchar

middle_name:varchar

last_name:varchar

address:varchar

contact:int

set_po_id()

set_password()

set_first_name()

set_middle_name()

set_last_name()

set_address()

set_contact_no()

get_po_id()

get_password()

get_first_name()

get_middle_name()

get_last_name()

get_address()

get_contact_no()

Logistics

Officer

lo_id:int

password:int

first_name:varchar

middle_name:varchar

last_name:varchar

address:varchar

contact:int

set_lo_id()

set_password()

set_first_name()

set_middle_name()

set_last_name()

set_address()

set_contact_no()

get_lo_id()

get_password()

get_first_name()

get_middle_name()

get_last_name()

get_address()

get_contact_no()

Customer Relationship

Officer

crm_id:int

password:int

first_name:varchar

middle_name:varchar

last_name:varchar

address:varchar

contact:int

set_crm_id()

set_password()

set_first_name()

set_middle_name()

set_last_name()

set_address()

set_contact_no()

get_crm_id()

get_password()

get_first_name()

get_middle_name()

get_last_name()

get_address()

get_contact_no()

Stockman

Officer

so_id:int

password:int

first_name:varchar

middle_name:varchar

last_name:varchar

address:varchar

contact:int

set_so_id()

set_password()

set_first_name()

set_middle_name()

set_last_name()

set_address()

set_contact_no()

get_so_id()

get_password()

get_first_name()

get_middle_name()

get_last_name()

get_address()

get_contact_no()

Inventory Deployment SystemPage 13