Agile Modeling with UML
Are you looking for ways to facilitate the communication with colleagues and stakeholders, making it to-the-point, graphic in both respects? Or, are you already walking the fine line between TAGRI (“They ain’t gonna read it”) and absence of a concise overview?
Audience
- Developers/programmers, modelers, designers, analysts, architects, testers, PMs, technical managers, and other stakeholders, especially in agile projects interested in models, abstraction, the Unified Modeling Language (UML), objects, or model driven development.
- Devs new to the role, as well as experienced seniors who want to add structure and clarity to their work.
Courseware
Presentation slides and exercises, in English.
The course is taught in English or Swedish (Contact us if you prefer a 3-day version on-site with Swedish slides).
Utbildningsformer
Remote
Längd
2 dagar
Pris
20450 kr
Goal
The Agile Modeling course will:
- Deepen your understanding of the fundamentals in agile modeling and its benefits
- Show how fundamental UML diagram types fit into and complement each other
- Teach you how to produce lean drawings from requirements, and to build robust, extensible, portable, concisely documented systems
- Stay technology-neutral, avoiding solutions tied to a particular language or environment, and emphasize exercises, teamwork and communication in small groups (rather than explore tools or methodologies)
- Take 2 days, in contrast to its initial 4-day version.
Prerequisites
Basic general knowledge of systems development, or of object orientation. Experience as an IT developer, or similar, is optional yet useful.
Contents of Agile Modeling with UML
Day 1
-
Introduction
- Practical information, course hours, course agenda
- Agile models, JBGE, UML 2, and model driven (versus traditional)
- The benefits
-
Key Concepts and Terminology
- Class and Object
- Relationships: generalization, association, aggregation
- Polymorphism
- Parameterization, template classes
- Connection (for senior staff) to legacy and some concepts in traditional systems development
- Key consequences: size and modifiability of the code, a simple example with and without objects
- Exercises
-
Modeling: Structure
- Think big, start small, travel light
- How functional requirements/Use Cases/User Stories complement structure
- Exercise
- Classes and relationships
- Domains, subsystems
- Exercise
Day 2
-
Modeling: Behavior, dynamics
- Scenarios: Sequence diagrams
- Exercise
- Life cycles, states, state transitions: State diagrams (per class)
- Exercise
-
Design checklist
- Seamless, iterative
- Architectural design, with examples of Class structure adjustments
- Detail design
- Maintainability: Design for change
- Results
- Exercise
-
Reusability, sum up, Q & A
- SOA, components, degrees of component reusability
- Summing up: Slim UML in agile projects.
End of the course
Schedule
Kursstart: 09.00
Kursslut (ca): 17.00