Object Oriented Analysis 300144 : Overview and Introduction
Prepared By © Bhuvan Unhelkar, 1998-2006
Page 1 of 10
Object Oriented Analysis
Introduction & Teaching Plan
Unit: 300144;
300146; Level: 200; Credit Points 10
By
BHUVAN UNHELKAR, PHD, FACS
bhuvan@cit.uws.edu.au
+61-(0)413-821-454; +61-(0)2-9685-9232
www.cit.uws.edu.au/~bhuvan
School of Computing and Mathematics,
Room ECG63, Parramatta Campus; University of Western
Sydney; Locked Bag 1797, Penrith South DC NSW 1797.
AUSTRALIA
Object Oriented Analysis 300144 : Overview and Introduction
Prepared By © Bhuvan Unhelkar, 1998-2006
Page 2 of 10
Introduction
Welcome to Object Oriented Analysis. The material required for this unit is now
available in book form, as specified in the reference of the unit outline. This document
provides introductory information on this interesting subject. This document also contains
the teaching (lecture) plan for this subject. Please ensure you have read the Unit Outline
for this subject to understand the requirements of this unit.
Administrative
Ensure you have thoroughly read the unit outline, especially the requirements of the unit,
assignments and related deliverables etc. Please also have a look at the Lecture plan
provided in this document in order to understand what is being taught during the lectures.
(when this unit is run over multiple campuses, the lecture plan will obviously vary).
Attendance in lectures is considered vital in order to grasp the concepts discussed in this
document. Furthermore, valuable and important advice as well as information on
deliverables, tests etc. will be provided during the lectures. If you miss lectures you are
likely to miss out on grasping the concepts as well as following important advice – this is
done at your discretion and risk.
At the end of each lecture, there is a small workshop. This workshop is made up of small
questions and / or exercises. You are expected to participate in all of these Classroom
workshops. Exercises provided at the end of each module have to be worked in the class.
This is followed by project work to be done in groups during the labs (also called
tutorials).
Relevant parts of the course material is available on the following website. However,
most of the material is covered in the corresponding text book Practical Object Oriented
Object Oriented Analysis 300144 : Overview and Introduction
Prepared By © Bhuvan Unhelkar, 1998-2006
Page 3 of 10
Analysis which is based on the course material prepared by the author over past couple of
years:
www.cit.uws.edu.au/~bhuvan
Object Oriented Analysis 300144 : Overview and Introduction
Prepared By © Bhuvan Unhelkar, 1998-2006
Page 4 of 10
Lecture Plan (Parramatta –varies for Penrith and
Campbelltown)
Following is a rough mapping of the lecture topics with the corresponding chapters presented in
the aforementioned book. The total presentation is divided into 10 modules, each reflecting a
topic of discussion during a two-hour lecture. Assuming an introduction and a conclusion lecture,
these notes cover a teaching period of 13 weeks.
Date
Ch
Chapter Topic
Comments
apt
er
3 March
Introduction to the Unit where the detailed outline
2006
of the subject of Object Oriented Analysis is
discussed. Students are also briefed with the
assessment tasks and the case study problem
statement.
(The
“EPHARMA”
Case
study
Problem Statement is read out)
Project Work: Students to form groups of FOUR
to work on the project. All actual group work will
be carried out in the Tutorial sessions in the Labs.
3 March,
2006
1
Fundamentals of Object-
Detailed discussion of the five Fundamentals of
Orientation
Object-orientation:
Classification, Abstraction,
Inheritance, Encapsulation and Polymorphism.
Relevance
of
the
three
modelling
spaces
(Problem, Solution and Background) to Object
Oriented Analysis is discussed.
Project Work: Group formation must be complete;
Tutor contact established; Labs available with the
UML CASE tool. (While usually this will take first
two weeks of the semester, due to loss of one
Object Oriented Analysis 300144 : Overview and Introduction
Prepared By © Bhuvan Unhelkar, 1998-2006
Date
Ch
Page 5 of 10
Chapter Topic
Comments
apt
er
Friday lecture – Good Friday – some discussion
on Chapter 1 will take place in First week).
10
2
The
Unified
Modelling
Discussion on what comprises the Unified
Object
Modelling Language, the purpose it serves, and a
March,
Language
in
2006
Oriented Analysis
Walkthrough of all 13 UML 2.0 diagrams.
Project
Work:
Students
should
informally
experiment creating these diagrams in their CASE
tool - individually and in groups.
17
3
March,
Process, Prioritization and
Understanding an Iterative and Incremental
Package Diagrams
process and its relevance to the UML; Discussion
of a process architecture comprising Roles,
2006
Deliverables
and
Activity-Tasks.
Specific
discussion of Business analysis and Requirements
Modelling process-components.
Critical Requirement Analysis for Prioritization.
Package Diagrams.
Project Work: Creation of an Iterative and
Incremental Project Plan. Identification and
prioritization of Packages.
Use Case Models: Actors,
Modelling the requirements with Actors, Use
March,
Use
cases and their corresponding Documentation
2006
Documentation
24
4
cases
and
using a Template.
Project Work: Identify Actors and Use cases
based on the Problem Statement. Document them
separately for each Package.
Use Case Diagrams and
Placing Actors and Use cases on use case
March,
Activity Diagrams; UML’s
diagrams. Creation of activity diagrams. Studying
2006
Extensibility Mechanisms.
stereotypes and notes.
31
5
Project Work: Create use case diagrams; Create
Object Oriented Analysis 300144 : Overview and Introduction
Prepared By © Bhuvan Unhelkar, 1998-2006
Date
Ch
Page 6 of 10
Chapter Topic
Comments
apt
er
corresponding
Activity
diagrams.
Apply
stereotypes and notes to diagrams.
Mid-Term Test
7 April,
A Mid-Term test will be conducted DURING
CLASS TIME. This is a CLOSED book test, for
2006
90 minutes including reading time, and is meant
to test the knowledge gained by the students thus
far, as well as provide them with a feedback on
how they are progressing. Appearing in this test in
MANDATORY for passing this unit. Please
advise your lecturer BEFOREHAND if you are
unable to attend this test..
EASTER BREAK
21 April,
6
Classes
and
Class
Diagrams.
2006
Revisit classes and objects; Extract and model
Classes from use cases and activity diagrams. Add
Attributes and Operations to Classes. Create Class
diagrams using class relationships. Understand
and apply multiplicities on Class diagrams.
Project Work: Identify classes from use case
documentation and problem statement. Model
classes with attributes and operations. Create
class
diagrams
and
apply
multiplicities,
stereotypes and notes.
28 April,
2006
7
Interaction Modelling with
Modelling
Sequence
Diagrams;
diagrams. Providing an overview of sequence
Interaction
Overview
diagrams and use cases with Interaction overview
Diagrams; State Machines
the
Interactions
with
sequence
diagrams. Modelling the dynamic object states
with state machine diagrams.
Project Work: Create sequence diagrams for
sequences identified in use cases / or activity
Object Oriented Analysis 300144 : Overview and Introduction
Prepared By © Bhuvan Unhelkar, 1998-2006
Date
Ch
Chapter Topic
Page 7 of 10
Comments
apt
er
diagrams. Also, create state machines for selected
object/classes from the class diagrams.
5
May,
8
Interface
specifications;
Prototyping.
2006
Specification of Interfaces (especially Graphic
User Interfaces) in the problem space. Creation of
navigation maps for front-ends and web sites.
Mapping sequences to Interfaces. Prototypes as
models.
Project Work: Create interface specifications
corresponding to interface actors within use
cases. Create navigation maps. Create possible
prototype interfaces.
12 May,
9
Quality
Assurance
and
Acceptance Testing
2006
Quality management, quality assurance and
testing. Planning and organizing testing for use
cases. Writing good test cases.
Project Work: Write a mini Test Plan; Write test
cases corresponding to use cases with valid and
invalid input.
19 May,
2006
10
Operational Requirements
Operational issues like Performance, Scalability,
in Analysis
Security & Volume and their specifications during
analysis work.
Project Work: Specify operational requirements;
specify development environment for your project.
26 May,
No New Chapter Material;
Detailed Discussion on Project Work; Sorting of
2006
Discussion on Project
outstanding issues in Project. Revision of project,
binding and submission discussion (together with
soft copies of OO Analysis Report, UML models
and Project Plans).
2
June,
2006
Consolidation
Preparation
for
exam. Appendix C
and
final
Submission of Project Work in corresponding
Tutorials; Discussion on Final Exam.
Object Oriented Analysis 300144 : Overview and Introduction
Prepared By © Bhuvan Unhelkar, 1998-2006
Date
Ch
Chapter Topic
Page 8 of 10
Comments
apt
er
Suggested timings and markings.
Object Oriented Analysis 300144 : Overview and Introduction
Prepared By © Bhuvan Unhelkar, 1998-2006
Page 9 of 10
Deliverables for the Project Work (Assignment 2)
NOTE: Project Work 1 through 10, as listed at the end of each chapter of the Practical OO
Analysis book form the detailed step-by-step requirements of the project. Therefore, it is essential
that students have carefully worked through Project Work 1 through 10 throughout the semester.
In addition, here is a summarized list of what you have to produce and how:
1. A printed and bound report of the complete OO Analysis work with all Word deliverables.
AN EXAMPLE REPORT TEMPLATE HAS BEEN PROVIDED AS A STARTING POINT.
2. An iterative, incremental project plan containing relevant activities and tasks in Microsoft
Project (use the project plan from the ‘Process Quality…’ book as a starting point.
3. An .mdl file (if using ROSE) containing the analysis models; a .ttw file (if using TauG2); if
using any other tool, corresponding model file should be submitted. Please note: these files
should be included on a diskette or CD along with the report, as simply emailing the model
file will not be considered as submitted.
4. Any additional material accompanying the project.
5. Electronic copies of ALL submissions are required along with the final project report. These
Electronic copies should be in a floppy/CD format and Attached to the report.
6. Students are requested to keep a copy of their submissions for future reference.
Object Oriented Analysis 300144 : Overview and Introduction
Prepared By © Bhuvan Unhelkar, 1998-2006
Page 10 of 10
Coordinator Profile
Bhuvan Unhelkar (BE, MDBA, MSc, PhD; FACS) has 24 years of strategic as well as
hands-on professional experience in Information Technology, followed by close to three
years of full-time academic experience at University of Western Sydney, and 6 years of
part-time academic experience. He is also an Internationally Acclaimed Consultant &
Trainer and Founding Principal of MethodScience.com, specializing in the field of
Software Process and Modeling. His earned his PhD in 1997 from the University of
Technology, Sydney. His thesis was in the area of “Granularity of Object Oriented
Design and its application to Financial Risk Management” and was supervised by Prof.
Brian Henderson-Sellers.
Bhuvan is Author of Nine Books including Practical Object Oriented Analysis and Practical
Object Oriented Design (Thomson Publishing, 2005) and Process Quality Assurance for
UML-based Projects (Addison-Wesley, Boston, 2003). He has Published numerous papers,
Presented at and Chaired Seminars and Conferences. As a Senior Manager with Dow
Jones, he won the Computerworld Object Developers Award, for “Best use of Objectorientation across the organization”. He leads the Emerging Technologies sub-group
with AeIMS research group at the Univ. of Western Sydney;
Bhuvan is Fellow of the Australian Computer Society; Member Computer Society of
India; Convener, Object-oriented Special Interest Group, and Branch Executive
Committee member of the ACS NSW branch. He is also Rotarian St.Ives, Dist. 9680;
previous Mentor Director at TiE.org Sydney chapter; Friend Of Chase Alive (FOCAL).
End of Document