Final Sltc Doc

8/3/2019 Final Sltc Doc

1/84

SLTC Retail System

Subject Title : Software Development Project AAPP006-3-2-SDP

System Name : SLTC Retail System

Group Member : Kasun Fernando - CB003947

AshanMaduranga - CB003717

LakshikaTennakoon - CB003961

Intake : DF1061-ICT

Submitted to : Ms. Oshini Jayatunga

Hand out Date : 23 rd February 2011

Hand in Date : 13 th May 2011

Word Count :
http://../USB/My%20Documents/APIIT%20Projects/SAD%20Projects/Group%20Projects/cb002094/Local%20Settings/Temporary%20Internet%20Files/Content.IE5/index.ht


2/84

SLTC System Development Project

Asia Pacific Institute of Information Technology 2

Table of Contents

Table of Figures ........................................................................................................... 6

Table of Tables ............................................................................................................. 8

1. Introduction .......................................................................................................... 9 Scope ...................................................................................................................... 11

2. Requirement Specifications ............................................................................... 11

2.1 Functional requirements ................................................................................... 11

2.2 Non Functional Requirements.......................................................................... 12

3. Feasibility Study ................................................................................................ 13

3.1 Technical Feasibility ........................................................................................ 13

3.2 Operational Feasibility ..................................................................................... 13 3.2.1 Performance .............................................................................................. 13

3.2.2 Information ................................................................................................ 14

3.2.3 Economy ................................................................................................... 14

3.2.4 Control ...................................................................................................... 14

3.2.5 Efficiency .................................................................................................. 14

3.2.6 Services ..................................................................................................... 14

3.3 Economic Feasibility ........................................................................................ 15

3.3.1 Cost Benefit Analysis ................................................................................ 15

4. ER Diagrams ...................................................................................................... 19

5. Data Flow Diagrams .......................................................................................... 21

5.1 Context Diagram .............................................................................................. 21

5.2 Level 0 Diagram ............................................................................................... 22

6. Hierarchy Chart .................................................................................................. 23

7. System Designs .................................................................................................. 24

7.1 Login ................................................................................................................ 24

7.1.1 Screen Design............................................................................................ 24

7.1.2 Pseudo Code .............................................................................................. 24

7.1.3 Test Plan .................................................................................................... 25

7.2 Main Menu ....................................................................................................... 26

7.2.1 Screen Design............................................................................................ 26

7.2.2 Pseudo Code .............................................................................................. 26

7.2.3 Test Plan .................................................................................................... 27


3/84



7.3 Invoice .............................................................................................................. 28

7.3.1 Screen Design............................................................................................ 28

7.3.2 Pseudo Code .............................................................................................. 29

7.3.3 Test Plan .................................................................................................... 31

7.4 Customer Back Order ....................................................................................... 33

7.4.1 Screen Design............................................................................................ 33

7.4.2 Pseudo Code .............................................................................................. 34

7.4.3 Test Plan .................................................................................................... 35

7.5 Suppliers Menu ................................................................................................ 36

7.5.1 Screen Design............................................................................................ 36

7.5.2 Pseudo Code .............................................................................................. 36

7.5.3 Test Plan .................................................................................................... 37

7.6 Manage Suppliers ............................................................................................. 38

7.6.1 Screen Design............................................................................................ 38

7.6.2 Pseudo Code .............................................................................................. 39

7.6.3 Test Plan .................................................................................................... 40

7.7 Returns to Suppliers ......................................................................................... 41

7.7.1 Screen Design............................................................................................ 41

7.7.2 Pseudo Code .............................................................................................. 41

7.7.3 Test Plan .................................................................................................... 42

7.8 Non Active Suppliers ....................................................................................... 43

7.8.1 Screen Design............................................................................................ 43

7.8.2 Pseudo Code .............................................................................................. 44

7.8.3 Test Plan .................................................................................................... 44

7.9 Customers Menu .............................................................................................. 45

7.9.1 Screen Design............................................................................................ 45

7.9.2 Pseudo Code .............................................................................................. 46

7.9.3 Test Plan .................................................................................................... 46

7.10 Manage Customers ......................................................................................... 47

7.10.1 Screen Design.......................................................................................... 47

7.10.2 Pseudo Code ............................................................................................ 48

7.10.3 Test Plan .................................................................................................. 49

7.11 Customer Returns ........................................................................................... 50


4/84



7.11.1 Screen Design.......................................................................................... 50

7.11.2 Pseudo Code ............................................................................................ 50

7.11.3 Test Plan .................................................................................................. 51

7.12 Payments ........................................................................................................ 52

7.12.1 Screen Design.......................................................................................... 52

7.12.2 Pseudo Code ............................................................................................ 52

7.12.3 Test Plan .................................................................................................. 53

7.13 Non Active Customers ................................................................................... 54

7.13.1 Screen Design.......................................................................................... 54

7.13.2 Pseudo Code ............................................................................................ 55

7.13.3 Test Plan .................................................................................................. 55

7.14 User Account Menu ....................................................................................... 56

7.14.1 Screen Design.......................................................................................... 56

7.14.2 Pseudo Code ............................................................................................ 56

7.14.3 Test Plan .................................................................................................. 57

7.15 New User ........................................................................................................ 57

7.15.1 Screen Design.......................................................................................... 57

7.15.2 Pseudo Code ............................................................................................ 57

7.15.3 Test Plan .................................................................................................. 58

7.16 Modify / Delete User ...................................................................................... 59

7.16.1 Screen Design.......................................................................................... 59

7.16.2 Pseudo Code ............................................................................................ 59

7.16.3 Test Plan .................................................................................................. 60

7.17 Stock Menu .................................................................................................... 61

7.17.1 Screen Design.......................................................................................... 61

7.17.2 Pseudo Code ............................................................................................ 61

7.17.3 Test Plan .................................................................................................. 62

7.18 Good Receive Note ........................................................................................ 63

7.18.1 Screen Design.......................................................................................... 63

7.18.2 Pseudo Code ............................................................................................ 63

7.18.3 Test Plan .................................................................................................. 64

7.19 Purchase Order Generation ............................................................................ 65

7.19.1 Screen Design.......................................................................................... 65


5/84



7.19.2 Pseudo Code ............................................................................................ 65

7.19.3 Test Plan .................................................................................................. 66

7.20 Product Management ..................................................................................... 67

7.20.1 Screen Design.......................................................................................... 67

7.20.2 Pseudo Code ............................................................................................ 68

7.20.3 Test Plan .................................................................................................. 69

7.21 Category Management ................................................................................... 70

7.21.1 Screen Design.......................................................................................... 70

7.21.2 Pseudo Code ............................................................................................ 70

7.21.3 Test Plan .................................................................................................. 71

8. Report Designs ................................................................................................... 72

8.1 Invoice .............................................................................................................. 72

8.2 Debtors ............................................................................................................. 73

8.3 Price List .......................................................................................................... 74

9. Gantt chart .......................................................................................................... 75

10. Workload Matrix ............................................................................................. 76

11. Business Rules ................................................................................................ 80

12. Assumptions .................................................................................................... 81

13. Limitations ...................................................................................................... 82

14. Conclusion ...................................................................................................... 83

Appendix .................................................................................................................... 84

Weekly Meeting Reports........................................................................................ 84


6/84



Table of Figures

Figure 1: ER Diagram A ............................................................................................ 19

Figure 2: ER Diagram B ............................................................................................ 20

Figure 3: Context Diagram ........................................................................................ 21

Figure 4: Level 0 Diagram ......................................................................................... 22

Figure 5: Hierarchy Chart .......................................................................................... 23

Figure 6: Login Screen ............................................................................................... 24

Figure 7: Main Menu Screen ..................................................................................... 26

Figure 8: Invoice Screen ............................................................................................ 28

Figure 9: Customer Back Order Screen ..................................................................... 33

Figure 10: Supplier Menu Screen .............................................................................. 36

Figure 11: Suppliers Screen ....................................................................................... 38

Figure 12: Returns to Supplier Screen ....................................................................... 41

Figure 13: Non Active Suppliers Screen .................................................................... 43

Figure 14: Customer Menu Screen ............................................................................ 45

Figure 15: Customer Management Screen ................................................................. 47

Figure 16: Customer Returns Screen ......................................................................... 50

Figure 17: Customer Payments Screen ...................................................................... 52

Figure 18: Non Active Customers Screen .................................................................. 54

Figure 19: User Accounts Menu ................................................................................ 56

Figure 20: New User Screen ...................................................................................... 57

Figure 21: Modify/Delete User Screen ...................................................................... 59

Figure 22: Stock Menu Screen ................................................................................... 61

Figure 23: Good Receive Note Screen ....................................................................... 63

Figure 24: P.O. Generation Screen ............................................................................ 65

Figure 25: Product Management Screen .................................................................... 67
http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169746http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169746http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169747http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169747http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169748http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169748http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169749http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169749http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169750http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169750http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169751http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169751http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169752http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169752http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169753http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169753http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169754http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169754http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169755http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169755http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169756http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169756http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169757http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169757http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169758http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169758http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169759http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169759http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169760http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169760http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169761http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169761http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169762http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169762http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169763http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169763http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169764http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169764http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169765http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169765http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169766http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169766http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169767http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169767http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169768http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169768http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169770http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169770http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169770http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169768http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169767http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169766http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169765http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169764http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169763http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169762http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169761http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169760http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169759http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169758http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169757http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169756http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169755http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169754http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169753http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169752http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169751http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169750http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169749http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169748http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169747http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169746


7/84



Figure 26: Category Management Screen .................................................................. 70

Figure 27: Reports - Invoice ...................................................................................... 72

Figure 28: Reports - Debtors ...................................................................................... 73

Figure 29: Reports - Price List ................................................................................... 74
http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169770http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169770http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169770http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169771http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169771http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169772http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169772http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169773http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169773http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169773http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169772http://c/Documents%20and%20Settings/cb003947/Desktop/VERY%20FINAL%20SLTC/FINAL%20SLTC%20DOC.docx%23_Toc294169771


8/84



Table of Tables

Table 1: Test Plan - Login .......................................................................................... 25

Table 2: Test Plan - Main Menu ................................................................................ 27

Table 3: Test Plan - Invoice ....................................................................................... 32

Table 4: Test Plan - Customer Back Order ................................................................ 35

Table 5: Test Plan Supplier Menu .............................................................................. 37

Table 6: Test Plan - Suppliers .................................................................................... 40

Table 7: Test Plan - Returns to Supplier .................................................................... 42

Table 8: Test Plan - N.A. Suppliers ........................................................................... 44

Table 9: Test Plan - Customer Menu ......................................................................... 46

Table 10: Test Plan - Customer Management ............................................................ 49

Table 11: Test Plan - Customer Returns .................................................................... 51

Table 12: Test Plan - Customer Payments ................................................................ 53

Table 13: Test Plan N.A. Customers .......................................................................... 55

Table 14: Test Plan - User Accounts Menu ............................................................... 57

Table 15: Test Plan - New User ................................................................................. 58

Table 16: Test Plan - Modify/Delete User ................................................................. 60

Table 17: Test Plan - Stock Menu .............................................................................. 62

Table 18: Test Plan - GRN ......................................................................................... 64

Table 19: Test Plan - P.O. Generation ....................................................................... 66

Table 20: Test Plan - Product Management ............................................................... 69

Table 21: Test Plan - Category Management ............................................................. 71

Table 22: Discount Criteria ........................................................................................ 80


9/84



1. Introduction

Sri Lanka Trading Company (SLTC) is a company that sells goods ranges from

sports goods, building materials and hardware to household equipments to food stuff.

After 10 successful years management has decided to deploy an information

system in order to achieve following;

Gain competitive advantage. Increase the accuracy (eg: calculation errors) Enhance efficiency and performance.

Make use of the reports to analyze and take critical decisions. Ease out the work of employees and management. To achieve a high data integrity and confidentiality.

Hence the management offered A+ Solutionz to undertake the project and make

an inventory system to cater the above mentioned criteria. Thus the basic outline was

made so as to what are the modules to be developed and so forth. Following was the

project proposal made by the steering committee considering the constraints of the

system to define a scope for the project.

Components Product Management, Purchase order generation, Supplier

maintenance, Customer maintenance.

Interrelated Components Orders, Sales Boundary The system will be implemented on a LAN scale basis limiting

to one building.

Purpose Stock, Supplier and Customer details management of thecommunication. Enhance the efficiency and the accuracy of the

communications inventory controlling.

Environment Customers, Suppliers. Input Supplier details, Stock details, Customer details, Sales details Output quantity-on-hand report, Product s price list report, Re-order

report, Supplier reports, Sales report, Customer reports, POG report

Constraints System will be offering the above mentioned modules onlysince this is an inventory system all the components required for inventory


10/84



handling will be incorporated. The network is only limited to the LAN that is

defined and not over the internet.

Interfaces o Security Access Control to system. System will be only accessed by

authorized personals. Unauthorized access will be blocked using

password protection.

o Filtering When taking Customer/Stock/Supplier/Sales details only

necessary data will be gathered and when printing a

Customer/Stock/Suppler/Sales report, only relevant details will be

printed.

o Detecting and Correcting Errors System will validate the data

entered into the System at its submitting process and will inform to do

corrections if detected any errors.

o Buffering In stock management, when stock reaches its reorder

level, cashier will get an alert message regarding that.

o Summarizing Customer detail reports and Stock reports will be

available for manager to view and print in a useful way.


11/84



Scope

The major scope of the system generated by the A+ Solutionz to Sri LankaTrading Company as follows,

Product Maintenance Stock Maintenance Supplier Maintenance Return goods to the Supplier Customer Maintenance Receive goods returned by the Customers Maintaining Sales on cash or credits

Generate back orders

2. Requirement Specifications

2.1 Functional requirements

Stocks

Manage Stocks Add New Categories Update Existing Categories

Manage Categories Add New Departments Update Existing Departments Deleting Existing Departments

Good Received Note Add New Stocks

Suppliers

Manage Suppliers Add New Supplier Update Existing Supplier Deleting Existing Supplier

Return Damaged goods to Supplier


12/84



Customers

Manage Customers Add New Customers Update Existing Customers Deleting Existing Customers

Receive Damaged goods returned by the Customer

Handle payments by the credit holders

Generate report on debtors based on the criteria given by the user User Accounts

Create New User Accounts

Modify Existing User Accounts

Delete Existing User Accounts Invoice

Maintain Sales on Credit and Cash

Creating back orders for goods which are not available in the

company

2.2 Non Functional Requirements

User friendliness Accessibility Maintainability Reliability Response Time Robustness Security of Information Stability


13/84



3. Feasibility Study

3.1 Technical Feasibility

In order to use the system implemented by A+ Solutionz Sri Lanka Trading

Company (SLTC) needs to occupy resources such as a desktop computer or a laptopdevice and a printer to print bills and reports generated by the system as thesetechnology is not available within the organization currently. Furthermore usertraining needs to be carried out in order to plunder the highest advantages of thesystem.

Recommended Specifications for the computer

1024 MB or more RAM

2.2 GHz or higher CPU

Windows XP or any other higher version

1280 * 780 display

Microsoft Visual Studio

Microsoft Database Management Studio

Keyboard and Mouse Printer Dot Matrix or Inkjet Printer User Training

3.2 Operational Feasibility

PIECES Framework was conducted within the organization in order to get aclear picture of the current manual system.

3.2.1 Performance

Current manual system consumes a great amount of time in the Sales processas the Total amount and the discounts should calculate manually. Furthermore when

selling goods on credit basis consumes furthermore time as the credit limits and debtamount need to be calculated manually for every transaction. When the GoodReceive Notes arrive all the information needs to be kept manually whereas the unitprice need to be calculated in the same manner based on the profit approved by thesupplier. Moreover when Customers are purchasing goods the stock keeper needsmanually go through the existing stocks in order to identify whether the request canbe fulfilled. Overall throughput is low as registering processes consumes a lot of time.


14/84



3.2.2 Information

The details of all the transactions are not recorded resulting Cashier frauds.Moreover when customers are returning goods there can be deceptions as thecompany does not possess satisfactory information on the goods purchased by thecustomers. The current system does not provide timely, pertinent information and asthe information is not properly formatted the accuracy is low.

3.2.3 Economy

Current system results in increasing the stationary cost as all the transactionsbetween the suppliers are need to be maintained manually. Moreover by moving onto the new system intangible benefits such as Customer satisfaction can be gainedwhereas the disadvantage of frauds by the Customers or Cashier can be eliminated.

3.2.4 ControlProviding security to the data is essential but this is not fulfilled by the

existing manual system hence providing the appropriate security to the data bygiving hierarchical approach which ensures that the users of the system are exposedto the information which is relaxant to them.

3.2.5 Efficiency

One of the major disadvantages of the existing system in Sri Lanka TradingCompany is the vast response time it consumes in generating Invoice. By introducingthe new system Transaction time can be reduced by a huge level. The man power isalso not satisfactorily utilized.

3.2.6 Services

As the customer satisfaction is not up to recommended standards as the issueswith credit limits and return goods are frequent occurrence. Therefore by maintainingcustomer records the new system eliminates those issues as a certain credit limit isassigned to all the customers who are registered within the organization and theseinformation can only be altered by the Finance Manager or CEO of the organization

hence increase the reliability of the services provided by the system.

Some of the major services provided by Sri Lanka Trading Company are,

Stock Maintenance Sales of goods on cash/credit Customer returned goods maintenance Customer credit maintenance Supplier information maintenance Back order generation


15/84


16/84



Estimated Annual Operational Costs

Cost Type Cost (Rs.)

Personal Salary

Cashier

Stock Manager

System Maintenance

Ongoing Training

System Maintenance and Modifications

Other Expenses

Printing Papers, Cartridges and Stationary

Electricity Bill

180 000.00

360 000.00

10 000.00

60 000.00

100 000.00

60 000.00

Total Operational Costs 770 000.00

Benefits

Intangible Benefits

- Higher employee morale

- Customer satisfaction

- Supplier satisfaction

- Less time consumption in Stock maintenance


17/84



Tangible Benefits

Payback Analysis

Benefit Type Cost (Rs.)

Error Reduction and Enhanced Accuracy

Improved Stock Management and Control

Increased Sales Opportunities

Opening New Markets

Accelerated Speed of Transactions

250 000.00

300 000.00

400 000.00

80 000.00

210 000.00

Total tangible Benefits 1 240 000.00

Year Costs Cumulative

Costs

Benefits Cumulative

Benefits

Year 0 982 500.00 982 500.00 - -

Year 1 770 000.00 1 752 500.00 1 240 000.00 1240 000.00

Year 2 800 000.00 2 552 500.00 1 300 000.00 2 540 000.00

Year 3 852 000.00 3 404 500.00 1 900 000.00 4 140 000.00

Year 4 933 000.00 4 337 500.00 2 500 000.00 6 640 000.00

Year 5 1 254 000.00 5 591 500.00 3 200 000.00 9 840 000.00


18/84



Payback Period = 2 + [(2 552 500 2 540 000) / (1 900 000 852 000) ] years

= 2.01193 years

= 2 years and 1 month

To accomplish the payback the system would take 2 years and 1 month.

Return on Investment Analysis

ROI = (Total Benefits Total Costs) / Total Costs * 100

= (9 840 000.00 5 591 500.00) / 5 591 500.00 * 100

= 75.9814%


19/84



4. ER Diagrams

Figure 1: ER Diagram A


20/84



Figure 2: ER Diagram B


21/84



5. Data Flow Diagrams

5.1 Context Diagram

Figure 3: Context Diagram


22/84



5.2 Level 0 Diagram

Figure 4: Level 0 Diagram


23/84



6. Hierarchy Chart

Figure 5: Hierarchy Chart


24/84



7. System Designs

7.1 Login

7.1.1 Screen Design

7.1.2 Pseudo Code

STARTLogin button

READ User nameREAD PasswordIF User name == OR Password == THEN

DISPLAY Error ELSEIF User name == existing Username AND Password ==

relevant PasswordDISPLAY Success UPDATE TblUser with timeELSE

DISPLAY Error ENDIF

Cancel buttonClose the Form

END

Figure 6: Login Screen


25/84



7.1.3 Test Plan

Test Case Description Expected Result/s Actual Result

System

Login

Login - btn If User Name and

Password is correct

Display amsgBox about a

successful login.

Success

Cancel - btn Close the form. Success

Table 1: Test Plan - Login


26/84



7.2 Main Menu

7.2.1 Screen Design

Main menu is the interface that follows after a successful login. This contains

the main buttons of the system which connects to the relevant forms. Buttons are

enabled according to the rank of the user. For an example, the user account but ton

is enabled only to managers. A menu strip is available for quick access to other

forms.

7.2.2 Pseudo Code

STARTIF logged in User Rank== Cashier THEN

DISABLE btnSupplierDISABLE btnStock

ENDIFInvoice button

Figure 7: Main Menu Screen


27/84



Show Invoice Form

Supplier buttonShow Supplier Form

Customer buttonShow Customer Form

User Account button Show User Accounts Form

Stock buttonShow Stock Form

Log out button

Close Form

END

7.2.3 Test Plan

Test Case Test Description Expected Result Actual Result

Main Invoice-button Takes to the Invoice. Success

Suppliers-button Takes to the Supplier

Menu.

Success

Customers-button Takes to the Customer

Menu.

Success

User Accounts-button Takes to the User

Account menu

Success

Stocks-button Takes to the Stocks Menu Success

Log out Log out from the system Success

Table 2: Test Plan - Main Menu


28/84



7.3 Invoice

7.3.1 Screen Design

Invoice form is the form where Invoice is generated when a customer

purchases goods from the company. It allows the user to see the available amount of

products when the category and the product name are given. Thus the product to be

sold is selected with the quantity. When all the items are selected total Qty, total

amount and discount will be automatically generated. Once this is done the customer

ID and the payment method is selected and the invoice is generated unless there is no

back order.

Figure 8: Invoice Screen


29/84



7.3.2 Pseudo Code

START

AUTOGENARATE Invoice No, Date, User IDLOAD cboCategory with Category namesTotal quantity = 0Total amount = 0Net amount = 0

Search button READ Product NameIF selected item in cboCategory = OR Product Name = THEN

LOAD Product List dataGridwith Product ID, Product Names,Available amount, PriceELSE IF Product Name == Existing Product Name THEN

Available amount = COUNT of products WHERE Product ID== Selected Product s ID AND Sold field == FALSE AND Damage == FALSEfrom Tbl Stock

LOAD Product List dataGrid with Product ID, ProductNames, Available amount, PriceENDIFIF Row is selected from the Datagrid THEN

AUTOFILL Product Name textboxENDIF

Add To Cart buttonREAD QuantityIF Quantity > Available Amount THEN

DISPLAY Needs to create back order ELSE

UPDATE Invoice Detail Table with Invoice ID, Stock ID,

ProductID, Quantity UPDATETbl Stockwith Sold field = TRUEFILL Invoice Detail DataGrid with Product ID, Name,

Quantity, PriceTotal quantity = Total quantity + QuantityTotal amount = Total amount + (Unit price * Quantity)IF Total amount > 100 000 THEN

Discount = 20%ELSE IF Total amount > 50 000 THEN

Discount = 10%ELSEIF Total amount > 30 000 THEN


30/84



Discount = 5%ELSE

Discount = 0%ENDIFNet Amount = Total Amount (1-(Discount/100))

ENDIF

Availability buttonREAD Customer IDIF Customer ID == Existing Customer ID THEN

AUTO FILL Credit Limit , Available CreditELSE

DISPLAY ErrorENDIF

Credit Radio buttonIF Available Credit > Total amount THEN

AUTOFILL Credit textbox with Total amountAvailable credit = Available credit Total amount

ELSEAUTOFILL Credit textbox with available CreditCash amount = Total amount available Credit amountDISPLAY Cash amount

Available credit = 0ENDIF

Cash Radio buttonAUTO FILL Credit textbox with Total amount

Back Order buttonShow Back order form

Print buttonUPDATETbl Invoice with Date, Invoice ID, Total Amount, Discount,

Customer IDUPDATE Tbl Customer with Available Credits, Credit DateShow Invoice Report

END


31/84



7.3.3 Test Plan


Invoice

Invoice No - txtBox New Invoice number willbe auto generated at theform load.

Success

Category cmbBox Category names will beloaded at the form load.

And when a category isselected, Product List data grid will be loaded.

Success

Search btn Will filter Product list inthe data grid to matchingProduct Name.

If Name is not valid,msgBox will be display.

Success

Product List dataGrid When a row is selected,Product Name will bedisplayed on ProductName txtBox

Success

Add to Cart btn Product details and Qtywill be added to theInvoice List dataGridand Total Qty, TotalAmount, Discount, NetAmount txtBoxes willbe updated.

Or, amsgBox will be

displayed.

Success

Reset btn Will empty all data inInvoice List dataGrid.

Success


32/84



Availability btn Will check the existenceof the Customer ID onID txtBox.

And display Customers

Credit Limit andAvailably Credit ontxtBoxes.

Or, amsgBox will bedisplayed.

Success

Payments CreditchkBox

Will make Credit txtBoxeditable.

Success

Payments Cash chkBox Will make Cash txtBoxeditable.

Success

Back Order btn Opening Back OrderForm

Success

Print Show invoice to beprinted.

Success

Table 3: Test Plan - Invoice


33/84



7.4 Customer Back Order

7.4.1 Screen Design

Customer back order is created when the stock is out of order. The items areadded just like it was in invoice form and is saved with the quantity required so thatwhen the stock arrives the customer could be contacted.

Figure 9: Customer Back Order Screen


34/84



7.4.2 Pseudo Code

START

AUTOGENERATE Date, User Name, Customer IDLOAD cboCategory with Category namesIF Product Name == OR selected Item in cboCategory == THEN

LOAD Product List dataGrid with Product ID, ProductNames, Available amount, Price

ELSE IF Product Name == Existing Product Name THEN Available amount = COUNT of products WHERE Product ID ==

Selected Product s ID AND Sold field == FALSE from Stock Table FILL Product List dataGrid with Product ID, Product Names,Available amount, Price

ENDIFIF Row is selected from the datagrid THEN

AUTOFILL Product Name textboxENDIF

Add to Cart buttonREAD QuantityBack order quantity = quantity

SAVE Quantity, ProductID in Tbl BackorderdetailsUPDATE Backorder quantity, Product ID in Tbl ProductsADD ProductID, Product Name, Back order quantity in Back order

dataGrid

Reset buttonClear text boxesClear Data Grid views

Save buttonREAD Due DateSAVE Date, Due Date, CustomerID, UserID in Tbl BackOrder

END


35/84



7.4.3 Test Plan


Customer

back order

Back order no-text Back order number is

automatically generated

which is unique to each

form.

Success

Customer ID-text Customer ID will be loaded

from the invoice.

Success

Category - cmbBox Categorieswill be loaded onthe form load.

And when selected,

Product details of less

available products will be

displayed on the grid.

Success

Product List -dataGrid When the required item is

selected from the data

grid,Product Name will be

displayed on Product

txtBox .

Success

Add to cart-button Selected Product details

and Qty will be added to

the BackOrder list

dataGrid

Success

Reset-button Will emptying all data on

Back Order list dataGrid

Success

Save-button Back Order details will be

saved

Success

Table 4: Test Plan - Customer Back Order


36/84



7.5 Suppliers Menu

7.5.1 Screen Design

Supplier form allows the user to navigate for managing Suppliers where newSupplier registration and modification can be done to the existing Suppliers; Returngoods to the Suppliers and Delete the Suppliers who are currently have no businessdealing with the company.

7.5.2 Pseudo Code

STARTIF logged in User == Finance Manager THEN

DISABLE BtnReturnTo SupplierENDIFSuppliers button

Show Manage Supplier Form

Return To Supplier buttonShow Supplier Returns Form

Non Active Suppliers

Show Non active Supplier FormEND

Figure 10: Supplier Menu Screen


37/84



7.5.3 Test Plan

Test Case Description Expected Result/s Actual ResultSupplier

Menu

Manage Suppliers - btn Show Supplier

management form

Success

Returns to Suppliers btn Show Returns to

Suppliers form

Success

Non Active Suppliers -

btn

Show Non Active

Suppliers Form

Success

Table 5: Test Plan Supplier Menu


38/84



7.6 Manage Suppliers

7.6.1 Screen Design

Manage Supplier form allows the user to add new Suppliers to the companyby adding information of them and allows the user to update the Suppliers whoalready exist in the company.

Figure 11: Suppliers Screen


39/84



7.6.2 Pseudo Code

START

AUTOGENERATE UserName

Search buttonREAD supplier nameIF Supplier name == THEN

LOAD Supplier DataGridView with all Suppliers Supplier ID, Name, Contact person, Tel No, Address FROM Tbl Supplier

ELSE IF Supplier name == Existing supplier name THEN LOAD Supplier DataGridView with Supplier ID, Name,

Contact person, Tel No, Address FROM Supplier TableFILL the Supplier ID, Contact Person, Name, Tel No,

Address textboxesELSE

DISPLAY ErrorENDIF

New Check boxAUTOGENERATE Supplier IDENABLE btnSave

DISABLE btnUpdate

Save buttonREAD Supplier Name, Contact Person, TelNo, AddressIF Supplier Name == OR Contact person == OR TelNo ==

THENDISPLAY error

SAVETbl Suppier with Supplier ID, Name, Contact Person,TelNo,Address

Update buttonREAD Supplier ID, Name, Contact Person, TelNo, AddressUPDATETbl Suppier with Supplier ID, Name, Contact Person,

TelNo,Address

END


40/84



7.6.3 Test Plan


Supplier

Main

User - txtBox User ID will be autofilled at the form load.

Success

Search btn Will filter Supplier

details in the data grid tomapping Supplier Name.

If Name is not valid

msgBox will be display.

Success

New - chk Text boxes in thegroupbox will be cleared.Supplier ID will be autogenerated.btnSave EnabledbtnUpdate Disabled

Success

Supplier list dataGrid When a row is selected,Supplierdetails will bedisplayed on txtBoxes of the Group box.

Success

Save btn Supplier ID, Name,

Contact person, Tel No,

Address will add to

Supplier list dataGrid. Or

Display messagebox for

an error.

Success

Update btn Update the Supplier list

dataGridwith newSupplier ID, Name,Contact person, Tel No,Address in textboxes.

Success

Table 6: Test Plan - Suppliers


41/84


42/84



7.7.3 Test Plan


Supplier

Return

User - txtBox User ID will be autofilled at the form load.

Success

Check - btn If Supplier ID is mappedto an existing Supplier IDFill the Product listdataGrid with Productdetails about to return.

Success

Print - btn Report on the products inthe dataGrid will beshowed.

Success/ with some

exceptions

Table 7: Test Plan - Returns to Supplier


43/84



7.8 Non Active Suppliers

7.8.1 Screen Design

Here when the time duration is given a report can be printed with the detailsof non active suppliers of the system with their last GRN date and the informationabout the supplier for managerial purposes.

Figure 13: Non Active Suppliers Screen


44/84


45/84



7.9 Customers Menu

7.9.1 Screen Design

This takes the user to the customer related forms as well as the ability of taking reports such as debtor reports and non active customers.

Figure 14: Customer Menu Screen


46/84



7.9.2 Pseudo Code

START

IF logged in User Rank == Cashier THEN DISABLE btnManageCustomersDISABLE btnDebtor ReportDISABLE btnNonactive Customer

ENDIFIF logged in UserRank == Finance Manager THEN

DISABLE btnCustomerReturnsENDIFIF logged in UserRank == Stock Manager

DISABLE btnManageCustomersDISABLE btnDebtor ReportDISABLE btnNonactive CustomerDISABLE btnPay

ENDIF

7.9.3 Test Plan


Customer

Menu

Manage Customers - btn Show Customer

management form

Success

Customer Returns btn Show Customer returns

form

Success

Payment btn Show Payment form Success

Debtors Report btn Show Debtors Report Success

Non Active Customers -

btn

Show Non Active

Customers Form

Success

Table 9: Test Plan - Customer Menu


47/84



7.10 Manage Customers

7.10.1 Screen Design

Here customer s details can be added modified as well as be deleted. As wellthe credit limits can be updated and is visible for only for managers.

Figure 15: Customer Management Screen


48/84



7.10.2 Pseudo Code

START

AUTOGENERATE User Name

Search button READ Supplier NameIF Customername == THEN

LOAD Customers DataGrid with all Customers' Customer ID,Name, Contact person, Tel No, Address FROM Customer Table

ELSEIF Customer Name == Existing Customer Name in CustomerTable

LOAD Customers DataGrid with Customer ID, Name,Contact person, Tel No, Address FROM Customer Table

FILL the Customer ID, Contact Person, Name, Tel No,Address, Credit Limit, debt Amount, Date of last credit, date of last paymenttextboxes

ELSEDISPLAY Error

ENDIF

New Chech box

AUTOGENERATE Customer IDbtnSave Enable == TRUEbtnUpdate Enable == FALSEDebt Amount, Date of last credit, date of last payment textboxes

Enable = FALSE

Savebutton READ the Customer ID, Contact Person, Name, Tel No, Address,

Credit Limit

SAVETbl Customer with Customer ID, Contact Person, Name, TelNo, Address, Credit Limit

Update buttonREAD the Customer ID, Contact Person, Name, Tel No, Address,

Credit Limit, debt Amount, Date of last credit, date of last payment textboxesUPDATETbl Customer with Customer ID, Contact Person, Name,

Tel No, Address, Credit Limit, debt Amount, Date of last credit, date of last payment

END


49/84


50/84



7.11 Customer Returns


When customers return an item the relevant details are given here and areprinted so that they can produce the slip to the finance department. This data is alsoadded to the customer return database with relevant details

7.11.2 Pseudo Code

STARTAUTOGENERATE Slip No, Date, User Name

Availability buttonREAD Invoice IDIF Invoice ID == Existing Invoice ID THEN

AUTOFILL Date of Purchase, Customer IDLOAD cboStockCode with Stock codes in the Invoice ID

ELSE

DISPLAY ErrorENDIF

Figure 16: Customer Returns Screen


51/84



Add buttonREAD Product Code, CommentsUPDATETbl Stock with StockID, Damaged field = TRUE,

CommentsFILL Stock dataGrid with Stock code and comments

Reset buttonClear textboxes

Print buttonClear textboxesSAVE Slip ID, Return Date, Invoice ID, User ID in Tbl Customer-

Returns

END

7.11.3 Test Plan


Customer

Returns

Availability -btn Check for Invoice ID existence and

display a msgBox

Success

Customer ID-

text

Customer ID of the Invoice will be

displayed

Success

Stock Code-text Stock codes of the Invoice will be

loaded.

Success

Add-button The stock code and the comment

will be added to the data grid.

Success / with some

exceptions

Reset btn Data in the dataGrid will be emptied Success

Print-button Print view of the Return Slip will be

displayed.

Success/ with some

exceptions

Table 11: Test Plan - Customer Returns


52/84



7.12 Payments


When the debtors are about to pay the amount they owe this interface is madeuse of. This prints out and saves the details about the amount paid and the remainingamount.

7.12.2 Pseudo Code

STARTAUTOGENERATE Date, User Name

Check button READ Customer IDIF Customer ID == Existing Customer ID

FILL DateOfLastCredit, Debt Amount text boxesELSE

DISPLAY ErrorENDIF

ENDIF

Print buttonREAD Amount PayingDebt Amount = Debt Amount Amount PayingUPDATETbl Customer with Customer ID, Credits, Payment Date,

User ID

Figure 17: Customer Payments Screen


53/84



DISPLAY Payment Slip with Customer ID, Customer Name, CreditLimit, Amount Paid, Debt Amount, User ID


END

7.12.3 Test Plan


Customer

Payments

Check-button Check for Customer ID availability Success

Debt amount-

text

The current debt amount of the

customer will be loaded in to the

text box.

Success

Reset-button Resets all the data in the form Success

Save-button Payment details will be balanced

and remaining debt will be shown.

Success

Table 12: Test Plan - Customer Payments


54/84



7.13 Non Active Customers


Here when the time duration is given a report can be printed with the details

of non active customers of the system with their debt amount and the information

about the customer for managerial purposes.

Figure 18: Non Active Customers Screen


55/84



7.13.2 Pseudo Code

START

AUTO GENERATE User NameFILL CustomerdataGrid with Customer ID, Name, Contact Person, Last

Credit Date, last payment Date of the Customer whose Last Credit Date < Selecteddue date

IF Row is selected THEN FILL textboxes in the group box with Customer Details of the

selected rowENDIF

END

7.13.3 Test Plan


Non ActiveCustomers

dataGrid When a row is

selected, data in thatrow will bedisplayed

on txtBoxes

Success

Check btn Customers who

haven t done

transactions after the

selected date will be

loaded to the grid view

Success

Table 13: Test Plan N.A. Customers


56/84



7.14 User Account Menu


Allows the user to create users, modify the user details and so on and isvisible for managers.

7.14.2 Pseudo Code

STARTIF logged in User != CEO THEN

DISABLE btnNewUserELSE

ENABLE btnNewUserENDIFIF btnNewUserClicked THEN

Show New User FormENDIFIF btnModifyUserClicked THEN

Show Modify/Delete User FormENDIF

END

Figure 19: User Accounts Menu


57/84



7.14.3 Test Plan


User

Accounts

NewUser - btn Show new User Form Success

Modify\DeleteUser btn Show Modify\Delete

User Form

Success

Table 14: Test Plan - User Accounts Menu

7.15 New User


CEO could create new users with rankings in order to allow access to theSLTC system.

7.15.2 Pseudo Code

STARTLOAD cboRank with Cashier, Finance Manager, Stock Manager,

CEO

Create buttonREAD User NameREAD Password

Figure 20: New User Screen


58/84



READ Confirm PasswordIF User Name == Existing User Name THEN

DISPLAY ErrorELSEIF Password != Confirm Password OR Rank == THEN

DISPLAY ErrorELSE

SAVE User Name, Rank, Password in Tbl UserENDIF


END

7.15.3 Test Plan


New User Rank - cbo Cashier, Finance

Manager, Stock

Manager, and CEO

will be displayed.

Success

Create btn If password and confirm

password is the same,

display a message box

about successful creation

else display a message

box about an error.

Success

Table 15: Test Plan - New User


59/84



7.16 Modify / Delete User


Existing user accounts can be modified and only CEO could modify ranksand delete any account in order to suspend the access to the system.

7.16.2 Pseudo Code

START

IF current LoggedUser != CEO THEN

LOAD cboUserName with currentLoggedUser Name FROM UserTable

LOAD cboRank with currentLoggedUser Rank cboRank = disabled

Modify buttonREAD User Name, Rank READ Password, Confirm PasswordREAD New Password, Confirm PasswordIF Password != Confirm Password OR New Password !=

Confirm New THEN DISPLAY Message Box

ELSE

UPDATETbl User with User Name, Rank, PasswordENDIF

Figure 21: Modify/Delete User Screen


60/84



Deletebutton = disabled

ELSE

LOAD cboUserName with existing User Names FROM User TableLOAD cboRank with Cashier, Finance Manager, Stock Manager,

CEO Modify button

READ User Name, Rank READ Password, Confirm PasswordREAD New Password, Confirm PasswordIF Password != Confirm Password OR New Password != Confirm

New THEN DISPLAY Messege Box

ELSEUPDATETbl User with User Name, Rank, Password

ENDIF

Deletebutton DELETE User FROMTbl User

END

7.16.3 Test Plan


Modify\

Delete

User

Rank - cbo Cashier, Finance Manager,

Stock Manager, and CEO

will be displayed.

Success

User Name - cbo Fill with User names at the form

load.

Success

Modify - btn If existing password and confirmpassword equals and newpassword and existing passwordequals then display a msgBoxabout successful modificationElse Display error msg.

Success

Delete - btn If existing password and confirmpassword equals Display asuccessful account deletion.

Success

Table 16: Test Plan - Modify/Delete User


61/84



7.17 Stock Menu


7.17.2 Pseudo Code

STARTIF logged in user = Finance manager THEN

DISABLE btnGRNDISABLE btnPOGDISABLE btnManagecategoryDISABLE btnManageproduct

ENDIFIF logged in user = Cashier THEN

DISABLE btnGRNDISABLE btnPOGDISABLE btnManagecategoryDISABLE btnManageproduct

ENDIF

Good Receive Note buttonShow Good Receive Note Form

Purchase Order Generation buttonShow Purchase Order Generation Form

Figure 22: Stock Menu Screen


62/84



MnageProoducts buttonShow Manage Products Form

Manage Category buttonShow Purchase Order Generation Form

END

7.17.3 Test Plan


Stock Manage

Products-btn

Takes to the Manage Products

interface

Success

Good Receive

note-btn

Takes to the GRN interface Success

ManageCategories - btn

Takes to the Category managementinterface

Success

POG - btn Takes to the POG interface Success

Price List btn Load Price List Success

Table 17: Test Plan - Stock Menu


63/84



7.18 Good Receive Note


When a stock comes to the company a GRN is created with the relevantdetails and the profit percentages. These can be saved on the stock file oncecompleted.

7.18.2 Pseudo Code

STARTAUTOGENERATE Date, User IDLOAD cboCategory with Category names at the form load

Check buttonREAD Supplier IDIF Supplier ID != existing Supplier ID THEN

DISPLAY ErrorENDIF

IF Category is Selected THEN LOAD cboProduct with Product names within the selected category

ENDIFIF Product is Selected THEN

AUTOFILL Profit textboxENDIF

Figure 23: Good Receive Note Screen


64/84



Save buttonUPDATE Tbl Supplier with last GRN dateReceived quantity = Existing received quantity + GRN quantityUPDATE Tbl Products table with Received quantitySAVE Tbl Stocks with Damage = FALSE AND Sold = FALSE,Product IDClose the Form

END

7.18.3 Test Plan


Good

Receive

Notes

User txtBox User ID will be auto

filled at the form load.

Success

Check btn If supplier ID does not

exists Display MsgBox.

Success

Category - cbo Category names will beloaded at the form load.

When a category isselected Product cbo willbe loaded with Productnames.

Success

Save btn Close the form. Success

Table 18: Test Plan - GRN


65/84



7.19 Purchase Order Generation


Figure 24: P.O. Generation Screen

When the reorder level reaches its level a POG is generated by the managerto be given to the supplier to deliver the stock.

7.19.2 Pseudo Code

STARTAUTOGENERATE Date

Check buttonREAD Supplier IDIF Supplier ID != existing Supplier ID THEN

DISPLAY ErrorELSE

ADD Supplier ID, Name, contact person to the SupplierDataGrid


66/84



AUTOFILL Supplier name textboxENDIFIF selected Product s reorder quantity > received quantity OR

backorder quantity > 0 THENFILL Product dataGrid with Product ID, Reorder quantity and

back order quantity of the selected supplierENDIF

Reset buttonClear all the text boxesClear supplier dataGrid

Print buttonSHOW Purchase order Generation report

END

7.19.3 Test Plan


Purchase

Order

Generation

Search - btn Filtering the Supplier

details on the Supplier

list dataGrid to match

Supplier Name txtBox

Success

Supplier list dataGrid When a row is selected,

data in that row will be

displayed on Supplier

txtBox

And

Load Product list

dataGrid with, to be

Purchase list which are

matching to that Supplier

Success

Reset btn Reset the filtering of the

Supplier list dataGrid

Success

Print btn Print Suppliers Purchase

Order

Success

Table 19: Test Plan - P.O. Generation


67/84


68/84



7.20.2 Pseudo Code

START

LOAD cboCategory with Category Names in Category TableIF Ctegory is Selected THEN

FILL Stocks DataGridView with Product information of selectedCategory

ENDIFIF Product Row is Selected THEN

FILL Product ID, Product Name, Reorder Point, Unit Price, ReorderQty, Unit Price, Profit, Reorder Date, Last Reviewed Date textboxes

ENDIFNew Check box

btnUpdate Enable = FALSEbtnSave Enable = TRUEtxtLastRecievedDate Enable = FALSEClear textboxes

Save buttonAUTOGENERATE Product IDREAD Product ID, Product Name, Reorder Point, Unit Price, Reorder

Qty, Unit Price, Profit, Reorder DateUnit Price = UnitPrice * (1 + Profit)

SAVE Product ID, Stock Name, Reorder Point, Unit Price, ReorderQty, Unit Price, Profit, Reorder Date in Tbl Product

Update buttonREAD Product ID, Product Name, Reorder Point, Unit Price, Reorder

Qty, Unit Price, Profit, Reorder Date, Last Received DateUnit Price = UnitPrice * (1 + Profit)SAVE Product ID, Product Name, Reorder Point, Unit Price, Reorder

Qty, Unit Price, Profit, Reorder Date, Last Received Date in Tbl ProductEND


69/84



7.20.3 Test Plan


ProductManagement

Category - chk Load with Categorynames at the form load.

Success

Product list - dataGrid When a row is selected,Product details will bedisplayed on txtBoxes inthe Group box.

Success

New - chk Text boxes in thegroupbox will be cleared.Product ID will be autogenerated.btnSave EnabledbtnUpdate Disabled

Success

Save btn Product ID, Name,Reorder point, Unit price,Profit, Reorder date andlast received date willadd to Product list

dataGrid. Or Displaymessagebox for an error.

Success

Update btn Update the Product listdataGrid with newProduct ID, Name,Reorder point, Unit price,Profit, Reorder date andlast received date intextboxes.

Success

Table 20: Test Plan - Product Management


70/84



7.21 Category Management


In this form, the categories can be managed by the user by adding newcategories and modifying the once which are already available in the database.

7.21.2 Pseudo Code

STARTLOAD CategoryDataGridView with Existing Category IDs, Category NamesIF Category is Selected THEN

FILL Category ID, Name textboxesENDIFNew Check box

Clear textboxesBtnSave Enable = TRUEbtnUpdate Enable = FALSEbtnDelete Enable = FALSE

Save buttonAUTOGENERATE Category ID

Figure 26: Category Management Screen


71/84



READ Category NameIF Category Name == OR Category Name == Existing Category

THEN Display Error

ELSESAVE Category ID, Category Name in Category Table

ENDIFUpdate button

READ Category ID, Category NameUPDATETbl Category with Category ID, Category Name

Delete buttonREAD Category IDDELETE selected Category FROM Tbl Category

END

7.21.3 Test Plan


Category

Management

Category dataGrid When a row is selectedfrom the list, data in thatrow will be displayed ontxtBoxes to edit.

Success

New chkBox txtBoxes will be emptiedand an auto generatedCategory ID will bedisplayed.

Success

Save btn New Category will be

saved or/and amsgBox

will display.

Success

Update btn Edited fields of theselected Category will beupdated and/or a msgBoxwill be displayed

Success

Delete btn Selected Category will bedeleted and/or amsgBoxwill appear.

Success

Table 21: Test Plan - Category Management


72/84



8. Report Designs

8.1 Invoice

Invoice report will display the records of currently generated invoice in-orderto provide the customer with a record of transactions.

Figure 27: Reports - Invoice


73/84



8.2 Debtors

Debtors report will display all the details of current debtors of the company.

Figure 28: Reports - Debtors


74/84



8.3 Price List

Figure 29: Reports - Price List


75/84



9. Gantt chart


76/84


77/84



Test Plan 100%

Non Active Supplier

Screen 100%

Pseudo 100%

Test Plan 100%

o Customers 100%

Manage Customers

Screen 100%

Pseudo 100%

Test Plan 100%

Payments

Screen 100%

Pseudo 100%

Test Plan 100%

Customer Returns

Screen 100%

Pseudo 100%

Test Plan 100%

Non Activecustomers

Screen 100%

Pseudo 100%

Test Plan 100%

o User Accounts 100%

New User 100%

Modify User 100%

o Stock 100%

GRN


78/84



Screen 100%

Pseudo 100%

Test Plan 100%

POG

Screen 100%

Pseudo 100%

Test Plan 100%

Manage products

Screen 100%

Pseudo 100%

Test Plan 100%

Manage Categories

Screen 100%

Pseudo 100%

Test Plan 100%

Reports

Invoice

o Invoice Reports 100%

Suppliers

o Non active supplier 100%

o POG 100%

o Return to supplier 100%

Customers

o Customer payment 100%

o Customer returns 100%

o Non active customers 100%

o Debtors report 100%


79/84



Stock

o Price List 100%

o Sales Report 100%

Assumptions/Business Rules 100%

Gantt Chart 100%

Limitation 100%

Work load matrix 40% 40% 20%

Programming

o Invoice 100%

o Back Order 100%

o Customer Forms 100%

o Supplier Forms 100%

o User Accounts 100%

o Stock Forms 100%

Crystal Report Programming

o Invoice 100%

o POG 100%

o Debtors 100%

o Price List 100%


80/84



11. Business Rules

Discounts are given to the Customer based on the total amount of the invoice.

The criteria for discount allocation is as follows,

Criteria Discount

Total amount > Rs.100 000 20%

Rs.100 000 > Total amount > Rs.50 000 10%

Rs.50 000 > Total amount > Rs.30 000 5%

Total amount < Rs.30 000 None

Table 22: Discount Criteria

Customers are considered as suppliers to be deleted if they have not dealt

with the company for more than six months, except for extenuating

circumstances.

Suppliers are considered as suppliers to be deleted if they have not dealt with

the company for more than six months and company keeps no products

delivered from that Supplier.

Generate Purchase Order for the products of which, on hand quantity is less

than reorder point.


81/84



12. Assumptions

SLTC only deals with Wholesale customers. The organization does not deal

with Retail customers.

The company does not keep a base stock for any particular product. Thestocks are reordered based on the reorder point and on hand quantity.

When a customer returns a stock if the customer is a credit holder the credit

balance is adjusted while the finance manager settles the money for products

bought on cash.

The dealings with the customers and suppliers who are considered as deleted

are done by the finance department.

If a customer exceeds his credit limits he needs to pay the amount overexceeded amount by cash.

If a new stock of an existing product receives with a new price first the stocks

with the earlier price will be sold to the Customers.

The users of the system are Cashier, Finance Manager, and Stock Manager

and CEO.

The responsibilities of user are,

Cashier -

Invoice Generation

Back order Generation

Return damaged goods to Suppliers

Accept damaged goods by the Customers

Carryout credit holders payments

Stock Manager

Manage Stocks and Departments

Manage Suppliers

Purchase order generation

Registering Good Receive Notes


82/84



Finance Manager

Manage Customers

Handle Returns to the Supplier

Settle payments for the Customers on returned goods which arepurchased on cash

CEO

Manage user accounts

Have the authority to do all the tasks within the system

13. Limitations

Company won t keep a track of every payment done by the customers, onlythe last payment date is saved

Supplier payments are not dealt by the system When the goods of the back orders receive the Customers are not informed by

the system.

System does not deal with any kind of accountancy areas.


83/84



14. Conclusion

As stated in the introduction, the main objective of this project was to analyze

the requirements of the SLTC and Design a system to address those requirements

found in the analysis phase. When gathering