Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Time: This study covers for the whole year of Academic Year
2009 – 2010.
Definition of Terms
The following terms are used mainly in the system and which
contains significant meaning. To let the readers understand what
the proponents means.
Manual Work - a work has done by hand not a machine; work done
without using computer or other devices.
Menu - The tool used in searching and finding the file
in a system.
Purchasing:
Sales:
Bottlenecks:
Supplier
Compute the purchase products
Supplier
Owner
Process Sells Transaction
Customer
The product information contains the list of products and all the
information about the products/items of the store. It include the
size, description and unit price of the item. By saving the
product information in to the system, this will help the owner of
the store view the product list, and find/trace the product
information easily.
ACTOR Owner
Workflow
OWNER
STAR
T
END
Workflow
Owner Supplier
STAR
T
END
Post condition Save the information of the purchase order.
Sales
This process starts when a costumer buy and pay the products
Workflow
costumer Owner
STAR
T
sale
Go to store to buy products
goods/products
END
ACTOR Owner
Workflow
costumer Owner
START
END
Owner
This diagram shows the flow when the owner Record the delivered
product (Purchase order) to the Automated Purchase Sales System.
Owner
Owner
Customer
3. Select an item/products
purchase by the costumer.
Owner
Automated Purchase
Search
Addnew
ChangeQTY
ChangePrice
RemoveItem CItem
Save ItemNo as Integer
Close Desc1 as String
Desc2 as String
OnhandQty as Integer
UnitPrice as Currency
Size as String
UPC as Integer
OrderCost as Currency
AddNew
Save
Close
CSales
InvoiceNo as Integer
ItemNo as Integer
Qty as Integer
ExtendedPrice as Currency
SDate as Date
SubTotal as Currency
Discount as Currency
TotalPayment as Currency
Cash as Currency
ChangeStatus as String
Search
ChangeQTY
RemoveItem
Payment
Close
Chapter 4
System Design
This chapter contains the structure and proposed outputs
plan that are being discussed and illustrated in this chapter. It
explains the programming language that are being used by the
proponents and its also described the preliminary user interfaces
that interacts between the systems structure of the system.
The Use Case diagram determined the scenarios of the
proponent system; the class diagram design determined the
attributes of the proposed system; the screen shots guided the
user in accessing and using the system; the sequence diagram
design of the proposed system determined the flow of events done
by the users.
Status :
Supplier
Owner
Process Sells Transaction
Customer