Projectsem2 Eproject

Address : 2nd floor, Innovation Building, plot 24, Quang trung Software Park, Tan Chanh Hiep Ward,
District 12, Ho Chi Minh Phone Number: (84-8) 54.371.777 DESIGN DOCUMENT Medical Store Billing Guild Teacher Class Group Groups Member: Name Trn i Nguyn Nguyn Minh Hiu Nguyn Tin Thnh Mai V Phc August 2013 ID Number Student705002 Student694844 Student694878 Student 687837 : : : PHAN MINH TM GC0865 06
Prepared by: Project group No.6 Trn i Nguyn, Nguyn Minh Hiu, Mai V Phc, Nguyn Tin Thnh Date: September 2013
Approved by: Phan Minh Tm
Review 1 .................................................................................................................. Acknowledgement ........................................................................................ I. Introduction ................................................................................................ II. Problem Definition ...................................................................................... 1.Exist Scenario .......................................................................................... 2. Propose Solution .....................................................................................
III. Customer Requirement and Specification (CRS) ..................................... IV. System Requirement Specification .............................................................. Task sheet 1 ..................................................................................................
Acknowledgement: We would like to thank Aptech Centre, which has helped us implement this subject. Thanks to the guidance from our teacher Mr. Phan Minh Tam. Thanks to the FPT-University Greenwich school, which has created the most favorable conditions of facilities for us to complete this eProject. Finally, thanks to all members who participate in this eProject.
I. Introduction RS Medical Agencies is a General Medical Store, which buys and sells the medicines as per the requirement of the customer. It has so many dealer ships from which the medicines are purchased and also some of the medicines it gets directly from the company and some of them from the wholesale retail shops. For the past few months they are facing difficulties in the current system for tracking down the details of the available and that of the sold due to the increased consumption of the medicines. So they had approached you to study the situation and resolve their difficulties in maintaining the records of the sold ones and that of the available and also to track down the details of the Payments done to the distributors, received from the customers, etc and also to track down the information of the quantity of the stock available and that of the purchasable.
II. Problem Definition Creating and Maintain details of the customer, dealers, wholesale retailers Creating and Maintain details of the stocks that are available Creating, Maintain and Management the Oder of customers Creating, Maintain and Management the Purchases, Payments
II.1. Scenario.
RS Medical Agencies is purchasing the drugs directly from the distributors of the company and as well with the dealers or from the wholesale retail shops who are the clients from whom the drugs are purchased. They did not have proper management in maintaining the records of the drugs like how much stock is available and how much is to be purchased, as well there is a lot of discrepancy in payments, discounts depending on the ratings and purchasal done. Some slipups in delivering stocks as per the requirement of the customers with in time due to the slipups in the records
II.2. Propose Solution

Developing an automated system application that holds the complete information about the drugs, dealers, and wholesale retailers in a modular form so as to make a convenient approach to track all the records and to avoid the slipups during the dispatch of the stocks to the shops or customer and Maintain the list of the order requests so as to deliver in time to the corresponding customer. a. Non-Financial : It should maintain all the details of the customer, dealers, wholesale retailers, and about the stocks in a modular form. The different concepts that are included are details of the stock available, the details of the stock ordered along with the address, and the payments that are to be received and that of the received ones, details of the dealers and the whole sale retailers Maintain separate records of the orders placed by the customers along with the payments including the dues and that of the paid. There is a separate department called the Order management that handles the order of the customer and dispatches them as per their request Maintain separate records for the dealers indicating the products that are to be purchased from them, their contact details and as well the payments indicating the due amount, balance amount Maintain separate records for the whole sale retailers indicating the products that are to be purchased from them, their contact details and as well the payments indicating the due amount, balance amount
Maintain separate records of the stock that is available and that of the consumed and as well they take care of the purchasal of the products which is to be taken care by the Marketing department which is maintained in a separate module Every time a product has been sold out, the application should alone automatically calculate and deduct the number of products that are sold from the existing and update with the exact number of products available, so as to keep track of the products and ensure to purchase them so as to deliver to the customers as per their requests in time In the Order Management module the details of the orders along with the customers, about the payments done or left, Address where it has to be delivered etc are to be maintained In the Administration Module the details of the Customer, Dealers, and that of the wholesale retailers and the distributors are maintained like the contact details, in case of customer the relation is also to be maintained, based on which he will avail the discount, and in case of the dealers, wholesale retailers and the distributors, the details of the drugs that are available with them are maintained. Prioritizing the orders based on the customers requirement and the distance. There is a reports module that consists of all the details of the customers, dealers, wholesale retailers, Distributors, etc It also contains a reminder tab where the details of the date of the delivery is stored, and as well the details of the stock are maintained here in different tabs for easy reference
There is a Purchasal module where all the details of the purchased items are mentioned, like the details of the purchases done by the customer, and as well the details of the purchasable done from the retailers, distributors, dealers are mentioned, and as well the payments of the purchases done will also be maintained in the same tab for easy reference. All the details are to be stored in a database. Also the drugs are to be provided with the codes so as to make it an easy reference
b. Financial :
The payment details of the purchases done are maintained in Purchasal module, which include the list of the purchasable and of the payments done and that of the due. So, they can keep track of the payments regularly.
III. Customers Functional Requirements Entering the Details of the customers, Dealers, Retailers and Distributors Entering all the details of the stock available For every purchase of products, the number of products purchased to be debited from that of the available list by the application itself automatically so as to increase the comfort level as the details of the stock will be regularly updated Depending on the type of the customer and his relations ship he will be availing the discount. Payment details and the details of the purchase done are maintained in purchasable module so as to keep track of the payments. Easy to retrieve the details of the stocks that are maintained along with the expiry date and that of the customers, and clients are maintained for easy reference.
IV. System Requirement Specification

a. Hardware:
A minimum computer system that will help you access all the tools in the courses is a Core i3 or better. 1Gb of RAM or better. HDD 5G free space available.
b. Software:
OS: Windows XP Services Pack 3. Java Virtual Machine 1.6.0. Net beans 6.8 or better. DBMS: SQL Server 2005 or better.
c. Development Software:
Net beans 6.8 or higher. SQL Server 2005 or higher.
d. Technology:
JDK1.6 (or higher). JRE 1.6 (or higher). JDBC.
TASK SHEET 1
eProject Title: Medical Store Billing No. 01 02 03 04 Task Review 1 Introduction Problem Definition Customers Functional Requirements System Requirements Start Day Day of Prepare of Activity Plan Compl ete Day Team Member Names rn i Nguy n
Status
31/9/ 2013
2/9/2 013
Nguyn Minh iu Nguyn in Th nh Mai V Phc
Completed
I. Architecture & Design of the Project : Since the application will have client server architecture, it will have 3-Layer architecture. 3-Layer: Architecture developed at the Logic level Layer indicates logical separation of components, such as having distinct namespace and classes for Database Access Layer, Business Logic Layer and User Interface Layer. GUI (Graphic User Interface): Data input, data presentation, checking the correct information when user input to database, before calling to the Business Logic Layer. Data Processing : To meet requirement of the GUI to manipulate the data layer and examine the business requirement before updating data, inserting data and deleting data. Data Access : connection, search, update, insert, delete the database
II.Data Flow Diagram: II.1. DFD level 0 Context Diagram:
Figure: DFD level 0 Context diagram
DFD level 0: Context diagram of system includes: Two external: Financial, non-Financial One main process: Manager Medical Store Billing System process The operation of the system: When two external entities have requirement to system, they will send commands, the system will process and return the results for two external entities
II.2.DFD level 1 Application Process: Prepared by: Project group No.6 Trn i Nguyn, Nguyn Minh Hiu, Mai V Phc, Nguyn Tin Thnh Date: September 2013 Approved by: Phan Minh Tm
DFD level 1: Data flow diagram at a top level of system includes: Two external entities: Financial, non-Financial Two processes: o Managing Clients, Stocks, Orders o Managing Purchases, Payments
II.3.DFD level 2 Managing Clients, Stocks, Orders:
When external entity Non-Financial has gotten required information to the Managing Clients, Stocks, Orders process, the Managing Clients, Stocks, Orders process will check information for that Client/Stock/Order from Customer, Dealer, Wholesale_Retailer/Stock/Order in data store and reply information to the Managing Clients, Stocks, Orders process, and then feedback information to external entity NonFinancial There are twelve processes: Add Clients (Clients= Customer/Dealer/Wholesale_Retailer/ Distributor) Update Clients Delete Clients View Clients Information Add Stocks Update Stocks Delete Stocks View Stock Information Add Orders Update Orders Delete Orders View Orderss Information
Five data stores: Customer Dealer Wholesale_Retailer Stock Order
1.1Add Clients Add Clients for non-Financial only. When external entity non-Financial has gotten required add new Clients into system, the Clients information will be sent to Add Clients process, after checking the validity, result will be replies to external nonFinancial and save the information of new Client in the right data store. 1.2Update Clients Update Clients for non_Financial only. When external entity non-Financial has gotten requiered update Clients information from system, the Clients information will be sent to Update Clients process, then this process will send request to check and change within Clients Information, result will be replies to external entity non-Financial and save change information of Updated Clients in the right data store.
1.3Delete Clients Prepared by: Project group No.6 Trn i Nguyn, Nguyn Minh Hiu, Mai V Phc, Nguyn Tin Thnh Date: September 2013 Approved by: Phan Minh Tm
Delete Clients for non-Financial only. When external entity non-Financial has gotten required Delete Clients from system, the Clients information will be sent to Delete Clients process, this process will check that information, then replies result to external entity non-Financial and remove the information of Deleted Client out of the right data store. 1.4View Clients When external entity non-Financial has gotten required view Clients. he View Clients process will retrieve data from the right database for the right Clients and display it. 1.5Add Stocks Add Stocks for non-Financial only. When external entity non-Financial has gotten required add new Stocks into system, the Stocks information will be sent to Add Stocks process, after checking the validity, result will be replies to external nonFinancial (havent draw in the figure above yet) and save the information of new Stock in Stock data store. 1.6Update Stocks Update Stocks for non_Financial only. When external entity non-Financial has gotten requiered update Stocks information from system, the Stocks information will be sent to Update Stock process, then this process will send request to check and change within Stock Information, result will be replies to external entity non-Financial and save change information of Updated Stock in Stock data store.
1.7Delete Stocks Prepared by: Project group No.6 Trn i Nguyn, Nguyn Minh Hiu, Mai V Phc, Nguyn Tin Thnh Date: September 2013 Approved by: Phan Minh Tm
Delete Stocks for non-Financial only. When external entity non-Financial has gotten required Delete Stocks from system, the Stocks information will be sent to Delete Stocks process, this process will check that information, then replies result to external entity non-Financial and remove the information of Deleted Stock out of the Stock data store. 1.8View Stocks When external entity non-Financial has gotten required view Stocks. he View Stocks process will retrieve data from the Stock database and display it. 1.9Add Orders Add Orders for non-Financial only. When external entity non-Financial has gotten required add new Orders into system, the Orders information will be sent to Add Orders process, after checking the validity, result will be replies to external nonFinancial and save the information of new Order in the Order data store. 1.10Update Orders Update Orders for non-Financial only. When external entity non-Financial has gotten requiered update Orders information from system, the Orders information will be sent to Update Orders process, then this process will send request to check and change within Orders Information, result will be replies to external entity non-Financial and save change information of Updated Orders in Order data store
1.11Delete Orders
Delete Orders for non-Financial only. When external entity non-Financial has gotten required Delete Orders from system, the Orders information will be sent to Delete Orders process, this process will check that information, then replies result to external entity non-Financial and remove the information of Deleted Oder out of the Order data store. 1.12View Oders When external entity non-Financial has gotten required view Orders. he View Orders process will retrieve data from the Order database and display it. II.4.DFD level 2 Managing Payments:
Figure: DFD level 2 Managing Purchases, Payments
There are four processes: Prepared by: Project group No.6 Trn i Nguyn, Nguyn Minh Hiu, Mai V Phc, Nguyn Tin Thnh Date: September 2013
Add Payment Update Payment Delete Payment View Payments
2.1Add Payment Add Payments for Financial only. When external entity Financial has gotten required add new Payments into system, the Payments information will be sent to Add Payments process, after checking the validity, result will be replies to external Financial and save the information of new Payment in the Payment data store. 2.2Update Payment Update Payments for Financial only. When external entity Financial has gotten requiered update Payments information from system, the Payments information will be sent to Update Payments process, then this process will send request to check and change within Payments Information, result will be replies to external entity and save change information of Updated Payment in Payment data store 2.3Delete Payment Delete Payments for Financial only. When external entity Financial has gotten required Delete Payments from system, the Payments information will be sent to Delete Payments process, this process will check that information, then replies result to external entity Financial and remove the information of Deleted Payment out of the Payment data store.
2.4View Payment Prepared by: Project group No.6 Trn i Nguyn, Nguyn Minh Hiu, Mai V Phc, Nguyn Tin Thnh Date: September 2013 Approved by: Phan Minh Tm
When external entity Financial has gotten required view Payments. he View Payments process will retrieve data from the Payment database and display it. III.Flowchart III.1.Flowchar Login
III.2.1Flowchar Add New Customer
III.2.2Flowchar Update Customer
III.2.3Flowchar Delete Customer
III.3.1Flowchar Add Dealer Prepared by: Project group No.6 Trn i Nguyn, Nguyn Minh Hiu, Mai V Phc, Nguyn Tin Thnh Date: September 2013 Approved by: Phan Minh Tm
III.3.2Flowchar Update Dealer
III.3.3Flowchar Delete Dealer Prepared by: Project group No.6 Trn i Nguyn, Nguyn Minh Hiu, Mai V Phc, Nguyn Tin Thnh Date: September 2013 Approved by: Phan Minh Tm
III.4.1Flowchar Add Wholesale_Reatailer Prepared by: Project group No.6 Trn i Nguyn, Nguyn Minh Hiu, Mai V Phc, Nguyn Tin Thnh Date: September 2013 Approved by: Phan Minh Tm
III.4.2 Flowchar Update Wholesale_Reatailer Prepared by: Project group No.6 Trn i Nguyn, Nguyn Minh Hiu, Mai V Phc, Nguyn Tin Thnh Date: September 2013 Approved by: Phan Minh Tm
III.4.3Flowchar Delete Wholesale_Reatailer Prepared by: Project group No.6 Trn i Nguyn, Nguyn Minh Hiu, Mai V Phc, Nguyn Tin Thnh Date: September 2013 Approved by: Phan Minh Tm
III.5.1Add Customer Order Prepared by: Project group No.6 Trn i Nguyn, Nguyn Minh Hiu, Mai V Phc, Nguyn Tin Thnh Date: September 2013 Approved by: Phan Minh Tm
III.5.2Update Customer Order
III.5.3 Delete Customer Order
III.6.1Add Dealer Order
III.6.2 Update Dealer Order
III.6.3 Delete Dealer Order
III.7.1Add Wholesale_Retailer Order
III.7.2 Update Wholesale_Retailer Order
III.7.3 Delete Wholesale_Retailer Order
III.8.1 Add Customer_Payment
III.8.2 Update Customer_Payment
III.8.3 Delete Customer_Payment
III.9.1 Add Dealer_Payment
III.9.2 Update Dealer_Payment
III.9.3 Delete Dealer_Payment
III.10.1 Add WholesaleRetailer_Payment
III.10.2 Update WholesaleRetailer_Payment
III.10.3 Delete WholesaleRetailer_Payment
III.11.1 Add Stock
III.11.2 Update Stock
III.11.3 Delete Stock
III.12.1 Add User
III.12.2 Update User
III.12.3 Delete User
IV.Entity relationship Diagram
V.Enity Details V.1Customer
CustomerID
CustomerName
CustomerPhone
Customer
CustomerAddress Type Relationship
V.2Dealer
DealerID DealerName DealerPhone
Dealer
DealerAddress Description
V.3Stock Prepared by: Project group No.6 Trn i Nguyn, Nguyn Minh Hiu, Mai V Phc, Nguyn Tin Thnh Date: September 2013 Approved by: Phan Minh Tm
StockID StockName
DealerID CustomerPhone
Stock
Consignment Type Price ExpiryDate
Available
V.4Wholesale_Retailer
Wholesale_RetailerID
Description
Wholesale_Retailer Address
Wholesale_Retailer
Wholesale_RetailerName Wholesale_RetailerPhone
V.5Customer_Order
CustomerID
Customer_OrderID
StockID Quantity
Customer_Order DateTakeOrder
DateDeliver
AddressDeliverTo
V.6Dealer_Order Prepared by: Project group No.6 Trn i Nguyn, Nguyn Minh Hiu, Mai V Phc, Nguyn Tin Thnh Date: September 2013 Approved by: Phan Minh Tm
DealerID
Dealer_OrderID
Dealer_Order DateTakeOrder
StockID Quantity
DateDeliver
AddressDeliverTo
V.7WholesaleRetailer_Order
Wholesale_Retailer
ID WholesaleRetailer_Order ID
StockID Quantity
WholesaleRetailer _Order
DateTakeOrder
DateDeliver
AddressDeliverTo
V.8Customer_Payment Prepared by: Project group No.6 Trn i Nguyn, Nguyn Minh Hiu, Mai V Phc, Nguyn Tin Thnh Date: September 2013 Approved by: Phan Minh Tm
Payment
Customer_Payment ID
Customer_OrderID
Customer_Payment
Due Status
V.9Dealer_Payment
Payment
Dealer_Payment ID Dealer_OrderID
Dealer_Payment
Due Status
V.10WholesaleRetailer_Payment
Payment
WholesaleRetailer_ Payment ID WholesaleRetailer_ Payment
WholesaleRetailer_Order ID
Due
Status
V.11User
Username
Password
PurchaseFrom Dealer
Fullname
Department
VI.Database Relationship Diagram Prepared by: Project group No.6 Trn i Nguyn, Nguyn Minh Hiu, Mai V Phc, Nguyn Tin Thnh Date: September 2013 Approved by: Phan Minh Tm
Table Customer
Column Number 1 2 3 4 Column Name CustomerID CustomerName CustomerAddress CustomerPhone Data Type nvarchar (10) nvarchar (100) nvarchar (100) nvarchar (15) Constraint Primary Key Not Null Not Null Not Null Not Null Description Store ID of Customer Store Name of Customer Store Address of Customer Store Phone number of Customer Store Type of Customer Store Relationship of Customer
5 6
Type Relationship
nvarchar (100) nvarchar (100)
Not Null Not Null
Table Dealer
Column Number 1 Column Name DealerID Data Type nvarchar (10) Constraint Not Null Primary Key Not Null Not Null Not Null Not Null Description Store ID of Dealer Store Name of Dealer Store Address of Dealer Stores Phone number of Dealer Store Dealer Description
2 3 4 5
DealerName DealerAddress DealerPhone [Description]
nvarchar (100) nvarchar (100) nvarchar (15) nvarchar (1000)
Table Wholesale_Retailer
Column Column Name Number 1 Wholesale_RetailerID Data Type nvarchar (10) Constrain Description t Not Null Primary Key Not Null Not Null Not Null Store ID of Wholesale_Retailer
2 3 4
Wholesale_RetailerName nvarchar (100) Wholesale_RetailerAddre nvarchar ss (100) Wholesale_RetailerPhone nvarchar (15) [Description] nvarchar (1000)
Not Null
Store Name of Wholesale_Retailer Store Address of Wholesale_Retailer Stores Wholesale_RetailerPhon e of Wholesale_Retailer Stores Description of Wholesale_Retailer
TABLE: Stock
Colum Column Name n Numbe r 1 StockID Data Type Constraint Description
nvarchar (10)
Not Null Primary Key Not Null Not Null Foreign key Not Null Foreign key Not Null Not Null Not Null Not Null Not Null
Store the ID of Stock
2 3 4
StockName DealerID Wholesale_RetailerI D [Description] Price Available Consignment ExpiryDate
nvarchar (100) nvarchar (100) nvarchar (15)
5 6 7 8 9
nvarchar (1000) float Int nvarchar (100) date
Store the name of Stock Store ID of Dealer that sell stock Store the ID of Wholesale_Retailer that have stock Stores Description of Stock Stores Price of Stock Stores number of Available Stock Stores Consignment of Stock Stores the Expiry Date Approved by: Phan Minh Tm
of Stock
TABLE: Customer_Order
Colum Column Name n Numbe r 1 Customer_OrderID Data Type Constraint Description
nvarchar (10)
Not Null Primary Key Not Null Foreign key Not Null Foreign key Not Null Not Null
Store Customer_OrderID of Customer_Order Store CustomerID of Customer_Order Store StockID of Customer_Order Stores Quantity of Customer_Order Stores the date DateTakeOrder of Customer_Order Stores Description of Customer_Order Stores AddressDeliverTo of Customer_Order Approved by: Phan Minh Tm
2 3 4 5
CustomerID StockID Quantity DateTakeOrder
nvarchar (10) nvarchar (10) int date
6 7
DateDeliver AddressDeliverTo
date Nvarchar(100)
Not Null Not Null
TABLE: Dealer_Order
Colum Column Name n Numbe r 1 Dealer_OrderID Data Type Constraint Description
nvarchar (10)
Not Null Primary Key Not Null Foreign key Not Null Foreign key Not Null Not Null
Store Dealer_OrderID of Dealer_Order
2 3 4 5
DealerID StockID Quantity DateTakeOrder
nvarchar (10) nvarchar (10) int date
DateDeliver
date
Not Null
Store DealerID of Dealer_Order Store StockID of Dealer_Order Stores Quantity of Dealer_Order Stores the date DateTakeOrder of Dealer_Order Stores Description of Dealer_Order
TABLE:
WhoSaleRetailer_Order
Column Column Name Number 1 WholesaleRetailer_ OrderID Data Type nvarchar (10) Constraint Not Null Primary Key Not Null Foreign key Not Null Foreign key Not Null Description Store Dealer_OrderID of WholesaleRetailer_Ord er Store DealerID of WholesaleRetailer_Ord er Store StockID of WholesaleRetailer_Ord er Stores Quantity of WholesaleRetailer_Ord er Stores the date DateTakeOrder of WholesaleRetailer_Ord er Stores Description of WholesaleRetailer_Ord er
Wholesale_Retailer ID StockID
nvarchar (10)
nvarchar (10)
Quantity
int
DateTakeOrder
date
Not Null
DateDeliver
date
Not Null
TABLE: Dealer_payment
Column Number
1
Column Name
Dealer_PaymentID
Data Type
Int Indentity(1,1)
Constraint
Not Null Primary Key Not Null Foreign key Not Null Not Null Not Null
Description
Store
Dealer_PaymentID of Dealer_Payment
2 3 4 5
Dealer_OrderID Payment Due [Status]
nvarchar (10) float date Nvarchar(100)
Store Dealer_OrderID of Dealer_Payment Store Payment of

Dealer_Payment
Stores the date Due of

Dealer_Payment Status of Dealer_Payment
Stores
TABLE: WhoSaleRetailer_Payment
Column Number
1
Column Name
WholesaleRetailer_ PaymentID
Data Type
Int Indentity(1,1)
Constraint
Not Null Primary Key Not Null Foreign key Not Null Not Null Not Null
Description
Store
WholesaleRetailer_PaymentID of WholesaleRetailer _Payment
WholesaleRetailer_ OrderID
nvarchar (10)
Store
WholesaleRetailer_OrderID of WholesaleRetailer _Payment Store Payment of WholesaleRetailer _Payment
3 4 5
Payment Due [Status]
float date Nvarchar(100)
Stores the date Due of

WholesaleRetailer _Payment Status of WholesaleRetailer _Payment
Stores
Column Number
1
TABLE: Customer_payment Column Name Data Type Constraint Cutomer_PaymentID Int Indentity(1,1)
Customer_OrderID
Description
3 4
Payment Due
[Status]
Not Null Store Primary Key Cutomer_Paymentof Cutomer_Payment nvarchar (10) Not Null Store Foreign key Customer_OrderID of Cutomer_Payment float Not Null Store Payment of Cutomer_Payment date Not Null Stores the date Due of Cutomer_Payment Nvarchar(100) Not Null Stores Status of Cutomer_Payment
TASKSHEET 2
eProject Title: Medical Store Billing No. Task Description Start Day Complete Day Team Member Name Trn i Nguyn Complete 3/9/2013 Nguyn Minh Hiu Mai V Phc Nguyn Tin Thnh Status
1 2 3 4 5 6 7 8
Architecture and Design of Project Data Flow Diagram Flowchart Entity Relationship Diagram Entity Details Database Relationship Database Design/Structure
Review 2
I GUI Design I.1 Database Configuration
I.2 Login
I.3Add Customer
I.4Update Customer
I.5 View Customer
I.6 Add Dealer
I.7 Update Dealer
I.7 View Dealer
I.8Add Retailer
I.9 Update Retailer
I.10 View Retailer
I.11 Add Distributor
I.12 Update Distributor
I.13 View Distributor
I.14 Add Stock
I.15Update Stock
I.16 View Stock
I.17 Add Order
I.18Update Order
I.19View Order
I.20 Add Payment
I.21Update Payment
I.22View Payment

Projectsem2 Eproject

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Projectsem2 Eproject

Uploaded by

Copyright:

Available Formats

Address : 2nd floor, Innovation Building, plot 24, Quang trung Software Park, Tan Chanh Hiep Ward,

Approved by: Phan Minh Tm

Approved by: Phan Minh Tm

Approved by: Phan Minh Tm

Approved by: Phan Minh Tm

Approved by: Phan Minh Tm

II.2. Propose Solution

Approved by: Phan Minh Tm

Approved by: Phan Minh Tm

Approved by: Phan Minh Tm

IV. System Requirement Specification

Approved by: Phan Minh Tm

Nguyn Minh iu Nguyn in Th nh Mai V Phc

Approved by: Phan Minh Tm

Approved by: Phan Minh Tm

Approved by: Phan Minh Tm

II.Data Flow Diagram: II.1. DFD level 0 Context Diagram:

Figure: DFD level 0 Context diagram

Approved by: Phan Minh Tm

II.3.DFD level 2 Managing Clients, Stocks, Orders:

Approved by: Phan Minh Tm

Approved by: Phan Minh Tm

Five data stores: Customer Dealer Wholesale_Retailer Stock Order

Approved by: Phan Minh Tm

Figure: DFD level 2 Managing Purchases, Payments

Approved by: Phan Minh Tm

Add Payment Update Payment Delete Payment View Payments

Approved by: Phan Minh Tm

III.2.1Flowchar Add New Customer

Approved by: Phan Minh Tm

III.2.2Flowchar Update Customer

III.2.3Flowchar Delete Customer

Approved by: Phan Minh Tm

III.3.2Flowchar Update Dealer

Approved by: Phan Minh Tm

III.5.2Update Customer Order

Approved by: Phan Minh Tm

Approved by: Phan Minh Tm

III.5.3 Delete Customer Order

Approved by: Phan Minh Tm

III.6.1Add Dealer Order

III.6.2 Update Dealer Order

Approved by: Phan Minh Tm

III.6.3 Delete Dealer Order

Approved by: Phan Minh Tm

Approved by: Phan Minh Tm

III.7.1Add Wholesale_Retailer Order

III.7.2 Update Wholesale_Retailer Order

Approved by: Phan Minh Tm

III.7.3 Delete Wholesale_Retailer Order

Approved by: Phan Minh Tm

III.8.1 Add Customer_Payment

Approved by: Phan Minh Tm

III.8.2 Update Customer_Payment

Approved by: Phan Minh Tm

III.8.3 Delete Customer_Payment

Approved by: Phan Minh Tm

III.9.1 Add Dealer_Payment

Approved by: Phan Minh Tm

III.9.2 Update Dealer_Payment

Approved by: Phan Minh Tm

III.9.3 Delete Dealer_Payment

Approved by: Phan Minh Tm