7 years, 29 days ago

Identify Indirect Stakeholders with System Context Diagrams

A Systems Flow consultant has skills that tend to fall in the triangle of technical, business and organizational excellence. One common and repetitive case of project dysfunction where this overlap brings real benefits is that of the “Operational Business Stakeholders Missing from Business Requirements.” Here’s how it usually goes: Architect is engaged to design project’s solution architecture […]

7 years, 4 months ago

Documenting Design Decisions

We previously discussed Options Analysis – our method for evaluating multiple viable technical solutions.  We also facilitate numerous smaller design choices at all levels of the architecture.  We often need to document these as “design decisions,” and use a common approach and format to document at all levels of design (conceptual, logical, physical, component, etc.). […]

7 years, 5 months ago

Prose: Great for Novels, Lousy for Solution Design

While we often find ourselves advocating for design documentation, we typically are referring to “some” design documentation vs. “more” design documentation.  When it comes to design documentation, more is actually not better.  We have encountered customers, and even other consulting firms, that deliver design documentation by the inch – measuring design quality horizontally across the […]

8 years, 1 month ago

The System Context Diagram

We use a system context diagram in the early stages of our Investigative Architecture™ process. It provides a high level functional view of a system and, while it is very powerful for the early stages of functional design, it also ensures you have identified any functional needs that impact the non-functional, or architectural, aspects of […]