Computer Science
Department
CS 314 Software Engineering
Weekly Guide, Spring 2016 (an evolving plan for 2016)
Plans are much more tentative later in the semester.
Links:
Week 1. Jan 17-23. Introduction, Life as a software engineer.
- Class sessions: January 20 & 22, 2016.
- Introduction to the class
- Software Engineering Industry Panel.
- Notes 0.
- Reading: Text Ch. 1.
Week 2. Jan. 24 - 30. Software Process, Agile Development, Code Inspection.
- Class sessions: January 25, 27, & 29, 2016.
- Quiz 0, Parts A, B, and C (3 separate short quizzes): course prerequisites on Canvas, due 11:55 PM on Monday January 25.
- Quiz 1: Pre-Inspection Quiz on Canvas, due 11:55 PM on Tuesday January 26.
- Notes 1.
- Notes 2;
- Assignment 0, Due Jan. 27 Part A: hardcopy due in class, Part B: submit on Canvas 1/26/16 by 11:55 PM on 1/27/15.
-
Design Studio 1: Inspection,
preparation and pre-class quiz (on canvas) due Tuesday 1/26/16,
design studio activites in class 1/27/16.
Post-class retrospective writing due 1/28/16 on Canvas.
- Reading: Text Ch 1 and 2.
Week 3. Jan. 31 - Feb 6. UML Modeling, JUnit.
- Class sessions: February 1, 3, & 5.
- Assignment 1 Git and Eclipse, Due 2/4/16.
- Notes 2.
- Reading: Text Ch. 3 and 4.
- See Text Ch. 15, Appendix A (starting on p. 533)for an overview of UML.
- Introduction of Assignment 2, which concerns model-view separation.
- Reading on JUnit: to be posted.
Week 4. Feb 7-13. UML Modeling; User Stories; Verification and Validation.
Week 5. Feb 14-20. Verification and Validation.
Week 6. Feb. 21 - 27. Structural testing.
Week 7. Feb. 28 - March 4. Midterm Review, Exam 1, Intro to Design.
Week 8. March 6-12. Intro to Assignment 4.
*** Spring Break. March 15-21 ***
Week 9. March 20-26. Software Architecture and design. Android Development.
- Class Sessions: March 21, 23, & 25.
- On Monday, Saksham Manchanda will talk about Android programming and interfacing with Git.
- Notes: Notes 4
- Text: Ch 12 Using Design Patterns (pp. 446 - 477)
Week 10. March 27 - April 2. Android, Software Architecture, and Software Requirements.
- Class Sessions: March 28, March 30, April 1.
- Assignment 4 Android interface,
DUE: Wednesday 30 March 2016.
- Reading: Notes 4 and text Ch. 12 Using design patterns (pp. 446 - 477).
- Reading on Use Case Analysis: Text pp. 334-393.
- Reading on Domain Modeling: Text pp. 394-445.
- Notes: Notes 5.
Week 11. April 3-9. Software Requirements, Introduce A5, User Interface Design
Week 12. April 10-16. Use Case Analysis, Domain Modeling.
- Class sessions: April 11, 13 & 15.
- Reading on Use Case Analysis: Text pp. 334-393.
- Reading on Domain Modeling: Text pp. 394-445.
- Notes: Notes 5.
- Wednesday (April 13):
Design Studio 6 - Domain modeling.
Week 13. April 17-23. Requirements: Domain Modeling, Software Safety.
Week 14. April 24 - 30.
Review, Exam 2, Software Safety
15 Week 15. May 1-7.
Software safety, Team Demos, Review.
- Class sessions: May 2, 4, 6.
- Team Demonstrations of A5 solutions:
Volunteer to show off your solution to Assignment 5
in class
on Monday, May 2 or Friday, May 6.
- Notes 6: Software Safety
- Design Studio 7 on software safety is scheduled for Wednesday May 4.
Read the
Therac-25 report to prepare.
- Friday, May 6: (Voluntary) Demonstrations of Assignment 5: enhanced Adventure Game by the following teams:
- Review and retrospective
Week 16 Final Exam Week.