As an Enterprise Architect, whether you are getting ready for the VCDX Design Scenario portion of your VCDX defence or improving your “on the fly” consulting skills in client meetings, it makes a lot of sense to have a standard set of “Go-To” logical design templates that you can rely
As Enterprise Architects we instinctively understand the purpose of the Conceptual Model (Requirements, Constraints and Assumptions) and the Physical Design (Vendor XYZ, Product A with setting B). Unfortunately, the Logical Design is something most architects struggle with, because it is abstract and theoretical. This is very common with Enterprise Architects
One of the requirements for the VCDX submission is a set of Logical and Physical Design Blueprints. As the name suggests, the Blueprint collates all of the pertinent information from each technology silo of the Architecture Design into one document. I have heard of candidates not using a separate set
One of the biggest challenges with developing your design is checking and measuring how closely your Logical and Physical Design decisions have aligned with the Customer’s Business Requirements. This is one of the reasons why it is worth starting your design from a blank sheet of paper and ignore any
After two attempts, 12+ months and 1,000+ hours of effort, I finally achieved the VCDX5-DCV certification (#133) in Frimley 2014. Thank you to all that supported me, particularly my wife and kids.