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 with.

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 minuet) status report from each team.


Date

Lecture/Discuss in Class

Reading

Project milestones

Week 1
Mon. 9/29

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

 

Due: fill out and return team formation survey before class. Project 1 groups are assigned. first meeting.

Assembla team workspaces available:Team 1, Team 2, Team 3, Team 4, Team 5, Team 6, Team 7.

Week 1
Wed.
10/1

Software Processes

Download slides in PDF or in Powerpoint

Read Project Description

Process Models

Recent Software Failures: Of 2011, Agile

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

Due: look at example projects for some guidance. Familiarize yourselves with the assembla site:
1. Create accounts for all team members, then create the "Our Team" wiki page on your Assembla worksite
2. Create an entry for the first meeting on the Meeting Notes page
3. Choose initial roles and responsibilities for each team member, fill out roles on Project Plan page
4. Individuals fill out developer logs

Week 2
Mon. 10/6

Project Planning
Download slides in PDF or in Powerpoint

Standup Status Report: team meeting results

Advice on scheduling

Due:
1. Initial project plan including team member roles, risks and risk mitigations, choice of process, list of deliverables, and major milestones to the end of the first development iteration.
2. Fill out ConOps part of Requirements template, generate questions on expected behavior for customer (instructor).

Resources: Project planning summary, Create a PERT chart

Week 2
Wed.
10/8

Requirements analysis
Quality Assurance I:
Download slides in PDF or in Powerpoint

IBM Use Case Guide

Example Use Case: ATM

Due: 1) First draft of Requirements including key Use Cases and 2) First set of test cases. Everyone on the project need to know Use Case basics, 3) Initiate design: decompose software into work assignments.

Week 3
Mon. 10/13

Requirements & QA II
Download slides in PDF or in Powerpoint

Video Lecture here

Faulk: Software Requirements

Due: 1) Finalize requirements, 2) Draft of User's Guide, 3) initial implementation of all modules.

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

 

Week 3
Wed.
10/15

Group Dynamics
Download slides in PDF or in Powerpoint

Software Problems in the health care exchanges

Due: 1) initial implementation of all modules. 3) Module level testing

Week 4
Mon.10/20


 

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

Week 4
Wed.
10/22

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 by the end of the day (freeze Assembla pages).

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

Week 5
Mon. 10/27

Midterm Review: Recorded Lecture 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.
10/29

Midterm

 

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

Week 6
Mon. 11/3

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.
11/5

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

 

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

Week 7
Mon. 11/
10

Architecture III: Modularization
Download slides in PDF or in Powerpoint

 

 

Week 7
Wed.
11/12

Architecture IV: Design examples, class exercise
Second half of slides from the Architecture III lecture.

 

Data Banker Interface Specification example

Week 8
Mon. 11/
17

Architecture V: Documenting architecture
Download slides in PDF or in Powerpoint

 

Due: minimal subset (iteration 1 of code)

Week 8, Wed.11/19

Quality Assurance I:
Download slides in PDF or in Powerpoint

 

QA Plan Examples: DataMining Project and Cyclone Project (longer)

Week 9,
Mon. 11/
24

Quality Assurance II: Video lecture on software reviews (~35 mi.). Download slides in PDF or in Powerpoint

Guest Lecture: Software lead Cyndie Merten of Fabtrol

 

Due: second code increment

Week 9,
Wed.
11/26

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

 

Due: finalizing testing, documentation

Week 10,
Mon. 12/1

No class. Review lecture video convering materail since midterm.
Slides in PDF or Powerpoint

 

 

Week 10,
Wed.
12/3
Project 2 demos.  

Project 2 code is due (projects should be completed by Wed. 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)

Wed. Dec. 10, 2:45

Second Midterm (at the time scheuled for finals)