Computer Science and Software Engineering 371

Software Requirements and Specification (“Reqs & Specs”)

Fall 2005

Course Syllabus

Instructor: Don Bagert

Office: Moench Hall, Room H224

Phones: (work) 877-8327; (home) 877-2285; (cell) 201-6084

Email: Don.Bagert@rose-hulman.edu

Course Meeting Times: (Section 1) 8^th period MTRF

(Section 2) 9^th period MTRF

Office Hours:

• MTRF – 3^rd, 4^th and 7^th periods
• W – 8^th and 9^th periods

Course Prerequisite: CSSE 230 (Fundamentals of Software Development III) or equivalent

Course Description: Basic concepts and principles of software requirements engineering, its tools and techniques, and methods for modeling software systems. Topics include requirements elicitation, prototyping, functional and non-functional requirements, object-oriented techniques, and requirements tracking.

Course Objectives:

1. Understand the role of requirements engineering and its process

2. Use analysis techniques to develop a problem statement

3. Use multiple techniques to elicit requirements from stakeholders

4. Take the elicited requirements and develop a specification with functional and non-functional requirements

5. To be able to negotiate with the client and other stakeholders regarding priorities and scope

6. Use quality assurance techniques to verify that requirements are: verifiable, traceable, measurable, testable, accurate, unambiguous, consistent, and complete

7. Know how to manage requirements

8. To be able to develop and use user interface prototypes to validate requirements

Course Texts (Both Required):

· Managing Software Requirements: A Use Case Approach, Second Edition, by Dean Leffingwell and Don Widrig (ISBN 0-321-12247-X)

· Interaction Design: beyond human-computer interaction by Jennifer Preece, Yvonne Rogers and Helen Sharp (0-471-49278-7)

Course Evaluation and Feedback: Please feel free to provide me feedback about the course at any time. Also, an anonymous feedback box under the ANGEL account for this course will be available for feedback throughout the course; I will check it sometime during each weekend. There will also an anonymous midterm evaluation of the course.

I also recommend that you keep a “course evaluation log” somewhere to make notes that you can use for the course evaluation at both midterm and the end of the course.

Course Average Determination:

40%	Software Team Project Work (details below)
14%	Exam 1
14%	Exam 2
10%	Exam 3
12%	Homeworks (six at 2% each)
10%	Class Participation (including attendance and quizzes)

Team Project Work Breakdown:

20%	Supervisor’s Evaluation
15%	Clients’ Evaluation
15%	Peer Evaluations
10%	Weekly Summary Reports
30%	Other Project Artifacts
10%	Project Presentations

Course Grade Division:

90-100	A
85- 89	B+
80- 84	B
75- 79	C+
70- 74	C
65- 69	D+
60- 64	D
0- 59	F

Ethics and Professional Practice: You are expected to act honestly and professionally in this course at all times, in a manner consistent with the school’s honor code.

Class Participation Policy: There are 40 meeting times during the term. You can potentially receive 10 points towards the class participation portion of your grade for each of those classes in the following fashion:

· If there is a quiz during class, you can earn up to 10 points on it.

· If there is no quiz during class and you attend and make an effort to participate (since with a small class there will be lots of discussion), you will earn 10 points.

· If the class for some reason does not meet, you automatically receive 10 points.

There are 400 possible points, but the Class Participation part of the grade will be computed on a scale of 360 points. (If you get more than 360 points, you still only can get 5% toward the final grade!) In other words, if you miss four classes (10% of the meetings) for absences, is still possible to obtain full credit for class participation.

Late Submissions: Late quizzes will not be accepted. Late homeworks or project assignments may receive a deduction (or not be accepted at all), depending on the circumstances and the degree of lateness.

Exam Policy: Exams will be in-class, closed book, and closed notes except for one 8.5 by 11 sheet of paper which you can put notes on using both sides of the page.

No exams will be “dropped”. Giving a makeup exam for an unexcused absence is at the discretion of the instructor. Any requests for regrading must be made in writing by the beginning of the next class period after the exams are returned.