The Residual World::Tag = 'Artefact'
Entries that have been tagged with 'Artefact'.-
by Nic Plum on Saturday 27 February, 2010 - 16:24 GMT
Choosing stereotypes for an enterprise architecture framework isn’t easy. In defining something you embed the prevailing view at the time the framework was created. This may later haunt you. With every extra stereotype you add choice and then when you add the poor old architect or modeller into the mix you increase the possibility of inconsistency - the very thing the metamodel is designed to constrain and eliminate. This is illustrated very nicely in trying to place ’System’ at the centre of TRAK.
Since we started with MODAF 1.2 this is where the story begins.
In the MODAF System is defined as
The usage of an artefact as a System in a Capability Configuration
and part of the physical architecture.
Technically it is defined as an Artefact alongside Platform. This arose because when the MODAF was originally launched the consensus on what a system is wasn’t the currently accepted one with emergence et al and the MODAF quite reasonably took the then accepted view - hence it is a purely man-made thing. No notion of complexity whatsoever.
From the The MODAF System Viewpoint(SV) (17th February 2009):
‘Artefacts - Physical objects made for a purpose (e.g. system, sub-system, platform, component or any physical item that occupies space and has attributes)’
‘Physical Architectures - Configurations of resources for a purpose (e.g. capability configurations)’
‘The physical resources contributing to a capability must either be an organisational resource or a physical asset. That is, a system cannot contribute alone; it must be hosted on a physical asset used by an organisational resource of both. Organisational aspects (e.g. who uses a system) can now be shown on SV-1.’
In short as it is defined in MODAF 1.2:
- system is something physical
- it is man-made
- it can’t contain anything else like Organisation, Post or Role, or Software
- it is not the same thing as a Capability Configuration
- systems cannot provide capability
When creating TRAK we found we couldn’t use MODAF::System as it didn’t fit with either the London Underground view of a system or the INCOSE or ISO ones.
The current INCOSE Systems Engineering Handbook defines a system as:
‘an integrated set of elements, subsystems, or assemblies that accomplish a defined objective. These elements include products (hardware, software, firmware), processes, people, information, techniques, facilities, services, and other support elements.’
It was therefore impossible to use MODAF::System to represent what is currently accepted to be a system. So what could we use? As a system is a mixture of hard and soft resources it made sense to position at the centre of TRAK:
Immediately therefore this allows us to describe systems
- composed of a mixture of equipment, software and people - not just physical
- composed of just software or of just human stuff - soft systems
and we don’t need ‘Sub-system’ either or ’System of Systems’ since the terms just reflect a point of view in the hierarchy of systems and we already have the construct ‘System is configured with System’ to allow us to represent systems at any level. In fact if we introduced sub-system we would be forcing architects to make a choice and with choice comes difference of opinion and the potential for inconsistency - my Sub-system might be your System and so on.
Now Add People
The choice of metamodel elements is important, particularly when you add people (users of the metamodel) into the mix.
Some of you will be looking at the TRAK metamodel fragment above and thinking ... Capability Configuration. Indeed in MODAF this is where Capability Configuration sits. So is Capability Configuration correct? As defined it cannot be - Capability Configuration is still part of the Physical Architecture.
The bigger problem, however, is that you end up using one element but with the meaning of another. It’s easy to see how this might arise - being not allowed to add parts to MODAF::System the architect takes the stereotype that does allow him or her to add the stereotypes that they want - the Capability Configuration. It is possible that they don’t even see the problem in doing so. The trouble is that they describe something as a system but use Capability Configuration. Their ‘head-model’ doesn’t fit the meaning of the model elements used.
It is actually worse because in providing MODAF::Platform and MODAF::System there is a choice to be made - when is something a platform and when is it a system? You can almost guarantee that different choices will be made and therefore it makes it more likely that architecture descriptions (models) can’t be ported between organisations. In fact the poor modeller has 3 stereotypes that can be used to mean ’system’ (in their head) - the MODAF::Capability Configuration, MODAF::System and MODAF::Platform. On the receiving end you can’t predict which will have been used.
This is why in TRAK there is only 1 TRAK::System. It’s flexible, can be used for hard or soft systems and, importantly, ‘there shall only be one’ - no sub, super or whatever-system.
You describe the context simply by the system boundary and hierarchy. Easy.
After all a system is a system.
The MODAF is Crown Copyright/MOD
The TRAK Metamodel is released under the GNU Free Documentation License.
- Solution Risk, Vulnerability, Threat and Mitigation - Does Risk Need to be Separate from Event? (21% )
- Definitions - What Exactly is a Risk Part 2? (14% )
- Just When You Thought It Was Safe - EntiTy Returns (7% )
- What Would a TRAK View Look Like in a Graph Database? Part 1 (7% )
- MODAF is Dead - Long Live ‘NAF’? (7% )