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...
Thank you for visiting my blog. Having not posted any new content during 2024 I thought I would give a quick update. I have been busy working on Client engagements and developing our new Global Regulatory Directory (GRD) / Sanctions Portal ( www.kyc-data.com ). Having paused work on the Solutions Architecture Book – I plan to restart in 8 weeks and will be posting snippets throughout the development. Hopefully it should be out in draft and available towards the end of the year. Thanks for visiting and expect some new content soon
Let me start by apologising, as todays blog can be considered, by some , as content of little value to support macro EA views and a topic where information can be sourced easily via the web or by using AI tools (fast becoming everyday tools). However I felt I would share this reference type material, as error codes are always required for those building information systems. FYI recently I had to examine various http error codes used in a Cloud based API management system in respect of the flows of message exchanges and conduct analysis of non-typical scenarios e.g. a missing authentication token resulting in an invalid exchange between the backend and the API Gateway. Under normal operational conditions, interactions between two or more system will result in the exchange numerous codes which notify each system of task status e.g. a 200 return code will represents that all is well and allows the process continuation of further orchestration of a workflo...
Comments
Post a Comment