SE-3821: Software Requirements and Specification

Fall 2008

Instructor Dr. Ben Uphoff
Office L342
Phone (414) 277-7326
Email uphoff@msoe.edu
AIM uphoffmsoe
Meeting Times Monday/Wednesday/Friday 10-10:50am (Lecture)
Tuesday 9-10:50am (Lab)

Location CC51 (Lecture)
CC43 (Lab)
Office Hours Monday 3-4pm,
Thursday 9-10am (IM only),
Thursday 10-11am or by appointment


Course Description

From the MSOE catalog:


This course covers activities that relate to the determination and documentation of software system requirements. Topics covered include requirements elicitation, object-oriented analysis techniques, prototyping, requirements tracking and re-engineering.


Please consult the official course description for more detailed information and course outcomes. We will be collaborating with Biomedical Engineering student for the content of all assignments. Teams of BE students will be matched with groups of SE students for the course project. More details of this interaction will be given in class.

Schedule (subject to change)

Week

Lecture 1 (Monday)

Lab (Tuesday)

Lecture 2 (Wednesday)

 

Lecture 3 (Friday)

1
  • Course Introduction
  • Expectations for the quarter
  • What are Requirements? (Ch 1)
PDF
  • Discuss the BE/SE collaboration
  • Email client requirements discovery exercise [PDF]
  • Software design models
  • "Rabbit-Horse-Elephant"
PDF
2 
  • Dr. Tritt will present BE projects to class
  • More on the Requirements Process (Ch 2)
  • Group assignments announced
  • Research project domain
  • Initial meeting with BE teams

  • More on the Requirements Process (Chapter 2)
  • Discuss Assignment 1
  • Begin Project Blastoff (Chapter 3) if time allows [PDF]
Project Blastoff (Chapter 3) [PDF]
3
  • Review Projects Goals, make updates as needed
  • Work on Assignment 1
 Event-driven Use Cases (Chapter 4) [PDF] [Google Doc]
  • Submit Assignment 1
  • Event-driven Use Cases (contd.)
4

Work on Assignment 2

 Trawling for Requirements        (Chapter 5) [PDF] [Google Doc]
  • Submit Assignment 2
  • Scenarios and Requirements        (Chapter 6) [PDF] [Google Doc]
5  Work on Assignment 3 Midterm Exam
  • Midterm Exam Post-Mortem
  • Functional Requirements (Chapter 7) [Google Doc]
6

Nonfunctional Requirements (Chapter 8) [Google Doc]
  • Review Use-cases
  • Work on Assignment 3
 In-class exercise on Functional/Non-functional Requirements
  • Submit Assignment 3
  • Discuss In-Class excercise results
  • Security and Privacy [Google Doc]
7

Work on Assignment 4

 Quality Attributes [Google Doc] In class exercise [DOC]  Fit Criteria (Chapter 9) [Google Doc]
8 Writing the Requirements (Chapter 10) [Google Doc]
  • Review requirements and their respective fit criteria
  • Work on Assignment 4

 Quality Gateway (Chapter 11) [Google Doc]
  • Submit Assignment 4
  • Reviewing the Specification (Chapter 14) [Google Doc]
9 Work on Assignment 5 with emphasis on  implementing the Quality Gateway Work on Assignment 5 with emphasis on Reviewing Specifications

Work on Assignment 5

 Review for Final
10
  • Topic TBA
  • Submit Assignment 5
Final Exam (2 hours!) Work on Final Presentation Final Presentation Dry Run
11 Final Presentations with BE students

Requirements Resources

Grading

Note that this algorithm indicates how a grade will be determined for students who have successfully demonstrated mastery of the course objectives. An acceptable level of success in meeting all course objectives is a prerequisite for a passing grade in the course.


Criterion Weight
Assignments 40%
Final Presentation 10%
Midterm 25%
Final Exam 25%

This page was last updated on 09/05/2008. Content heavily borrowed from Dr. Deepti Suri.