CSC310 Lecture 01

Course Presentation
(20260824)

Transcript

1. CSC 3100 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
9. Your Turn • Wh t is your n me (or how you go by it)? • Wh t is your Progr mming (l ngu je(s), experience, proe iciency)? a a f a a a a a a a a 9 a • Wh t is Your experience progr mming (internships, person l projects, h ck thons, others)?
10. Course Content
12. This is NOT… This is NOT a web development course. That one is CSC 437 12
13. This is NOT… ❌ JavaScript ❌ Node.js ❌ React ❌ HTML ❌ CSS ✅ Software Engineering 13
14. This is About Engineering 14
15. Who is Alan Kay Computer scientist (Xerox, Apple, HP, Disney, MIT, Stanford…). His ideas on objects, message passing, and modular, human-centered system design strongly influenced modern programming languages and helped establish software development as an engineering discipline rather than just coding. https://en.wikipedia.org/wiki/Alan_Kay 15
16. This is About Engineering 16
17. To be continued...
18. This is About Engineering • M nuf cturing vs. Cr fting Softw re • Code is me nt for hum n consumption, nd it’s me nt for computer consumption. a a a a a a a a a a 18 a • Cre ting softw re together but not scr mbled
19. This is About Engineering 19
20. Code is meant for human consumption 20
21. Together but not Scrambled 21
22. Manufacturing vs. Crafting 22
23. Analogy Analysis understanding how systems work asking all the important questions before you start hammering nails Design creating solutions that meet requirements, budget, improving performance, cost, efficiency, or safety. Follow standards Use what already exists! Implementation translating ideas into functioning realities (Not always with their own hands) 23
24. Technical Debt 24
25. Topics Deployment Softw Testing a a 25 a Coding, Progr Developing [+] Requirement Engineering Softw Design
26. Key Ideas idea validation operation requirement s validation system testing architecture verification integration testing design verification unit testing code quality measure 26
27. Key Ideas Taiga Sprints of 2 weeks An oral presentation after Coding for Human Consumption Single ownership 27
28. Key Ideas GitHub Branches Play nice with your team Own you features 28
29. Key Ideas Testing Units System Delivery Continuous Integration (automatic) Continuous Deployment (automatic) 29
30. Key Ideas 1. Technic l presentation 2. Softw re quality - veri ic tion, v lid tion, testing, nd metrics 3. Implementation, integration, deployment, and maintenance of large software systems – reuse, modi ability, and extensibility. a a a a f fi a 30 a 4. Tools, Frameworks, API, and libraries
31. Topics 31
32. Syllabus
33. Guidelines Attendance (participation) is Expected 33
34. Guidelines Hours per Week 34
35. Guidelines Late Assignments 35
36. AI 36
37. Guidelines Regularly visit our course page on Canvas 37
38. Grading 20% Ex ms 15 + 15 % 38 a 10%
39. Grading 39 >= 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
40. 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 40
41. References 41
42. Homework
43. Homework: Read Chapter 1 Read the Textbook Chapter 1 (PDF available on Canvas) 43
44. Homework: Review Java Read The Java Tutorials (Links available on Canvas) As needed 44
45. Homework: Review the Java Style Guide Read Java Style Guide https://google.github.io/styleguide/javaguide.html Apply it Always! 45
46. Questions 46
47. CSC 3100 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.