Message-ID: <852288035.4849.1490505790713.JavaMail.confluence@ece-vmapps> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_4848_238347670.1490505790712" ------=_Part_4848_238347670.1490505790712 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The definition of the Design Context according to the Annex C Gl= ossary is "Methodological metadata that provide the basis for the spec= ification of the information objects required as input to and output from t= he Process Step Design including Process Method and R= ules." I think I can understand "Methodological metadata tha= t provide the basis for the specification of the information objects requir= ed as input to and output from the Process Step Design." but = the addition of Process Method and Rules in the defintion is slightly misle= ading. They are examples of information objects required as input to Proces= s Step Design, but they are not Design Context so they should be removed. I= nstead we should include som examples of Design Context in the Explanatory = text which is currently empty.
As a reminder the recommendations from ISO/IEC 11179-4: Formulating data= definitions are
A data definition should: a) state the essential meaning of the concept,= b) be precise and unambiguous, c) be concise, d) be able to stand alone, e= ) be expressed without embedding rationale, functional usage, or procedural= information, f) avoid circular reasoning, g) use the same terminology and = consistent logical structure for related definitions and h) be appropriate = for the type of metadata item being defined
Can someone provide an example, or two, of Design Context?