Galla the Small Shop ERP Product

1. Galla the Small Shop ERP Product Palwencha (palwencha@it.iitb.ac.in, Project Manager, Documentation) Gulavani Bhargav Subhash (bhargav@cse.iitb.ac.in, Software Architect, System Interfaces) Anirudha Joshi (anirudha@iitb.ac.in, Human Interface Designer, Domain Expert) Avinash Gupta (avinash08@iitb.ac.in, Quality Assurance) Nilesh Nalnikar (nileshnalnikar@iitb.ac.in, Tooling, Quality Assurance)

2. Contents • The need and the opportunity Requirements • Use cases • Quality assurance scenarios Design • Product and interaction design • Architecture • Quality assurance plan • Estimation

3. The Need • Large shopping malls • Scale and efficiency • Organized management • Experience • Small shops • Personalized service • Trust • Shops for all • Credit • Entrepreneurship • Employment

4. Future?

5. The Opportunity • Routine tasks • Improve efficiency, organization, flexibility • New possibilities • Enable informed decision making • Introduce modern business thinking • Retain • Credit • Service • Personal contact • Informality

6. Contents • The need and the opportunity Requirements • Use cases • Quality assurance scenarios Design • Product and interaction design • Architecture • Quality assurance plan • Estimation

7. Functional Requirements • Ordering and billing • Items in hand • Shopping list (on phone) • Advance order • Recurring order • Mobile order • Up-sale • Order changes • Home delivery • Returns

8. Functional Requirements • Ordering and billing • Settlement • Cash • Credit card • Credit • Account opening • Credit tracking • Settlement

9. Functional Requirements • Ordering and billing • Settlement • Cash flow management • Statement • Demand forecasting • Cash flow forecasting

10. Functional Requirements • Ordering and billing • Settlement • Cash flow management • Inventory and vendor management • Tracking • Ordering • Vendor returns • Vendor accounts and profitability • Demand forecasting

11. Functional Requirements • Ordering and billing • Settlement • Cash flow management • Inventory and vendor management • Revenue management • Customer relationship management • Customer purchase prediction • Preferred customer programme (own or external) • Discounts and sales

12. Non-functional Requirements • Availability don’t disturb my work • Open the door and I can attend to a customer • Costs 10,000 + 1,000/m • Product + service • Flexibility many types of shops, scalability • Groceries, dairy, laundry • Performance dust, electricity • Security tamper proof • Usability non-tech savvy • Fit in my culture Laxmi

13. Use Cases

14. Speed of use Modifiability Security Scalability Availability Availability, flexibility Availability, robustness Quality Assurance Scenarios

15. Speed of use Modifiability Security Scalability Availability Availability, flexibility Availability, robustness source - the user stimulus - starts up ... artefact - ... the system environment - in off state response - boots up ... response measure - ... in less than half a minute Quality Assurance Scenarios

16. Speed of use Modifiability Security Scalability Availability Availability, flexibility Availability, robustness source - the user stimulus - switches to billing mode ... artefact - ... the system environment - currently running in non-billing mode response - the system switches to billing mode ... response measure - ... in less than 5 seconds Quality Assurance Scenarios

17. Speed of use Modifiability Security Scalability Availability Availability, flexibility Availability, robustness source - the cashier stimulus - submits an item for billing artefact - ... the system environment - currently running in billing mode response - identifies and bills the item ... response measure - ... operation completes correctly, within 5 seconds per item Quality Assurance Scenarios

18. Speed of use Modifiability Security Scalability Availability Availability, flexibility Availability, robustness source - the user stimulus - adds an extra terminal to artefact - ... the system environment - under normal operation response - extra terminal along with all other existing terminals are functional response measure - ... there is no downtime Quality Assurance Scenarios

19. Speed of use Modifiability Security Scalability Availability Availability, flexibility Availability, robustness source - the user stimulus - performs any permissible operation on artefact - ... the system environment - under normal operation response - the permissible operation is completed successfully response measure - ... the system does not hang up, and the notification of the completed operation is given to the user Quality Assurance Scenarios

20. Packaging Requirements • Terminal (s) • Screen for showing the information graphically • Input device which has facility to enter the alphanumeric characters • A central ‘hub’ • Centralized database

21. External Interfaces • Terminal • Credit card reader • Printer • Scratch disk • Hub • ‘Hub’ • Terminal

22. Contents • The need and the opportunity Requirements • Use cases • Quality assurance scenarios Design • Product and interaction design • Architecture • Quality assurance plan • Estimation

23. Database – Customer

24. Database – Vendor

25. The Product

26. CustomerSessions

35. VendorSessions

41. AdminSessions

45. UI Structure

46. Contents • The need and the opportunity Requirements • Use cases • Quality assurance scenarios Design • Product and interaction design • Architecture • Quality assurance plan • Estimation

48. Thanks • The need and the opportunity Requirements • Use cases • Quality assurance scenarios Design • Product and interaction design • Architecture • Quality assurance plan • Estimation

50. Thanks • The need and the opportunity Requirements • Use cases • Quality assurance scenarios Design • Product and interaction design • Architecture • Quality assurance plan • Estimation