Home Next

SE 4351-501

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

requirements engineering. The requirements engineering process, including requirem
Deliverable Samples elicitation, specification, and validation. Essential words and types of requirements. S
informational, and behavioral requirements. Non-functional requirements. Scenario
Conventional, object-oriented and goal-oriented methodologies. Prerequisite: SE 237
3354 or consent of instructor.

Syllabus

SE 4351.501(call # 13433) Requirements E

Spring 2005

Instructor
Anthony D. Sullivan

Office: ECSS 4.701 Phone:972 883 6620, email: sulliva@utdallas.edu

Office Hours: Monday and Wednesday 19:30 to 2030

Teaching Assistants
Name Office Hours

Lectures: MW 8:30-9:45 pm ECS 2.306

Textbooks:

Required: Managing Software Requirements: A Use Case Approach, 2nd Edition.,

Don Widrig, Addison Wesley: Boston

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

Grading Scheme

Project - Part 1 15; Part 2 17;

Status Reports and Project Plan 10
Class Participation 5
Homework-3
Test 1 - 25
Test 2 - 25

Class learning objectives

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
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

Class Participation

The class participation grade is based on your class attendance, your effort as part o
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
and Regulations, Part One, Chapter VI, Section 3, Paragraph 3.22. Any student who
an act of scholastic dishonesty is subject to discipline. Scholastic dishonesty include
not limited to cheating, plagiarism, collusion, the submission for credit of any work or
that are attributable in whole or in part to another person, taking an examination for a
any act designed to give unfair advantage to a student or the attempt to commit such

Project HOMEWORK I will post the due d

for homework
The project will be done by teams of 3-5 students. All students on a team will re
same mark for the work,

unless they unanimously (in writing) agree otherwise. I will assign team membe
will be no late projects.

Teams will submit a peer evaluation toward the end of the semester which coul
your grade.

Homework assignment is an individual project and NO collaboration is allowed

NOTE THAT THIS SYLLABUS AND ACCOMPANYING HANDOUTS ARE SUBJEC

CHANGE

Schedule
Date Subject Notes
10 Jan Introductions - Course Syllabus Introductio
Requirem
Semester objectives Engineerin

Team formation
12 Jan RE Process (Overview) Read proj
document
Discussion of Requirements prepared t
Deliverables discuss
17 Jan Holiday

19 Jan Project Management Project

 Managem

24 Jan RE Process Ch 3/4

Business Models Ch 5

Vision Document CH 16
26 Jan Business Models Team Rosters
31 Jan Requirements Elicitation Ch 6-8

Microsoft
Plan Sam
2 Feb Requirements Elicitation CH 9-11
Brainstorming Session 1

Results
7 Feb Brainstorming Part 2 CH 12

Requirements Elicitation

Prioritization
9 Feb Requirements Elicitation In Class P
Work Grou

14 Feb Model Techniques Project P

(draft) an
Status R
due

16 Feb UML models

21 Feb UserFocus

23 Feb

28 Feb Review Status R

Requirem
 due
2 Mar 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

7-11 Mar Spring Break

14 Mar What are Requirements?

The Softw
requireme
Specificat

Requirements Analysis FROM

WANTS AND NEEDS TO
SOFTWARE REQUIREMENTS

16 Mar

Scope CH 21
also NFRS
samples -

UML -use case

UML Glossary

UML Supplemental Specification

21 Mar Verification/Validation CH 24

Sample fin
23 Mar Scenarios CH 27

Project Team Work - get ready

for scenario walkthrough
28 Mar scenario walkthrough Status R
due
30 Mar CH 29

4 Apr Change Management HOMEWO

 CH 31
6 Apr

11 Apr

13 Apr Presentations begin Final Re

Due with
Presenta
TEAM Assignments

Team 1-3
18 Apr Presentations: CH 34

Teams 4-5 Requirem

Due
20 Apr Review part 2
25 Apr 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