Capstone Project_Đồ án tốt nghiệp (For IS, ES, BLC, ATM Specializations)

The capstone project provides students important skills and initial experiences in participating in the software projects. Student can apply knowledges they have learned to the real current projects include: - Experiencing across all project phases: requirement, design, coding, testing and release - Finding out and using the templates and composing documents for each project stage - Using knowledges of technology that have been taught - Having the opportunity to research and apply new technologies - Practicing teamwork and how to interact with colleagues in a project implementation process - Ensuring the proper implementation of quality requirements and schedule - Doing troubleshooting With the team size of 4-5 members, the output product size are required to be equivalent to 20-25 medium use cases (3-7 transactions for each use case; action buttons on the screen, end user transactions to the software screens/functions or database transactions can be counted as transaction) The capstone project provides students, working in groups, with a significant project experience in which they can integrate much of the material they have learned in their program, including matters relating to requirements, design, implementation, human factors, professionalism, and project management. Students should be expected to deliver one or several iterations of a software system, along with all artifacts appropriate to the process model they are using. These would likely include a) Project management Plan (perhaps updated regularly), b) Software Requirements Specifications (SRS) c) Architectural and Design Documents (SDD) d) Test Plan and other Test Documentation (STD) e) Software package & the user guides (package content, installation guide & user manuals) All the documents in the project implementation process and the progress reports are required to write in English. "Final Result = OGA*50% + TDA*50% In which:" "1) On-going Assessment (OGA) - Project Introduction (Report 1): 4% - Project Management Plan (Report 2): 8% - Software Requirement (Report 3): 16% - Software Design (Report 4): 18% - Testing (Report 5): 18% - User Guides (Report 6): 4% - Implementation (Report 7): 32%" "2) Thesis Defense Assessment (TDA) - Project Introduction: 5% - Project Management Plan: 5% - Software Requirement: 15% - Software Design: 10% - Testing: 10% - User Guides: 5% - Implementation: 35% - Presentation Skills: 5% - Q&A: 10%" "Completion Criteria: 1. TDA >=4/10 2. Final Result >=5 Before thesis defense, students must wait until the second thesis defense round if they have the OGA less than 5/10 OR they are in one of below cases: (1) Students complete less than 75% use cases functions/screens as submitted (as mentioned in the submitted Report 3, at the end of the week 3) OR there are less than 20 average (3-7 transactions) use cases completed. (2) Students can't prove the fact that they prepare any of the project reports or the output software by themselves (3) There are more than 3 obvious coding-logic defects OR more than 1 show-stopper defects (the defects that prevent end user from completing his/her use case on any software functions) in the submitted software. The student(s) has to re-do the capstone project if the above cases occur with the assessments for the second thesis defense OR there is one OGA with grade (see the list above) less than 2/10. After thesis defense, student(s) is evaluated as failed the capstone project if they are in one of below cases (no matter when the guiding teacher doesn't evaluate that): (1) Student can't demonstrate any function or use case (2) Students can't prove the fact that they prepare any of the project reports or the output software by themselves (3) There are more than 3 obvious coding-logic defects OR more than 1 show-stopper defects (the defects that prevent end user from completing his/her use case on any software functions) in the submitted software. "