final project

Transcript

1. Dr. Javier Gonzalez-Sanchez javiergs@calpoly.edu www.javiergs.info o ffi ce: 14 -227 CSC 307 Introduction to Software Engineering Lecture. Final Project
2. 2 Grading Assignments L a bs + Quizzes Attend a nce & P a rticip a tion 20% 30% 10% 100% Project Fin a l Project Fin a l Ex a m 5% 20% Peer Ev a lu a tion 15%
3. Schedule • Fin a l Review :: M a y 29 • Fin a l Ex a m :: Mond a y June 08 (O f ici a l University Schedule) • Fin a l Project Due :: Frid a y June 05 (one more sprint) 3
4. Sprint 4
5. 5 Features Taiga Syncronization (Read, Update, Delete)
6. 6 Features https://javiergs.github.io/tulip-api/
8. 8 Maven Central <dependency> <groupId>com.javiergs</groupId> <artifactId>tulip</artifactId> <version>8.0.0</version> </dependency>
9. 9 Features https://github.com/javiergs/tulip-api example/Main.java
10. Chatbot 10
11. v7.2
12. Project Submission
13. 13 Deliverables 1. Source Code: GitHub cl a ssroom. Commit your own code! https://cl a ssroom.github.com/ a /E32D6J_o 2. T a ig a : s a me a s per the previous Sprints - H a ve 4 completed sprints with Stories/T a sks individu a lly a ssigned 3. UML Cl a ss Di a gr a m: m a ke it a v a il a ble in your GitHub cl a ssroom repository 4. Metrics per cl a ss (D, I, A a nd m a x CC) 5. README.md - for e a ch te a m member expl a in wh a t you did, your a ccomplishments (stories) every sprint. Add a self ev a lu a tion in a 0 to 5 sc a le. 6. Add Test C a ses for your project - You c a n reuse the provided in the TDD l a b but a dd a pt to your code a nd a dd more a s needed. 7. Add a YML f ile to ( a ) run your test c a ses a utom a tic a lly; (b) p a ck a ge your a pplic a tion. On the t a rget folder is f ine but bonus if you cre a te a rele a se on GitHub th a t c a n be downlo a ded a nd run with a single click.
14. 14 Front-end and Back-end for this • Authentic a tion • List a ll projects ( a dd a nd remove) • Bl a cklog per project ( a dd a nd remove stories) + upd a te • Sprints per project ( a dd a nd remove stories) + upd a te • T a sks ( a dd, remove per stories) + upd a te • T a skbo a rd (ch a nge t a sks current st a tus) • Dr a w a BurnDown Ch a rt
15. Important • User Stories E a ch te a m member is responsible for their own stories. • T a sk bo a rd E a ch te a m member de f ines a nd upd a tes their own t a sks, foster a sense of a ccount a bility a nd commitment. 15
16. Important • UML Cl a ss Di a gr a m One di a gr a m per te a m includes a ll cl a sses a nd their rel a tionships; however, e a ch te a m member is responsible th a t their own cl a sses a re correctly represented. • Apply design principles a nd p a tterns. M a inly but not limited to integr a ting e a ch te a m member's fe a tures into a single product. Consider Observer, Singleton, Composite/Decor a tor, but explore Null-Object, F a ctory, Builder, Memento, etc. However, “Design Principles a nd P a tterns a re not Supposed to be used r a ndomly; I will not ev a lu a te th a t you know the element but th a t you c a n use it correctly when a ppropri a te. 16
17. Important • Source Code • Or a l Present a tion (5 minutes video) My fe a tures, my design a nd its integr a tion, my code, a nd the qu a lity metrics of my code. • Self- Peer Ev a lu a tion A link will be provided on C a nv a s to submit this individu a lly a nd a nonymous. 17
18. Project Presentation
19. Project Presentation 19 Product Process You
20. First Act – Demo Demo of your project. Show your project running. 20
21. Second Act – Your process T a ig a - Stories, B a cklogs, a nd T a sk bo a rd Stories (INVEST), Sprint b a cklog, product b a cklog. Estim a tion (story points) T a lk a bout t a sks; who is doing wh a t? Everybody is doing some progr a mming! 21
22. Note 22 Review that your stories are stories and not tasks; review that your tasks are tasks not stories Review that your stories are INVEST
23. Third Act – Software Design Show your cl a ss di a gr a m. Use colors a s needed (Single Responsibility Principle) Wh a t a re the A, I, or D in the new cl a ss? (show the 2D plot reg a rding where your cl a sses a re in terms of the p a in zone) 23
24. 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. Note 24
25. Fourth Act – Code Show your Code a nd Code Metrics Are your metrics OK (CC)? Any signi f ic a nt a spect th a t you w a nt to sh a re? 25
26. Quality in your code: metrics Would another developer understand what I did? Note 26
27. Fifth Act – Review and Retrospective Review Wh a t is Good in the product? Wh a t is next for the product (next fe a tures to be a dded)? (your promise for the next sprint present a tion) Retrospective (Process & People) Wh a t went well? Wh a t did not go well? 27
28. Do you have issues (with your team, your technical skills, understanding the project instructions)? Talk, ASAP. Nothing can be done after the due date. Note 28
29. 29 Questions
30. Lab.
31. 31 Let’s Work
32. 32 Features https://github.com/javiergs/tulip-api example/Main.java
33. CSC 307 Introduction to Software Engineering Javier Gonzalez-Sanchez, Ph.D. javiergs@calpoly.edu Winter 2026 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.