Upgrade to Pro — share decks privately, control downloads, hide ads and more …

CSC310 Lecture 27

CSC310 Lecture 27

Final Project
(20261116)

Javier Gonzalez-Sanchez PRO

November 15, 2026

Transcript

24 slides
  1. CSC 5100 Modern Software Engineering Lecture 27. Final Project Dr.

    Javier Gonzalez-Sanchez [email protected] www.javiergs.phd office: 14 -227
  2. Grading 4 >= 98.5 A+ >= 77.5 C+ >= 95

    A >= 74 C >= 91.5 A- >= 70.5 C- >= 88 B+ >= 67 D+ >= 84.5 B >= 63.5 D >= 81 B- >= 60 D- < 60 F
  3. Agenda Week 13 Week 14 Week 15 Exams Week December

    09 Final Review December 11 Final Exam ? December 18 Final Project
  4. Deliverables 1. Source Code: GitHub Commit your own code! 2.

    Project. Have 4 completed sprints with Stories/Tasks individually assigned 3. UML Class Diagram: make it available in your GitHub classroom repository 4. README.md - explain what you did, accomplishments (stories). 5. Test Cases for your project - You can reuse the provided in the TDD lab but addapt to your code and add more as needed. 6. Add a YML file to (a) run your test cases automatically; (b) package your application. On the target folder is fine but bonus if you create a release on GitHub that can be downloaded and run with a single click. 7. Add me (mscjaviergs@gmail) as member of your team. 9
  5. Important • User Stories Each team member is responsible for

    their own stories. • Task board Each team member defines and updates their own tasks, foster a sense of accountability and commitment. 10
  6. Important • UML Class Diagram One diagram per team includes

    all classes and their relationships; however, each team member is responsible that their own classes are correctly represented. • Apply design principles and patterns. Mainly but not limited to integrating each team member's features into a single product. Consider Observer, Singleton, Composite/Decorator, but explore Null-Object, Factory, Builder, Memento, etc. However, “Design Principles and Patterns are not Supposed to be used randomly; I will not evaluate that you know the element but that you can use it correctly when appropriate. 11
  7. Important • Source Code • Oral Presentation (5 minutes video)

    My features, my design and its integration, my code, and the quality metrics of my code. • 12
  8. Second Act – Your process Taiga - Stories, Backlogs, and

    Task board Stories (INVEST), Sprint backlog, product backlog. Estimation (story points) Talk about tasks; who is doing what? Everybody is doing some programming! 16
  9. Note Review that your stories are stories and not tasks;

    review that your tasks are tasks not stories Review that your stories are INVEST 17
  10. Third Act – Software Design Show your class diagram. Use

    colors as needed (Single Responsibility Principle) What are the A, I, or D in the new class? (show the 2D plot regarding where your classes are in terms of the pain zone) 18
  11. Note 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. 19
  12. Fourth Act – Code Show your Code Are your metrics

    OK (CC)? (optional) Any significant aspect that you want to share? 20
  13. Fifth Act – Review and Retrospective Review What is Good

    in the product? What is next for the product (next features to be added)? (your promise for the next sprint presentation) Retrospective (Process & People) What went well? What did not go well? 22
  14. Note Do you have issues (with your team, your technical

    skills, understanding the project instructions)? Talk, ASAP. Nothing can be done after the due date. 23
  15. CSC 5100 Modern Software Engineering Javier Gonzalez-Sanchez, Ph.D. [email protected] Fall

    2026 Copyright Notice. These slides are provided exclusively for educational use in CSC 5100 within the California State University system. Redistribution or use for any other purpose is prohibited without prior written permission.

More Decks by Javier Gonzalez-Sanchez

Other Decks in Programming