Object-Oriented Analysis & Design Using UML
- Object-Oriented Analysis & Design Using UML Training Class Summary
-
Object-Oriented Analysis and Design (OOA&D) is a process of identifying the needs of a software project and laying out specifications in various models. The Unified Process, in which four iterative phases are used to hone the architecture and build the system, is the framework for many OOA&D endeavors. Each phase can consist of models from different perspectives. These models are documented using the Unified Modeling Language, an industry-standard language for visualizing, specifying, and documenting the architecture of the system.
In this course, students learn how to identify and design objects, classes, and their relationships to each other, which includes links, associations, and inheritance. A strong emphasis is placed on UML diagram notation for use cases, class and object representation, links and associations, and object messages. This course utilizes UML 2.0 notation.
Audience: Analysts, designers, and programmers responsible for applying OO techniques in their software engineering projects.
Prerequisites: Familiarity with structured techniques such as functional decomposition is helpful.
Class Length: 5 days
- Object-Oriented Analysis & Design Using UML Training Class Objectives
-
- Apply the principals and practices of Object-Oriented Analysis and Design.
- Use modeling in analysis and design, particularly in visual modeling.
- Use the Unified Modeling Language to create visual models of business problems and software solutions.
- Design programs with objects.
- Create more flexible and more maintainable software systems at lower costs.
- Object-Oriented Analysis & Design Using UML Training Class Detailed Outline
-
- Course Introduction
- Course Objectives
- Overview
- Suggested References
- Introduction to Analysis and Design
- Why is Programming Hard?
- The Tasks of Software Development
- Modules
- Models
- Modeling
- Perspective
- Objects
- Change
- New Paradigms
- Objects
- Encapsulation
- Abstraction
- Objects
- Classes
- Responsibilities
- Attributes
- Composite Classes
- Operations and Methods
- Visibility
- Inheritance
- Inheritance Example
- Protected and Package Visibility
- Scope
- Class Scope
- Advanced Objects
- Constructors & Destructors
- Instance Creation
- Abstract Classes
- Polymorphism
- Polymorphism Example
- Multiple Inheritance
- Solving Multiple Inheritance Problems
- Interfaces
- Interfaces with Ball and Socket Notation
- Templates
- Classes and Their Relationships
- Class Models
- Associations
- Multiplicity
- Qualified Associations
- Roles
- Association Classes
- Composition and Aggregation
- Dependencies
- Using Class Models
- Sequence Diagrams
- Sequence Diagrams
- Interaction Frames
- Decisions
- Loops
- Creating and Destroying Objects
- Activation
- Synchronous & Asynchronous
- The Objects Drive the Interactions
- Evaluating Sequence Diagrams
- Using Sequence Diagrams
- Communication Diagrams
- Communication Diagrams
- Communication and Class Diagrams
- Evaluating Communication Diagrams
- Using Communication Diagrams
- State Machine Diagrams
- What is State?
- State Notation
- Transitions and Guards
- Registers and Actions
- More Actions
- Internal Transitions
- Superstates and Substates
- Concurrent States
- Using State Machines
- Implementation
- Activity Diagrams
- Activity Notation
- Decisions and Merges
- Forks and Joins
- Drilling Down
- Iteration
- Partitions
- Signals
- Parameters and Pins
- Expansion Regions
- Using Activity Diagrams
- Package, Component, and Deployment Diagrams
- Modeling Groups of Elements – Package Diagrams
- Visibility and Importing
- Structural Diagrams
- Components and Interfaces
- Deployment Diagram
- Composite Structure Diagrams
- Timing Diagrams
- Interaction Overview Diagrams
- Use Cases
- Use Cases
- Use Case Diagram Components
- Use Case Diagram
- Actor Generalization
- Include
- Extend
- Specialize
- Other Systems
- Narrative
- Template for Use Case Narrative
- Using Use Cases
- Process
- Process
- Risk Management
- Test
- Reviews
- Refactoring
- History
- The Unified Process
- Agile Processes
- The Project
- Inception
- Elaboration
- Elaboration II
- Construction Iterations
- Construction Iterations - The Other Stuff
- Domain Analysis
- Top View – The Domain Perspective
- Data Dictionary
- Finding the Objects
- Responsibilities, Collaborators, and Attributes
- CRC Cards
- Class Models
- Use Case Models
- Other Models
- Judging the Domain Model
- Requirements and Specification
- The Goals
- Understand the Problem
- Specify a Solution
- Prototyping
- The Complex User
- Other Models
- Judging the Requirements Model
- Design of Objects
- Design
- A Few Rules
- Object Creation
- Class Models
- Interaction Diagrams
- Printing the Catalog
- Printing the Catalog II
- Printing the Catalog III
- Object Links
- Associations
- Refactoring
- Refactoring
- Clues and Cues
- How to Refactor
- A Few Refactoring Patterns
- Appendix A – UML Syntax
- Appendix B – Design by Contract
- Contracts
- Enforcing Contracts
- Inheritance and Contracts
- Appendix C – University Summary
- Appendix D – Implementations in C++, Java, and C#
- Course Introduction