Skip to main content.
Skip to main content.

Overall Organization

Each Week

Many Mondays beginning week 2 will begin with short presentations by each project team. Typically these will be done in the form of a "standup" report. You should also provide constructive criticism of both content and presentation to other teams.

Many Fridays will be used, at least in part, for group meetings (with or without the instructor) and discussion.

Notes on presentation

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 preliminary and subject to change over the term.

Readings: Readings are from the van Vliet text with occasional downloads. Reading should be done before the class where they are listed. There are a few additional notes below the schedule. Papers labeled "522" are additional readings from the literature required for graduate students and recommended for undergraduates.

Date

Lecture/Discuss in Class

Reading

Project milestones

Week 1
Mon (9/24)

Overview of Software Engineering and the class. Slides in PDF.

 

Hand out team formation survey

Week 1
Wed.

Teamwork. Effective meetings. Slides in PDF.

Text: 1

Due: Read Project Description, fill out and return team formation survey

Week 1 Fri.

Walkthrough of assembla project work sites. Team assignments

Text: 5

Project 1 groups are assigned. First meeting

Week 2
Mon. (10/1)

Software Processes. Slides in PDF

Text: 2, & 3

522: "Fake it" paper

Due: Team page on your Assembla worksite

Quick Status: team meeting, status
First meeting completed, project chosen

Week 2
Wed.

Project Planning. Slides in PDF

Text:. 8

Due: Draft project plan including team member roles, risks and risk mitigations, choice of process, and major milestones to the end of the first development iteration (week 5)

Week 2
Fri.

Project Requirements and goals

 

 

Week 3
Mon. (10/8)

No class scheduled, work on projects

 

Text: 9

Due: Draft requirements

Week 3
Wed.

Requirements analysis: understanding requirements. Slides in PDF

522: Faulk Requirements

Review: Groups meet with instructor. Set up time for team to meet with instructor.

Week 3
Fri.

Requirements methods

   

Week 4
Mon. (10/15)

Technical session (lecture delayed to accommodate)

 

Due: revise requirements for first iteration

Week 4
Wed.

Use Cases & Documentation. Slides in PDF

 

Due: system design documentation

 

Week 4
Fri.

Architecture and design introduction    

Week 5
Mon. (10/22)

Project 1 review and post mortem

 

Project 1 is due. Groups present Project 1 results and lessons learned. Use this guideline for your team presentation.

Week 5
Wed.

Project 1 Presentations continued

Midterm Review: Slides in PDF.

 

 

Week 5
Fri.

Midterm

 

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

Week 6
Mon. (10/29)

Midterm Postmortem:

Architecture I: Slides in PDF

Text: Ch.  11

Project Phase 2 Kickoff

Schedule meeting with Instructor for Project 1 review, Phase 2 planning

Week 6
Wed.

Instructor meetings

 

 

Week 6
Fri.

Instructor meetings: No class

   

Week 7
Mon. (11/5)

Complete Architecture I

 

Updated Plan, Iteration 2

Updated ConOps, key features added for Iteration 2 (prioritized according to those you must accomplish, should accomplish, want to accomplish)

Week
Wed.

Architecture II: Mitralization and information hiding. Slides in PDF

 

Draft Quality Assurance and Testing Plan (How will you establish that your software meets its requirements?)

Week 7
Fri.

   

Updated Requirements Specification

Draft architectural design document

Week 8
Mon. (11/12)

Verification and Validation. Slides in PDF

Text: Ch. 12.1-12.4

Data Banker Interface Specification example

Week 8 Wed.

Architecture III: Architectural documentatio. Slides in PDF.

 

 

Week 8
Fri.

Midway project 2 review -->   Quick project reviews in class: roughly 5 minute update with each team.

Week 9
Mon. (11/19)

Architecture IV: Interface design

 

 

Week 9
Wed.

No class

 

 Work on projects

Week 9
Fri.

Thanksgiving break: no class

   

Week 10
Mon. (11/26)

Final lecture and course review. Slides in PDF.

 

 

Week 10 Wed.

Project 2 demos.

 

Complete all assembla pages.

Week 10
Fri.

Project 2 demos.

 

All Project 2 materials due. Read instructions for final presentations and handins here (donwload)

Fill out final team member evaluations. Here are electronic versions in Word (.docx), Rich Text (.rtf) and PDF (.pdf). Please email to me or print and leave in my box (or office).

Notes: