Final SLTC

SLTC Retail System
Subject Title System Name Group Member
: : :
Software Development Project AAPP006-3-2-SDP SLTC Retail System Kasun Fernando AshanMaduranga - CB003947 - CB003717
LakshikaTennakoon - CB003961 Intake Submitted to Hand out Date Hand in Date Word Count : : : : : DF1061-ICT Ms. Oshini Jayatunga 23rd February 2011 13th May 2011
SLTC System Development Project
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. 5. ER Diagrams ...................................................................................................... 19 Data Flow Diagrams .......................................................................................... 21 5.1 Context Diagram .............................................................................................. 21 5.2 Level 0 Diagram ............................................................................................... 22 6. 7. Hierarchy Chart .................................................................................................. 23 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 Asia Pacific Institute of Information Technology 2
SLTC System Development Project 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
Asia Pacific Institute of Information Technology
SLTC System Development Project 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
SLTC System Development Project 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. 10. 11. 12. 13. 14. Gantt chart .......................................................................................................... 75 Workload Matrix ............................................................................................. 76 Business Rules ................................................................................................ 80 Assumptions .................................................................................................... 81 Limitations ...................................................................................................... 82 Conclusion ...................................................................................................... 83
Appendix .................................................................................................................... 84 Weekly Meeting Reports........................................................................................ 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 Asia Pacific Institute of Information Technology 6
SLTC System Development Project Figure 26: Category Management Screen .................................................................. 70 Figure 27: Reports - Invoice ...................................................................................... 72 Figure 28: Reports - Debtors ...................................................................................... 73 Figure 29: Reports - Price List ................................................................................... 74
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
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 the communication. 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, Products price list report, Re-order report, Supplier reports, Sales report, Customer reports, POG report Constraints System will be offering the above mentioned modules only since this is an inventory system all the components required for inventory Asia Pacific Institute of Information Technology 9
SLTC System Development Project 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.
10
Scope
The major scope of the system generated by the A+ Solutionz to Sri Lanka Trading 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 Suppliers Manage Suppliers Add New Supplier Update Existing Supplier Deleting Existing Supplier Add New Categories Update Existing Categories
Manage Categories Add New Departments Update Existing Departments Deleting Existing Departments
Good Received Note Add New Stocks
Return Damaged goods to Supplier
11
SLTC System Development Project Customers Manage Customers Invoice Maintain Sales on Credit and Cash Creating back orders for goods which are not available in the company 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
2.2 Non Functional Requirements

User friendliness Accessibility Maintainability Reliability Response Time Robustness Security of Information Stability
12
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 laptop device and a printer to print bills and reports generated by the system as these technology is not available within the organization currently. Furthermore user training needs to be carried out in order to plunder the highest advantages of the system. 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 a clear picture of the current manual system. 3.2.1 Performance Current manual system consumes a great amount of time in the Sales process as the Total amount and the discounts should calculate manually. Furthermore when selling goods on credit basis consumes furthermore time as the credit limits and debt amount need to be calculated manually for every transaction. When the Good Receive Notes arrive all the information needs to be kept manually whereas the unit price need to be calculated in the same manner based on the profit approved by the supplier. Moreover when Customers are purchasing goods the stock keeper needs manually go through the existing stocks in order to identify whether the request can be fulfilled. Overall throughput is low as registering processes consumes a lot of time.
13
SLTC System Development Project 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 the company does not possess satisfactory information on the goods purchased by the customers. The current system does not provide timely, pertinent information and as the information is not properly formatted the accuracy is low. 3.2.3 Economy Current system results in increasing the stationary cost as all the transactions between the suppliers are need to be maintained manually. Moreover by moving on to the new system intangible benefits such as Customer satisfaction can be gained whereas the disadvantage of frauds by the Customers or Cashier can be eliminated. 3.2.4 Control Providing security to the data is essential but this is not fulfilled by the existing manual system hence providing the appropriate security to the data by giving hierarchical approach which ensures that the users of the system are exposed to the information which is relaxant to them. 3.2.5 Efficiency One of the major disadvantages of the existing system in Sri Lanka Trading Company is the vast response time it consumes in generating Invoice. By introducing the new system Transaction time can be reduced by a huge level. The man power is also not satisfactorily utilized. 3.2.6 Services As the customer satisfaction is not up to recommended standards as the issues with credit limits and return goods are frequent occurrence. Therefore by maintaining customer records the new system eliminates those issues as a certain credit limit is assigned to all the customers who are registered within the organization and these information 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 14
3.3 Economic Feasibility

3.3.1 Cost Benefit Analysis Costs Estimated Developmental Costs of three months
Cost Type Personal Salary Project Manager System Analyst Programmer / Developer Quantity Assurance System Architect and GUI Designer Training expenses Initial User Training Hardware purchase Personal Computer Printer Software Purchase MS Visual Studio MS Database Management Tool Software License 11 500.00 10 000.00 6 000.00 25 000.00 5 000.00 10 000.00 240 000.00 225 000.00 180 000.00 120 000.00 150 000.00 Cost (Rs.)
Total Developmental Costs
982 500.00
15
SLTC System Development Project Estimated Annual Operational Costs

Cost Type Personal Salary Cashier Stock Manager System Maintenance Ongoing Training System Maintenance and Modifications Other Expenses Printing Papers, Cartridges and Stationary Electricity Bill Total Operational Costs 100 000.00 60 000.00 770 000.00 10 000.00 60 000.00 180 000.00 360 000.00 Cost (Rs.)
Benefits Intangible Benefits Higher employee morale Customer satisfaction Supplier satisfaction Less time consumption in Stock maintenance
16
SLTC System Development Project Tangible Benefits

Benefit Type Cost (Rs.)
Error Reduction and Enhanced Accuracy Improved Stock Management and Control Increased Sales Opportunities Opening New Markets Accelerated Speed of Transactions Total tangible Benefits
250 000.00 300 000.00 400 000.00 80 000.00 210 000.00 1 240 000.00
Payback Analysis
Year
Costs
Cumulative Costs 982 500.00
Benefits
Cumulative Benefits -
Year 0
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
17
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%
18
4. ER Diagrams
Figure 1: ER Diagram A
19
Figure 2: ER Diagram B
20
5. Data Flow Diagrams

5.1 Context Diagram
Figure 3: Context Diagram
21
5.2 Level 0 Diagram
Figure 4: Level 0 Diagram
22
6. Hierarchy Chart
Figure 5: Hierarchy Chart
23
7. System Designs
7.1 Login
7.1.1 Screen Design
Figure 6: Login Screen
7.1.2 Pseudo Code
START Login button READ User name READ Password IF User name == OR Password == THEN DISPLAY Error ELSEIF User name == existing Username AND Password == relevant Password DISPLAY Success UPDATE TblUser with time ELSE DISPLAY Error ENDIF Cancel button Close the Form END
24
SLTC System Development Project 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.

Table 1: Test Plan - Login
Success
25
7.2 Main Menu

7.2.1 Screen Design
Figure 7: Main Menu Screen
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 button is enabled only to managers. A menu strip is available for quick access to other forms. 7.2.2 Pseudo Code
START IF logged in User Rank== Cashier THEN DISABLE btnSupplier DISABLE btnStock ENDIF Invoice button Asia Pacific Institute of Information Technology 26
SLTC System Development Project Show Invoice Form Supplier button Show Supplier Form Customer button Show Customer Form User Account button Show User Accounts Form Stock button Show Stock Form Log out button Close Form END 7.2.3 Test Plan
Test Case Main
Test Description Invoice-button Suppliers-button
Expected Result Takes to the Invoice. Takes to the Supplier Menu.
Actual Result Success Success
Customers-button
Takes to the Customer Menu.
Success
User Accounts-button
Takes to the User Account menu
Success
Stocks-button Log out
Takes to the Stocks Menu Log out from the system

Table 2: Test Plan - Main Menu
Success Success
27
7.3 Invoice
7.3.1 Screen Design
Figure 8: Invoice Screen
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.
28
SLTC System Development Project 7.3.2 Pseudo Code
START AUTOGENARATE Invoice No, Date, User ID LOADcboCategory with Category names Total quantity = 0 Total amount = 0 Net amount = 0 Search button READ Product Name IF selected item in cboCategory = OR Product Name = THEN LOAD Product List dataGridwith Product ID, Product Names, Available amount, Price ELSE IF Product Name == Existing Product Name THEN Available amount = COUNT of products WHERE Product ID == Selected Products ID AND Sold field == FALSE AND Damage == FALSE from TblStock LOAD Product List dataGrid with Product ID, Product Names, Available amount, Price ENDIF IF Row is selected from the DatagridTHEN AUTOFILL Product Name textbox ENDIF Add To Cart button READ Quantity IF Quantity > Available Amount THEN DISPLAY Needs to create back order ELSE UPDATE Invoice Detail Table with Invoice ID, Stock ID, ProductID, Quantity UPDATETblStockwith Sold field = TRUE FILL Invoice Detail DataGrid with Product ID, Name, Quantity, Price Total quantity = Total quantity + Quantity Total 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 Asia Pacific Institute of Information Technology 29
SLTC System Development Project Discount = 5% ELSE Discount = 0% ENDIF Net Amount = Total Amount (1-(Discount/100)) ENDIF Availability button READ Customer ID IF Customer ID == Existing Customer ID THEN AUTO FILL Credit Limit , Available Credit ELSE DISPLAY Error ENDIF Credit Radio button IF Available Credit > Total amount THEN AUTOFILL Credit textbox with Total amount Available credit = Available credit Total amount ELSE AUTOFILL Credit textbox with available Credit Cash amount = Total amount available Credit amount DISPLAY Cash amount Available credit = 0 ENDIF Cash Radio button AUTO FILL Credit textbox with Total amount Back Order button Show Back order form Print button UPDATETblInvoice with Date, Invoice ID, Total Amount, Discount, Customer ID UPDATE TblCustomer with Available Credits, Credit Date Show Invoice Report END
30
Test Case
Description Invoice No - txtBox
Expected Result/s New Invoice number will be auto generated at the form load. Category names will be loaded at the form load. And when a category is selected, Product List data grid will be loaded.
Actual Result Success
Invoice Category cmbBox
Success
Search btn
Will filter Product list in the data grid to matching Product Name. If Name is not valid, msgBox will be display.
Success
Product List dataGrid
When a row is selected, Product Name will be displayed on Product Name txtBox Product details and Qty will be added to the Invoice List dataGrid and Total Qty, Total Amount, Discount, Net Amount txtBoxes will be updated. Or, amsgBox will be displayed.
Success
Add to Cart btn
Success
Reset btn
Will empty all data in Invoice List dataGrid.
Success
31

Availability btn Will check the existence of the Customer ID on ID txtBox. And display Customers Credit Limit and Availably Credit on txtBoxes. Or, amsgBox will be displayed. Payments Credit chkBox Payments Cash chkBox Back Order btn Success
Will make Credit txtBox editable. Will make Cash txtBox editable. Opening Back Order Form Show invoice to be printed.
Success
Success
Success
Print
Success
Table 3: Test Plan - Invoice
32
7.4 Customer Back Order

7.4.1 Screen Design
Figure 9: Customer Back Order Screen
Customer back order is created when the stock is out of order. The items are added just like it was in invoice form and is saved with the quantity required so that when the stock arrives the customer could be contacted.
33
START AUTOGENERATE Date, User Name, Customer ID LOADcboCategory with Category names IF Product Name == OR selected Item in cboCategory == THEN LOAD Product List dataGrid with Product ID, Product Names, Available amount, Price ELSE IF Product Name == Existing Product Name THEN Available amount = COUNT of products WHERE Product ID == Selected Products ID AND Sold field == FALSE from Stock Table FILL Product List dataGrid with Product ID, Product Names, Available amount, Price ENDIF IF Row is selected from the datagridTHEN AUTOFILL Product Name textbox ENDIF Add to Cart button READ Quantity Back order quantity = quantity SAVE Quantity, ProductID in TblBackorderdetails UPDATE Backorder quantity, Product ID in TblProducts ADDProductID, Product Name, Back order quantity in Back order dataGrid Reset button Clear text boxes Clear Data Grid views Save button READ Due Date SAVE Date, Due Date, CustomerID, UserID inTblBackOrder END
34
Test Case Customer back order
Test Description Back order no-text
Expected Result Back order number is automatically generated which is unique to each form.
Customer ID-text
Customer ID will be loaded from the invoice.
Success
Category - cmbBox
Categorieswill be loaded on the 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
35
7.5 Suppliers Menu

7.5.1 Screen Design
Figure 10: Supplier Menu Screen
Supplier form allows the user to navigate for managing Suppliers where new Supplier registration and modification can be done to the existing Suppliers; Return goods to the Suppliers and Delete the Suppliers who are currently have no business dealing with the company. 7.5.2 Pseudo Code START IF logged in User == Finance Manager THEN DISABLE BtnReturnTo Supplier ENDIF Suppliers button Show Manage Supplier Form Return To Supplier button Show Supplier Returns Form Non Active Suppliers Show Non active Supplier Form END Asia Pacific Institute of Information Technology 36
7.5.3 Test Plan
Test Case Supplier Menu
Description Manage Suppliers - btn
Expected Result/s Show Supplier management form
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
37
7.6 Manage Suppliers

7.6.1 Screen Design
Figure 11: Suppliers Screen
Manage Supplier form allows the user to add new Suppliers to the company by adding information of them and allows the user to update the Suppliers who already exist in the company.
38
START AUTOGENERATEUserName Search button READ supplier name IF Supplier name == THEN LOAD Supplier DataGridView with all Suppliers Supplier ID, Name, Contact person, Tel No, Address FROM TblSupplier ELSE IF Supplier name == Existing supplier name THEN LOAD Supplier DataGridView with Supplier ID, Name, Contact person, Tel No, Address FROM Supplier Table FILL the Supplier ID, Contact Person, Name, Tel No, Address textboxes ELSE DISPLAY Error ENDIF New Check box AUTOGENERATE Supplier ID ENABLE btnSave DISABLE btnUpdate Save button READ Supplier Name, Contact Person, TelNo, Address IF Supplier Name == OR Contact person == OR TelNo == THEN DISPLAY error SAVETblSuppier with Supplier ID, Name, Contact Person, TelNo,Address Update button READ Supplier ID, Name, Contact Person, TelNo, Address UPDATETblSuppier with Supplier ID, Name, Contact Person, TelNo,Address END
39
Test Case
Description User - txtBox
Expected Result/s User ID will be auto filled at the form load. Will filter Supplier details in the data grid to mapping Supplier Name. If Name is not valid msgBox will be display.
Supplier Main Search btn
Success
New - chk
Text boxes in the groupbox will be cleared. Supplier ID will be auto generated. btnSave Enabled btnUpdate Disabled When a row is selected, Supplierdetails will be displayed on txtBoxes of the Group box. Supplier ID, Name, Contact person, Tel No, Address will add to Supplier list dataGrid. Or Display messagebox for an error.
Success
Supplier list dataGrid
Success
Save btn
Success
Update btn
Update the Supplier list dataGridwith new Supplier ID, Name, Contact person, Tel No, Address in textboxes.
Success
Table 6: Test Plan - Suppliers
40
7.7 Returns to Suppliers

7.7.1 Screen Design
Figure 12: Returns to Supplier Screen
In here the return items can be printed. For this information such as the supplier ID, product name and the number of quantities returning should be given to be saved in the supplier return table and to print out the report.
7.7.2 Pseudo Code
START AUTOGENERATE Slip No, Date, User ID Check button IF Supplier ID == Existing supplier ID THEN LOAD Supplier DataGridView with Product ID, Product Name, Total Damage Quantity FROM TblStock, TblProducts ELSE DISPLAY Error ENDIF Print button Show Supplier Return Report END Asia Pacific Institute of Information Technology 41
Test Case
Description User - txtBox
Expected Result/s User ID will be auto filled at the form load.
Supplier Return Check - btn
Print - btn
If Supplier ID is mapped to an existing Supplier ID Fill the Product list dataGrid with Product details about to return. Report on the products in the dataGrid will be showed.
Table 7: Test Plan - Returns to Supplier
Success
Success/ with some exceptions
42
7.8 Non Active Suppliers

7.8.1 Screen Design
Figure 13: Non Active Suppliers Screen
Here when the time duration is given a report can be printed with the details of non active suppliers of the system with their last GRN date and the information about the supplier for managerial purposes.
43
START AUTOGENERATE User Name FILL Supplier dataGrid with Supplier ID, Name, Contact Person, Address, TelNo, Last GRN Date of the suppliers whose Last GRN Date < Selected Due Date IF Row is selected THEN FILL textboxes in the group box with Supplier Details of the selected row ENDIF Delete button DELETE Selected Supplier FROMTblSupplier SAVE Selected Supplier to TblOldSupplier END
7.8.3 Test Plan
Test Case Non Active Suppliers
Test Description Check -btn
Expected Result Suppliers whose last GRN date is less than the selected date will be loaded to Grid View
txtUser - txtBox Delete - btn
Current User name will loaded Delete selected Supplier
Success Success
Table 8: Test Plan - N.A. Suppliers
44
7.9 Customers Menu

7.9.1 Screen Design
Figure 14: Customer Menu Screen
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.
45
START IF logged in User Rank == Cashier THEN DISABLE btnManageCustomers DISABLE btnDebtor Report DISABLE btnNonactive Customer ENDIF IF logged in UserRank == Finance Manager THEN DISABLE btnCustomerReturns ENDIF IF logged in UserRank == Stock Manager DISABLE btnManageCustomers DISABLE btnDebtor Report DISABLE btnNonactive Customer DISABLE btnPay ENDIF
7.9.3 Test Plan
Test Case Customer Menu
Description Manage Customers - btn
Expected Result/s Show Customer management form
Customer Returns btn Payment btn Debtors Report btn Non Active Customers btn
Show Customer returns form Show Payment form Show Debtors Report Show Non Active Customers Form
Success
Success Success Success
Table 9: Test Plan - Customer Menu
46
7.10 Manage Customers

7.10.1 Screen Design
Figure 15: Customer Management Screen
Here customers details can be added modified as well as be deleted. As well the credit limits can be updated and is visible for only for managers.
47
START AUTOGENERATE User Name Search button READ Supplier Name IF 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 Customer Table 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 payment textboxes ELSE DISPLAY Error ENDIF New Chech box AUTOGENERATE Customer ID btnSave Enable == TRUE btnUpdate Enable == FALSE Debt 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 SAVETblCustomer with Customer ID, Contact Person, Name, Tel No, Address, Credit Limit Update button READ the Customer ID, Contact Person, Name, Tel No, Address, Credit Limit, debt Amount, Date of last credit, date of last payment textboxes UPDATETblCustomer with Customer ID, Contact Person, Name, Tel No, Address, Credit Limit, debt Amount, Date of last credit, date of last payment END
48
7.10.3 Test Plan
Test Case Customer Management
Description Search btn
Expected Result/s Search matching Customer Name details to Name- txtBox and display on the dataGrid
dataGrid
Customer details of selected row, will be displayed on txtBoxes for updating.
Success
New chkBox
Clear all text fields, auto generated the Customer ID, enabling Save-btn and disabling Update-btn
Success
Save btn
New Customer details will be saved and/or display a msgBox
Success
Update - btn
Updated Customer details will be saved and/or display a msgBox
Success
Table 10: Test Plan - Customer Management
49
7.11 Customer Returns

Figure 16: Customer Returns Screen
When customers return an item the relevant details are given here and are printed so that they can produce the slip to the finance department. This data is also added to the customer return database with relevant details
7.11.2 Pseudo Code
START AUTOGENERATE Slip No, Date, User Name Availability button READ Invoice ID IF Invoice ID == Existing Invoice ID THEN AUTOFILL Date of Purchase, Customer ID LOADcboStockCode with Stock codes in the Invoice ID ELSE DISPLAY Error ENDIF Asia Pacific Institute of Information Technology 50
Add button READ Product Code, Comments UPDATETblStock with StockID, Damaged field = TRUE, Comments FILL Stock dataGrid with Stock code and comments Reset button Clear textboxes Print button Clear textboxes SAVE Slip ID, Return Date, Invoice ID, User ID in TblCustomerReturns END
7.11.3 Test Plan
Test Case Customer Returns
Test Description Availability -btn
Expected Result Check for Invoice ID existence and display a msgBox
Customer IDtext Stock Code-text
Customer ID of the Invoice will be displayed Stock codes of the Invoice will be loaded.
Success
Success
Add-button
The stock code and the comment will be added to the data grid.
Success / with some exceptions
Reset btn Print-button
Data in the dataGrid will be emptied Success Print view of the Return Slip will be displayed.
Table 11: Test Plan - Customer Returns
Success/ with some exceptions
51
7.12 Payments
Figure 17: Customer Payments Screen
When the debtors are about to pay the amount they owe this interface is made use of. This prints out and saves the details about the amount paid and the remaining amount.
7.12.2 Pseudo Code START AUTOGENERATE Date, User Name Check button READ Customer ID IF Customer ID == Existing Customer ID FILLDateOfLastCredit, Debt Amount text boxes ELSE DISPLAY Error ENDIF ENDIF Print button READ Amount Paying Debt Amount = Debt Amount Amount Paying UPDATETblCustomer with Customer ID, Credits, Payment Date, User ID Asia Pacific Institute of Information Technology 52
SLTC System Development Project DISPLAY Payment Slip with Customer ID, Customer Name, Credit Limit, Amount Paid, Debt Amount, User ID Reset button Clear textboxes END
7.12.3 Test Plan
Test Case Customer Payments
Test Description Check-button
Expected Result Check for Customer ID availability
Debt amounttext
The current debt amount of the customer will be loaded in to the text box.
Success
Reset-button Save-button
Resets all the data in the form Payment details will be balanced and remaining debt will be shown.
Success Success
Table 12: Test Plan - Customer Payments
53
7.13 Non Active Customers

Figure 18: Non Active Customers Screen
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.
54
START AUTO GENERATE User Name FILL CustomerdataGrid with Customer ID, Name, Contact Person, Last Credit Date, last payment Date of the Customer whose Last Credit Date < Selected due date IF Row is selected THEN FILL textboxes in the group box with Customer Details of the selected row ENDIF END
7.13.3 Test Plan
Test Case
Description dataGrid
Expected Result/s When a row is selected, data in that row will bedisplayed
Non Active Customers
on txtBoxes Check btn Customers who havent done transactions after the selected date will be loaded to the grid view
Table 13: Test Plan N.A. Customers
Success
55
7.14 User Account Menu

Figure 19: User Accounts Menu
Allows the user to create users, modify the user details and so on and is visible for managers.
7.14.2 Pseudo Code
START IF logged in User != CEO THEN DISABLE btnNewUser ELSE ENABLE btnNewUser ENDIF IFbtnNewUserClickedTHEN Show New User Form ENDIF IFbtnModifyUserClickedTHEN Show Modify/Delete User Form ENDIF END
56

Test Case User Accounts Description NewUser - btn Modify\DeleteUser btn Expected Result/s Show new User Form Show Modify\Delete User Form
Table 14: Test Plan - User Accounts Menu
Actual Result Success Success
7.15 New User

Figure 20: New User Screen
CEO could create new users with rankings in order to allow access to the SLTC system.
7.15.2 Pseudo Code
START LOADcboRank with Cashier, Finance Manager, Stock Manager, CEO Create button READ User Name READ Password Asia Pacific Institute of Information Technology 57
SLTC System Development Project READ Confirm Password IF User Name == Existing User Name THEN DISPLAY Error ELSEIFPassword != Confirm Password OR Rank == THEN DISPLAY Error ELSE SAVE User Name, Rank, Password in TblUser ENDIF Reset button Clear textboxes END
7.15.3 Test Plan
Test Case New User
Description Rank - cbo
Expected Result/s Cashier, Finance Manager, Stock Manager, and CEO will be displayed.
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.
Table 15: Test Plan - New User
Success
58
7.16 Modify / Delete User

Figure 21: Modify/Delete User Screen
Existing user accounts can be modified and only CEO could modify ranks and delete any account in order to suspend the access to the system.
7.16.2 Pseudo Code
START IF currentLoggedUser != CEO THEN LOADcboUserName with currentLoggedUser Name FROM User Table LOADcboRank with currentLoggedUser Rank cboRank = disabled Modify button READ User Name, Rank READ Password, Confirm Password READ New Password, Confirm Password IF Password != Confirm Password OR New Password != Confirm New THEN DISPLAY Message Box ELSE UPDATETblUser with User Name, Rank, Password ENDIF Asia Pacific Institute of Information Technology 59
Deletebutton = disabled ELSE LOADcboUserName with existing User Names FROM User Table LOADcboRank with Cashier, Finance Manager, Stock Manager, CEO Modify button READ User Name, Rank READ Password, Confirm Password READ New Password, Confirm Password IF Password != Confirm Password OR New Password != Confirm New THEN DISPLAY Messege Box ELSE UPDATETblUser with User Name, Rank, Password ENDIF Deletebutton DELETE User FROMTblUser END
7.16.3 Test Plan

Test Case Modify\ Delete User User Name - cbo Description Rank - cbo Expected Result/s Cashier, Finance Manager, Stock Manager, and CEO will be displayed. Fill with User names at the form load. Modify - btn If existing password and confirm password equals and new password and existing password equals then display a msgBox about successful modification Else Display error msg. If existing password and confirm password equals Display a successful account deletion. Success Success Actual Result Success
Delete - btn
Success
Table 16: Test Plan - Modify/Delete User
60
7.17 Stock Menu

Figure 22: Stock Menu Screen
7.17.2 Pseudo Code
START IF logged in user = Finance manager THEN DISABLE btnGRN DISABLE btnPOG DISABLE btnManagecategory DISABLE btnManageproduct ENDIF IF logged in user = Cashier THEN DISABLE btnGRN DISABLE btnPOG DISABLE btnManagecategory DISABLE btnManageproduct ENDIF Good Receive Note button Show Good Receive Note Form Purchase Order Generation button Show Purchase Order Generation Form Asia Pacific Institute of Information Technology 61
MnageProoducts button Show Manage Products Form Manage Category button Show Purchase Order Generation Form END
7.17.3 Test Plan
Test Case Stock
Test Description Manage Products-btn Good Receive note-btn Manage Categories - btn POG - btn Price List btn
Expected Result Takes to the Manage Products interface Takes to the GRN interface
Success
Takes to the Category management interface Takes to the POG interface Load Price List
Table 17: Test Plan - Stock Menu
Success
Success Success
62
7.18 Good Receive Note

Figure 23: Good Receive Note Screen
When a stock comes to the company a GRN is created with the relevant details and the profit percentages. These can be saved on the stock file once completed.
7.18.2 Pseudo Code
START AUTOGENERATE Date, User ID LOADcboCategory with Category names at the form load Check button READ Supplier ID IF Supplier ID != existing Supplier ID THEN DISPLAY Error ENDIF IF Category is SelectedTHEN LOADcboProduct with Product names within the selected category ENDIF IF Product is SelectedTHEN AUTOFILL Profit textbox ENDIF Asia Pacific Institute of Information Technology 63
Save button UPDATE TblSupplier with last GRN date Received quantity = Existing received quantity + GRN quantity UPDATE TblProducts table with Received quantity SAVE TblStocks with Damage = FALSE AND Sold = FALSE, Product ID Close the Form END
7.18.3 Test Plan
Test Case Good Receive Notes
Description User txtBox Check btn
Expected Result/s User ID will be auto filled at the form load. If supplier ID does not exists Display MsgBox.
Success
Category - cbo
Category names will be loaded at the form load. When a category is selected Product cbo will be loaded with Product names.
Success
Save btn
Close the form.
Success
Table 18: Test Plan - GRN
64
7.19 Purchase Order Generation

Figure 24: P.O. Generation Screen
When the reorder level reaches its level a POG is generated by the manager to be given to the supplier to deliver the stock.
7.19.2 Pseudo Code START AUTOGENERATE Date Check button READ Supplier ID IF Supplier ID != existing Supplier ID THEN DISPLAY Error ELSE ADD Supplier ID, Name, contact person to the Supplier DataGrid Asia Pacific Institute of Information Technology 65
SLTC System Development Project AUTOFILL Supplier name textbox ENDIF IF selected Products reorder quantity > received quantity OR quantity > 0 THEN FILL Product dataGrid with Product ID, Reorder quantity and order quantity of the selected supplier ENDIF
backorder back
Reset button Clear all the text boxes Clear supplier dataGrid Print button SHOW Purchase order Generation report END
7.19.3 Test Plan
Test Case Purchase Order Generation
Description Search - btn
Expected Result/s Filtering the Supplier details on the Supplier list dataGrid to match Supplier Name txtBox
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 Print btn
Reset the filtering of the Supplier list dataGrid Print Suppliers Purchase Order
Table 19: Test Plan - P.O. Generation
Success
Success
66
7.20 Product Management

Figure 25: Product Management Screen
In this form, Products can be managed by adding new products and by updating the existing products which are available in the database.
67
START LOADcboCategory with Category Names in Category Table IFCtegory is SelectedTHEN FILL Stocks DataGridView with Product information of selected Category ENDIF IF Product Row is SelectedTHEN FILL Product ID, Product Name, Reorder Point, Unit Price, Reorder Qty, Unit Price, Profit, Reorder Date, Last Reviewed Date textboxes ENDIF New Check box btnUpdate Enable = FALSE btnSave Enable = TRUE txtLastRecievedDate Enable = FALSE Clear textboxes Save button AUTOGENERATE Product ID READ Product ID, Product Name, Reorder Point, Unit Price, Reorder Qty, Unit Price, Profit, Reorder Date Unit Price = UnitPrice * (1 + Profit) SAVE Product ID, Stock Name, Reorder Point, Unit Price, Reorder Qty, Unit Price, Profit, Reorder Date in TblProduct Update button READ Product ID, Product Name, Reorder Point, Unit Price, Reorder Qty, Unit Price, Profit, Reorder Date, Last Received Date Unit Price = UnitPrice * (1 + Profit) SAVE Product ID, Product Name, Reorder Point, Unit Price, Reorder Qty, Unit Price, Profit, Reorder Date, Last Received Date in TblProduct END
68
Test Case Product Management
Description Category - chk
Expected Result/s Load with Category names at the form load. When a row is selected, Product details will be displayed on txtBoxes in the Group box. Text boxes in the groupbox will be cleared. Product ID will be auto generated. btnSave Enabled btnUpdate Disabled
Product list - dataGrid
Success
New - chk
Success
Save btn
Product ID, Name, Success Reorder point, Unit price, Profit, Reorder date and last received date will add to Product list dataGrid. Or Display messagebox for an error. Update the Product list Success dataGrid with new Product ID, Name, Reorder point, Unit price, Profit, Reorder date and last received date in textboxes.
Update btn
Table 20: Test Plan - Product Management
69
7.21 Category Management

Figure 26: Category Management Screen
In this form, the categories can be managed by the user by adding new categories and modifying the once which are already available in the database.
7.21.2 Pseudo Code
START LOAD CategoryDataGridView with Existing Category IDs, Category Names IF Category is SelectedTHEN FILL Category ID, Name textboxes ENDIF New Check box Clear textboxes BtnSave Enable = TRUE btnUpdate Enable = FALSE btnDelete Enable = FALSE Save button AUTOGENERATE Category ID Asia Pacific Institute of Information Technology 70
SLTC System Development Project READ Category Name IF Category Name == OR Category Name == Existing Category THEN Display Error ELSE SAVE Category ID, Category Name in Category Table ENDIF Update button READ Category ID, Category Name UPDATETblCategory with Category ID, Category Name Delete button READ Category ID DELETE selected Category FROM TblCategory END
7.21.3 Test Plan
Test Case Category Management
Description Category dataGrid
Expected Result/s When a row is selected from the list, data in that row will be displayed on txtBoxes to edit. txtBoxes will be emptied and an auto generated Category ID will be displayed. New Category will be saved or/and amsgBox will display.
New chkBox
Success
Save btn
Success
Update btn
Edited fields of the selected Category will be updated and/or a msgBox will be displayed
Success
Delete btn
Selected Category will be Success deleted and/or amsgBox will appear.
Table 21: Test Plan - Category Management
71
8. Report Designs
8.1 Invoice
Figure 27: Reports - Invoice
Invoice report will display the records of currently generated invoice in-order to provide the customer with a record of transactions.
72
8.2 Debtors
Figure 28: Reports - Debtors
Debtors report will display all the details of current debtors of the company.
73
8.3 Price List
Figure 29: Reports - Price List
74
9. Gantt chart
75
10.Workload Matrix
Task
Kasun Fernan do
AshanMadura nga
LakshikaTennak oon
Introduction DFD ER Hierarchy chart Forms Login Main o Invoice Screens Pseudo Test Plan Back Order Screen Pseudo Test Plan o Supplier Manage Supplier Screen Pseudo Test Plan Return to Supplier Screen Pseudo 100% 100% 100% 100% 100%
100%
100%
100% 100%
100% 100%
100% 100%
100% 100% 100%
100% 100%
76

Test Plan Non Active Supplier Screen Pseudo Test Plan o Customers Manage Customers Screen Pseudo Test Plan Payments Screen Pseudo Test Plan Customer Returns Screen Pseudo Test Plan Non Active customers Screen Pseudo Test Plan o User Accounts o Stock GRN New User Modify User 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100%
100% 100% 100%
77

Screen Pseudo Test Plan POG Screen Pseudo Test Plan Manage products Screen Pseudo Test Plan Manage Categories Screen Pseudo Test Plan Reports Invoice o Invoice Reports 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100%
Suppliers o o o Non active supplier POG Return to supplier 100% 100% 100%
Customers o o o o Customer payment Customer returns Non active customers Debtors report 100% 100% 100% 100%
78

Stock o o Price List Sales Report 100% 100% 100% 100% 100% 40% 40% 20%
Assumptions/Business Rules Gantt Chart Limitation Work load matrix Programming o o o o o o Invoice Back Order Customer Forms Supplier Forms User Accounts Stock Forms 100% 100% 100% 100%
100% 100%
Crystal Report Programming o o o o Invoice POG Debtors Price List 100% 100% 100% 100%
79
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.
80
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. The stocks 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 over exceeded 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
81
SLTC System Development Project Finance Manager Manage Customers Handle Returns to the Supplier Settle payments for the Customers on returned goods which are purchased on cash
CEO Manage user accounts Have the authority to do all the tasks within the system
13. Limitations
Company wont keep a track of every payment done by the customers, only the 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.
82
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 the requirements, a scope was decided by the business analysis and within that scope a feasibility study was carried out in order to find if this is worthwhile for the A+ Solutionz to carry on with the project. Hence the system programmer designed the ER and DFD diagrams to the scope the business analysis produced with his help. Before designing the system, both those diagrams and the hierarchy charts were designed by the system programmers. Once the design has been successfully completed, the system was tested with actual data before handing over the system to the SLTC. A test plan was created with the results obtained from those testing and the parts where it needed to be upgraded was done after the information gathered from the test plan. This was done for forms as well as the reports which were taken. The documentation was concluded with stating the assumptions, business rules and limitations of the system which was designed. For an example for all those steps which are mentioned above, in the system there has to be user accounts with different access rights to the system. Hence in the design of the forms, the enabling of buttons differs from user to user. In the testing it was tested if those enabling works with different ranking available. Concluding the project A+ Solutionz believes that most of the requirements which were needed by the project have been addressed in the system which was developed.
83
Appendix
Weekly Meeting Reports
84

Final SLTC

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Final SLTC

Hochgeladen von

Copyright:

Verfügbare Formate

SLTC Retail System

Subject Title System Name Group Member

SLTC System Development Project

Asia Pacific Institute of Information Technology

Asia Pacific Institute of Information Technology

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

Asia Pacific Institute of Information Technology

SLTC System Development Project

Asia Pacific Institute of Information Technology

SLTC System Development Project

Asia Pacific Institute of Information Technology

SLTC System Development Project

Asia Pacific Institute of Information Technology

SLTC System Development Project

Good Received Note Add New Stocks

Return Damaged goods to Supplier

Asia Pacific Institute of Information Technology

2.2 Non Functional Requirements

Asia Pacific Institute of Information Technology

SLTC System Development Project

Printer Dot Matrix or Inkjet Printer User Training

3.2 Operational Feasibility

Asia Pacific Institute of Information Technology

Asia Pacific Institute of Information Technology

SLTC System Development Project

3.3 Economic Feasibility

Total Developmental Costs

Asia Pacific Institute of Information Technology

SLTC System Development Project Estimated Annual Operational Costs

Asia Pacific Institute of Information Technology

SLTC System Development Project Tangible Benefits

Cumulative Costs 982 500.00

Asia Pacific Institute of Information Technology

SLTC System Development Project

Return on Investment Analysis

Asia Pacific Institute of Information Technology

SLTC System Development Project

Asia Pacific Institute of Information Technology

SLTC System Development Project

Asia Pacific Institute of Information Technology

SLTC System Development Project

5. Data Flow Diagrams

Figure 3: Context Diagram

Asia Pacific Institute of Information Technology

SLTC System Development Project

5.2 Level 0 Diagram

Figure 4: Level 0 Diagram

Asia Pacific Institute of Information Technology

SLTC System Development Project

Figure 5: Hierarchy Chart

Asia Pacific Institute of Information Technology

SLTC System Development Project

Figure 6: Login Screen

7.1.2 Pseudo Code

Asia Pacific Institute of Information Technology

SLTC System Development Project 7.1.3 Test Plan

Close the form.

Asia Pacific Institute of Information Technology

SLTC System Development Project

7.2 Main Menu

Figure 7: Main Menu Screen

Test Case Main

Test Description Invoice-button Suppliers-button