skip to the main content area of this page
Trainings

Architecture Clinic

 



The Architecture Clinic is designed to guide and accelerate your exposure to the practices of modern software design. It is a 5 day highly interactive event where you will learn, improve, and exercise software architecture skills, all based on the IDesign Method – a breakthrough, battle-proven approach to software architecture that has shown up to 80% reduction in the effort and time required for architecting, designing, and implementing software solutions. Through its application, it produces an easy-to-follow blueprint for the construction of a software system, while covering all the important aspects involved.
During the Clinic, you will architect several systems, most of them based on real-world problems brought in by the Clinic’s participants (and you may offer a system for the team to work on as well, which could be a nice side benefit). Through guided practice, you will exercise the IDesign Method and become proficient at it - the Clinic will be run by an IDesign Master Architect who will teach you the thought process and the rationale behind the design decisions. Along the way we will walk you through the steps of the IDesign Method, share insight, inform best practices, and also help develop the “soft skills” that are so important to success such as customer interview and design review presentation. In normal day-to-day work, this type of knowledge and insight can take many years to attain. The Clinic will shorten your learning curve through our years of deep industry experience, and provide a perfect forum for focused, high caliber discussions and mentorship.
The clinic starts with a thorough presentation of the IDesign Method, after which the first system is presented. The attendees are divided into teams; each analyzes and architects the system. Then, the Master Architect will critic or approve each team's design as well as present the school's solution. For the subsequent systems design, all teams are reshuffled, so that no team is ever the same. This helps train architects to focus and communicate, and work efficiently and effectively with other architects.
But the clinic is not just about architecture. A good design is only good if you were able to build it. The clinic bridges the crucial gap between the design and the development process in the last day. You will see how to derive and design a project plan out of your architecture, how to design against the critical path of integration, how to identify potential problem in the plan that may necessitate changes to the design, and how to estimate the cost and schedule of constructing your architecture, to enable educated decisions further on.
Clinic Alumni refer to it as a "career changing event" since "finally, the blinders are off", and they can confidently architect correctly any system they encounter and execute that design.

Who Should Attend:

Any .NET architect, project lead or senior developer would benefit greatly from the clinic.

Course Outline:

Introduction to the IDesign Method

  • The IDesign Method
  • Service decomposition
  • Use cases analysis
  • ¦Assembly allocation
  • Run-time processes design
  • Identity management
  • Authentication
  • Authorization
  • Transaction flow
  • Synchronization

System 1

  • The interview thought process
  • System and business overview
  • Core use cases by the Master Architect
  • Service decomposition
  • Architecture diagrams
  • Presentation and review of teams design
  • School solution

System 2

  • System and business overview
  • Core use cases by the students
  • Service decomposition
  • Architecture diagrams
  • Presentation and review of teams design
  • School solution
  • Mid-week debriefing and assessmen

System 3

  • System and business overview
  • Core use cases by the students
  • Service decomposition
  • Architecture diagrams
  • Presentation and review of teams design
  • School solution

Project Plan Design

  • Designing a project plan for the architecture
  • Effort estimation techniques
  • Services dependency tree
  • Integration plan
  • Critical path analysis
  • Assigning resources
  • Scheduling activities
  • Analyzing shape of project plan
  • Changing architecture to accommodate plan
  • Feasibility
  • Reducing risk



arrow Register

Date & Location

 

http://www.haeckers-hotels.com/hotel-startseite-bad-ems-en.phtml

Häcker's Grand Hotel
Bad Ems, Germany

June 25-29, 2012
arrow Price and Register
Architecture Clinic

Shy is a Chief Cloud Architect with IDesign focusing on cloud computing, distributed systems, and software architecture. Shy was a Senior Program Manager at Microsoft, where he worked for 13 years on projects such as WCF, MSN, MSMQ, and Windows. Today Shy is a Microsoft MVP (Connected Systems) and a frequent presenter at technology conferences around the world. In addition to his consulting work for clients like Microsoft, HP and the US Government, Shy is closely involved with various product groups at Microsoft, and is often invited to participate in advisory boards and design reviews, helping Microsoft shape their future products.