Topic Cafeteria Management SystemGROUP :

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. 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 ConstraintsTime: 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 OrganizationThe 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 ResourceAll 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 ResourcesCafeteria Management System is created by using java, with functions and small database, so we just need an average sever.

4. Work Breakdown.Task No Task Name

Duration

(days)Engineers

Estimated

Completion Date

T1Introduction

  1Hung Oct 1, 2012

T2Project organization

  1Hung Oct 2, 2012

T3Source requirement

  1Linh Oct 3, 2012

T4Work breakdown

  1Linh Oct 4, 2012

T5Project schedule

  1Linh Oct 5, 2012

T6System requirement

  5Linh Oct 10, 2012

T7System architecture

  5Du Oct 15, 2012

T8Risk analysis

  1Du Oct 16, 2012

T9System Designing

  3Team Oct 22, 2012

4. Work Breakdown.T10

Object Interface Specification (sprint cycle

1)

 

1

Linh, Du Oct 23, 2012

T11Graphic User Interface (sprint cycle 1)

  1Du, Nhật Oct 24, 2012

T12Design/Development issues (sprint cycle 1)

  3Nam, 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)Register function

 2

Nam(coder), Nhật

 

Nov 2, 2012

T15

Project Implementation (sprint cycle 1)Login function 

2

Nam(coder) , Du

 

Nov 4, 2012

T16

Project Implementation (sprint cycle 1)

Order function  

2

Nam(coder) , Du Nov 6, 2012

T17Testing and Validation

(sprint cycle 1)1

Hùng Nov 7, 2012

4. Work Breakdown.T18

Object Interface Specification (sprint cycle 2)

1Linh, Du, Hùng Nov 8, 2012

T19Graphic User Interface

(sprint cycle 2)1

Nhật, Nam Nov 9, 2012

T20Design/Development issues

(sprint cycle 2)1

Linh, Du, Nam Nov 10, 2012

T21Domain Requirement

Design/Development(sprint cycle 2)

1Du, 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  

2

Linh(coder), Hùng Nov 13, 2012

 

Project Implementation (sprint cycle 2)Remove Item Function 

1Du (coder), Nhật Nov 14,2012

 

Project Implementation (sprint cycle 2)Manage Report Function 

2Nam(coder), Nhật Nov 16, 2012

 

Project Implementation (sprint cycle 2)Manage Cart Function 

2Du(design), Nam(code), Hùng Nov 18, 2012

 

Project Implementation (sprint cycle 2)Manage Payment method Function 

2Du(design), Nam(code), Nhật Nov 20, 2012

T21Testing and Validation

(sprint cycle 2)1

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 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

FunctionalBrief Description: This allows the admin to add the new food/drink

Initial Assumption: the admin must be login by admin’s usernames and passwordStep-By-Step Description:1. 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”

2. The admin will choose “menu” button in the admin manager page, choose “add new food/drink”

3. The admin input the information of the new food/drink4. The admin send an adding request to the system by choosing “update”

button5. 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.

FunctionalBrief Description: This allows the admin to update the information of the store

Initial Assumption: the admin must be login by admin’s usernames and passwordStep-By-Step Description:1. 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”

2. The admin will choose “menu” button in the admin manager page, edit the information.

3. The admin send an update request to the system by choosing “update” button

4. 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.

FunctionalBrief Description: This allows the admin to delete food/drink

Initial Assumption: the admin must be login by admin’s usernames and passwordStep-By-Step Description:1. 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”

2. The admin will choose “menu” button in the admin manager page, choose the food/drink that the admin want to remove.

3. The admin click on “delete” button.4. The admin send an remove-items request to the system. The system will

remove food/drink information in the database.5. 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.

2Fast

When the customer access to the websites, the time is 3-4 seconds to load the information and the completed interface.

3Memory 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 platformThe 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 IllegalThe 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 RisksRisk Probability Effects

Illness in staff Low Serious

Interpersonal difficulties within team that are

not easily solved

Low Tolerable

Design problems that take a long time to resolve High Serious

Poor communication within team that creates

Inconsistencies

High Serious

Project is too large and will take too long to

Complete

High Catastrophic

Requirements change High Serious

Members do not know web programming method and security

method

High Serious

Product RisksRisk Probability Effects

Program does not do what client expects Low Serious

Program too complex for client to use Low Serious

Hacker High Serious