
This paper documents a number of observations that may provide the basis for how User Requirements Notation (URN), currently the subject of ITU-T Z.150 and Z.151, can act as a modelling approach atop which normative guidance for architecture rationale or decision capture of System Safety and other concerns may be applied to Architecture Descriptions to act as an Assurance Justification. URN is thus offered as a means to fill recognized gaps in ISO/IEC/IEEE 42010 as the means for rationale capture. Moreover, the goal-oriented or goal-refinement aspects of URN may be viewed as an analogue of the Claims-Argument-Evidence style of argument ISO/IEC/IEEE 15026 proposes. URN certainly can compete with Goal Structured Notation (GSN). Stealing then from the tension between safety viewpoints at the University of York (UK) and those at MIT (US), and looking at ideas from outside those cliques (but alluded to by those cliques), the potential for integration of safety argument philosophies into Architecture Descriptions, so as to arrive at Intentional Enterprise Architecture, is investigated. All roads appear to lead to URN.
| selected citations These citations are derived from selected sources. This is an alternative to the "Influence" indicator, which also reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | 0 | |
| popularity This indicator reflects the "current" impact/attention (the "hype") of an article in the research community at large, based on the underlying citation network. | Average | |
| influence This indicator reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | Average | |
| impulse This indicator reflects the initial momentum of an article directly after its publication, based on the underlying citation network. | Average |
