4 § Stories originated in a storyboarding process, show me a use case diagram § How many actors? Were there inclusion, extension, or inheritance? § All your Stories § Are they INVEST? § Stories on Sprint 1, 2, 3 (and those that never reach a Sprint) § What percentage of stories were featured, knowledge acquisition, bugs to fix, and technical activities? § For each story provide its estimation. § How do you estimate it (linear, binary, Fibonacci, other)? Part 1. The process
5 § How many story points have you addressed per sprint? § Be sure to make them visible in your burndown chart § Burndown chart per sprint. § How often do you update (daily)? § How do you assign tasks? § Who did what? § How many story points are accomplished per team member? § (self and peer evaluation) What should be your grade and the grade of each of your teammates? Part 1. The process
7 § Describe your architecture ( a diagram with boxes is fine) § Did you create packages (yes/no)? Why? § Describe your design. Could it be easy for a new developer to reuse, modify or extend what you have created? § Draw a class diagram (use Astah) § Be sure the diagram and code match. § What components were developed by each team member? What were the criteria for splitting the work (components, classes, methods)? Part 2. The product
8 § Source code with Javadoc in public methods and Classes § Source code clean, DRY, and KIS § Code Metrics: LOC, eLOC, lLOC, CC § Structure Metrics: Abstractness, Instability, Distance § Does the product have a “good” quality? § What features were Unit Tested? § How many test cases are in total? § Coverage (statement, condition, condition-decision)? Part 2. The product
9 § What about Continuous Integration? § Did you implement and used GitHub Actions (or equivalent)? § In general, (self and peer evaluation) What should be the team grade for the product accomplished – consider functionality, code, and quality. Does it have value for the customer? § Could COCOMO support or undermine your grading decision? Explain. Part 2. The product
10 a) Final Version of your Source Code - submit your Java files b) Software Design - your UML class diagram c) Screenshot of your Backlog, Task board, and your Burn-down Chart from Taiga d) Links to your GitHub repository and Taiga project site f) Metrics (Code and Structure) g) Report addressing questions and global retrospective e) Link to your video of the Final Presentation Wednesday, March 17
Fall 2022 Copyright. These slides can only be used as study material for the class CSC308 at Cal Poly. They cannot be distributed or used for another purpose.