Kurs: Architecture Skills - Kevlin Henney

Every system has an architecture, whether accidental or intentional, and regardless of whether it was put in place by a nominated architect or whether it emerged from the decisions and discussions of a team. All too often the focus of what is often described as architecture is centred around a specific set of platform technologies, which forms only one part of the set of concerns an architecture should address and only one aspect of the skill set an architect needs to possess.

The Architecture Skills course introduces a broad curriculum for software architects. The course introduces development process models, architectural styles, requirements techniques, sufficient modelling techniques, design patterns and testing practices. This course includes a number of practical exercises so that attendees can see how the different activities fit together. There is also plenty of opportunity for discussion.

Software architects and lead developers looking to both broaden and sharpen their skills in the disciplines touched on by software architecture, not just specific technologies.

Software Architecture Architecture and design · Architectural viewpoints · Design stability and feedback · Dependencies · Agility · Prototyping · The role of the architect · The place of technology

Development Process Schedule–driven versus value–driven versus risk–driven approaches · Sequential versus iterative and incremental · RUP · Agility · XP · Scrum · Lean · Kanban

System Context and Requirements Context models · Functional, operational and developmental requirements · Use cases and user stories · Complexity, risk and value

Modelling Information modelling with UML · Behavioural modelling with UML · Design models · Models versus modelling · Sufficiency · Techniques and notations beyond OO modelling and UML

Architectural Styles Procedural approaches · Implicit invocation · Concurrency · Modularity · Partitioning and layering · OO · Distributed computing · Dataflow versus repository systems

Patterns Recurring designs · Context dependency · Lone patterns · Combining patterns · Pattern stories and pattern languages · Pattern examples and counterexamples

Testing System versus programmer testing · Unit and integration tests · TDD, POUT and DDT · Test–driven feedback on dependencies · Dependency management · Test doubles

Exercises Identify consequences of intentional and accidental design decisions in attendee projects · List risks and challenges in actual and example projects · Establish conceptual model · Draw up a product backlog

Workshop Examine and clarify requirements for an example project · Identify risks and challenges · Establish conceptual model · Draw up and prioritise a product backlog · Draw up a high–level design model over short timeboxes, identifying patterns and trade–offs · Review progress, design and decisions