11. Link to 207 report.

This is the link to our 207 report and also the diagrams

http://savefile.com/projects/808623969.

10. User Interface.

This is the front page of our Online Bakery Ordering System.

9. Sequence Diagrams of Administrator activities

    

1. Manage Topping Records                                            2. Manage Pending Order Records

    

3. Manage Discount Records                                          4. Manage Default Cake Weight Records

    

5. Manage Default Cake Records                                    6. Manage Customers Records

         

7. Manage Custom Cake Weight Records                          8. Manage Custom Cake Shape Records

9. Manage custom cake base flavour

8. Sequence Diagrams of Customer activities

    

1. User Login                                                               2. User Logout

      

3. Customer sign up                                                     4. Manage own information details

      

5. Order Custom cakes                                                     6. Order Default cakes

      

7. Payment – by Credit Card                                              8. Payment -  by E-Nets

        

9. Check order details                                                     10. Cake World Game

 

11. Treasure Chest Game

7. Entity Relationship Diagram (ERD)

The Entity Relationshop Diagram (ERD) is used to model the structure of the database. It models the database tables that are avaliable in the database, the fields of the tables and also how the tables are related.

Note: Click on the image for clearer view.

6. Class Diagram

The below is the Class Diagram.

 

*Note: Subject to changes.

*Click click for clearer view.

5. Potential Classes List

The Online Bakery System allows both customers and administrators to access it as separate users with different menus and functions in both cases.  

Existing customers are required to log in through the login UI, and upon being logged in, they are remembered as a User. New customers are able to register for a new account at the sign up UI. Once the customer is logged in, they will be directed to the Customer User Interface (UI) where they can choose to order a default cake or customized cake. After the customer has decided on the cakes of choice, they can then be added to a cart. From this cart, the customer is able to choose between two payments methods, either by credit card or by eNETs, and they will be directed to a payment UI which is either a credit card UI or a NETs UI. Once the payment is successful, customers will then be able to choose to play between two games, either Treasure Chest or Cake World. Either of the games award customers with discounts for future visits. 

Administrators once logged in, will be redirected to an Admin UI where they can choose to view the various tables of the database, categorized into users, inventory and orders. In each database, administrators can then perform various functions like add, edit or delete entries. Administrators are also able to create a transaction log using a transaction log creator. 

One of the games that determine the discounted amount is the Cake World game. Each token picked up increases the length of the player’s trail, and the score incremented. When the player collides with the walls or its trail, the game over screen is displayed. The discount given is based on the player’s score. 

The Treasure Chest is a game of luck. In order to play the game, the user would have already ordered either a custom or default cake and his payment would have already been made. The customer will select one of three treasure chests to earn himself a discount for his next visit. Clicking on one of the treasure chest will randomly generate a discount value. The discount value will be displayed.

Potential Class List

Online Bakery System	Things remembered or structure	Confirmed (system itself)
Customers	Things remembered or role played	Rejected (criteria 1 & 2 fails)
Administrators	Things remembered or role played	Rejected (criteria 1 & 2 fails)
Login UI	Things remembered or structure	Confirmed(criteria 1-3 & 6 apply)
User	Things remembered or role played	Confirmed(criteria 1-3 apply)
Signup UI	Things remembered or structure	Confirmed(criteria 1-3 & 6 apply)
Customer UI	Things remembered or structure	Confirmed(criteria 1-3 & 6 apply)
Default Cake	Things remembered or role played	Rejected(criteria 1 & 2 apply but 3 fails)
Customized Cake	Things remembered or role played	Rejected(criteria 1 & 2 apply but 3 fails)
Cart	Things remembered or structure	Confirmed(criteria 1-3 & 6 apply)
Payment	Things remembered or structure	Rejected
Credit Card	Things remembered or structure	Rejected(criteria 1 & 2 apply but 3 fails)
eNETs	Things remembered or structure	Rejected(criteria 1 & 2 apply but 3 fails)
Payment UI	Things remembered or structure	Confirmed(criteria 1-3 & 6 apply)
Credit Card UI	Things remembered or structure	Confirmed(criteria 1-3 & 6 apply)
CakeWorld	Things remembered or structure	Confirmed(criteria 1-3 & 6 apply)
TreasureChest	Things remembered or structure	Confirmed(criteria 1-3 & 6 apply)

4. Acitivity Diagrams

            
1.CustomerValidateLoginandMenuSelection                      2.CustomerTreasureChest
            
            
3.CustomerPlaceOrder                                                    4.CustomerManageExistingCustomerInfo

            
5.CustomerMakePayment                                               6.CustomerCustomerSignUp

              
7.CustomerCakeWorld                                                   8.AdminMaintainDefaultcakesRecord

           
9.AdminMaintaindefaultcakeweightrecord                       10.AdminMaintainCustomerRecordtable

            
11.AdminMaintaincustomcakeshapetable                         12.AdminMaintainAdminRecordtable.

              
13.AdminMaintainPendingOrder                                     14.AdminMaintainCustomtoppingtable

         
15.AdminMaintainCustomtoppingtable                             16.AdminMaintainCustomCakeWeighttable

         
17.AdminMaintainCustomBaseFlavourtable                      18.AdminCreateTransactionLog

3. Refined Use-case diagram and specifications

After Another round of refinement.

Note: Click on the image for clearer view.

After another round of FAST to understand more of the system requirements and drawing of Activity diagram, a refined use-case is produced.

*Diagram subject to changes.

2. Proposed Project Schedule (Gantt Chart)

1.  2.

3.  4.

Note: Click on the Gantt Chart for bigger and clearer image.