| <?xml version="1.0" encoding="UTF-8"?>
|
| <?eclipse version="3.4"?>
|
| <plugin>
|
| <extension
|
| point="org.eclipse.amalgam.explorer.activity.ui.pagesProvider">
|
| <Page
|
| class="org.eclipse.opencert.infra.dashboard.pages.DashboardWorkflowPage"
|
| id="org.eclipse.opencert.infra.dashboard.pages.dashboard"
|
| imageOff="icons/workflow/workflow_off.png"
|
| imageOn="icons/workflow/workflow_on.png"
|
| index="0"
|
| tabName="Workflow"
|
| title="Workflow"
|
| viewer="false">
|
| <Description>
|
| Dashboard in OpenCert
|
| </Description>
|
| <Predicate
|
| class="org.eclipse.opencert.infra.dashboard.predicates.DashboardPredicate">
|
| </Predicate>
|
| </Page>
|
| <Page
|
| class="org.eclipse.opencert.infra.dashboard.pages.StandardComplianceDefinitionPage"
|
| id="org.eclipse.opencert.infra.dashboard.pages.standard.compliance.definition.page"
|
| imageOff="icons/standardcompliance/standard_compliance_def_off.png"
|
| imageOn="icons/standardcompliance/standard_compliance_def_on.png"
|
| index="1"
|
| tabName="Standard Compliance Definition"
|
| title="Standard Compliance Definition"
|
| viewer="true">
|
| <Description>
|
| Project independent activities capture, digitalize, store and retrieve standard compliance knowledge. Specify reusable compliant process associated with a specific standard.
|
| </Description>
|
| <Predicate
|
| class="org.eclipse.opencert.infra.dashboard.predicates.DashboardPredicate">
|
| </Predicate>
|
| <Overview
|
| imageOff="icons/standardcompliance/standard_compliance_def_off.png"
|
| imageOn="icons/standardcompliance/standard_compliance_def_on.png">
|
| <Description>
|
| Define the standard compliance.
|
| </Description>
|
| </Overview>
|
| <Section
|
| expanded="true"
|
| filtering="true"
|
| id="org.eclipse.opencert.infra.dashboard.section.modelling.standards"
|
| index="0"
|
| name="Modelling Standards">
|
| <Description>
|
| Digitalize the standards, regulations, guidelines, best practices into a model. This can be done in a reference framework by the Assurance Manager who is an expert in standards appliance and/or a process engineer, who can model the process implicitly on a standard.
|
| </Description>
|
| <Activity
|
| class="org.eclipse.opencert.infra.dashboard.pages.adapters.OpenNewRefframeworkDiagramWizard"
|
| id="org.eclipse.opencert.infra.dashboard.activity.model.new.standard"
|
| image="icons/standardcompliance/refframework_diagram_icon.png"
|
| index="0"
|
| name="Model a new standard/regulation/guideline">
|
| <Description>
|
| Model a new standard, a new regulation or a new guideline.
|
| </Description>
|
| </Activity>
|
| <Activity
|
| class="org.eclipse.opencert.infra.dashboard.pages.adapters.OpenNewMethodLibraryWizard"
|
| id="org.eclipse.opencert.infra.dashboard.activity.modelling.processes.definition"
|
| image="icons/standardcompliance/method_library_icon.png"
|
| index="1"
|
| name="Modelling of processes definitions mandated by standards">
|
| <Description>
|
| Modelling of processes definitions mandated by standards.
|
| </Description>
|
| </Activity>
|
| </Section>
|
| <Section
|
| expanded="true"
|
| filtering="true"
|
| id="org.eclipse.opencert.infra.dashboard.section.standard.compliance.definition.reuse"
|
| index="1"
|
| name="Reuse">
|
| <Description>
|
| The Process Engineer can reuse existing process elements. The Assurance Manager indicates the equivalences between different standards already modelled as reference frameworks.
|
| </Description>
|
| <Activity
|
| id="org.eclipse.opencert.infra.dashboard.activity.modelling.reusable.process.elements"
|
| index="0"
|
| name="Modelling of reusable process elements">
|
| <Description>
|
| Modelling of reusable process elements.
|
| </Description>
|
| </Activity>
|
| <Activity
|
| id="org.eclipse.opencert.infra.dashboard.activity.modelling.reusable.process.patterns"
|
| index="1"
|
| name="Modelling of reusable process patterns">
|
| <Description>
|
| Modelling of reusable process patterns.
|
| </Description>
|
| </Activity>
|
| <Activity
|
| class="org.eclipse.opencert.infra.dashboard.pages.adapters.OpenMappingSetDialogHyperLinkAdapter"
|
| id="org.eclipse.opencert.infra.dashboard.activity.map.equivalences.standard"
|
| image="icons/standardcompliance/equivalence_mapping_icon.png"
|
| index="2"
|
| name="Map equivalences between standards">
|
| <Description>
|
| Map equivalences between standards.
|
| </Description>
|
| </Activity>
|
| </Section>
|
| </Page>
|
| <Page
|
| class="org.eclipse.opencert.infra.dashboard.pages.AssuranceProjectDefinitionPage"
|
| id="org.eclipse.opencert.infra.dashboard.pages.assurance.project.definition.page"
|
| imageOff="icons/assuranceproject/assurance_project_def_off.png"
|
| imageOn="icons/assuranceproject/assurance_project_def_on.png"
|
| index="2"
|
| tabName="Assurance Project Definition"
|
| title="Assurance Project Definition"
|
| viewer="true">
|
| <Description>
|
| Define the scope of compliance for a project, project compliance lifecycle, reuse possibilities and compliance means.
|
| </Description>
|
| <Predicate
|
| class="org.eclipse.opencert.infra.dashboard.predicates.DashboardPredicate">
|
| </Predicate>
|
| <Overview
|
| imageOff="icons/assuranceproject/assurance_project_def_off.png"
|
| imageOn="icons/assuranceproject/assurance_project_def_on.png">
|
| <Description>
|
| Define a new assurance project.
|
| </Description>
|
| </Overview>
|
| <Section
|
| expanded="true"
|
| filtering="true"
|
| id="org.eclipse.opencert.infra.dashboard.section.create.assurance.project"
|
| index="0"
|
| name="Create Assurance Project">
|
| <Description>
|
| The Assurance Manager can maintain the lifecycle of projects by creating Assurance Projects and system design projects associated.
|
| </Description>
|
| <Activity
|
| class="org.eclipse.opencert.infra.dashboard.pages.adapters.OpenNewAssuranceProjectWizard"
|
| id="org.eclipse.opencert.infra.dashboard.activity.create.assurance.project"
|
| image="icons/assuranceproject/assurance_project_icon.png"
|
| index="0"
|
| name="Create a new assurance project">
|
| <Description>
|
| Open a wizard to create a new assurance project.
|
| </Description>
|
| </Activity>
|
| <Activity
|
| class="org.eclipse.opencert.infra.dashboard.pages.adapters.OpenNewChessProjectWizard"
|
| id="org.eclipse.opencert.infra.dashboard.activity.create.chess.project"
|
| image="icons/assuranceproject/chess_project_icon.png"
|
| index="1"
|
| name="Create a system architecture design">
|
| <Description>
|
| Open a wizard to create a new Chess project.
|
| </Description>
|
| </Activity>
|
| </Section>
|
| <Section
|
| expanded="true"
|
| filtering="true"
|
| id="org.eclipse.opencert.infra.dashboard.section.define.compliance.baseline"
|
| index="1"
|
| name="Define Compliance Baseline">
|
| <Description>
|
| The Assurance Manager can manage the lifecycle of projects by updating previous defined compliance plan of a project.
|
| </Description>
|
| <Activity
|
| id="org.eclipse.opencert.infra.dashboard.activity.create.update.baseline"
|
| index="0"
|
| name="Create or update a baseline">
|
| <Description>
|
| A baseline configuration has a set of baseline models. A baseline model represents what is planned to comply with, in a specific assurance project.
|
| </Description>
|
| </Activity>
|
| </Section>
|
| <Section
|
| expanded="true"
|
| filtering="true"
|
| id="org.eclipse.opencert.infra.dashboard.section.assurance.project.definition.reuse"
|
| index="2"
|
| name="Reuse">
|
| <Description>
|
| The Assurance Manager can reuse the assurance assets from one assurance project to another or reuse artefacts between projects according to the equivalence maps.
|
| </Description>
|
| <Activity
|
| id="org.eclipse.opencert.infra.dashboard.activity.cross.system.reuse"
|
| index="0"
|
| name="Cross system reuse">
|
| <Description>
|
| Cross system reuse.
|
| </Description>
|
| </Activity>
|
| <Activity
|
| id="org.eclipse.opencert.infra.dashboard.activity.cross.standard.reuse"
|
| index="1"
|
| name="Cross standard reuse">
|
| <Description>
|
| Cross standard reuse.
|
| </Description>
|
| </Activity>
|
| </Section>
|
| </Page>
|
| <Page
|
| class="org.eclipse.opencert.infra.dashboard.pages.ProcessComplianceDefinitionPage"
|
| id="org.eclipse.opencert.infra.dashboard.pages.process.compliance.definition.page"
|
| imageOff="icons/processcompliance/process_compliance_def_off.png"
|
| imageOn="icons/processcompliance/process_compliance_def_on.png"
|
| index="3"
|
| tabName="Process Compliance Definition"
|
| title="Process Compliance Definition"
|
| viewer="true">
|
| <Description>
|
| Validate process reusability, deploy executable process.
|
| </Description>
|
| <Predicate
|
| class="org.eclipse.opencert.infra.dashboard.predicates.DashboardPredicate">
|
| </Predicate>
|
| <Overview
|
| imageOff="icons/processcompliance/process_compliance_def_off.png"
|
| imageOn="icons/processcompliance/process_compliance_def_on.png">
|
| <Description>
|
| Define the process compliance.
|
| </Description>
|
| </Overview>
|
| <Section
|
| expanded="true"
|
| filtering="true"
|
| id="org.eclipse.opencert.infra.dashboard.section.specify.compliance.process"
|
| index="0"
|
| name="Specify Compliance Process">
|
| <Description>
|
| The Process Engineer can import existing processes and resolve the variability due to safety/security appliance.
|
| </Description>
|
| <Activity
|
| id="org.eclipse.opencert.infra.dashboard.activity.export.definition.planning"
|
| index="0"
|
| name="Export the definition and planning of processes modelled ">
|
| <Description>
|
| Export the definition and planning of processes modelled.
|
| </Description>
|
| </Activity>
|
| <Activity
|
| id="org.eclipse.opencert.infra.dashboard.import.definition.planning"
|
| index="1"
|
| name="Import the definition and planning of processes modelled into an assurance project">
|
| <Description>
|
| Import the definition and planning of processes modelled into an assurance project.
|
| </Description>
|
| </Activity>
|
| </Section>
|
| <Section
|
| expanded="true"
|
| filtering="true"
|
| id="org.eclipse.opencert.infra.dashboard.section.reuse.process.development"
|
| index="1"
|
| name="Reuse Process Development">
|
| <Description>
|
| The Process Engineer instantiate the reusable generic base process developed to a project specific process. A check is necessary to be sure that the assumptions for the reused activities are valid for the new project.
|
| </Description>
|
| <Activity
|
| id="org.eclipse.opencert.infra.dashboard.activity.derivate.project.specific.process"
|
| index="0"
|
| name="Derivate project specific process">
|
| <Description>
|
| Derivate project specific process.
|
| </Description>
|
| </Activity>
|
| <Activity
|
| id="org.eclipse.opencert.infra.dashboard.activity.check.process.reusability"
|
| index="1"
|
| name="Check process reusability">
|
| <Description>
|
| Check process reusability.
|
| </Description>
|
| </Activity>
|
| </Section>
|
| <Section
|
| expanded="true"
|
| filtering="true"
|
| id="org.eclipse.opencert.infra.dashboard.section.coassessment"
|
| index="2"
|
| name="Co-Assessment">
|
| <Description>
|
| The Process Engineer takes the modelling the definition and planning of processes already defined in EPF and import it into OpenCert in order to look at post-planning phases.
|
| </Description>
|
| <Activity
|
| id="org.eclipse.opencert.infra.dashboard.activity.coassessment.cross.system.reuse."
|
| index="0"
|
| name="Cross system reuse">
|
| <Description>
|
| Cross system reuse.
|
| </Description>
|
| </Activity>
|
| <Activity
|
| id="org.eclipse.opencert.infra.dashboard.activity.coassessment.cross.standard.reuse"
|
| index="1"
|
| name="Cross standard reuse">
|
| <Description>
|
| Cross standard reuse.
|
| </Description>
|
| </Activity>
|
| </Section>
|
| </Page>
|
| <Page
|
| class="org.eclipse.opencert.infra.dashboard.pages.SystemDesignAnalysisVVPage"
|
| id="org.eclipse.opencert.infra.dashboard.pages.system.design.analysis.vv"
|
| imageOff="icons/systemdesignanalysis/system_design_analysis_vv_off.png"
|
| imageOn="icons/systemdesignanalysis/system_design_analysis_vv_on.png"
|
| index="4"
|
| tabName="System Design Analysis and V&V"
|
| title="System Design Analysis and V&V"
|
| viewer="true">
|
| <Description>
|
| Define the system architecture, elicit system requirements, define and validate component contracts and execute Safety/Security analyses.
|
| </Description>
|
| <Predicate
|
| class="org.eclipse.opencert.infra.dashboard.predicates.DashboardPredicate">
|
| </Predicate>
|
| <Overview
|
| imageOff="icons/systemdesignanalysis/system_design_analysis_vv_off.png"
|
| imageOn="icons/systemdesignanalysis/system_design_analysis_vv_on.png">
|
| <Description>
|
| System design, analysis, validation and verification
|
| </Description>
|
| </Overview>
|
| <Section
|
| expanded="true"
|
| filtering="true"
|
| id="org.eclipse.opencert.infra.dashboard.section.system.definition"
|
| index="0"
|
| name="System Definition">
|
| <Description>
|
| The development engineer uses SysML BDD, IBD and Requirements Diagrams, possibility to import requirements from external tools, formalization of requirements supported with syntax-driven editors.
|
| </Description>
|
| <Activity
|
| class="org.eclipse.opencert.infra.dashboard.pages.adapters.OpenNewChessProjectWizard"
|
| id="org.eclipse.opencert.infra.dashboard.activity.create.chess.project"
|
| image="icons/assuranceproject/chess_project_icon.png"
|
| index="0"
|
| name="Create a Papyrus CHESS project">
|
| <Description>
|
| Create a Papyrus CHESS project.
|
| </Description>
|
| </Activity>
|
| <Activity
|
| id="org.eclipse.opencert.infra.dashboard.activity.create.savona.project"
|
| index="1"
|
| name="Create a SAVONA project">
|
| <Description>
|
| Create a SAVONA project.
|
| </Description>
|
| </Activity>
|
| <Activity
|
| class="org.eclipse.opencert.infra.dashboard.pages.adapters.CreateNewChessRequirementDiagram"
|
| id="org.eclipse.opencert.infra.dashboard.activity.specify.requirements.chess"
|
| image="icons/systemdesignanalysis/requirement_diagram.png"
|
| index="2"
|
| name="Specify requirements in Papyrus CHESS">
|
| <Description>
|
| Specify requirements in Papyrus CHESS.
|
| </Description>
|
| </Activity>
|
| <Activity
|
| class="org.eclipse.opencert.infra.dashboard.pages.adapters.OpenImportUserModelDialogHyperLinkAdapter"
|
| id="org.eclipse.opencert.infra.dashboard.activity.import.requirements.chess"
|
| image="icons/systemdesignanalysis/requirement_diagram.png"
|
| index="3"
|
| name="Import system entities/requirements from a Papyrus CHESS model">
|
| <Description>
|
| Import requirements in Papyrus CHESS.
|
| </Description>
|
| </Activity>
|
| <Activity
|
| class="org.eclipse.opencert.infra.dashboard.pages.adapters.CreateNewChessBlockDefinitionDiagram"
|
| id="org.eclipse.opencert.infra.dashboard.activity.create.system.components.chess"
|
| image="icons/systemdesignanalysis/block_definition_diagram.png"
|
| index="4"
|
| name="Create system components in Papyrus CHESS">
|
| <Description>
|
| Create system components in Papyrus CHESS
|
| </Description>
|
| </Activity>
|
| <Activity
|
| id="org.eclipse.opencert.infra.dashboard.activity.import.savona.model"
|
| index="5"
|
| name="Import a SAVONA model in Papyrus CHESS">
|
| <Description>
|
| Import a SAVONA model in Papyrus CHESS.
|
| </Description>
|
| </Activity>
|
| </Section>
|
| <Section
|
| expanded="true"
|
| filtering="true"
|
| id="org.eclipse.opencert.infra.dashboard.section.requirements.formalization.early.validation"
|
| index="1"
|
| name="Requirements Formalization and Early Validation">
|
| <Description>
|
| Formal semantic analysis of formal properties, analysis of requirements quality with machine learning techniques and requirements quality metrics editors.
|
| </Description>
|
| <Activity
|
| id="org.eclipse.opencert.infra.dashboard.activity.analysis.requirements.metric"
|
| index="0"
|
| name="Analysis of requirements based on quality metrics">
|
| <Description>
|
| Analysis of requirements based on quality metrics.
|
| </Description>
|
| </Activity>
|
| <Activity
|
| id="org.eclipse.opencert.infra.dashboard.activity.formalize.requirements.temporal.logic"
|
| index="1"
|
| name="Formalize a requirement into temporal logics in Papyrus CHESS">
|
| <Description>
|
| Formalize a requirements into temporal logics in Papyrus CHESS.
|
| </Description>
|
| </Activity>
|
| <Activity
|
| id="org.eclipse.opencert.infra.dashboard.activity.formalize.requirements.savona"
|
| index="2"
|
| name="Formalize a requirement in SAVONA">
|
| <Description>
|
| Formalize a requirement in SAVONA.
|
| </Description>
|
| </Activity>
|
| <Activity
|
| id="org.eclipse.opencert.infra.dashboard.activity.define.contract.component.chess"
|
| index="3"
|
| name="Define a contract for a component in Papyrus CHESS">
|
| <Description>
|
| Define a contract for a component in Papyrus CHESS.
|
| </Description>
|
| </Activity>
|
| <Activity
|
| id="org.eclipse.opencert.infra.dashboard.activity.analysis.requirements.semantics"
|
| index="4"
|
| name="Analysis of requirements’ semantics based on their formalisation into temporal logics">
|
| <Description>
|
| Analysis of requirements’ semantics based on their formalisation into temporal logics.
|
| </Description>
|
| </Activity>
|
| </Section>
|
| <Section
|
| expanded="true"
|
| filtering="true"
|
| id="org.eclipse.opencert.infra.dashboard.section.functional.refinement"
|
| index="2"
|
| name="Functional Refinement">
|
| <Description>
|
| Using SysML IBD extended with contracts.
|
| </Description>
|
| <Activity
|
| id="org.eclipse.opencert.infra.dashboard.activity.decompose.component.chess"
|
| index="0"
|
| name="Decompose a component in Papyrus CHESS">
|
| <Description>
|
| Decompose a component in Papyrus CHESS.
|
| </Description>
|
| </Activity>
|
| <Activity
|
| id="org.eclipse.opencert.infra.dashboard.activity.decompose.component.savona"
|
| index="1"
|
| name="Decompose a component in SAVONA">
|
| <Description>
|
| Decompose a component in SAVONA.
|
| </Description>
|
| </Activity>
|
| <Activity
|
| id="org.eclipse.opencert.infra.dashboard.activity.model.contracts.refinement.chess"
|
| index="2"
|
| name="Model contracts refinement in Papyrus CHESS">
|
| <Description>
|
| Model contracts refinement in Papyrus CHESS.
|
| </Description>
|
| </Activity>
|
| <Activity
|
| id="org.eclipse.opencert.infra.dashboard.activity.model.contracts.refinement.savona"
|
| index="3"
|
| name="Model contracts refinement in SAVONA">
|
| <Description>
|
| Model contracts refinement in SAVONA.
|
| </Description>
|
| </Activity>
|
| <Activity
|
| id="org.eclipse.opencert.infra.dashboard.activity.apply.architectural.patterns.chess"
|
| index="4"
|
| name="Apply architectural patterns in Papyrus CHESS">
|
| <Description>
|
| Apply architectural patterns in Papyrus CHESS.
|
| </Description>
|
| </Activity>
|
| <Activity
|
| id="org.eclipse.opencert.infra.dashboard.activity.specify.parameters.chess"
|
| index="5"
|
| name="Specify parameters of the parameterized architecture in Papyrus CHESS">
|
| <Description>
|
| Specify parameters of the parameterized architecture in Papyrus CHESS.
|
| </Description>
|
| </Activity>
|
| <Activity
|
| id="org.eclipse.opencert.infra.dashboard.activity.instantiate.parameterized.architecture.chess"
|
| index="6"
|
| name="Instantiate a parameterized architecture in Papyrus CHESS">
|
| <Description>
|
| Instantiate a parameterized architecture in Papyrus CHESS.
|
| </Description>
|
| </Activity>
|
| </Section>
|
| <Section
|
| expanded="true"
|
| filtering="true"
|
| id="org.eclipse.opencert.infra.dashboard.section.components.nominal.faulty.behaviour.definition"
|
| index="3"
|
| name="Component's Nominal and Faulty Behaviour Definition">
|
| <Description>
|
| Using State Machines or Simulink models extended with fault injection.
|
| </Description>
|
| <Activity
|
| id="org.eclipse.opencert.infra.dashboard.activity.define.nominal.statemachine.chess"
|
| index="0"
|
| name="Define a nominal state machine for a component in Papyrus CHESS">
|
| <Description>
|
| Define a nominal state machine for a component in Papyrus CHESS.
|
| </Description>
|
| </Activity>
|
| <Activity
|
| id="org.eclipse.opencert.infra.dashboard.activity.define.error.statemachine.chess"
|
| index="1"
|
| name="Define an error state machine for a component in Papyrus CHESS">
|
| <Description>
|
| Define an error state machine for a component in Papyrus CHESS.
|
| </Description>
|
| </Activity>
|
| <Activity
|
| id="org.eclipse.opencert.infra.dashboard.activity.define.failure.progation.rule.chess"
|
| index="2"
|
| name="Define a failure propagation rule for a component in Papyrus CHESS">
|
| <Description>
|
| Define a failure propagation rule for a component in Papyrus CHESS.
|
| </Description>
|
| </Activity>
|
| </Section>
|
| <Section
|
| expanded="true"
|
| filtering="true"
|
| id="org.eclipse.opencert.infra.dashboard.section.functional.early.verification"
|
| index="4"
|
| name="Functional Early Verification">
|
| <Description>
|
| Contract-based Verification of refinement and state-machines, Model Checking, Contract-based Monitoring of Simulink models, Contract-based Verification of Refinement with Strong and Weak Contracts.
|
| </Description>
|
| <Activity
|
| id="org.eclipse.opencert.infra.dashboard.activity.contractbased.verification.refinement"
|
| index="0"
|
| name="Contract-based verification of refinement">
|
| <Description>
|
| Contract-based verification of refinement.
|
| </Description>
|
| </Activity>
|
| <Activity
|
| id="org.eclipse.opencert.infra.dashboard.activity.contractbased.verification.statemachines"
|
| index="1"
|
| name="Contract-based verification of state machines">
|
| <Description>
|
| Contract-based verification of state machines.
|
| </Description>
|
| </Activity>
|
| <Activity
|
| id="org.eclipse.opencert.infra.dashboard.activity.model.checking"
|
| index="2"
|
| name="Model checking">
|
| <Description>
|
| Model checking.
|
| </Description>
|
| </Activity>
|
| <Activity
|
| id="org.eclipse.opencert.infra.dashboard.activity.contractbased.monitoring.simulink"
|
| index="3"
|
| name="Contract-based monitoring with Simulink">
|
| <Description>
|
| Contract-based monitoring with Simulink.
|
| </Description>
|
| </Activity>
|
| <Activity
|
| id="org.eclipse.opencert.infra.dashboard.activity.contractbased.verification.refinement.strong.weak"
|
| index="4"
|
| name="Contract-based verification of refinement for strong and weak contracts">
|
| <Description>
|
| Contract-based verification of refinement for strong and weak contracts.
|
| </Description>
|
| </Activity>
|
| <Activity
|
| id="org.eclipse.opencert.infra.dashboard.activity.contractbased.tradeoff.analysis"
|
| index="5"
|
| name="Contract-based trade-off analysis in parameterized architectures">
|
| <Description>
|
| Contract-based trade-off analysis in parameterized architectures.
|
| </Description>
|
| </Activity>
|
| </Section>
|
| <Section
|
| expanded="true"
|
| filtering="true"
|
| id="org.eclipse.opencert.infra.dashboard.section.coanalysis"
|
| index="5"
|
| name="Co-Analysis">
|
| <Description>
|
| The Development Engineer executes safety and security analysis using: Simulation-based Fault Injection, Model-Based Safety Analysis, Contract-Based Safety Analysis.
|
| </Description>
|
| <Activity
|
| id="org.eclipse.opencert.infra.dashboard.activity.simulationbased.fault.injection"
|
| index="0"
|
| name="Simulation-based fault injection">
|
| <Description>
|
| Simulation-based fault injection.
|
| </Description>
|
| </Activity>
|
| <Activity
|
| id="org.eclipse.opencert.infra.dashboard.activity.modelbased.fta"
|
| index="1"
|
| name="Model-based FTA">
|
| <Description>
|
| Model-based FTA.
|
| </Description>
|
| </Activity>
|
| <Activity
|
| id="org.eclipse.opencert.infra.dashboard.activity.modelbased.fmea"
|
| index="2"
|
| name="Model-based FMEA">
|
| <Description>
|
| Model-based FMEA.
|
| </Description>
|
| </Activity>
|
| <Activity
|
| id="org.eclipse.opencert.infra.dashboard.activity.contractbased.safety.analysis"
|
| index="3"
|
| name="Contract-based safety analysis">
|
| <Description>
|
| Contract-based safety analysis.
|
| </Description>
|
| </Activity>
|
| <Activity
|
| id="org.eclipse.opencert.infra.dashboard.activity.concerto.fla.coanalysis"
|
| index="4"
|
| name="Concerto FLA co-analysis">
|
| <Description>
|
| Concerto FLA co-analysis.
|
| </Description>
|
| </Activity>
|
| <Activity
|
| id="org.eclipse.opencert.infra.dashboard.activity.model.fmvea"
|
| index="5"
|
| name="Model failures modes vulnerability & effects analysis">
|
| <Description>
|
| Model failures modes vulnerability& effects analysis.
|
| </Description>
|
| </Activity>
|
| <Activity
|
| id="org.eclipse.opencert.infra.dashboard.activity.safetysecurity.coanalysis.sa"
|
| index="6"
|
| name="Safety & Security co-analysis in Safety Architect">
|
| <Description>
|
| Safety & Security co-analysis in Safety Architect.
|
| </Description>
|
| </Activity>
|
| <Activity
|
| id="org.eclipse.opencert.infra.dashboard.activity.dependability.coanalysis.papyrus.sse"
|
| index="7"
|
| name="System dependability co-analysis via Papyrus SSE">
|
| <Description>
|
| System dependability co-analysis via Papyrus SSE.
|
| </Description>
|
| </Activity>
|
| </Section>
|
| </Page>
|
| <Page
|
| class="org.eclipse.opencert.infra.dashboard.pages.AssuranceCaseManagementPage"
|
| id="org.eclipse.opencert.infra.dashboard.pages.assurance.case.management"
|
| imageOff="icons/assurancecasemanagement/assurance_case_management_off.png"
|
| imageOn="icons/assurancecasemanagement/assurance_case_management_on.png"
|
| index="5"
|
| tabName="Assurance Case Management"
|
| title="Assurance Case Management"
|
| viewer="true">
|
| <Description>
|
| Define argumentation using compliance arguments, product arguments. Resolve Safety/Security trade off, link to architecture.
|
| </Description>
|
| <Predicate
|
| class="org.eclipse.opencert.infra.dashboard.predicates.DashboardPredicate">
|
| </Predicate>
|
| <Overview
|
| imageOff="icons/assurancecasemanagement/assurance_case_management_off.png"
|
| imageOn="icons/assurancecasemanagement/assurance_case_management_on.png">
|
| <Description>
|
| Assurance case management.
|
| </Description>
|
| </Overview>
|
| <Section
|
| expanded="true"
|
| filtering="true"
|
| id="org.eclipse.opencert.infra.dashboard.section.create.assurance.case.structure"
|
| index="0"
|
| name="Create Assurance Case Structure">
|
| <Description>
|
| The assurance engineer creates and manages assurance cases and link them to the assurance project asset package.
|
| </Description>
|
| <Activity
|
| id="org.eclipse.opencert.infra.dashboard.activity.create.assurance.case"
|
| index="0"
|
| name="Create a new assurance case">
|
| <Description>
|
| Create a new assurance case.
|
| </Description>
|
| </Activity>
|
| </Section>
|
| <Section
|
| expanded="true"
|
| filtering="true"
|
| id="org.eclipse.opencert.infra.dashboard.section.develop.claims.links.evidence"
|
| index="1"
|
| name="Develop Claims and Links to Evidence">
|
| <Description>
|
| The assurance engineer defines the argumentation structure, develops claims and links to evidences. The assurance engineer can take advantage of the arguments generation to complete the assurance case arguments.
|
| </Description>
|
| <Activity
|
| id="org.eclipse.opencert.infra.dashboard.activity.import.argumentation.model"
|
| index="0"
|
| name="Import argumentation model">
|
| <Description>
|
| Import argumentation model.
|
| </Description>
|
| </Activity>
|
| <Activity
|
| id="org.eclipse.opencert.infra.dashboard.activity.generate.arguments.fragments"
|
| index="1"
|
| name="Generate arguments fragments from system contracts">
|
| <Description>
|
| Generate arguments fragments from system contracts.
|
| </Description>
|
| </Activity>
|
| <Activity
|
| id="org.eclipse.opencert.infra.dashboard.activity.generate.process.based.arguments"
|
| index="2"
|
| name="Generate process based arguments">
|
| <Description>
|
| Generate process based arguments.
|
| </Description>
|
| </Activity>
|
| </Section>
|
| <Section
|
| expanded="true"
|
| filtering="true"
|
| id="org.eclipse.opencert.infra.dashboard.section.manage.architecture.assurance.links"
|
| index="2"
|
| name="Manage Architecture - Assurance Links">
|
| <Description>
|
| The assurance engineer or the development engineer can explicitly indicate the links between the system architecture components and the assurance cases elements such as argument modules.
|
| </Description>
|
| <Activity
|
| id="org.eclipse.opencert.infra.dashboard.activity.link.architecture.components"
|
| index="0"
|
| name="Link your architecture components to the assurance case elements">
|
| <Description>
|
| Link your architecture components to the assurance case elements.
|
| </Description>
|
| </Activity>
|
| </Section>
|
| <Section
|
| expanded="true"
|
| filtering="true"
|
| id="org.eclipse.opencert.infra.dashboard.section.assurance.case.reuse"
|
| index="3"
|
| name="Reuse">
|
| <Description>
|
| The assurance engineer can either create a reusable argument element such as argument patterns or arguments modules or use those elements in the actual argumentation. Assurance engineer can also reuse arguments based on the variability points specified.
|
| </Description>
|
| <Activity
|
| id="org.eclipse.opencert.infra.dashboard.activity.create.argument.pattern.module"
|
| index="0"
|
| name="Create an argument pattern or argument module">
|
| <Description>
|
| Create an argument pattern or argument module.
|
| </Description>
|
| </Activity>
|
| <Activity
|
| id="org.eclipse.opencert.infra.dashboard.activity.reuse.assurance.case.patterns.modules"
|
| index="1"
|
| name="Reuse from assurance case patterns and modules">
|
| <Description>
|
| Reuse from assurance case patterns and modules.
|
| </Description>
|
| </Activity>
|
| <Activity
|
| id="org.eclipse.opencert.infra.dashboard.activity.assurance.case.related.reuse"
|
| index="2"
|
| name="Assurance case-related reuse via management of assurance case lines">
|
| <Description>
|
| Assurance case-related reuse via management of assurance case lines.
|
| </Description>
|
| </Activity>
|
| </Section>
|
| </Page>
|
| <Page
|
| class="org.eclipse.opencert.infra.dashboard.pages.EvidenceManagementPage"
|
| id="org.eclipse.opencert.infra.dashboard.pages.evidence.management"
|
| imageOff="icons/evidencemanagement/evidence_management_off.png"
|
| imageOn="icons/evidencemanagement/evidence_management_on.png"
|
| index="6"
|
| tabName="Evidence Management"
|
| title="Evidence Management"
|
| viewer="true">
|
| <Description>
|
| Define the project evidences, define the traceability between artefacts, execute the process to generate evidence and map them to the compliance needs.
|
| </Description>
|
| <Predicate
|
| class="org.eclipse.opencert.infra.dashboard.predicates.DashboardPredicate">
|
| </Predicate>
|
| <Overview
|
| imageOff="icons/evidencemanagement/evidence_management_off.png"
|
| imageOn="icons/evidencemanagement/evidence_management_on.png">
|
| <Description>
|
| Evidence management.
|
| </Description>
|
| </Overview>
|
| <Section
|
| expanded="true"
|
| filtering="true"
|
| id="org.eclipse.opencert.infra.dashboard.section.create.evidence.specification"
|
| index="0"
|
| name="Create Evidence Specification">
|
| <Description>
|
| The assurance engineer can create an evidence model and link it to the assurance project asset package.
|
| </Description>
|
| <Activity
|
| id="org.eclipse.opencert.infra.dashboard.activity.create.evidence.model"
|
| index="0"
|
| name="Create a new evidence model">
|
| <Description>
|
| Create a new evidence model.
|
| </Description>
|
| </Activity>
|
| </Section>
|
| <Section
|
| expanded="true"
|
| filtering="true"
|
| id="org.eclipse.opencert.infra.dashboard.section.create.artiface.traceability"
|
| index="1"
|
| name="Create Artefact Traceability">
|
| <Description>
|
| The assurance engineer can specify the traceability between the artefacts and other elements in the models.
|
| </Description>
|
| <Activity
|
| id="org.eclipse.opencert.infra.dashboard.activity.define.traceability.evidences"
|
| index="0"
|
| name="Define the traceability of your evidences">
|
| <Description>
|
| Define the traceability of your evidences.
|
| </Description>
|
| </Activity>
|
| </Section>
|
| <Section
|
| expanded="true"
|
| filtering="true"
|
| id="org.eclipse.opencert.infra.dashboard.section.execute.process.generate.artefacts"
|
| index="2"
|
| name="Execute Process and Generate Artefacts">
|
| <Description>
|
| The assurance engineer import evidences either from processes modelled in EPF, from external tools or in a process management tool such as WEFACT execute the processes and retrieve the generated evidences.
|
| </Description>
|
| <Activity
|
| id="org.eclipse.opencert.infra.dashboard.activity.import.process.evidences.epf"
|
| index="0"
|
| name="Import process and evidences from EPF">
|
| <Description>
|
| Import process and evidences from EPF.
|
| </Description>
|
| </Activity>
|
| <Activity
|
| id="org.eclipse.opencert.infra.dashboard.activity.import.evidences.external.tool"
|
| index="1"
|
| name="Import evidences from external tool">
|
| <Description>
|
| Import evidences from external tool.
|
| </Description>
|
| </Activity>
|
| <Activity
|
| id="org.eclipse.opencert.infra.dashboard.activity.execute.processes.generate.evidences"
|
| index="2"
|
| name="Execute processes to generate evidences">
|
| <Description>
|
| Execute processes to generate evidences.
|
| </Description>
|
| </Activity>
|
| </Section>
|
| <Section
|
| expanded="true"
|
| filtering="true"
|
| id="org.eclipse.opencert.infra.dashboard.section.manage.compliance.process.artefacts"
|
| index="3"
|
| name="Manage Compliance of Process and Artefacts">
|
| <Description>
|
| The assurance engineer should create and manage the mapping between what has been done and the needs of compliance from a standard/regulation… The assurance manager or the project manager can show the status of compliance of a project at any time.
|
| </Description>
|
| <Activity
|
| id="org.eclipse.opencert.infra.dashboard.activity.create.new.compliance.maps"
|
| index="0"
|
| name="Create a new compliance maps">
|
| <Description>
|
| Create a new compliance maps.
|
| </Description>
|
| </Activity>
|
| <Activity
|
| id="org.eclipse.opencert.infra.dashboard.activity.update.compliance.project"
|
| index="1"
|
| name="Update the compliance of a project">
|
| <Description>
|
| Update the compliance of a project.
|
| </Description>
|
| </Activity>
|
| <Activity
|
| id="org.eclipse.opencert.infra.dashboard.activity.show.compliance.status.project"
|
| index="2"
|
| name="Show the compliance status of a project">
|
| <Description>
|
| Show the compliance status of a project.
|
| </Description>
|
| </Activity>
|
| </Section>
|
| <Section
|
| expanded="true"
|
| filtering="true"
|
| id="org.eclipse.opencert.infra.dashboard.section.evidence.management.reuse"
|
| index="4"
|
| name="Reuse">
|
| <Description>
|
| Evidence management reuse.
|
| </Description>
|
| <Activity
|
| id="org.eclipse.opencert.infra.dashboard.activity.manage.evidence.reuse.variability"
|
| index="0"
|
| name="Manage the evidence reuse variability">
|
| <Description>
|
| Manage the evidence reuse variability.
|
| </Description>
|
| </Activity>
|
| </Section>
|
| </Page>
|
| </extension>
|
| <extension
|
| point="org.eclipse.ui.navigator.viewer">
|
| <viewerActionBinding
|
| viewerId="org.eclipse.ui.navigator.ProjectExplorer">
|
| <includes>
|
| <actionExtension
|
| pattern="org.eclipse.opencert.infra.dashboard.content">
|
| </actionExtension>
|
| </includes>
|
| </viewerActionBinding>
|
| </extension>
|
| <extension
|
| point="org.eclipse.ui.navigator.navigatorContent">
|
| <actionProvider
|
| class="org.eclipse.opencert.infra.dashboard.actions.DashboardActionProvider"
|
| id="org.eclipse.opencert.infra.dashboard.content"
|
| overrides="org.eclipse.amalgam.explorer.activity.navigator.content"
|
| priority="highest">
|
| <enablement>
|
| <or>
|
| <instanceof
|
| value="org.eclipse.core.resources.IProject">
|
| </instanceof>
|
| <instanceof
|
| value="org.eclipse.core.resources.IFile">
|
| </instanceof>
|
| </or>
|
| </enablement>
|
| </actionProvider>
|
| </extension>
|
| <extension
|
| point="org.eclipse.ui.handlers">
|
| <handler
|
| class="org.eclipse.opencert.infra.dashboard.handlers.OpenDashboardHandler"
|
| commandId="org.eclipse.opencert.infra.dashboard.commands.opendashboard">
|
| <activeWhen>
|
| <or>
|
| <with
|
| variable="activePartId">
|
| <equals
|
| value="org.eclipse.ui.navigator.ProjectExplorer">
|
| </equals>
|
| </with>
|
| <with
|
| variable="activePart">
|
| <instanceof
|
| value="org.eclipse.ui.IEditorPart">
|
| </instanceof>
|
| </with>
|
| </or>
|
| </activeWhen>
|
| <!--activeWhen>
|
| <with variable="activePartId">
|
| <or>
|
| <instanceof
|
| value="org.eclipse.ui.navigator.ProjectExplorer">
|
| </instanceof>
|
| <instanceof
|
| value="org.eclipse.ui.IEditorPart">
|
| </instanceof>
|
| </or>
|
| </with>
|
| </activeWhen-->
|
| </handler>
|
| </extension>
|
| <extension
|
| point="org.eclipse.ui.commands">
|
| <command
|
| id="org.eclipse.opencert.infra.dashboard.commands.opendashboard"
|
| name="Open Dashboard">
|
| </command>
|
| </extension>
|
| <extension
|
| point="org.eclipse.ui.menus">
|
| <menuContribution
|
| locationURI="toolbar:org.eclipse.ui.main.toolbar?after=additions">
|
| <toolbar
|
| id="org.eclipse.opencert.infra.dashboard.toolbar.opendashboard">
|
| <command
|
| commandId="org.eclipse.opencert.infra.dashboard.commands.opendashboard"
|
| disabledIcon="icons/toolbar/icon_dashboard_disabled.png"
|
| icon="icons/toolbar/icon_dashboard.png"
|
| id="org.eclipse.opencert.infra.dashboard.toolbar.opendashboard"
|
| label="Open Dashboard">
|
| </command>
|
| </toolbar>
|
| </menuContribution>
|
| </extension> |
| </plugin>
|
