1. Records Registration Management System The HOB Capstone Project

2. WHAT IS PROJECT? OUR

3.  Nguyễn Thế Đức  Trần Thị Mộng Hà  Tạ Quang Hiệp  Bùi Huỳnh Kinh Luân  Nguyễn Tiến Luân  Nguyễn Trần Hồng Phúc Owner – The team

4. Information mentor  Mentor: Mr. M.S. Bùi Minh Phụng  Development Assistant: Mr. Đinh Đức Trí  Software Development VLU Center

5. 1. Project Presentation 2. Demonstration 3. Reflection 4. Question & Answer

6. 1. Project presentation

7. Agenda 1.Project management 2.Project overview 3.Requirements - Constraints 4.Quality attribute 5.Architecture 6.Quality control - Test

8. Project management Process Timeline Measurement Configuration management

9. Process

10. Process apply ACDM

11. Timeline

12. Measurement  Time: 5726 hour  Time week: 31 hour/ week  Change log: 12  Issue: 23

13. Configuration management Use Tortoise SVN as repository of project, combination with communication by email (Gmail) and each team member must have Google email. It provided by Google with the address: www.code.google.com SVN Final Process forder Process folder... Old Process forder Process folder... Other

14. Project overview Problems of VLU Problems in enrollment Solution Scope Stakeholder

15. Problems of VLU VLU has 13 departments have been distributed in 2 campuses separated by 10 km of the flight of birds. So communication between departments and faculties are quite inconvenience mainly through documents or excel file.

16. Problems in enrollment Admitted student list send by Training Department through email. Receive student's records by Excel file. Report to Dean, Principal by email. Input records information by Excel file.

17. Solution An application installed on the computer using the Windows operating system in Departments. Website are used to view statistical reports about enrollment status of new students.

18. Scope Perform system development allows Van Lang University receiving records management. This development project is developed within 30 weeks. The project is a 6-member group of the Department of Information Technology development projects aimed at protecting and developing graduate management software for universities.

19. Stakeholder Customer: Users: Department staff of VLU (Delegate: Department staff of IT & Accounting – Auditing) Admin: Staff of Software Development VLU Center Support and development consultancy: Software Development VLU Center

20. Requirements - Constraints System context RRMS modules Use case Constraints

21. System context

22. RRMS modules RRMS Receiving Records Management Records Detail Management System Management Statistic (Website)

23. Use case

24. Constraints Business Constraints Our team has worked to finish this project for 30 weeks. Working time average of 30-35 hours per individual. Members of this project team will not change the entire project, unless specifically indicated from the instructor. Technical Constraint Develop application runs on Windows XP or higher

25. Quality attribute Discover QA  Detailed scenarios  Priority ranking

26. QA: Performance System receives requirements from users and response results quickly, especially in functions: Print and save the records receipt View and search the list of students View and search records list

27. QA: Usability The user interface is designed for easy looks, easy to operate, the function buttons are arranged scientists help users become easy to familiar and manipulate. Input interface simple and effective instead of entering data in excel file as before to help save time.

28. QA: Availability Records receiving action always continuous during rush hour when there are many access Records receiving action does not stopped in Campus 2 in case of loss of connection with the base 1 when there is error due to power outage or transmission error.

29. Architecture Physical view Static view C&C view Data model

30. Physical view

31. Static view (App)

32. Static view (Web)

33. C&C view

34. C&C view (App)

35. C&C view (Web)

36. Data model

37. Quality control - Test Test process Test result

38. Test process The project was carried out through two testing phases:  Alpha Testing: Improve the quality of the product and ensure beta readiness. Toward the end of a development process when the product is in a near fully-usable state.  Beta Testing: Improve the quality of the product, integrate customer input on the complete product, and ensure release readiness. Just prior to launch, sometimes ending within weeks or even days of final release.

39. Test process Beta Testing Alpha Testing

40. System test result Total Number of Test Cases: 128 Total Number of Test Cases Executed: 128 Total "Pass" Test Cases: 128 Total "Failed" Test Cases: 0

41. Acceptance test result Received confirmation of two faculty representatives are users of Information Technology and Accounting - Auditing department. In addition, the system administrator has the positive feedback when trying to use the system. Pass 100% requirement confirmed the initial.

42. 2. Demonstration

43. 3. Reflection Teamwork Management & Planning Technical: Coding skill of members are not equal Mentor enthusiastic support, but the communication channel between the group and mentor has not been used effectively.

44. 4. Question & Answer

45. THANKS YOUR LISTENING !