402schedule

This schedule is based on a 2002 version of the course and will change as needed since the course tends to be dynamic and we have a new customer. Please look to this directory for lecture slides for your use. They are in no particular order and will appear before or shortly after the lecture.

Assignments and notes about deliverables will be added and modified as needed.

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

1 Introduction to Software
Requirements
Introduce customer.
Team Formation
GPS research?
Customer contact

Wiegers Part 1 (Ch 1 - 4)
Jackson: "Descriptions" and
"Machines"
Look at Yourdon
Locate and Purchase Texts.
Begin Journal - List of words to define in journal to be refined. Produce a Team cover sheet with critical information for instructor. Domain research. Lecture Notes 1, Lecture Notes 2, Lecture Notes 3
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 - learn about domain
Wiegers Ch 5 - 7
Jackson: "Procrustes," "Rough
Sketches," and "Application
Domain"
Continue Yourdon
Team activity reports to class. Structure open. Team cover sheets due on Monday. Domain research.
Working on draft Vision
and Scope Document
(Wie Ch 6)

3 Process, Planning, Risks Team processes
Requirements
Elicitation, Milestone
Scheduling Wiegers Ch 7-9
Jackson: "Software,"
"Software Engineering,"
"Top Down" Submit questions for customer to clarify Vision and Scope work Tuesday, Vision and Scope
draft due.
Friday: Project Risk
document draft due.

4 Specifying Requirements Elicit and develop
requirements Wiegers Ch 10-12
Jackson: "Specifications,"
"Fudge Factor"
RSL (link from Prof. Fisher's
webpage) Vision and Scope document due.
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 Wie Ch 12-
I apologize for a misdated assignment that was here, I will repost when and if it becomes important. If you wrote up Assignment 1 already, show me, you will receive some credit. Continue to get input from customer and other sources for requirements. Formulate good written questions. Revision of Vision and Scope.
Risks document maintenance.
Keep current with your schedule

6 Requirements Analysis Building models of
requirements. Continue
analysis and elicitation. Wie Ch 13, 14 Perform Team Evaluations and turn in Monday (in paper).
Review the practice questions for the midterm coming soon. 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
page reaction and
analysis of Jackson on
OOA in your journal. Plan for 17 Nov trip to Trimble in Sunnyvale

Elicitation and analysis proceeds with SRS.

8 Requirements Quality

Jackson, "Models" Write a one
page reaction and
analysis of Jackson on
Models in your journal Prioritize deliverables list with Top Level managers and Trimble for rational final schedule.

9 Acceptance Tests and User
Manual Issues, if any Continuing QA, Basic Architectural design

Continue QA activities, review
and update schedules.

10

11

Week	*Expected Lecture* *Topics*	*Expected Lab* *Focus*	*Assigned Readings*	*Assignments*	*Other notes and expectations*
1	Introduction to Software Requirements Introduce customer.	Team Formation GPS research? Customer contact	Wiegers Part 1 (Ch 1 - 4) Jackson: "Descriptions" and "Machines" Look at Yourdon	Locate and Purchase Texts. Begin Journal - List of words to define in journal to be refined. Produce a Team cover sheet with critical information for instructor. Domain research. Lecture Notes 1, Lecture Notes 2, Lecture Notes 3	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 - learn about domain	Wiegers Ch 5 - 7 Jackson: "Procrustes," "Rough Sketches," and "Application Domain" Continue Yourdon	Team activity reports to class. Structure open. Team cover sheets due on Monday. Domain research.	Working on draft Vision and Scope Document (Wie Ch 6)
3	Process, Planning, Risks	Team processes Requirements Elicitation, Milestone Scheduling	Wiegers Ch 7-9 Jackson: "Software," "Software Engineering," "Top Down"	Submit questions for customer to clarify Vision and Scope work	Tuesday, Vision and Scope draft due. Friday: Project Risk document draft due.
4	Specifying Requirements	Elicit and develop requirements	Wiegers Ch 10-12 Jackson: "Specifications," "Fudge Factor" RSL (link from Prof. Fisher's webpage)		Vision and Scope document due. 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	Wie Ch 12-	I apologize for a misdated assignment that was here, I will repost when and if it becomes important. If you wrote up Assignment 1 already, show me, you will receive some credit. Continue to get input from customer and other sources for requirements. Formulate good written questions.	Revision of Vision and Scope. Risks document maintenance. Keep current with your schedule
6	Requirements Analysis	Building models of requirements. Continue analysis and elicitation.	Wie Ch 13, 14	Perform Team Evaluations and turn in Monday (in paper). Review the practice questions for the midterm coming soon.	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 page reaction and analysis of Jackson on OOA in your journal.	Plan for 17 Nov trip to Trimble in Sunnyvale Elicitation and analysis proceeds with SRS.
8	Requirements Quality		Jackson, "Models"	Write a one page reaction and analysis of Jackson on Models in your journal	Prioritize deliverables list with Top Level managers and Trimble for rational final schedule.
9	Acceptance Tests and User Manual Issues, if any	Continuing QA, Basic Architectural design			Continue QA activities, review and update schedules.
10
11