Five EA app ideas – anyone interested?

This is another follow-on to the earlier post ‘Helping others make sense of my work’ – this time about how to bring all of this to a wider audience and market, and help bring ‘whole-enterprise architecture’ ideas into more general use.

If you’ve been around this weblog for a while, you’ve probably noticed I tend to churn out ideas for tools for whole-enterprise-architecture. That’s what I am, really – a toolmaker, a maker of conceptual tools.

Some of those ideas for tools, I’ll have to admit, have pretty much gone nowhere. Others, though, have gained a fair bit of attention and interest. A few have so far made it out into book-form, and look like going a lot further.

But what I really want to do is re-work all of the best ideas into apps – tools that can be used online or offline, on any part of the EA toolset-ecosystem, from smartphones to tablets to laptops to desktops to ‘proper’ repository-based EA-toolsets.

The practical catch is that I’m long out of date as a software-developer, and at present I don’t have access to investment funds to pay someone else to do it.

So I’m looking for partners to work with me in developing these apps.

I firmly believe that if we get it right, there’s a huge potential market for several of these app-ideas, and at present there’s little or nothing out there to serve that need. And the first developer who fully ‘gets’ what I’ve been struggling to explain here on this weblog over the past few years is going to gain a market-position that should establish them for many years to come. So, your choice, folks: anyone interested?

I’ll quickly outline below the five ideas that I think are the most ready to be implemented as apps:

• SCAN sensemaking-framework
• Context-space mapping sensemaking-method
• ‘This’ exploratory game for service-oriented enterprise-architectures
• Enterprise Canvas for modelling service-oriented enterprise-architectures
• SEMPER diagnostic and intervention-design for organisational ‘ability to do work’

For each app-idea, I’ll summarise:

• why and how this app will help
• what the app would do
• what it would look like
• existing apps which include some aspects of this
• how this links with broader EA-tools context
• probable market (and hence potential revenue)
• probable complexity / difficulty for development (and hence potential cost)
• current development-status
• posts and other sources for further information on this prospect
• other notes (if any)

For the right person, or the right team, there really is a huge opportunity here that’s too good to miss…

Read on, anyway: and if you’re interested in any of this, or know someone else who might be, please get in touch with me as soon as possible. Thanks!

App idea 1: SCAN sensemaking framework

Why and how this app would help: This app would support people in practical sensemaking at work, much like SWOT (Strengths, Weaknesses, Opportunities, Threats) does for basic strategy and tactics. The focus is always on helping the user to make meaningful decisions in uncertain circumstances at ‘business-speed’.

What this app would do: The app would present the SCAN core-graphic, and allow people to build a quick ‘story’ of their current context, using the core-graphic as a guideline and checklist. The ‘story’ would point to different approaches, and clarify trade-offs and the risks and opportunities of particular approaches.

Using the app, the user will, for example, be able to:

• start a session – “let’s do a quick SCAN on this” – by typing or recording a brief intro to describe the context
• record text, voice, photo and video (dependent on device-capabilities), such as via attaching ‘post-it’ tags, audio-recordings and suchlike
• ‘drill-down’ into each of the segments (‘domains’) of the core-graphic, and apply the same method recursively to each ‘domain’
• ‘replay’ all or any part of the current session or previous sessions
• synchronise and/or store a SCAN from a small device (smartphone, tablet) onto a larger device (laptop, desktop)
• export reports of SCANs

What this app would look like: The app would be centred around the SCAN core-graphic:

The user would be able to attach ‘post-its’ and other tags to ‘domains’ (defined regions on the core-graphic), to act as reminders or to carry notes and memos of the sensemaking exploration.

The reverse of this main page (and of individual ‘domains’) would include explanatory text of what each ‘domain’ means in practice, how it’s used, and where the various choices lead.

Other pages would include session-details, and lists of previous sessions.

Existing apps: I envisaged this as a cross between a note-taker app [for text-notes], an audio-memo app (see AudioNote for iPhone/iPad) [for audio-notes, text-notes and ‘replay] and a fixed-frame sensemaking structure (see BMTBox for iPad, the ‘official’ app for Business Model Canvas) [for ‘post-its’, tagging and session-based descriptions].

Broader context: This app should feed into the general EA-toolset ecosystem, such that SCAN sessions can be attached to models, or have models derived from SCAN sessions.

Probable market: The potential market for a smartphone version of this app could be enormous, across every possible industry or context – especially if SCAN becomes as ubiquitous as SWOT, for which it does have the potential to be. The market for a web-based app would probably be rather smaller, but still significant. It would need to be low-priced, and very quick to use and re-access. Establishing the market may take some time, but could take off virally if used / recommended by key figures in an industry.

Probable development issues: This should be straightforward, though very high quality user-experience and workflow will be absolutely critical to success. For iPhone/iPad, the main part of the app is only about five ‘pages’, with perhaps 10 ‘pages’ more of ancillary information, selection-lists, text-entry and so on. The audio-record/playback functions are built-in for most smartphones and tablets.

Current status: Preliminary storyboards, workflows and wireframes are under development at present. The basic concepts, workflows and usage-scenarios have been and are still being documented in various blog-posts (see ‘Further information’ below).

Further information:

• “Let’s do a quick SCAN on this”
• Using SCAN: some quick examples
• On SCAN, PDCA, OODA and the acronym-soup
• Domains and dimensions in SCAN
• Comparing SCAN and Cynefin

Other notes: (See ‘Other notes’ for ‘Context-space mapping’ app.)

App idea 2: Context-space mapping sensemaking-method

Why and how this app would help: This is another app for sensemaking in an uncertain context, but aimed more at enterprise-architects, strategists, futurists and other conceptual-level consultants. It’s likely to be used in a shared environment (cafe-conversation, brainstorming-meeting etc) as well as in solo use.

Context-space mapping uses a selected ‘base-map’ to as a guide and checklist for sensemaking in a context, much as for SCAN. However, unlike SCAN, other ‘cross-maps’ can be overlaid on the base-map to trigger different perspectives: in some cases these cross-maps will intentionally cause mismatch, to force alternate and often-unexpected ways of thinking about a context.

(SCAN is actually a simplified form of context-space mapping, optimised for rapid use under real-time pressure; this is the full generic version, allowing more options but typically taking more time to do.)

What this app would do: The app would be an extended version of the SCAN app, and should be able to do everything that the SCAN app would do (e.g. session-creation and review, tagging, text- and audio-memos, reports etc). In addition, the user should also be able to:

• select a ‘base-map’ graphic from a list of base-map types (rather than the single fixed based-map used in SCAN), and apply tags, memos etc to ‘domains’ on that base-map
• given a base-map, select from a list of compatible ‘cross-map’ overlays, and apply tags, memos etc to ‘domains’ created by the cross-map

What this app would look like: This would look much the same as for the SCAN app. The main addition would be selectors for base-maps and cross-maps – both graphic-format (as ‘cards’) and list-format.

Existing apps: I envisaged this as a combination of text/audio etc note-taking (e.g. AudioNote for iPhone/iPad) and fixed-frame sensemaking (BMTBox for iPad, SWOT for iPad), plus something like Gamestorming for the iPhone (for its use of ‘cards’ to represent models or processes).

Broader context: As for the SCAN app, this should fit in with the broader EA toolset. Also, assuming that a library of base-maps is developed – possibly or even probably by the user-community – it can also fit in with and support all kinds of general business-sensemaking that uses a static base-map and optional overlays: e.g. Porter Value Chain, SWOT, Galbraith Star, Five Element, Kotter Eight Phases etc. (For other examples see e.g. van Assen, van den Berg & Pietersma, Key Management Models, FT/PrenticeHall.)

Probable market: The basic market is a subset of that for SCAN – i.e. EA specialists and consultants. However, if support for an extensible library is added, the market could be huge – essentially everyone who needs to do any kind of business-sensemaking.

Probable development issues: This is best understood as an extension of the SCAN app (or rather, that the SCAN app is a subset of this). The main additions are:

• graphic selectors (‘cards’) for base-maps and for cross-map overlays for the current base-map
• text-list selectors for same
• zoom and horizontal/vertical scroll (some base-maps will be too large to make sense in one go, especially on smaller devices)

To allow for zooming, graphics will probably be best stored in vector format (e.g. SVG) rather than as bitmaps. (This would also make it easier to maintain the exchangeable data-format in text-only form.)

Current status: As for the SCAN app, preliminary storyboards, workflows and wireframes are under development at present. The basic concepts, workflows and usage-scenarios have been and are still being documented in various blog-posts (see ‘Further information’ below).

Further information:

• Book ‘Everyday Enterprise Architecture: sensemaking, strategy, structures and solutions‘ (complete book in free-download e-book)
• Context-space mapping and enterprise-architecture
• Context-space mapping with the Enterprise Canvas
• Context-space mapping with Enterprise Canvas, Part 2: Business-context
• Context-space mapping with Enterprise Canvas, Part 3: Value-proposition
• Context-space mapping with Enterprise Canvas, Part 4: Rethinking vision bottom-up
• Context-space mapping with Enterprise Canvas, Part 5: Service content
• On business-rules (worked-example with business-rules)
• Standing up for the value of our work (worked example with Cynefin framework)
• Causal Layered Analysis, SCCC and Cynefin (worked-example with Causal Layered Analysis)

Other notes: One option that would greatly add to the market would be to present the SCAN app as the extensible base for this larger-scope app. Offer the SCAN app as a very low cost ($2-3) or even ‘free’ app, and add other models via in-app purchase or via subscription to a web-based library. (Proprietary models could be included into the library on a royalty basis.) The extended features for context-space mapping become available as soon as the first extension is downloaded; further models become visible as new ‘cards’ or text-items in the selector-lists.

App idea 3: ‘This’-game for context-exploration

Why and how this app would help: One of the practical problems in requirements-elicitation (and modelling in general) is knowing where to start. The ‘This’ game bypasses the problem by supporting a ‘start anywhere’ principle – everything connects with everything else, so it doesn’t matter where we start. The broader meaning and central themes within the context emerge from the exploration, rather than having to be predefined (possibly incorrectly) from the start.

A key point in requirements-elicitation, which this app would help to emphasise, is that often the most important information and ideas arise from the conversation around a topic, rather than from the specific questions themselves.

What this app would do: The app presents questions about the current focus within the context – i.e. ‘This’ – and records the answers to those questions as text, audio, video, photo (e.g. of a whiteboard) and perhaps also sketch-diagrams. The questions can be presented in structured sequences (checklists), by manual selection from a list, or at random.

Some of the questions allow us to change the current focus (the ‘This’) to a related item, enabling us to expand the overall scope of the game.

The context can also display a graphic model of the context, in simplified Enterprise Canvas notation (see app-idea #4). The model is generated from the information collected to date, and is non-editable, but can be used to select a different ‘This’ within the current scope.

The app maintains a list of ‘This’-game sessions, and allows us to create a new session, review or edit an existing session, or delete a session. We can also export a session to another compatible system, such as a toolset for modelling with Enterprise Canvas.

What this app would look like: The core of the ‘game’ is a set of questions and supporting information, typically each presented in a format much like a playing-card:

Options to add responses to the question would be arranged around the ‘card’, with existing responses accessed either via a scrolling list ‘below’ the card, or on the ‘reverse’ of the card. Other administrative options – view session-details, select another question, export, etc – would also be arranged around the ‘card’, together with any context-specific options such as to move to or create a new ‘This’ focus-point.

Lists in graphic or text-format would be displayed as per the usual format for the respective device and user-interface paradigm.

Existing apps: Much as for the SCAN and Context-space mapping apps. The ‘card’ concept can be seen in the Gamestorming app; the zoomable/scrollable display could be much as per the Prezi web-based presentation-app.

Broader context: This will definitely need to link in to the EA-toolset ecosystem, as it will be a primary information-source for EA-toolset content. It could also be used as a method for review of EA-toolset content.

Probable market: Anyone involved in the broader enterprise-architecture context, including conventional (IT-oriented) ‘enterprise’-architecture, process- and service-design, value-network review, business-model implementation, and general review and troubleshooting in a wide variety of business contexts.

Probable development issues: Structurally this would be similar to the Context-space mapping app (app-idea #2), and could probably be built on top of the same underlying ‘engine’.

Compared to the Context-space mapping app-idea, the main differences are the ‘card’-selection mechanisms, and that the display is not editable as such: because the ‘card’ can be re-used many times even within the same session, responses would be added to a list, rather than ‘dragged’ onto the card-graphic. See the Gamestorming app for idea for ‘card’-selection.

Current status: Again, preliminary storyboards, workflows and wireframes are under development at present. The basic concepts, workflows and usage-scenarios have been and are still being documented in various blog-posts (see ‘Further information’ below).

Further information:

• This: an exploratory game for service-oriented EA
• More on the ‘This’ game for enterprise-architecture
• The ‘This’ game and EA toolsets

Other notes: So far I’ve done very little work on ‘gamification’ as such: it’s described as a ‘game’ only in the sense that ‘cards’ could be selected at random, rather than always as predefined lists. Some people have come up with possible suggestions for ‘gamification’ – see the ‘More on the ‘This’ game’ post – but it’s an avenue that may need further exploration.

App idea 4: Enterprise Canvas architecture-modelling

Why and how this app would help: One of the major problems in current enterprise-architecture is the way in which the many different model-types fragment the overall space into narrow subsets, often with no means to link between them. (Archimate is one of the few model-types that attempts to bridge across domains, but at present only in relation to IT.)

Enterprise Canvas resolves this by using a completely consistent service-oriented approach that applies to every part of the enterprise context, at every level, using the same small set of entity-types across the whole space, which can later be ‘translated’ into the other context-specific model-types.

This app provides a means to model or review any aspect of the business, at any level, that can be described in service-oriented terms.

What this app would do: This app provides a space to develop and review context-models of an aspect of an enterprise-architecture, based on the simplified Enterprise Canvas notation. On small devices (e.g. smartphones, small tablets) the emphasis would be on review, because the ‘screen real-estate’ would be too small for practical modelling; however, full modelling should be possible from mid-size tablets (7-inch? 10-inch?) upwards.

An extended version of the app should also allow comparison, cross-link and merge of models, to build a larger-scope model. This would then feed into a full EA-toolset (see ‘Bonus app’ below).

What this app would look like: On a small device, the app would allow:

• select from a list of models
• create a new model (including description of model-context etc)
• download a model for review
• upload/sync models that have been created or reviewed
• review by adding ‘wiki-like’ comments to existing entries

The display would be much as per the app-idea for the ‘This’-game: a zoomable/scrollable graphic that can also be used to select entities for review, and a ‘scrolling card’ display for the contents and comments for the entity itself.

On a larger device, the app would also allow creation and editing of graphic models, using the small palette of entities in the simplified Enterprise Canvas notation (two main entities, two subsidiary entities, three relation-types – see the ‘Simplifying the Enterprise Canvas’ post).

The larger screen would also allow using a sketch or image (such as a photo of a Business Model Canvas on a whiteboard) as a backplane on top of which to develop a model. (See the post ‘Enterprise Canvas as service-viability checklist’ for a cross-map between Business Model Canvas and the standard-layout Enterprise Canvas shown in simplified-notation above.)

Existing apps: For smaller devices, see the ‘Existing apps’ summary for the ‘This’-game app-idea above. For larger devices, see any graphic-modelling tool for UML, BPMN or any other similar notation: example tools include Visio, Archi, BizzDesign, Sparx Enterprise Architect etc.

Broader context: This app should be able to import sessions from the ‘This’-game app, and potentially re-export to the ‘This’-game app. It should also be able to exchange with a full EA-toolset that can convert between Enterprise Canvas and other model-types such as Archimate, BPMN and UML.

Probable market: The initial market is enterprise-architects and others who need to be able to model any part of an enterprise. This initial market is quite small, and depends on awareness of a need for whole-enterprise scope (rather than an IT-centric scope, as in most current ‘enterprise’-architecture).

However, as Enterprise Canvas becomes better known as a means to link across disparate model-types, the market is likely to grow radically, especially if an app is available right down to the tablet or smartphone level, where it can be used for information-capture, review and problem-resolution on-site.

Probable development issues: For the smaller-device implementations or for web-implementation, development could be based on the ‘This’-game app, without the need for the ‘card’-questions, but with an active rather than passive graphic display. In other words, it will be necessary to be able to drag-and-drop entities onto the workspace; to draw flow-links and other relation-links between entities; and to open, edit and review property-sheets associated with entities and flows. This is supported by HTML5 ‘canvas’, for example, but is likely to require more development-effort than for a passive graphic-display.

A standalone app could be based directly on the open-source Archi toolset for Archimate. (The simplified Enterprise Canvas notation is, by design, a UML-compatible subset of the Archimate notation, with a somewhat different structure and content for its property-sheets.)

Development of an appropriate file-format will be crucial to the success of this app. It must be public domain, extensible, and (as far as practicable) compatible with other standards in the EA, process-architecture and software-architecture space: the XMI format is a probable good candidate for a starting-point for such development.

Current status: Once again, preliminary storyboards, workflows and wireframes are under development at present. The Enterprise Canvas notation is fully specified in various blog-posts (see ‘Further information’ below). Further ideas for workflow, structure and user-experience can be adapted directly from Archi and other existing toolsets in the EA-modelling space.

Further information:

• Simplifying the Enterprise Canvas
• More on simplified Enterprise Canvas
• Enterprise Canvas as service-viability checklist
• Book ‘Mapping the enterprise: modelling the enterprise as services with the Enterprise Canvas‘
• Reference-sheet for ‘Mapping the enterprise‘ (Enterprise Canvas)

Other notes: (n/a).

App idea 5: SEMPER diagnostic

Why and how this app would help: The physics definition of ‘power’ approximates to ‘the ability to do work’; in many social contexts, though, the effective definition is often closer to ‘the ability to avoid work’. Therein lie many problems for organisations, who definitely do want work to happen… This app provides a simple, unthreatening means to identify and measure the ‘ability to do work’ within a given context, and, via a cross-map, suggest appropriate techniques for intervention.

What this app would do: The diagnostic works somewhat like a more structured version of the ‘This’-game, presenting a set of questions for each section of each ‘domain’. (In the SEMPER-5 model, there are 5×5 questions; in the SEMPER-11 model, which is more for experienced consultants, there are 5×10 +1 questions.) In general, the app would use predefined sets of questions, which can be defined externally and uploaded to the app, but also potentially also edited within the app if required.

To start with, the user would define the context for a session. It should be possible to link sessions together into groups, so as to do statistical evaluations such as 360degree-view, vertical-slice view or comparison of executive versus front-line view.

To answer each question, the user picks an option from two pull-down lists (in effect, the ‘ability to do work’ score, and any trend upward or downward), and optionally enters a comment. In principle, the questions can be answered in any order, though it would be more usual to do them in sequence.

The results are shown in tabular or ‘dashboard’ format, with or without trends.

The results can be exported in appropriate form such as CSV for statistical-analysis on spreadsheet.

What this app would look like: Defining a new session, reviewing a previous session, running the diagnostic itself, and export/re-import, would all quite similar to that for the ‘This’ game.

A ‘dashboard’ display would be much as above, though probably simplified for a small-device.

Existing apps: A complete demonstrator, implemented in PHP/MySQL, already exists, as shown on the SEMPER Metrics website. This is also available as a ‘Portable App’, to run direct from a USB thumb-drive or SD card, complete with its own web-server. For smaller devices, see the descriptions for the ‘This’-game.

Broader context: This is largely a standalone app, but could be integrated into a larger EA toolset or equivalent as appropriate.

Probable market: This is likely to be a somewhat specialist tool, primarily for organisational consultants and enterprise-architects. Even so, it does have quite a broad potential market, as the need (if perhaps not always the want) for this will be evident within every medium- to large-sized organisation or enterprise.

Probable development issues: A demonstrator already exists, incorporating all of the functionality described above, although it’s likely that it will need a complete re-implementation even for a web-based app. Structurally it is quite simple, using only a handful of database tables and very straightforward business-logic. A portable version could be based on the ‘This’-game app.

Current status: A complete demonstrator already exists, together with full design-documentation. The formal theory and structure of the SEMPER diagnostic is described on the SEMPER Metrics website and, in more detail, in the book SEMPER & SCORE; the latter also includes paper-based versions of the diagnostics.

Further information:

• Book ‘SEMPER & SCORE: enhancing enterprise effectiveness’ (key chapters are in free-download e-book)
• SEMPER Metrics website (reference and demonstrator)

Other notes: (n/a).

Bonus rather-more-than-an-app idea: full EA toolset

This final item is a lot more than a simple app: it’s a complete commercial-grade toolset to cover the entire scope of enterprise-architecture. Without it, we’re stuck with the limitations of the existing ‘EA’-toolsets, many of which are so constrained in their scope, and often so IT-centric that – to be blunt – they’re almost worse than useless for doing any kind of real enterprise-architecture.

It’s a big challenge: but the first team who actually ‘gets’ this really will dominate the toolset-space for the upcoming enterprise-architecture market. And that’ll be huge, because it has to sort out everything that currently doesn’t work in the entire economic model typically described as ‘business as usual’ – which, to again be blunt, is just about everything in ‘business as usual’.

So yes, big challenge, huge opportunity, waiting there for the first person to ‘get’ it: I just wish someone would… Will it be you?

Anyway, quick summary follows.

Why and how this toolset would help: Most of the existing EA toolsets support only a small subset of the myriad of model-notations and model-types currently fragmenting across the EA space. Most of these toolsets are strictly IT-focussed, and are simply not usable for anything that does not centre around or at least focus on an IT-oriented implementation. It is almost impossible to use these toolsets to cover the full whole-enterprise space, and those few that do have no means to link across all the different notations.

The aim of this toolset is to provide a consistent means to link across the entire space, to develop and support a ‘holographic’ model of the enterprise that can be described from any required viewpoint using any appropriate notation.

This would be a professional-level tool, used primarily by enterprise-architects, process- and service-designers, organisational-change specialists and the like. It will probably be implemented only for mid-range systems and above, from laptops (single-user) to desktops (multi-user). Because of the necessity for significant amounts of ‘screen real-estate’ or equivalent, it is unlikely to be available on small devices.

What this toolset would do: The toolset is based on a ‘universal’ metametamodel, which allows entities, relations and model-types to be described in a consistent, notation-agnostic way. Notations themselves are described in terms of the metametamodel, allowing consistent re-use of the same nominal entities in different notations and model-types.

Models can then be developed in the usual way, much as with any other existing EA toolset, and with entities stored in a local or shared repository as required. The toolset must also support import and export in a standardised notation-agnostic file-format, enabling sharing of models between different toolsets, and also with other compatible apps such as the ‘This’-game and the notation-specific Enterprise Canvas app.

What this toolset would look like: On the surface, it is likely that this toolset would look much like any existing EA-toolset, with multiple panes to access palettes for different notations, filtered subsets of existing entities in the repository, and so on.

Existing toolsets: A huge range to choose from, such as Archi or Aris Express at the single-user level, Sparx Enterprise Architect or Bizzdesign at the basic-repository level, mid-level systems such as Mega or Casewise (or, more IT-oriented, planningIT or alfabet), and ‘big-systems’ such as Aris, Troux or IBM System Architect.

Broader context: The toolset needs to be able to import and share with most of the apps above, especially the ‘This’-game and the Enterprise Canvas app. It also needs to be able to share models with many other toolsets, though this may be constrained by limitations of those other toolsets.

Probable market: The market for EA toolsets is specialist, but large – estimated in the low hundreds of millions of dollars per year. Most of this income is for high-end toolsets such as Troux or IBM System Architect, for which some configurations can be priced well into the tens of thousands of dollars per seat; but even low-end toolsets such as Sparx Enterprise Architect, which is priced in the low hundreds of dollars, do still sell many thousands of user-licenses overall.

To me, it would seem best to provide a range of offerings, from a high-end enterprise-wide repository with support-services that would genuinely justify a high per-seat license-fee (which, bluntly, cannot be said for some of the current toolsets), all the way down to a simple single-user system – still fully file-compatible with the high-end system, but with a simple local repository and reduced functionality – at a much lower price, or even available free. A ‘freemium’ structure would also help to create and extend the overall market.

Probable development issues: This would not be a simple development; nor would it be cheap, in terms of time at least. A good approach might be to start from some of the existing open-source toolsets such as Archi or Essential, and rework the underlying mechanisms to align with the notation-agnostic metametamodel, whilst still keeping the surface functionality essentially unchanged.

Current status: A lot of work has been done on ideas for a notation-agnostic metametamodel, and how that could be used to underpin multi-notation enterprise-modelling and information-exchange – see the ‘Further information’ section below for more details. Many of the workflows and wireframes can be based on or adapted from existing EA-toolsets, though the opportunity also exists for a complete rethink, more in line with the ‘holographic’ nature of the overall enterprise-model maintained by the toolset.

Further information:

• Enabling enterprise-architecture conversations
• Scenarios in ‘The ‘This’-game and EA toolsets‘
• Next-generation toolsets for EA
• The toolset-ecosystem
• More on that enterprise-architecture ‘help needed’
• Enterprise-architecture? – it’s all about story
• Back to the roots for EA toolset metamodels
• EA metamodel: two questions
• EA metamodel – the big picture (and the small picture too)
• What’s the point of this EA metamodel?
• Dependency and resilience in enterprise-architecture models
• More detail on EA metamodel
• Meanderings on metamodels
• More metamodel stuff
• Wiki on metamodels and structure for Open Source EA Toolset

Other notes: (n/a).

Nothing more to add for now: over to you for comments, if you would?