Back Home Next

CS 6359-501

Up CS 6359 Object Oriented Analysis and Design(3 semester hours) Analysis and pra
tools and concepts that can help produce software that is tolerant of change. Conside
6359 Class Project tools of encapsulation and inheritance. Construction of "software-ICs" which show the
hardware construction. Prerequisites: CS 5354 and either CS 5335 or CS 5336. (3

Syllabus

CS 6359.501 Object Oriented Analysis and

Spring 2005
Instructor Anthony D. Sullivan
Office: ECSS 4.701 Phone:972 883 6620, email: sulliva@utdallas.edu
Office Hours:

Teaching
Assistant
Tong Gao [tong.gao@utdallas.edu]
Office ECSS 3.214. 7:00PM to 9:00PM Thursday and 2:00-4:00PM Friday.
Hours
Lectures: TR 2030-2145 ECSS 2.214
Textbooks: Required: The Unified Modeling Language User Guide: Grady Booch, J
Ivar Jacobson, Addison Wesley: Boston

Recommended: The Unified Software Development Process , Grady Boo

Rumbaugh, Ivar Jacobson, Addison Wesley: Boston

Course Objectives:

1. In-depth study of object-oriented analysis and design of software systems base

design language (UML)

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

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. Introduction to CASE tools and techniques

Course Requirements:

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

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

Computer Usage: The labs at UTD have PC’s with Rational Rose installed on them

You can obtain a demo version of Rational Rose from the Rational web site to run th
your home PC (good only for 30 days). The Rational web site is
http://www.developer.ibm.com/university/students/downloads/

Late work: Any assigned work will have 10 points deducted for each week passe

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%

The project will be done by teams of 4-6 students. All students on a team will re
mark for the work, unless they unanimously (in writing) agree otherwise. You m
own team members. There will be no late projects. Teams will submit a peer ev
end of the semester which could affect your grade.

NOTE THAT THIS SYLLABUS AND ACCOMPANYING HANDOUTS ARE SUBJEC

CHANGE

Outline
Date Subject
11 Jan Introduction to OOAD ; About the
course;

13 Jan Introduction to UML. Concepts of OO.

Overview of the Unified Method.

 Best Practices of Software
Engineering

18 Jan Overview of Requirements

Use Case Diagrams

and Collaboration
20 Jan Overview of Analysis and Design

Use Case Analysis

Classes
25 Jan

27 Jan

Common mechanisms

Team Rosters

1 Feb System Architecture Analysis

3 Feb Analysis

8 Feb Analysis

10 Feb
15 Feb Analysis in Context
17 Feb Identify Design Elements
22 Feb
24 Feb Use Case Design

1 Mar Review 1
3 Mar Test 1a

BRING A SCANTRON narrow green

Form 882-E and a number 2 pencil

Picture of Scantron 882E

Test 1b

I will supply the paper for the

practical exercise.

8 Mar - Spring Break

10 Mar

15 Mar Advanced Classes/Relationships

17 Mar Events and Signals

22 Mar

24 Mar Class Design State Machines

(Charts)

29 Mar Class Design

31 Mar Database Design

5 Apr

7 Apr
11 Apr Presentations
14 Apr Presentations
19 Apr Review
21 Apr Test 2a

BRING A SCANTRON narrow green

Form 882-E and a number 2 pencil

Picture of Scantron 882E

Test 2b

I will supply the paper for the

practical exercise.