CS 6359 http://cstalon.utdallas.edu/6359/6359f05.

htm

CS 6359 Object Oriented Analysis and Design(3 semester hours) Analysis and practice of
modern tools and concepts that can help produce software that is tolerant of change.
Consideration of the primary tools of encapsulation and inheritance. Construction of
"software-ICs" which show the parallel with hardware construction. Prerequisites: CS 5354
and either CS 5335 or CS 5336. (3-0) S

1 of 7 8/23/2005 9:57 AM
CS 6359 http://cstalon.utdallas.edu/6359/6359f05.htm

Fall 2005

Section 001 meets MWF 12:00 PM – 12:50 PM

Room ECS 2.312

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: The Unified Modeling Language User Guide: Grady Booch, James Rumbaugh, Ivar
Jacobson, Addison Wesley: Boston

Recommended: Object-Oriented Modeling and Design , Second Edition, Michael Blaha, James
Rumbaugh, Prentice Hall: Englewood Cliffs

Course Objectives: T

1. In-depth study of object-oriented analysis and design of software systems based on the
standard design language (UML)

2. Study of a software development methodology. Presentation of the use-case driven approach

for software requirements specification, analysis, and design

3. Study and use of object and dynamic modeling techniques

4. Study and use of object-oriented system design techniques

5. Study and use of object-oriented implementation techniques

6. Introduction to CASE tools and techniques

2 of 7 8/23/2005 9:57 AM
CS 6359 http://cstalon.utdallas.edu/6359/6359f05.htm

Class Project
There will be one term project (3 PARTS), one midterm examination, and one comprehensive final
examination. Examinations will be based on assigned reading, lectures, and the term project.
There will be no makeup examinations.

The term project will be assigned to teams of up to four students. It will consist of three parts.
Part one will be a use-case analysis of the assigned project and part two will be the design and
part three the transition (implementation) of a software system in either C++ or Java based on the
use-case design performed in part two.

Computer Usage:

You can obtain a trial version of Rational Rose to run the program(s) on your
home PC from IBM web sites (Since the URL changes from time to time, do an
internet search). A student version is also available.

If you wish, you can use the facilities at UTD too (ES2.104 on the ground floor in
ECS). All PCs in the labs of UTD are installed with Rational Rose. There are
several open access labs: http://www.utdallas.edu/ir/tcs/labs/locations.htm. You
will need to get a user ID for the lab, https://netid.utdallas.edu. Need help?
972-883-2911, assist@utdallas.edu, http://www.utdallas.edu/ir/tcs

Late work: Any assigned work will have 10 points deducted for each week passed DUE.

Grading:

The final grade will be determined as follows:

Percentage
Team project (part 1) 10%
Team project (part 2) 20%
Team project (part 3) 10%
Test 1 25%
Test 2 25%
Homework 5%
Class Participation 5%

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.

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 7 8/23/2005 9:57 AM
CS 6359 http://cstalon.utdallas.edu/6359/6359f05.htm

Class Changes
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 ONE DAY PRIOR TO EACH CLASS. The schedule below is subject to change

Course Topics Sequence and Road Map of Events

CS 6359 Fall 2005

4 of 7 8/23/2005 9:57 AM
CS 6359 http://cstalon.utdallas.edu/6359/6359f05.htm

Date Subject Notes

22Aug Introduction to OOAD ; About the course; Instructor Notes

24 Aug Introduction to UML. Concepts of OO. Overview of the lecture 2

Unified Method. Best Practices of Software Engineering
Lecture 3

Appendix C
Overview of Analysis and Design

Use Case Analysis

Classes, relationships, properties

5 Sep Labor Day Holiday

common mechanisms

Use Case Analysis Models

Architecture Analysis

21 Sep Project 1 Due

23 Sep Review 1

25 Sep Test 1a

BRING A SCANTRON narrow green Form 882-E and a

number 2 pencil

Picture of Scantron 882E

5 of 7 8/23/2005 9:57 AM
CS 6359 http://cstalon.utdallas.edu/6359/6359f05.htm

27 Sep Test 1b

I will supply the paper for the practical

exercise.

Identify Design Elements

Use Case Design

Advanced Classes/Relationships

Events and Signals

Class Design State Machines (Charts)

Design Patterns

Class Design

31 Oct Project 2 Due

Date

Database Design

Implementation Models

Mapping to code

21 Nov Review Project 3 DUE

DATE

24 Nov Test 2a PEER REVIEW

BRING A SCANTRON narrow green Form 882-E and a PROJECT

number 2 pencil EVALUATION

Picture of Scantron 882E

26 Nov Test 2b

I will supply the paper for the practical

6 of 7 8/23/2005 9:57 AM
CS 6359 http://cstalon.utdallas.edu/6359/6359f05.htm

exercise.
29 Nov No Class

7 of 7 8/23/2005 9:57 AM