diff --git a/examples/CENELEC_50128/mini_odo/mini_odo.thy b/examples/CENELEC_50128/mini_odo/mini_odo.thy index f3b5e92..3bd7021 100644 --- a/examples/CENELEC_50128/mini_odo/mini_odo.thy +++ b/examples/CENELEC_50128/mini_odo/mini_odo.thy @@ -19,6 +19,8 @@ theory "Isabelle_DOF.technical_report" begin declare[[strict_monitor_checking=true]] +define_shortcut* dof \ \\dof\ + isadof \ \\isadof{}\ (*>*) title*[title::title]\The CENELEC 50128 Ontology\ @@ -27,14 +29,31 @@ subtitle*[subtitle::subtitle]\Case Study: An Odometer-Subsystem\ chapter*[casestudy::technical]\An Odometer-Subsystem\ text\ In our case study, we will follow the phases of analysis, design, and implementation of the - odometry function of a train. This software processes data from an odometer to compute the position, - speed, and acceleration of a train. This system provides the basis for many - safety critical decisions, \eg, the opening of the doors. Due to its relatively small size, it + odometry function of a train. This \<^cenelec_term>\SF\ processes data from an odometer to compute + the position, speed, and acceleration of a train. This system provides the basis for many + safety critical decisions, \<^eg>, the opening of the doors. Due to its relatively small size, it is a manageable, albeit realistic target for a comprehensive formal development: it covers a - physical model of the environment, the physical and architectural model of the odometer including - the problem of numerical sampling, and the boundaries of efficient computations. The interplay + physical model of the environment, the physical and architectural model of the odometer, + but also the \<^cenelec_term>\SFRS\ aspects including + the problem of numerical sampling and the boundaries of efficient computations. The interplay between environment and measuring-device as well as the implementation problems on a platform - with limited resources makes the odometer a fairly typical safety critical embedded system. + with limited resources makes the odometer a fairly typical \<^cenelec_term>\safety\ critical + \<^cenelec_term>\component\ of an embedded system. + + The case-study is presented in form of an \<^emph>\integrated source\ in \<^isadof> containing all four + reports from the phases: + \<^item> \<^term>\software_requirements\, \<^ie> the \<^onto_class>\SWRS\ \<^typ>\software_requirements_specification\(-report) + \<^item> \<^term>\software_architecture_and_design\, \<^ie> the \<^typ>\software_design_specification\(-report) + \<^item> \<^term>\component_implementation_and_testing\, \<^ie> the \<^typ>\software_architecture_and_design_verification\(-report) + \<^item> \<^term>\component_implementation_and_testing\, \<^ie> the \<^typ>\software_component_design_verification\(-report) + + The objective of this case study is to demonstrate deep-semantical ontologoies in + software developments targeting certifications, and in particular, how \<^isadof>'s + integrated source concept permits to assure \<^cenelec_term>\traceability\. + + \<^bold>\NOTE\ that this case study has aspects that were actually covered by CENELEC 50126 - + the 'systems'-counterpart covering hardware aspects. Recall that the CENELEC 50128 covers + software. Due to space reasons, we will focus on the analysis part of the integrated document; the design and code parts will only be outlined in a final resume. The @@ -45,7 +64,7 @@ text\ development. \ -section\System Requirements as an \<^emph>\Integrated Source\\ +section\A CENELEC-conform development as an \<^emph>\Integrated Source\\ text\Accurate information of a train's location along a track is in an important prerequisite to safe railway operation. Position, speed and acceleration measurement usually lies on a set of independent measurements based on different physical principles---as a way to enhance @@ -74,17 +93,19 @@ text\ This model is already based on several fundamental assumptions relevant for the correct functioning of the system and for its integration into the system as a whole. In - particular, we need to make the following assumptions explicit:\vspace{-.3cm} - \<^item> that the wheel is perfectly circular with a given, constant radius, - \<^item> that the slip between the trains wheel and the track negligible, - \<^item> the distance between all teeth of a wheel is the same and constant, and - \<^item> the sampling rate of positions is a given constant. + particular, we need to make the following assumptions explicit: \<^vs>\-0.3cm\ + + \<^item> that the wheel is perfectly circular with a given, constant radius, + \<^item> that the slip between the trains wheel and the track negligible, + \<^item> the distance between all teeth of a wheel is the same and constant, and + \<^item> the sampling rate of positions is a given constant. These assumptions have to be traced throughout the certification process as + \<^emph>\derived requirements\ (or, in CENELEC terminology, as \<^emph>\exported constraints\), which is also reflected by their tracing throughout the body of certification documents. This may result - in operational regulations, \eg, regular checks for tolerable wheel defects. As for the + in operational regulations, \<^eg>, regular checks for tolerable wheel defects. As for the \<^emph>\no slip\-assumption, this leads to the modeling of constraints under which physical slip can be neglected: the device can only produce reliable results under certain physical constraints (speed and acceleration limits). Moreover, the \<^emph>\no slip\-assumption motivates @@ -112,7 +133,7 @@ subsection\Capturing ``System Interfaces.''\ text\ The requirements analysis also contains a sub-document \<^emph>\functions and interfaces\ (CENELEC notion) describing the technical format of the output of the odometry function. - This section, \eg, specifies the output \<^emph>\speed\ as given by a \<^verbatim>\int_32\ to be the + This section, \<^eg>, specifies the output \<^emph>\speed\ as given by a \<^verbatim>\int_32\ to be the ``Estimation of the speed (in mm/sec) evaluated over the latest $N_{\text{avg}}$ samples'' where the speed refers to the physical speed of the train and $N_{\text{avg}}$ a parameter of the sub-system configuration. \ @@ -143,7 +164,7 @@ text\ The design provides a function that manages an internal first-in-first-out buffer of shaft-encodings and corresponding positions. Central for the design is a step-function analyzing new incoming shaft encodings, checking them and propagating two kinds of error-states (one allowing - recovery, another one, fatal, signaling, \eg, a defect of the receiver hardware), + recovery, another one, fatal, signaling, \<^eg>, a defect of the receiver hardware), calculating the relative position, speed and acceleration. \ @@ -316,7 +337,7 @@ text\ \isadof is designed to annotate text elements with structured meta-information and to reference these text elements throughout the integrated source. A classical application of this capability is the annotation of concepts and terms definitions---be them informal, semi-formal or formal---and - their consistent referencing. In the context of our CENELEC ontology, \eg, we can translate the + their consistent referencing. In the context of our CENELEC ontology, \<^eg>, we can translate the third chapter of @{cite "bsi:50128:2014"} ``Terms, Definitions and Abbreviations'' directly into our Ontology Definition Language (ODL). Picking one example out of 49, consider the definition of the concept ``traceability'' in paragraphs 3.1.46 (a notion referenced 31 times in the standard), @@ -370,7 +391,7 @@ datatype vnt_technique = suggest that their work is superfluous. Our framework allows to statically check that tests or proofs have been provided, at places where the ontology requires them to be, and both assessors and developers can rely on this check and navigate through related information easily. It does not guarantee that - intended concepts for, \eg, safety or security have been adequately modeled. + intended concepts for, \<^eg>, safety or security have been adequately modeled. \ section*[moe::text_section] @@ -386,7 +407,7 @@ doc_class requirement = text_element + where the \inlineisar*roles* are exactly the ones defined in the previous section and represent the groups of stakeholders in the CENELEC process. Therefore, the \inlineisar+is_concerned+-attribute allows expressing who ``owns'' this text-element. \isadof supports a role-based -presentation, \eg, different presentation styles of the +presentation, \<^eg>, different presentation styles of the integrated source may decide to highlight, to omit, to defer into an annex, text entities according to the role-set. @@ -400,17 +421,17 @@ doc_class sub_requirement = section*[claimsreqevidence::text_section]\Tracking Claims, Derived Requirements and Evidence\ text\An example for making explicit implicit principles, -consider the following statement @{cite "bsi:50128:2014"}, pp. 25.:\vspace{-1.5mm} +consider the following statement @{cite "bsi:50128:2014"}, pp. 25.: \<^vs>\-0.15cm\ \begin{quote}\small The objective of software verification is to examine and arrive at a judgment based on evidence that output items (process, documentation, software or application) of a specific development phase fulfill the requirements and plans with respect to completeness, correctness and consistency. -\end{quote}\vspace{-1.5mm} +\end{quote} \<^vs>\-0.15cm\ The terms \<^emph>\judgment\ and \<^emph>\evidence\ are used as a kind of leitmotif throughout the CENELEC standard, but they are neither explained nor even listed in the general glossary. However, the standard is fairly explicit on the \<^emph>\phase\s and the organizational roles that different stakeholders -should have in the process. Our version to express this key concept of judgment, \eg, by +should have in the process. Our version to express this key concept of judgment, \<^eg>, by the following concept: \begin{isar} doc_class judgement = @@ -461,7 +482,7 @@ text*[J1::judgement, refers_to="<@>{docitem encoder_props}", \end{isar} The references \inlineisar|<@>{...}|, called antiquotation, allow us not only to reference to formal concepts, they are checked for consistency and there are also antiquotations that -print the formally checked content (\eg, the statement of a theorem). +print the formally checked content (\<^eg>, the statement of a theorem). \ subsection\Exporting Claims of the Requirements Specification.\ diff --git a/src/DOF/Isa_DOF.thy b/src/DOF/Isa_DOF.thy index 915e37a..26bad3c 100644 --- a/src/DOF/Isa_DOF.thy +++ b/src/DOF/Isa_DOF.thy @@ -2429,6 +2429,8 @@ val parse_cid = Scan.lift(Parse.position Args.name) val parse_oid' = Term_Style.parse -- parse_oid val parse_cid' = Term_Style.parse -- parse_cid + + val parse_attribute_access = (parse_oid --| (Scan.lift @{keyword "::"}) -- Scan.lift (Parse.position Args.name)) @@ -2473,6 +2475,25 @@ fun pretty_trace_style ctxt (style, (oid,pos)) = fun pretty_cid_style ctxt (style, (cid,pos)) = Document_Output.pretty_term ctxt (style (compute_cid_repr ctxt cid pos)); +(* NEW VERSION: PLEASE INTEGRATE ALL OVER : *) +fun context_position_parser parse_con (ctxt, toks) = + let val pos = case toks of + a :: _ => Token.pos_of a + | _ => @{here} \ \a real hack !\ + val (res, (ctxt', toks')) = parse_con (ctxt, toks) + in ((res,pos),(ctxt', toks')) end + +val parse_cid = (context_position_parser Args.typ_abbrev) + >> (fn (Type(ss,_),pos) => (pos,ss) + |( _,pos) => ISA_core.err "Undefined Class Id" pos); + + +val parse_cid' = Term_Style.parse -- parse_cid + +fun pretty_cid_style ctxt (style,(pos,cid)) = + (*reconversion to term in order to haave access to term print options like: short_names etc...) *) + Document_Output.pretty_term ctxt ((compute_cid_repr ctxt cid pos)); + in val _ = Theory.setup (ML_Antiquotation.inline \<^binding>\docitem\ @@ -2483,6 +2504,7 @@ val _ = Theory.setup (fn (ctxt,toks) => (parse_oid >> trace_attr_2_ML ctxt) (ctxt, toks)) #> basic_entity \<^binding>\trace_attribute\ parse_oid' pretty_trace_style #> basic_entity \<^binding>\doc_class\ parse_cid' pretty_cid_style #> + basic_entity \<^binding>\onto_class\ parse_cid' pretty_cid_style #> basic_entity \<^binding>\docitem_attribute\ parse_attribute_access' pretty_attr_access_style ) end diff --git a/src/ontologies/CENELEC_50128/CENELEC_50128.thy b/src/ontologies/CENELEC_50128/CENELEC_50128.thy index de97088..71fdee6 100644 --- a/src/ontologies/CENELEC_50128/CENELEC_50128.thy +++ b/src/ontologies/CENELEC_50128/CENELEC_50128.thy @@ -15,9 +15,9 @@ chapter \An Outline of a CENELEC Ontology\ text\ NOTE: An Ontology-Model of a certification standard such as CENELEC or Common Criteria identifies: -- notions (conceptual \emph{categories}) having \emph{instances} +- notions (conceptual \<^emph>\categories\) having \<^emph>\instances\ (similar to classes and objects), -- their subtype relation (eg., a "SRAC" is an "assumption"), +- their \<^emph>\subtype\ relation (eg., a "SRAC" is an "assumption"), - their syntactical structure (for the moment: defined by regular expressions describing the order of category instances in the overall document as a regular language) @@ -40,23 +40,78 @@ begin *) -text\We re-use the class @\typ math_content\, which provides also a framework for +text\We re-use the class \<^typ>\math_content\, which provides also a framework for semi-formal "math-alike" terminology, which we re-use by this definition.\ doc_class semi_formal_content = math_content + status :: status <= "semiformal" - mcc :: math_content_class <= "terminology" + mcc :: math_content_class + + type_synonym sfc = semi_formal_content -(*>>*) +doc_class cenelec_term = semi_formal_content + + mcc :: math_content_class <= "terminology" -declare[[ Definition_default_class="semi_formal_content"]] + +text\ in the following, all \<^theory_text>\Definition*\ statements are interpreted as + \<^doc_class>\cenelec_term\s, i.e. semi-formal teminological definitions.\ + +(* +ML\ +val typ_abbrev = Scan.lift +\ + +ML\ +Parse.position: ( Token.T list -> 'a * Token.T list) -> ('a * Position.T) parser; +Scan.lift(Parse.position Args.name) ; +Args.name_position; +Proof_Context.read_typ_abbrev; + + Args.typ_abbrev : Context.generic * Token.T list -> typ * (Context.generic * Token.T list) ; + + Proof_Context.read_typ_abbrev; + +(Args.typ_abbrev >> (fn Type(ss,_) => ss + | _ => error "Undefined Class Id")) + + +\ +ML\ + +fun context_position_parser parse_con (ctxt, toks) = + let val pos = case toks of + a :: _ => Token.pos_of a + | _ => @{here} \ \a real hack !\ + val (res, (ctxt', toks')) = parse_con (ctxt, toks) + in ((res,pos),(ctxt', toks')) end + +val parse_cid = (context_position_parser Args.typ_abbrev) + >> (fn (Type(ss,_),pos) => (pos,ss) + |( _,pos) => ISA_core.err "Undefined Class Id" pos); + + +val parse_cid' = Term_Style.parse -- parse_cid + +fun pretty_cid_style ctxt (style,(pos,cid)) = + (*reconversion to term in order to haave access to term print options like: short_names etc...) *) + Document_Output.pretty_term ctxt ((AttributeAccess.compute_cid_repr ctxt cid pos)); + +val _ = Theory.setup (AttributeAccess.basic_entity \<^binding>\Onto_class\ parse_cid' pretty_cid_style) + +\ + +text\ \<^Onto_class>\cenelec_term\ \ + +*) + +declare[[ Definition_default_class="cenelec_term"]] +(*>>*) text\ Excerpt of the BE EN 50128:2011, page 22. \ - section\Terms and Definitions\ Definition*[assessment,short_name="''assessment''"] @@ -66,90 +121,90 @@ requirements and to form a judgement as to whether the software is fit for its Safety assessment is focused on but not limited to the safety properties of a system.\ Definition*[assessor, short_name="''assessor''"] -\entity that carries out an assessment\ +\entity that carries out an assessment.\ Definition*[COTS, short_name="''commercial off-the-shelf software''"] \software defined by market-driven need, commercially available and whose fitness for purpose -has been demonstrated by a broad spectrum of commercial users\ +has been demonstrated by a broad spectrum of commercial users.\ Definition*[component] \a constituent part of software which has well-defined interfaces and behaviour with respect to the software architecture and design and fulfils the following criteria: -\<^enum> it is designed according to “Components” (see Table A.20); -\<^enum> it covers a specific subset of software requirements; -\<^enum> it is clearly identified and has an independent version inside the - configuration management system or is a part of a collection of components - (e. g. subsystems) which have an independent version + \<^enum> it is designed according to “Components” (see Table A.20); + \<^enum> it covers a specific subset of software requirements; + \<^enum> it is clearly identified and has an independent version inside the + configuration management system or is a part of a collection of components + (e. g. subsystems) which have an independent version \ typ "sfc" Definition*[CMGR, short_name="''configuration manager''"] \entity that is responsible for implementing and carrying out the processes for the configuration management of documents, software and related tools including -\<^emph>\change management\\ +\<^emph>\change management\.\ Definition*[customer] -\entity which purchases a railway control and protection system including the software\ +\entity which purchases a railway control and protection system including the software.\ Definition*[designer] \entity that analyses and transforms specified requirements into acceptable design solutions -which have the required safety integrity level\ +which have the required safety integrity level.\ Definition*[entity] -\person, group or organisation who fulfils a role as defined in this European Standard\ +\person, group or organisation who fulfils a role as defined in this European Standard.\ declare_reference*[fault] Definition*[error] \defect, mistake or inaccuracy which could result in failure or in a deviation -from the intended performance or behaviour (cf. @{semi_formal_content (unchecked) \fault\}))\ +from the intended performance or behaviour (cf. @{cenelec_term (unchecked) \fault\})).\ Definition*[fault] \defect, mistake or inaccuracy which could result in failure or in a deviation -from the intended performance or behaviour (cf @{semi_formal_content \error\})\ +from the intended performance or behaviour (cf @{cenelec_term \error\}).\ Definition*[failure] -\unacceptable difference between required and observed performance\ +\unacceptable difference between required and observed performance.\ Definition*[FT, short_name="''fault tolerance''"] \built-in capability of a system to provide continued correct provision of service as specified, -in the presence of a limited number of hardware or software faults\ +in the presence of a limited number of hardware or software faults.\ Definition*[firmware] \software stored in read-only memory or in semi-permanent storage such as flash memory, in a -way that is functionally independent of applicative software\ +way that is functionally independent of applicative software.\ Definition*[GS,short_name="''generic software''"] \software which can be used for a variety of installations purely by the provision of -application-specific data and/or algorithms\ +application-specific data and/or algorithms.\ Definition*[implementer] -\entity that transforms specified designs into their physical realisation\ +\entity that transforms specified designs into their physical realisation.\ Definition*[integration] \process of assembling software and/or hardware items, according to the architectural and -design specification, and testing the integrated unit\ +design specification, and testing the integrated unit.\ Definition*[integrator] -\entity that carries out software integration\ +\entity that carries out software integration.\ -Definition*[PES :: sfc, short_name="''pre-existing software''"] +Definition*[PES, short_name="''pre-existing software''"] \software developed prior to the application currently in question, including COTS (commercial -off-the shelf) and open source software\ +off-the shelf) and open source software.\ -Definition*[OSS :: sfc, short_name="''open source software''"] -\source code available to the general public with relaxed or non-existent copyright restrictions\ +Definition*[OS, short_name="''open source software''"] +\source code available to the general public with relaxed or non-existent copyright restrictions.\ Definition*[PLC, short_name="''programmable logic controller''"] \solid-state control system which has a user programmable memory for storage of instructions to -implement specific functions\ +implement specific functions.\ Definition*[PM, short_name="''project management''"] -\administrative and/or technical conduct of a project, including safety aspects\ +\administrative and/or technical conduct of a project, including safety aspects.\ Definition*[PMGR, short_name="''project manager''"] -\entity that carries out project management\ +\entity that carries out \<^cenelec_term>\PM\.\ Definition*[reliability] \ability of an item to perform a required function under given conditions for a given period of time\ @@ -157,52 +212,52 @@ Definition*[reliability] Definition*[robustness] \ability of an item to detect and handle abnormal situations\ -Definition*[RMGR, short_name="''requirements manager''"] -\entity that carries out requirements management\ - Definition*[RM, short_name="''requirements management''"] \the process of eliciting, documenting, analysing, prioritising and agreeing on requirements and then controlling change and communicating to relevant stakeholders. It is a continuous process throughout a project\ +Definition*[RMGR, short_name="''requirements manager''"] +\entity that carries out \<^cenelec_term>\RM\.\ + Definition*[risk] \combination of the rate of occurrence of accidents and incidents resulting in harm (caused by -a hazard) and the degree of severity of that harm\ +a hazard) and the degree of severity of that harm.\ Definition*[safety] -\freedom from unacceptable levels of risk of harm to people\ +\freedom from unacceptable levels of risk of harm to people.\ Definition*[SA, short_name="''safety authority''"] \body responsible for certifying that safety related software or services comply with relevant -statutory safety requirements\ +statutory safety requirements.\ Definition*[SF, short_name="''safety function''"] -\a function that implements a part or whole of a safety requirement\ +\a function that implements a part or whole of a safety requirement.\ Definition*[SFRS, short_name= "''safety-related software''"] -\software which performs safety functions\ +\software which performs safety functions.\ Definition*[software] \intellectual creation comprising the programs, procedures, rules, data and any associated -documentation pertaining to the operation of a system\ +documentation pertaining to the operation of a system.\ Definition*[SB, short_name="''software baseline''"] \complete and consistent set of source code, executable files, configuration files, installation scripts and documentation that are needed for a software release. Information about compilers, operating systems, preexisting software and dependent tools is stored as part of the baseline. This will enable the organisation to reproduce defined versions and be the input -for future releases at enhancements or at upgrade in the maintenance phase\ +for future releases at enhancements or at upgrade in the maintenance phase.\ Definition*[SD, short_name="''software deployment''"] \transferring, installing and activating a deliverable software baseline that has already been -released and assessed\ +released and assessed.\ Definition*[SWLC, short_name="''software life-cycle''"] \those activities occurring during a period of time that starts when software is conceived and ends when the software is no longer available for use. The software life -cycle typically includes a requirements phase, design phase,test phase, integration phase, -deployment phase and a maintenance phase\ +cycle typically includes a requirements phase, design phase, test phase, integration phase, +deployment phase and a maintenance phase.\ Definition*[SWMA, short_name="''software maintainability''"] \capability of the software to be modified; to correct faults, @@ -210,11 +265,12 @@ improve performance or other attributes, or adapt it to a different environment\ Definition*[SM, short_name="''software maintenance''"] \ action, or set of actions, carried out on software after deployment functionality -performance or other attributes, or adapt it with the aim of enhancing or correcting its\ +performance or other attributes, or adapt it with the aim of enhancing or correcting its behaviour.\ Definition*[SOSIL, short_name="''software safety integrity level''"] \classification number which determines the techniques and measures that have to be applied to -software +software. + NOTE: Safety-related software has been classified into five safety integrity levels, where 0 is the lowest and 4 the highest.\ @@ -255,16 +311,16 @@ not obvious; a compiler that incorporates an executable run-time package into th Definition*[traceability, short_name="''traceability''"] \degree to which relationship can be established between two or more products of a development process, especially those having a predecessor/successor or master/subordinate relationship to one -another\ +another.\ Definition*[validation, short_name="''validation''"] \process of analysis followed by a judgment based on evidence to documentation, software or application) fits the user needs,in particular with respect to safety and quality and determine whether an item (e.g. process, with emphasis on the suitability of its -operation in accordance to its purpose in its intended environment\ +operation in accordance to its purpose in its intended environment.\ Definition*[validator, short_name="''validator''"] -\entity that is responsible for the validation\ +\entity that is responsible for the validation.\ Definition*[verification, short_name="''verification''"] \process of examination followed by a judgment based on evidence that output items (process, @@ -275,13 +331,13 @@ NOTE: Verification is mostly based on document reviews \ Definition*[verifier, short_name="''verifier''"] -\entity that is responsible for one or more verification activities\ +\entity that is responsible for one or more verification activities.\ chapter\Software Management and Organisation\ text\Representing chapter 5 in @{cite "bsi:50128:2014"}.\ section\Organization, Roles and Responsabilities\ -text\See also section \<^emph>\Software management and organization\. and Annex B and C\ +text\See also section \<^emph>\Software management and organization\ and Annex B and C.\ text\REQ role in Table C.1 is assumed to be a typo and should be RQM.\ @@ -300,17 +356,17 @@ datatype role = RQM \ \Requirements Manager\ datatype phase = SYSDEV_ext \ \ System Development Phase (external)\ - | SPl \ \Software Planning\ - | SR \ \Software Requirements\ - | SADES \ \Software Architecture and Design\ - | SCDES \ \Software Component Design\ - | CInT \ \Component Implementation and Testing\ - | SI \ \Software Integration\ - | SV \ \Overall Software Testing/Final Validation\ - | SCADA \ \Systems Configured by Application Data/Algorithms\ - | SD \ \Software Deployment\ - | SM \ \Software Maintenance\ - | SA \ \Software Assessment\ + | SPl \ \Software Planning\ + | SR \ \Software Requirements\ + | SADES \ \Software Architecture and Design\ + | SCDES \ \Software Component Design\ + | CInT \ \Component Implementation and Testing\ + | SI \ \Software Integration\ + | SV \ \Overall Software Testing/Final Validation\ + | SCADA \ \Systems Configured by Application Data/Algorithms\ + | SD \ \Software Deployment\ + | SM \ \Software Maintenance\ + | SA \ \Software Assessment\ abbreviation software_planning :: "phase" where "software_planning \ SPl" abbreviation software_requirements :: "phase" where "software_requirements \ SR" @@ -340,7 +396,7 @@ text\Requirement levels specified Annex A: we use the term \<^emph>\ them from the requirements specified in the standard.\ datatype normative_level = - M \ \(Mandatory)\ + M \ \(Mandatory)\ | HR \ \Highly Recommended\ | R \ \Recommended\ | Any \ \No recommendation\ @@ -365,14 +421,15 @@ doc_class safety_requirement = requirement + formal_definition :: "thm list" -text\The category @{emph \hypothesis\} is used for assumptions from the - foundational mathematical or physical domain, so for example: - \<^item> the Mordell-Lang conjecture holds, - \<^item> euklidian geometry is assumed, or - \<^item> Newtonian (non-relativistic) physics is assumed, - Their acceptance is inherently outside the scope of the model - and can only established inside certification process by - authority argument. +text\ +The category \<^emph>\hypothesis\ is used for assumptions from the +foundational mathematical or physical domain, so for example: + \<^item> the Mordell-Lang conjecture holds, + \<^item> euklidian geometry is assumed, or + \<^item> Newtonian (non-relativistic) physics is assumed, +Their acceptance is inherently outside the scope of the model +and can only established inside certification process by +authority argument. \ datatype hyp_type = physical | mathematical | computational | other @@ -384,7 +441,7 @@ doc_class hypothesis = requirement + hyp_type :: hyp_type <= physical (* default *) text\ The following sub-class of security related hypothesis might comprise, for example: - \<^item> @{term "P \ NP"}, + \<^item> \<^term>\P \ NP\, \<^item> or the computational hardness of certain functions relevant for cryptography (like prime-factorization). (* speculation bu, not 50128 *)\ @@ -469,7 +526,7 @@ figure*[fig3::figure, relative_width="100", \Illustrative Development Lifecycle 1\ text\Actually, the Figure 4 in Chapter 5: Illustrative Development Lifecycle 2 is more fidele -to the remaining document: Software Architecture and Dediwn phases are merged, like in 7.3.\ +to the remaining document: Software Architecture and Design phases are merged, like in 7.3.\ section\Software Assurance related Entities and Concepts\ @@ -541,8 +598,9 @@ doc_class judgement = status :: status is_concerned :: "role set" <= "{VER,ASR,VAL}" -section\ Design and Test Documents \ +section\ A Classification of CENELEC Reports and Documents \ +(* should we rename this as "report" ??? bu *) doc_class cenelec_document = text_element + phase :: "phase" sil :: "sil" @@ -680,7 +738,7 @@ doc_class SWADVR = cenelec_document + phase :: "phase" <= "SADES" nlvl :: "normative_level" <= "HR" invariant force_nlvl_swadvr :: "nlvl \ = HR" - type_synonym software_architecture_and_design_verification_report = SWADVR + type_synonym software_architecture_and_design_verification = SWADVR doc_class SWCDS = cenelec_document + phase :: "phase" <= "SCDES" @@ -695,7 +753,7 @@ doc_class SWCTS = cenelec_document + doc_class SWCDVR = cenelec_document + phase :: "phase" <= "SCDES" invariant force_nlvl_swcdvr :: "if sil \ = SIL0 then nlvl \ = R else nlvl \ = HR" - type_synonym software_component_design_verification_report = SWCDVR + type_synonym software_component_design_verification = SWCDVR doc_class SWSCD = cenelec_document + phase :: "phase" <= "CInT"