Skip to main content.
Skip to main content.

Overall Organization

Each Week

Notes on presentations

Presentation duties should rotate among team members. Presentation and verbal communication skills are important; use this as an opportunity to practice in a friendly environment. Everyone should give at least part of one presentation during the term.

I know some people have anxiety about public speaking since I have had this as well. If you do not feel able to take a turn presenting to the class, come talk to me about it.

Week by Week Schedule

This schedule is approximate and will change in response to class needs. It will be updated to reflect current assignments and any changes in class schedule. You should check the schedule routinely during the quarter to make sure you are keeping up as things change.

Readings: Reading should be done before the class where they are listed. Papers labeled "522" are additional readings from the literature required for graduate students and recommended for undergraduates.

Status Reports: Monday classes will begin with a quick (2-3 minute) status report from each team.


Date

Lecture/Discuss in Class

Reading

Project milestones

Week 1
Mon. 1/9

School closed.

Read Project Description

Read Team Roles

 

Due: fill out and return team formation survey before class.

Read Project 1 requirements and discussion of team roles. Consider which roles you would be best suited for and most interested in trying.

Week 1
Wed.
1/11

Overview of Software Engineering and the class.
Download slides in PDF
or in Powerpoint

 

Assembla team workspaces available:Team 1, Team 2, Team 3, Team 4, Team 5, Team 6. Retrieve templates for Wiki pages from

Project 1 groups are assigned. first meeting.

Week 1
Fri. 1/13

Software Processes
Download slides in PDF or in Powerpoint
Assembla workspaces


Process Models. Short summary description.

Recent Software Failures: of 2011, Agile

Examples of of project workspaces from past 422 and 423 classes: Example1, Example2 and Example 3. While overall good examples, these should not be emulated without thought.

Milestones: Look at example projects for some guidance. Familiarize yourselves with the Assembla site and complete the following:
1. All team members added to Assembla.
2. Initial roles decided and documented on the Project Plan page.

Week 2
Mon.
1/16

Project Planning. Download slides in PDF or in Powerpoint.

Lecture video (~35 min.)

Advice on scheduling

Team Exercise: process model exercise on Piazza. Discuss which process models would, or would not, make sense for your projects.

Deliverables:
1. Fill out initial cut at Project Plan to include: roles and responsibilities for each team member, risks and risk mitigations, choice of process, list of deliverables, and major milestones to the end of the first development iteration. Use milestones from this column to start with.
2. Meeting Notes for any meetings held (at least first meeting)
3. Individuals have filled out developer logs for Week 1

Week 2
Wed.
1/18

Project Planning (cont'd). Project planning exercise

Short lecture on Use Cases. Download slides in PDF or in Powerpoint.

IBM Use Case Guide

Example Use Case: ATM

Milestones:
1. Fill out ConOps part of Requirements template (may copy parts of assignment)
2. Generate questions on expected behavior for customer (instructor).
3. Work together to create a one or two use cases.

Resources: Project planning summary, Create a PERT chart

Week 2
Fri.
1/20

Requirements analysis and
Quality Assurance I: Video lecture here
Download slides in PDF or in Powerpoint

Use cases: In class exercise.
(a few additonal slides used in class in PDF and Powerpoint)

Deliverables walkthrough

Faulk: Software Requirements

Plan "customer" meetings with instructor.

Milestones: Everyone on the project should know Use Case basics
1. First draft of Requirements including key Use Cases
2. First set of test cases based on Use Cases
3. Initiate design: decompose software into work assignments.

Week 3
Mon. 1/
23

Requirements & QA II
Download slides in PDF or in Powerpoint. We'll cover most of this in class but there is also a lecture video on line. (Let me know if you have trouble viewing it.)

 

Deliverables:
1. Finalize requirement,
2. Draft of User's Guide

Critical: should include communication and at least one meeting with the client to ensure requirements correctness.

Week 3
Wed.
1/25

Address Book requirements exercise. Discussion of detailed requirements.

Software Problems in the health care exchanges

Due: Midway review: Increment 1 due, artifacts graded focusing on whether the team is producing all the artifacts needed and shows basic understanding of planning.

Week 3
Fri.
1/27

Short progress meetings with instructor.

 

 

Week 4
Mon.
1/
30

Quality Assurance I:
Download slides in PDF or in Powerpoint

 

Due: Final increment integration.

QA Plan Examples: Cyclone Project (short) and a Data Mining Project (longer)

Week 4
Wed.
2/1

Group Dynamics:
Download slides in PDF or in Powerpoint
.

 

Due: Acceptance testing, final bug fixes, draft of presentation for practice.

Week 4
Fri. 2/3

Project 1 Presentations

Slides on final submissions: PDF

 

Project 1 is due. Groups present Project 1 results and lessons learned. Use this guideline for your team presentation. All project materials are due class time (freeze Assembla pages).

Fill out Peer Evaluation Forms and return (Word or PDF format)

Week 5
Mon. 2/
6

Midterm Review: Recorded Lecture video here
Download slides in PDF or in Powerpoint

Project Phase 2 Kickoff: project ideas

Midterm Review Questions

Due: Selection of Project 2 or proposal in the form of a draft ConOps document.

Review: meeting with Instructor for Project 1 review, Project 2 planning

Week 5
Wed.
2/8

Midterm

 

In class midterm, multiple choice and short answer. Closed book and notes.

Week 5
Fri. 2/10

Quality Assurance: Testing and test planning:
Slides in PDF or Powerpoint

   

Week 6
Mon.
2/13

Architecture I: Introduction to software architecture
Download slides in PDF or in Powerpoint

 

Due: ConOps complete, initial project plan including schedule and milestones.

Week 6
Wed.

2/
15

Architecture I continued.

 

Due: first draft of SRS, identify and prioritize project risks, plan for risk mitigation

Week 6
Fri.
2/17

Architecture II: Design goals and the meaning of "design" in the software context
Download slides in PDF or in Powerpoint

   

Week 7
Mon.
2/20

Architecture III: Modularization
Download slides in PDF or in Powerpoint

 

 

Week 7
Wed.
2/22

Architecture III: Design examples, class exercise: Address Book Design

 

 

Week 7
Fri. 2/24

Architecture IV: Design examples. Download slides in PDF or in Powerpoint

   

Week 8
Mon.
2/27

Architecture IV (contd.): design principles

 

Due: minimal subset (iteration 1 of code)

Data Banker Interface Specification example

Week 8,
Wed.
3/1

Architecture VI: Documenting architecture
Download slides in PDF or in Powerp oint

 

 

Week 8
Fri. 3/3

Architecture VI (cont'd): Module interface specification

 

Example of Architectural design documentation (grad student projects done by professional developers) RequirementsReader

Example of Module Structure documentation for a simple system: Floating Weather Station Requirements and Module Guide

Week 9,
Mon.
3/6

In class team meetings with instructor: progress check

 

Due: second code increment

Week 9,
Wed.
3/8

Quality Assurance III: lecture video (choose the video "Quality Assurance Software Reviews"). Slides in PDF or in Powerpoint

In class team meetings with instructor: progress check

 

Due: finalizing testing, documentation

Week 9
Fri. 3/10

TBD

   

Week 10,
Mon.
3/13

 

 

 

Week 10,
Wed.
3/15

Early project demos?

 

 

Assembla pages for the Project Plan, Requirements, and Architecture should be frozen and available for evaluation. Teams should inform the instructor if they cannot meet this deadline.

Week 10
Fri. 3/17

Project 2 demos.  

Project 2 code is due (projects should be completed by class time). Read instructions for final presentations and hand-ins here (download). Read the Project Grading page for details on how your project will be graded.

Fill out Peer Evaluation Forms and return (Word or PDF format)

Mon. March 20th 10:15

Second Midterm

Review lecture video covering material since midterm.
Slides in PDF or Powerpoint