Object Oriented Analysis and Design with UML

Course Category: Business Analysis
Course Duration: 3 Days
Hours: 21 Contact Hours

Select your country

Select your country to access the registration page

Singapore

Register Now

Duration: 3 Day
Timing: 9 AM to 5 PM Singapore Time

Malaysia

Register Now

Duration: 3 Day
Timing: 9 AM to 5 PM Malaysia Time

Philippines

Register Now

Duration: 3 Day
Timing: 9 AM to 5 PM Philippine Time

Australia

Register Now

Duration: 3 Day
Timing: 11AM to 7PM AEST

All other locations

Register Now

Duration: 3 Day
Timing: Timing: 9 AM to 5 PM Philippines/Singapore/Hong Kong Time

About the Course

Any non-trivial software development needs good strategy to increase success probability. This program equips participants with one which focuses on risk management and development of use-case centric object-oriented applications without being burdensome.

This program familiarizes participants with process of Object-Oriented Analysis and Design (OOAD) using Unified Modeling Language (UML) which starts with structuring requirements and then to come up with design model with logical progression. Participants learn how to identify domain concepts and relationships to model using UML. Participants also learn to use UML modeling as fundamental tool to analyze and then to design formally. Roles of architect, designer, analyst and developer are clearly demarked in context of OOAD. Program starts with advanced OO concepts and takes participants through UML concepts, iterative way of working, requirements management and then to analysis & design process using UML. En-route it includes good view of architect’s role.

This program is interesting blend of theory and hands-on which renders learning process interactive and fun.

Pre-Requisites

Participants must have good practical knowledge and experience of software development using OO technology. Program is very intense and will need utmost attention from participants.

Who should Attend

  • Software developers, project leaders, system analysts, technical leaders.
  • Any software professional who aspires to systematically analyze and design software using OOAD.

Course Outline

OOT, SDLC, UML

  • OOT Pillars understanding
    • Encapsulation
    • Abstraction
    • Hierarchy – inheritance and polymorphism
    • Modularity
  • How do technologies implement these?
  • SDLC
    • Why not waterfall
    • Iterative Model
    • UP and its phases
    • Other SDLC model
  • Modeling, incompleteness and ambiguity
  • UML Vocabulary
    • Object
      • Identity
      • Boundary
      • State
      • Behavior
    • Object Oriented
    • Class
    • Interface
    • Component
    • Subsystem
    • Package
    • Message
    • Introduction to all diagrams of UML
    • Reverse Engineering
  • More About UML
    • Primary Artifacts
    • Motivation to Define UML
    • Goals of the UML
    • Scope of the UML
  • Visualizing a Class
    • Elements of the Class Definition
    • Classes
    • Attributes
    • Operations
    • Visibility
  • Modeling a Class
    • Elements of a Class Diagram
    • Modeling an Attribute
    • Modeling an Operation
    • Modeling the Class Compartments
  • Modeling the Relations among Classes
    • Modeling Association
    • Modeling Aggregation
    • Modeling Composition
    • Modeling Generalization
    • Modeling Realization
  • Hands on – Convert a diagram to source code

THE ELEMENTS OF THE USE CASE MODEL

  • Use Case Diagrams
    • Use Case System
    • Use Case Actors
    • Use Cases
  • Use Case Narratives
    • Assumptions
    • Pre-Conditions
    • Use Case Initiations
    • Dialog
    • Use Case Termination
    • Post-conditions
    • Additional narrative Elements
  • Use Case Scenarios
  • Use Case Relationships
    • Association
    • Include
    • Extend
    • Generalization
  • Understanding the Activity Diagrams
    • Modeling Workflow
    • Activity Diagram Notations
    • Action State
    • Sub-activity State
    • Decisions
    • Swim-lanes
    • Action-object Flow Relationship
  • Applying Use Cases
    • Applying Use Case Relationships
    • Building Use Case Diagrams
    • Writing Use Case Narratives
    • Identifying Use Case Scenarios
    • Hands on – Find Actors and Use Cases
  • Hands on – Convert a diagram to source code

ANALYSIS - CONVERT USE CASE MODEL TO ANALYTICAL MODEL DESIGN

  • Understanding Business Modeling
  • What is Analysis
  • What is Design
    • Requirement Vs Analysis Vs Architecture Vs Design Vs Development
  • 4 + 1 View
  • Neither top-Down nor bottom-up
  • Steps of Analysis
  • The Interaction Diagrams
  • Understanding the Sequence Diagrams
    • Purpose of Sequence Diagrams
    • Notations of a Sequence Diagram
    • Object Lifeline
    • Activation
    • Message
  • Understanding the Collaboration (Communication) Diagrams
    • Purpose of Collaboration Diagrams
    • Similarities and Differences between Sequence and Collaboration Diagrams
    • Notations of a Collaboration Diagram
    • Creation and Destruction Markers
  • Entity, Control, Boundary
  • Hands on – Apply interaction diagrams to evolve analytical model

DESIGN

  • Mechanics
    • Conceptual
    • Analytical
    • Implementation
  • Apply Mechanism
  • Subsystem Identification
  • Packaging
  • Architectural Patterns
  • Component Diagram
  • Deployment Diagram
  • New Diagrams
  • Class Design Patterns
    • Example of one GoF pattern using object diagram and class diagram
  • Class Design
    • How to decide relationship
    • Black Box Vs White Box
    • Design Strategy
      • Visibility
      • Scope
      • Coupling
      • Cohesion
    • Best Practices
  • Understanding the State Chart Diagrams
    • Purpose of State Chart Diagram
    • Mapping Object Life Cycle
    • Notations for State Chart Diagrams
    • State and Composite State
    • Event
    • Transition
  • Hands on – Applying the State Chart Diagrams to the Design