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

CSC309 Lecture 21

CSC309 Lecture 21

Software Engineering II
Project Presentation
(202306)

Javier Gonzalez-Sanchez
PRO

March 07, 2023
Tweet

More Decks by Javier Gonzalez-Sanchez

Other Decks in Programming

Transcript

  1. jgs
    CSC 309
    Software Engineering II
    Lecture 21:
    Final Project Presentation
    Dr. Javier Gonzalez-Sanchez
    [email protected]
    www.javiergs.com
    Building 14 -227
    Office Hours: By appointment

    View Slide

  2. jgs
    Key Ideas

    View Slide

  3. jgs
    Javier Gonzalez-Sanchez | CSC 309 | Winter 2023 | 3
    Project Presentation
    Product
    Process You

    View Slide

  4. jgs
    1. The Process

    View Slide

  5. jgs
    Javier Gonzalez-Sanchez | CSC 309 | Winter 2023 | 5
    We are here
    Burndown
    Chart

    View Slide

  6. jgs
    Javier Gonzalez-Sanchez | CSC 309 | Winter 2023 | 6
    § 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

    View Slide

  7. jgs
    Javier Gonzalez-Sanchez | CSC 309 | Winter 2023 | 7
    § 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

    View Slide

  8. jgs
    Javier Gonzalez-Sanchez | CSC 309 | Winter 2023 | 8
    § 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

    View Slide

  9. jgs
    1. The Product

    View Slide

  10. jgs
    Javier Gonzalez-Sanchez | CSC 309 | Winter 2023 | 10
    Rules

    View Slide

  11. jgs
    Javier Gonzalez-Sanchez | CSC 309 | Winter 2023 | 11
    § 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

    View Slide

  12. jgs
    Javier Gonzalez-Sanchez | CSC 309 | Winter 2023 | 12
    § 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)?
    Present your metrics in your video. Explain!
    Part 2. The product

    View Slide

  13. jgs
    Javier Gonzalez-Sanchez | CSC 309 | Winter 2023 | 13
    § What about Continuous Integration?
    § Did you implement and use GitHub Actions (or equivalent)? Show it!
    § Cost Estimation. Compare your product/work with worse best COCOMO
    case scenarios Explain.
    § 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?
    Part 2. The product

    View Slide

  14. jgs
    3. You

    View Slide

  15. jgs
    Javier Gonzalez-Sanchez | CSC 309 | Winter 2023 | 15
    § My Stories
    § My Tasks
    § My Story Points
    § My design - Classes / Methods
    § My metrics: Cyclomatic Complexity / LOC / D,A,I
    § My testing approach
    § My (continuous) integration/deployment
    Part 3. Individual Contribution

    View Slide

  16. jgs
    Javier Gonzalez-Sanchez | CSC 309 | Winter 2023 | 16
    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, June 14

    View Slide

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

    View Slide

  18. jgs
    Javier Gonzalez-Sanchez | CSC 309 | Winter 2023 | 18
    Office Hours
    Tuesday and Thursday 3 - 5 pm
    But an appointment required
    Sent me an email – [email protected]

    View Slide

  19. jgs

    View Slide

  20. jgs
    CSC 309
    Software Engineering II
    Lab 23:
    Work in Your Project
    Dr. Javier Gonzalez-Sanchez
    [email protected]
    www.javiergs.com
    Building 14 -227
    Office Hours: By appointment

    View Slide

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

    View Slide

  22. jgs
    CSC 308 Software Engineering I
    Javier Gonzalez-Sanchez, Ph.D.
    [email protected]
    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.

    View Slide