Grocery Store Information System

1
Grocery Store Information System

• Team Members
• Trevor Foraie
• Kobe Davis
• Guy Davis
• Adnan Ahmed

2
Introduction

• The Company
• A software development company specializing in
  Retail Information System.
• Systems are developed using agile methodologies.
• Small organization assigning resources varying
  tasks throughout the assignment.
• Based in Calgary, Alberta, Canada.

3
Introduction (cont..)

• The Product
• Grocery Store Information System broken into
  modules, delivery of which is determined by
  clients.
• Includes but not limited to features such as
  point of sales systems, inventory tracking,
  ordering, invoicing, accounting etc
• Will be developed using RUP.
• Multiple Releases will be shipped to customers.

4
Customers and Stakeholders

• Primary Stakeholders are customers who have
  expressed interest in purchasing the finished
  product, or one or more of the available modules.
• Different size of the customers leads to
  different types of licensing.
• Currently 3 major customers in total.

5
Customers and Stakeholders (cont..)

• Safeway our largest customer will be installing
  the system in its stores throughout the
  northwestern states and western Canada.
• Co-op our second largest customer will be
  installing the system throughout Alberta
• Mom Pop grocery will be installing the system
  in a singlestore in SW Calgary

6
MILOS

• Process model entered into MILOS in a hierarchy.
• Repeat the hierarchy for iterative development.
• Differing focus across processes determined by
  clients importance.
• Agents assigned to processes are responsible for
  that process and its deliverables.
• MILOS demonstration to illustrate.

7
Agents

• Project Manager
• 6 Developers
• 3 Testers
• Safeway Business Rep (Domain Expert)
• Co-op Business Rep (Domain Expert)

8
Requirements Model
Grocery store Information System
Billing/Invoicing System
Transaction Processing System
Order/Inventory System
Invoice Generation

• Product Management GUI
• Add/Edit/Delete Products
• Spoilage/wastage entry

• Pricing Management System
• Set Pricing by Product
• Set sale pricing byproduct/date

Accounts Payable/Receivable Reporting

• Stock Reporting
• By product
• By dept.
• By Store

Sales Reporting
POS GUI Touch Screen Interface

• Order Creation
• By product
• By dept.
• By Store

Barcode Scanner
Credit/Debit Interface
DIY Checkout System
Receipt Generation
9
Constraints

• Coupling Constraints
• Product Management System/GUI is coupled to
  Spoilage/Wastage Entry
• Stock Reporting (Product) is coupled to Stock
  Reporting (Dept)
• Stock Reporting (Product) is coupled to Stock
  Reporting (Store)

• Precedence Constraints
• View Invoice must precede Print Invoice
• Pricing Management (By Product) must precede
  Pricing Management (Sales)
• Product Management System/GUI must precede
  Pricing Management (By Product)
• Credit/Debit Card System Interface must precede
  Self Checkout System

10
Motivators

• Safeway, Co-op
• Reduce costs.
• Improve efficiency.
• Mom Pop
• Reduce staff.

11
Voting

• Weighted according to size and value to our
  company.
• Safeway
• Weight 9
• Co-op
• Weight 6
• Mom Pop
• Weight 3

12
Voting (2)
13
Release Plans

• 2 release plans generated.
• Subtle but major difference between the plans is
  the scheduling of the Self Checkout System.
• Plan 1 favors smaller client, plan 2 favors
  larger clients.
• Use plan 2 since larger clients are more
  important to our company.

14
Release Plan (2)
15
Release Plan (3)

• First plan makes better use of resources in first
  release.

16
Tools Used

• MILOS
• Hierarchical breakdown of development process and
  process model.
• Hierarchy is repeated for iterative development.
• Assign agents to deliverables or tasks and send
  notifications.
• Release Planner
• Coordinate requirements delivery.
• Automate gathering stakeholder input.
• Provide central location for release status and
  overview.

17
Process Improvement

• MILOS process should be made available to release
  planner to show how releases are achieved.
• Cant assign aspects of release plan to MILOS.
• Release planner doesnt have explanation
  component.
• Release planner is not adaptive once releases are
  planned (cant redo processes).
• Dynamically regenerate plan x1, x2 when plan x
  is complete.

18
Explanation Component

• Release planner does not explain why decisions
  were made in a release.
• Concept map of process and requirement dependency
  would help illustrate dependencies across
  requirements.
• Use priorities and dependencies to explain to
  customers why certain requirements were in a
  certain release.

19
Discussion