BRP: Milestones Combined

From Software Engineering

Jump to: navigation, search

[ Back Row Productions ] - [ Milestone 2 ]

Contents

[edit] Executive Summary

[ Executive Summary ]

[edit] System Test Cases

[ MS5 System test cases ]

[ System test cases by Team Ace ]

[edit] Design Class Diagram

Design Class: Diagram

Design Class(POS): Diagram

[edit] Interaction Diagrams for selected use cases

Pizza to Cart : Diagram

Dvd to Cart: Diagram

Special to Cart: Diagram

Create Acct: Diagram

[edit] State Diagrams for selected analysis or design classes

State Diagram Edit Account: Diagram

State Diagram View Cart: Diagram

[edit] Descriptions of Design Classes

BRP Design Descriptions

[edit] Analysis Descriptions and Classes Used

DVDBrowse analysis

Customize Pizza

Customer Orders Special Meal

View Shopping Cart

Check Out

Change Password

Customer Changes Account Information

[edit] Use Case Realization Table

Use Cases ::: Classes Used


DVD Browse Dvd
Customize Pizza Pizza SpecialItem GenItem
Order Special Meal Pizza SpecialItem GenItem
View Shopping Cart Pizza ShoppingCart Dvd
Check Out Pizza ShoppingCart Dvd
Change Password Customer Query
Change Account Info Customer Query
Add Gen item to cart Cart Query
Add Pizza to cart Cart Query Pizza
Add special to cart Cart Query
Add DvD to cart Cart Query DvD
Add DvD to DB DvD
Add gem item to DB Query
Manager Logs in Query
Add/Change/Delete Employee Info Query EmpInfo
Change/Delete Item Info Query
Employee Clocks in/out EmpClock
Employee brings up customer order Query
View whos clocked in EmpInfo
Employee enters new customer Query Customer
Employee Start day Cash EmpInfo
Employee cash drop EmpInfo
Manager views sales report EmpInfo
Manager views inventory EmpInfo Query
User pays order Customer OrderParser Query
Cook views kitchen order screen OrderParser Query
Manager views employee hours worked EmpInfo EmpClock Query
Manager views labor report EmpClock Query
Employee Recalls Customer's Order on Register OrderParser Query
Employee Rings Up Customer's Order on Register OrderParser Query

[edit] Use Cases

[edit] Basic Architecture

  • Programming Language: C#
  • User Interface:
    • Website for external users (customers)
    • Touch-screen GUI for employess
    • Kitchen order screen
  • Persistence Mechanism: SQL Database
  • Libraries: .NET Libraries

[edit] Basic Infrastructure

We are going to be using:

  • Website
  • Database
  • Visual Studio

[edit] Requirements Document

[edit] 1.Customer Ordering

1a. Website
1a1. Customers will be able to go to our website and order pizza and a movie for delivery or pickup.
1a2. Customers may create an account with the website in order to save some of their information for ease of ordering in future purchases.
1a3. Customers may browse pizza/movies without logging in and may even order food/movies without logging in.
1a4. Orders will be logged in the database and sent to the store where they will be filled.
1a5. Customers may order a meal, special, or create their own pizza and add sides to their meal.
1a6. Upon ordering the customer will be given a time estimate for arrival.
1a7. Manager/Webmaster will be able to edit the specials, meals, and toppings, movies, and prices, along with adding meals, specials, and prices.

[edit] 2.In-Store

2a. Register Program
2a1.Register program will feature customizable buttons which can be changed by the manager and will server as the buttons to create an order.
2a2.All orders will be logged along with any corrections made to the orders.
2a3. The order will create a receipt with an order number on it which will be recallable by the register.
2a4. Will keep track of how much money is in the register at all times.
2a5. Discounts may be applied to orders.
2a6. Employees can clock in at terminals.
2a7. An order screen will contain orders in a queue fashion. Orders will be movable by employees.

[edit] 2b. Manager Program

2b1. A manager program will interact with the database in order to give the manager up to date stats on sales and inventory.
2b2. Manager will be able to view employee activity.
2b3.The program will be able to print off an inventory sheet which would include Item, location, size, usage, price per week.
2b4. The inventory sheet would be editable in order to change price of certain items per week.


[edit] Client Note

I have met with the team, and the requirements appear to meet my needs. Rich did an excellent job of taking notes and all of the guys had distinctive and probing questions. I believe that our meeting gave them a true sense of the scope and nature of the program required and its precise implementation. I am looking forward to their continued success in its production.

Robert

Personal tools