• Aucun résultat trouvé

Formalization, Evaluation of non-functional properties for system of system engineering: Application to Resilience

N/A
N/A
Protected

Academic year: 2021

Partager "Formalization, Evaluation of non-functional properties for system of system engineering: Application to Resilience"

Copied!
2
0
0

Texte intégral

(1)

HAL Id: hal-02016577

https://hal.archives-ouvertes.fr/hal-02016577

Submitted on 12 Feb 2019

HAL is a multi-disciplinary open access

archive for the deposit and dissemination of sci-entific research documents, whether they are pub-lished or not. The documents may come from teaching and research institutions in France or abroad, or from public or private research centers.

L’archive ouverte pluridisciplinaire HAL, est destinée au dépôt et à la diffusion de documents scientifiques de niveau recherche, publiés ou non, émanant des établissements d’enseignement et de recherche français ou étrangers, des laboratoires publics ou privés.

Formalization, Evaluation of non-functional properties for system of system engineering: Application to

Resilience

Behrang Moradi, Nicolas Daclin, Vincent Chapurlat

To cite this version:

Behrang Moradi, Nicolas Daclin, Vincent Chapurlat. Formalization, Evaluation of non-functional properties for system of system engineering: Application to Resilience. 14th International Conference on Information Systems for Crisis Response and Management (ISCRAM 2017), Albi, France, 21-24 May 2017., May 2017, Albi, France. �hal-02016577�

(2)

Formalization, Evaluation of non-functional properties for system of system

engineering: Application to Resilience

Behrang MORADI, Nicolas DACLIN, Vincent CHAPURLAT

(firstname.lastname@mines-ales.fr)

LGI2P, Ecole des Mines d’Alès

Systems of Systems Engineering

A system of system (SoS) is an integration of a finite number of constituent systems which are independent and operable, and which are networked together for a period of time to achieve a certain higher goal.1[Jamshidi, 2009].

SoS are composed of separate constituent systems and have a majority of the following five characteristics 2[Maier, 1998]:

Operational independence – constituent has a purpose of its own and can be

operated independently, without the need to interact with other systems.

Managerial independence - constituent are controlled by different authorities (or system owners), they not only have operational independence but are, actually, operated independently.

Emergent behavior – behaviors are only exhibited at the SoS level and cannot

be achieved by any of the constituent systems operating independently of the other constituent systems.

Evolutionary development – SoS is not created once and for all, but evolves as

constituent systems, or functions thereof, are added, removed, or modified.

Geographical distribution – the concern of SoSE is primarily with the

information exchange between constituent systems.

Fig.1. A Transport System-of-Systems

Resilience

Ability to prevent, prepare for, respond to, adapt to disruptions and to mitigate the consequences as well as to recover in timely and efficient manner

including preservation, restoration of services 3[Cutter et al. 2013].

Fig.2. Illustration of essential resilience capabilities.

Prevention: Identifying and minimizing the risks posed by the Critical Infrastructure, its equipment and fittings, and the natural hazards of the environment 4[UNESCO 2017].

Preparation: “Getting ready to cope” 4[UNESCO, 2017].

Response: Following the previously established emergency procedures.

Absorption: Endogenous ability to reduce the negative impacts caused by disruptive events and minimize consequences with less effort 5[Nan, 2017].

Adaptation: Endogenous ability to adapt to disruptive events through self-organization to minimize consequences. It can be enhanced by using emergency systems 5 [Nan and Sansavini 2017].

Recovery: “Getting back to normal” 4[UNESCO 2017].

Relationships amongst Resilience and System Lifecycle Properties

(Ilities) :

 The “-ilities” are properties that often manifest and determine value after a system is put into initial use (e.g. resilience, interoperability, robustness).

 Resilience is an important “-ilities- and must be mastered and maximized with engineering systems of systems.

Hypothesis 1: The resilience can be evaluated by defining and analysing its relations

within the “-ilities” “ecosystem”.

Fig. 3. Correlation network of ilities based on a normalized 2-tubel keyword analysis 6[De Weck, Ross,

Rhodes,2012]

 Analysis of dependencies between the other ilities and resilience  Definition of the orientation of the dependencies (from /to resilience)

 Definition of the intensity between resilience and ilities (level of variation from of the resilience from a variation of a linked ilities)

 Definition and formalization of the propagation concept

Hypothesis 2: The evaluation of resilience is decomposed in local resilience evaluation

according to its lifecycle.

Fig. 4. Framework of evaluation of resilience

Hypothesis 3: The evaluation is done according to different points of view:

organizational, physical, behavioral and functional.

 Definition of organizational, behavioral, physical and functional resilience .  Adaptation of each indicator to the studied point of view.

 Comment

References

References

1. Sauser, B., Boardman, J., & Gorod, A. (2009). System of systems management. Chap, 8, 191-217. 2. Maier, M. (1998). Principles of System of System Architecture.

3. Cutter, S. L., Ahearn, J. A., Amadei, B., Crawford, P., Eide, E. A., Galloway, G. E., ... & Scrimshaw, S. C. (2013). 4. UNESCO. 2017. “Disaster Planning: Prevention, Preparedness, Response, Recovery.”

5. Nan, C., & Sansavini, G. (2017). A quantitative method for assessing resilience of interdependent infrastructures. Reliability Engineering & System Safety, 157, 35-53. 6. De Weck, O. L., Ross, A. M., & Rhodes, D. H. (2012). Investigating relationships and semantic sets amongst system lifecycle properties (Ilities).

Prevention Preparation Disruptive event MOP(t

)

Time Response phase Absorption Adaptation Recovery phase M e a su rem e n t Of P e rf o rm a n ce Evaluation of Resilience

Evaluation of Prevention Evaluation of Response Evaluation of Recovery

Set of expected-Ilities Set of expected-Ilities Set of expected-Ilities

Dependence , orientation, propagation, intensity Formalization of mitigation indicator Dependence , orientation, propagation, intensity Formalization of prevention indicator Dependence , orientation, propagation, intensity

Formalization of recovery indicator

To define, specify and develop equipped method

to evaluate resilience for System of System

Engineering

1 2 3 4 1 2 3 4 Resilience Behavioral Resilience S 0 S 1 Functional Resilience F1 Physical Resilience Organizational Resilience SoS Resilicence comp 3 comp 4 comp 1 comp 2 F2 F2 F2 S 0 T2 T1

Références

Documents relatifs

We show how this approach can be used to extend DSLs which specify behavior in terms of rules (that describe the evolution of the modeled artifacts along some time model), and how

In this paper, we presented the analysis of non-functional service properties in the presence of transactional workflow patterns in order to guarantee semi-atomic execution

During the performance of normative tasks, determined by the nominal tactical and technical characteristics of the system, the requirements of the system and its ele-

More kinds of time links between jobs are imaginable, but they will appear in a schedule, on later stages of planning when jobs will be distributed among executors.. Time links set

The conditions for the stable existence of this system, originally formulated in terms of the asymptotic properties of this iterative process, reduce to the existence of

Students proposed to design a system (electrical generator) that, assembled in the rims of a bicycle, would produce the amount of energy needed to load a

In this paper we present a novel framework, called Drive, to allow the programmer to model non-functional properties of time, energy and security in their C source-code as

To overcome the problem and provide an end-user approach to support automating the maintenance of non-functional properties in DSMLs, we have been investigating