CSC307 Lecture 06

Introduction to Software Engineering
Taskboard
(202504)

Transcript

1. Dr. Javier Gonzalez-Sanchez javiergs@calpoly.edu www.javiergs.info o ffi ce: 14 -227 CSC 307 Introduction to Software Engineering Lecture 06. Taskboard
2. Previously
3. 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)
4. Create a Backlog and Task board 4 stories tasks (new) UI UI UI UI UI
5. Task Board 5
6. Test Yourselves
13. Storyboarding
14. Step 1 14
15. Step 2 15
16. Step 3 16
17. Step 4 17
18. Step 5 18
19. Ideas
20. Ideas Story 1: As a te a m member, I w a nt to cre a te a new session so p a rticip a nts c a n join. T a sks: • Design “Cre a te Session” di a log (inputs: session n a me, m a x pl a yers). • Implement session cre a tion logic a nd store session in memory. • Gener a te unique session ID. • Displ a y a ctive session info on screen 20
21. Ideas Story 2: As a p a rticip a nt, I w a nt to join a session so I c a n estim a te stories with the te a m. T a sks: • Design “Join Session” screen (input: session ID). • Implement p a rticip a nt registr a tion logic. • Show list of current p a rticip a nts in session view. 21
22. Ideas Story 3: As a f a cilit a tor, I w a nt to a dd stories to estim a te so the te a m c a n vote on them. T a sks: • Cre a te form to input story title a nd description. • Add stories to a n intern a l list (per session). • Displ a y list of stories in a t a ble or c a rd list view. 22
23. Ideas Story 4: As a te a m member, I w a nt to see the c a rds visu a lly, so I c a n choose one. T a sks: • Design a nd dr a w Pl a nning Poker c a rds in the UI. • Add hover a nd click visu a l feedb a ck (e.g., highlight on selection). • Adjust l a yout responsively if the window resizes. 23
24. Ideas Story 5: As a te a m member, I w a nt to submit my vote for the current story. T a sks: • Implement vote selection logic (h a ndle when a c a rd is clicked). • Link vote to the current p a rticip a nt. • Allow vote ch a nge but prevent multiple votes • Store vote in session memory. 24
25. Ideas Story 6: As a f a cilit a tor, I w a nt to reve a l the votes a fter everyone h a s submitted theirs. T a sks: • Implement “Reve a l Votes” button. • Displ a y votes in list (do not show n a mes, keep it a nonymous). • Show a ver a ge or consensus result 25
26. Ideas Story 7: As a user, I w a nt to see who h a s voted. T a sks: • Add st a tus indic a tor next to e a ch p a rticip a nt (e.g., “voted” vs “w a iting”). • Upd a te UI in re a l-time a s votes a re submitted. • Highlight result when a ll votes a re completed. 26
27. Ideas Story 8: As a te a m, we w a nt to reset so th a t the te a m c a n estim a te a new story. T a sks: • Add “Next Story” button. • Cle a r vote st a tes a nd lo a d next story. • En a ble re-voting if needed. 27
28. Ideas Story 9: As a user, I w a nt to export the voting results to a text or CSV f ile. T a sks: • Implement result export logic. • Let user choose f ile loc a tion (Swing JFileChooser). • S a ve: story title, votes, a ver a ge. 28
29. Ideas Story 10: As a user, I w a nt to export the voting results to a text or CSV f ile. T a sks: • Implement result export logic. • Let user choose f ile loc a tion (Swing JFileChooser). • S a ve: story title, votes, a ver a ge. 29
30. Optional Enhancements • Add a timer per story estim a tion. 30
31. Questions 31
32. Lab 03. Taiga
33. Java Desktop Application | Planning Poker 33 https://www.planitpoker.com
34. Lab Improve your Taiga board considering the following: • This project can be completed in a single week. Move all stories to the Sprint Backlog. • Reflect on this: • If you were randomly assigned one of the listed tasks… • Would you understand what needs to be done (your specific part and how it fit into the whole)? • Is it clear what inputs you will receive and what outputs you are expected to deliver? • If your task depends on data or UI from another Task or Story, do you know what mock objects you might need? • Can you easily identify who on your team to contact for the part that will connect with yours? 34
35. Let’s Work 35
36. 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.