UK INCOSE Annual Systems Engineering Conference. Case Study - Implementing TRAK in Sparx Systems Enterprise Architect

1,896 views

Published on

A presentation given to the UK INCOSE Annual Systems Engineering Conference (ASEC) 2010 at Heythrop Park. See http://www.incoseonline.org.uk/Program_Files/Calendar/Show_Event_Details.aspx?
CatID=Events&EventID=138

Describes how an implementation of TRAK, a generic architecture framework, was implemented using Sparx Systems Enterprise Architect UML modelling tool.

TRAK is defined at http://trakviewpoints.sourceforge.net and http://trakmetamodel.sourceforge.net

Published in: Technology, Education
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,896
On SlideShare
0
From Embeds
0
Number of Embeds
18
Actions
Shares
0
Downloads
26
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • London Underground had selected Sparx Systems Enterprise Architect as the UML modelling tool for the project, the Sub Surface Upgrade Programme (SUP). Prior to using Sparx Systems their architectural output had been produced as drawings using Visio (increasingly difficult to maintain, very difficult to keep individual drawings consistent and not easily re-usable by other than the author). Having selected the tool they then needed something to make it easier to produce TRAK-compliant architecture description.
  • A typical configuration includes:- Mk1 Human Being – the architect a computer on which sits Sparx Systems Enterprise Architect modelling software TRAK MDG Plugin for Sparx Systems Enterprise Architect. This is a non-executable text file that contains a set of UML profiles the UML profile for TRAK the profile that represents TRAK diagrams the profile that represents the set of toolbox palettes (each corresponds to a particular TRAK view type) the Quicklinker profile that tells the tool what relationships to offer when connecting 2 objects in a particular view In addition and not shown is a profile that represents the custom searches to help manage the repository The Quicklinker profile is the largest – runs to approx 700 lines i.e. 700 rules.
  • ×