300144 – OBJECT ORIENTED ANALYSIS

School of Computing and Mathematics, College of Health and

Science

Learning Guide
Spring Semester 2010
Table of Contents
1. Staff details 1
2. Schedule of Learning and Teaching Activities 1
3. Special Requirements 5
4. Links to key policies 5
5. Expectations of student conduct 5
6. Assessment information 7
7. Learning resources information 12
8. Student feedback and improvements to the unit. 14
3 0 0 1 4 4 - O B J E C T O R I E N T E D A N A L Y S I S

1. Staff details
Unit Coordinator: Dr Quang Vinh Nguyen
Building Y, Room 3.53, Penrith Campus

Phone: 4736 0482 Email: [email protected]

First point of contact: The tutor of your registered tutorial class

Teaching Staff: Dr Jamie Yang (Campbelltown Campus)

Building ER, Room G.12, Parramatta Campus

Phone: 9685 9233 Email: [email protected]

Dr Quang Vinh Nguyen (Parramatta Campus)

Building ER, Room 1.07, Parramatta Campus

Phone: 4736 0482 Email: [email protected]

Dr Quang Vinh Nguyen (Penrith Campus)

Building Y, Room 3.53, Penrith Campus

Phone: 4736 0482 Email: [email protected]

Student Consultation Times:

The consultation times for the unit coordinator and lecturers are available on the
unit’s vUWS site. Any other consultation times must be requested. All e-mails
from enrolled students related to this unit will be answered at regular interval
during the week.

2. Schedule of Learning and Teaching Activities

Week Topic Weekly Activities
Commencing

Week 1 Fundamentals of OO Fundamentals:

Object-Orientation - 3-Conceptes (Class, Object, Message)
(OO) – Starting the - 5-Principles Classification,
OO Journey Abstraction, Inheritance,
Encapsulation and Polymorphism)
- 3-Modelling spaces

No Tutorial/Practical Lab this week.

Week 2 The Unified UML in a nutshell:

Modelling Language - What comprises the UML

1
 in Object Oriented - The purpose it serves, and
Analysis - A walkthrough of 13 UML 2.0
diagrams.

Project Work 1: 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.

Week 3 Process, Understanding software processing

Prioritization and - Its relevance to the UML
Package Diagrams - Iterative, Incremental, and Parallel
process
- The process architecture and
elements: Roles, Activities,
Deliverables
- Specific discussion: Business analysis
and Requirements Modelling process-
component.
o Critical Requirement Analysis for
Prioritization.
o Package Diagrams.

Project Work 2: Students should

informally experiment creating these
diagrams in their CASE tool -
individually and in groups.

Week 4 Use Case Models: Modelling the requirements in the form

Actors, Use cases of Use cases
and Documentation - System scope: What and Who
- Use Cases
- Actors
- High level UC documentation using a
Template

Project Work 3: Undertake Critical

Requirement Analysis, Identification and
prioritization of Package, Creation of an
IIP Project Plan

Week 5 Use Case Diagrams - Use case diagrams – visual modelling

and Activity o Placing Actors and Use cases on
Diagrams; UML’s use case diagrams.
Extensibility - Creation of activity diagrams.
Mechanisms. - UML extensibility
o Studying stereotypes and notes.

2
 Project Work 4: Identify Actors and Use
cases based on the Problem Statement.
Document them separately for each
Package.

Week 6 Classes and Class - Revisit classes and objects

Diagrams. - Modelling tasks:
o Extract classes from use cases and
activity diagrams
o Model classes - define Attributes
and Operations of Classes
o Relate classes
o Create Class diagrams

Project Work 5: Create use case diagrams;

Create corresponding activity diagrams.
Apply stereotypes and notes to diagrams.

Week 7 Sequence Diagrams; Modelling Interaction (in use

Interaction cases/activity diagrams)
Overview Diagrams; - Sequence diagrams.
State Machines - Interaction overview diagrams.
- Modelling dynamic object states
- State machine diagrams.

Project Work 6: Identify classes from use

case documentation and problem
statement. Model classes with attributes
and operations. Create class diagrams and
apply multiplicities, stereotypes and notes.

Week 8 Mid-Term Test - The CLOSED book test conducted

DURING CLASS TIME.

- For 90 minutes including reading time

- Test the knowledge gained by the

students thus far (up to Lecture 6), as well
as provide them with a feedback on how
they are progressing.

MANDATORY for passing this unit.

Please advise your lecturer
BEFOREHAND if you are unable to
attend this test.

Week 9 Intra-Session Break

3
Week 10 Interface Specification of Interfaces in the problem
specifications; space:
Prototyping. - Graphic User Interfaces
- Creation of navigation maps for
front-ends and web sites.
- Mapping sequences to Interfaces.
- Prototypes as models.

Project Work 7: Create sequence

diagrams for sequences identified in use
cases / or activity diagrams. Also, create
state machines for selected object/classes
from the class diagrams.

Week 11 Quality Assurance Quality management:

and Acceptance - Quality assurance and quality control
Testing - Planning and organizing testing for
units (e.g. use cases)
- Writing good test cases.

Project Work 8: Create interface

specifications corresponding to interface
actors within use cases. Create navigation
maps. Create possible prototype
interfaces.

Week 12 Operational Operational issues:

Requirements in - Performance, Scalability, Security &
Analysis Volume
- Their specifications during analysis
work.

Project Work 9: Write a mini Test Plan;

Write test cases corresponding to use
cases with valid and invalid input.

Week 13 Emergent Discuss on web technologies:

Technologies - Web services and emerging
technologies
- Web services and modelling
- Web services dynamics
- Web services in practices
Final discussion on Discussion on Project:
Project - Revision of project, binding and
submission (together with soft copies
of OO Analysis Report, UML models
and Project Plans)

4
 - Sorting of outstanding issues in
Project

Project Work 10: Specify operational

requirements; specify development
environment for your project.

Week 14 Consolidation and Unit revision, Discussion on Final Exam.

Preparation for final Suggested timings and markings.
exam. Appendix C
Submission of Project Work in
corresponding Lectures or Tutorials.

For full details about the timetable for this unit, go to {insert link to
timetable}.

3. Special Requirements
Equipment: Not Applicable.

Uniform: Not Applicable.

4. Links to key policies and Student information

A special web page has been set up at:

http://www.uws.edu.au/learning_teaching/learning_and_teaching/office_of_the_
pro-vice-chancellor/key_policies_and_information_affecting_students

to help students locate key policies and information

5. Expectations of student conduct

Unit credit points and Workload

This unit is a 10 credit point unit and will require your full and continuous
attention to maintain the highest possible grades. It is expected that you
will spend at least 10 hours each week (on average) which includes the four
(4) contact hours (lectures and tutorials/practicals) per week. Some weeks
you will spend more time on learning activities and assessments and in
other weeks the workload will be somewhat less. It will be essential for you

5
to keep up with the assigned reading so that you are properly prepared for
each session.

Attendance

Attendance at the tutorials/practicals is compulsory. Attendance at the

lectures is highly desirable as it will reflect student’s performance and
understanding.

Online learning

Students should access vUWS and/or check their student email account at
least twice a week.

General conduct and behaviour

According to the UWS Teaching and Learning code

(http://policies.uws.edu.au/view.current.php?id=00139 ) you are required
to:

- obtain the unit outline for this unit, by the end of the second teaching
week;
- regularly and actively participate in all scheduled educational activities,
which includes lectures, tutorial and laboratory sessions, online
activities etc;
- give honest, helpful and courteous feedback to your lecturer(s),
- make every effort to undertake the work required to successfully
complete this unit;
- submit work that is your own for any assessment task;
- not indulge in any behaviour that disrupts the teaching and learning
environment, or negatively affects fellow students and university staff,
and understand that the University will take action against such
behaviour as outlined in the Misconduct – Students Non-Academic
Misconduct Policy
- treat university property with due care and report and damaged or
broken equipment.

In addition, you should:

- be on time to lectures, tutorial and laboratory sessions. If you are late,

then please enter the lecture/tutorial room or lab with courtesy and
consideration for others;
- pay attention in lectures ,tutorials and laboratory sessions as this is
where helpful information is given out of the assessment tasks;
- switch off your mobile phone;

6
- ask questions about the content that you found difficult, immediately
after the lecture, tutorial or lab session finishes. If this cannot be
accomplished, then make sure you see your lecturer or tutor as soon as
possible to resolve any problems.

6. Learning Outcomes and Assessment

Learning Outcomes

At the successful completion of this unit, students will be able to:

- Explain the theoretical fundamentals underpinning Object Oriented Analysis.

- Identify Unified Modelling Language (UML) of the Object Management Group
(OGM) for analysing software requirements,
- Outline an object oriented lifecycle and methodology, especially the iterative and
incremental nature of Object-Oriented lifecycle,
- Explain the process of object oriented analysis especially within the context of
iterative and incremental nature of the process,
- Construct well-documented UML-based artefacts from the early phases of the
development process for the case study,
- Identify system domain, system boundaries and system interfaces,
- Construct the Model of the Problem Space based on the analysis in an industrial
CASE tool,
- Apply team work skills in a small development team, including: distributing the
development workload, resolving disputes, running meetings, and taking
minutes.
- Identify and create operational (non functional) requirements of a system
including performance and security,
- Analyse a system using generic analysis skills such as interviews and workshops,
- Transfer verbal and written instructions about the performance of software
development tasks and associated administrative duties,
- Illustrate quality assurance, quality control and user-expectations..

Assessment Activities

Continuous assessment: 50%

- Tutorial/Practical Exercises: 15% (weekly performance and attendance)

7
 - Mid-term Test: 15% (90 minutes test including reading time; closed book; held
in Week 8 or as specified in class)
- Group Assignment (also known as Project Work): 20% (submission in last
week of the semester or as specified in class)

Final Examination: 50% (180 minutes exam + reading time of 10 minutes, closed
book).

To be able to receive a pass grade or higher you must obtain at least 40% in the
final examination, and at least 50% as a total value of all your assessment scores.
(For example, getting 30 out of 50 in the assessments, and only 15 out of 50 in the
final exams will NOT pass you. It is essential to get 20 or more marks out of 50 in
the final exam to pass this unit.)

Thus, students are advised that final grades will be awarded on the basis of scaled
aggregate of assessment component marks, reflecting the requirement that the final
exam must be passed separately, and not on the basis of simple addition of raw
marks. An exceptionally poor exam mark, around 10 out of 50 or less, will cause
other assessment marks to be reduced in proportion; e.g. in the extreme case of a
mark of zero for the final exam, the unit mark would also be zero, irrespective of
lab or assignment marks. Marks shown on returned written assessment work must
therefore be interpreted as a guide only to the final mark attributed to that work.

The total mark that the student achieves in the unit will form the basis for the
determination of the grade the student will receive in the unit. Moderation of
individual task marks may be required when more than one marker marks an
assessment task. The unit is graded using criteria referencing.

Final marks and grades are subject to confirmation by the School and College
Assessment Committee which may scale, modify or otherwise amend the marks
and grades for the unit, as may be required by University policies.

6. Assessment Details
Tutorial/Practical Exercises, 15%, weekly performance and attendance
A S S E S S M E N T

I T E M 1 Criteria and Standards

Examine materials from previous lecture(s). This weekly tutorial/practical exercises
provide students with a continuous feedback on how they are progressing. It also
provides an opportunity for each group knowing the progress of members toward
the completion of the group work.

Marking Guide
Count 15% of the total assessment scores. Marking is based on the weekly
attendance and satisfactory completion of the corresponding project work (10
marked tutorial sessions corresponding to 10 project works in total). Students will

8
 receive no marks if they fail the demonstration. The feedback to student’s work will
be delivered orally during the demonstration.

Annotated example
Refer to the examples at the project work section of each chapter in the text book:
Practical Object Oriented Analysis, Bhuvan Unhelkar, ISBN 0-17-012298.

Submission details
Students will demonstrate their work to the tutor(s) before the end of the
tutorial/practical classes.

Mid-term Test, 15%, 90 mins test including reading time; Closed book; held in
A S S E S S M E N T
Week 8 or as specified in class
I T E M 2

Criteria and Standards

Examine materials from lecture 1 to lecture 6, including gained knowledge and OO
analysis and design experience during the tutorials and project works (up to week
7). This test provides students with a feedback on how they are progressing.

Marking Guide
Count 15% of the total assessment scores. Marking is based on the gained
knowledge and the understanding of concepts and models as well as OO analysis
and design in term of clarity, effectiveness and comprehension of answers. The
primitive feedbacks (e.g. score of each question) to your work will be delivered on
the return of the test results. Detail feedbacks will be given by the lecturer(s) upon
requests at the consultation hours.

Annotated example
Refer to the example at the appendix B of the text book: Practical Object Oriented
Analysis, Bhuvan Unhelkar, ISBN 0-17-012298.

Submission details
Students will hand in the exam papers to the lecturer(s) at the end of the test.

Group Assignment (also known as Project Work), 20%, OO Analysis Model in a

A S S E S S M E N T
CASE tool + Deliverables Report.
I T E M 3

Criteria and Standards

Presence in tutorials and group work is mandatory. This also includes a fair
contribution and collaborative work as a team. The project outcome reflects the
student’s gained knowledge through out the semester based on their weekly project
works.

Marking Guide
Count 20% of the total assessment scores. Important: note: students must attend
with satisfactory performance for at least 5 tutorials to be marked for the project.

9
 Annotated example
Check the vUWS website for the project template and/or instruction.

Submission details
Submission in last week of the semester (week 14) or as specified in class. Each
group will hand one hard-copy of the report (with proper binding, e.g. spiral
binding with cover page). Soft-copy (e.g. a copy in a CD or DVD disk) of the work
(e.g. diagrams, reports, etc) should also be included in the submission.

Do not send your work to the unit coordinator or your lecturer. Your tutor is
responsible to mark your work.

Final Examination, 50%, 180 mins exam + reading time of 10 mins (Closed book)
A S S E S S M E N T

I T E M 4 Criteria and Standards

Examine materials of all lectures, tutorials and project. This will test the gained
knowledge and understanding object oriented concepts, models as well as analysis
and design skills which student have learnt during the lectures, tutorials and project
works.

Marking Guide
Count 50% of the total assessment scores. Marking is based on the gained
knowledge and the understanding of concepts and models as well as OO analysis
and design in term of clarity, effectiveness and comprehension of answers.

Annotated example
Refer to the example at the appendix C of the text book: Practical Object Oriented
Analysis, Bhuvan Unhelkar, ISBN 0-17-012298.

Submission details
Students will hand in the exam papers to the examiners at the end of the test.

10
 Assignment Cover Sheet

College of xxx
School of xxxxxx

Student name:

Student number:

Unit name and number:

Tutorial group:

Tutorial day and time:

Lecturer/Tutor:

Title of assignment:

Length:

Date due:

Date submitted:

Campus enrolment:

Declaration:

I hold a copy of this assignment if the original is lost or damaged.

I hereby certify that no part of this assignment or product has been copied from
any other student’s work or from any other source except where due
acknowledgement is made in the assignment.

No part of the assignment/product has been written/produced for me by any
other person except where collaboration has been authorised by the subject
lecturer/tutor concerned

I am aware that this work may be reproduced and submitted to plagiarism
detection software programs for the purpose of detecting possible plagiarism
(which may retain a copy on its database for future plagiarism checking)

Signature:______________________________________

Note: An examiner or lecturer/tutor has the right to not mark this

assignment if the above declaration has not been signed.

11
7. Learning resources information

Essential textbooks:
Unhelkar, B., Practical Object Oriented Analysis, 2005, Thomson Publishing;
ISBN: 0170122980

Referencing requirements and assistance:

These references are not required to have, but they are good reading references for Deep Learning in
Object Oriented Analysis.

Unhelkar, B., Practical Object Oriented Design, 2005, Thomson Publishing; ISBN:
0170122999. This book covers the design persepective of the Object Orientation.
It is easy to read and follow.

Fowler, M., UML Distilled, 3rd Edition, 2004, Addison-Wesley. ISBN: 0321193687.
This is a good readable book and should be referred to in addition to the course
material.

Unhelkar, B., Process Quality Assurance for UML-Based Projects, 2003, Boston:
Addison-Wesley. ISBN: 0201758210. This book contains detailed discussion on
the process aspect of quality. Chapter 1 for UML-based models, Chapter 3 for
relevant process components, and Chapter 6 for testing are quite relevant.

Booch, G., et al, The UML User Guide, 2005, 2nd edition, Addison-Wesley, ISBN:
0321267974. This is a substantial text and should be occasionally referred to, when
students (especially teams) are looking for additional and in-depth material on a
particular topic.

Brown, D., An Introduction to Object-Oriented Analysis: Objects and UML in Plain English,
2nd edition, 2002, New York: Wiley, ISBN: 0471371378. This book is a very general
and accessible introduction to Object Oriented Analysis. It contains extensive
pedagogy and incorporates patient explanations, making it ideal for beginners as a
complement reading material.

Ian, G., O'Callaghan, A. and Wills, A. C., Object-Oriented Methods: Principles & Practice,
3rd edition, Addison-Wesley, 2001, ISBN: 020161913X. This book is very
comprehensive and informative about Object Orientation. This is suitable for deep
study students.

George, J.F., Object-Oriented Systems Analysis and Design, 2nd edition, 2007, Pearson
Prentice Hall, ISBN: 0132279002. This covers variety topics in both OO analysis
and design

Garzas, J. and Piattini, M., Object-Oriented Design Knowledge: Principles, Heuristics, and
Best Practices, 2007, Hershey, PA: Idea Group Pub, ISBN: 1591408962. This book is
suitable for students who would like to learn more about the design perspective of
OO.

12
Weisfeld, M.A., The Object-Oriented Thought Process, 2000, Indianapolis, Ind: Sams,
ISBN: 0672318539. This book covers the foundation in object-oriented concepts
and then explains how various object technologies are used.

O'Docherty, M., Object-Oriented Analysis and Design: Understanding System Development

with UML 2.0, 2005, Hoboken, NJ : Wiley, ISBN: 0470092408. This book provides
a thorough grounding in object-oriented analysis and design, providing
authoritative and accessible coverage of object-oriented concepts, the software
development process, UML and multi-tier technologies.

Booch, G. et al. Object-Oriented Analysis and Design with Applications, 2007, Addison-
Wesley, ISBN: 020189551X. This book outlines object-oriented methods using the
Unified Modeling Language 2.0 with real applications.

Key weblinks:

Good Online Books as References. These books are not required to have, but they are good reading
references for Deep Learning in Object Oriented Analysis.

Dennis, A. (2005). Systems Analysis and Design with UML Version 2.0 an Object-Oriented
Approach (2nd ed.). Hoboken, NJ: Wiley.
http://www.knovel.com/web/portal/basic_search/display?_EXT_KNOVEL_D
ISPLAY_bookid=1420

Douglass, B. P. (2007). Real Time UML Workshop for Embedded Systems. Burlington,
Mass.: Elsevier.
http://www.sciencedirect.com/science/book/9780750679060

Larman, C. (2005). Applying UML and Patterns: An Introduction to Object-Oriented

Analysis and Design and Iterative Development (3rd ed.). Upper Saddle River, N.J.:
Prentice Hall Professional Technical Reference.
http://proquest.safaribooksonline.com/0131489062

O’Docherty, M. (2005). Object-Oriented Analysis and Design: Understanding System

Development with UML 2.0. Hoboken, NJ: Wiley.
http://lib.myilibrary.com/browse/open.asp?ID=23852

Samek, M. (2009). Practical UML Statecharts in C/C++ Event-driven Programming for

Embedded Systems (2nd ed.). Amsterdam; Boston Newnes/Elsevier.
http://www.sciencedirect.com/science/book/9780750687065

13
8. Student feedback and improvements to the
unit.
You are welcome to provide feedbacks that are related to teaching, tutoring and
coordinating of the unit to the unit coordinator, lecturers and tutors. The teaching
team will seriously consider the feedbacks and improve their work.

14