Architecture Modeling - SPES 2020

More documents

Recommendations

Info

Patternn Failuure has cr riticalityy critical lity S7: This paattern allows to associate e failures withh criticalities s that have been derived for instance e from the hazard classification during FHA A (functional hazard asse essment). Naturaal Language Requirement: Loss of the braking syst tem is considdered hazard dous Patternn based RSLL: LossOfBraakingSyste em has criiticality hazardous s Patteern hazarrd Hazard is definned by ( event e ) S8: This ppattern can bbe used to describe the hhazard. The event repres sents the point in time wh here the hazarrd occurs. Natural Languagge Requirem ment: Unannnounced losss of deceleration capability during landing Patteern based RSL: Architecture Modeling Hazaard UnannoouncedLoss sOfDecelerrationCapa ability is s defined by ((CoontrolLampp==1) hold ds not durring [tr(p phase==Lan nding),PeddalPushed] ] and thenn Brake noot during [PedalPusshed,500ms s]) This eexample is taaken from the ARP4754 standard. Th he following graphic g explaains the form malization in moore detail: The CControlLampp indicates the failure of thhe braking system. Since e the hazard only occurs if the failuree is unannouunced there shall s be no innterruption in n the Control lLamp signall between the start of the laanding proceess and the PedalPushed P d event. This is expressed d in the first part of the ev vent descrription of the pattern: ... (ControlLLamp==1) holds h not during [t tr(phase== =Landing), ,PedalPush hed] .. T1 exxpresses thee time in whic ch a brake reeaction to the e request by the pedal is expected. Is s there no Brakee event in thiis interval the e hazard occcurs: .... ... Brakee not duri ing [PedallPushed,50 00ms] .... .... 132/ 156
Pattern S9: failureCondition failureCondition is defined by: event does [not] occur [during interval | under condition condition] This pattern defines a failure condition by the occurrence (or absence) of an event during an interval or while a condition holds. Conditions and intervals can be used as described for the functional pattern. Natural Language Requirement: The failure “unintended inflation of airbag” happens if the crash signal gets emitted while both gravity sensors detect no crash. Pattern based RSL: failureCondition UnintendedInflationOfAirbag is defined by: crash does occur under condition (gravitySensor1.gnormal) gets violated Pattern S11: Architecture Modeling failureCondition failureCondition is defined by: condition holds [longer|shorter] than timeunit This pattern defines a failure condition by the violation of interval a condition holds. Conditions can be written as described for the functional pattern. Natural Language Requirement: It is considered as a failure if the current of the engine control system is longer than 2 sec. above 2A. Pattern based RSL: failureCondition TooMuchEnergyConsumption is defined by: (consumption > 2) holds longer than 2s 133/ 156
Page 1 and 2:
Architecture Modeling ∗ Andreas B
Page 3 and 4:
Contents 1 Introduction 1 2 Quick-T
Page 5 and 6:
1 Introduction This document propos
Page 7 and 8:
Architecture Modeling allowing to m
Page 9 and 10:
Architecture Modeling creating a vi
Page 11 and 12:
Architecture Modeling the design it
Page 13 and 14:
Architecture Modeling of the logica
Page 15 and 16:
Architecture Modeling realization o
Page 17 and 18:
Architecture Modeling can usually o
Page 19 and 20:
3 The Architecture Meta-Model In Se
Page 21 and 22:
Abstraction-Levels (detail increase
Page 23 and 24:
3.2.2 Functional Perspective Archit
Page 25 and 26:
Architecture Modeling The semantics
Page 27 and 28:
Architecture Modeling expressed by
Page 29 and 30:
Architecture Modeling computing cap
Page 31 and 32:
3.2.5 Geometrical Perspective Archi
Page 33 and 34:
ShapeCompositionOperator intersecti
Page 35 and 36:
Architecture Modeling The constrain
Page 37 and 38:
Architecture Modeling of particular
Page 39 and 40:
Architecture Modeling Shape that de
Page 41 and 42:
Architecture Modeling Conjugation o
Page 43 and 44:
RichComponent Architecture Modeling
Page 45 and 46:
MultiplicityElement +part 0..* Rich
Page 47 and 48:
ComponentC Architecture Modeling pa
Page 49 and 50:
4 Steps in Component-Based Design T
Page 51 and 52:
Architecture Modeling Assume/guaran
Page 53 and 54:
Architecture Modeling When specifyi
Page 55 and 56:
Architecture Modeling next selectio
Page 57 and 58:
Architecture Modeling ports must ha
Page 59 and 60:
established if (and only if): Archi
Page 61 and 62:
12°C < tempSelect < 35°C actTemp
Page 63 and 64:
Architecture Modeling The component
Page 65 and 66:
Architecture Modeling 4.3.2 Establi
Page 67 and 68:
Architecture Modeling a mapping is
Page 69 and 70:
Architecture Modeling Another impor
Page 71 and 72:
5 Using the Architecture Meta-Model
Page 73 and 74:
Architecture Modeling Design proces
Page 75 and 76:
Architecture Modeling abstraction l
Page 77 and 78:
Pwr1 Pedal_Pos1 Pwr2 Pedal_Pos2 CMD
Page 79 and 80:
Architecture Modeling Figure 5.4: O
Page 81 and 82:
Architecture Modeling Figure 5.7: L
Page 83 and 84:
Architecture Modeling Figure 5.9: T
Page 85 and 86: Architecture Modeling Figure 5.12:
Page 89 and 90: Architecture Modeling However this
Page 91 and 92: Architecture Modeling The considera
Page 97 and 98: Architecture Modeling tasks Command
Page 99 and 100: Architecture Modeling of the V, suc
Page 101 and 102: Architecture Modeling thus decorate
Page 103 and 104: Architecture Modeling In summary, P
Page 105 and 106: Architecture Modeling OEMs are incr
Page 107 and 108: Architecture Modeling provide effec
Page 111 and 112: Architecture Modeling patterns, cap
Page 113 and 114: Architecture Modeling 6.1 Syntax an
Page 115 and 116: 6.1.1.1.1 Attribuute Definit tion a
Page 117 and 118: Constrrain Eventts with Co ondition
Page 119 and 120: These events used in the “and the
Page 121 and 122: Formalization: whenever StartButton
Page 123 and 124: Architecture Modeling Basic bloock
Page 125 and 126: 6.1.1.1.1.3 Conditions Conditions c
Page 127 and 128: 6.1.1.1.2.2 Seammless Con ncatenati
Page 129 and 130: e3 && (clk==0) e1 idle pre e1 idle
Page 131 and 132: Pattern whenever event occurs condi
Page 133 and 134: If the brake force is above 80% for
Page 135: Pattern S3: Failure shall not be ca
Page 139 and 140: Pattern R2: Event occurs each perio
Page 141 and 142: idle e1 |clk:=0 e2 && (l
Page 143 and 144: The function : allocates a singl
Page 145 and 146: Examplees of clocks: • Run: {c=0@
Page 147 and 148: Architecture Modeling 1. For σ ∈
Page 149 and 150: Architecture Modeling Traces accord
Page 151 and 152: Architecture Modeling Definition 6.
Page 153 and 154: Architecture Modeling the one given
Page 155 and 156: Architecture Modeling Decomposition
Page 157 and 158: Bibliography [1] ARINC 653 - Avioni
Page 159 and 160: Architecture Modeling [26] Holger G
show all

Architecture Modeling - SPES 2020

Create successful ePaper yourself

Delete template?

Save as template?