1. TEACHER FEEDBACK WEBSITE HTVN TEAM

2. AGENDA 1.TEAM INTRDUCTION 2.PROJECT OVERVIEW 3.PLAN 4.PRODUCT ARCHITECTURE 5.DATABASE DESIGN 6.TEST PLAN & TEST REPORT 7.REFLECTION 8.DEMO 9.QUESTIONS AND ANSWERS HTVN TEAM

3. TEAM MEMBER HTVN TEAM

4. Roles of team members HTVN TEAM RoleParticipant(s) MentorTam Thanh Thi Nguyen Project ManagerHung Phi Cao ProgrammerNam Nhat Nguyen Thanh Thuy Thi Le TesterNam Nhat Nguyen Thanh Thuy Thi Le Vu Xuan Nguyen ReviewerHung Phi Cao DesignerHung Phi Cao Nam Nhat Nguyen Thanh Thuy Thi Le Vu Xuan Nguyen AnalystHung Phi Cao Nam Nhat Nguyen Thanh Thuy Thi Le Vu Xuan Nguyen

5. TEAM GOALS Learn XP process and follow XP. Learn how to write document. Learn what and how to communicate between members. HTVN TEAM

6. AGENDA 1.TEAM INTRDUCTION 2.PROJECT OVERVIEW 3.PLAN 4.PRODUCT ARCHITECTURE 5.DATABASE DESIGN 6.TEST PLAN & TEST REPORT 7.REFLECTION 8.DEMO 9.QUESTIONS AND ANSWERS HTVN TEAM

7. PROJECT IDEAS Student do teacher feedback more easily. Teacher will change teaching method to suitable for students. Students will benefit from the evaluation of teachers. HTVN TEAM

8. XP Process HTVN TEAM

9. XP - The 12 Principles 1. Planning project. 2. Small releases. 3. Metaphor. 4. Simple design. 5. Testing. 6. Refactoring. 7. Pair programming. 8. Continuous integration. 9. Collective ownership. 10. On-site customer. 11. 40-hour weeks. 12. Coding standards HTVN TEAM

10. AGENDA 1.TEAM INTRDUCTION 2.PROJECT OVERVIEW 3.PLAN 4.PRODUCT ARCHITECTURE 5.DATABASE DESIGN 6.TEST PLAN & TEST REPORT 7.REFLECTION 8.DEMO 9.QUESTIONS AND ANSWERS HTVN TEAM

11. AGENDA 1.TEAM INTRDUCTION 2.PROJECT OVERVIEW 3.PLAN 4.PRODUCT ARCHITECTURE 5.DATABASE DESIGN 6.TEST PLAN & TEST REPORT 7.REFLECTION 8.DEMO 9.QUESTIONS AND ANSWERS HTVN TEAM

12. Architectural Drivers HTVN TEAM

13. Architectural Drivers Business constraints: Project begins from August 31th, 2010 to November 24th, 2012. The HTVN team has no budget for commercial software. Resource availability is defined below: 31/8 – 12/12, 4 members x 14 hours x 12 weeks. HTVN TEAM

14. Architectural Drivers Technical constraints: Technology: Microsoft Visual Studio 2012, Microsoft SQL Server 2008. Network : Internet OS: Windows XP/ Vista/ 7 / 8 Framework Tool:.NET framework 4.0+, ASP.NET, C#. Server hardware: Ram: Min 512M, HDD: Min 40GB, CPU: Intel or AMD. HTVN TEAM

15. Architectural Drivers Functional requirements: Log in Log out Student do feedback Teacher view feedback Feedback management User management Class management HTVN TEAM

16. Architectural Drivers Quality Attribute: Usability Performance Modifiability Scalability Security Availability HTVN TEAM

17. System Context Diagram HTVN TEAM

18. C&C VIEW HTVN TEAM

19. MODULE VIEW HTVN TEAM

20. ALLOCATION VIEW HTVN TEAM

21. AGENDA 1.TEAM INTRDUCTION 2.PROJECT OVERVIEW 3.PLAN 4.PRODUCT ARCHITECTURE 5.DATABASE DESIGN 6.TEST PLAN & TEST REPORT 7.REFLECTION 8.DEMO 9.QUESTIONS AND ANSWERS HTVN TEAM

22. Figure : Entity relationship diagram of TFW DATABASE DESIGN HTVN TEAM

23. AGENDA 1.TEAM INTRDUCTION 2.PROJECT OVERVIEW 3.PLAN 4.PRODUCT ARCHITECTURE 5.DATABASE DESIGN 6.TEST PLAN & TEST REPORT 7.REFLECTION 8.DEMO 9.QUESTIONS AND ANSWERS HTVN TEAM

24. TEST TYPES Unit testing Function testing Integration testing Regression testing Acceptance testing HTVN TEAM

25. TEST LIST HTVN TEAM

26. TEST REPORT HTVN TEAM

27. AGENDA 1.TEAM INTRDUCTION 2.PROJECT OVERVIEW 3.PLAN 4.PRODUCT ARCHITECTURE 5.DATABASE DESIGN 6.TEST PLAN & TEST REPORT 7.REFLECTION 8.DEMO 9.QUESTIONS AND ANSWERS HTVN TEAM

28. 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. HTVN TEAM

29. 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. HTVN TEAM

30. 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. HTVN TEAM

31. 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. HTVN TEAM

32. 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. HTVN TEAM

33. 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? HTVN TEAM

34. Reflection 7  Negatives Workload balance among teams were not even. Get trouble in write technical documents. During do Capstone, we work and study simultaneously so time is not ensure. Spend a lot of time learning XP process. Sometimes conflict between members. HTVN TEAM

35. AGENDA 1.TEAM INTRDUCTION 2.PROJECT OVERVIEW 3.PLAN 4.PRODUCT ARCHITECTURE 5.DATABASE DESIGN 6.TEST PLAN & TEST REPORT 7.REFLECTION 8.DEMO 9.QUESTIONS AND ANSWERS HTVN TEAM

36. THANK YOU! HTVN TEAM

37. QUESTION & ANSWER