| Requirements: | |
| – UC | here (in each folder equals one UC) |
| – SRS | here |
| – Test Cases | here |
| – Test Log (for example screen shot in red/green) – testcoveragetest log can also be generated for .feature files | here |
| – Test Plan includes 3 different tests´+ include lifecycle management tools and metrics + change | here |
| – Functional Test | here |
| + unit tesxt+ one other test (like installation, stress test, …) | Unit tests repo Unit tests blog Third test blog User test formular |
| Project Management | board time spent issue list |
| – RUP gantt chart (past) future long-term plan using FP estimation (including hours/team member breakdown) | GANTT FP diagrams Time by labels (instead of commutative flow chart diagram) |
| – Jira / burndown | burndown charts by milestone (we totally forgot in second semester and mixed up a bit) WORKAROUND |
| – FP calculation(include esimtes and actual time spent comparison) | FP calculation FP comparison FP diagrams |
| healthy sprints / burndowns: | S2 Week 12 Week 6 |
| Ability to Execute | |
| – Demo | (demo is in the oral) videos here |
| – Code- installation (manual / or virtual machine) | here |
| Quality: | |
| ArchitectureSAD document+ includes pattern highlighted as part of architecture | here |
| Configuration Management/ Environmental Setup | here |
| – Metricsshow how code change improves a metric. Explain 2 metricsshow code samples when explaining metricexplain why some parts of code have bad metric but no need to change(can be in SAD document) | here |
| – Risk Managementshow living document – correctly filled | here |
| – Automated Testingfunctionalunitautomatic with deploy | gitlab ci/cd-pipeline blog post |
| Pattern (place in SAD) explain pattern | here |
| Other | Time spent by user |
| – Presentations | midterm final |
download this git-repo as zip here
Project: Itemize 
