Course Syllabus

Course Information
Course Number/Section CS6361/501
Course Title (Advanced) Requirements Engineering

Term Fall 2006

Days & Times TR 5:30-6:45pm

Professor Contact Information

Professor Lawrence Chung
Office Phone 972-883-2178
Other Phone
Email Address [email protected]
Office Location ECSS3.204
Office Hours T12:30-2:00pm
Other Information

Course Pre-requisites, Co-requisites, and/or Other Restrictions

CS 5354 (SE 5354) Software Engineering, or CS 3353 (SE 3354)

Course Description
To be able to systematically establish, define, and manage the requirements for a large,
complex, changing, software-intensive system, be it organizational or mostly a computer
sub-system. To be able to understand the central issues which form the background to, or
have tendency to deform, the process. To be able to understand, evaluate and choose from
traditional techniques and further advances in the field.

Student Learning Objectives/Outcomes

Ability to understand Issues in Requirements Engineering a,b,c,d
Ability to understand and apply Requirements Engineering Process a,b,c,d
Ability to understand and use Requirements Elicitation and Specification:
Notations and Methodologies a,b,c,d,e
Ability to understand and use Formal Techniques
(Axiomatizations, Meta-modeling, Model Checking) a,b,c,d
Non-Functional Requirements: Modeling and Analysis a,b,c,d

CS Outcomes
a. an ability to understand advanced concepts in theory of computer science;
b. an ability to understand advanced concepts in applications of computer science;
c. an ability to apply knowledge of advanced computer science
to formulate and analyze problems in computing and solve them;
d. an ability to learn emerging concepts in theory and applications
of computer science; and,
e. an ability to design and conduct experiments as well as to analyze
and interpret data.

Required Textbooks and Materials

Required Texts
Required Materials
Lecture Notes

Suggested Course Materials

Suggested Readings/Texts
System Requirements Engineering, P. Loucopoulos and V. Karakostas, McGraw-Hill: 1.zip;
2.zip; 3.zip; 4.zip
Requirements Engineering: Processes and Techniques, G. Kotonya and I. Sommerville, John
Wiley Sons
Software Requirements: Objects, Functions, & States, A. M. Davis,
Prentice Hall: Englewood Cliffs
Non-Functional Requirements in Software Engineering, L. Chung, B. Nixon, E. Yu and J.
Mylopoulos, Kluwer Academic Publishing, 2000 (An earlier version of a framework book
chapter)
System and Software Requirements Engineering: Tutorial, R. H. Thayer and M. Dortman
(Editors), IEEE Computer Society Press
Requirements Engineering - A Good Practice Guide, I. Sommerville and P. Sawyer, Wiley
Requirements Engineerng: Frameworks for Understanding, R. Wieringa, Wiley, 1997
Requirements Engineering, L. Macaulay, Springer Verlag, 1996
User-Centered Requirements Analysis, C. F. Martin, Prentice-Hall, 1994
Information System Requirements: Determination and Analysis, D. Flynn, McGraw-Hill, 1992
Exploring Requirements, D. Gause and G. Weinberg, Dorset House, 1989
Object-Oriented Analysis and Design, with Applications, G. Booch, Benjamin-Cummings,
1994
Object-Oriented Methods: A Foundation, J. Martin and J. Odell, Prentice-Hall, 1995
The Unified Modeling Language Reference Manual, J. Rumbaugh, I. Jacobson and G. Booch, Addison-Wesley, 1998
The Unified Modeling Language User Manual, G. Booch, J. Rumbaugh and I. Jacobson, Addison-Wesley, 1998.

Suggested Materials

Assignments & Academic Calendar

Topics, Reading Assignments, Due Dates, Exam Dates

Course Outline (subject to evolution, hence it is recommended that you download 1-2 modules at a
time on a weekly basis or whenever appropriate)

Requirements Engineering Journal and a Swing [PowerPoint]

Requirements Engineering: Introduction - Part I [PostScript] [PDF]
Requirements Engineering: Introduction - Part II [PostScript] [PDF]
- Examples of requirements defects
- http://techdirt.com/articles/20060818/1613226.shtml

Requirements Engineering Processes [PowerPoint]

Requirements Elicitation: Part I [PostScript] [PDF]
Requirements Analysis, Modelling and Specification: Review [PostScript] [PDF]
My Cat is Object-Oriented – A Brief Review of UML
Enterprise Requirements & Functional Requirements: Structural Requirements [PostScript] [PDF]
Functional Requirements: A Formal OO-RML [PostScript] [PDF];
 Metamodeling
Functional Requirements: Behavioral Requirements [PostScript] [PDF]
Non-Functional Requirements: New; Old [PostScript] [PDF]

Enterprise Requirements: Part II [PostScript] [PDF]

Requirements Elicitation: Part II [PostScript] [PDF]
Scenario Analysis [PostScript] [PDF]
Model Checking

Project: There will be a 2-phase project. Each project phase should be submitted by the expected due date in
the beginning of the class that day. Project phases should be submitted with student name, student ID, student email
address, project phase #, and class/section written on the first page. The project will be done by teams of 3 students.
(Teams with more or less than 3 members will be allowed only under exceptional circumstances). All students in a
team will get the same mark for the work they do unless they unanimously agree (in writing) to an unequal division.
You are to choose your own team members. An orphan will be assigned to a team by the instructor. Project I under
development should be presented approximately 2 weeks before the final submission due date; Project II under
development should be presented approximately 2 weeks before the submission due date.

Important Dates:

1. August 17 (Thursday) - First day of class for this course

2. September 28 (Thursday) – Interim Project I (old: [PostScript] [PDF] – to be updated) presentation

3. October 3 (Tuesday) – Test 1

4. October 12 (Thursday) – Final Project I submission (and also possibly presentation)

5. November 9 (Thursday) – Interim project II (old: [PostScript] [PDF]) presentation

6. November 21 (Tuesday) – Test 2

7. November 22 (Wednesday) – November 28 (Tuesday) – Final Project II submission and demo

(Each team should set up a time with the TA to do a demo; A hardcopy should be submitted at the
time of the demo.)

Grading Policy
Project (2 x 15) 30 %
Test 1 25 %
Test 2 40 %
Class Participation 5%

Course Policies
Make-up exams

Extra Credit

Late Work

Special Assignments

Class Attendance

Classroom Citizenship

Field Trip Policies / Off-Campus Instruction and Course Activities

Student Conduct & Discipline

The University of Texas System and The University of Texas at Dallas have rules and regulations for the orderly and
efficient conduct of their business. It is the responsibility of each student and each student organization to be
knowledgeable about the rules and regulations which govern student conduct and activities. General information on
student conduct and discipline is contained in the UTD publication, A to Z Guide, which is provided to all registered
students each academic year.

The University of Texas at Dallas administers student discipline within the procedures of recognized and established due
process. Procedures are defined and described in the Rules and Regulations, Board of Regents, The University of Texas
System, Part 1, Chapter VI, Section 3, and in Title V, Rules on Student Services and Activities of the university’s
Handbook of Operating Procedures. Copies of these rules and regulations are available to students in the Office of the
Dean of Students, where staff members are available to assist students in interpreting the rules and regulations (SU 1.602,
972/883-6391).

A student at the university neither loses the rights nor escapes the responsibilities of citizenship. He or she is expected to
obey federal, state, and local laws as well as the Regents’ Rules, university regulations, and administrative rules. Students
are subject to discipline for violating the standards of conduct whether such conduct takes place on or off campus, or
whether civil or criminal penalties are also imposed for such conduct.

Academic Integrity

The faculty expects from its students a high level of responsibility and academic honesty. Because the value of an
academic degree depends upon the absolute integrity of the work done by the student for that degree, it is imperative that
a student demonstrate a high standard of individual honor in his or her scholastic work.

Scholastic dishonesty includes, but is not limited to, statements, acts or omissions related to applications for enrollment or
the award of a degree, and/or the submission as one’s own work or material that is not one’s own. As a general rule,
scholastic dishonesty involves one of the following acts: cheating, plagiarism, collusion and/or falsifying academic
records. Students suspected of academic dishonesty are subject to disciplinary proceedings.

Plagiarism, especially from the web, from portions of papers for other classes, and from any other source is unacceptable
and will be dealt with under the university’s policy on plagiarism (see general catalog for details). This course will use
the resources of turnitin.com, which searches the web for possible plagiarism and is over 90% effective.

Email Use
The University of Texas at Dallas recognizes the value and efficiency of communication between faculty/staff and
students through electronic mail. At the same time, email raises some issues concerning security and the identity of each
individual in an email exchange. The university encourages all official student email correspondence be sent only to a
student’s U.T. Dallas email address and that faculty and staff consider email from students official only if it originates
from a UTD student account. This allows the university to maintain a high degree of confidence in the identity of all
individual corresponding and the security of the transmitted information. UTD furnishes each student with a free email
account that is to be used in all communication with university personnel. The Department of Information Resources at
U.T. Dallas provides a method for students to have their U.T. Dallas mail forwarded to other accounts.

Withdrawal from Class

The administration of this institution has set deadlines for withdrawal of any college-level courses. These dates and times
are published in that semester's course catalog. Administration procedures must be followed. It is the student's
responsibility to handle withdrawal requirements from any class. In other words, I cannot drop or withdraw any student.
You must do the proper paperwork to ensure that you will not receive a final grade of "F" in a course if you choose not to
attend the class once you are enrolled.

Student Grievance Procedures

Procedures for student grievances are found in Title V, Rules on Student Services and Activities, of the university’s
 Handbook of Operating Procedures.

In attempting to resolve any student grievance regarding grades, evaluations, or other fulfillments of academic
responsibility, it is the obligation of the student first to make a serious effort to resolve the matter with the instructor,
supervisor, administrator, or committee with whom the grievance originates (hereafter called “the respondent”).
Individual faculty members retain primary responsibility for assigning grades and evaluations. If the matter cannot be
resolved at that level, the grievance must be submitted in writing to the respondent with a copy of the respondent’s School
Dean. If the matter is not resolved by the written response provided by the respondent, the student may submit a written
appeal to the School Dean. If the grievance is not resolved by the School Dean’s decision, the student may make a
written appeal to the Dean of Graduate or Undergraduate Education, and the deal will appoint and convene an Academic
Appeals Panel. The decision of the Academic Appeals Panel is final. The results of the academic appeals process will be
distributed to all involved parties.

Copies of these rules and regulations are available to students in the Office of the Dean of Students, where staff members
are available to assist students in interpreting the rules and regulations.

Incomplete Grade Policy

As per university policy, incomplete grades will be granted only for work unavoidably missed at the semester’s end and
only if 70% of the course work has been completed. An incomplete grade must be resolved within eight (8) weeks from
the first day of the subsequent long semester. If the required work to complete the course and to remove the incomplete
grade is not submitted by the specified deadline, the incomplete grade is changed automatically to a grade of F.

Disability Services

The goal of Disability Services is to provide students with disabilities educational opportunities equal to those of their
non-disabled peers. Disability Services is located in room 1.610 in the Student Union. Office hours are Monday and
Thursday, 8:30 a.m. to 6:30 p.m.; Tuesday and Wednesday, 8:30 a.m. to 7:30 p.m.; and Friday, 8:30 a.m. to 5:30 p.m.

The contact information for the Office of Disability Services is:

The University of Texas at Dallas, SU 22
PO Box 830688
Richardson, Texas 75083-0688
(972) 883-2098 (voice or TTY)

Essentially, the law requires that colleges and universities make those reasonable adjustments necessary to eliminate
discrimination on the basis of disability. For example, it may be necessary to remove classroom prohibitions against tape
recorders or animals (in the case of dog guides) for students who are blind. Occasionally an assignment requirement may
be substituted (for example, a research paper versus an oral presentation for a student who is hearing impaired). Classes
enrolled students with mobility impairments may have to be rescheduled in accessible facilities. The college or university
may need to provide special services such as registration, note-taking, or mobility assistance.

It is the student’s responsibility to notify his or her professors of the need for such an accommodation. Disability Services
provides students with letters to present to faculty members to verify that the student has a disability and needs
accommodations. Individuals requiring special accommodation should contact the professor after class or during office
hours.

Religious Holy Days

The University of Texas at Dallas will excuse a student from class or other required activities for the travel to and
observance of a religious holy day for a religion whose places of worship are exempt from property tax under Section
11.20, Tax Code, Texas Code Annotated.

The student is encouraged to notify the instructor or activity sponsor as soon as possible regarding the absence, preferably
in advance of the assignment. The student, so excused, will be allowed to take the exam or complete the assignment
within a reasonable time after the absence: a period equal to the length of the absence, up to a maximum of one week. A
student who notifies the instructor and completes any missed exam or assignment may not be penalized for the absence. A
student who fails to complete the exam or assignment within the prescribed period may receive a failing grade for that
exam or assignment.

If a student or an instructor disagrees about the nature of the absence [i.e., for the purpose of observing a religious holy
day] or if there is similar disagreement about whether the student has been given a reasonable time to complete any
 missed assignments or examinations, either the student or the instructor may request a ruling from the chief executive
officer of the institution, or his or her designee. The chief executive officer or designee must take into account the
legislative intent of TEC 51.911(b), and the student and instructor will abide by the decision of the chief executive officer
or designee.

Off-Campus Instruction and Course Activities

Off-campus, out-of-state, and foreign instruction and activities are subject to state law and University policies and
procedures regarding travel and risk-related activities. Information regarding these rules and regulations may be found at
the website address given below. Additional information is available from the office of the school dean.
(http://www.utdallas.edu/Business Affairs/Travel_Risk_Activities.htm)

These descriptions and timelines are subject to change at the discretion of the Professor.