Software Requirements Engineering


Com S 409/509 Fall 2009
Tuesday and Thursday 9:30 - 10:50am
3149 Pearson

Announcements

 

 

·         11/17 Project, Software Requirements Specification due beginning of class, Thursday, Dec. 4.  More information about the team presentations will be given in class.  Presentations will be Dec. 8 and Dec. 10.

·         11/17 Homework #4, due beginning of class, Tuesday, Dec. 2.  Note in-class exercises.

·         11/5 Lecture on AADL and Decision Model, slides download

·         11/3 John Mylopoulos's Paper & Presentation

·         11/3 Homework #3, due beginning of class, Thursday, Nov. 12

·         10/27: Midterm Exam Key Released, Download Here

·         10/20: Midterm Exam in class Thursday, 10/22

·         10/20 My class notes (partial & incomplete). Chap. 5; Chap. 6; Chap. 7; Chap. 8; Chap. 9; Chap. 10

·         10/15: More Information and Example for DOORS . Updated with some students’ questions.

·         9/24: IBM Rational DOORS installation guide.

·         9/24:  Homework #2, due beginning of class, Thursday, Oct. 8.  Download for Axel van Lamsweerde's paper.

·         9/22: No class on Tues. Attend Career Fair instead, 12 - 6 in Hilton. Send email noting at least 3 companies with whom you spoke.

·         9/16:  HW #1 due date extended to beginning of class, Thursday, Sept. 24.

·         9/15:  fyi (not for class): 2 papers from the 13th Int’l Software Product Line Conf (SPLC’09) and the 2nd Int’l Workshop on Managing Requirements Knowledge (MaRK’09 at RE’09) that we presented recently 

·         9/10:  Homework #1, due beginning of class, Tuesday, Sept. 22. Off-Campus Download for Jackson's Paper

·         9/3: Lecture2/ Lecture3 slides. Download

·         8/24: Attendance at Thursday, 8/27 class will be substituted by attendance at upcoming colloquium

 

Staff


Instructor: Dr. Robyn R. Lutz


TA: Hongyu (Russell) Sun

Textbook

Course Information

Description:   Prereq: Com S 309, Engl 250, Sp Cm 212. The requirements engineering process, including identification of stakeholders, requirements elicitation techniques such as interviews and prototyping, analysis fundamentals, requirements specification, and validation. Use of Models: State-oriented, Function-oriented, and Object-oriented. Documentation for Software Requirements. Informal, semi-formal, and formal representations. Structural, informational, and behavioral requirements. Non-functional requirements. Use of requirements repositories to manage and track requirements through the life cycle. Case studies, software projects, written reports and oral presentations. 

Syllabus

Resources

Grading

Adapted from Provost Office H1N1 guidelines: Public health experts predict that the highly contagious H1N1 virus will re-emerge this fall.  The university will encourage students who are experiencing flu symptoms to stay home and follow the CDC’s self-isolation guidelines.

·         Stay home: The CDC recommends that people with flu-like illness remain at home at least 24 hours after they are symptom-free. 

·         Self-isolate: Inform me by email or phone.  Do not visit the classroom or offices. 

·         I’ll provide a reasonable way to make up missed work for a successful semester.

·         It is best to rest and stay home, away from others, if you think you may be getting sick.

Iowa State University complies with the Americans with Disabilities Act and Section 504 of the Rehabilitation Act.  Any student who may require an accommodation under such provisions should contact me no later than the end of the first week of class or as soon as you become aware of it.