3 Demo of your project. Show your project running. Particularly show us what have you added in the previous two weeks that was not there before :: notes :: I know you could be working mostly on fixing things, but at least a few new functionalities should be there Show how you are moving your CSC 308 project to the new one that you describe in your proposal. you can, additionally, talk (briefly) about your proposal, i.e., the next features to be added First Act – The product for the Customer
4 Taiga à Stories, Backlogs, and Task board Show your Stories, a glimpse of stories in the Sprint backlog, and Stories in the product backlog. Which are the ones with high value in the estimation (story points)? Are they INVEST? Talk about tasks; who is doing what? Did you complete your stories this sprint? If not, Why? Show and explain your Burndown Chart. How Often are team members updating (reporting)? Second Act – Your process
6 Show your class diagram. (Show what is important and make it easy to read for the audience) :: notes :: Show how you are moving your CSC 308 project to the new one that you describe in your proposal. (you can use colors for the newly added classes) What did you do that make this design better than the one in the CSC 308 submission? Do you achieve SOLID? Do you improve A, I, or D? (show the 2D plot regarding where your classes are in terms of the pain zone) Third Act – Software Design
8 Show US your GitHub Who is doing What? (commits, LOC, added, removed, etc.) Share with Us what is happening there and how things are being done (as a team effort) You can describe this together with your Taiga activities or separately. Show US your Code and Code Metrics Are your metrics OK (LOC, eLOC, lLOC, CC)? Any significant aspect that you want to share? Do you acquire technical debt for something? What did you do that make this code better than the one in the CSC 308 submission? Do you have Test Cases (Unit Testing) If so, What are you testing? If not, What are your plans for testing? Fourth Act – Code
9 Sprint Review What is Good in the product? What Problems were detected in the product? What potential risks does the product have? What is next for the product (next features to be added)? (kind of your promise for the next sprint presentation) Sprint Retrospective (Process & People) What went well? What did not go well? What can be improved? And, your velocity this sprint Fifth Act – Review and Retrospective
11 § “Any fool can write code that a computer can understand. Good programmers write code that humans can understand”. -Martin Fowler § “Even bad code can function”. –Robert C. Martin Coding
12 § Check Javadoc for Classes (recommended for public Methods) § Check to name classes, methods, and variables. § Be suspicious of any static element and ask, Does this really need to be static? Static is dangerous and can drive you to the Structural Programming model, and you want to do Object-Oriented. § Is it DRY? § Is it KIS? Summary (par 1 /2 )
13 § Check connections (inheritance, having, using) § Are these global variables needed as global? § Should this be delegation or inheritance? § Be careful about what is shared on a Singleton. Singleton is dangerous; it can make you forget encapsulation and drive you to the everyone has access to everything approach. § Check for Observer pattern misuse or overuse Summary (par 1 /2 )
Winter 2023 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.
javiergs
oekazuma
niftycorp
andpad
lamodatech
memory1994
yoshifumi_ishikura
nrslib
yusukebe
makihiro
okuzawats
akase244
n3xem
dougneiner
paulrobertlloyd
addyosmani
erikaheidi
michaelherold
thekraken
lara
morganepeng
soudai
lauravandoore
shpigford
chriscoyier
![jgs CSC 309 Software Engineering II Javier Gonzalez-Sanchez, Ph.D. [email protected]](https://files.speakerdeck.com/presentations/afc2de4042c542ceb52148abb6f8d6d1/slide_17.jpg){kind=link}