AMERICAN INTERNATIONAL UNIVERSITY-BANGLADESH (AIUB)

Faculty of Science and Information Technology

Department of Computer Science
Undergraduate Program

COURSE OUTLINE
Term: Summer 2015-2016
I.
Course Code and Title: CSC 2210: Object Oriented Analysis and Design
(OOAD)
II.
Credit: 3 credit hours (3 hours of theory per week)
III.
Nature: Major Course for BSc. in CS, CSE, CSSE, SE, CIS
IV.
Prerequisite:
CSC 2105 Data Structure
CSC 2107 - Introduction to Database
V.
Course Description:
Object oriented (OO) technology is the most modern way of thinking to implement
any realistic information system. This course covers one of the most widely used and
popular OOAD tools available at the moment- UML (Unified Modeling Technique)
along with OO metrics, IS Project Planning tools and above all OO Design Pattern.
UML is a language for visualizing, specifying, constructing and documenting the
artifacts of a software-intensive system. The other topics cover the Object Oriented
Software Engineering aspects.
VI.

Objectives:

The main objectives of this course are as follows:

1. to introduce System Analysis and Design using Object Oriented Technology,
2. to provide a sound understanding of the fundamental concepts of the object
model,
3. to familiarize with the notation and process of object-oriented analysis and
design,
4. through Design Patterns students will be given an introduction to the recurring
abstraction of tools to formulate and implement complex, yet flexible, extensible,
robust and correct systems,
5. enable students to realize the industrial-strength of the Object Oriented
Technology, comfortable to use visual tools to design Object Oriented System,
6. to familiarize with various Object Orientated Project management aspects and
metrics and
7. introduce students with the concepts of Design Patterns and its implementations
using some common design patterns that are widely used in the industry.
VII

Topics to be Covered

Day 1: * Please send an email to [email protected] from your email account, so that I can
create a group email list where I can send important information and directions. The subject
of the email should be Object Oriented Analysis and Design Sec A or I

Introduction
to Software
Modeling

Introduction
of UML
Use Case
Diagram

Class
Diagram

CRC Cards

Sequence
Diagram

Introducing the
outline of the
upcoming topics.
Discuss the
necessity of formal
modeling techniques
in system
development.
Introducing various
UML and its building
blocks with their
notations.
Understanding the
requirements with the
static view of a
system. Also.

1 class

Why we do software
modeling will be
lectured in
summarized form
along with necessary
explanation of phrases
and concepts

Lecture notes,
Explanation of
quotations, real
life examples,
questionanswer session

2
classes

Lecture notes,
questionanswer session

Realizing and
understanding the
relationships
between a set of
classes, interfaces
and collaborations.
Class diagrams
address the static
design view of a
system.
The goal is to provide
the simplest possible
conceptual
introduction to OO
modeling.

3
Classes

The introduction of
UML necessary
explanation of phrases
and concepts.
Students will realize
the importance of the
requirement analysis
as the first step of
system analysis with
the help of the most
visual tool Use Case
Diagram
The most common
artifact of OO designclasses will be
introduced to the
students with all
possible relationships
explained with
notations and
examples

Students will be
shown a comparison
of the class diagram
with another popular
technique of class
identification - CRC
Cards.
A sequence diagram 3
Notations of
is an interaction
Classes interaction diagrams
diagram that
would be introduced to
emphasizes the timethe students with its
ordering of
necessity to
messages.
understand the
dynamic view of a
system. Both, UML 1.4
and 2.0 specifications
will be introduced.
Mid Term Exam

Lecture notes,
real life case
study solutions,
questionanswer session

2
Classes

0.5
Class

Lecture notes,
real life case
study solutions,
questionanswer session

Lecture notes,
real life case
study solutions,
questionanswer session

Lecture notes,
real life case
study solutions,
questionanswer session

Activity
Diagram

Statechart
Diagram

Combined
DiagramComponent
and
Deployment
Diagram

COCOMO &
Function
Point
(Software
Project
Estimation)
OO
Software
metrics

Design
Patterns

To introduce
activity diagram as
a special kind of a
statechart diagram
that shows the
flow from activity
to activity within a
system
It is important in
modeling the
behavior of an
interface, class or
collaboration and
emphasize the
event-ordered
behavior of an
object
To enable the
students
understand the
physical
implementation of
the system

2 Classes

2 Classes

0.5 Class

To discuss various 1 Class

aspects of IS
project estimation
using one of the
popular
methodologies
named COCOMO
To introduce the
2 Classes
Software
measuring
technique specially
for Object Oriented
Methodology using
various OO
software metrics
To discuss design 2 Classes
patterns which
capture the
essence of a
design solution
that has been

Students will learn the

notations of activity
diagram along with
identifying and
drawing the flow of the
system from activity to
activity within a
system
Students would be
able to understand the
behavioral aspects of
the system by drawing
states of the objects
using various
examples

Lecture notes,
real life case
study solutions,
questionanswer session

Through notations and

diagrams used on
examples students will
be able to visualize
the physical
implementation of the
software prior to real
implementation.
Students can see the
residence of various
components of the
system to various
locations and the
deployment
relationships
Students will be
introduced with
theories and formulae
of COCOMO and
practice them in
exercises

Lecture notes,
real life case
study solutions,
questionanswer session

Students will study the

theories and formulae
of various OO
Software metrics and
then apply them in
exercises

Lecture notes,
board work,
questionanswer session

Lecture notes,
real life case
study solutions,
questionanswer session

Lecture notes,
board work,
questionanswer session

Students will be
Lecture note,
shown the theories
examples, code
and technique of using walkthroughs
various design
patterns

proven to be
useful in practice
of OO
Methodology
Final Term Exam

IX.

Course Requirements
1. Must appear at least two quizzes before the midterm examination and also
before the final term examination.
2. Students must have 80% attendance to pass the course.
3. Assignments:
Mid Term Assignment:
It is a group assignment. Maximum number of members of a group is 3
(Three). Students will be required to design a system using the diagrams
learnt up to midterm (i.e. Use Case, Class and Sequence Diagram). The
system must be an old project that the students have completed in a prior
course, i.e. PL-1, DBMS, ADBMS, OOP1, etc.
Last Date of Submission: By first Tuesday after midterm
Form of submission:
1. Via E-mail (Compress all the files in a single zip file and send as
attachment in an e-mail to [email protected]). Group member names and
ID must be written in the body of the e-mail. OR
2. In a CD (Group member names and ID must be written on top of the CD).
NO FLOPPY OR
3. Bring your pen drive with the files in a folder. There must be a text file in
the folder containing the names of the group members and their IDs.
Final Term Assignment
Its a group assignment. Maximum number of members of a group is 3
(Three).
Deliverables:
1. Students will be required to complete the design of the system they did as
the midterm assignment using the diagrams learnt up to final term (i.e.
Activity and Statechart).
2. Various Object oriented Software metrics must be used to make comment
on the design (especially on the Class Diagram)
3. Student must use COCOMO to estimate effort, time and person required
for the system development project
Last Date of Submission: By first Tuesday after final term
Form of submission:
1. Via E-mail (Compress all the files in a single zip file and send as
attachment in an e-mail to [email protected]). Group member names and
ID must be written in the body of the e-mail. OR
2. In a CD (Group member names and ID must be written on top of the CD).
NO FLOPPY OR
3. Bring your pen drive with the files in a folder. There must be a text file in
the folder containing the names of the group members and their IDs.

X.

Evaluation
Mid Term Exam:
Major Exam:

40% (MCQ + Diagram Drawing)

Quizzes:
MT Project:
Attendance & Performance:
Final Term Exam:
Major Exam:
Quiz:
Project:
Attendance, Performance and Presentation:

40%
10%
10%
40% (MCQ + Diagram Drawing)
40%
10%
10%

Semester grade: 40% midterm + 60% final term

XI.

Textbook/ Reference Materials

1. The Unified Modeling Language User Guide
by Grady Booch, James Rumbaugh, Ivar Jacobson
2. UML Weekend Crash Course
by Thomas A Pender
3. Head first design patterns
by Eric Freeman, Elisabeth Freeman, Kathy Sierra, Bert Bates
4. Design Patterns- Elements of Reusable Object-Oriented Software
by Eric, Gamma, Richard Helm, Ralph Johnson, John Vlissides

Reference Materials:
1. An Integrated Approach to Software Engineering
by Pankaj Jalote
2. Object Oriented Software Engineering
Ivar Jacobson, Magnus Christerson, Patrik Jonsson, Gunnar Overgaard
3. The Unified Modeling Language Reference Manual
by Grady Booch, James Rumbaugh, Ivar Jacobson
4. Object Oriented System Analysis and Design, Second Edition
by Grady Booch
Prepared By
S.A.M. Manzur H. Khan
Senior Assistant Professor, Department of Computer Science & MIS
Director, Office of Student Affairs, Administrative Building, Level 3
Phone: 9894229, 8811749 (Ext 134),
Email: [email protected]; [email protected]
Consulting hours:
Sunday & Tuesday: 11.00 AM 1.30 PM, 3.30 PM 6.30 PM
Monday, Wednesday & Thursday: 9.00 AM 1.30 PM, 3.00 PM 6.30 PM