CSC307 Lecture 05

Introduction to Software Engineering
Software Design
(202407)

This lecture delves into the fundamentals of UML class diagrams for representing the structural models of software systems. We cover the graphical abstract descriptions that serve as blueprints for software solutions, detailing how class diagrams illustrate attributes, methods, and relationships between classes, including dependency, associations, aggregations, compositions, and generalization/specialization. Practical examples and activities help students apply these concepts.

Transcript

1. Dr. Javier Gonzalez-Sanchez javiergs@calpoly.edu www.javiergs.info o ffi ce: 14 -227 CSC 307 Introduction to Software Engineering Lecture 05. Sprint Backlog
2. Previously
3. Product Backlog 3 INVEST
5. Sprint Backlog
6. As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit)
7. Agile in Action 7
8. Create a Backlog and Task board 8 stories tasks (new)
9. Create a Backlog and Task board 9 stories tasks (new) UI UI UI UI UI
10. Note • User Stories: Describe the go a l, not the UI design. • Accept a nce Criteri a : Add speci f ics like “the f ilter should be a dropdown” or “results should upd a te without refreshing the p a ge.” • Wirefr a mes/Mockups: Att a ched to a User Story a s supplement a ry m a teri a l (done by a designer or with coll a bor a tion). • T a sks/Sub-t a sks: Bre a k the story down a nd a dd T a sks for UI implement a tion (e.g., “Include a f ilter dropdown”). 10
11. Create a Backlog and Task board 11 stories tasks (new) UI UI UI UI UI
12. Tools We need a Tool
13. Taiga
14. https://taiga.io 14
15. Let’s Work 15 Register on Taiga
16. https://taiga.io 16
17. Project 17
18. Project 18
19. Team 19
20. Team 20
21. Product Backlog 21
22. Product Backlog 22
23. Product Backlog 23
24. Sprint 24
25. Sprint 25
26. Sprint 26
27. Task Board 27
28. Task Board 28
29. Burndown Chart 29
30. One More Thing Burn down Chart
31. 31 Work Remaining (Hours or Points) days Burn down Chart
32. Which ones are Burn down Charts? 32 A B C D
33. Questions 33
34. Lab 02. Taiga
35. Estimation | Planning Poker Technique 35 https://www.planitpoker.com
36. Lab Lab. Create your Product Backlog, define a Sprint, and develop a Sprint Backlog with Tasks for each User Story. Add me (mscjaviergs@gmail) to your project
37. Let’s Work 37
38. CSC 307 Introduction to Software Engineering Javier Gonzalez-Sanchez, Ph.D. javiergs@calpoly.edu Spring 2025 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.