Clearly enterprise architecture views only have so much utility. On the other hand they can be useful for discovering and establishing relationships and integrating with more specialist tools sets or models produced by these other tools.
Would EA views be useful in the management of system safety and system security and if so, what might they address?
]]>This supports the change in definition of the names of the TRAK stereotypes (blocks and connectors) and their attributes to make the names into ‘proper’ english rather than typical ‘softese’ so that you get ‘Resource Interaction’ rather than ‘ResourceInteraction’ and attributes like ‘tools used’ (Architecture Description) rather than’ toolsUsed’.
There is also support for a commercial privacy marking e.g. ‘IN STRICT CONFIDENCE’ .
Scripts are included to migrate any existing EA project to the new names. Scripts are also included to clear out some of the artefacts of the model of TRAK in EA itself which produced tagged values wherever a relationship role was defined. As these are nothing to do with the definition of TRAK they add no value, only clutter. The scripts also merge any values for location for Resources (Software, System, Role, Job, Organisation, Physical) stored in the old ‘locationLatitude’, ‘locationLongitude’ into the single ‘location’ tagged value which uses the format latitude (degrees), longitude (decimal degrees), altitude (m) [optional] as specified by RFC 5870 . A Uniform Resource Identifier for Geographic Locations. June 2010. (the implementation of TRAK in terms of standards, naming, enumerated values is defined by TRAK. Implementation. Architecture Description Elements )
It is ready to go bar one problem. There is an EA Model View - ‘Missing Descriptions - Objects’ which lists all the objects that have no description - which when run for an EA project in a .eap file (not for one in a DBMS server like MySQL) causes EA to hang. The search, which can be run separately, works perfectly and causes no errors. It’s only when a Model View is created and based on the (working) search that the error occurs. A priority support request has been raised with Sparx Systems and they’re looking into it.
]]>It examines the contents of the tagged value used to hold the protective marking (‘pm marking’) for every object (not connector):
if it finds values that correspond to ‘NONE’, ‘NOT PROTECTIVELY MARKED’, ‘RESTRICTED’, ‘CONFIDENTIAL’, ‘SECRET’ or ‘TOP SECRET’ (or any combination of upper / lower case to this effect) it corrects them
if it finds the older tagged value named ‘pm_Marking’ it issues a warning to run the script that comes with v 0.124 of the MDG Technology for TRAK that changes the tagged value names.
if it finds that the object (excluding packages/folders) is missing the tagged value it adds it with default value ‘NONE’ and reports this.
if it finds a value that it doesn’t recognise it reports this. You can then run the script again with a setting to forcibly set these values to ‘NONE’ .
As ever - no warranty and you should always backup your project file before running a script that modifies your project.
Any suggestions for useful things to be able to do / automate when using the MDG Technology for TRAK / creating a TRAK architecture description?
==
!INC Local Scripts.EAConstants-JScript
/*
* Script Name: Project - correctPMmarking.js
* Author: Nic Plum Eclectica Systems Ltd. http://eclectica-systems.co.uk
*
* Purpose: Checks the 'pm marking' protective marking tagged value contents across an entire TRAK EA project
* and corrects values to current definition (NONE/NOT PROTECTIVELY MARKED/RESTRICTED/CONFIDENTIAL/SECRET/TOP SECRET)
* If 'pm marking' is missing it will be added with the default value of 'NONE'
* Reports where a non matching value is found and can then be run again to set this to 'NONE'
* Does not apply marking to packages (folders)
*
*
*
* Support: http://trak-community.org/index.php/forums/viewforum/11/ - look out for new scripts in the future
* and http://sourceforge.net/projects/mdgfortrak/support
*
*
* Date: 31th December 2011
*
* __________________________________________________________________
* NOTE: Backup up EA project file (.eap) or database before running !!
* __________________________________________________________________
*
*/
/*
* Legal Weasel Words
* GNU Free Documentation License Version 1.3, 3 November 2008
* The text of the license is at http://www.gnu.org/licenses/fdl-1.3.html
*
* This script is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY;
without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
i.e intended to be helpgul but no guarantee of anything.
*/
function repositoryDetails()
{
// Outputs some basic information that might be useful for debugging
// Show the script output window
Repository.EnsureOutputVisible( "Script" );
Session.Output("=====================================");
Session.Output("Project / Environment Information");
Session.Output("EA build = "+Repository.LibraryVersion);
Session.Output("EA edition = "+EAEdition(Repository.EAEdition));
Session.Output("EA edition ex = "+EAEdition(Repository.EAEditionEx));
Session.Output("Project ID = "+Repository.ProjectGUID);
Session.Output("=====================================");
}
function EAEdition (enValue)
{
switch (enValue)
{
case piLite:
return "EA Lite" ;
case piDesktop:
return "Desktop Edition";
case piProfessional:
return "Professional Edition";
case piCorporate:
return "Corporate Edition";
case piBusiness:
return "Business Edition";
case piSystemEng:
return "Systems Engineering Edition";
case piUltimate:
return "Ultimate Edition";
default:
return "Unknown edition";
}
}
function correctPMmarking(changeUknownValues)
{
// Show the script output window
Repository.EnsureOutputVisible( "Script" );
var forceChange = changeUknownValues;
//deprecatedAttName =oldAttName;
var allExistingElements as EA.Collection;
var currentAttribute as EA.Attribute;
var theTaggedValue as EA.AttributeTag;
var theExistingTaggedValues as EA.Collection;
var theElement as EA.Element;
var SQLstatement = "SELECT t_object.Object_ID FROM t_object WHERE t_object.Stereotype IS NOT Null AND t_object.Stereotype <> 'stereotype' AND t_object.Stereotype <> 'metaclass' AND t_object.Stereotype <> 'enumeration' AND t_object.Stereotype <> 'Pre-condition' AND t_object.Stereotype <> 'profile'";
allExistingElements=Repository.GetElementSet(SQLstatement,2);
var taggedValue_pm_marking_curr as EA.TaggedValue;
var taggedValue_pm_Marking_old as EA.TaggedValue;
var newTaggedValue as EA.TaggedValue;
var thisTaggedValue as EA.TaggedValue;
var noUnknownChanged = 0;
var newTaggedValues = 0;
var taggedValName = "pm marking"
Session.Output( "Searching project looking at contents of '"+taggedValName+"'" );
Session.Output( "=======================================" );
Session.Output( "Number of repository elements= "+ allExistingElements.Count );
// Get the currently selected element in the tree to work on
for ( var i = 0 ; i < allExistingElements.Count ; i++ )
{
theElement = allExistingElements.GetAt(i);
taggedValue_pm_marking_curr = theElement.TaggedValues.GetByName(taggedValName );
taggedValue_pm_Marking_old = theElement.TaggedValues.GetByName("pm_Marking");
if ( taggedValue_pm_marking_curr != null )
{
//first check / correct for mixed case typos e.g. 'nONE', 'NOnE' etc.
switch (taggedValue_pm_marking_curr.Value.toUpperCase())
{
case "NONE":
taggedValue_pm_marking_curr.Value="NONE" ;
taggedValue_pm_marking_curr.Update;
break;
case "NOT PROTECTIVELY MARKED":
taggedValue_pm_marking_curr.Value="NOT PROTECTIVELY MARKED" ;
taggedValue_pm_marking_curr.Update;
break;
This is a by product of the development of the forthcoming MDG Technology for TRAK version 0.124 which implements the change (#3418285) to the TRAK metamodel where normal english is used rather than ‘softese’ i.e. ‘Concept Activity’ instead of ‘Concept Activity’ and ‘tools used’ for ‘toolsUsed’. The idea is to make it easier for anyone to read any view since it’s all about communication of ideas.
Most of the development activity at the moment is to provide supporting scripts to change the names of the tagged values and stereotypes affected and to preserve values.
The script to delete a tagged value is
!INC Local Scripts.EAConstants-JScript
/*
* Deletes object attribute (not connector attribute) name across entire repository.
*
* NOTE: Backup uo before running
*
* Nic Plum Eclectica Systems Ltd
*/
function deleteAttribute(oldAttName)
{
// Show the script output window
Repository.EnsureOutputVisible( "Script" );
var allExistingElements as EA.Collection;
var currentAttribute as EA.Attribute;
var theElement as EA.Element;
var taggedValue as EA.TaggedValue;
//limit operation to those elements having a tagged value with the correct name
var SQLstatement="SELECT t_object.Object_ID FROM t_objectproperties INNER JOIN t_object ON t_objectproperties.Object_ID = t_object.Object_ID WHERE t_objectproperties.Property='"+oldAttName+"'";
//select those elements using the query
allExistingElements=Repository.GetElementSet(SQLstatement,2);
Session.Output( "Delete Tagged Value Name: '"+oldAttName+"'" );
Session.Output( "=======================================" );
Session.Output( "Number of repository elements having tagged value '"+ oldAttName+ "' = "+ allExistingElements.Count );
// operate on an element within the returned collection
for ( var i = 0 ; i < allExistingElements.Count ; i++ )
{
theElement = allExistingElements.GetAt(i);
taggedValue = theElement.TaggedValues.GetByName( oldAttName );
if ( taggedValue != null )
{
//have to iterate through collection of tagged values because there is only a means to delete using the index value within the collection
//not a DeleteByName
for (var ttv=0; ttv < theElement.TaggedValues.Count ; ttv++)
{
thisTaggedValue=theElement.TaggedValues.GetAt(ttv);
if ( thisTaggedValue.Name == oldAttName)
theElement.TaggedValues.DeleteAt (ttv,true);
}
taggedValue.Update;
}
}
Session.Output( "Done!" );
Session.Output( "" );
}
deleteAttribute("add tagged value name here");
]]>
MooD is different in that it isn’t a UML modelling tool so nice to see TRAK on something a bit different for a change.
]]>]]>Job purpose
Systems Design/Requirements Engineers are required to join the System Engineering team to assist in the development of the ATC signalling system and the safety-related and safety-critical products of which it is comprised, particularly in the front-end of the system engineering lifecycle.
Role Outline / Key Responsibilities:
The candidate should possess expertise in two or more of the following:
• Requirements capture, analysis and management;
• Systems design, analysis, modelling and simulation ( “black-box design” );
• Sub-system specification and interface control and management;
• Sub-system design and analysis (Hardware / Software allocation).Note that the engineering techniques involved with the development are cutting-edge with extensive use of the UML and SysML, increasing use of Architectural Frameworks such as MoDAF/DoDAF/TRAK, with support from tool-sets such as DOORS® and Artisan Studio®.
The candidate will also be expected to maintain an appreciation of new technologies and their application to support ongoing deliveries.
The Candidate:
Essential Requirements
• A formal qualification in a relevant engineering, scientific or numerate discipline.
• Experience of working to industry quality and safety standards, preferably in the safety-critical arena.
• Excellent verbal and written communication skills.
• Motivated, dependable and self-reliant.Desirable Requirements
• Experience in the development of Signalling Systems, Automatic Train Protection products or Control System for Railways.
Personal Qualities
• Personable and fair
• Analytical and solutions based
• Good written and spoken communication skill
• A completer finisher with an eye for detail
“Systems Engineering: Adding Value in Challenging Times”
We live in challenging times - budgets are shrinking, and customers are increasingly looking for value-for-money solutions, with the added complication of a perceived shortage of systems engineers across many industry sectors.
These are the challenges that Systems Engineering needs to address:
* driving down costs by effectively managing uncertainty on projects
* developing novel solutions that address the actual stakeholder problems
* promoting a systems approach as the cornerstone of good engineering practiceINCOSE UK invites you to attend ASEC 2010 and share your views on how the Systems Engineering community can move things forward.
ASEC 2010’s new format offers a mixture of keynote speakers representing the challenges of our increasingly “Systems World”, paper presentations giving an insight into some of the real world situations where INCOSE UK members are adding value, invited speaker sessions highlighting the best of the technical activities of INCOSE UK, workshops to allow smaller groups to look at a topic in detail and finally tutorials providing opportunities to learn more about Systems Engineering techniques and approaches.
This year’s theme considers the value of Systems Engineering in ‘Challenging Times’. The ‘Value’ of Systems Engineering in this context includes:
* Applying a Systems Approach to complex real world ‘System of Systems’ problems. Our first keynote speaker, Professor Brian Collins - Chief Scientific Adviser,
Department for Transport, will talk about the challenges of an integrated approach to ground transport, rail and infrastructure. We will also consider the challenges of dealing with System of Systems properties such as Safety and Resilience.* How to get the most value out of Systems Engineering in engineering or service delivery organisations. Our second keynote speaker, Peter Price - Director of Engineering and Technology (Civil Aerospace) at Rolls-Royce, will talk about the role of Systems Engineering within his organisation. We will also have sessions on Systems Engineering skills, competencies and case studies from across the INCOSE community.
* Getting the most value from specific Systems Engineering activities. This will include the work of some of the INCOSE UK technical working groups, together with detailed workshops and tutorials. These will be complemented by an exhibition of Systems Engineering suppliers, tool vendors and specialist consultancies.
There are 2 sessions relating to TRAK:
Day 1: 11:10 - 11:50 Nic Plum & Chris Lowe Human Factors - On the Right TRAK?
Nic Plum - Eclectica Systems Ltd.
Chris Lowe - Liv Systems Ltd.
This presentation is about applying a user-centred design (UCD) approach to unusual things: the design of a UK rail industry architectural framework called TRAK and its use for Human Factors work in a challenging Systems Engineering environment.
This architectural framework, if it is to be usable, has to address a number of challenges. The framework needs to unite or integrate the different stakeholder viewpoints on the same underlying system or problem. The framework also needs to be usable by these different stakeholders.
In applying UCD, the emphasis has been placed on consistency, simplicity and ease of use, and as a system it is essential that not only does it embed HF principles in its design but also that it should support the practical needs of Systems Engineering disciplines. For this reason, we will also describe how TRAK supports the needs of practitioners with reference to studies conducted within the Rail Industry.
Day 1 13:30 - 15:00 Colin Wood et al TRAK - An Architecture Framework for Rail
Colin Wood - London Underground Ltd., Capital Programmes Directorate
Nic Plum - Eclectica Systems Ltd.
Andy Pryor - SEA Ltd.
Systems Engineering extols, amongst other things, the virtues of having greater control and awareness of interfaces, sometimes called Interface Management. Systems Architecting is the activity of choice for delivering managed interfaces. Systems architecting of complex systems within and across different contractual boundaries requires a common architectural description language – aka an architecture framework.
While other sectors have been applying architecture frameworks for years, the rail sector has largely ignored them, perhaps thinking that they are over-complicated, another bureaucratic layer and just too difficult to roll-out successfully. It may have a point…
... but TRAK is different. It is easy for small, medium and large enterprises alike to get to grips with. It was developed by rail professionals for rail professionals. It is system-centric and has just enough to get the job done. Its open source means anyone can download it freely from the internet and start producing productive systems architecture diagrams straightaway. What is more, they are re-usable and shareable with partners.
This lively 60 minute joint presentation will explain TRAK and explore three case studies:
* An implementation of TRAK using Sparx Systems Enterprise Architect;
* Applying TRAK to interface management for the London Underground Sub-Surface Railway Upgrade;
* Applying TRAK to developing a functional architecture model of the UK railway.
Further information can be found at on the INCOSE UK Chapter’s website
]]>Permanent
An exciting opportunity has arisen for an experienced Business Analyst/Systems Engineer proficient in Requirements Engineering to deliver a range of high profile programmes in the defence and public sectors.
The ideal candidate will be a strong professional, multi disciplined Business Analyst/Requirements Engineer with a strong academic and commercial background and a strong grasp of modern technologies, systems, software and architectural methodologies. You will have a high degree of technical ability, be innovative and imaginative with strong problem solving skills.
You will ideally have solid commercial experience in User and Systems Requirements Engineering, Gathering, capturing and modelling requirements, with experience of working in Architectural Frameworks such as MODAF, DODAF, TOGAF with experience with tools such as MooD, DOORS, UML etc. To complement your technical skills you will ideally have a good ground in the MOD/Defence arena with a good knowledge of the relevant projects, programmes and companies in the Defence sector. Preferably along with an understanding of GIS/Geospatial solutions and technologies. You will also have the flexibility to travel across the UK and Internationally as required.
This is an exciting opportunity to join a leading bespoke solutions provider working on cutting edge applications, where you can make a real contribution to the business and you will be rewarded with genuine opportunities for ongoing career progression and training, coupled with a very competitive benefits package. South West - Gloucestershire - Bristol - Herefordshire - West Midlands.
Due to the nature and urgency of this post, candidates holding or who have held high level security clearance in the past are most welcome to apply. Please note successful applicants will be required to be security cleared prior to appointment which can take up to 18 weeks.
LA International Computer Consultants Ltd is an HMG Approved Consultancy and operates as an IT & Engineering Consultancy or as an Employment Business & Agency, depending upon the precise nature of the work, for security cleared jobs or non clearance vacancies. Award Winning LA International Computer Consultants Ltd ( Recruiter Awards For Excellence - Best IT, Best Public Sector & Gold Awards)
Location South West England
Country UK
Start Date ASAP
Rate £30k - £48k per annum + Excellent Benefits Package
Employment Agency LA International Computer Consultants Ltd
Contact Tom Cowen
Email Tom.Cowen.C0CAA.9469F@mail.jobserve.com
Reference JS-TC/REQMODAF/04198565
Posted Date 19/08/2010 17:51:23
If you wish to raise a bug or feature request this is best done using the trackers for these purpose on Sourceforge i.e.
* to raise a bug - https://sourceforge.net/tracker/?group_id=270567&atid=1150722
* to raise a feature request - https://sourceforge.net/tracker/?group_id=270567&atid=115072
This way I can easily refer to the request numbers and sentence them in a systematic way.
]]>