Class Schedule and Reading List 

Under development - Notes will change, so don't download and printeverything now.

1. Introduction to Software Engineering (Feb. 1)
   
   • What is software engineering? Why is it important?
   • The software lifecycle
   • Software process models
   • Reading: Sommerville - Chapter 1 and Chapter 3
   • Notes
   • PDF
   • Homework Questions (Due before class Feb. 1)
   • Sommerville pp. 18-19, Q. 1.2, Q 1.4, p. 6, Q. 3.1, Q. 3.3
2. Introduction to Software Engineering (Feb. 6)
   
   • Case Study: HowMicrosoft builds software, Michael Cusumano and Richard Selby, Communicationsof the ACM, vol. 40, No. 6, pp. 53-62, June 1997.
   • Homework: (Due before class Feb. 6)
   • Q1. Is Microsoft's software development process more like the waterfallmodel or the evolutionary model? Why or why not?
   • Q2. What is meant by the phrase "Synch and Stabilize?"
3. Static Verification (Feb 8.)
   
   • Formal technical reviews
   • Case study: Whatmakes inspections work? Adam Porter and Larry Votta, IEEE Software,Vol. 14, No. 6, November/December 1997
   • Reading: Sommerville - Chapter 19, pages 417 - 431.
   • Notes
   • PDF
   • Homework Questions (Due before class Feb. 8)
   • Sommerville p. 439, Q. 19.3, Q 19.5
   • Case Study Q1: Despite our findings that meeting may not be cost-effective, many companies still want to conduct them. Why?
   • Case Study Q2: What is meant by the term "interval?" What inspection factorsincrease interval? Do these same factors affect the interval of other process?Why or why not?
4. UML - The Unified Modeling Language (Feb. 13,15)
   
   • Reading: Sommerville - Chapter 7
   • Notes
   • PDF- part 1
   • PDF- part 2  
   • PDF- part 3  
   • Homework Questions (Due before class Feb. 13)
   • Sommerville p. 170, Q 7.8, Q 7.9
5. Requirements Analysis (Feb. 20)
   
   • Software requirements elicitation
   • Reading: Sommerville - Chapter 5, Chapter 6.
   • Notes
   • PDF 
   • Homework Questions (Due before class Feb. 20)
   • Sommerville p. 120, Q 5.2, Q 5.6, p. 146 Q 6.1, Q 6.5
6. Requirements Analysis (Feb. 22)
   • Case study: Creating products customers demand, Anthony F. Hutchings and Steve T. Knox, pp. 72 - 80 Communications of the ACM, Volume 38 , No. 5 (May. 1995).
7. Software Architectures (Feb. 27)
   
   • Reading: Sommerville - Chapter 10, Chapter 11.
   • Notes
   • PDF 
   • Homework Questions (Due before class Feb. 27) 
   • Sommerville p. 238, Q 10.5, Q 10.6, p. 258-259 Q 11.1, Q 11.8
8. Architectural Design (Mar. 1)
   
   • Case study: Hints for computer system design. Butler Lampson, ACM Operating Systems Rev. 15, 5 (Oct. 1983), pp 33-48. Reprinted in IEEE Software 1, 1 (Jan.1984), pp 11-28.
   • Homework Questions (Due before class Oct. 10) (updated 10/5/00)
   1. Case Study Q1: What's a procedure argument? Can you use this approach inJava? If so, how?
   2. Case Study Q2: What's a log? How might you use one in your class project?
9. Detailed Design (Mar. 6)
   
   •     Design Principles
   • Reading: Sommerville Chapter 12
   • Notes
     • PDF
   • Homework Questions (Due before class Mar. 6) 
     • Sommerville p. 283 Q 12.1, Q 12.2
10. Detailed Design (Mar. 8)
    
    • Case study: On the CriteriaTo Be Used in Decomposing Systems into Modules, D. L. Parnas, Communicationsof the ACM, Vol. 15, No. 12, December 1972 pp. 1053 - 1058.

     

11. Coding (Mar. 13)
    
    • Design patterns
    • Reading: Sommerville - Chapter 14.
    • Notes 
    • PDF- Design Patterns
12. Coding (Mar. 15)
    
    • Case study:  Experience using design patterns to develop reusable object-oriented communication software , Douglas Schmidt, Communications of the ACM, October 1995.
    • Homework Questions (Due before class Mar. 15) 
      • Q1: What would be the strengths and the weaknesses of using the Reactor pattern to implement an ftp server?

       

13. Testing (Mar. 27)
    
    • Software Testing
    • Unit testing techniques
    • Reading: Sommerville - Chapter 20.
    • Homework Questions (Due before class Mar. 27) 
    • Sommerville p. 466, Q 20.1, Q 20.5
    • Notes
    • PDF 

     

14. Testing ( Mar. 29)
    
    • Case study: Rethinking the Taxonomy of Software Fault Detection Techniques", by Michal Young and Richard N. Taylor in Proceedings of the Eleventh International Conference on Software Engineering, pages 53-62, Pittsburgh, PA, May 1989.

     

15. Maintenance and Evolution (Apr. 3)
    
    • Configuration management
    • Regression testing
    • Reading: Sommerville - Chapter 27, Chapter 29.
    • Notes
16. Maintenance and Evolution (Apr. 5)
    
    • Case study: TheCathedral and the Bazaar, Eric S. Raymond

     

17. Project Management (Apr. 10)
    
    • Organizational structure
    • Project management
    • Process definition, evaluation, and improvement
    • Reading: Sommerville - Chapter 4, Chapter 22.
    • Notes
    • PDF

     

18. Project Management (Apr. 12)
    
    • Case study: Understanding software development processes, organizations and technologies, D.E. Perry, N. A. Staudenmayer, and L. G. Votta Jr. IEEE Software, July 1994.

     

19. Systems Engineering (Apr. 17)
    
    • Software as part of a system
    • Human factors
    • Reading: Sommerville - Chapter 2.
    • Notes
    • Powerpoint

     

20. Systems Engineering (Apr. 19)
    
    • Case study: An investigation of the Therac-25 accidents, Nancy Leveson and Clark S.Turner, IEEE Computer, Vol. 26, No. 7, July 1993, pp. 18-41.

Web Accessibility