402schedule

This schedule may change since the course tends to be dynamic.

This page is mostly incomplete at this point, assignments and notes about deliverables will be added.

Week Expected Lecture
Topics Expected Lab
Focus Assigned Readings Assignments Other notes and expectations

1 Introduction to Software
Requirements Team Formation Chaos
SE Code of Ethics
Student Survival Guide
Wie Ch 1
Jackson: "Descriptions" and
"Machines" Begin Journal -
List of words to
define in journal to
be refined as we
learn. Team social meeting,
name, motto, cover sheet
identifying members and
contact info

2 Introduction to Requirements
Elicitation, where to start Customer contact
Define customer
problem and context Wie Ch 6,7
Jackson: "Procrustes," "Rough
Sketches," and "Application
Domain" Working on draft Vision
and Scope Document
6)

3 Process, Planning, Risks Team processes
Requirements
Elicitation, Milestone
Scheduling
Jackson: "Software,"
"Software Engineering,"
"Top Down" Questions1 due in
Journal by next Tuesday Tuesday, Vision and Scope
draft due
Thursday, Project Risk
document draft due.

4 Specifying Requirements Elicit and develop
requirements
Jackson: "Specifications,"
"Fudge Factor"
RSL (link from Prof. Fisher's
webpage) Questions2 due in
Journal by next Tuesday Vision and Scope document due
if necessary, Risks Document
revision (and maintenance),
present proposed Milestone
Schedule to Instructor

5 Formal Specification RSL and other formal
methods to specify
user requirments,
continuing analysis and
elicitation Revision of Vision and Scope.
Risks document maintenance.
Keep current with your schedule

6 Requirements Analysis Building models of
requirements. Continue
analysis and elicitation. Coordinate documents to
keep in synch. Produce one of
each type of model discussed
in classes and apply to
appropriate parts of the
requirements.

7 Requirements Quality QA. Reviews,
inspections and
walkthroughs. Testing
analysis models Jackson, "Object-Oriented
Analysis," "Graphic Notations" Write a one (or more)
page reaction and
analysis of Jackson on
OOA in your journal. Memos to detail how your
project meets 405 criteria
(Stearns). Get comments on
V&S, rework as elicitation
and analysis work goes into
SRS.

8 Requirements Quality
Jackson, "Models" Write a one (or more)
page reaction and
analysis of Jackson on
Models in your journal

9 Acceptance Tests and User
Manual Issues Continuing QA, prepare
acceptance tests from
requirements. Prepare
user manual.

Continue QA activities, review
and update schedules, work on
acceptance tests and user
manual (or equivalent help
system).

10

Week	*Expected Lecture* *Topics*	*Expected Lab* *Focus*	*Assigned Readings*	*Assignments*	*Other notes and expectations*
1	Introduction to Software Requirements	Team Formation	Chaos SE Code of Ethics Student Survival Guide Wie Ch 1 Jackson: "Descriptions" and "Machines"	Begin Journal - List of words to define in journal to be refined as we learn.	Team social meeting, name, motto, cover sheet identifying members and contact info
2	Introduction to Requirements Elicitation, where to start	Customer contact Define customer problem and context	Wie Ch 6,7 Jackson: "Procrustes," "Rough Sketches," and "Application Domain"		Working on draft Vision and Scope Document 6)
3	Process, Planning, Risks	Team processes Requirements Elicitation, Milestone Scheduling	Jackson: "Software," "Software Engineering," "Top Down"	Questions1 due in Journal by next Tuesday	Tuesday, Vision and Scope draft due Thursday, Project Risk document draft due.
4	Specifying Requirements	Elicit and develop requirements	Jackson: "Specifications," "Fudge Factor" RSL (link from Prof. Fisher's webpage)	Questions2 due in Journal by next Tuesday	Vision and Scope document due if necessary, Risks Document revision (and maintenance), present proposed Milestone Schedule to Instructor
5	Formal Specification	RSL and other formal methods to specify user requirments, continuing analysis and elicitation			Revision of Vision and Scope. Risks document maintenance. Keep current with your schedule
6	Requirements Analysis	Building models of requirements. Continue analysis and elicitation.			Coordinate documents to keep in synch. Produce one of each type of model discussed in classes and apply to appropriate parts of the requirements.
7	Requirements Quality	QA. Reviews, inspections and walkthroughs. Testing analysis models	Jackson, "Object-Oriented Analysis," "Graphic Notations"	Write a one (or more) page reaction and analysis of Jackson on OOA in your journal.	Memos to detail how your project meets 405 criteria (Stearns). Get comments on V&S, rework as elicitation and analysis work goes into SRS.
8	Requirements Quality		Jackson, "Models"	Write a one (or more) page reaction and analysis of Jackson on Models in your journal
9	Acceptance Tests and User Manual Issues	Continuing QA, prepare acceptance tests from requirements. Prepare user manual.			Continue QA activities, review and update schedules, work on acceptance tests and user manual (or equivalent help system).
10