|
System Modelling and Software
Architecture “I just wanted to say how
enjoyable the course was” A workshop in a training
centre. Available from Xpertise over 2 days. Can be delivered on-site over 3 days. |
|
||
|
To navigate, click on
underlined text. |
|
||
Overview
|
At
the end of the course the delegates will
|
||
|
This is an introductory level course. It distils into 2 or 3 days the principles that all architects should
know about the design and modularization of software. It covers the essentials of UML and other system modelling techniques. It introduces design patterns. It explains approaches such as CBD and SOA. It provides a good grounding for those looking ahead to career as a
solution, application or data architect, to examination for the ISEB
certificate in IT architecture, or to the System/Solution Architecture
course. It includes paper exercises, but involves no coding and there is no use
of technology. |
·
Know what software
architecture involves. ·
Know UML and other
system modelling techniques ·
Know ways to
modularize software, and their limitations. o
Software layering o
CBD
(component-based design) o
SOA
(service-oriented architecture). ·
Understand
development guidelines: design patterns, design by contract and defensive
design. ·
Understand how waterfall
and agile development methods differ ·
Have compared
experiences and exchanged knowledge with others. |
||
Relevant
examination
|
Experience
required
|
||
|
This course covers some of the syllabus the Certificate
in IT Architecture provided by the Information
Systems Examinations Board (ISEB). However, delegates intending to sit the
exam should attend the System/Solution Architecture course, to which this course is a stepping stone. |
Delegates should have used a programming language and understand the
concept of module invocation. People with more experience are welcome. You
should find the course to be useful as an overview and a ground-breaker for
the System/Solution Architecture course. |
||
|
Course outline |
|||
|
System modelling techniques ·
Systems and Models ·
Requirements/Function Models ·
Structure/Static Models ·
Behavior/Dynamic Models Design
Patterns ·
Design Patterns §
Group exercise. |
Software
modularity and reuse ·
Component-Based Development ·
Component Distribution and Integration ·
Service-Oriented Architecture Software development processes §
The SDLC and agile principles. §
Test-driven development. |
||
|
Location: A training centre. |
Timings: Usually 9 am to 5.30 pm. The tutor may vary
and extend the timings. |
Number: Maximum 14 delegates. |
Prices: See Terms. |
