Enterprise Systems Architecture

  Today’s short blog, the first for 2024, derives from recent work in which I required a classic Table of Contents (TOC) for a Solution Design( SD ) Document/ Artefact. To create this TOC, I began by listing elements one would expect to see in the artefact i.e. primary section headers, which is challenging when you consider the ‘ purpose’ of the document, and  the target audience both of which impact the overall structure of the document. For most artefacts, it would be prudent to tailor the SD to meet the needs and challenges of the specific  problem. For example, a basic SD for a new in-house development may be very technical, especially when the target audience may be the Systems Community ( Developers, Testers, Service Management etc.) and resulting in an artefact with the content and focus on  Component Views(Building Module Blocks) , Deployment Views and the Runtime Operations .  So, when I considered the elements for the SD Artefact I wanted to create a generic TOC , on

Thank you for visiting the blog. I would like to start by posting a short message / comment regarding the horizon of content creation and blogging stemming from an interesting question I came across on another channel. Which asked, “ Why create new content when one can simply do a google search and retrieve examples or ask the Generative Pre-trained Transformer (ChatGPT) for a solution with some basic context?” The above is fast becoming a important question in today’s world of Generative AI and the wide array of search tools allowing one to simply ‘ rinse and repeat ’ other people’s work? A great comment which goes to the heart of content creation - For me using Generative AI Tools to create content could be classed as ‘cheating’ and like all cheats – they always get found out in the end. So as I start creating new content I will ensure it’s not ripped off and will always share the source of for any 3 rd party references  made    and I ask you do the same – If reusing any of