The architecture viewpoints (specifications for architecture views iaw ISO 42010) for TRAK. TRAK is a general systems-thinkers'/system engineering enterprise architecture framework. It is simple, user-friendly, pragmatic and not limited to IT.
Defines a total of 22 viewpoints. The ones needed for any task are selected by taking the task sponsor's concerns and matching them to the typical concerns that each TRAK viewpoint addresses.
The minimal process is defined in the overall TRAK specification. The allowed elements and relationships are taken from the TRAK metamodel.
- designed by systems engineers for others & based on need / typical application
- supports simple, pragmatic, no nonsense, just "good enough" way of addressing typical concerns (not populating a data model)
- defines each TRAK architect viewpoint
- specification for each TRAK architecture view - content/ tuples from the TRAK metamodel
- defines naming convention
- defines stakeholder concerns addressed
- provides method for selecting viewpoints needed to address stakeholder concerns
- defines mandatory & optional architecture tuples for each view
- specifies minimum acceptable content for each view (well-formedness)
- defines consistency rules between views
- defines minimum allowed view sets so that elements can be found where you'd expect them to be
- viewpoints conform to IEEE1471 / ISO 42010 for architecture description of systems
- defines difference wrt MODAF 1.2
- designed to be used with the TRAK Overall (http://trak.sf.net) & TRAK metamodel (http://trakmetamodel.sf.net) (available on sourceforge)
- implementations for Sparx EA, MooD, Visio and OmniGraffle for Mac / iPad on Sourceforge
- viewpoints cover enterprise, concept, procurement, solution and management & everything from structure, behaviour, interchange to assurance, requirements and the architecture description task itself
- MVp-04 assurance viewpoint based on Claim, Argument, Evidence - can be used for any assurance e.g. claim of design compliance with requirements
- SVp-13 Solution Risk viewpoint integrates description of safety and security (Threat/Hazard, Vulnerability, Mitigation) with that of the design itself
Anonymous single word thumbs downs like "Pointless" don't contribute anything. By way of balance, TRAK works for me - its easy to get to grips with and being open source my company doesn't tie itself to big maintenance bills.
Simple, accessible, logical - as my first foray into enterprise architecture, TRAK has made the experience a lot easier than wading through defence-specific standards and dogma. Its genericity could see it used throughout business and civil services.