RU ENG ECE 14:332:452 :
        Software Engineering

Lecture Schedule—subject to change

Project Deliverables at a Glance

 Project description is available here.
Make every effort to form your team before January 23, 2009 and notify the instructor/TA 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 January 30, 2009.

ItemDue date
I
t
e
r.
#1		 1.   Proposal January 30
2.   First report   (Specification only) February 20
3.   Second report   (Design only) March 13
4.   First demo March 27 ► ...
I
t
e
r #2		 5.   Third report   (All reports collated) May 1
6.   Second demo May 5 ► ...
7.   Electronic Project Archive May 7

Syllabus at a Glance

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

The parentheses below indicate the section(s) in the lecture notes that are relevant to the lecture topic covered.

Download Lecture Notes

Jan
   20 (T)   Software Development Lifecycle   (lect-notes Ch. 1)Note #1
   23 (F)   Object Model      (lect-notes Ch. 1)Note #2
   27 (T)   Use Cases - 1     (lect-notes Sec. 2.2)
   30 (F)   Use Cases - 2     (lect-notes Sec. 2.2)
            System Sequence Diagrams   (lect-notes Sec. 2.2.4)

Feb
    3 (T)   Domain Model - 1    (lect-notes Sec. 2.3)
    6 (F)   Domain Model - 2    (lect-notes Sec. 2.3)
   10 (T)   Object-Oriented Design - 1    (lect-notes Sec. 2.4)
   13 (F)   Object-Oriented Design - 2    (lect-notes Sec. 2.4)
   17 (T)   Visibility and Coupling   (textbook Ch. 7)
   20 (F)   Software Architecture - 1   (textbook Ch. 6)
   24 (T)   Software Architecture - 2   (textbook Ch. 7)
   27 (F)   Specifying Systems

Mar
    3 (T)   ******* EXAM #1 (in-class, 1-period) *******
    6 (F)   UML State Diagrams
   10 (T)   Object Constraint Language (OCL)
   13 (F)   
        (Spring Recess: March 14 - 22)
   24 (T)   Software Measurement   (lect-notes Sec. 4.1 and 4.2.1)
   27 (F)   ******* DEMO #1 *******
   31 (T)   ******* DEMO #1 *******

Apr
    3 (F)   Use Case Points   (lect-notes Sec. 4.2.2)
    7 (T)   Coupling and Cohesion   (lect-notes Sec. 4.3)
   10 (F)   
   14 (T)   Design Patterns: Publisher-Subscriber   (lect-notes Sec. 5.1)
   17 (F)   Other Patterns (Proxy, etc.)   (lect-notes Sec. 5.2)
   21 (T)   Concurrent Programming   (lect-notes Sec. 5.3)
   24 (F)   ******* EXAM #2 (in-class, 1-period) *******
   28 (T)   Broker and Distributed Computing (Java RMI)     (lect-notes Sec. 5.4)

May
    1 (F)   Security      (lect-notes Sec. 5.5)
    5 (T)  ******* DEMO #2 *******
        (Regular Classes End: May 4  ·  Spring Exams End: May 13)

^ Note #1: Ch. 1 in the textbook is only briefly reviewed in the class. The student should read this as an introduction to the lectures, but it will not appear in the exams/project-reports.

^ Note #2: A comprehensive treatment of UML is available in Miles & Hamilton's Learning UML 2.0 and online http://www.uml.org. 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 http://www.uml.org should serve as reference material.


Ivan Marsic

Created:  December 29, 1997

Modified: Tue Jan 20 13:08:07 EST 2009