About this course
Object Orientation affects more than just code. Many common development problems — such as unexpected behaviour, difficult changes, and long debugging cycles — often start during analysis and design.
This course focuses on applying object-oriented thinking during analysis. Using UML as a communication tool, you will learn how to model systems that reduce ambiguity, control complexity, and support change.
The course is for analysts who work closely with OO developers.
The course runs in parallel with the first three days of the Object-Oriented Analysis and Design course.
Delegate feedback
Feedback from delegates who have attended this course:
H. Swanepoel
W. Smith
M. Ntuli
K. Mtintsilana
S. Siricoth
Intended audience
This course is useful if:
- You are a business analyst, project manager or system architect, and you work with developers who use object orientation.
- You are involved in analysing business requirements and you need to model object-oriented systems clearly and consistently.
Prerequisites
- You do not need any programming experience.
- You should, however, have some experience working with systems and analysing user requirements.
Course details
Price: R12,900 excluding VAT per delegate.
Included:
- Electronic course material.
- Attendance certificate (PDF).
Duration: 3 day3.
Delivery: Virtual classroom
See how virtual training works.
Note: this course is presented on request only.
See the course schedule for upcoming dates.
Booking information
Email your booking to info@incusdata.com. A purchase order, or completed enrolment form is sufficient.
We will confirm the booking and issue an invoice.
Course contents
Introduction
- Why design problems show up later as bugs and rework.
- Object orientation as a thinking model, not a syntax feature.
- Where OO helps, and where it creates unnecessary complexity.
Object-Oriented Concepts and Terminology
- Classes, objects, and responsibilities.
- Encapsulation and abstraction for reducing coupling.
- Inheritance vs composition.
- Polymorphism and interfaces.
- Associations and relationships between classes.
UML as a Communication Tool
- What UML is for: shared understanding and fewer assumptions.
- Choosing the right diagram for the question you are answering.
- Core diagrams used on the course: use case, activity, class, sequence, state, component, deployment.
- Common extension mechanisms (stereotypes, notes, constraints).
- Practical use of modelling tools.
Object-Oriented Process and Method Choices
- Iterative development and feedback loops.
- How analysis and design fit into Agile projects.
- Lightweight OOAD workflows (RUP overview, ICONIX overview, Agile Modelling).
- What to do when process guidance is missing.
Object-Oriented Analysis
- Use cases for clarifying behaviour and scope.
- Use case text vs diagrams: when each helps.
- Activity diagrams for flows, paths, and edge cases.
- Domain modelling and terminology alignment.
- Class identification and domain classes.
- CRC cards and collaborative modelling.
- Selecting UML diagrams that reduce ambiguity during analysis.
Download the course outline
Download the Object-Oriented Analysis course outline in PDF format.