CSC309 Lecture 15

Software Engineering II
GitHub Issues
(202302)

Transcript

1. jgs
   CSC 309
   Software Engineering II
   Lecture 15:
   Sprint Review
   Dr. Javier Gonzalez-Sanchez
   javiergs@calpoly.edu
   www.javiergs.com
   Building 14 -227
   Office Hours: By appointment
   

   View Slide

2. jgs
   Javier Gonzalez-Sanchez | CSC 309 | Winter 2023 | 3
   Note
   Sprint 2 Presentation This Friday!
   

   View Slide

3. jgs
   Javier Gonzalez-Sanchez | CSC 309 | Winter 2023 | 4
   Demo of your project.
   Show your project running.
   Particularly
   New Features
   Intelligent Tutoring System
   JFreeChart, JDBC, JSON,
   Maps API, Weather API, OpenAI API
   First Act – Demo
   

   View Slide

4. jgs
   Javier Gonzalez-Sanchez | CSC 309 | Winter 2023 | 5
   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!
   Show and explain your Burndown Chart.
   Second Act – Your process
   

   View Slide

5. jgs
   Javier Gonzalez-Sanchez | CSC 309 | Winter 2023 | 6
   Compare Sprint 1 and Sprint 2
   

   View Slide

6. jgs
   Javier Gonzalez-Sanchez | CSC 309 | Winter 2023 | 7
   Show your class diagram.
   Use colors for the newly added classes)
   If there are new functionalities, then there are new classes, right?
   (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)
   Third Act – Software Design
   

   View Slide

7. jgs
   Javier Gonzalez-Sanchez | CSC 309 | Winter 2023 | 8
   Structural Metrics
   Abstract
   concrete
   Stable
   Hard to Change
   Only incoming dependencies
   Unstable
   Changeable
   Only outgoing dependencies
   

   View Slide

8. jgs
   Javier Gonzalez-Sanchez | CSC 309 | Winter 2023 | 9
   Show US your GitHub
   Who is doing What?
   (everyone is adding or updating code)
   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 that made this code better than
   the one in the CSC 308 submission?
   Test Cases (Unit Testing)
   What are you testing? Why?
   Fourth Act – Code
   

   View Slide

9. jgs
   Javier Gonzalez-Sanchez | CSC 309 | Winter 2023 | 11
   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)
   What Problems/Risks were detected in the product?
   Retrospective (Process & People)
   What went well?
   What did not go well?
   And your velocity this sprint and the previous one
   Fifth Act – Review and Retrospective
   

   View Slide

10. jgs
    One last Thing
    

    View Slide

11. jgs
    Javier Gonzalez-Sanchez | CSC 309 | Winter 2023 | 13
    § “Any fool can write code that a computer
    can understand. Good programmers write
    code that humans can understand”.
    -Martin Fowler
    Coding
    Take care of Clean Coding (Readability)
    And Clean Design
    

    View Slide

12. jgs
    Javier Gonzalez-Sanchez | CSC 309 | Winter 2023 | 14
    Questions
    

    View Slide

13. jgs
    Javier Gonzalez-Sanchez | CSC 309 | Winter 2023 | 15
    Office Hours
    Tuesday and Thursday 3 - 5 pm
    But an appointment required
    Sent me an email – javiergs@calpoly.edu
    

    View Slide

14. jgs
    

    View Slide

15. jgs
    CSC 309
    Software Engineering II
    Lab 15:
    Work in your Sprint
    Dr. Javier Gonzalez-Sanchez
    javiergs@calpoly.edu
    www.javiergs.com
    Building 14 -227
    Office Hours: By appointment
    

    View Slide

16. jgs
    Javier Gonzalez-Sanchez | CSC 309 | Winter 2023 | 18
    Let’s Work
    

    View Slide

17. jgs
    CSC 309 Software Engineering II
    Javier Gonzalez-Sanchez, Ph.D.
    javiergs@calpoly.edu
    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.
    

    View Slide