Overview
 While
many developers and managers have a clear idea regarding the characteristics,
practices, and corresponding set of responsibilities of their own roles, the
picture is often vague when it comes to software architects. What is the single
most important task facing the software architect? What is the division of labor
and responsibilities between the architect and the project manager? How much the
architecture should be tied in to the particulars of the underlying technology
used, or for that matter, for the specifics of the business? where is the
hand-off point between the architect and the developers? What are the necessary
skills and analysis tools employed by an architect? How do you validate the
design before construction? How do methodologies such as service-orientation
affect the design and development process? What are software architecture best
practices, guidelines and pitfalls? How do you go about designing world-class
systems? How do you make the transition from abstract design patterns and
concepts to concrete development decisions? How does the architect decompose the
system into its sub system and modules?
The class answers the above
questions by teaching the attendees the battle-proven practices of IDesign,
distilling lessons learned during more than a decade of architecting systems
across numerous projects, industries, countries, and teams. The class also
points out classic mistakes and risk mitigations across the process, technology
and design. Conducted in the style of a classic Master Class, the IDesign
architect will provide the common foundation required by software architects,
both technical and soft skills.
Noteworthy is that this class is called the Architect’s Master Class (as opposed
to the Architecture Master Class) because it is dedicated to the core body of
knowledge required of today’s modern software architects, knowledge that
transcends mere design patterns and architecture. The core body of knowledge
comprises of three elements: development process, technology, and finally
analysis & design. The class shows the architect how to take an active
leadership role on all three aspects, as a continuum, since when executing a
design, one cannot separate process from design from technology – all three have
to work in concert. The class agenda reflects these three elements. The first
part is devoted to the accompanying service-oriented development process and the
required project management skills. The second part is an immersion
in key modern design patterns and development skills, using WCF as a reference
model, as a way of illustrating the design ideas and best practices, ensuring
the architect is a qualified technical lead. These include interface-based
design and contract factoring, service-oriented design, general design principal and
patterns concerning reliability, data transfer, instance management scalability
and throughput, availability and responsiveness, loosely coupled systems,
service discovery, fault
propagation, transaction management, concurrency management, security scenarios,
and the new Windows Azure AppFabric Service Bus.
In the last part the
IDesign architect will explain the IDesign original approach to large system
analysis and design called the IDesign Method™.
The IDesign Method has three elements: it is a method for decomposing a system
into modules or services based on the system top-level uses cases, the IDesign
Method offers a set of very simple design notations to capture the design
decisions, and the Method is a near-mechanical approach to automating the design
decision of rarely discussed topics such as allocation of services to
assemblies, allocation of services to processes, transaction boundaries,
identity management, authorization and authentication boundaries,
synchronization and more.
You will also receive the IDesign
documents and diagram templates, tools and samples and reference projects.
Don’t miss on this unique opportunity to learn from the IDesign architects,
share their passion for architecture and software engineering, gain from their
experience of numerous design projects and profound insight on architecture,
technology and its applications.
Target Audience
Any .NET architect, project lead or senior developer would benefit greatly from the class.
Duration
5 very intense days.
Offering
Available as an on-site class and as a public class. The next public class
will be in San Jose, CA, in December 13-17 2010.
Click
here for registration and additional information. |