Visão Geral
Independentemente da abordagem de desenvolvimento de software, da clássica cascata à programação extrema (XP), todos os especialistas concordam que o desenvolvimento de software de qualidade requer análise e design. A Unified Modeling Language (UML) fornece uma notação padrão comum para registrar modelos de análise e artefatos de design. Este curso aprofunda os processos de análise orientada a objetos e design orientado a objetos usando UML como linguagem de notação.
Objetivo
A importância da modelagem no ciclo de vida de desenvolvimento de software
A notação e os símbolos UML
A abordagem orientada a objetos para analisar e projetar sistemas e soluções de software
Como empregar a notação UML para criar projetos de sistema eficazes e eficientes
Publico Alvo
- Desenvolvedores de software, arquitetos de sistemas, analistas, designers e qualquer pessoa interessada em entender a UML aplicada à análise de objetos e ao projeto de sistemas.
Pre-Requisitos
- Uma boa compreensão de tecnologias orientadas a objetos e uma compreensão básica de análise e desi
Materiais
Português
Conteúdo Programatico
Analysis, Design, Modeling
- Systems and Software Quality
- Software Engineering
- Life Cycle Properties
- Analysis and Design
- Structured vs. Object Approach
- Modeling
- Modeling Problem and Solution
- Modeling Perspectives
The Object-Oriented Paradigm
- Basic Concepts
- Classes and Objects
- Characteristic of Objects
- Relationships
- Methods
- Object-Oriented Analysis
- Object-Oriented Design
- Processes and Approaches to OOA&D
- Unified Process
- Rational Unified Process
- Agile Approaches
- Other Approaches
Basic Unified Modeling Language
- Overview
- Basic Concepts
- Classifiers
- Well-Formedness Rules
- Basic Notation
- Classes and Objects
- Characteristic of Objects
- Relationships and Methods
- Other Notation
- UML Diagrams
Domain Modeling
- The Information Model
- Structural Modeling
- Objects, Attributes, and Associations
- Links and Messages
- Information Modeling in the UML
- Basic Constructs
- Relationships
- Stereotypes
- Packages
Use Case and the Behavior Model
- Use Case Model
- Use Cases in the Life Cycle
- Use Case Diagram
- Use Case Description
- Main Success Scenario
- Alternate Paths
- Preconditions and Post-Conditions
- Exception Paths
- Use Case Extensions
- Use Case Relationships
- Generalization
- The <<extends>> Relationship
- The <<includes>> Relationship
- Extension Points
- Packages
The Analysis Phase
- Modeling Process
- Architectural Views
- Use Case Realizations
- Activity Diagrams
- Application of the Activity Diagram
- Activity Diagram Notation and Syntax
- State Machines
- Application of the State Machine
- State Machine Notation and Syntax
- Sequence Diagrams
- Application of the Sequence Diagram
- Sequence Diagram Notation and Syntax
- Collaboration Diagrams
- Communication diagrams
- Application of the Communication Diagram
- Communication Diagram Notation and Syntax
Design Phase
- Moving to Code
- Internal Component Definition
- Design for Reuse
- Design Class Diagrams
- Operations
- Methods
- Designing Quality into Modules
- Iterating the Design
- Refactoring
- Design Best Practices
- Cohesion
- Complexity
- Coupling
- Congruence
Physical Design
- UML Implementation Diagrams
- Component Diagram
- Application of the Component Diagram
- Component Diagram Notation and Syntax
- Deployment diagram
- Application of the Deployment Diagram
- Deployment Diagram Notation and Syntax
Patterns
- The Pattern Concept
- Benefits of Patterns
- Common Design Patterns
- Useful Analysis Patterns
- Useful Design Patterns
The Bottom Line
- A Development Process
- Where to Go for More Information
TENHO INTERESSE