RU ENG ECE 16:332:567 :
        Software Engineering I

Lecture Schedule -- subject to change


Project Deliverables at a Glance

Project description is available here.
Make every effort to form your team before September 14, 2007 and notify the instructor by email, listing the team members and their emails. After this date, the students without a team will be randomly assigned a team.
Students will not be allowed to switch the team after September 21, 2007.

ItemDue date
I
t
e
r.
#1
1.   Proposal September 21
2.   First report   (Specification only) October 5
3.   Second report   (Design only) October 26
4.   First demo November 2
I
t
e
r #2
5.   Third report   (All reports collated) December 7
6.   Second demo December 7
7.   Electronic Project Archive December 10

Syllabus at a Glance

Topic 1 (1 lecture): Software Lifecycle and Team Projects
Topic 2 (1 lecture): Use Cases
Topic 3 (1 lecture): Object-Oriented Analysis
Topic 4 (1 lecture): Object-Oriented Design
Topic 5 (1 lecture): Description Notations
Topic 6 (1 lecture): Requirements Elicitation and System Specification
Topic 7 (2 lectures): Software Measurement and Estimation
Topic 8 (2 lectures): Design Patterns
Topic 9  (1 lecture):   Software Architecture

The parentheses below indicate the textbook chapter relevant to the lecture topic covered. All indicated textbook material should be read. That highlighted in red color are more important than the rest.

Download Lecture Notes

Sep
    7 (F)   Software Development Lifecycle   (textbook Ch. 1, 3;   lect-notes Ch. 1)Note #1
            Object Model      (lect-notes Ch. 1)Note #2
                     (For UML, check http://www.uml.org)
   14 (F)   Use Cases     (lect-notes Sec. 2.2)
            System Sequence Diagrams   (lect-notes Sec. 2.2.4)
   21 (F)   Domain Model    (Ch. 5;   lect-notes Sec. 2.3)
   28 (F)   Object-Oriented Design    (lect-notes Sec. 2.4)
            Visibility and Coupling   (textbook Ch. 7)

Oct
    5 (F)   Software Architecture - 1   (textbook Ch. 6)
            Description Notation: Logic and State Machines
   12 (F)   Object Constraint Language (For OCL, check  http://www.omg.org/docs/ptc/03-10-14.pdf)
            Progress Report: Slide Presentations of Group Projects (30 min per project)
   19 (F)   Specifying Systems in TLA+   (For TLA+, check http://lamport.org/)
            Problem Frames
   26 (F)   Problem Frames
            Software Measurement - 1

Nov
    2 (F)   ******* DEMO #1 *******
    9 (F)   ******* EXAM #1 (in-class, 1-period) *******
   16 (F)   Software Measurement - 2
            Software Estimation
   21 (W)   Design Patterns: Publisher-Subscriber   (Ch. 8;   lect-notes Sec. 4.1)
            Other Patterns (Proxy, etc.)   (Ch. 8;   lect-notes Sec. 4.2)
        (Changes in Designation of Class Days: Tue Nov 20 <- Thurs Classes; Wed Nov 21 <- Fri Classes)
        (Thanksgiving Recess: Thurs Nov 22- Sun Nov 25)
   30 (F)   Broker and Distributed Computing (Java RMI)     (lect-notes Sec. 4.4)
            Software Architecture - 2   (textbook Ch. 7)

Dec
    7 (F)   ******* DEMO #2 *******
        (Regular Classes End: Wed Dec 12)


   14 (F)  ******* FINAL EXAM *******
                Time      4:00 - 7:00 P.M.
                Location  CoRE-538

^ Note #1: Ch. 1 and 3 in the Bruegge & Dutoit textbook are briefly reviewed in the class. The student should read these for their own reference, but they'll not appear in the exams/project-reports. Ch. 3 gives a good advice about managing the teamwork.

^ Note #2: UML is introduced in Bruegge & Dutoit Ch. 2 and more comprehensive treatment is available in Miles & Hamilton's Learning UML 2.0. There will be no lectures covering exclusively UML. Rather, the symbols will be explained as they're introduced in the context of software development methodology. Miles & Hamilton and Ch. 2 of Bruegge & Dutoit should serve as reference material.



Ivan Marsic
Created: September 10, 2007
Modified: Mon Sep 10 13:14:18 EDT 2007