Dr. Javier Gonzalez-Sanchez [email protected] www.javiergs.info o ffi ce: 14 -227 CSC 307 Introduction to Software Engineering Lecture 16. Final Project 

Problem Planning Poker For Taiga 

Step 1 3 

Step 2 4 

Step 3 5 Import from T a ig a B a cklog 

Product Backlog 6 

Some Help • https://github.com/CSC3100/Pl a nIt-Poker/ • T a ig a StoryFetcher.j a v a 7 

Step 4 8 

Step 5 9 Plots 

Step 5 10 Te a m members x Their Stories 

Libraries 11 https://github.com/CSC3100/Tool-Maven 

Next 12 trace() debug() info () warn () error() message 01 message 02 message 03 message 04 message 05 Logger Appender Appender 

Ideas • Plot of numbers per Story • Plot of numbers per Te a m-member • Option to logout a nd login into a new project/T a ig a • Alw a ys a T a ig a involve for stories 13 

Questions 14 

Project Presentation 

Project Presentation 16 Product Process You 

First Act – Demo Demo of your project. Show your project running. 17 

Second Act – Your process T a ig a - Stories, B a cklogs, a nd T a sk bo a rd Stories (INVEST), Sprint b a cklog, product b a cklog. Estim a tion (story points) T a lk a bout t a sks; who is doing wh a t? Everybody is doing some progr a mming! 18 

Note 19 Review that your stories are stories and not tasks; review that your tasks are tasks not stories Review that your stories are INVEST 

Third Act – Software Design Show your cl a ss di a gr a m. Use colors a s needed (Single Responsibility Principle) Wh a t a re the A, I, or D in the new cl a ss? (show the 2D plot reg a rding where your cl a sses a re in terms of the p a in zone) 20 

The code and diagram (blueprint) should match. Be sure that your classes are updated in the blueprint submitted Correctly apply DRY, SRP, Patterns, Principles, etc. Note 21 

Fourth Act – Code Show your Code a nd Code Metrics Are your metrics OK (CC)? Any signi f ic a nt a spect th a t you w a nt to sh a re? 22 

Quality in your code: numbers of lines per method, cyclomatic complexity, following Java coding conventions, etc. Would another developer understand what I did? Note 23 

Fifth Act – Review and Retrospective Review Wh a t is Good in the product? Wh a t is next for the product (next fe a tures to be a dded)? (your promise for the next sprint present a tion) Retrospective (Process & People) Wh a t went well? Wh a t did not go well? 24 

Do you have issues (with your team, your technical skills, understanding the project instructions)? Talk, ASAP. Nothing can be done after the due date. Note 25 

Questions 26 

Project Submission 

To-Do List • User Stories E a ch te a m member is responsible for their own stories. • T a sk bo a rd E a ch te a m member de f ines a nd upd a tes their own t a sks, foster a sense of a ccount a bility a nd commitment. 28 

To-Do List • UML Cl a ss Di a gr a m One di a gr a m per te a m includes a ll cl a sses a nd their rel a tionships; however, e a ch te a m member is responsible th a t their own cl a sses a re correctly represented. • Apply design principles a nd p a tterns. M a inly but not limited to integr a ting e a ch te a m member's fe a tures into a single product. Consider Observer, Singleton, Composite/Decor a tor, but explore Null-Object, F a ctory, Builder, Memento, etc. However, “Design Principles a nd P a tterns a re not Supposed to be used r a ndomly; I will not ev a lu a te th a t you know the element but th a t you c a n use it correctly when a ppropri a te. 29 

To-Do List • Source Code • Or a l Present a tion (5 minutes video) My fe a tures, my design a nd its integr a tion, my code, a nd the qu a lity metrics of my code. • Self- Peer Ev a lu a tion 30 

Questions 31 

CSC 307 Introduction to Software Engineering Javier Gonzalez-Sanchez, Ph.D. [email protected] Summer 2024 Copyright. These slides can only be used as study material for the class CSC307 at Cal Poly. They cannot be distributed or used for another purpose.