• Aucun résultat trouvé

A requirement engineering driven approach to security architecture design for distributed embedded systems

N/A
N/A
Protected

Academic year: 2021

Partager "A requirement engineering driven approach to security architecture design for distributed embedded systems"

Copied!
222
0
0

Texte intégral

Loading

Figure

Figure 2.1: KAOS security requirements metamodel (taken from [103]) All requirements in KAOS are written by default using semi-formal graphical notations and, if needed, using formal notation
Figure 2.7: Ontology-driven security requirement engineering methodology Our analysis have revealed that multiple SRE models can be expressed in terms of the security ontologies and their associated relationships that we identify, that the
Figure 2.9: IEEE system architecture metamodel [3]and its equivalent system architecture ontology
Figure 2.11: Adversary taxonomy
+7

Références

Documents relatifs

The following section introduces a tools and technologies used to manage the requirements and performs a simple comparative study between three tools DOORS, RTM, and Volere, by

Conditional dependence networks represent obligations as particular kinds of dependencies and these obligations are related to notions by means of sanc- tions if the obligation is

How- ever, the applicability of these approaches in the context of security and privacy requirements modeling for multi-device software ecosystems shows limitations with respect to

The main features of requirements engineering for Scrum project management of software development are analyzed.The quality assessment criteria of user stories are

We brifely describe two requirements specification templates, named TERASE and CAMA, and one requirements elicitation guide, named GERSE which is supported by a

We are currently working on SecCo, which will be the socio-technical security mod- elling language for the EU-funded Aniketos project. Aniketos is about ensuring trust- worthiness

We use the model in the approach to support two steps in particular: (1) deriving misuse cases based on the modelled attack patterns and (2) refinement of the high-level misuse cases

A conceptual framework is presented, where the relationships between business vision, critical impact factors and valuable assets (together with their security requirements) are