TEAM TEACUP 2006 CAMBODIAN RESTAURANT PROJECT LOCAL TEAMEXTENDED US TEAMEXTENDED INDIAN TEAM...

TEAM TEACUP 2006

CAMBODIAN RESTAURANT PROJECT

LOCAL TEAMEXTENDED US TEAM EXTENDED INDIAN TEAM

Jonathan Lee - Team Leader Jonathan Lee - Team Leader Kelum Wick - Quality Kelum Wick - Quality Nick Rudzwick - Communication Nick Rudzwick - Communication Ricardo Viera - DocumentationRicardo Viera - Documentation

Sam Ath Ouch -Team Leader Sam Ath Ouch -Team Leader Ly Chea -Quality Ly Chea -Quality Kimheng Sok -Communication Kimheng Sok -Communication Samvannak Samon -DocumentationSamvannak Samon -DocumentationSovanndara Chheng -LocalizationSovanndara Chheng -Localization

Anushree Dixit -Database Design Anushree Dixit -Database Design Vikrant Arora -Database DesignVikrant Arora -Database Design

RESPONSIBLE BY

Prof. Sopheap Seng Prof. Chanthearith HUONProf. Christelle Scharff

ACADEMIC YEAR: 2005 ~ 2006

OUTLINE1. INTRODUCTION

Project DescriptionExtended team and the software systemFunctional and Non-functional requirements

2. CLIENT ROLESProject MilestonesProcess of the projectSoftware showCompare US and Indian Students softwareTop 10 things to keep client happyTop 10 things make client unhappyTop 10 things making a good client

3. EXPERIENCE IN TEAMWORK

Interaction with PACE studentsDifficulty

4. GLOBAL SOFTWARE DEVELOPMENTOur project & Real lifeComment for the developerPersonal experience

5. CONCLUSION Evaluation of both software

/20

1. INTRODUCTION | Project Description | Extended team and the software system | Functional & Non-Functional Requirements |

Project Description

June, 2006

Objective:

We would like to have a web-based application that could help usto sell the food online in Phnom Penh with the delivery service.

The users of the software are:

Administrator of the restaurant Managers of the restaurant Receptionists of the restaurant Clients of the restaurant Internet Users ( Lambda Users )

Duration:

Start from : Jan 24, 2006 Until : May, 2006

CAMBODIAN RESTAURANT PROJECT


Extended team and the software system

Jonathan Lee Jonathan Lee Team LeaderTeam Leader

Kelum WickQuality Leader

NickRudzwick Communication Leader

Ricardo VieraDocumentation Leader

The CASE-Tools US team used for this project were:

Microsoft Word and PowerPoint for the Documents and Presentation. The Java Programming Language (Servlets) Eclipse and JCreator. Dreamweaver 8 and HTML and WordPad for the website. MYSQL was used in the construction of the databases.

Page 2/20June, 2006


Functional & Non-Functional Requirements

– Register (Lambda User)– Place Order (Client)– Check Order Status (Client)– Cancel Order (Client)– Leave and View Feedback (Client, Manager/Admin)– View List of Pending and Completed Orders (Receptionist, Manager)– View Financial and Customer Information (Manager)– Create and delete accounts (Client, Admin)– View Menu (Client, Receptionist/Manager/Admin)– Log in and Log out (Client/Receptionist/Manager/Admin)– Request and View Menu Change (Manager, Admin)– Update Menu (Admin)– Change Profile (Client/Receptionist/Manager/Admin)– View all account information (Admin)

– Website Security (High Priority)– Language Preference (Medium Priority)– Website Layout/Easy to Use Interface (High Priority)– Alert Messages (Medium Priority)

Functional Requirements

Non-Functional Requirements

Page 3/20June, 2006

2. CLIENT ROLES | Project Milestones | Process of the Project | Software show | Compare US and Indian students software |

Project Milestones

Team bonding and initialization of communications (1 week)

Requirements (4 weeks)

Design (4 weeks)

Mid-semester presentations

Implementation (2-3 weeks)

Testing (1-2 weeks)

Presentations (Last week of class)

Page 4/20June, 2006

2. CLIENT ROLES | Project Milestones | Process of the Project | Software show| Compare US and Indian students software |

Requirements Phase

Page 5/20June, 2006

Objective:

Stakeholder Functional & Non-Functional Requirements

Communication:

Confirm about some problems that need to be avoid Answering Questionnaire which was sent by US students Answering mail and discuss in the conference Make sure that the developer understand what is needed Help developer to find out the solution of how the software works

by giving comments

Annex:

URL of the other online restaurants Pictures of the foods, map and logo of the restaurant Menu in PDF format

Post the blog and do the survey Validate the requirements document


Design Phase

Page 6/20June, 2006

Communication: • Answering mail and discuss in the conference• Keep discussing about the points that were not clear

Modification:

• Add some new features to make the software more accurate• Remove some features which were not important• Try to encourage the extended team to share the work that they have done, even though it wasn’t completed yet, in order to make the project go smoothly and correctly

Annex:

Index page (How it looks like) Contact page

Post the blog and do the survey View the design and GUI documents Validate the design document


Testing Phase

Page 7/20June, 2006

Testing: • Test the software of Cambodian Restaurant• Post the bug to share about the points that were not well done enough• Giving the comment about the interface and the quality of the software, how the software should improve• Accept or Reject the software by giving the good points and bad points

Validation:

• US students software• Indian students software• Compare both software

http://rest.tomchuk.com/wiki/CompletedWork/


Software developed by US Students

Page 8/20June, 2006

STRONG POINTS • The interface is acceptable• Most of the features were done well• Good security protection• Good navigator and links• All the page title are clearly shown• Respect the deadline

WEAK POINTS

• Type exception were not done well• The error message was not fulfill• Something which were told in the conference were lack

RESULT

WE ACCEPT THIS SOFTWARE.

http://matrix.csis.pace.edu/~s06-cs389-s11/


Software developed by Indian Students

Page 9/20June, 2006

STRONG POINTS

• The interface is acceptable• Good at database design• Even 2 members in the team, but could provide the software

WEAK POINTS

• Type exception were not done well• The error message was not fulfill• Most of the features were not done well• Security fail• The web page isn’t well organized• Didn’t satisfy the our desire

RESULT

WE REJECT THIS SOFTWARE.

http://csdb.du.ac.in:8090/restaurant_india/


Comparison of both software

Page 10/20June, 2006

Among both software which were done by US and Indian students:

We prefer the software of US students, because the software that had been developed respected what we need. Most of the features and most of the things that we were working together through answering mail and discussing were included

We don’t accept the software of Indian students, it doesn’t mean that they didn’t respect our desire. In fact, we didn’t contact with Indian students, even mail or face to face. We can’t say that they did bad job or anything. The point is that, the security of the software were not done well and there were also many error on some features.

NOTE: Thanks to Indian students anyway for their hard work

2. CLIENT ROLES | Top 10 things to keep client happy |Top 10 things make client unhappy | Top 10 things make a good client |

Top 10 things to keep client happy


Client’s comments were taken in action Provide more service available Show the capacity of hard working and serious about the project Good interaction between developer and client Provide the document necessary of the work that have done Before changing anything about the software, let’s client knows first Find out the good solution to replace the thing that had been changed Respect the deadline of the project Result of the software should adapt with client desire The price of creating the software is suitable


Top 10 things make client unhappy


Changing the features of the software without any reasons Not good relationship between clients and developers Incapable of doing the project Quality of the software( Many errors, web page isn’t interesting) Lost contact during the project Misunderstanding the desire of client Not taking serious about develop the project Not respect the deadline of the project Result of the software not adapt with client desire Make client feel that they lost the time and resource


Top 10 things make a good client


Good at explaining about the problem and the need Know something about how the project work Providing the resource available Answering the developer’s question as quickly as possible Be patient on waiting for the software Encouraging the developer to work hard Make the developer feel happy when they do good things Giving the comment when they do something not adapt with our desire Be prepare enough time for the developer, so that the developer could

have enough time to correct the bug or to create a new one with some conditions (ex. Reduce the price of the software)

If the client could know something about the informatics

3. EXPERIENCE IN TEAMWORK

Reports

| Interaction with PACE Students |Difficulty|


Number of Mails: Feb =17, Mar = 40, Apr = 24, May = 20

Online Meeting: 6 times (Jan 26, Feb 04, Feb 25, Mar 23, Apr 01, Apr 27)

Website using :

http://www.itc.edu.kh/http://www.csis.pace.edu/~scharff/cs3892006 (Prof scharff webpage)http://teamteacup2006.i8.com/ (webpage for teamteacup)http://blogger.com (website to create the blog)http://restaurantproject2006.blogspot.com/ (Post the blog)http://www.zoomerang.com/survey.zgi?p=U24E9SC4D4D6 (survey)http://www.zoomerang.com/survey.zgi?p=WEB22527X7G588 (survey)http://www.questionpro.com/akira/TakeSurvey?id=402682&rd=4765075 (survey)http://www.csis.pace.edu/~scharff/cs3892006/PASSWORD/FEEDBACK/restaurantdesign.zip ( login: alllogin /password: gsd123/ Feedback)http://www.youtube.com/watch.php?v=jQaHrcwKsoc (video of Thomas Friedman entitled "The other side of outsourcing")http://www.yousendit.com/ ( This service permits us to share files (up to 1GB)http://matrix.csis.pace.edu/~s06-cs389-s11/ (online restaurant website)http://rest.tomchuk.com/wiki/CompletedWork (Bug reports)http://csdb.du.ac.in:8090/restaurant_india/ (Website Indian)

3. EXPERIENCE IN TEAMWORK | Interaction with PACE Students |Difficulty|

Difficulty


The different of geometric time (12hours different)

We don’t have the internet service at home

Few time after school going to the internet café to response the mail

Unaware about the process of the project, What is our responsibility in each phase

Difficult to explain in distance and solve the problem in a short time

Take many days to check, discuss and response mail

4. GLOBAL SOFTWARE DEVELOPMENT | Our Project & Real life | Comment for the developer | Personal experience |

The Quality of our software


Good security is the main point of our software

Most of the features that is needed respect the desire

Medium interface human and machine

Even though we have completed our project successfully with the acceptable result, but it doesn’t mean that we could use this software in public

In reality, our software isn’t completely done yet

The modification of the software is needed


How to improve our software ?


Though our experience in this project we have notice some main points to improve our software :

• The requirement phase is the most important in the project (Client desire should clarify here, not at the design phase)• In the beginning of the design phase should think about the problem that was not complete in the requirement phase• Good communication skill between client and developer is needed• Division of the duty for each member is also an important thing • Abilities to solve the problems when we face in coding phase • Try to find out the bug as much as possible and correct them immediately• Work more harder to finish the project on time with the result coming


Experiences of local team


Team Leader related to team work leadership skill

Quality Leader validate the document relationship in the team

Communication Leader communication skill responsible for information distribution

Documentation Leader keep all the documents of the project be sure that all members in the group have the document needed

Localization Leader join team activities test the software

5. CONCLUSION | Evaluation of both software |Gratitude |

Acceptation or Reject the software


As a result of the final phase in our project

• We accept the software that was done by US team• We reject the software that was done by Indian team

5. CONCLUSION | Evaluation of both software |Gratitude |

Gratitude


Professor Sopheap and Professor Scharff Professor Thearith, Professor Longchrea and others Professors Extended team US students and Indian students Local team Cambodian students

Good luck for every body !!!THANKS YOU

TEAM TEACUP 2006 CAMBODIAN RESTAURANT PROJECT LOCAL TEAMEXTENDED US TEAMEXTENDED INDIAN TEAM...

Documents

Transcript of TEAM TEACUP 2006 CAMBODIAN RESTAURANT PROJECT LOCAL TEAMEXTENDED US TEAMEXTENDED INDIAN TEAM...