Scalability and uniqueness

What actually do we mean by ‘scalability’ in enterprise-architecture? What can and can’t we scale within the architecture, or the process of architecture itself? These questions came up for me in thinking about a comment by Dave Duggal to the previous

Requisite-fuzziness

How should we respond to inherent-uncertainty in qualitative-requirements, for enterprise-architecture and the like? Yes, we can reduce every qualitative-requirement to some sort of metric, but is that always a wise thing to do? And if not, how can we tell whether

Metrics for qualitative requirements

Just how should we handle qualitative requirements in system-design and enterprise-architecture? Should we, for example, reframe them into quantitative terms, as metrics – because it’s a lot easier to keep track of ‘measurable things’? Over the past couple of days

The craft of knowledge-work, the role of theory and the challenge of scale

If enterprise-architecture is a kind of craft – part art, part science – then how do we get it to scale? Is it even possible to get it to scale? – because if not, the whole enterprise of enterprise-architecture itself

Control, complex, chaotic

What exactly is ‘the chaotic’ in enterprise-architectures? How do we work with it, design for it rather than ‘against’ it? Yeah, I know this is a theme I’ve visited often here, but to me it’s a challenge that’s right at the core of