CHAPTER 3

3.1 SOFTWARE REQUIREMENTS SPECIFICATION

3.1.1 Introduction
3.1.1.1 Goal and o!"#cti$#
The purpose of this document is to describe requirements for an
Enterprise Operation System that will serve as a foundation for the final
product. It is of importance that an agreement of these requirements will
be reached so that everyones expectation will be met. This document uses
written descriptions as well as different types of modeling diagrams to
illustrate the high level structure of the system. lthough some of these
diagrams may seem to convey similar information they typically do so
from an alternate perspective. This gives different sta!eholders a view of
the requirements that is better suited to their area of responsibility.
The system is a "eb#based application. Only authori$ed personnel
and user will gain access to the system by means of a log in engine. %y
designing around a standardi$ed language li!e &ava' the application will
run on the most popular computer platforms. centrali$ed database
connected to the system will allow the users to store large amount of
information.
Logistics Page 23
The Enterprise Operation System is intended to provide an
enhanced' computer#based system that will assist the logistics companys
operations.
Logistics Page 24
3.1.1.% Stat#&#nt o' Sco(#
This section contains a general description of the software
functionality followed by detailed requirements that will be traced
throughout the pro(ect.
%efore gaining access to the system' the user will be required to
enter their user name and password. The main user of this system is the
admin who will have unlimited access privileges within the system.
dministrators are responsible for adding new information to the
system' as well as viewing and updating the existing records.
3.1.1.3 So't)ar# Cont#*t
"ith the increasing effect of globali$ation and technology'
organi$ations have started to use information systems in various functions
and departments in the last decades. )ogistics management is a supply
chain management component that is used to meet customer demands
through the planning' control and implementation of the effective
movement and storage of related information' goods and services from
origin to destination. )ogistics management helps companies reduce
expenses and enhance customer service.
Logistics Page 25
The logistics management process begins with raw material
accumulation to the final stage of delivering goods to the destination. %y
adhering to customer needs and industry standards' logistics management
facilitates process strategy' planning and implementation.
In logistics management' unwise decisions create multiple issues.
*or example' deliveries that fail or are delayed lead to buyer
dissatisfaction. +amage of goods' due to careless transportation' is another
potential issue. ,oor logistics planning gradually increases expenses' and
issues may arise from the implementation of ineffective logistics software.
-ost of these problems occur due to improper decisions related to
outsourcing' such as selecting the wrong vendor or carrying out delivery
tas!s without sufficient resources.
To resolve these issues' organi$ations should implement best
logistic management practices. .ompanies should focus on collaboration
rather than competition. /ood collaboration among transportation
providers' buyers and vendors helps reduce expenses. lso' an efficient
and safe transportation provider is vital to business success.
3.1.1.+ Ma"or contraint
The )ogistics -anagement system server codes will be written in
&ava.
Logistics Page 26
3.1.% Ua,# Sc#nario
3.1.%.1 U#r Pro'il#
The following definitions describe the actors in the system.
dministrator n administrator has the responsibility for
registering new 0ser ccount. They have the
authority to access the system including dd' Edit'
1iew and .hanging password 2 user.
System The system refers to the tangibles and Intangible
parts of the system that controls the application.
Server The server is a remote computer system that
maintains the database and serves pages to the
system
3.1.%.1 U#-ca#
The following use#cases are typical interactions between the external
environment and the internal software system.
3. /eneral 0se#.ase +iagram
3.1.%.%.1 U#-Ca# .ia,ra&
Logistics Page 27
Fi,ur# 1/ G#n#ral U#-Ca# .ia,ra&
3.1.%.%.% U#-Ca# .#cri(tion
Logistics Page 28
dmin
4ew *inished ,roduct
nd ingredients
-onitoring Of
item
/et orders of
client from .5-
5eturn %ad orders
and %ac! orders
5equesting
ingredients in ,.O
4otification of
critical level in
,roduct and
ingredients
.ollect all
available
ingredients and
products
Inventory
"arehouse
personnel
0se .ase6 )og onto the System
,rimary ctor6 "arehouse dministrator
/oal in .ontext6 To gain access to the system
,reconditions6 -ust have a valid 0serI+ and ,assword
Trigger6 n access to perform their (obs
Scenario6 The System ,rompts for a 1alid 0serI+ and ,assword.
The administrators enter their 0sername and ,assword.
The System Sends 0serI+ and ,assword to the Server.
The Server sends bac! the password registered to the 0serI+.
The system verifies the password and sets the users authori$ation.
The administrator is given access to use the system to perform their
(ob.
Ta!l# 1/ U#-Ca# .#cri(tion
0se .ase6 "arehouse -anagement
,rimary ctor6 dministrator
/oal in .ontext6 To manage the transactions inside the warehouse
,reconditions6 -ust have a valid 0serI+ and ,assword
Trigger6
Scenario6 The dministrator must log onto the system.
The dministrator selects "arehouse -anagement from the main
menu.
The administrator has the option if 7e8She wants to 1iew Information
of ,roduct' 5e(ect ,roduct' Save 5e(ect ,roduct for 5epair or -anage
Logistics Page 29
,roduct for Storage.
The administrator must save all the changes.
The administrator receives confirmation that the changes have been
saved.
Ta!l# %/ U#-Ca# .#cri(tion
0se .ase6 *inished Inventory
,rimary ctor6 dministrator
/oal in .ontext6 To manage the *inished Inventory transactions
,reconditions6 -ust have a valid 0serI+ and ,assword
Trigger6
Scenario6 The dministrator must log onto the system.
The dministrator selects *inished Inventory from the main menu.
The administrator has the option if 7e8She wants to view and update the 4ew
*inished ,roduct' Inventory of *inished ,roducts and the 4umber of 5e(ects.
The administrator must save all the changes.
The administrator receives confirmation that the changes have been save.
Ta!l# 3/ U#-Ca# .#cri(tion
Logistics Page 30
0se .ase6 Order ,rocessing
,rimary ctor6 dministrator
/oal in .ontext6 To manage the transactions of Order ,rocessing
,reconditions6 -ust have a valid 0serI+ and ,assword
Trigger6
Scenario6 The dministrator must log onto the system.
The dministrator selects Order ,rocessing from the main menu.
The administrator has the option if 7e8She wants to view and update the
,roduct Order Information' ,roduct 5elease Information' ,roduct vailable'
Out of Stoc! ,roduct' and 5eady for +elivery Information.
The administrator must save all the changes.
The administrator receives confirmation that the changes have been save.
Ta!l# +/ U#-Ca# .#cri(tion
Logistics Page 31
3.1.%.3 S(#cial ua,# Conid#ration
The proposed system will only focus on warehouse management'
monitoring of raw material' finished product' and deployment of the
product. ny system that may occur in the proposed system is not our
concern anymore.

3.1.%.+ Acti$it0 .ia,ra&
Fi,ur# %/ Acti$it0 .ia,ra& 'or 1o, In
In *igure 9 Shows the steps ta!en as an administrator logs on to the computer
system. ccess is granted if the correct username and password combination is entered
Logistics Page 32
Prompt User and Password
Enter user and Password
Check Bad Entries
Success Log In
Verify User and Password
Blocked
Try
Incorrect
within the first attempts. fter the three attempts the username and password will be
bloc!ed and the username and password is automatically.
Fi,ur# 3/ Acti$it0 .ia,ra& 'or War#2ou# Mana,#&#nt
Logistics Page 33
Log onto System
Inbound anage Product
Checking
Select to manage the
type of Product into Store
!oom
Count the Product
!e"ected
Try again
Fi,ur# +/ Acti$it0 .ia,ra& 'or Fini2#d In$#ntor0
Logistics Page 34
Try again
.hec!ing
Log onto System
Check #ew $inished
Product
Count !e"ect
Count the number of
product for In%entory for
time to time
Checking for the !e"ected
Product
Log onto System
View Product Information
&ut of Stock Product
!eady to 'ransportation
Product (%ailable
Fi,ur# 3/ Acti$it0 .ia,ra& 'or Ord#r Proc#in,
Logistics Page 35
Try again
1erify
)og onto system
Check order Product
&ut of stock
Sent notify of out of stock
View order product
Fi,ur# 4/ Acti$it0 .ia,ra& 'or Noti'ication o' Out o' Stoc5 Product
Logistics Page 36
)og onto system
Checking the dispatching
product to deli%ered
Encode total bill of
transporting for
costing
'ransport product
)i%e petty cash to dri%er
)et !eceipt for Costing
Fi,ur# 6/ Acti$it0 .ia,ra& 'or Cotin,
Logistics Page 37
Log onto System
View the Product will
deli%er
Verify
Log out
Check product if
a%ailable
Fi,ur# 7/ Acti$it0 .ia,ra& 'or R#ad0 to .#li$#r0
Logistics Page 38
Fi,ur# 8/ Acti$it0 .ia,ra& 'or Mat#rial 'ro& di''#r#nt War#2ou# ar# Monitor#d
Logistics Page 39
1iew
Log onto System
View all materials to
warehouse
&rder
Sending notification to
P* for una%ailable
materials
Check una%ailable
materials
1erify
Fi,ur# 19/ Acti$it0 .ia,ra& 'or FIFO M#t2odolo,0
Logistics Page 40
Log onto System
Check oldest Product for
+ispatching
Collect for
ordering
)et oldest product
anage the nearest
product and bring to
down of oldest Product
,rocess
Fi,ur# 11/ Acti$it0 .ia,ra& 'or Pat:Slo) Mo$in,
Logistics Page 41
Log onto System
View all products in database
Print
Un,buyable product
Select the 'op -. most
buy
1iew
Print
Fi,ur# 1%/ Acti$it0 .ia,ra& 'or P.O Co&(arion
Logistics Page 42
Log onto System
View Product order
Compare if E/ually to P*&
$orm to +ispatching
Product
!eorder
Checking P*& $orm order
Out of Stoc!
Collect order product
Fi,ur# 13/ Acti$it0 .ia,ra& 'or Monitor R#ord#r:Critical l#$#l
Logistics Page 43
Log onto System
View Product (%ailable
Sending of
notification to P*
Verifying
Checking if it is not critical
Le%el
.ount
1iew
3.1.3 .ata Mod#l .#cri(tion
3.1.3.1 .ata o!"#ct
)ogistics dmin +ata Ob(ects
0serI+6 unique identifier assigned to the employee.
,asswordI+6 The employees password used to log on to the computer system.
4ame6 The )ogistics dmin name
5eport6 admin report about the status of storage.
Operation -anager +ata Ob(ects
0serI+6 unique identifier assigned to the employee.
,assword6 The employees password used to log on to the computer system.
4ame6 The operation manager name.
"or!ers +ata Ob(ects
0serI+6 unique identifier assigned to the employee.
,assword6 The employees password used to log on to the computer system.
4ame6 The wor!ers name.
.lassification6 The (ob classification of the wor!ers. )imited to administrator or
Operation manager.
Logistics Page 44
"arehouse +ata Ob(ects
4ame6 The name of the warehouse.
ddress6 The address of the warehouse.
,hone 4umber6 The phone number of the warehouse.
)ogistics dmin6 The name of the logistics admin assigned to the warehouse.
Operation -anager6 The name of the operation manager assigned to the
warehouse.
"or!ers6 The name of the wor!ers assigned to the warehouse.
,roduct +ata Ob(ects
,roductI+6 unique identifier assigned to the product.
4ame6 The product name.
.ategory6 The product category.
-anufactured6 The product manufactured.
Inventory +ata Ob(ects
,roductI+6 The identifier number of a product.
4ame6 The product name.
.ategory6 The product category.
Logistics Page 45
Order +ata Ob(ects
Order Info6 The information of the ordered by client.
,roductI+6 The identifier number of a product.
4ame6 The product name.
.ategory +ata Ob(ects
,roductI+6 The identifier number of a product.
4ame6 The product name.
5epaired +ata Ob(ects
4ame6 The product name.
.ategory6 The product category.
5e(ect6 The re(ect of the item.
5eminder +ata Ob(ects
Operation -anager6 The Operation -anager remind the wor!ers.
+ate6 The date of the reminder.
.omment8-essage6 The reminder comment8message to be displayed.
Logistics Page 46
.osting +ata Ob(ects.
%illing Info6 Total of all extra billing fees.
.ategory6 The category of the product.
4ame6 The name of the person assigned to deliver.
Type6 The type of a vehicle.
)ocation6 The location to deliver.
Logistics Page 47
3.1.3.% R#lation2i(
The )ogistics admin or user of the system shall have an account
first before accessing the system.
The company should have a warehouse to !eep the products for
storage creating a one#to#many relationship. The warehouse will be
managed by a warehouse assistant
number of products may be stored in a single warehouse. Each
product will be categori$ed and labeled according to its category.
product shall have a product id' thus consisting of a one#to#one
relationship.
Each product is sub(ect to inventory process wherein the products
are listed and categori$ed based on its quantity and state.
n inventory has different labels' according to the quantity' the products
state if it is in o! state or damaged or for repair.
In order processing' a certain product is requested wherein an
invoice or receipt is received after the payment and the product is now
sub(ect for deployment.
*or deployment' the company shall have vehicles to deliver the
product to its designation. single vehicle may contain various products
to be deployed to different areas.
The system shall be able to trac! the deliveries to ma!e sure that
the products are deployed on their respective designations.
Logistics Page 48
3.1.3.3 Co&(l#t# data &od#l
The relationships between the data ob(ects describe in section :.9 are show
in *igure 3;.
Fi,ur# 1+/ R#lation2i( .ia,ra& 'or t2# 1MS
Logistics Page 49
4ame
ddress
,hone 4umber
"arehouse
4ame
.ategory
-anufactured

,roduct
+ate
.omment

5eminders
4ame
.ategory
Order
4ame
.ategory
Inventory
4ame
.ategory
5e(ect
5epaired
4ame
5eport
Operation -anager
4ame
.lassification
"or!ers
4ame
5eport
)ogistics dmin
3.1.+ Functional Mod#l .#cri(tion
3.1.+.1 Cla .ia,ra&
Fi,ur# 13/ 1o,itic Mana,#&#nt S0t#& Cla .ia,ra&
Logistics Page 50
+aily 5eminder
#date
#message
#next5eminder
<add=>
<remove =>
<chec!=>
)ogistics -anagement System .lass +iagram
,roduct
#,roductI+
#4ame
#.ategory
#-anufactured
#next,roduct
<add=>
<edit=>
<remove=>
"or!ers
#*irst4ame
#)ast4ame
#.lassification
-
NextEmploy
ee
<promote=>
<demotes=>
<terminated=>
<add"or!ers=>
Operation -anager
#0serI+
#,asswordI+
#*irst4ame
#)ast4ame
#nextO-
<promote=>
<demotes=>
<terminated=>
<addO-=>
.osting
#Type1ehicle
#)ocation
#Shipping
#Travel,ermit
#Total.ost
#next.osting
<add=>
<edit=>
<remove=>
)ogistics dmin
#4ame
#0serI+
#,asswordI+
#5eport
#nextdmin
<promote=>
<demotes=>
<terminated=>
<adddmin=>
,roduct Order
#OrderI+
#,roductI+
#4ame
#ddress
#To
#nextOrder
<add=>
<edit=>
<remove=>
Inventory
#,roductI+
#4ame
#.ategory
#,.S
#nextInventory
<add=>
<edit=>
<remove=>
,roduct
0navailable
#,roductI+
#4ame
#.ategory
#-anufactured
#,.S
<add=>
<edit=>
<remove=>
,roduct vailable
#,roductI+
#4ame
#.ategory
#-anufactured
#,.S
<add=>
<edit=>
<remove=>
5e(ect
#,roductI+
#4ame
#.ategory
<add=>
<edit=>
<remove=>
5epaired
#,roductI+
#4ame
#.ategory
<add=>
<edit=>
<remove=>
.ritical )evel
#,roductI+
#4ame
#.ategory
#-anufactured
#,.S
<add=>
<edit=>
<remove=>
0ncritical )evel
#,roductI+
#4ame
#.ategory
#-anufactured
#,.S
<add=>
<edit=>
<remove=>
"arehouse
#4ame
#ddress
#,hone4umber
#next"arehouse
<add=>
<edit=>
<remove=>
4otification
#,roductI+
#4ame
#.ategory
#-anufactured
#,.S
<add=>
<edit=>
<remove=>
5eturn *orm
#,roductI+
#4ame
#.ategory
#0navailable
#,.S
<add=>
<edit=>
<remove=>
5equest *orm
#,roductI+
#4ame
#.ategory
#0navailable
#,.S
<add=>
<edit=>
<remove=>
1.+.% So't)ar# Int#r'ac# .#cri(tion
3.1.+.%.1 E*t#rnal &ac2in# int#r'ac#
The software will be capable of printing reports on a local
or networ! printer.

3.1.+.%.% E*t#rnal 0t#& int#r'ac#
The )ogistics -anagement Systems Order ,rocessing' *inished
Inventory and "arehouse -anagement systems will communicate with a
"eb server on the internet through a high speed networ! connection such
as +S)' cable or a T3 line.
3.1.+.%.3 Hu&an int#r'ac#
The web pages shall permit complete navigation using the
!eyboard alone' In addition to using mouse and !eyboard combinations.
Logistics Page 51
3.1.+.3 R#(ort
3.1.+.3.1 In$#ntor0 o' R#(ort
The system shall be able to generate the following reports6
3. .ail0 R#(ort ? The daily report of the warehouse' orders
and deployment transactions.
9. Mont2l0 R#(ort ? The report of transactions per month.
:. Quart#rl0 R#(ort ? the transactions report for every ;
months.
;. ;#arl0 R#(ort ? the overall transactions report for a year.
Logistics Page 52
3.1.3 <#2a$ioral Mod#l .#cri(tion
3.1.3.1 .#cri(tion 'or o't)ar# !#2a$ior
3.1.3.1.1 E$#nt
dmin .lass Event
dmin -anage the System
dmin )og On to the System
dmin view the System
dmin dd Info
dmin Edit Info
dmin 0pdate Info
dmin +isplay Info
dmin ,rint Info
dmin )og Out to the System
Logistics Page 53
0ser .lass Event
0ser 5egister to the System
0ser )og On to the System
0ser 1iew Info
0ser dd Info
0ser 0pdate Info
0ser +isplay Info
0ser ,rint Info
0ser )og Out to the System
Logistics Page 54
3.1.3.1.% Stat#
dmin State
-anage The dministrator is the one who can manage the system
)ogging#in The dministrator will log in to the system.
1iew The dministrator will view information in the system.
dd The dministrator will add information to the system.
Edit The dministrator will edit information to the system.
0pdate The dministrator will update information to the system.
+isplay The dministrator will display information to the system.
,rint The dministrator will print information from the system.
)ogging#out The dministrator will log out to the system.
0ser State
5egister The 0ser will register to access the system.
)ogging#in The 0ser will log in to the system.
1iew The 0ser will view information.
dd The 0ser will add information.
0pdate The 0ser will update information.
+isplay The 0ser will display information.
,rint The 0ser will print information from the system.
)ogging#out The 0ser will log out to the system.
Logistics Page 55
3.1.3.% Stat#c2art .ia,ra&
Fi,ur# 14/ O$#rall S0t#& Stat#c2art .ia,ra&
Logistics Page 56
Overall System Statechart +iagram
/et new
*inished ,roduct
1iewing
0pdating
Inventory
Identifying
,roduct %y
.ategory
1iew 5epaired
,roduct
,rint
)ogin
1erifying
%loc!e
d
5etry
"arehouse
-anagement
-anage
Try
Incorrect
Order ,rocessing
*inished
Inventory
,rocessing
-anage
-anage
,rint
,rint
1iewing
0pdating
Out of
stoc!
4otification
of Out of
Stoc!
5eady to
delivery
1iewing
0pdating
Inventory
,rint
3.1.4 R#triction= 1i&itation= and Contraint
3. ll server code will be written in the (ava.
9. 0sername and password will only composed of @ to 3@ characters.
:. 0sername will be a combination of alphanumeric' full alphabet or has
special characters.
;. ,assword will be in numeric form.
@. ,assword will be encrypted.
A. 0sername will be visible.
3. 1.6 >alidation Crit#ria
Software validation will ensure that the system responds according to the
user expectationB therefore it is important that the end users be involved in some
phases of the test procedure coming from the system.
3.1.6.1 Cla# o' t#t
0nit testing will be conducted on all of software sub#system including
3. 1iewing and 0pdating of information
9. 1iewing and printing reports
:. )ogging on the system
Test result will be based on equivalence categories. These categories will
include values that the function of the system must process.
Logistics Page 57
3.1.6.% E*(#ct#d o't)ar# r#(on#
-* The software displays appropriate error message when a value
is not accepted by the system as entered.
0* The software should not be capable of deleting record even if
an employee is terminated or has already retired.
3.1.6.3 P#r'or&anc# <ound
3 .The system shall support numbers of users depending on the
companys needs at any given time.
9 The data storage shall be able to contain information enough to
support the records of an organi$ation consisting of wide
numbers of employees.
Logistics Page 58