Entrepreneurship, Commercialisation, and Innovation Centre publications
Permanent URI for this collection
Browse
Browsing Entrepreneurship, Commercialisation, and Innovation Centre publications by Author "27th Annual INCOSE International Symposium (IS) (15 Jul 2017 - 20 Jul 2017 : Adelaide, Australia)"
Now showing 1 - 1 of 1
Results Per Page
Sort Options
Item Metadata only Use of the goal structuring notation to argue technical integrity(Wiley on behalf of the International Council on Systems Engineering (INCOSE), 2017) Simmonds, S.; Cook, S.T.E.P.H.E.N.; 27th Annual INCOSE International Symposium (IS) (15 Jul 2017 - 20 Jul 2017 : Adelaide, Australia)The Australian Defence Force currently uses three separate technical regulatory frameworks, one for each of the services. These are each concerned with accepting materiel – Land, Aerospace or Naval – into Australian Service. These technical regulatory frameworks use similar terminology and conceptually are based upon a similar model of design assurance – in particular the concept of Design Acceptance. Design Acceptance is a process that (among other things) examines the system in terms of its functions, construction, and ability to be safely used and maintained through its service life. The Design Acceptance process has the goal of ensuring a design, sourced from a design agency, has met its specification as determined by verification, has been developed by competent personnel within the design agency, and as part of that development, has been subjected to independent review and certification. Goal Structuring Notation (GSN) is a means to produce a sound argument based upon evidence of the satisfaction of the above criteria. Using GSN, the assurance argument presented to the technical regulator can be partitioned such that the elements of a Design Acceptance argument can be built up over time, and can address the critical elements of the argument appropriately. This paper provides an introduction to the application of the GSN to formulating a Design Acceptance argument and, in particular, its application to a Technical Integrity argument.