Over time, software has been organised into architectural components, which have been documented and captured as patterns. “Each pattern describes a problem, which occurs over and over again in our environment, and then describes the core of the solution to that problem.” An architectural pattern describes a solution in terms of high-level abstraction.
This course teaches the techniques used to identify architecturally significant elements and how to express them using the UML notation.
The delegates will learn that, through architecture, we can more easily understand how the system “fits” and works together as well as what the system does and how it allows us to work on a part of it (generally in parallel with others).