The following course information is taken from the official course description.
Catalog course description
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.
On successful completion of this course, the student will:
- understand the role of requirements engineering in a variety of software development models
- be able to elicit requirements from system stakeholders and to overcome common obstacles to the elicitation process
- be able to analyze and negotiate software requirements
- be able to specify software requirements using industry standard documentation techniques (e.g. UML, Use Cases etc.)
- be able to specify requirements that are verifiable, traceable, measurable and testable
- be able to verify that specified requirements are accurate, unambiguous, complete and consistent
- understand the importance and common methods of managing software requirements
- be able to communicate software requirements in written documents and oral presentations
Textbook and reference materials
The course textbook is Mastering the Requirements Process, 2nd ed., by Suzanne Robertson and James Robertson, Addison-Wesley, 2006.
My general course policies apply to this course. However, in general, assignments will not be accepted after the submission deadline. If there are extenuating circumstances, advise the instructor immediately, preferably before the deadline.
- Quizzes/homework: 20%
- Lab assignments: 30%
- Midterm exam: 25%
- Final exam: 25%
Note that this algorithm indicates how a grade will be determined for students who have successfully demonstrated mastery of the course outcomes. An acceptable level of success in meeting all course outcomes is a prerequisite for a passing grade in the course.