CSC305 Lecture 01

Individual Software Design and Development
Course Presentation
(202509)

Transcript

1. Dr. Javier Gonzalez-Sanchez javiergs@calpoly.edu www.javiergs.info o ffi ce: 14 -227 CSC 305 Individual Software Design and Development Lecture 01. Course Presentation
2. 1. Introductions
3. First n a me L a st n a me Dr. J a vier Gonz a lez-S a nchez j a viergs@c a lpoly.edu www.j a viergs.info Contact Information 3
4. 4 Where Am I from?
5. www.j a viergs.info/te a ching/ At CSU: Softw a re Engineering (CSC 305, CSC 307, 308, 309, 508, 509) Hum a n-Computer Inter a ction (CSC 486 a nd CSC 570) Teaching 5
6. 6 Research
7. 7 Your Turn • Wh a t n a me do you prefer to go by? • How pro f icient a re you in J a v a progr a mming? • H a ve you t a ken CSC 307 / 308 / 309?
8. 8 Roster
9. 2. Course Content
10. 10 Key Ideas • Individual (well, sometimes team of two) • Design (Software Design) • Development (Tools)
11. 11 Individual | Code is meant for human consumption • Someone else is going to re a d my code. • Someone else is going to try to modify or extend my code. • My code should be Open a nd Close. • Wh a t m a kes code e a sy to underst a nd? • St a nd a rd Problems h a ve St a nd a rd Solutions
12. 12 Individual | Code is meant for human consumption
13. 13 Individual | Code is meant for human consumption • Anybody c a n do progr a mming. • You a re Engineers a nd Scientists, therefore … • Wh a t a bout te a m-working? "Gre a t te a ms a re built when good individu a ls bring their strengths together.” • CSC 305 is a bout the individu a l
14. 14 Design | Manufacturing vs. Crafting Standard Solutions
15. 15 Development Tools
16. 16 Topics covered in CSC 307, 308, and 309 Deployment Softw a Testing Coding, Progr a Developing Softw a Design Requirement Engineering [+]
17. 17 Not CSC 305, but Highly Relevant • C a n you cre a te the Product B a cklog for the project described in L a b 1 • How m a ny stories (user stories)? • Do you remember INVEST? • Priority? • Estim a tion?
18. 18 Topics • Course Overview • Object-Oriented Design • Exceptions, Logging, Error H a ndling • Memory M a n a gement • Disk-b a sed Dyn a mic D a t a Structures • I/O • Cre a ting Libr a ries a nd APIs • Best Pr a ctices for Reuse • Project • Fin a l Ex a m Week
19. 3. Syllabus
20. 20 Guidelines Attendance (participation) is Expected
21. 21 Guidelines Hours per Week
22. 22 Guidelines Late Assignments
23. 23 Guidelines Regularly visit our course page on Canvas
24. 24 Grading Assignments L a bs + Quizzes Attend a nce & P a rticip a tion 25% 25% 10% 100% Project Fin a l Project Fin a l Ex a m Project 20% 20%
25. 25 Grading >= 96.5 A >= 93 A- >= 89.5 B+ >= 86 B >= 82.5 B- >= 79 C+ >= 75.5 C >= 72 C- >= 68.5 D+ >= 65 D >= 61.5 D- < 61.5 F
26. 26 Guidelines Please avoid grade grubbing —feel free to ask questions and clarify doubts, but don’t request extra points unless there’s a clear grading error
27. References
28. 4. Summary
29. 29 Good vs. Bad
30. 30 Performance + Readability • Write e ff icient code but prioritize re a d a bility a nd m a int a in a bility. • Optimize perform a nce-critic a l sections only when necess a ry.
31. Homework
32. 32 Homework: Review Java Read The Java Tutorials (Links available on Canvas) As needed
33. 33 Homework: Style Guide Read Java Style Guide https://google.github.io/styleguide/javaguide.html Apply it Always!
34. 34 Questions
35. Lab
36. 36 Quiz 01 Programming 101 Exam Quiz!
37. CSC 305 Individual Software Design and Development Javier Gonzalez-Sanchez, Ph.D. javiergs@calpoly.edu Fall 2025 Copyright. These slides can only be used as study material for the class CSC305 at Cal Poly. They cannot be distributed or used for another purpose.