Both are ultimately concerned with risk inherent in a solution design which arises from threats (security) or hazards (safety). On the face of it there is quite a bit of overlap. By that I whether there is something useful that an enterprise architecture view can be used for in the system safety and security disciplines.
This is something that has been bumbling around for some considerable time - safety and security. Safety & Securityīy Nic Plum on Tuesday 10 April, 2012 - 21:25 GMT Solution Risk, Vulnerability, Threat and Mitigation - Does Risk Need to be Separate from Event? (20% ).
What Would a TRAK View Look Like in a Graph Database? Part 1 (20% ).Every Viewpoint Has to Be Distinct - Say “Goodbye” to the TRAK CVp-02 Concept Viewpoint (20% ).Definitions - What Exactly is a Risk? (60% ).Risk and Threats - The Common Ground Between Security and Safety? (80% ).Risk and Threats - The Common Ground Between Security and Safety?.If anyone wishes to help in this testing phase can they please make contact either via this site or the Sourceforge discussion forum for the Safety and Security Working Group. There will then follow a testing phase to ensure that what is proposed is usable, easily understood, pragmatic and of utility (fit for purpose - but no more than necessary as we don’t want perfection at the expense of usability) for jobbing engineers and those who need to be able to read and understand the products and who aren’t in any technical priesthood. a definition of the candidate viewpoints (ISO/IEC/IEEE 42010 terminology) against which views are prepared that use the candidate and existing parts of the metamodel.a definition of the candidate relationships that knit these entities together and to the residual TRAK metamodel.There will be other follow-on documents soon: If you have any views on the candidate entities please post them there. This has been published and comment / discussion is being encouraged on the forum on the TRAK Viewpoints project on Sourceforge. As part of the ongoing activity a candidate set of concepts / entities for the TRAK metamodel have been described in a short document together with some of the backgrounds from which they arise. TRAK::Application of Systems Engineering to the Design of TRAKīy Nic Plum on Wednesday 13 March, 2013 - 21:33 GMTĪ small band of happy volunteers have been musing over possible extensions to TRAK to provide viewpoints that address typical safety and security concerns.INCOSE UK Chapter's Annual Systems Engineering Conference: 8th - 10th November 2010.Systems Engineer - Early Lifecycle (ATC Signalling / TRAK).Salamander MooD - Version 2 of TRAK Template for MooD 2010 Released.Sparx Systems EA - Script - Delete Specified Tagged Value Across Repository.SparxSystems EA Script - Correct Protective Marking Tagged Value ('pm marking') Across Entire EA Project.MDG Technology for TRAK - Version 0.124.Applications / Utility of Architecture Description Views for System Safety and System Security?.Systems Architect - Defence Systems (Bedford / Lockheed Martin).TRAK Article Published by The Institution of Engineers (Singapore).Every Viewpoint Has to Be Distinct - Say “Goodbye” to the TRAK CVp-02 Concept Viewpoint.Definitions - What Exactly is a Risk?.Just When You Thought It Was Safe - EntiTy Returns.Definitions - What Exactly is a Risk Part 2?.What Would a TRAK View Look Like in a Graph Database? Part 1.Solution Risk, Vulnerability, Threat and Mitigation - Does Risk Need to be Separate from Event?.Nato AF (NAF) Version 4 - A Look at the Definition of View Content.
0 kommentar(er)
