KFC VIETNAM ORDER SYSTEM

1. DUY TAN UNIVERSITY INTERNATIONAL SCHOOL KFC VIETNAM ORDER SYSTEM HTC TEAM

2. AGENDA TEAM INTRODUCTION PROJECT OVERVIEW PLAN PRODUCT ARCHITECTURE DATABASE DESIGN TEST PLAN & TEST REPORT REFLECTION DEMONSTRATION QUESTIONS AND ANSWERS HTC TEAM

3. TEAM INTRODUCTION Mentor 1: Son Van Phan Mentor 2: ToanDuc Vo HTC TEAM

4. TEAM MEMBERS HTC TEAM

5. Roles of team members HTC TEAM

6. TEAM GOALS Learn XP process and follow XP process. Learn how to write document. Learn what and how to communicate between members. Create a product follow customer’s requirement. HTC TEAM

7. AGENDA TEAM INTRODUCTION PROJECT OVERVIEW PLAN PRODUCT ARCHITECTURE DATABASE DESIGN TEST PLAN & TEST REPORT REFLECTION DEMONSTRATION QUESTIONS AND ANSWERS HTC TEAM

8. PROJECT IDEAS Customers view and order KFC’s dishes from anywhere within a radius of 20km from 9am to 9pm. Saving time for customers. KFC Vietnam Stores can handle their order and expand their market share on android device. HTC TEAM

9. XP Process HTC TEAM

10. AGENDA TEAM INTRODUCTION PROJECT OVERVIEW PLAN PRODUCT ARCHITECTURE DATABASE DESIGN TEST PLAN & TEST REPORT REFLECTION DEMONSTRATION QUESTIONS AND ANSWERS HTC TEAM

11. MILESTONES HTC TEAM

12. BURNDOWN CHART OF DEVELOPING RELEASE HTC TEAM

13. EFFORT EVALUATION HTC TEAM

14. AGENDA TEAM INTRODUCTION PROJECT OVERVIEW PLAN PRODUCT ARCHITECTURE DATABASE DESIGN TEST PLAN & TEST REPORT REFLECTION DEMONSTRATION QUESTIONS AND ANSWERS HTC TEAM

15. Architectural Drivers HTC TEAM

16. Architectural Drivers Business constraints: • Project begins from March 8th, 2013 to May 14th, 2013 with 5 members. • The product follows customer’s requirements. HTC TEAM

17. Architectural Drivers Technical constraints: • Technology: Microsoft Visual Studio 2012, MySQL Server 5.1.57 , Eclipse with Android SDK. • Network : Internet. • OS: Windows XP SP3/ Vista/ 7 / 8. • Framework Tool: .NET framework 3.5+ , Java Runtime Environment, Android 3.0.3 or higher. • Server hardware: Ram: Min 512M, HDD: Min 40GB, CPU: Intel or AMD. HTC TEAM

18. Architectural Drivers Functional requirements: • Client Side • Registration • Log in • Log out • Profile Management • Route Map • Search • Ordering the dish • Favorite List • Cart Management HTC TEAM

19. Architectural Drivers Functional requirements: • Server Side • Role Management • User Management • Order Management • Dish Management • Cities Management • Policies Management • Branch Management HTC TEAM

20. Architectural Drivers Quality Attribute: • Availability • Performance • Security • Capability • Usability HTC TEAM

21. System Context Diagram HTC TEAM

22. C&C VIEW HTC TEAM

23. MODULE VIEW HTC TEAM

24. ALLOCATION VIEW HTC TEAM

25. AGENDA TEAM INTRODUCTION PROJECT OVERVIEW PLAN PRODUCT ARCHITECTURE DATABASE DESIGN TEST PLAN & TEST REPORT REFLECTION DEMONSTRATION QUESTIONS AND ANSWERS HTC TEAM

26. DATABASE DESIGN HTC TEAM Figure : Entity relationship diagram of TFWEntity relationship diagram of KFC Vietnam Order System

27. RELATION DIAGRAM MODEL Relation diagram model of KFC Vietnam Order System HTC TEAM

28. AGENDA TEAM INTRODUCTION PROJECT OVERVIEW PLAN PRODUCT ARCHITECTURE DATABASE DESIGN TEST PLAN & TEST REPORT REFLECTION DEMONSTRATION QUESTIONS AND ANSWERS HTVN TEAM

29. TEST TYPES Unit testing Function testing Integration testing Regression testing Acceptance testing HTC TEAM

30. TEST LIST HTC TEAM

31. TEST REPORT HTC TEAM

32. AGENDA TEAM INTRODUCTION PROJECT OVERVIEW PLAN PRODUCT ARCHITECTURE DATABASE DESIGN TEST PLAN & TEST REPORT REFLECTION DEMONSTRATION QUESTIONS AND ANSWERS HTC TEAM

33. Reflection 1 • What we did well? • Identifying task was helpful for focusing the followed XP process. • Analyzing, designing and coding are made simultaneously. • Writing technical documents. • Understanding how to workgroup together. HTC TEAM

34. Reflection 2 • What we did well? • Meeting with mentor to figure out problems and how to solve the problems. • Initially, effort for unplanned tasks was not tracked. Now, planning is more accurate. • Complete the project on schedule. HTC TEAM

35. Reflection 3 • What we didn’t well? • Spent more time than plan. • Need rule for process assessments. • Lacked of an on-site customer (as desired by XP) because customer was busy. • Initially, got trouble in XP process, sometimes mistake with other processes. HTC TEAM

36. Reflection 4 • What we didn’t well? • We have not analyzed the relevancy of performed tasks at the end of sprints. • Need to make more metrics visible. • Project was behind schedule but was then recovery. HTC TEAM

37. Reflection 5 • Positives • Adequate understanding of business drivers and System Architecture. • Better understanding what is XP and how to apply XP in a real environment. • Understanding the role of a mentor who has an influence on guiding & coaching students. HTC TEAM

38. Reflection 6 • Positives • Independent work help us to promote the full potential of each member. • Change thinking, and know how an actual software engineer must do, what actual skills? HTC TEAM

39. Reflection 7 • Negatives • Getting troubles when writing technical documents. • Sometimes conflicting happen between team’s members. HTC TEAM

40. AGENDA TEAM INTRODUCTION PROJECT OVERVIEW PLAN PRODUCT ARCHITECTURE DATABASE DESIGN TEST PLAN & TEST REPORT REFLECTION DEMONSTRATION QUESTIONS AND ANSWERS HTC TEAM

41. DEMONSTRATION HTC TEAM

42. THANK YOU! HTC TEAM

43. QUESTION & ANSWER HTC TEAM