Object Oriented Analysis and Design Using UML Training Logo

Object Oriented Analysis and Design Using UML Training

Live Online & Classroom Enterprise Training

Learn Object Oriented Analysis and Design using UML with various in depth topics like OOPs concept, Modeling, Design Essentials, Activity Diagram etc.

Looking for a private batch ?

REQUEST A CALLBACK

Need help finding the right training?

Your Message

  • Enterprise Reporting

  • Lifetime Access

  • CloudLabs

  • 24x7 Support

  • Real-time code analysis and feedback

What is Object Oriented Analysis and Design Using UML Training about?

Objective Oriented Programming and Design has taken a center stage in software development from last few years. Languages like Java, C# and even C++ thrive on these concepts and use them as an essential tool for their architecture and design. So our course starts with basic OOPs concepts like inheritance, polymorphism and encapsulation. It then touches a bit of software modeling, basically, a method to do requirement gathering and it's analysis to arrive at the design. Use Case approach is used for requirement gathering and documentation technique so that is covered in detail at this point of time in the course. Now Object Oriented Analysis and Design has many different parts like Class Diagrams and their relationships, sequence and collaboration diagrams, state machine diagrams, so this is what is taken up next in the course. A few very important and useful design principles like High Cohesion and Loose Couple are then taken up next. A quick look at design patterns like Inversion of Control and Dependency injection is covered next.

What are the objectives of Object Oriented Analysis and Design Using UML Training ?

This course gives you an in dept knowledge of basic and advance OOPS, UML and Software Design Principals, also the design essentials, activity diagram etc. for the depth.

Available Training Modes

Live Online Training

Course Outline Expand All

Expand All

  • What is Object-oriented?
  • What is an Object?
  • Encapsulation
  • Class vs. Object
  • Inheritance
  • Multiple Inheritance
  • Polymorphism
  • Object Orientation vs. Procedure Orientatio
  • Describe the Object-Oriented Software Development (OOSD) process
  • Describe how modeling supports the OOSD process
  • Describe the benefits of modeling software
  • Explain the purpose, activities, and artifacts of the following OOSD workflows (disciplines): Requirements Gathering, Requirements
  • Generalization
  • Realization
  • Association
    - Association Roles
    - Multiplicity / Cardinality
    - Association Classes
    - Building the Static Model
  • Composition
  • Aggregation
  • Dependency
  • Discovering Classes
  • Class Diagrams
  • Class Diagram Details
  • Class Stereotypes
  • Discovering Classes
  • Building Object Models
  • Decoupling Abstraction and Implementation
  • Eliminating Class Proliferation
  • Dependency Inversion
  • Prefer Inheritance over Composition
  • Building an Analysis Model
  • Analysis Level Classes
  • Boundary, Control, External Interface & Entity classes
  • Inheritance and maintainability
  • Low Coupling
  • High Cohesion
  • Loose Coupling vs. Tight coupling
  • Remodeling Multiple Inheritance (MI)
  • Collaboration & Relationships
  • Why prefer 'Composition over Inheritance'?
  • Inheritance and Abstractions
  • Single Responsibility Principle
  • Open Close Principle
  • Encapsulate what varies
  • Generalization = Association + Realization ( + Delegation)
  • Is-a vs. has-a trade-offs
  • Avoiding Class Proliferation
  • LISKOV Substitution Principle (LSP)
  • Interfaces, Packaging, Public and Internal classes
  • Inheritance Drivers
  • Composition Drivers
  • Dependency Inversion Principle
  • General Steps in a UML-Based Process
  • Use Cases
  • Actors
  • Use Case Diagrams
  • Use Case Description
  • Use Case Template
  • Use Case Relationships
  • Business Modeling
  • Justify the need for a Use Case diagram
  • Identify and describe the essential elements in a UML Use Case diagram
  • Develop a Use Case diagram for a software system based on the goals of the business owner
  • Develop elaborated Use Case diagrams based on the goals of all the stakeholders
  • Recognize and document use case dependencies using UML notation for extends, includes, and generalization
  • Describe how to manage the complexity of Use Case diagrams by creating UML packaged views
  • Identify and document scenarios for a use case
  • Create a Use Case form describing a summary of the scenarios in the main and alternate flows
  • Describe how to reference included and extending use cases.
  • Identify and document non-functional requirements (NFRs), business rules, risks, and priorities for a use case
  • Identify the purpose of a Supplementary Specification Document
  • Identify the essential elements in an Activity diagram
  • Model a Use Case flow of events using an Activity diagram
  • Identify a set of candidate key abstractions
  • Identify the key abstractions using CRC analysis
  • Refining the Models
  • Activity Diagrams
  • Activity Diagram Details
  • Activity Diagram : Example
  • Activity Diagram with Swimlanes
  • Identify the essential elements in a UML Class diagram
  • Construct a Domain model using a Class diagram
  • Identify the essential elements in a UML Object diagram
  • Validate the Domain model with one or more Object diagrams
  • Building the Dynamic Model
  • Interaction Diagrams
  • Sequence Diagrams
  • Messages
  • Lifelines
  • Activations
  • Sequence Diagram - Example
  • Collaboration Diagrams
  • Message Labels
  • Collaboration Diagram : Example
  • Model object state
  • Describe the essential elements of a UML State Machine diagram
  • States and Events
    - State Diagrams
    - Guard Conditions
    - State Diagram Details
    - Substates
    - Concurrent Substates
    - Disjoint Substates - Nesting
    - Disjoint Substates : Layering
  • Describe the concepts of the Client and Presentation tiers
  • Describe the concepts of the Business tier
  • Describe the concepts of the Resource and Integration tiers
  • Implementing Deployment Diagrams
    - Moving Towards Implementation
    - Logical vs. Physical Architecture
    - Hardware and Software Concepts
    - Creating Component Diagrams
    - Creating Deployment Diagrams
    - Allocating Components to Nodes

Who is the instructor for this training?

The trainer for this Object Oriented Analysis and Design Using UML Training has extensive experience in this domain, including years of experience training & mentoring professionals.

Reviews