Topic Cafeteria Management System Group :

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

1. Introduction. 1.1 Description 1.2 Constraints Introduction 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.

2. Project Organization The project development team are: Phạm Viễn Du (Scrum Master.) Cao Thùy Linh (Business Analyst) Đặng Hùng (Tester) Phạm Tôn Minh Nhật (Developer) Nguyễn Thành Nam (Developer)

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 functions and small database, so we just need an average sever.

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

4. Work Breakdown. T10 Object Interface Specification (sprint cycle 1)   1 Linh, Du Oct 23, 2012 T11 Graphic User Interface (sprint cycle 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) Nhật, Nam Oct 31, 2012 T14 Project Implementation (sprint cycle 1) Register function 2 Nam(coder), Nhật Nov 2, 2012 T15 Login function Nam(coder) , Du Nov 4, 2012 T16 Order function Nov 6, 2012 T17 Testing and Validation (sprint cycle 1) Hùng Nov 7, 2012

4. Work Breakdown. T18 Object Interface Specification (sprint cycle 2) Linh, Du, Hùng Nov 8, 2012 T19 Graphic User Interface Nhật, Nam Nov 9, 2012 T20 Design/Development issues Linh, Du, Nam Nov 10, 2012 T21 Domain Requirement Design/Development Du, Linh Nov 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 Linh(coder), Hùng Remove Item Function Du (coder), Nhật Nov 14,2012 Manage Report Function Nam(coder), Nhật Nov 16, 2012 Manage Cart Function Du(design), Nam(code), Hùng Nov 18, 2012 Manage Payment method Function Du(design), Nam(code), Nhật Nov 20, 2012 Testing and Validation Hùng Nov 21, 2012

5. Project Schedule

5. Project Schedule

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 can add the new food/drink. The admin can update the information of the store. The admin can delete food/drink. The admin can view the report.

6. User and 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

Functional Adding food/drink Brief Description: This allows the admin to add the new food/drink Initial Assumption: the admin must be login by admin’s usernames and password Step-By-Step Description: Admin log in to the system by usernames and password. The system will check , if the usernames and password is right , the system will go to the “admin manager’s page” The admin will choose “menu” button in the admin manager page, choose “add new food/drink” The admin input the information of the new food/drink The admin send an adding request to the system by choosing “update” button The system will update the information into the database and displays the successful message. What Can Go Wrong: None Other Activities: None System State on Complete: The database updated the new drink/food.

Functional Brief Description: This allows the admin to update the information of the store Initial Assumption: the admin must be login by admin’s usernames and password Step-By-Step Description: Admin log in to the system by usernames and password . The system will check , if the usernames and password is right , the system will go to the “admin manager’s page” The admin will choose “menu” button in the admin manager page, edit the information. The admin send an update request to the system by choosing “update” button The system will update the information and displays the successful message. What Can Go Wrong: None Other Activities: None System State on Complete: The database updated the new information of the drink/food.

Functional Brief Description: This allows the admin to delete food/drink Initial Assumption: the admin must be login by admin’s usernames and password Step-By-Step Description: Admin log in to the system by usernames and password . The system will check , if the usernames and password is right , the system will go to the “admin manager’s page” The admin will choose “menu” button in the admin manager page, choose the food/drink that the admin want to remove. The admin click on “delete” button. The admin send an remove-items request to the system. The system will remove food/drink information in the database. The system will update the information and displays the successful message. What Can Go Wrong: None Other Activities: None System State on Complete: The database updated the new information of the drink/food.

Non-Functional A/ Product Requirements Requirement Description 1 Ease of use The website should be clearly , modern interface , simple to understand. 2 Fast When the customer access to the websites, the time is 3-4 seconds to load the information and the completed interface. 3 Memory and CPU usage The content only have the main picture of the shop , the customer can use the websites fast and smooth.

Non-Functional B/ Organization Requirements Requirement Description 1 Website platform The environment is JSP method and run on Java Web Server (tomcat …) 2 Database System The website must use MySQL Community Server. 3 User Groups There are five types of users: Guest, Member and Administrator.

Non-Functional C/ External Requirement Requirement Description 1 Item Illegal The website must use legal items. The system will be acceptable to users and the general public

7. System Modelling

State Diagram

8. Risk analysis Project Risks Product Risks

Project Risks Risk Probability Effects Illness in staff Low Serious Interpersonal difficulties within team that are not easily solved Tolerable Design problems that take a long time to resolve High Poor communication within team that creates Inconsistencies Project is too large and will take too long to Complete Catastrophic Requirements change Members do not know web programming method and security method

Product Risks Risk Probability Effects Program does not do what client expects Low Serious Program too complex for client to use Hacker High