Week	Session	Class topics	Deliverable due	Points
Week 1	1	How to work as a team
	2	Meet team leaders; Review project descriptions	Exercise 1 - DyKnow	10
	3	Team time: Prepare for first meeting with client ("Build a relationship")	Exercise 2 - Team building	10
	4	A road map for Software Requirements and Specifications Team Skill 1: Analyzing the Problem Problem Analysis: Step 1 - Problem definition, Short-version Problem Statement	Agenda for first meeting with your client	10
Week 2	5	Problem Analysis: Step 2 - Root causes, Fishbone diagram, Pareto chart	Skim-read Chapter 1 ("The Requirements Problem") Skim-read Chapter 2 ("Introduction to Requirements Management")	10 10
	6	Team time: Prepare for second meeting with client ("Elicit short-version problem statement")	Notes from and attendance at first meeting with client	100
	7	Problem Analysis: Steps 3, 4 and 5 - Stakeholders,Boundary, Constraints	Agenda for second meeting with your client	10
	8	Big Picture of Software Requirements and Specifications -- Why it is important	Skim-read Chapter 5 ("The Five Steps in Problem Analysis")	10
Week 3	9	Models of software development - Waterfall, Spiral, Iterative	Notes from and attendance at second meeting with client Read Chapter 6 ("Business Modeling") Read Chapter 7 ("Systems Engineering of Software-Intensive Systems")	100 20 20
	10	Team time: Work toward short-version problem statement	Fishbone diagram for short-version problem statement Skim-read Chapter 3 ("Requirements and the Software Lifcycle") Skim-read Chapter 4 ("The Software Team")	20 10 10
	11	Team Skill 2: Understanding User and Stakeholder Needs	Pareto chart for short-version problem statement	20
	12	Peer review short-version problem statements	Short-version problem statement	100
Week 4	13	Team Skill 2: Understanding Needs - Problem statement, Features	Peer reviews of short-version problem statements	20
	14	Guest speaker
	15	Team Skill 2: Interviews	Revised short-version problem statement Exercise - What is a Problem Statement?	50 10
	16	Team time: Prepare questions for interview with client ("Agree on problem statement, Elicit features")	Skim-read Chapter 8 ("The Challenge of Requirements Elicitation") Skim-read Chapter 9 ("The Features of a Product or System")	10 10
Week 5	17	Team Skill 2: Understanding Needs - Requirements Workshops, Brainstorming and Idea Reduction	Skim-read Chapter 10 ("Interviewing") Prepared questions for individual interview(s)	10 100
	18	Team Skill 2: Understanding Needs - Requirements Workshops, Brainstorming and Idea Reduction	Skim-read Chapter 11 ("Requirements Workshops") Notes from individual interview(s)	10 100
	19	Team Skill 2: Understanding Needs - Storyboards	Notes from and attendance at client meeting regarding features	100
	20	Team Skill 3: Defining the System - Use Cases	Skim-read Chapter 12 ("Brainstorming and Idea Reduction") Skim-read Chapter 13 ("Storyboarding")	10 10
Week 6	21	Team time: Work toward completing problem statement and/or use cases	Skim-read Chapter 14 ("A Use Case Primer")	10
	22	Team Skill 3: Defining the system - Vision document	Problem Statement	300
	23	Team time: Work toward completing Storyboard and/or Vision Document	Exercise - What is a Vision Document?	10
	24	Team time: Work toward completing Storyboard and/or Vision Document	Skim-read Chapter 15 ("Organizing Requirements Information") Skim-read Chapter 16 ("The Vision Document")	10 10
Week 7	25	Team Skill 5: Refining the System Definition - Refining the Use Cases	Vision Document	300
	26	Peer review Problem Statements	Skim-read Chapter 17 ("Product Management") Storyboard	10 200
	27	Team time: Work toward completing Use Case Model	Skim-read Chapter 20 ("Software Requirements - A More Rigorous Look") Skim-read Chapter 21 ("Refining the Use Cases") Revised Problem Statement	10 10 100
	28	Team Skill 4: Managing Scope - Introduction	Client signed off on Problem Statement Notes from and attendance at client meeting presenting Storyboard	10 100
Week 8	29	Team Skill 4: Managing Scope - Requirements Baseline	Use Case Model Diagam Use Case Model	50 300
	30	Team time: Work toward completing your Requirements Baseline	Skim-read Chapter 18 ("Establishing Project Scope") Read Chapter 19 ("Managing Your Customer")	10 10
	31	Team Skill 5: Refining the System Definition - Supplementary Specifications	Requirements Baseline	200
	32	Interaction Design - Introduction	Skim-read Chapter 22 ("Developing the Supplementary Specifications") Notes from and attendance at client meeting presenting Use Case Model	10 100
Week 9	33	Schneiderman's Eight Golden Rules for User Interface Design	Read Chapter 1 of Interaction Design ("What is Interaction Design?") Read Chapter 6 of Interaction Design ("The Process of Interaction Design")	20 20
	34	Schneiderman's Rules, continued Team time: Prototype User Interface - How does Chapter 8 feed into your User Interface Design?	Split with team - Read and summarize Chapters 7 and 8 of Interaction Design ("Identifying Needs and Establishing Requirements" and "Design, Prototyping and Construction")	50
	35	Team time: Prototype User Interface - How does Chapter 8 feed into your User Interface Design?	Schneiderman's Golden Rules exercise Supplementary Specifications	100 200
	36	Team time: Prototype User Interface - How does Chapter 8 feed into your User Interface Design?	Notes from and attendance at client meeting negotiating your Requirements Baseline	100
Week 10	37	Interaction Design - Evaluation	Revised Use Case Model Diagam Revised Use Case Model	50 100
	38	Managing change Assessing requirements quality	Delta Vision Document	100
	39	Exam	Assessment of Requirements Quality - Checklist Exam on K and C-level learning outcomes	100 300
	40	Course evaluations	How Chapter 8 of Interaction Design applies to your prototype user interface Your evaluation of your team members' work Your evaluation of your own work	100 100 100
Exam week	Early in exam week	Show your client and instructor your prototype user interface	Your prototype user interface	400
	By end of exam week	Show your instructor your evaluation of your prototype user interface	Your evaluation of your prototype user interface	50
			Total points is about	4500