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 = 'Wiki'

Entries that have been tagged with 'Wiki'.-

Pulling the MODAF, DODAF, NAF et al Into a Common Frame of Reference

by Nic Plum on Monday 05 April, 2010 - 10:52 GMT

Posted in Architecture FrameworkMODAFNAFSite

Tags: comparecontrastdodafmodafnafsitetrakwiki

c300 pages on the wikiSome of the more observant amongst you might have noticed that we have a wiki that aims to cover multiple enterprise architecture frameworks (DODAF, MODAF, NATO Architecture Framework and TRAK as a minimum) as well as the use of such things in a typical systems engineering lifecycle.

This is a long slow process. The first to be covered was TRAK and now we’ve got decent coverage of the NATO Architecture Framework as well as a sprinkling of MODAF. To date there are the best part of 300 pages. There’s a lot still to do so if anyone would like to help then this would be gratefully received as it takes time to locate source material and extract the essence.

Why go to this trouble? For several reasons:

  • To help. Some frameworks either don’t have much of a web presence or provide information in forms that isn’t the easiest to navigate through. MODAF has suffered in navigability as a result of being taken from the site maintained by Model Futures and squeezed into the ‘one size fits all’  corporate MoD structure. The NATO Architecture Framework and some others just offer a set of unlinked PDF documents without supporting web content. If we can extract the bare bones in terms of view definitions and link them to other views, the respective metamodel and other frameworks then this has to be better.
  • To compare and contrast. All of these frameworks have a common origin, the DODAF, and have at times borrowed bits from each other so there is a lot of similarity. There are also some important differences reflecting their ages and their respective specification and user communities. It’s very difficult to see this when they are widely separated and presented in very different formats and language or terminology. If we can provide bridges between the frameworks and put the information in a similar way alongside each other then it’s much easier for the user or potential user of the frameworks. I have this belief that there will be a universal metamodel at some point. One of the reasons we separated the definition of the TRAK Viewpoints from the TRAK metamodel was to   allow for the possibility that we’d not got it right and to enable the metamodel to be re-used if needs be).
  • To provide points of reference. As a lot of the frameworks are expressed in large documents it’s quite hard to make reference to a particular view or metamodel element. If each view, each term or each metamodel element is a separate wiki page it makes it much easier to make reference to - each element is addressable by a URL (which is where I’d really like the architecture models themselves to be at some point in the future) and within a namespace named after the framework (not all terms have the same meaning e.g. MODAF:View is a singular architecture view, NAF:View is a collection of subviews and TRAK:Architecture View although singular is a response to a view specification (TRAK:Viewpoint).

Being forced to read the documentation in some detail means that you do learn quite a lot. I’ve learnt that NAF:System cannot realise a capability and that NAF:Organisational Resource  (Organisation and Post = ‘Job’)  cannot have functions assigned directly only indirectly via NAF:Role.

I’d be interested if anyone has good pointers to AUSDAF documentation and very much so if any site member wanted to help to start fleshing out other frameworks.

Keep up to date with the wiki by subscribing to the RSS feedAnyway, you can keep up to date with progress / changes on the wiki by subscribing to the RSS feed.

 

Comments

Comment on this article

Related Articles

    {REL[122][related1_blog]2VZPhL0BREL}

    Sharing tags:

    External Links

    Support for the ‘AFs - Wiki Now Live

    by Maestoso on Thursday 25 February, 2010 - 15:27 GMT

    Posted in NewsSite

    Tags: dodafmodafnafsitetrakwiki

    Snapshot of the pages in one part of the TRAK-Community Wiki

    Wiki- With Spaces for TRAK, MODAF, DODAF and Common Process/Problems

    After a long time - some months - of effort the wiki has got to the point where it’s sensible to let it loose.

    It has something over 200 pages (a devil to keep consistent) and there’s inevitably a lot of explanation to support the recent release of TRAK. It does have a comparison between TRAK and MODAF 1.2 and sections for MODAF, DODAF, NAF as well as for the modelling process.

    Any site member can add content as with the rest of this site - if you don’t see the page you wanted help create it!

    There’s lots still to do both in terms of content and adding functionality

    • wiki page heading links
    • linking the wiki to the discussion forums so that comments can be made on each page

    Visit the wiki now!

    Comments

    Comment on this article

    Related Articles

      {REL[123][related1_blog]2VZPhL0BREL}

      Sharing tags:

      Forums

      External Links

      Putting the Architectural Modelling Community First - What You Can Expect to See

      by Nic Plum on Saturday 02 January, 2010 - 14:03 GMT

      Posted in Site

      Tags: blogforumfunplansitestructurewiki

      This current site is really only a interim site. What is intended is a site that properly supports the folks using TRAK or other MDAF-based architecture frameworks and one which represents the ethos behind it:-

      • pragmatic - led by need and application - the human interface to the framework (usability, affordance etc.)
      • open - decisions, rationale, explanation
      • democratic - involve the community in the site content rather than broadcast top down what I/we think folks need. The centre of gravity ought to be with the users rather than the specifiers-of the framework
      • fun - why not? Systems thinkers/engineers and architects are real, dare I say it ‘whole’ people and all sides need to be addressed
      • dynamic - the content needs to be able to change and adapt to new circumstances, thinking or practice

      What You Might Expect

      The features that you should expect to see are:-

      • each section of the site is a ‘blog’
        • articles can be discussed and commented on by site members
        • updates notified by RSS news feeds
      • articles can be linked together, tagged, put into categories and dynamically sorted/displayed and searched for by users
      • discussion forums
        • tool support
        • use of architecture frameworks
        • modelling / repository organisation - not governed by frameworks but important and common to all
      • architects can submit examples of views to help others
      • wiki to hold facts on architecture frameworks e.g. metamodel elements, use of UML tools, tips, plugins etc.
      • single sign-on to comment, add a forum discussion or to add to the wiki
      • everyone can see everything - nothing hidden
        • only site members can contribute or comment - contributors and commenters recognised and stand up to the mark!
      • fun / anarchic humour
        • the lighter side
        • not taking life too seriously

      Comments

      Comment on this article

      Related Articles

        {REL[135][related1_blog]2VZPhL0BREL}

        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.