5 Days course
Language: English
This course is only available on request!!
| Object Oriented Analysis and Design Using the Unified Modeling Language
(UML)
5 Days course Language: English This course is only available on request!! |
|
|
DESCRIPTION |
WHAT YOU WILL LEARN |
|
WHO SHOULD ATTEND: |
ASSUMED KNOWLEDGE |
OUTLINES
CHAPTER 1: INTRODUCTION
1) Why OO? OO vs. Procedural
2) Object Principles
3) The OO Lifecycle
4) Iterative/Incremental Development Process
CHAPTER 2: THE UNIFIED MODELING LANGUAGE
1) The Role Of OO Modeling
2) Key Concepts of UML
CHAPTER 3: REQUIREMENTS DEFINITION
1) Requirements Gathering Techniques
2) Use Cases & Scenarios
CHAPTER 4: DISCOVERING OBJECTS FROM REQUIREMENTS
CHAPTER 5: STATIC MODELING
1) Class Diagrams
2) Object Diagrams
CHAPTER 6: DYNAMIC MODELING
1) Interaction Models
2) Modeling State & Concurrency
CHAPTER 7: OBJECT RELATIONSHIPS
1) Generalization (Inheritance)
2) Aggregation & Composition
3) Association
4) Dependency
CHAPTER 8: QUALITY CHARACTERISTICS
1) What is a "good" object?
2) What is a "good" model?
CHAPTER 9: PRINCIPLES OF SOFTWARE ARCHITECTURE
1) Architectural Styles
2) Tiering
3) Designing to Architecture
CHAPTER 10: INTRODUCTION TO ADVANCED TECHNIQUES
1) Patterns
2) Modeling Roles
3) Design Efficiency
4) Exception Management
5) Wrapping Legacy Systems
![[HOME]](../home.gif){kind=small}
![[dates]](../sched.gif){kind=small}
![[reserve]](../reserve.gif){kind=small}
![[seminars]](../seminars.gif){kind=small}
This course uses the industry-standard Unified Modeling Language
as the means of expressing OO concepts, and providing team members with a common notation and vocabulary for communicating
their ideas. 
Understand essential UML notation.
Business or system analysts, technical managers, and software developers
who need a common, practical technique for describing and constructing object-oriented systems.
Experience in analysis, design or development is desirable, but not mandatory.