Course Category: Business Analysis
Course Duration: 4 Days
Hours: 28 Contact Hours
Select your country to access the registration page
Singapore
Duration: 4 Day
Timing: 9 AM to 5 PM Singapore Time
Malaysia
Duration: 4 Day
Timing: 9 AM to 5 PM Malaysia Time
Philippines
Duration: 4 Day
Timing: 9 AM to 5 PM Philippine Time
Australia
Duration: 4 Day
Timing: 12 PM to 8PM AEST
All other locations
Duration: 4 Day
Timing: Timing: 9 AM to 5 PM Philippines/Singapore/Hong Kong Time
Course Overview
All software development projects require a set of good processes for success.
This four-day course focuses on risk management and development of use-case and centric object-oriented applications. The training familiarizes participants with process of Object-Oriented Analysis and Design (OOAD) using Unified Modeling Language (UML2).
The workshop begins with structuring requirements and then illustrates the methodology to design PIM (Platform Independent Model) and PSM (Platform Specific Model) with logical progression. Roles of architect, designer, analyst and developer are clearly identified, in context of OOAD. Program covers UML2 concepts, OO concepts, iterative development, requirements management and then analysis & design process using UML2. A view of architect’s role is explained. This program is interactive blend of theory and hands-on with Modelio Open Source. The class is intense, yet fun.
Pre-Requisites
Attendees must have experience of software development in any object-oriented programming language. Familiarity with UML is not required but will be helpful.
Software Requirements
Modelio Open Source
Audience
The course is aimed for software developers who aspire to be efficiently design and evolve their software.
Training Duration
Training: 4 days.
The course material shall be issued on the first day of the course during registration.
Course Outline
OO and UML
- Complexity
- Iterative Development
- Modeling
- What is it?
- Why do it?
- Guidelines
- Pillars of OO
- Coupling & Cohesion
- Modularity
- Abstraction
- Encapsulation
- Polymorphism
- Generalization
- Hierarchy
- Heuristics
- DRY
- KISS
- YAGNI
- Analysis vs Design
- Design vs Architecture
- Architecture Views
- UML2
- Object
- Concepts
- Diagrams
- Tools
- Intro to Modelio Open Source
UML
- Key Concepts
- Profiles
- Stereotypes
- Tagged Values
- Constraints
- Class Diagram
- Dependency
- Realization
- Association
- Aggregation
- Composition
- Generalization
- Use Case Diagram
- Use Case Specification
- Relationships
- Sequence Diagrams
- Lifeline and Activation
- Messages
- Structures
- Activity Diagram
- Activity and Action
- Nodes and Flows
- Partitions and Regions
- Object Diagram
- State Machine Diagram
- States and Transitions
- Events and Actions
- Other Diagrams
- Package Diagram
- Component Diagram
- Deployment Diagram
- Communication Diagram
- Interaction Overview Diagram
- Timing Diagram
- Composite Structure Diagram
PROCESS
- Requirements Modeling
- Vision Document
- Use Case Model
- Supplementary Specification
- Vision
- Glossary
- More
- Use Case Modeling
- Identifying Actors
- Defining Use Cases
- Use Case Relationships
- Object-Oriented Analysis
- Scenarios and Narratives
- CRC Cards
- Use Case Analysis
- Analysis Classes
- VOPC to PIM
- Use Case Realization
- Interaction Diagrams
- State Diagrams
- Identifying
- Responsibilities
- Information
- Object Oriented Design
- Architectural Patterns
- N+1 Views
- Component and Package Design
- Design Patterns
- Mapping PIM to PSM
- Technology Selection
- Code Generation
- Mechanism Design
- Database Design
- Distribution Design
- Packaging Principles
DESIGN PRINCIPLES
-
- SOLID+
- SRP
- OCP
- LSP
- ISP
- DIP
- DBC
- FCG
- More
- GRASP
- Expert
- Indirection
- CQRS
- Controller
- Dependency
- Dependency Injection
- Inversion of Control
- Packaging
