1. Topic Cafeteria Management System GROUP : 9 TEAM 1.

2. Project Plan  1. Introduction.  2. Project Organisation.  3. Resource Requirements.  4. Work Breakdown.  5. Project Schedule.  6. User and System Requirement.  7.System Modelling.  8.Risk Analysis

3. 1. Introduction.  Introduction  1.1 Description  The proposed topic Cafeteria Management System (hereafter called “CMS”) is a computer-based system that will allow Cafeteria Administrator to create online to assist teachers or students can order section if they can’t come to cafeteria. If this software can be used to IU portal, the student will be more comfortable and happy about IU’s cafeteria service.  1.2 Constraints  Time: This project must be implemented by November 19, 2012 to allow time for user familiarization and training in IU.  Budget: All costs associated with the project will relate to the human resources required to develop the software.

4. 2. Project Organization The project development team are: _ Pham Vien Du. _ Cao Thuy Linh. _ Dang Hung. _ Pham Ton Minh Nhat. _ Nguyen Thanh Nam. Project team consist of: _ Scrum Master. _ Business Analyst (product owner). _ Software Programmer (development team). _ Test Engineer (development team).

5. 3. Resource Requirements  3.1 Human Resource All members of team come from International University, so we have a good basic knowledge about software process and skill in programming as well as team-work.  3.2. Hardware and software Resources Cafeteria Management System is created by using java, with simple functions and small database, so we just need an average sever.

6. 4. Milestones and Deliverables Task No Task Name Duration (days) Engineers Estimated Completion Date T1 Introduction 1 Hung Oct 1, 2012 T2 Project organization 1 Hung Oct 2, 2012 T3 Source requirement 1 Linh Oct 3, 2012 T4 Work breakdown 1 Linh Oct 4, 2012 T5T5 Project schedule 1 Linh Oct 5, 2012 T6T6 System requirement 5 Linh Oct 10, 2012 T7T7 System architecture 5 Du Oct 15, 2012 T8 Risk analysis 1 Du Oct 16, 2012 T9 System Designing 3 Team Oct 22, 2012

7. 4. Milestones and Deliverables T10 Object Interface Specification (sprint cycle 1) 1 Linh, DuOct 23, 2012 T11 Graphic User Interface (sprint cycle 1) 1 Du, Nh ậ t Oct 24, 2012 T12 Design/Development issues (sprint cycle 1) 3 Nam, Linh, Hùng Oct 28, 2012 T13 Domain Requirement Design/Development (sprint cycle 1) 3 Nh ậ t, Nam Oct 31, 2012 T14 Project Implementation (sprint cycle 1) Login function 2 Nam(coder), Nh ậ t Nov 2, 2012 T15 Project Implementation (sprint cycle 1) Order function 2 Nam(coder), Du Nov 4, 2012 T16 Project Implementation (sprint cycle 1) Register function 2 Nam(coder), Du Nov 6, 2012 T17 Testing and Validation (sprint cycle 1) 1 Hùng, Du Nov 7, 2012 T18 Object Interface Specification (sprint cycle 2) 1 Linh, Du, Hùng Nov 8, 2012 T19 Graphic User Interface (sprint cycle 2) 1 Nh ậ t, Nam Nov 9, 2012 T20 Design/Development issues (sprint cycle 2) 1 Linh, Du, Nam Nov 10, 2012 T21 Domain Requirement Design/Development ( sprint cycle 2) 1 Du, LinhNov 11, 2012 T22 Project Implementation (sprint cycle 2) Add Item Function 2 Du, Nam Nov 13, 2012 Project Implementation ( sprint cycle 2) Update Item information Function 2 Linh, Hùng Nov 13, 2012 Project Implementation (sprint cycle 2) Remove Item Function 1 Du, Nh ậ t Nov 14,2012 Project Implementation (sprint cycle 2) Manage Report Function 2 Nam, Nh ậ t Nov 16, 2012 Project Implementation (sprint cycle 2) Manage Cart Function 2 Du, Nam, Hùng Nov 18, 2012 Project Implementation (sprint cycle 2) Manage Payment method Function 2 Du, Nam, Nh ậ t Nov 20, 2012 T21 Testing and Validation (sprint cycle 2) 1 Hùng, Du Nov 21, 2012

8. 5. Project Schedule

10. 6. User and System Requirement  User Requirement :  The customer or the admin to log in their homepages.  The customer register an account.  The customer select the food/drink in the cafeteria shop websites.  The users check out the selected product.  The admin to add the new food/drink.  The admin to update the information of the store.  The admin to delete food/drink.  The admin to view the report.

11. 6. User and System Requirement  System Requirement:  Functional:  Login  Register  Order food/Drink  Checkout product  Add Food/Drink  Update Food/Drink information  Delete Food/Drink  View Report  Non-Functional:  Product Requirements  Organization Requirements  External Requirement

12. 7. System Modelling

13. 8. Risk analysis  Project Risks  Project Risk Analysis  Project Risk Planning  Product Risks  Product Risk Analysis  Product Risk Planning