Site

RW - Navigation

RW - Recent

Last 10 entries [comments]:

Forums

Last 10 posts [threads/views]:

Wiki

Last 10 pages updated:

There are 484 wiki pages in total.



RSS logoRSS Feed
 

The Residual World::Tag = 'Sos'

Entries that have been tagged with 'Sos'.-

A MODAF Architecture Description Only Applies to a ‘System of Systems’?

by Nic Plum on Thursday 22 September, 2011 - 12:29 GMT

Posted in Architecture FrameworkMODAF

Tags: 1.2.004architecture descriptiondefinitionm3sossystem of systems

In the MODAF metamodel (M3) v 1.2.004 we have:

ArchitecturalDescription : public <<stereotype>> class

A specification of a system of systems at a technical level which also provides the business context for the system of systems.

This definition of an architecture description has been unchanged since at least v 1.1 (May 2007).

This defines an AD as a specification. This is too restrictive and doesn’t fit current usage within the MoD since MODAF ADs are more often used to discover and analyse the architecture that exists in order to assess the impact of decisions or proposed design changes.

The real problem is the ‘system of systems’ bit because it looks to be misusing the term. In restricting an AD to a ‘system of systems’ and not ‘system’:

     
  • Are they then saying it is only an AD when it describes a ‘system of systems’? Since a ‘system of systems’ is formed from systems that have an independent existance this definition means that you can’t have a MODAF AD of a submarine where the systems are tightly coupled and have no meaningful existence away from the submarine.
  •  
  • Are they saying MODAF cannot be used to describe a vanilla system? This states that a description of the architecture of a system (formed from essential parts that aren’t themselves systems) isn’t an AD.
  •  
  • Are they saying that ‘system of systems’ is a new type (in which case how do they know it can be described using MODAF)? This would be technically incorrect since a ‘system of systems’ is of the type ‘system’ with the emergence et al that this brings.

I don’t for one minute believe that any of this is the intent nor that this represents how MODAF ADs are intended to be used. It doesn’t therefore reflect the real use of an AD and needs to be changed to make it a valid definition.

The good thing is that the MODAF M3 recognises the distinction between the architecture (of the system) and the thing that describes it (the AD). Far too many others confuse the 2 concepts

Comments

Comment on this article

Related Articles

    Sharing tags:

    External Links

    1.2.004 adl admin advice applescript application architecture architecture description architecture description language architecture framework artefact artisan studio award berlow blog boundary browser bug c3 capability capability configuration colaboration collaboration committee compare compliance concept concert conference configuration control conformance consistency content contrast css cv01 def stan defence definition demonstration denmark department for transport develop discovery dndaf document dod dodaf drawing enterprise enterprise architect ertms event evolve exchange exploit forum fun geneology gfdl gnu graph group handbook hazard head-model history humour ibm rhapsody iec ieee ieee1471 iet ietf implement implementation incose innovation institute integrated ea interoperability introduction ipad iso iso42010 isse keynote knowledge language linkedin lockheed martin london london underground m3 mac management mdg meaning meeting metamodel mil std modaf model modelling style naf nato natural language needline news nist no magic magicdraw noun omg omnigraffle ontology open source opensource operational organisation oxfordshire perspective plan platform playlist portability presentation procurement profile project public publication publish purpose rail relationship release repository research resource rfc4677 risk role rssb rule safety sea search security sentence service singapore site softeam modelio software solution song sos sourceforge sparx systems sparx systems enterprise architect specification spreadsheet stakeholder concern standard steering group stencil stereotype store strategy structure support sysml system system authority system of systems systems engineering team template test threat
     

    All articles/posts © of the respective authors

    Site design and architecture © 2010 - 2011 Eclectica Systems Ltd.