Software Design Training : nTier Training

Software Design Training: Applied Object Oriented Programming and Architecture

nTier's Applied Object Oriented Programming and Architecture course is an intense, customizable 2-3 week "boot camp". This is where we bring language syntax, UML, OO Principles and Practices, Design Patterns (J2EE and GoF), Agile Programming, and the best industry practices together in one course that will show you how to write well designed, reusable code that truly harnesses the power that OO promises.

The course starts out with several days of traditional 50% lecture, 50% lab format to ensure that every student is adequately prepared for their boot camp experience. The real challenge follows as students are given a true-to-life assignment that must be coded, tested and reviewed by both peers and instructors (typically two full time instructors are present for the entire boot camp). The coding assignment is done in an iterative fashion that gradually increases in difficulty as we guide students repetitively through the steps of gathering requirements, designing, coding, refactoring and testing.The boot camp section of the class is 20% lecture/coaching and 80% building software in small, self-organized teams.

Two key focus areas are "Principle Driven Development" and "Being a Chef Not A Cook" (cooks just follow receipes, chef's understand the science and principles behind what they are doing).

Topics Covered (customizable):

Agile Programming and Scrum &emdash; Create your own religion
UML &emdash; Use Cases, Class and Sequence Diagrams Sign language for geeks
OO Programming &emdash; Magic or Science?
Abstract Class and Interfaces &emdash; The beauty of incompleteness
OO Precepts and First Principles &emdash; Even people over 40 can do this
The OO Equation &emdash; Understanding P cubed
MVC for the real world &emdash; Applications have layers
Analyzing Commonality and Variability &emdash; Abandon spiritual programming
Change Happens &emdash; Giving up hope and telling smaller lies
Strategy Pattern &emdash; Rules fear me
Composition and Delegation &emdash; When in doubt, delegate
The Open/Closed Principle &emdash; Surgery is always major
Factories &emdash; Instantiation for Dummies
Decorator Pattern &emdash; When bi-polar objects are good
Template Method Pattern &emdash; I say when, you say how
TDD and other contagious practices
Refactoring &emdash; clean as you go
Front Controller &emdash; Gate-keeping made easy
Command Pattern &emdash; Do what I say
Business Delegates &emdash; Coarser is better
Documentation &emdash; It cant be this easy
Requirements Traceability &emdash; Did we get it right?
Software and Total Cost of Ownership &emdash; Show them the money!