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...
It is essential for those charged with the support, management and delivery of technology capabilities for an organisation to be fully conversant with its Business Operating Model (BOM). BOMs, as one would expect, are not standard across industries. They evolve when the organisation transitions and develops as is the case in dynamic service-based industries, such as professional services, where organisations are constantly looking to repeat and generate new revenue streams. The current state of BOMs for professional service firms, although dynamic in nature, do exhibit mutual patterns across industries and using the global law firm example we highlight how capabilities across these firms are quite common . Law firms that have a global footprint can serve large global organisations that require advisory and legal services across multiple jurisdictions. The Business Operating Model (BOM) for the majority of the global law firms is quite unique, primarily due to specia...
I recently completed a short assignment, where my focus was to deliver a High-Level Design (HLD) document using the client's template, for an Enterprise Resource Planning (ERP) replacement/implementation project at the delivery stage of the project lifecycle. Before you ask - yes, this artefact was pushed 'down the road' to the delivery phase of the project and yes, this is not best practice - but that's material for another blog. Let's start by stating that a High-Level Design (HLD) document should NOT be confused with a Solution Design (SD) document, as both have purposes that provide specific lenses for their audiences, who require different views and level of detail. The HLD presents the high-level view for senior stakeholders ( business and technical ), who wish to understand the drivers for change, a view of the proposed system, its components, costs, and the resources required to achieve the desired outcome to name but a few. As one would expect the ...
Comments
Post a Comment