Syllabus
35365 SWEN
5130-01 Requirements Engineering
SPRING SEMESTER 2013 January 14 - May 6
This page is definitely the most important page in this entire course. Take the time to print this page, as it contains all the information you need to know about this course. The student can download and read the course content, however the instructor will also look at the number of times the student has accessed the content pages. The instructor will use the student’s access of the content to insure that the student has accessed the course throughout the semester. A set of questions at the end of each lecture will be available for the student’s comprehension and understanding of the material. There will be a classroom midterm and final if the student is on or near the UHCL campus.
Course Description
The goal of Requirements Engineering course is to introduce the processes involved in the concept, eliciting, developing, analyzing, validating and managing requirements for complex systems.
The course presents the common forms of the software life cycle, which are used throughout the commercial, industrial, institutional, and even governmental communities when a single development effort is appropriate and military standards or other government standards are not mandated. The model is referred to as the commercial life cycle. The focus is on what is involved in requirements engineering and how specific techniques may be applied during the life cycle processes.
The stakeholders' needs document, concept or vision document and the requirements document are presented and preliminary versions developed. The critically important process of managing requirements, which are evolving as the customers' business and priorities change, is presented.
Outcomes
At the completion of the requirements engineering course the student will be able to:
· Understand the processes involved in eliciting, developing, analyzing, validating and managing requirements for complex systems
· Name and reproduce the common forms of the software life cycle
· Apply specific techniques involved in requirements engineering during the life cycle processes
· Compose and design a stakeholders' needs document, a vision document and a requirements document
Instructor
Dr. James Helm, helm@uhcl.edu. Please e-mail the instructor for this semester's office hours.
Required Materials
Required Book: Managing Software Requirements Second Addition: A Use Case Approach
Authors: Dean Leffingwell & Don Widrig
Publisher: Addison-Wesley 032112247X 544 pp,
Three MS Word Document Templates (notice the extension .dot).
Download the zip file of these templates. You will use
these templates to complete projects 1, 2, 3.
Schedule and Assignments
This table lists all the readings and assignments you are responsible for. Feel free to print and use this table as a checklist for this course. The student can download and read the course content, however the instructor will also look at the number of times the student has accessed the content pages. The instructor will use the student’s access of the content to insure that the student has access the course throughout the semester. A set of questions at the end of each lecture will be available for the student’s comprehension and understanding of the material. There will be a classroom midterm and final if the student is on or near the UHCL campus.
|
Week |
DESCRIPTION SPRING SEMESTER
Jan 14-May 6, 2013 |
|
Week 1 Jan 13 - Jan 19 |
Software Development Requirements Overview
|
|
Week 2 Jan 20 - Jan 26 |
|
|
Week 3 Jan 27 - Feb 2 |
|
|
Week 4 Feb 3 - Feb 9 |
Read Software Development Roles and Responsibilities
|
|
Week 5 Feb 10 - Feb 16 |
Software Development Process Kernels
|
|
Week 6 Feb 17 - Feb 23 Last day to drop with no grade |
Commercial Life Cycle Model
|
|
Week 7 Feb 24 - Mar 2 |
Carnegie Mellon Capability Maturity Model
|
|
Week 8 Mar 3 - Mar 9 |
Mid Term over Modules 1-5 |
|
Week 9 Mar 10 - Mar 16 |
Rational Unified Process
|
|
Week 10
Mar 17 - Mar 23 |
University Registration Case Study
|
|
Week 11 |
Stakeholder's Needs & Analysis
|
|
Week 12 Mar 31 - Apr 6 |
Vision Development
|
|
Week 13 Apr 7 - Apr 13 |
Vision Development
|
|
Week 14 |
Requirements Development
|
|
Week 15 Apr 21 - Apr 27 |
Requirements Development
|
|
Week 16 Apr 28 - May 4 |
Group Project 3 - Requirements Document
turn in for grading |
| Week 17 May 5 - May 11 | Final Exam May 5 - 11 over Modules 6-10 |
Assignments
Assignments will be graded according to the following percentages.
|
Assignments |
Percent |
|
Activities 1 - 3 |
10% |
|
Project 1 -Stakeholders Document and questionnaire |
10% |
|
Project 2 - Vision Document |
20% |
|
Project 3 - Requirements Document and related documents |
20% |
|
On Quizzes for comprehension of Mid-Term and Final. |
0% |
|
|
|
|
Mid Term |
20% |
|
Final |
20% |
The Honesty Code is the University community's standard of honesty and is
endorsed by all members of the
Academic honesty is the cornerstone of the academic integrity of the University. It is the foundation upon which the student builds personal integrity and establishes a standard of personal behavior.
Because honesty and integrity are vital to society and to individuals' emotional and ethical well-being, failure to perform within the bounds of academic honesty is sufficient grounds to receive a grade of "F" in this course and be recommended for suspension from the University.
The Honesty Code at UHCL states, "I will be honest in all of my academic activities and will not tolerate dishonesty."
This code of conduct is more fully defined and elaborated in the University Catalog and on the UHCL Web site at http://b3308-adm.uhcl.edu/PolicyProcedures/Policy.html. This course will function under this Honor Code.
Americans with Disability Act (ADA)
Statement
If you have any special needs due to a disability please feel free to contact the instructor of this course. For information of disability accommodations and access, please contact the Disability Services Office, or call 281-283-2627.