1. Moon Fleet Management Six Sigma Supervisor: Nguyễn Trường Long Members: - Lê Hoàng - Nguyễn Đăng Phượng - Nguyễn Thanh Tùng - Phạm Phương Duy - Vũ Quang Hưng - Phạm Út Lan

2. CONTENT A.Introduction 1.Context 2.MFM Solution B.Process 1.Task assignment 2.Requirement 3.Model Application 4.Technology 5.Design 6.Testing 21-Jul-16

3. INTRODUCTION 3

4. Context Fleet Management Enterprises –Lower cost on vehicles –Improve efficiencies –Reduce risks –Improve customer services Citizens –Management of time 1-Jul-164

5. Context Fleet Management System 1-Jul-165

6. MFM Solution Objective: solving following problems: –Lack of a proper system to keep track of large fleet. –Loss of productivity due to inefficient utilization and unauthorized use of vehicles. –Problems with high cost and complicated system 61-Jul-16

7. MFM Solution MFM consists of GPS/GPRS/GIS and Web based Framework, which brings: –An easy to use web based desktop-interface –A widespread, already available communication infrastructure (GPRS) –A client-server solution, which makes everything easier –Open source tools to reduce the system cost: Java, Google Map, etc. –Supported features to interact with existed systems. 71-Jul-16

8. MFM Solution Bounderies of MFM: MFM Solution: –Abstract FM solution of any vehicle –Focus on business domain of bus: planning, scheduling, etc. MFM Project: –A software for managing bus –System consists: »GPS Device (simulator) »Communication Server (simulator) »Central Database »Web based server »Map based server 81-Jul-16

9. PROCESS 9

10. TASK ASSIGNMENT Project Manager (PM) -Planned and kept track of schedule -Assigned tasks for team members Team Leader (TL) -Kept contact with stakeholders -Team building Project Technical Leader (PTL) -Initiated work ground -Led the design phase -Trained members -Solved technical issue Developers -Implemented coding phase -Executed unit test -Participated in other phases Testers -Created and managed test cases and test reports -Executed system test and integration test -Logged and assigned bugs -Participated in other phases 101-Jul-16

11. TASK ASSIGNMENT 111-Jul-16

12. Project Model V-model: 121-Jul-16

13. Requirement Methods: –Reality observing –Learning from current solution. –Asking experts. –Researching based on documents, senior’s ideas. 131-Jul-16

14. Requirement Main requirements: –Tracking vehicle –History reviewing –Reporting feature –Managing: Schedule Vehicle Driver Route GPS Device –Administration 141-Jul-16

15. Design Choice of system Architecture Problems: –Human related –System 151-Jul-16

16. Design 161-Jul-16

17. Design Component diagram 171-Jul-16

18. Design Persistence –Focus on business –Database independent –Reduce effort 181-Jul-16

19. Design Logging Component 191-Jul-16

20. Technology Servlet, JSP, JDBC, JPA Framework: Struts, Spring, Hibernate, JUnit Database: Oracle 10g Libraries: ExtJS, Google Maps, JasperReport, Poi Others: Eclipse IDE, Apache Subversion, Apache Tomcat 1-Jul-1620

21. Testing Test Plan Test case Test report Defect log TESTING 211-Jul-16

22. TEST PLAN Test Approach -Black Box Testing: Functional Test -Security: Authentication & Authorization -Load Test: Performance Test 221-Jul-16

23. TEST PLAN Test Strategy: V model 231-Jul-16

24. TEST PLAN Test tool: Fire bug (Test TAT) 241-Jul-16

25. TEST CASE Base on Requirement & Design Review & Update Test case Execute Test case Example: 251-Jul-16

26. BUG LIFE CYCLE 261-Jul-16

27. DEFECT Example 271-Jul-16

28. TEST REPORT 281-Jul-16

29. Q & A Thanks for listening! 1-Jul-16