CSC510 Lecture 01

Course Presentation
(20260824)

Transcript

1. CSC 5100 Modern Software Engineering Lecture 01. Course Presentation Dr. Javier Gonzalez-Sanchez javiergs@calpoly.edu www.javiergs.info ffi o ce: 14 -227
2. Introductions
3. Contact Information Dr. J vier Gonz lez-S nchez First n me L st n me j viergs@c lpoly.edu a a a a a a a a 3 a www.j viergs.info
4. Note | Spanish naming customs In Spanish naming conventions, a person uses two surnames— one from each parent—so in my case González-Sánchez is the full family name. This means I can be correctly addressed as Dr. Gonzalez ✅ or Dr. Gonzalez-Sanchez ✅, but not Dr. Sanchez ❌. https://en.wikipedia.org/wiki/Spanish_naming_customs 4
5. Where Am I from? 5
6. Teaching www.j viergs.info/te ching/ At CSU: Softw re Engineering (CSC 305, CSC 307, 308, 309, 508, 509) (CSC 3100, CSC 5100) a a a a a 6 a Hum n-Computer Inter ction (CSC 486 nd CSC 570)
7. Research 7
8. Context Rosalind Picard MIT MediaLab 1997 Winslow Burleson University of Arizona PhD Advisor David Garlan Carnegie Mellon PhD Committee Member SW Engineering HCI Affective Computing 8 SelfAdaptive Systems
10. Your Turn • Wh t is your n me (or how you go by it)? • Wh t is your b ckground in Softw re Engineering? a a a a a a a a a 10 a • Wh t is Your experience developing softw re (internships, person l projects, h ck thons, others)?
11. Course Content
12. Modern 🤔 a a a a a 12 a • Engineering softw re th t is distributed, continuously integr ted nd deployed, oper ted in the cloud, nd expected to evolve.
13. This Course • Apply wh t you know • Deepen into engineering decision-m king • Apply development skills (le rn, s needed, new fr meworks, libr ries, APIs, nd services) • Build nd integr te softw re s p rt of l rger, distributed system • Deploy, oper te, nd evolve softw re a a a a a a a a a a a a a a a a a a a a a a a a a f 13 a • Cre te softw re th t not only works but h s qu lity (reuse, extensibility, modi i bility, test bility, nd reli bility)
14. Concepts Architecture Design Code 14
15. Blueprint Architecture Design Code Deploy 15 Services
16. Eric Gamma 16
17. Robert Martin Design principles re not perfume to be liber lly sc ttered ll over the system. a a a a a a a 17 a Robert M rtin (Agile m nifesto, SOLID principles, Cle n Code Book)
18. Werner Vogels You build it, you run it. ... Everything f ils, ll the time. Werner Vogels CTO Am zon a a a 18 a Engineering responsibility does not stop when the code is written — the te m is responsible for the running system.
19. Questions: • C n I deploy it reli bly? • How do I know it is working? • Wh t h ppens when one service f ils? • C n I di gnose the problem? • C n I upd te it without t king everything down? • C n it h ndle more users/d t /devices? a a a a a a a a a a a a a 19 a • How much does running it cost?
20. To be continued...
21. Topics
22. Software Engineering Undergr du te Course on Softw re Engineering (3100) • Found tion l concepts, tools, nd techniques • Prep ring students for entry-level positions in industry • Follow est blished processes • Develop well-de ined softw re pplic tions • Emph sis on te mwork Gr du te Course on Softw re Engineering (5100) a a a a a a a a a a a a a a a a a a a a a a a f ff a a a a a a a a a a a a a a a a a a 22 a • Engineer l rger, distributed softw re systems • M ke nd justify rchitectur l nd technology decisions • Integr te pplic tions, services, d t , nd infr structure • Consider deployment nd oper tion s p rt of development • Ev lu te tr deo s involving qu lity, cost, time, nd people • Self-le rning, critic l thinking, nd open-ended projects
23. Together but not Scrambled (people and systems) 23
24. This is About Engineering 24
25. This is About Engineering 25
26. Code is meant for human consumption 26
27. • Production is p rt of the design problem. • Even good, fe ture-complete code is not necess rily production-re dy Mich el Nyg rd nd Rele se It! a a a a a a a a a a a a a a a a a a a 27 a Fe ture complete is not the s me s being production re dy, nd th t developers/ rchitects need to design for f ilures, deployment, monitoring, d pt tion, nd re l-world oper tion a a Release It!
28. Topics Operation (Monitoring, Adapting, Evolving) Deployment Softw Testing a a 28 a Coding, Progr Developing [+] Requirement Engineering Softw Design
30. Syllabus
31. Guidelines Attendance (participation) is Expected 31
32. Guidelines Hours per Week 32
33. Guidelines Late Assignments 33
34. AI 34
35. Guidelines Regularly visit our course page on Canvas 35
36. Grading 20% Ex ms 15 + 15 % 36 a 10%
37. Grading 37 >= 98.5 A+ >= 77.5 C+ >= 95 A >= 74 C >= 91.5 A- >= 70.5 C- >= 88 B+ >= 67 D+ >= 84.5 B >= 63.5 D >= 81 B- >= 60 D- < 60 F
38. 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 38
39. References • Research Papers posted on Canvas • Recommended Books: 39
40. Questions 40
41. CSC 5100 Modern Software Engineering Javier Gonzalez-Sanchez, Ph.D. javiergs@calpoly.edu Fall 2026 Copyright. These slides may be used only as study material for CSC 5100 within the California State University system. They may not be distributed or used for any other purpose.