expert enterprise

8/14/2019 Expert Enterprise

1/128

Expert Enterprise

Session: BSc. Spring 2001

Team ID: BSc/S01/DI/Tid-33

Project Advisor: Jamal Abdul Nasir

Submitted By

Haroon Rafique Khan BCSS01M036

Ubaid Hayee BCSS01M047

Ahmed Usman Awan BCSS01M081

Hafiz M Naveed Sattar BCSS01M082

Punjab University College of Information Technology

University of the Punjab, Lahore.


2/128

Proof Reading Certificate

It is to certify that I have read the document meticulously and circumspectly. I amconvinced that the resultant artifact does not contain any spelling, or grammaticalmistake. All in all I find the document well organized and I am in no doubt that its

objective has been successfully met.


3/128

Statement of Submission

This is certify that Haroon Rafiq Khan Roll No. BCSS01M036, Ubaid Hayee Roll No.BCSS01M047, Ahmed Usman Awan Roll No. BCSS01M081 and Hafiz M NaveedSattar have successfully completed the final project named as: Expert Enterprise, at the

Punjab University College of Information Technology, University of The Punjab, Lahore,to fulfill the partial requirement of the degree ofBachelors in Computer Science.

______________________ ___________________External Supervisor Project Coordination Office

Jamal Abdul Nasir PUCIT, LahoreAssistant ProfessorPUCIT, Lahore

_____________________________ ________________________External Examiner Dr. M. Anwar Ur Rehman Pasha

Munawar Hussain PrincipalLecturer PUCIT, Lahore.PUCIT, Lahore


4/128

Acknowledgement

We truly acknowledge the cooperation and help make by Name ofJamal Abdul Nasir,Assistant Professor of PUCIT, Lahore. He has been a constant source of guidancethroughout the course of this project. We would also like to thank Rizwan YousaffromLecturer ofPUCIT, Lahore for his help and guidance throughout this project. We arealso thankful to our friends and families whose silent support led us to complete ourproject.

Date

August 15, 2005


5/128


6/128

Table of Contents

Chapter 01 Product Estimations and Scheduling 1

Introduction 2

1.1 Project Feasibility Report 21.1.1 Technical Feasibility 21.1.2 Operational Feasibility 21.1.3 Economic Feasibility 21.1.4 Schedule Feasibility 21.1.5 Specification Feasibility 21.1.6 Information Feasibility 31.1.7 Motivational Feasibility 31.1.8 Legal & Ethical Feasibility 3

1.2 Project Scope1.2.1 Purchase 3

1.2.2 Accounts 31.2.3 Sales 3

1.3 Tools and Technologies 41.3.1 Hardware/Software Specification 41.3.2 Platform 4

1.4 Scale/Cost Drivers 51.5 Task Dependency and Member Allocation Table 7

1.5.1 Table 1.5 Task Dependency 71.6 Gant Chart 81.7 Network Diagram

Chapter 02 Requirement Engineering 10

2.1 About Organization 112.1.1 Existing System 112.1.2 Organization Flow 12

2.2 Summary of Requirements 132.2.1 Sales Department Requirements 132.2.2 Purchase 13

2.2.2.1 Purchase 132.2.2.2 Purchase Accounts 13

2.3 Identifying External Entities 142.3.1 Over Specified Entities 14

2.3.2 Refined entities 142.4 Context Level Diagram 152.5 Capture Shall Statements 162.6 Allocate Requirements 162.7 Priorities Requirements 172.8 Requirements Traceability Matrix 182.9 High Level Use Case Description 19

2.9.1 UC1 Sales Target 19


7/128

2.9.2 UC2 Generate Sales Target Report 202.9.3 UC3 Vendor Selection 212.9.4 UC4 Purchase Order Note 222.9.5 UC5 Purchase Report s 232.9.6 UC6 Purchase Account 24

Chapter 03 Object Oriented Analysis and Design 25

3.1 Use Case Modeling 263.1.1 Sales Module 26

3.1.1.1 UC1 Maintain Customer 263.1.1.2 UC2 Sales Order 263.1.1.3 UC3 Sales Invoicing 273.1.1.4 UC4 Generate Receipt 283.1.1.5 UC5 Handle Sales Return 283.1.1.6 UC6 Generate Sales Journal Report 29

3.1.1.7 UC7 Generate Cash Receipts Report 303.1.1.8 UC8 Journal Ledger 303.1.2 Purchase Module 31

3.1.2.1 UC1 Maintain Vendor 313.1.2.2 UC2 Maintain Inventory Items 313.1.2.3 UC3 Purchase Order 323.1.2.4 UC4 Purchases/ Received Inventory 333.1.2.5 UC5 Purchase Payment 333.1.2.6 UC6 Handle Purchase Return 343.1.2.7 UC7 Generate Purchase Journal 353.1.2.8 UC8 Generate Cash Disbursements 35

3.1.2.9 UC9 Journal Ledger 363.2 System Use Case Diagrams 373.2.1 Purchase Module 373.2.2 Sales Module 38

3.3 System Sequence Diagrams 393.3.1 Sales Module 39

3.3.1.1 Cash Receipts Journal Report 393.3.1.2 Generate Receipt 403.3.1.3 Generate Sales Journal Report 413.3.1.4 Handle Sales Return 423.3.1.5 Journal Ledger 43

3.3.1.6 Maintain Customer 443.3.1.7 Sales Invoicing 453.3.1.8 Sales Order 46

3.3.2 Purchase Module 473.3.2.1 Cash Disbursements Journal Report 473.3.2.2 Generate Purchase Journal Report 483.3.2.3 Journal Ledger 493.3.2.4 Maintain Inventory Items 50


8/128

3.3.2.5 Maintain Vendor 513.3.2.6 Purchase Order 523.3.2.7 Purchase Payment 533.3.2.8 Purchase Return 543.3.2.9 Purchase/Received inventory 55

3.4 Identifying Conceptual Classes 563.4.1 Sales Module 563.4.1.1 Cash Receipts Journal Report 563.4.1.2 Generate Receipt 563.4.1.3 Maintain Customer 563.4.1.4 Sales Invoicing 563.4.1.5 Sales Order 573.4.1.6 Sales Return 57

3.4.2 Purchase Module 573.4.2.1 Cash Disbursements Journal Report 573.4.2.2 Maintain Inventory Items 57

3.4.2.3 Maintain Vendor 583.4.2.4 Purchase Order 583.4.2.5 Purchase Payment 583.4.2.6 Purchase Received 583.4.2.7 Purchase Return 58

3.5 Class Diagram 593.5.1 Sales Module 59

3.5.1.1 Cash Receipts Journal Report 593.5.1.2 Generate Receipt 603.5.1.3 Maintain Customer 613.5.1.4 Sales Invoicing 623.5.1.5 Sales Order 633.5.1.6 Sales Return 64

3.5.2 Purchase Module 653.5.2.1 Cash Disbursements Journal Report 653.5.2.2 Maintain Inventory Items 663.5.2.3 Maintain Vendor 663.5.2.4 Purchase Order 673.5.2.5 Purchase Payment 683.5.2.6 Purchase Received 693.5.2.7 Purchase Return 70

3.6 Sequence Diagram 713.6.1 Sales Module 71

3.6.1.1 Sales Order 713.6.1.2 Sales Invoicing 723.6.1.3 Maintain Customer 733.6.1.4 Handle Sales Return 753.6.1.5 Generate Receipt 77

3.6.2 Purchase Module 783.5.2.1 Maintain Inventory Items 78


9/128

3.5.2.2 Maintain Vendor 793.5.2.3 Purchase Order 803.5.2.5 Purchase Payment 813.5.2.6 Purchase Return 823.5.2.6 Purchase Receive/Inventory 83

3.7 Design Model (Packages) 843.7.1 Item 843.7.2 Vendors 853.7.3 Purchase Order 863.7.4 Customer 873.7.5 Sales Order 88

Chapter 04 User Interface Design 89

4.1 Screen 904.1.1 Login Screen 904.1.2 Purchase Main Screen 91

4.1.3 Purchase Receive 924.1.4 New Purchase 934.1.5 Sales Main Screen 954.1.6 New Sales 94.1.7 Sales Ship 974.1.8 Sales Ship Detail 984.1.9 Vendor Maintain Screen 994.1.10 New Vendor 104.1.11 Customer Main Screen 1024.1.12 New Customer 1034.1.13 Ship to Information 105

4.1.14 Ship for Information 1064.1.15 Inventor 1074.1.16 Inventory Adjustment 1084.1.17 Product Main Screen 1094.1.18 New Product Detail 1104.1.19 Log Out 111

4.2 Traceability Matrix 112References 114


10/128

Tables

Table 1.1 Deployment and Maintenance 5Table 1.2 Results 5Table 1.3 Effort 6Table 1.4 Activity Distribution 6

Table 2.1 Capturing Shall Statement 16Table 2.2 Allocate Requirement 16Table 2.3 Priorities Requirement 17Table 2.4 Requirement Traceability Matrix 18Table 4.1 GUI to DB Mapping for Screen 4.1.1 90Table 4.2 GUI to DB Mapping for Screen 4.1.2 91Table 4.3 GUI to DB Mapping for Screen 4.1.3 92Table 4.4 GUI to DB Mapping for Screen 4.1.4 94Table 4.5 GUI to DB Mapping for Screen 4.1.5 95Table 4.6 GUI to DB Mapping for Screen 4.1.6 96Table 4.7 GUI to DB Mapping for Screen 4.1.8 98

Table 4.8 GUI to DB Mapping for Screen 4.1.10 101Table 4.9 GUI to DB Mapping for Screen 4.1.12 104Table 4.10 GUI to DB Mapping for Screen 4.1.13 104Table 4.11 GUI to DB Mapping for Screen 4.1.14 105Table 4.12 GUI to DB Mapping for Screen 4.1.16 108Table 4.13 GUI to DB Mapping for Screen 4.1.18 108Table 4.14 Traceability Matrix 113

Figures

Figure 1.1 Gant Chart 8Figure 1.2 Network Diagram 9Figure 2.1 Organization Flow 12

Figure 2.2 Context Level Diagram 15Figure 3.1 Purchase Module 37Figure 3.2 Sales Module 38Figure 3.3 Cash Receipts Journal Report SD 39Figure 3.4 Generate Receipt 40Figure 3.5 Generate Sales General Report 41Figure 3.6 Handle Sales Return 42Figure 3.7 Journal Ledger 43Figure 3.8 Maintain Customer 44Figure 3.9 Sales Invoicing 45Figure 3.10 Sales Order 46

Figure 3.11 Cash Disbursements Journal Report 47Figure 3.12 Generate Purchase Journal Report 48Figure 3.13 Journal Ledger 49Figure 3.14 Maintain Inventory Items 50Figure 3.15 Maintain Vendor 51Figure 3.16 Purchase Order 52Figure 3.17 Purchase Payment 53Figure 3.18 Purchase Return 54


11/128

Figure 3.19 Purchase/Received inventory 55Figure 3.20 Cash Receipts Journal Report 59Figure 3.21 Generate Receipt 60Figure 3.22 Maintain Customer 61Figure 3.23 Sales Invoicing 62

Figure 3.24 Sales Order 63Figure 3.25 Sales Return 64Figure 3.26 Cash Disbursements Journal Report 65Figure 3.27 Maintain Inventory Items 66Figure 3.28 Maintain Vendor 66Figure 3.29 Purchase Order 67Figure 3.30 Purchase Payment 68Figure 3.31 Purchase Received 69Figure 3.32 Purchase Return 70Figure 3.33 Sales Order 71Figure 3.33 Sales Invoicing 72

Figure 3.34 Maintain Customer 74Figure 3.35 Handle Sales Return 76Figure 3.36 Generate Receipt 77Figure 3.37 Maintain Inventory Items 78Figure 3.38 Maintain Vendor 79Figure 3.39 Purchase Order 80Figure 3.40 Purchase Payment 81Figure 3.41 Purchase Return 82Figure 3.42 Purchase/Received inventory 83Figure 3.43 Item 84Figure 3.44 Vendors 85Figure 3.45 Purchase Order 86Figure 3.46 Customer 87Figure 3.47 Sales Order 88Figure 4.1 Login Screen 90Figure 4.2 Purchase Main Screen 91Figure 4.3 Purchase Receive 92Figure 4.4 New Receive 93Figure 4.5 Sales Main Screen 95Figure 4.6 New Sales 96Figure 4.7 Sales Ship 97Figure 4.8 Sales Ship Detail 98Figure 4.9 Vendor Main Screen 99Figure 4.10 New Vendor 100Figure 4.11 Customer Main Screen 102Figure 4.12 New Customer 103Figure 4.13 Ship to Information 105Figure 4.14 Ship for Information 106Figure 4.15 Inventory 107Figure 4.16 Inventory Adjustment 108


12/128

Figure 4.17 Product Main Screen 109Figure 4.18 New Product Detail 110Figure 4.19 Log out 111


13/128

Expert Enterprise

CHAPTRE 01

Product Estimations and Scheduling


14/128


15/128

Expert Enterprise

1.1.5 Specification feasibilityIn our ERP solution we are going to cover

Purchase

Accounts (Payable, Receivable) Sales

Accounts related to purchase will be covered in our system.Sales is like the complete component as purchase we are just covering the componentup to that extend that we can show the interfacing of to ERP component and we canshow that these components can work independently.

1.1.6 Information FeasibilityFor this project we will analyze group of Industries for gathering information, aswe have to develop a generic solution.

1.1.7 Motivational FeasibilityOur project will be user friendly; using BI our project will be help full for

management in managing business policies and help them in setting business goals.

1.1.8 Legal and Ethical Feasibility

This project is business oriented and it is legally and ethicallyfeasible everywhere.

1.2 Scope

The Project scope will include following.

1.2.1-Purchase

Our System will handle Purchase handling. On the basis of current and previousrecord component will completely schedule the whole plan for purchase.

This component will handleo Purchase recordo Item setupo Vendor setupo Request reporto Requisition reporto Order note


16/128

Expert Enterprise

Run time reports will also be generated. Using BI our system will show alerts on business constraints.1.2.2-Accounts

Accounts payable Accounts Receivable

Return Accounts handling1.2.3-Sales Our sales system will set Products targets. Our sales system will completely schedule the sales forecasting.

1.3 Tools and technology with reasoning

1.3.1 HARDWARE / SOFTWARE SPECIFICATIONS:

Hardware specifications include mainly the personal computers with Intel P2 or higher.

128MB Ram.Windows 95, 98 NT and XP will be suitable platforms.

o . Net platform/JAVAo Visio/Rational Rose/Erwino ASP. Net/JSPo VB.Neto SQL Servero Bi-toolso Analytical Server

1.3.2 PLATFORM:

IBM or its clone will be the host platform for the entire development (normally code

related).


17/128


18/128


19/128

Expert Enterprise

1.5 Task Dependency and Member Allocation Table

Table 1.5 Task De endenc and Member Allocation Table


20/128

Expert Enterprise

1.6 GANT CHART


21/128

Expert Enterprise

Figure 1.1 GANT CHART

1.7 Network diagram

Figure 1.2 GANT CHART


22/128

Expert Enterprise

CHAPTRE 02

Re uirement En ineerin


23/128


24/128

Expert Enterprise

2.1 About Organization:

The System we are going to produce is not for a specific company, as it is ageneric solution it should be for all companies but due to limitations we are restricting itup to some companies.

2.1.1 Existing System:

In current Industry some companies do there work manually, and some are usingcomputer based solutions.Solution exists for the companies are specially designed for specific companies. Eachcompanies has its own requirements and there solutions. According to the exiting systemit is considered that every company weather it is related to pharmaceuticals, Automobiles,or Leather every one has its own different Purchase system .So their solutions are entirelytreated as separately. They as analyzed designed and implemented individually.In normal sales of any company, customer places order and on the basis of order, saletargets are set. In order to achieve these targets purchase department purchases stock if it

is not in stores.Purchases are done by fixed vendors or some companies select vendors after marketanalysis. Vendor selection based on different parameters, some companies prefer low costwhile others prefer quality.Purchase Department has there own account management for local stock like stationary,furniture and office goods. Normally purchase department has an accountant with a fixedamount of cash .Accountant purchases local stock on self payments and then withdrawsthere cash from Accounts department.


25/128

Expert Enterprise

2.1.2 Organization Flow:

Sales department of organization set there Targets on the basis of Order they receive.These Targets are passed to Production cell and Production department verifies stock inInventory department If not a sufficient stock then Inventory passes the Purchase request

note to Purchase Department. Purchase department Purchases necessary stock and in thisway the whole cycle of purchase and sales flows.

Figure 2.1 Organization Flow

The departments we are concerned in this Expert Enterprise are mainly

Sales Purchase

Sales Dept.Customer

Production Dept.

Inventory Dept.

Purchase Dept.


26/128

Expert Enterprise

2.2 Summary of requirements.

2.2.1 Sale Department requirements.

P-1 Only registered clerk can enter the sales order. So clerk should first register

one self. Clerk will enter the order for sale and set the sales Target. Sales targetwill include the Item no, customer specification, order no, Order delivery date.Targets are set on the basis of these orders.P-2 Clerk, Manager and any authentic person can view the Sales Target list.Sales Target Report will be generated so that Stock According to the Target canbe Checked or purchased. Again only authorized users can generate the salestarget Report. User can generate report according to there requirements ascustomer vise, date vise, country vies.

2.2.2 Purchase2.2.2.1 Purchase

P-3 Only purchase clerk can do vendor selection. Clerk is first authenticated.

Clerk then enter the purchase request note. These request notes are according tosales target and they help in purchase to achieve target. System will prompt for thecurrent quotations for these purchases. System will record quotations for the preexisting vendors and update record for new vendors. Then System generate thebest vendor .Vendor selection may be on different parameters as on low cost or onquality. Sales Manager may accept or reject the selected vendor. After finalvendor selection System will generate the Order Note or the selected vendor.P-4 Only authenticated clerk can update the received purchase goods. So clerkfirst authenticated. Clerk will then enter the received goods that are approved bythe purchase manager. And update the record. System may set purchase alerts onthe basis on company policies and any well defined sequence that will be helpful

In purchase forecasting. If there is an existing alert message for purchaseforecasting system will show it.

P-5 Only authenticated user can generate the Purchase Report. Report may begenerated by vendor vise, product vise, order vise or Date vise.2.2.2.2 Purchase Account

P-6 Only Purchase Accountant can handle the purchase account. Clerk is firstauthenticated and then enters the new account. Account is updated andAccountant will generate the voucher. If system failed any time during transactionupdate system will recover it, delete anomalies and bring data base to consistentstate.

We are going to combine the common attributes and requirements of different companiesbecause up to some extend purchase system is similar. Common purchase attributes willbe implemented centrally while special requirements for the companies will beimplemented as extended components of purchase.


27/128

Expert Enterprise

2.3 Identifying External Entities:

2.3.1 Over Specified Entities:

1. Sales Clerk2. Sales Manager

3. Sales Target4. Order5. Purchase Clerk6. Purchase Manager7. Purchase Request8. Vendor9. Sales report10.Purchase report11.Purchase Accountant12.Order note

2.3.2 Refined Entities:1. Sales Clerk2. Sales Manager3. Purchase Clerk4. Purchase Manager5. Vendor


28/128

Expert Enterprise

2.4 Context Level Diagram

Figure 2.2 Context Level Diagram

Expert

Enterprise

Sales Order

Sales Target

Sales Clerk

Purchase Clerk

Select Vendor

Vendors List

Account Dept.

Purchase voucher

Vendor

Order note

Material

Order Note

Receipt


29/128

Expert Enterprise

2.5 Capturing Shall Statements:

Par# Initial requirements

P-1 Sales Clerk Shall set Sales Target

P-2 User Shall generate the sales report

P-3 Purchase Clerk Shall select the vendor

P-4 Purchase Clerk Shall generate the purchase order note

P-5 User Shall generate the Purchase report

P-6 Purchase Accountant Shall update the local purchase account.

Table 2.1 Capturing Shall Statement

2.6 Allocate Requirements:

Par# Initial requirements Use Case Name

P-1 Sales Clerk Shall set Sales Target Sales Target

P-2 User Shall generate the sales report Generate Sales Target Report

P-3 Purchase Clerk Shall select the vendor Vendor Selection

P-4 Purchase Clerk Shall generate thepurchase order note

Purchase Record Update

P-5

User Shall generate the Purchase report Purchase Report

P-6 Purchase Accountant Shall update thelocal purchase account.

Purchase Account

Table 2.2 Allocate Requirement


30/128

Expert Enterprise

2.7 Priorities Requirements:

Table 2.3 Priorities Requirement

Par# Rank Initial requirements UC Id Use Case

NameP-1 Highest Sales Clerk Shall set Sales

TargetUC1 Sales Target

P-3 Highest Purchase Clerk Shall select thevendor

UC3 VendorSelection

P-4 Middle Purchase Clerk Shall generatethe purchase order note

UC4 PurchaseRecord Update

P-6 Middle Purchase Accountant Shallupdate the local purchaseaccount.

UC6 PurchaseAccount

P-2 Lowest User Shall generate the sales

report

UC2 Generate Sales

Target ReportP-5 Lowest User Shall generate the

Purchase reportUC5 Purchase

Report


31/128

Expert Enterprise

2.8 Requirement Traceability Matrix:

Table 2.4 Requirement Traceability Matrix

Sr# Par# Rank Initial requirements Build Use Case

Category1 P-1 Highest Sales Clerk Shall set Sales

TargetB1 Business

2 P-3 Highest Purchase Clerk Shall selectthe vendor

B1 Business

3 P-4 Middle Purchase Clerk Shallgenerate the purchase OrderNote

B1 Business

4 P-6 Middle Purchase Accountant Shallupdate the local purchaseaccount.

B1 Business

5 P-2 Lowest User Shall generate thesales report

B1 Business

6 P-5 Lowest User Shall generate thePurchase report

B1 Business


32/128

Expert Enterprise

2.9 High Level Use Case Description

2.9.1 Use Case UC1 Sales Target:

Primary Actor: Sales Clerk

Stakeholders and Interests:

Sales Manager:

Sales Manager wants to view sales target.

Pre Conditions:

Clerk is authenticated and validated by checking correct Id and password.

Post Conditions:

Sales Targets are set, Targets may be deleted or updated by the sales manager withminimal effort and fast service.

Main Flows:

1 Clerk enters the Set Sales Target screen.2 System shows appropriate screen for the desired action.3 Clerk adds the new Orders for Sale.4 Clerk updates the existing Sale Targets.5 Clerk presses OK button.

6 System will prepare sales Request Note.7 Clerk exits the Set Sales Target screen.

Alternate Flows:

4- If Targets are not updated system will generate the message


33/128

Expert Enterprise

2.9.2 Use Case UC2 Generate Sales Target Report:

Primary Actor: Marketing Manager, Director Sales, Accountant, Auditors,Chief Executive

Stakeholders and Interests:Marketing Manager:

Marketing manager generates the reports of sales in order to be aware of the totalsales made up to certain time. He generates sales analysis report customer vice andsales analysis report product vice. He also generates report country vice.

Chief Executive:

Chief Executives all decisions are based on the reports of the company performance.These reports allow him to think about the product to be focused in the future.

Pre Conditions:

User is authenticated and validated by checking correct user name and password.

Only authenticated users can enter the system. User wants to generate report of sales.

Post Conditions:

Sales Target Reports are generated with minimal effort and fast service.

Main Flows:

1. User enters the Generate Reports of Sales screen.2. System shows appropriate screen for the desired action.3. User generates the Detailed Report of Sale Target.4. User presses Ok button.5. User exits the Generate Reports of Sales Target screen.

Alternate Flows:

3.1 User generates the Report of Sale Customer vice3.2 User generates the Report of Sale Product vice.3.3 User generates the Report of Sale Country vice.


34/128

Expert Enterprise

2.9.3 Use Case UC3: Vendor Selection

Primary Actor: Purchase Clerk.

Stakeholders and Interests:Purchase Manager:

Manager will approve the Final vendor.Pre Conditions:

Clerk is authenticated and validated by checking correct user name and password.Purchase Department receives the request note for purchase.

Post Conditions:

Order note of purchase will be generated for the selected vendor.

Main Flows:

1. Clerk enters the Vendor Selection screen.2. System shows appropriate screen for the desired action.3. Clerk enters the Request note for purchase.4. System will prompt for the quotations.5. Clerk will enter the quotations for the purchases.6. System will update the record7. System Select the best vendors.8. System will generate the Order note for the selected vendor.9. Clerk presses Ok button.10.Clerk will exit the Vendor Selection screen.

Alternate Flows:

5.1 For new vendor clerk will enter vendor info.7.1 Manager may change the selected vendor and update the record.7.1 Manager may call for sample.

7.1.1 Manager may accept the vendor after quality assurance.7.1.2 Manager may reject the vendor then step 7 will repeat.


35/128

Expert Enterprise

2.9.4 Use Case UC4: Purchase Order Note

Primary Actor: Purchase Clerk.

Stakeholders and Interests:Procurement Manager:

Procurement manager is responsible for the purchases of the company. By managingthe purchases of the company new decisions could be taken for better results.

Chief Executive:

Chief Executives may want to know the status of the companys purchases during afixed period of time. It will be useful for him in making decisions.

Pre Conditions:

Clerk is authenticated and validated by checking correct user name and password.Clerk received the purchased goods.Post Conditions:

Purchase is completed.Main Flows:

1. Clerk enters the Purchase update screen.2. System shows appropriate screen for the desired action.3. Clerk enters the goods that are approved by manager and press update button.4. System will update the purchase.5. System will set Alerts for a sequence of purchase that will use in purchase

forecasting.6. Clerk presses Ok button.7. Clerk will exit the Vendor Selection screen.

Alternate Flows:

3.1 If Purchased goods are not approved by manager system will do nothing andgive a message not approved goods.5.1 If there is an Alert message system will show that message.


36/128

Expert Enterprise

2.9.5 Use Case UC5: Purchase Reports

Primary Actor: PurchaseManager, Chief Executive

Stakeholders and Interests:Procurement Manager:

Procurement manager is responsible for the purchases of the company. By managingthe purchases of the company new decisions could be taken for better results.

Chief Executive:

Chief Executives may want to know the status of the companys purchases during afixed period of time. It will be useful for him in making decisions.

Pre Conditions:

User is authenticated and validated by checking correct user name and password.Only authenticated users can enter the system. User wants to generate report ofpurchases.

Post Conditions:

Reports of Purchases are generated with minimal effort and fast service.

Main Flows:

1 User enters the Generate Reports of Purchases screen.2 System shows appropriate screen for the desired action and show if there is

any alert message.3 User generates the Report of Purchase Vendor vice.4 User generates the Report of Purchase Product vice.5 User generates the Report of Purchase Order vice.6 User generates the Report of Purchase Date vice.7 User presses Ok button.8 User exits the Generate Reports of Purchases screen.

Alternate Flows:

If user enters the invalid password, message try again is shown to the user.

If user is not registered, message get registration is shown to user.

1. If at any time Generate Reports of Purchases system fails then user will not beable to generate account reports but all other works will continue uninterruptible.


37/128

Expert Enterprise

2.9.6 Use Case UC6: Purchase Account

Primary Actor: Accountant, Auditor

Stakeholders and Interests:Accountant:

Accountant manages accounts according to the transactions. These are necessary formaintaining proper record of transactions.

Pre Conditions:

Accountant is authenticated and validated by checking correct user name and password. Only authenticated users can enter the system. User wants to manageaccounts. When only local purchases are done.

Post Conditions:

Purchase accountant balance is updated.

1 Accountant enters the Manage Accounts screen.2 System shows appropriate screen for the desired action.3 Accountant adds the new Account.4 Accountant updates the existing Account.5 Accountant Generate the voucher.6 Accountant presses Ok button.7 Accountant exits the Manage Account screen.

Alternate Flows:

If user enters the invalid password, message try again is shown to the user.

If user is not registered, message get registration is shown to user.

1. If at any time Manage Accounts system fails

a) Backup of the system is available.

b) Recovery of the transactions is possible.

Accountant restarts the system, logs in and requests for recovery of prior state.2. If system reconstructs prior state.

2.1 System detects anomalies preventing recovery.2.2 System enters error signal to Accountant.2.3 Accountant restarts a new transaction.


38/128

Expert Enterprise

CHAPTRE 03

Object Oriented Analysis and Design


39/128

Expert Enterprise


40/128

Expert Enterprise

3.1 Use Case Modeling

3.1.1 Sales Module

3.1.1.1 Use case UC-1 Maintain Customers:

Primary Actor:

Sales ManagerStakeholders and Interests:

Sales Manager: Sales Manager wants to maintain Customers.

Preconditions: Sales Manager is authenticated

Post condition: Customers record is updated.

Main Flow: 1- Sales Manager request for new Customers.2- System Will Show Customer Screen.3- Sales Manager enters Customers Info, Customers Type, Customer Ship

To Location, Customer Ship For Location, Customer Contacts, anddetails of the Customers.

4- Sales Manager will save the record by clicking on the savebutton.

Alternative Flow:

1- Sales Manager wants to update previous Customers1) Sales Manager will enter the Customers ID. System presentsCustomers Information2) Sales Manager will make the required changes.3) Sales Manager will save the changes by clicking on the savebutton.

3.1.1.2 Use case UC-2 Sales Order:

Primary Actor: Sales ClerkStakeholders and Interests:

Sales Manager: Sales Manager wants to post Sales orders.

Preconditions: 1- Sales Clerk is authenticated.

Post condition: Sales order is posted For Packing.

Main Flow: 1- Sales Clerk starts a new Sales Order


41/128

Expert Enterprise

3- Sales Clerk enters Order Header and Order Detail..4- Sales Clerk enters Customer ID and Item Id.5- System presents the description and unit price of Item and its Available

Quantity.6- Sales Clerk enters Quantity..

Sales Clerk repeats step no 4 until all the Items required andtheir quantities are entered.7- System Approve Order and presents total with accepted discount.8-System saves Sales order or print it when Sales Clerk clicks save orprint button.9- Update Inventory.

Alternative Flow:

3- Invalid Customer ID is entered.1. System signals error and rejects entry2. Maintain New Customer.

7- Not Sufficient Quantity1. System signals and Sales order is rejected.

3.1.1.3 Use case UC-3 Sales Invoicing:

Primary Actor:

Sales Clerk.Stakeholders and Interests:

Sales Manager: Sales Clerk wants to generate sale invoices.

Preconditions: Sales Clerk is authenticated.Sale Order is Packed..

Post condition: 1- Sales invoice is generated.2- Inventory is updated

Main Flow:

1- Sales Clerk Request for new Invoice.2- System will show Invoice screen.3- Sales Clerk enters Sale Order no.4- System presents the Order Specification.5- Sales Clerk enters Invoice no.6- System Saves invoice or prints invoice when Sales Clerk clicks save

Button or print button.7- Order is posted for shipping.

Alternative Flow:

3- Invalid Order no is entered.1. System signals error and rejects entry


42/128

Expert Enterprise

3.1.1.4Use Case UC-4 Generate Receipt

Primary Actor:

Sales Clerk


Sale Manager: Sales Manager wants to keep record of payment received.Customer: Customer pays his liability.

Precondition:

Customer pays via check or cash.

Post condition: Transaction is saved. Accounting is updated. Customersrecord is updated. Provisional Receipt is generated.

Main Flow:

1 - Sales Clerk starts a new Receipt.2- Sales Clerk enters Receipt no.3- Sales Clerk enters the Invoice no.4- System presents the Customer name ,remit to address and terms and

conditions agreed to Customer.5- Sales Clerk enters the mode of payment.6- Sales Clerk enters amount of payment.7- System generates provisional receipt .

Alterative Flow:

3. Invalid Customer is entered.1. System signals error and rejects entry

6- Payment by check method is selected.1. Sales Clerk enters the check no check date and bank account no.

3.1.1.5 Use Case UC-5 Handle Sales Return:

Primary Actor:

Sales Clerk.

Stakeholders and interests:

Sale Manager: Sales Manager wants to keep record of Sale returns.Customer: Customer returns Items which are demanded. He wants to


43/128

Expert Enterprise

Precondition:

Customer returns Items.

Post condition:

Sale return is saved. Accounting and inventory are updated.

Main Flow:

1- Sale Clerk. starts Sales return.2- Sale Clerk enters Invoice Number.3- Sale Clerk enters the Item name, quantity and status of returned Items.

Sales Clerk. repeats step no 4 until indicates done.5- Inventory and accounts are updated.

Alternative Flow:

6- System will generate error if invoice number is not correct.

3.1.1.6 Use Case UC-6 Generate Sales Journal Report

Primary Actor:

Sales Manager.


Sales Manager: Sales Manager wants to view the report.

Precondition:

Sales Manager is authenticated.

Post condition:

Report has been shown.Main Flow:

1- Sales Manager starts the Sales journal report2- Sales Manager will enter the range of date for Report, Report order.3- Sales Manager will select the fields he want to view.4- System will show the required report.5- Sales Manager can save the report, print the report or can view inMicrosoft Excel.


44/128

Expert Enterprise

3.1.1.7 Use Case UC-7 Generate Cash Receipts Journal Report

Primary Actor:

Sales Manager.



Precondition:


Post condition:


1- Sales Manager starts the Cash Receipts Journal report

2- Sales Manager will enter the range of date for Report, Report order.3- Sales Manager will select the fields he want to view.4- System will show the required report.5- Sales Manager can save the report, print the report or can view inMicrosoft Excel.

3.1.1.8 Use Case UC-8 Journal Ledger

Primary Actor:

Sales Manager.



Precondition:


Post condition:


1- Sales Manager starts the Journal Ledger report2- Sales Manager will enter the range of date for Report, Report order.3- Sales Manager will select the fields he want to view.4- System will show the required report.5- Sales Manager can save the report, print the report or can view inMicrosoft Excel.


45/128

Expert Enterprise

3.1.2 Purchase Module

3.1.2.1 Use case UC-1 Maintain Vendor:

Primary Actor: Purchase ManagerStakeholders and Interests:

Purchase Manager: Purchase Manager wants to maintain vendors.

Preconditions: Purchase Manager is authenticatedPost condition: Vendor record is updated.

Main Flow: 1- Purchase Manager request for new Vendor.2- System will show Vendor Info Form.

3-Purchase Manager enters Vendor Info, Vendors Contact ,VendorComments, Terms.4-Purchase Manager will save the record by clicking on the savebutton.

Alternative Flow:

1- Purchase Manager wants to update previous vendor1) Purchase Manager will enter the VendorID.

System presents Vendor Information2) Purchase Manager will make the required changes.3) Purchase Manager will save the changes by clicking on the savebutton.

3.1.2.2 Use case UC-2 Maintain Inventory Items

Primary Actor:

Purchase ManagerStakeholders and Interests:

Purchase Manager: Purchase Manager wants to maintain inventory items.

Preconditions: Purchase Manager is authenticatedPost condition: Inventory Items record is Posted.

Main Flow: 1- Purchase Manager Requests for new Item.

2- System will show item related screen.

3- Purchase Manager enters Inventory Item Info, Inventory Category, and


46/128

Expert Enterprise

4- Purchase Manager enters Item sales price, Item inventory GL accountID., Item Sales GL account ID.

5- Purchase Manager enters preferred vendor and alternative

vendor(optional) for Vendor Item Cross Reference..

6- Item is assigned in the inventory as Inventory Adjustment by clickingon the save button.

Alternative Flow:

1- Purchase Manager wants to update any existing item.1) Purchase Manager enters item ID. System presents itemInformation.

2) Purchase Manager will enter the changed information andwill save the record by clicking on the save button.5- If vendor is already in record purchase Manager will select it from

there else he will Add a new vendor and will update the Vendorsrecord.

3.1.2.3 Use case UC-3 Purchase Order:

Primary Actor:

Purchase ClerkStakeholders and Interests:

Purchase Manager: Purchase Clerk Wants to post purchase orders to Vendorsfor getting items.

Preconditions: 1- Item is out of stock and is required for purchase.2- Purchase Clerk is authenticated.

Post condition: Purchase order is saved.

Main Flow: 1- Purchase Clerk starts a new Purchase Order2- System show purchase order screen generates Purchase order no.3- Purchase Clerk enters Vendor ID4- System presents the Vendor name ,remit to address and terms and

conditions agreed to Vendor.5- Purchase Clerk enters Item and Purchase Header info.6- Purchase Clerk enter Purchase Detail.7- System presents total with accepted discount amount.8- System generates purchase order when Purchase Manager clicks print

button.

Alternative Flow:


47/128

Expert Enterprise

1. System signals error and rejects entry

3.1.2.4 Use Case UC-4 Purchases/ Received Inventory:

Primary Actor:

Purchase Clerk


Purchase Manager: Purchase Clerk wants to update inventory.

Precondition:

1- Items are received from the Vendor (from which product is purchased).2- Purchase Clerk is authenticated.

Post condition:

Inventory is updated. Vendor Invoice for payment is send to accounts.

Main Flow:

1- Purchase Clerk starts a new purchase receiving.2- System Show Purchase receiving screen.3- Purchase Clerk enters the Vendor ID. And purchase order no.4- Purchase Clerk enters invoice number of Vendor System ShowPurchase Detail.5- Purchase Clerk enters Item name, size quantity, Received Date,

Shipping Information, Warehouse, Freight ,Total and Tax amount.6-System Approve Received Purchase order.7-System updates inventory.

Alternative Flow:

2. Invalid Vendor invalid purchase order no is entered.1. System signals error and rejects entry

6- Purchased order is not Approved System signals.

3.1.2.5 Use Case UC-5 Purchase Payment

Primary Actor:

Purchase Manager


48/128

Expert Enterprise


Purchase Manager: Purchase Manager wants to keep record ofPayment made.

Precondition:

Purchase Manager Receive approval for payment fromAccounts.

Post condition: Transaction is saved. Account is updated.

Main Flow:

1-Purchase Manager starts a new Payment.2-Purchase Manager enters Vendor ID and Purchase no, system presents the

Vendor info, Order Info and Invoice numbers.

3- Purchase Manager enters the date of payment being made and PaymentDescription.4- Purchase Manager selects payment method. If the payment is in the form

of cash.7- Purchase Manager enters amount of payment.8- System updates the record of payments.

Alterative Flow:

2. Invalid Purchase No is entered.1. System signals error and rejects entry

7- Payment by check method is selected.1. Purchase Manager enters the check no and check date .

3.1.2.6 Use Case UC-6 Handle Purchase Return:

Primary Actor:

Purchase Clerk.

Stakeholders and interests:

Purchase Manager: Purchase Manager wants to keep record of purchasereturns.

Precondition:

Purchases are returned.

Post condition:

Purchase return is saved. Accounting and inventory are updated.

Main Flow:

1 Purchase Clerk. Starts Purchase return.


49/128

Expert Enterprise

3 -Purchase Clerk enters the Item name, quantity and status of returned Items.Purchase Clerk. Repeats step no 4 until indicates done.

4- Inventory and accounts are updated and adjustments are made.

Alternative Flow:

1 System will generate error if invoice number is not correct.

3.1.2.7 Case UC-7 Generate Purchase Journal Report

Primary Actor:

Purchase Manager.

Stakeholders and Interests:Purchase Manager: Purchase Manager wants to view the report.

Precondition:

Purchase Manager is authenticated.

Post condition:


1- Purchase Manager starts the purchase journal report2- Purchase Manager will enter the range of date for Report, Report order.3- Purchase Manager will select the fields he want to view.4- System will show the required report.5- Purchase Manager can save the report, print the report or can view inMicrosoft Excel.

3.1.2.8 Use Case UC-8 Generate Cash Disbursements Journal Report

Primary Actor:

Purchase Manager.


Purchase Manager: Purchase Manager wants to view the report.

Precondition:


Post condition:



50/128

Expert Enterprise

2- Purchase Manager will enter the range of date for Report, Report order.3- Purchase Manager will select the fields he want to view.4- System will show the required report.5- Purchase Manager can save the report, print the report or can view inMicrosoft Excel.

3.1.2.9 Use Case UC-9 Journal Ledger

Primary Actor:

Purchase Manager.


Purchase Manager: Purchase Manager wants to view the report.

Precondition:


Post condition:


1- Purchase Manager starts the Journal Ledger report2- Purchase Manager will enter the range of date for Report, Report order.3- Purchase Manager will select the fields he wants to view.4- System will show the required report.5- Purchase Manager can save the report, print the report or can view inMicrosoft Excel.


51/128

Expert Enterprise

3.2 System Use Case Diagram


Figure 3.1 Purchase Module


52/128

Expert Enterprise

3.2.2 SALES MODULE

Figure 3.2 Sales Module


53/128

Expert Enterprise

3.3 System Sequence Diagrams

3.3.1 Sales Module

3.3.1.1 Cash Receipts Journal Report

Figure 3.3 Cash Receipts Journal Report SD


54/128

Expert Enterprise

3.3.1.2 Generate Receipt

Figure 3.4 Generate Receipt


55/128

Expert Enterprise

3.3.1.3- Generate Sales Journal Report

Figure 3.5 Generate Sales Journal Report


56/128

Expert Enterprise

3.3.1.4 Handle Sales Return

Figure 3.6 Handle Sales Return


57/128

Expert Enterprise

3.3.1.5 Journal Ledger

Figure 3.7 Journal Ledger


58/128

Expert Enterprise

3.3.1.6 Maintain Customer

Figure 3.8 Maintain Customer


59/128

Expert Enterprise

3.3.1.7 Sales Invoicing

Figure 3.9 Sales Invoicing


60/128

Expert Enterprise

3.3.1.8 Sales Order

Figure 3.10 Sales Order


61/128

Expert Enterprise

3.3.2 PURCHASE MODULE

3.3.2.1 Cash Disbursements Journal Report

Figure 3.11 Cash Disbursements Journal Report


62/128

Expert Enterprise

3.3.2.2 Generate Purchase Journal Report

Figure 3.12 Generate Purchase Journal Report


63/128

Expert Enterprise

3.3.2.3 Journal Ledger

Figure 3.13 Journal Ledger


64/128

Expert Enterprise

3.3.2.4 Maintain Inventory Items

Figure 3.14 Maintain Inventory Items


65/128

Expert Enterprise

3.3.2.5 Maintain Vendor

Figure 3.15 Maintain Vendor


66/128

Expert Enterprise

3.3.2.6 Purchase Order

Figure 3.16 Purchase Order


67/128

Expert Enterprise

3.3.2.7 Purchase Payment

Figure 3.17 Purchase Payment


68/128

Expert Enterprise

3.3.2.8 Purchase Return

Figure 3.18 Purchase Return


69/128

Expert Enterprise

3.3.2.9 Purchase/Received inventory

Figure 3.19 Purchase/Received inventory


70/128

Expert Enterprise

3.4 Identifying Conceptual Classes

3.4.1 Sales Module

3.4.1.1 Cash Receipt general Report

Invoice DetailInvoice HeaderCash Disbursement ReportInventory ItemItem CategoryItem FamilyInventory AdjustmentItemInventory By Ware houseOrder Header

Customer InfoCustomer Item Cross ReferencesCustomer Ship To AddressCustomer Ship For Address

3.4.1.2- Generate Receipt

Invoice DetailInventory ItemInvoice HeaderReceipt

PaymentCashCheck


Customer TypeCustomer Ship For AddressCustomer InfoCustomer Ship To AddressCustomer

Customer ContactsCustomer Comments


Order HeaderOrder DetailSales InvoiceInvoice DetailInvoice HeaderInventory Item


71/128

Expert Enterprise

3.4.1.5 Sales Order

Order DetailOrder HeaderSales Order

Inventory ItemItemCustomer InfoInventory AdjustmentInventory By Ware houseCustomer Item Cross References

3.4.1.6 Sales Return

Invoice DetailInvoice Header

Inventory ItemSales ReturnInventory By Ware houseInventory Adjustment


3.4.2.1 Cash Disbursement Report

Purchase DetailPurchase HeaderCash Disbursement ReportVendor InfoInventory ItemVendor Item Cross ReferencesItem CategoryItemItem FamilyInventory AdjustmentInventory By Ware house

3.4.2.2 Maintain Inventory Item

Purchase ManagerVendor InfoItemInventory ItemItem CategoryItem FamilyInventory By Ware houseVendor Item Cross ReferencesInventory Adjustment


72/128

Expert Enterprise


Purchase ManagerVendor InfoVendor Contracts

VendorVendor Comments


Terms CategoryPurchase HeaderTermsPurchase ClerkPurchase OrderVendor Info

Purchase DetailInventory Item

3.4.2.5 Purchase Payments

Purchase HeaderVendor InfoVendor FinancialsPaymentPurchase DetailCashCheckPurchase Payments

3.4.2.6 Purchase Received

Purchase DetailPurchase HeaderItemInventory ItemPurchase ReceiveInventory By Ware houseInventory Adjustment


Purchase DetailPurchase HeaderInventory ItemPurchase ReturnItemInventory By Ware houseInventory Adjustment


73/128

Expert Enterprise

3.5 Class Diagram

3.5.1 Sales Module

3.5.1.1- Cash Receipt general Report

Figure 3.20 Cash Receipts Journal Report


74/128

Expert Enterprise




75/128

Expert Enterprise




76/128

Expert Enterprise




77/128

Expert Enterprise

3.5.1.5 Sales Order



78/128

Expert Enterprise

3.5.1.6 Sales Return

Figure 3.25 Sales Return


79/128

Expert Enterprise


3.5.2.1 Cash Disbursement Report

Figure 3.26 Cash Disbursements Journal Report


80/128

Expert Enterprise

3.5.2.2 Maintain Inventory Item





81/128

Expert Enterprise




82/128

Expert Enterprise

3.5.2.5 Purchase Payments



83/128

Expert Enterprise

3.5.2.6 Purchase Received

Figure 3.31 Purchase Received


84/128

Expert Enterprise




85/128

Expert Enterprise

3.6 Sequence Diagram

3.6.1 Sales Module

3.6.1.1 Sales Order



86/128

Expert Enterprise




87/128

Expert Enterprise



88/128

Expert Enterprise



89/128

Expert Enterprise

3.6.1.4 Handle Sales Return


90/128

Expert Enterprise

Figure 3.35 Handle Sales Return


91/128

Expert Enterprise


Figure 3.36 Generate Receipt


92/128

Expert Enterprise


3.6.2.1 Maintain Inventory Items



93/128

Expert Enterprise




94/128

Expert Enterprise




95/128

Expert Enterprise

3.6.2.4 Purchase Payment



96/128

Expert Enterprise




97/128

Expert Enterprise

3.6.2.6 Purchase/Received inventory

Figure 3.42 Purchase/Received inventory


98/128

Expert Enterprise

3.7 Design Model (PACKAGES)

3.7.1 Item

Figure 3.43 Item


99/128

Expert Enterprise

3.7.2 Vendors

Figure 3.44 Vendors


100/128

Expert Enterprise

3.7.3 Purchase Order



101/128

Expert Enterprise

3.7.4 Customer

Figure 3.46 Customer


102/128

Expert Enterprise

3.7.5 Sales Order



103/128

Expert Enterprise

CHAPTRE 04

User Interface Design


104/128

Expert Enterprise

4.1 Screen

4.1.1 Login screen.

Figure 4.1 Login Screen

GUI to DB Mapping for Screen 4.1.1

GUI Field

Name

DB Table

Name

Table Field

Name

Null able Data Type

Login Users User_id Not null nvarchar(50)

Password Users User_Password nvarchar(50)

Table 4.1 GUI to DB Mapping for Screen 4.1.1


105/128

Expert Enterprise

4.1.2 Purchase Main Screen

Figure 4.2 Purchase Main Screen


GUI Field

Name

DB Table

Name

Table Field

Name

Null able Data Type

Purchase Order PO_Header PO_Number Not null nvarchar(50)

Vendor Name Vendor_Info Vendor_ID Not null nvarchar(50)



106/128

Expert Enterprise

4.1.3 Purchase Receive

Figure 4.3 Purchase Receive


GUI Field

Name

DB Table Name Table Field

Name

Null able Data Type

PO Number PO_Header PO_Number Not null nvarchar(50)

Order Qty Vendor_Info Vendor_ID Not null nvarchar(50)Item Weight Item_Info Item_Weight float(10,2)

Item Cost Vendor_Item_Cross_Ref Price float(10,2)

Discount Per. Terms Discount_Per Number(3)

Total Amount PO_Header Total float(10,2)

Total Weight PO_Header Weight float(10,2)

Received Date Inventory_Adjust Received_date Date

Received Qty PO_Header Received_Qty float(10,2)



107/128

Expert Enterprise

4.1.4 New Purchase

Figure 4.4 New Receive


108/128

Expert Enterprise


GUI Field

Name

DB Table Name Table Field Name Null able Data Type

PO Number PO_Header PO_Number Not null nvarchar(50)ProductFamily

Item_Family Item_Family Not null nvarchar(50)

ProductName

Item_Info Item_Name nvarchar(50)

ProductVendor

Vendor_Item_Cross_Ref Vendor_ID nvarchar(50)

PurchaseDue date

PO_Detail Purchase_Due_date Number(3)

PurchaseShip date

PO_Detail Purchase_Ship_date float(10,2)

PurchaseCancel date

PO_Detail Purchase_Cancel_date float(10,2)


DiscountPer.

Terms Discount_Per Number(3)

Tex Per. Terms Tex_Per Number(3)

Freight PO_Detail Freight float(10,2)

Order Qty PO_Detail Order_Qty float(10,2)

Item Weight Item_Info Item_Weight float(10,2)



109/128

Expert Enterprise

4.1.5 Sales Main Screen

Figure 4.5 Sales Main Screen


GUI Field

Name


Invoice Date Invoice_Detail Invoice_Date Date


Order Qty PO_Detail Order_Qty float(10,2)



110/128

Expert Enterprise

4.1.6 New Sales

Figure 4.6 New Sales


GUI Field Name DB Table Name Table Field Name Null

able

Data Type

CustpmerName Customer_Info Customer_Name nvarchar(50)


InvoiceDueDate Invoice_Detail Invoice_Due_Date Date

InvoiceShipDate Invoice_Detail Invoice_Ship_Date Date

InvoiceCancelDate Invoice_Detail Invoice_Cancel_date Date

Item Name Item_Info Item_Name nvarchar(50)

Item Cost Vendor_Item_Cross_Ref Price float(10,2)Discount Per. Terms Discount_Per Number(3)




Description Invoice_Detail Invoice_Description nvarchar(50)



111/128

Expert Enterprise

4.1.7 Sales Ship

Figure 4.7 Sales Ship


112/128

Expert Enterprise

4.1.8 Sales Ship Detail.

Figure 4.8 Sales Ship Detail


GUI Field Name DB Table Name Table Field Name Null

able

Data Type

Invoice Number Invoice_Header Invoice_Number Notnull

Date

CustpmerName Customer_Info Customer_Name nvarchar(50)


InvoiceDueDate Invoice_Detail Invoice_Due_Date Date

InvoiceShipDate Invoice_Detail Invoice_Ship_Date Date

InvoiceCancelDate Invoice_Detail Invoice_Cancel_date DateItem Name Item_Info Item_Name nvarchar(50)


Discount Per. Terms Discount_Per Number(3)



Order Qty. Invoice_Header Order_Qty float(10,2)


Description Invoice_Detail Invoice_Description nvarchar(50)


113/128

Expert Enterprise

4.1.9 Vendor Main Screen.

Figure 4.9 Vendor Main Screens


114/128

Expert Enterprise

4.1.10 New Vendor (Insert/Update)

Figure 4.10 New Vendor


115/128

Expert Enterprise


GUI Field

Name


Vendor

Name

Vendor_Info Vendor_Name nvarchar(50)

VendorAdd 1

Vendor_Info Vendor_Add_1 nvarchar(50)

VendorAdd 2

Vendor_Info Vendor_Add_2 nvarchar(50)

Vendor City Vendor_Info Vendor_City nvarchar(50)

VendorCountry

Vendor_Info Vendor_Country nvarchar(50)

VendorPhone

Vendor_Info Vendor_Phone nvarchar(50)

Vendor

Email

Vendor_Info Vendor_Email nvarchar(50)

Vendor WebPage

Vendor_Info Vendor_Web_Page nvarchar(50)

VendorType

Vendor_Type Vendor_Type Not Null nvarchar(50)

Account no Vendor_Accounts Account_No Number(20)

ContactName

Vendor_Contact Contact_Name nvarchar(50)

ContactDescription

Vendor_Contact Contact_Description nvarchar(50)

Contact

Add 1

Vendor_Contact Contact_Add 1 nvarchar(50)

ContactAdd 2

Vendor_Contact Contact_Add 2 nvarchar(50)

ContactPhone

Vendor_Contact Contact_Phone nvarchar(50)

ContactCellular

Vendor_Contact Contact_Cellular nvarchar(50)

ContactEmail

Vendor_Contact Contact_Email nvarchar(50)

ContactWeb Page

Vendor_Contact Contact_Web_Page nvarchar(50)



116/128

Expert Enterprise

4.1.11 Customer Main screen

Figure 4.11 Customer Main Screen


117/128

Expert Enterprise

4.1.12 New Customer (Insert/Update)

Figure 4.12 New Customer


118/128

Expert Enterprise


GUI Field

Name


Customer

Name

Customer _Info Customer _Name nvarchar(50)

CustomerAdd 1

Customer _Info Customer _Add_1 nvarchar(50)

CustomerAdd 2

Customer _Info Customer _Add_2 nvarchar(50)

CustomerCity

Customer _Info Customer _City nvarchar(50)

CustomerCountry

Customer _Info Customer _Country nvarchar(50)

CustomerPhone

Customer _Info Customer _Phone nvarchar(50)

CustomerEmail

Customer _Info Customer _Email nvarchar(50)

CustomerWeb Page

Customer _Info Customer _Web_Page nvarchar(50)

CustomerType

Customer _Type Customer _Type Not Null nvarchar(50)

Account no Customer _Accounts Customer _No Number(20)

ContactName

Customer _Contact Contact _Name nvarchar(50)

ContactDescription

Customer _Contact Contact _Description nvarchar(50)

ContactAdd 1

Customer _Contact Contact _Add 1 nvarchar(50)

ContactAdd 2

Customer _Contact Contact_Add 2 nvarchar(50)

ContactPhone

Customer _Contact Contact_Phone nvarchar(50)

ContactCellular

Customer _Contact Contact_Cellular nvarchar(50)

ContactEmail

Customer _Contact Contact_Email nvarchar(50)

Contact

Web Page

Customer _Contact Contact_Web_Page nvarchar(50)



119/128

Expert Enterprise

4.1.13 Ship to Information

Figure 4.13 Ship to Information


GUI Field

Name


ContactName

Ship_To_Info Contact _Name nvarchar(50)

ContactDescription

Ship_To_Info Contact _Description nvarchar(50)

ContactDepartment

Ship_To_Info Contact _Department nvarchar(50)

ContactAdd 1

Ship_To_Info Contact _Add 1 nvarchar(50)

ContactAdd 2

Ship_To_Info Contact_Add 2 nvarchar(50)

Contact City Ship_To_Info Contact_City nvarchar(50)ContactPhone

Ship_To_Info Contact_Phone nvarchar(50)

ContactCellular

Ship_To_Info Contact_Cellular nvarchar(50)

ContactEmail

Ship_To_Info Contact_Email nvarchar(50)

ContactWeb Page

Ship_To_Info Contact_Web_Page nvarchar(50)


120/128

Expert Enterprise

4.1.14 Ship for Information

Figure 4.14 Ship for Information


GUI Field

Name


Ship ForName

Ship_For _Info Ship_For _Name nvarchar(50)

Ship ForAdd 1

Ship_For _Info Ship_For _Add 1 nvarchar(50)

Ship ForAdd 2

Ship_For _Info Ship_For _Add 2 nvarchar(50)

Ship ForCity

Ship_For _Info Ship_For _City nvarchar(50)

Ship ForCountry

Ship_For _Info Ship_For _Country nvarchar(50)

Ship ForEmail

Ship_For _Info Ship_For _Email nvarchar(50)

Ship ForWeb Page

Ship_For _Info Ship_For _Web_Page nvarchar(50)


121/128

Expert Enterprise

4.1.15 Inventory

Figure 4.15 Inventory


122/128

Expert Enterprise

4.1.16 Inventory Adjustment

Figure 4.16 Inventory AdjustmentGUI to DB Mapping for Screen 4.1.16

GUI Field

Name


InventoryFamily

Inventory Family Inventory Family Not Null nvarchar(50)

InventoryCategory

Inventory Category Inventory Category nvarchar(50)

Item Name Item_Info Item Name nvarchar(50)

AdjustmentType

Inventory_Adjustment Adjustment Type Not Null nvarchar(50)

Adjustment

Date

Inventory_Adjustment Adjustment Date Date

AdjustmentReason

Inventory_Adjustment Adjustment Reason nvarchar(50)

AdjustmentNotes

Inventory_Adjustment Adjustment Notes nvarchar(50)

AdjustmentDescription

Inventory_Adjustment AdjustmentDescription

nvarchar(50)

Open Qty Inventory_Adjustment Open Qty Number(30)

AdjustedQty

Inventory_Adjustment AdjustedQty

Number(30)


123/128

Expert Enterprise

4.1.17 Product Main Screen

Figure 4.17 Product Main Screen


124/128

Expert Enterprise

4.1.18 New Product Detail.

Figure 4.18 New Product Detail


GUI Field

Name


Item Type Item_Type Item Type Not Null nvarchar(50)

ItemCategory

Item_Category Item Category nvarchar(50)

Item Name Item_Info Item Name nvarchar(50)

ItemDescription

Item_Info Item Description nvarchar(50)

Sales

Description

Item_Info Sales Description nvarchar(50)

PurchaseDescription

Item_Info Purchase Description nvarchar(50)

Item Weight Item_Info Item Weight Number(10.2)

Item Style Item_Info Item Style nvarchar(50)

Item Price Item_Info Item Price Number(30)



125/128

Expert Enterprise

4.1.19 Log Out Screen

Figure 4.19 Log out


126/128

Expert Enterprise

4.2 Traceability Matrix

Sr# Feature

Use

caseID

Elaborat

edUse-Case-ID

Depende

nt

Classes

UIID

DB-

Table

IDs(if

require

d)

Use Case

Cross

reference(Related Use

Cases)

1 Login N/A N/A Login 1 LoginStart Of AllUse cases

2

Purchase

Record

UC_7,UC

_8,UC_9

UC_7,

UC_

8,UC_

9

Purchase

Detail 2

POheader,

PO

Detail,invento

ry

PurchaseOrder,

Purchase

Receive,Purchasegeneral report,journal ledger

3

Purchase

Receive

UC_4

UC_4

PurchaseReceive

2.1

Inventory

adjustment,

Inventory

Adjust

mentDetail

PurchaseOrder,

PurchaseReceive

4NewPurch

ase

UC_3

UC_3

PurchaseOrder

2.2

POheader,

PODetail

PurchaseReceivePurchase

Order,

5Vend

orUC_1

UC_1

Vendor4

4.1

VendorInfo.

VendorDetail

Vendor

Contact

MaintainVendor

Purchase Order

6Inventory

UC_2,UC_6

UC_2

Inventory

6,6.1,

7, 7.1

Inventory

adjustment,

Inventory

AdjustmentDetail

PurchaseOrder,

PurchaseReceive,Purchase

general report,journal ledger


127/128

Expert Enterprise

7 Customer UC_1 UC_1Customer

5,

5.1.1,5.1.2,5.1.3

Customer Info.Custom

erDetail,

CusShip toAdd.Cus.ShipForAdd

Sales Order ,

Sales journalreport, journal

ledger

8 Sales

UC_2,UC_3

UC_2,

UC_

3

SalesOrder

3.1

Invoiceheader,InvoiceHeader

Detail

Sales Order

9SalesRecor

d

UC_4,UC_6,UC_7

UC_4,

UC_6,

UC_7

SalesRecord

3

Invoiceheader,InvoiceHeaderDetail,Invento

ryAdjustment

Sales Order ,Sales journal

report, journalledger

10SalesRetur

n

UC_ 5

UC_5

SalesReturn

6, 6.1

Invento

ryAdjustment,

Inventory

AdjustmentDetail

Sales Return,Sales Order

11LogOut

N/A N/A Log Out 8 LogoutEnd Of All Use

cases

Table 4.14 Tractability Matrix


128/128

Expert Enterprise

References

Roger S PressmenApplying UML and PatternsOOD Methodologies

Sewn 2000Richards SystemsPeach Tree Accounting Systemswww.Integralaccounting.comwww.Sapsolutions.comwww.Erpsolprovider.com

expert enterprise

Documents