1. ROBUST MARKETING

2. RM TEAM MEMBER Mr.TrungNT Supervisor DucMA Developer HaDV QA & Tester Leader HuongPM QA & Tester TungNT Developer AnhND Project Manager Technical Leader

3. 1 Introduction 2 Project Background 3 Project Management Plan 4 Requirement Specification 5 Software Design 6 Testing 7 Lesson Learned 8 Demo 9 Q&A Content

4. Project Background Common information Project name: Robust Marketing Project code: RM Project Lifetime: 6/1/2014 - 17/4/2014

5. Can not control the quality of the marketer Evaluation of customer tastes inaccurate Project Background Problems

6. QuậnSố lượng nhân viên chăm sóc khách hàng Số lượng nhân viên giao hàng Giám sát Ba Đình441 Cầu Giấy331 Đống Đa331 Hoàn Kiếm441 Thanh Xuân331 Long Biên441 Hai Bà Trưng331 Tây Hồ331 Project Background Statistics the number of marketer in the district Source: Internal of Hữu Nghị Food in 12/2013

7. Project Background The Idea

8. Project Background The Idea This system provides methods to collect data from customers with new approach.

9. Project Background Existing Systems http://gps.vietmap.vn/giai-phap/taxi

10. Proposal System

11. System solves the problem of managing marketer The system support to collect data of market more effective Objective

12. Success Criteria The project was completed on time Tracking system is working Team member is communication good Statistic system is working Mobile system is working Complete use case of normal user

13. Project Management Plan Software Process Model

14. Project Management Plan Team Work Time: 6 hours/day, 5 days/week Location: School, home… Communication: Meeting supervisor: Once a week Team building: Once a month

15. Project Management Plan Development Tools Balsamiq mockup tool Ver 2.2.21 Web server Ver 7.0.52 Juno Ver 2010 Database Ver 5.6.14 Subversion web tool Log bug web tool Ver 6.8.0

16. Project Management Plan Technology Ver 3.0.5 Android tracking library Ver 4.2.2 Ver 2.0 Front-end framework

17. Project Management Plan WBS and Gantt Chart

18. Project Risk Management

19. Requirement Specification Use case diagram

20. Home Requirement Specification Main Function - Web App

21. Login Requirement Specification Main Function - Web App

22. Admin – Add user Requirement Specification Main Function - Web App

23. Admin – List of user Requirement Specification Main Function - Web App

24. Manager – Add shop Requirement Specification Main Function - Web App

25. Manager – Add shop Requirement Specification Main Function - Web App

26. Manager – Assign shop for user Requirement Specification Main Function - Web App

27. Manager – Add task Requirement Specification Main Function - Web App

28. Manager – Tracking Requirement Specification Main Function - Web App

29. Marketer – Receive work Requirement Specification Main Function - Mobile App

30. Marketer – Product Introduction Requirement Specification Main Function - Mobile App

31. Customer – Feedback Requirement Specification Main Function - Mobile App

32. Marketer – Submit work Requirement Specification Main Function - Mobile App

33. Web App Availability The system available for service when requested by end- users. Maintainability Coding convention, source structure Usability The system has friendly interface and easy to use Security User is authorized, password is encrypted by SHA_256 Performance Response time should be less than 3 seconds. Requirement Specification Non-function Requirement

34. Mobile App Availability Always run app successfully when end-user start Maintainability All code must be clearly commented. The design of the system must be loosely coupled. Performance Codding convention, error logging Compatibility The app is designed for mobile. Requirement Specification Non-function Requirement

35. Web App Software Design Architecture Overview

36. Mobile App Software Design Architecture Overview

37. Web App-Manage task Software Design Class Diagram

38. Mobile App-Submit task Software Design Class Diagram

39. Web App-Manage task Software Design Sequence Diagram

40. Mobile App-Submit task Software Design Sequence Diagram

41. Software Design Database Diagram

42. Testing Process

43. Testing Stages

44. Testing Types GUI testing Function testing Regression testing Acceptance testing

45. Web App Mobile App Testing Enviroment Galaxy SIII FireFox 28

46. Testing Log bug

47. Testing Result (base on test case) ComponentNo. of test cases Result Round 1Round 2Round 3 PassFailNo of bugs PassFailNo of bugs PassFailNo of bugs GUI58391913481095800 Function2111149758140713021100 Total35623012679271854335600

48. Lesson Learn Working in group: Communication Resolve conflicts Technologies: Spring Framework JPA Gmap API Apache Tiles Boostrap Twitter Mytrack Management skills: Organize Negotiate Planing