Ever wanted to understand (like in really understand) why Dexterity? or what are the reasons for a dictionary-based architecture? Ever wanted to gain an insight (as in real insight) on the philosophical principles behind Microsoft Dynamics GP? Well, I pulled out all the stops for this and went to the guy who drafted it all up and architected most of it.
Back in 1997, I was first introduced to Tim Brookins at the Certified Installation Specialists Conference held in Fargo, North Dakota. Tim presented an opening session describing the Microsoft Dynamics GP architectural foundations and later materialized this session into a whitepaper.
Tomorrow marks the begining of a 7-part series of articles based on Microsoft’s Tim Brookins whitepaper Great Plains Dynamics Architectural Foundations. In advance, I would like to thank Tim for allowing me to reproduce his whitepaper, which in my personal opinion, is one of the best I have ever read on the on the subject. At the end of the series, Tim will also contribute his thoughts around the paper and update you on his current role with the Microsoft organization.
At the time of the release of the whitepaper (1999), Tim Brookins was Chief Architect and Technical Fellow at Great Plains. He was responsible for the technical designs and architecture of Dynamics. His interests (at the time) included Windows NT, COM+, C++, Java, VBA, and Microsoft SQL Server — the picture on the article is also of him back in the days.
The following is the series schedule:
|Published Date||Featured Article|
|03/26/2010||Introduction – Dynamics Architectural Foundations|
|03/29/2010||Built to Last|
|03/31/2010||Built to Grow|
|04/02/2010||Built to Leverage|
|04/05/2010||Built to Fit|
|04/09/2010||Series Insight – Featuring Tim Brookins|
Links to each article will available on the publishing date.
Until next post!
Mariano Gomez, MVP
Maximum Global Business, LLC