Course Duration: 3 Days

Course Category: Business Analysis & Requirements Engineering

 

21 Contact Hours

Object Oriented Analysis and Design with UML

   
About the Course Any non-trivial software development needs a good strategy for success. This program focuses on risk management and development of use-case centric object-oriented applications.

This program familiarizes participants with process of Object-Oriented Analysis and Design (OOAD) using Unified Modeling Language (UML). The course begins with workshops on structuring requirements and then illustrates on the methodology to design a model with logical progression.

Roles of architect, designer, analyst and developer are clearly demarcated in context of OOAD. Program covers UML concepts, advanced OO concepts, iterative development, requirements management and then analysis & design process using UML. A view of architect's role is demonstrated.

This program is interactive blend of theory and hands-on.  Program is intense, yet fun.

   
Learning Outcomes The course attendee would learn how to:

  • Identify domain concepts and relationships to model using UML.
  • Use UML modeling as fundamental tool to analyze and then to design 
   
Pre-requisites: Participants must have experience of software development using OO technology. 
   
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

    • Mechanisms
      • 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

     


    Available Funding Support
    Malaysia Only

    HRDF Logo_02This course is HRDF SBL & HRDF SBL Khas Approved

    Leave a Reply

    Your email address will not be published. Required fields are marked *

    You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong> <font color="" face="" size=""> <span style="">

    PMI, PMP, PMBOK, CAPM, PMI-ACP and the Registered Education Provider logo are registered marks of the Project Management Institute, Inc.
    CMMI®, Capability Maturity Model®, Capability Maturity Modeling®, CMM®, PCMM® and Carnegie Mellon® are registered in the US Patent and Trademark Office by Carnegie Mellon University.
    ISTQB® is a Registered Trade Mark of the International Software Testing Qualifications Board.
    IIBA®, BABOK® and Business Analysis Body of Knowledge® are registered trademarks owned by International Institute of Business Analysis. CBAP® and CCBA® are registered certification marks owned by International Institute of Business Analysis. Certified Business Analysis Professional, Certification of Competency in Business Analysis, Endorsed Education Provider, EEP and the EEP logo are trademarks owned by International Institute of Business Analysis.
    The APMG-International Agile Project Management, AgilePM and Swirl Device logos are trademarks of The APM Group Limited.
    PRINCE2®, ITIL®, IT Infrastructure Library®, and MSP® are registered trademarks of AXELOS Limited. The Swirl logo™ is a trade mark of AXELOS Limited.
    The ITIL Licensed Affiliate logo is a trademark of AXELOS Limited.
    SCRUM Alliance REP SM is a service mark of Scrum Alliance, Inc.