COMP223: Software Engineering Final Project Guideline
COMP223: Software Engineering Final Project Guideline |
Grading System (1/2) |
Popup Quiz ................................................... 10 % (Almost) every session will have a quiz. Group Activity (SDP) .................................... 20 % Group activity in the classroom Test (Mid Term) ............................................. 15 % Details shall be provided later. Final (Group) Project .................................... 15 % Final Project Report (15 %) Final Exam ..................................................... 40 % Details shall be provided later. 2/92 |
Group Final Project |
Group Member: more (or equal) than 3 up to 5 Target (or Objectives) Components of the project (15 points) Use GitHub: Main channel to communicate Youtube might be optional. 3/92 |
Grading System |
Popup Quiz ................................................... 10 % (Almost) every session will have a quiz. Group Activity (SDP) .................................... 20 % Group activity in the classroom Test (Mid Term) ............................................. 15 % Details shall be provided later. Final (Group) Project .................................... 15 % Final Project Report (15 %) Final Exam ..................................................... 40 % Details shall be provided later. 4/92 |
Group Final Project |
Target (or Objectives) Components of the project (15 points) Use GitHub: Main channel to communicate Youtube might be optional 5/92 |
Source codes |
6/92 |
Documentation (1/3) |
README.md: (in GitHub) GitHub Introduction |
Documentation (2/3) |
The document should contain the following items: Graphical Abstract* • Single pictures that shows your project. Purpose of the software includes: • Why you choses this type (Waterfall vs. Agile)? Software development plan • Development Process • Members (Roles & Responsibilities & Portion) • Schedule • Future plan
|
Documentation (3/3) |
Additional components in README.md Domo (Youtube URL) Environments of the software development and running pakcages; ... Declaration group) should be declared clearly. Submission via Canvas Basic information (directly put in Canvas) Filled contribution portion form (not same as the software development R&R) GitHub Link of your software 9/92 |
Demo & Remarks |
Demo video clip should include: How to run (or start) the software; Show them how to use the software;
10/92 |
Marking Scheme (1/2) |
Source code [+3] [+1] feasible to run (i.e., aligned with the demo); Document (README.ed) [Up to 9 marks] Good page design [Up to +2] Graphical Abstract [Up to 2; 0 – No] Covering the purpose [Up to 3 marks] Covering the components in SW development [Up to +7] • [+7] All components are covered • [+4 to +6] somewhat covered 11/92 |
Marking Scheme (2/2) |
Demo [+3] [+1] Show how to start the software; [+1] Show how to run the software. Additional extra marks [+1] Submit all required documents via Canvas on time [+2] Overall shape of the document (English writing, formats of using GitHub (README.md, ...) [+2] Good video editing (i.e., proper BGM, audio, ...) Total points could NOT be more than 15 points.
|
14/ |
