RW - Navigation

RW - Recent

Last 10 entries [comments]:


Last 10 posts [threads/views]:


Last 10 pages updated:

There are 487 wiki pages in total.

RSS logoRSS Feed

The Residual World::Tag = 'Naf'

Entries that have been tagged with 'Naf'.-

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 550 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!


Comment on this article

Related Articles


    Sharing tags:


    External Links

    What is the Point of this Site?

    by Nic Plum on Saturday 31 October, 2009 - 13:00 GMT

    Posted in Site

    Tags: collaborationdodafgeneologyhistoryintroductionmodafmodelling stylenafpurposesitetooltrakutility

    Indeed, what is the point of this site? Why go to the trouble and suffer the frustrations in creating it? Why not simply “get a life”?


    It started with TRAK (very nearly a Hot Chocolate hit there!) - The Rail Architecture Framework - which I’ve been developing over the last year for London Underground Limited. This is based on the MODAF, the MoD Architecture Framework which is important to the rationale for the site. At the beginning it was thought that a framework would need to contain rail-specific constructs and views but in the end we realised that we’d created something that was domain or industry-free. It should have been obvious from a system-thinker’s perspective, but the journey to this point is just as important as the realisation.

    Of course in developing and trying out the views, the UML profile and the plugin for Sparx Systems Enterprise Architect modelling tool similar questions arose. It was also valuable because it meant that the development was led by the pragmatic, down to earth needs and problems faced by architects delivering views and models to meet deadlines.

    In reality the experience in TRAK is building upon the experience over many years first at the MoD at Abbey Wood and then at the Architectures Lab at Malvern. Most of the support and help was provided by the group itself. It had to be this way because we were modelling in the days before MODAF and discovering and making rules based on practical experience. Like most things in life you need to experience failings and problems to properly appreciate the wisdom of others!


    Since DODAF first appeared many other related enterprise architecture frameworks have appeared. They all continue to borrow ideas from each other as they evolve.

    Enterprise Architecture Frameworks Related to DODAF

    Many Enterprise Architecture Frameworks are Related to DODAF

    The Perceived Need - Support

    The sorts of areas where help, advice and support is needed for enterprise architecture include

    • frameworks
      • definition - what must appear
      • advice - what should appear
      • what a framework can represent, what it can’t represent
      • when something else is best used to represent
    • modelling style
      • how to represent particular configurations, functionality
      • modelling patterns or conventions often encountered
      • types of model
    • utility or usefulness
      • best views for a purpose
      • fitness for purpose
      • when to use a model / when not to
      • dealing with stakeholders
      • applicability of views to common development scenarios / lifecycle e.g. design review points, activities
    • collaboration
      • preparing for sharing models
      • working with remote colleagues
      • keeping in sync - models & understanding & consistency
      • dealing with privacy
    • communication - the primary objective as we need to be able to communicate findings, analysis, implications (as interesting as it might be it’s not for our own benefit!)
      • detail, scope - what to include / leave out
      • adjusting for stakeholders - maintaining the model & avoiding the simple powerpoint/visio syndrome (“just a diagram”)
      • organisation of views / model - navigability - “telling a story” / the user-interface of the model presented
      • documenting the model, findings
    • tools for modelling
      • limitations
      • features
      • compatibiity/interoperability with other tools
      • model / repository organisation
      • model/repository consistency

    Apart from the very obvious framework-specific part many of these areas overlap and face common problems. Solved once the solution ought to be able to help others even if the framework being used is different.

    Then there’s the people side. Many of us who work with one framework have and will work with others so why create silos? As with the models produced it makes sense to try and reuse, adapt and extend wherever possible. The centre of gravity ought to reside with the users and user-generated content not with the standards themselves - it has to be of use and pragmatic.

    It therefore seemed if a means of enabling support were provided, to recognise this overlap between all the DODAF-related frameworks.

    The Purpose

    In short

    The purpose of the site is to provide a means for users and practioners of DODAF/MODAF-related architecture frameworks

    • to get practical advice and help
    • to give advice and help

    to help create, share and build-upon (extend) existing architecture models.

    The watchwords are - useful, practical, understandable

    The Belief

    It might be that everything is already covered - there’s enough “how to”, FAQ, examples, advice when faced with typical project situations. It might be that as a bunch we like best to keep quiet and keep it all to ourselves or that we believe that knowledge is power. I’d rather believe that we like helping others (and in doing so we often help ourselves).

    If you’re in the latter category then please sign up and please contribute - whether comments on entries, discussions in forums, examples of architectural views or adding to the wiki. You never know when it might prove useful. It’s also self-help and therapeutic to share!


    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 - 2019 Eclectica Systems Ltd.