CS 4351-501 http://cstalon.utdallas.edu/4351/4351f05.

htm

SE 4351 Requirements Engineering (3 semester hours) Introduction to system and

software requirements engineering. The requirements engineering process, including
requirements elicitation, specification, and validation. Essential words and types of
requirements. Structural, informational, and behavioral requirements. Non-functional
requirements. Scenario analysis. Conventional, object-oriented and goal-oriented
methodologies. Prerequisite: SE 2370, CS/Se 3354 or consent of instructor.

1 of 8 8/23/2005 9:55 AM
CS 4351-501 http://cstalon.utdallas.edu/4351/4351f05.htm

Fall 2005

Section 501 meets TR 7:00 PM – 8:15 PM

Room ECS 2.203

Instructor: Anthony D. Sullivan, Ph.D. UTD Office: ECSS 4.701

Office Hours: Wednesday 12:50-13:50 Thursday 20:15 -21:15

UTD Telephone: (972) 883-6620 E-mail: sulliva@utdallas.edu

Teaching Assistant: TBP

E-mail: Hours -

Office

Textbook:

Required: Managing Software Requirements: A Use Case Approach, 2nd Edition., Dean
Leffingwell,
Don Widrig, Addison Wesley: Boston

Recommended Reference: The Unified Modeling Language User Guide: Grady Booch, James
Rumbaugh, Ivar Jacobson, Addison Wesley: Boston

Course Objectives: This course is intended to provide an understanding of software requirements

engineering. Topics will include the software engineering techniques for the elicitation, specification
and validation of system specifications of large-scale software systems. Included in the scope is the
application of project management, feasibility analysis, cost estimation models, CASE tools,
information system proposals and presentations, prototype design, business process modeling and
software metrics.

Ability to understand the whys, whats and hows of a software system

Ability to differentiate process requirements from product requirements
Ability to specify and follow a requirements engineering process such as
Structured Analysis or Object Oriented
Ability to identify stakeholders (and other sources of requirements), elicit
their needs and objectives, identifying and resolving conflicts.
Ability to specify requirements
Ability to validate requirements

2 of 8 8/23/2005 9:55 AM
CS 4351-501 http://cstalon.utdallas.edu/4351/4351f05.htm

Ability to establish requirements traceability

Ability to model structural, behavioral and non-functional requirements
Ability to utilize case studies (of domain-specific) requirements engineering
Ability to build a prototype
Ability to use a CASE or modeling tools to capture the requirements
Ability to outline test plans
Ability to manage changing requirements
Ability to understand the derivation of architectural and design models from
requirements specification
Ability to produce a clear, comprehensive and complete Software
Requirements Specification

Grading Weights: Test One 25%; Test Two 25%; Project - Part 1 - 15%, Part 2 - 20%, Class
participation 5%, and Assignments 10%. Highest student score for each test will become the
divisor to determine individual event percentage score curve. Any missing or late event scores
will be given a zero grade in the calculation of a course grade. Incomplete grades will not be
issued.

Class Participation
The class participation grade is based on your class attendance, your effort as part of the
project team (peer review) and your interaction during the semester.

Letter grades will be assigned as follows:

Percentage Grade
98-100 A+
92-97 A
90-91 A-
88-89 B+
82-87 B
80-81 B-
78-79 C+
72-77 C
70-71 C-
68-69 D+
62-67 D
60-61 D-
Below 60 F

Academic Honesty:

The University of Texas System Policy on Academic honesty appears in the Regents Rules and
Regulations, Part One, Chapter VI, Section 3, Paragraph 3.22. Any student who commits an
act of scholastic dishonesty is subject to discipline. Scholastic dishonesty includes but is not
limited to cheating, plagiarism, collusion, the submission for credit of any work or
materials that are attributable in whole or in part to another person, taking an examination
for another, any act designed to give unfair advantage to a student or the attempt to
commit such acts.

3 of 8 8/23/2005 9:55 AM
CS 4351-501 http://cstalon.utdallas.edu/4351/4351f05.htm

Class Project

Student Responsibilities

While teamwork and collaboration is encouraged, identical assignment or test deliverables are not
acceptable. Regular class attendance and participation is expected. The sick leave policy for this class
allows one day per month for excused student absence due to illness, work or family related reasons. Student
will sign class attendance log in each class session. Should a student exceed four (4) class absences during
the approximately 44 class sessions, the course final score will be lowered by 13% (2/16) in the calculation of
the course grade. All UTD student conduct policies and standards will be in effect.

STUDENTS MUST CHECK THE CLASS WEBSITE AND NEWS AT www.utdallas.edu/~sulliva AT

LEAST ONCE A WEEK ---ALL CHANGES AND ASSIGNMENTS WILL BE PUBLISHED-- THERE
AND NO WHERE ELSE...YOU ARE RESPONSIBLE FOR ANY ASSIGNMENT CHANGES
PUBLISHED PRIOR TO THAT WEEKS CLASS. The schedule below is subject to change

At the end of the course you will be required to turn in project evaluations and peer reviews. Failure
to turn in an evaluation will reduce your final grade 5 points.

Course Topics Sequence and Road Map of Events

CS/SE 3354 Fall 2004

4 of 8 8/23/2005 9:55 AM
CS 4351-501 http://cstalon.utdallas.edu/4351/4351f05.htm

Date Subject
Introductions - Course Syllabus Lesson 1

Semester objectives

Team formation
RE Process (Overview) Lesson 2

Discussion of Requirements Deliverables

Project Management

RE Process

Business Models

Vision Document
Business Models
Requirements Elicitation

Requirements Elicitation Brainstorming Session 1

Brainstorming Part 2

Requirements Elicitation

Prioritization
Requirements Elicitation
Model Techniques

5 of 8 8/23/2005 9:55 AM
CS 4351-501 http://cstalon.utdallas.edu/4351/4351f05.htm

UML models

UserFocus

29 Sept Review

4 Oct Exam 1

BRING A SCANTRON narrow green Form 882-E

and a number 2 pencil
I will supply the paper for the
practical exercise.

Picture of Scantron 882E

What are Requirements?

Requirements Analysis FROM WANTS AND NEEDS

TO SOFTWARE REQUIREMENTS

Scope

samples -

UML -use case

UML Glossary

6 of 8 8/23/2005 9:55 AM
CS 4351-501 http://cstalon.utdallas.edu/4351/4351f05.htm

UML Supplemental Specification

IEEE formats
Verification/Validation
Scenarios

Project Team Work - get ready for scenario

walkthrough
scenario walkthrough

NFRS

Change Management

Traceability Sample

Quality

Presentations begin

TEAM Assignments

Team 1-3
Presentations:

Teams 4-5
17 Nov Review part 2
22 Nov Exam 2

BRING A SCANTRON narrow green Form 882-E

and a number 2 pencil
I will supply the paper for the
practical exercise.

Picture of Scantron 882E

7 of 8 8/23/2005 9:55 AM
CS 4351-501 http://cstalon.utdallas.edu/4351/4351f05.htm

8 of 8 8/23/2005 9:55 AM