Week 8 - Future-State Architecture: Implementation Level (Part 2)

It's time to get your geek on!

(With your fellow IT peers)

     Detailed artifacts are necessary to convey your Future-State Architecture to your fellow Information Technology (IT) peers who are ultimately responsible to implement the solution.  All the countless hours architects spent discussing whether the Directory synchronization should be asynchronous or synchronous, pay off in the end, when you have a successful implementation.  If you don't take the time to "get into the weeds" with your IT heavyweights, you leave the implementation wide open for interpretation.

Figure 1 -  An example of a SharePoint one-way hybrid search architecture

     Share that same diagram with your business peers and you may end up with a endless amount of questions or worse, blank stares.  Once IT agrees to the overall implementation solution, I often create a high level implementation artifact so I can communicate our agreed approach to a broader audience.  The SharePoint Search diagram below is a perfect illustration on how you can simplify a similar message.

Figure 2 - SharePoint Search

     Be forewarned, outside of your IT bubble, this is what most people see when you get overly technical with your diagrams, spaghetti.

Figure 3 - Spaghetti Diagram

References:

Bray, S., P. C., & M. W. (2013, July 15). Microsoft SharePoint 2013 Designing and Architecting Solutions: Gathering Requirements. Retrieved October 16, 2016, from https://www.microsoftpressstore.com/articles/article.aspx?p=2224356

Ody, B. P. (2014, March 19). Untangle the system of system spaghetti. Retrieved October 16, 2016, from http://internetretailing.net/issue/beyond-channels-omnichannel-2014/untangle-the-system-spaghetti/

SharePoint Search. (2013). Retrieved October 16, 2016, from http://www.cairocodes.com/services/sharepoint/sharepoint-search