The definition of the metamodel for TRAK (defines allowed AD elements and relationships i.e. tuples/ triples for the TRAK viewpoints and views). TRAK is a general systems-thinkers’/system engineering enterprise architecture framework. It is simple, user-friendly, pragmatic and not limited to IT.
If you are like the rest of our user community, your IT team is busy. With pressure to deliver on-time projects, you don’t have a lot of time to spend making your management tools work. You need network monitoring tools that work for you. You want tools that makes it easy to find performance issues before your users do and resolve them before they impact the business. That’s why tens of thousands of customers around the world love WhatsUp Gold.
Post Views:
467
| Website |
https://trakmetamodel.sourceforge.io |
| Tags |
EnterpriseInformation AnalysisModeling |
| License |
Other License
|
| Features |
- defines tuples / triples (declarative statements) that appear in TRAK viewpoints and views
- 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)
- metamodel (A3) for easy reference when modelling - see snapshot below for example
- defines each TRAK node and relationship type in architecture description)
- defines attributes/properties of each element type e.g. dublin core, security descriptors, safety-related
- provides tests for/against to determine what type to use when modelling using TRAK
- defines colours/ presentation for each element
- defines each relationship (between node)
- defines tuple set rules (combinations of nodes with relationships)
- provides rationale/justification for relationships
- released under GNU Free Documentation License
- written for users/architects/human beings - not specifiers or tool vendors
- designed to be used with TRAK Viewpoints document (http://trakviewpoints.sf.net) - also on Sourceforge
- defines initial baseline against MODAF 1.2
|