CSC 308:
Software Engineering I

WINTER 2009
(Section 01)

Course Schedule
Winter 2009 - Evolving Schedule - check on occasion!
(Changes will be announced in class, reading here does not substitute for attendance. Important changes will eventually be posted here only  for your convenience and reference. )
Week # Date 
Readings Activities - Lab Focus Due Dates and Notes
  
1 Jan 5, 7, 9
 Go order a copy of Schach, "Object-Oriented & Classical Software Engineering," Seventh Edition (Mc-Graw Hill, 2007)
Begin, chapters 1, 2 and 3 from Schach.  Read the   Chaos Report  .  Read Wiegers chapter 7 over the weekend.  Schach week 1 slides (annotated) 		Introductions

Form lab teams day 1.  Beginning lab team activities.

Basic domain exploration, initial meeting with customer

 Team Social Event
  
2 Jan 12, 14, 16
 Schach chapter 4 and 5 and (most importanly) Schach chapter 10.  Team members should work through the use-case tutorial (this one or some other source) this week.  Be sure to read the CPE 308 student survival guide.  This is really important. Some of Monday's slides. Basic requirements elicitation issues and discussion.  Distill important parts of Wiegers' Developer/Customer Rights and Responsibilities to discuss with team.  Slides Week 2a  Slides Week 2b

 Explore domain, meet with customer, build use-cases, begin Vision and Scope (business case and basic functional requirements.)  Teams should be working on "jelling" and producing a process and basic schedule of deliverables (what will they be?)  Homework 1 for week 2 -due at end of week in your journals
 Draft Use Cases due
  
3 Jan 21, 23
(Monday holiday!)
 Agile Manifesto fyi.  Process planning, risks, some basic requirements issues will be discussed.   Here is a pointer to a good overview article about Requirements (nice, quick, summary reading!)  Be sure to know and understand the bad words list and the intention behind it - it is important for all your documents and communications this term.
 Milestones should be just about set at this point.  Competitive intelligence (as requested by our customer) should result in a comparative feature matrix (sample feature matrix) for her review. Improve Use Case Document (Sample Use-Case Doc)
Wed: Vision and Scope
Fri: Risks Document
  
4 Jan 26, 28, 30
 Recent slides.
Specifying requirements - begin to describe the software system.  Milestones in perspective on the way to a requirements document.   Read and understand this short article by Wiegers on Requirements Traps.		 Formal milestones, week 4: fully realized Vision and Scope and Risks documents.  
The team should also produce a draft Data Dictionary from the individual homework (this will be maintained and utilized in the SRS.)

Basic use-case process to cross check against your process.
 Continue revisions of Use-Cases with customer. Weds: Fully developed Vision and Scope document
due and revised Risks document due.  Fri: Team Organization and role descriptions due.  Draft Use-Case document due. Use-Case forms here.
  
5 Feb 2, 4, 6
 Formal specification of software.  Object Oriented Analysis begins if schedule permits.
Carefully read Wiegers hints on documenting requirements (and review Schach Chapter 10).  
 Continue to elicit and develop requirements through use-cases and storyboards (or other prototypes).  

Formal inspection process required from this point onward.

Apply some formal method thinking to project.

 Mon: Fully developed Use-Case document
Weds: Full
Data Dictionary
due.
Friday, have a draft SRS ready for review with all team mamber responsibilities noted in WBS.
  
6 Feb 9, 11, 13
 Requirements Analysis.  Schach Chapters 11, 12.  Some slides from Monday.  Requirements types reference and short process description slides (slides 11-13) that were referenced in class. Building analysis models during requirements elicitation and analysis.
Requirements process self check 		Weds:  SRS draft
and Team (Self) Eval due.  Analysis models and continued improvement on all documents.
  
7 Feb 18, 20
(Monday holiday!)
 Requirements Quality.  Slides from this week and last 1(DFD-ERD) 2(ReqtsTraps) 3(ReqtsProps) 4(FSM-PN)
 * Midterm exam on Friday, 20 February.
 Weds:  SRS, Vision and Scope to Instructor and Customer for approvals. Architecture development.

  
8 Feb 23, 25, 27
 Continuing SRS - object oriented analysis.  If you didn't get the memo, here is your new cover sheet. Here are the Slides for the week on OOA following Schach's chapter 12.  Supplementary OMT OOA slides. (REVISED on Wednesday, please refresh!)  Presentations to class in lab - proposed architectures and continuing issues
 Draft UML E-R and dataflow diagrams.  
  
9 Mar 2, 4, 6
Software Architectural Design.  READ Schach Chapter  13 (skim this up to 13.8), be sure to Read Chapter 16 on UML.  Slides on reviews, slides on critical reading and ambiguity.
 Group Project Presentations
Pair Group
Review/Walkthrough
 Software Architecture Document due at end of week

  
10 Mar 9, 11, 13
 
Catch up, Requirements and Architecture (UML diagram) finalization.  Presentations and Posmortem meeting.
Final reviews and approvals.  Second round: Team (Self) Eval  due Friday.

Postmortem report due Friday.  
  
 





Final Exam Details:


FINAL Interviews during finals week.


 

 
Notes:
  • Weekly Readings: You must read the material before the corresponding lecture. You may be questioned in class about the readings and you will be expected to be knowledgeable about them.
  • Attendance and active participation are required in classes.  They account for a serious component of the grade.


Clark Savage Turner.

Page created January 2004; last updated 8 Feb 2009.