Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Standard view
Full view
of .
Look up keyword
Like this
0 of .
Results for:
No results containing your search query
P. 1
UT Dallas Syllabus for se6359.001.09f taught by (rxb080100)

UT Dallas Syllabus for se6359.001.09f taught by (rxb080100)

Ratings: (0)|Views: 16|Likes:
UT Dallas syllabus for se6359.001.09f Object-Oriented Analysis and Design taught by Rekha Bhowmik
UT Dallas syllabus for se6359.001.09f Object-Oriented Analysis and Design taught by Rekha Bhowmik

More info:

Published by: UT Dallas Provost's Technology Group on Dec 17, 2009
Copyright:Traditional Copyright: All rights reserved


Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less





CourseCS 6357, Object-Oriented Analysis and Design
ProfessorRekha Bhowmik
TermFall 2009
MeetingsMW 4.00-5.15 pm, ECSS 2.415
Professor\u2019s Contact Information
Office Phone(972) 883-4688
Other Phone
Office LocationECSS 4.701
Email Addressrxb080100@utdallas.edu
Office HoursMW 10:00-12:00 pm, 2.30-3.30 pm
Other Information
TA information
Name: Je Hun Jeon
Email: jhjeon@student.utdallas.edu
Office: ECSS 4.705
Office Hours: M 1:00 - 3:00 pm
Name: Angie Shia
Office: ECSS 4.705
Office Hours: W 1:00 - 2:30 pm
General Course Information

Pre-requisites, Co-
requisites, & other

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

This graduate course is intended to provide an in depth understanding of object oriented approaches to software development, in particular to the analysis and design phases of the software life cycle. Topics include notation, methods, competing methodologies, issues in object oriented development, and recent advancements which complement traditional object-oriented methodologies.

Learning Outcomes

Ability to understand Issues in Analysis and Design
Ability to understand and apply Object-Oriented Analysis and Design
Ability to understand and use UML: Notation and associated
Ability to understand and use UML metamodel (structural and behavioral
diagrams, and their extensions)
Forward engineering using UML

a. an ability to understand advanced concepts in theory of computer
b. an ability to understand advanced concepts in applications of
computer science;
c. 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 Texts &
1.Applying UML and Patterns: An Introduction to Object-Oriented
Analysis and Design and the Unified Process, Craig Larman, ISBN:
013 148 9062, Prentice-Hall, 2005.

Suggested Texts,
Readings, &

2.Object Oriented Modeling and Design, James Rumbaugh, et al,
Prentice Hall
3.The Unified Modeling Language User Guide , 2/e, Addison-Wesley,,
Booch, Rumbaugh, Jacobson.
4. The Unified Modeling Language Reference Manual, J. Rumbaugh, I.
Jacob and G. Booch, Addison-Wesley.
5. Object-Oriented Methods: A Foundation, J. Martin and J. Odell,
Prentice-Hall, 1995.
Assignments & Academic Calendar
There will be three exams. The exams will be closed book.
A design project will be performed by teams and homework will be assigned.
Course Outline
Tentative Schedule
All reading assignments are fromLar man text
Lecture Topics
Intro to OOA/D, Iterative & Agile Processes
Chapters 1 & 2
Inception, Requirements
Chapters 4 & 5
Elaboration, Domain Models
Chapters 8 & 9
System Modeling, Operation Contracts, Iterative
Requirements to Design
Chapters 10 - 12
Logical Architecture, Interaction & Class Diagrams
Chapters 13, 15, 16
Object Design, Responsibilities, Visibility
Chapters 17 - 19
Design to Code, Test-driven Development &
Chapters 20, 21
Activity Diagrams, State Machines, Domain
Model Refinement
Chapters 28, 29, 31
Architecture Analysis, Logical Architecture
Refinement, Package Design
Chapters 33 - 35
GoF Patterns, Persistence Framework
Chapters 36, 37
Project: There will be a 3-phase project. The project will be done by teams of 4-5 students.
(Teams with less than 4 members will be allowed). You are to select your own team members.
Important Dates:
1. September 28
\u2013 Project Phase I
2. September 30
\u2013 Exam 1
3. October 26
\u2013 Project Phase II
4. October 28
\u2013 Exam 2
5. November 23
\u2013 Project Phase III
6. December 7
\u2013 Exam 3
7. December 7
\u2013 Final Project submission
Course Policies
Grading (credit)
Grading Policy
Project (3 x 10), CW/HW
45 %
Exam 1
15 %
Exam 2
20 %
Exam 3

Grades are assigned according to the following scale:

Below 70=F
Make-up ExamsMake-up exams are only given to those students who coordinate the missing of an
exam prior to the originally scheduled exam date and time.
Extra CreditNo extra credit
Late WorkProjects are due in class on the dates given. Late projects will have 10 points
deducted. No late projects accepted after one week.
AssignmentsThere will be one required class project

Class AttendanceClass attendance will be documented

Field Trip

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

You're Reading a Free Preview

/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->