Records Registration Management System The HOB Capstone Project

WHAT IS PROJECT? OUR

 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

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

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

1. Project presentation

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

Project management Process Timeline Measurement Configuration management

Process

Process apply ACDM

Timeline

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

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

Project overview Problems of VLU Problems in enrollment Solution Scope Stakeholder

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.

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

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.

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.

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

Requirements - Constraints System context RRMS modules Use case Constraints

System context

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

Use case

Constraints Business Constraints Our team has worked to finish this project for 30 weeks. Working time average of 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

Quality attribute Discover QA  Detailed scenarios  Priority ranking

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

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.

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.

Architecture Physical view Static view C&C view Data model

Physical view

Static view (App)

Static view (Web)

C&C view

C&C view (App)

C&C view (Web)

Data model

Quality control - Test Test process Test result

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.

Test process Beta Testing Alpha Testing

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

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.

2. Demonstration

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.

4. Question & Answer

THANKS YOUR LISTENING !