Introduction |
|
13 | (2) |
Chapter 1. Model Engineering: From Principles to Platforms |
|
15 | (16) |
|
J. Bézevin, F. Jouault, D. Touzet |
|
|
Chapter 2. Model-Driven Development of Distributed Real-time and Embedded Systems |
|
31 | (30) |
|
D.C. Schmidt, K. Balasubramanian, A.S. Krishna, E. Turkay, A. Gokhale |
|
|
|
|
32 | (6) |
|
2.1.1. Emerging trends and challenges |
|
|
32 | (1) |
|
2.1.2. A partial solution: QoS-enabled component middleware |
|
|
33 | (3) |
|
2.1.3. Resolving key challenges of component-based DRE systems with model-driven development |
|
|
36 | (2) |
|
2.1.4. Chapter organization |
|
|
38 | (1) |
|
2.2. Overview of video distribution case study |
|
|
38 | (3) |
|
2.3. Applying CoSMIC to address video distribution needs |
|
|
41 | (13) |
|
2.3.1. Overview of CoSMIC and GME |
|
|
41 | (3) |
|
2.3.2. Applying CoSMIC to the packaging phase |
|
|
44 | (3) |
|
2.3.3. Applying CoSMIC to the configuration phase |
|
|
47 | (3) |
|
2.3.4. Applying CoSMIC to the planning phase |
|
|
50 | (4) |
|
|
54 | (1) |
|
|
55 | (2) |
|
|
57 | (4) |
Chapter 3. Model Transformation |
|
61 | (8) |
|
|
|
3.1. Why should we transform models 9 |
|
|
61 | (1) |
|
3.2. Role of model transformation in the software lifecycle |
|
|
62 | (1) |
|
3.3. Basics of model transformation |
|
|
63 | (2) |
|
3.4. Classification of model transformations |
|
|
65 | (2) |
|
3.4.1. Model-to-text approaches |
|
|
65 | (1) |
|
3.4.2. Model-to-model approaches |
|
|
66 | (1) |
|
|
67 | (1) |
|
|
67 | (2) |
Chapter 4. Modeling Dependability Features |
|
69 | (24) |
|
|
|
|
69 | (3) |
|
4.2. Separating crosscutting features |
|
|
72 | (4) |
|
|
72 | (1) |
|
4.2.2. An overview of the AOM approach |
|
|
73 | (3) |
|
|
76 | (2) |
|
|
78 | (7) |
|
4.5. Using the AOM approach to separate middleware-specific features |
|
|
85 | (2) |
|
|
87 | (1) |
|
|
88 | (1) |
|
|
88 | (5) |
Chapter 5. Model-Driven Systems Engineering: SysML & the MDSySE Approach at THALES |
|
93 | (18) |
|
|
|
|
93 | (3) |
|
5.1.1. Systems engineering practices at THALES |
|
|
93 | (1) |
|
5.1.2. Toward model-driven systems engineering |
|
|
94 | (2) |
|
5.2. The SysML profile for systems engineering |
|
|
96 | (3) |
|
|
96 | (1) |
|
5.2.2. SysML technical contents |
|
|
97 | (2) |
|
5.3. Building a model-driven systems engineering methodology: the MDSysE approach |
|
|
99 | (5) |
|
5.3.1. Drivers for defining MDSysE |
|
|
100 | (1) |
|
5.3.2. Main features of the MDSysE methodology |
|
|
100 | (1) |
|
5.3.3. Highlight on the MDSysE model work products |
|
|
101 | (3) |
|
5.4. Tooling model-driven systems engineering: the MDSysE tools |
|
|
104 | (3) |
|
|
105 | (1) |
|
5.4.2. Extra-functional aspects |
|
|
106 | (1) |
|
5.4.3. MDSysE tools architecture |
|
|
106 | (1) |
|
|
107 | (1) |
|
|
107 | (4) |
Chapter 6. Maturity of Model-Driven Engineering for Embedded Control Systems from a Mechatronic Perspective |
|
111 | (28) |
|
|
Chapter 7. Real-Time Components & Contracts |
|
139 | (20) |
|
|
|
|
139 | (2) |
|
7.2. Contract aware components: the four level of contracts |
|
|
141 | (8) |
|
7.2.1. Level 1 - Syntactic interfaces |
|
|
142 | (2) |
|
7.2.2. Level 2 - Functional properties |
|
|
144 | (1) |
|
7.2.3. Level 3 - Synchronization properties |
|
|
145 | (1) |
|
7.2.4. Level 4 - Quality of service |
|
|
146 | (3) |
|
7.3. Implementing contract-aware components |
|
|
149 | (3) |
|
7.3.1. Testing extra functional behaviour |
|
|
150 | (1) |
|
|
151 | (1) |
|
7.3.3. Limitations of extra-functional property testing |
|
|
152 | (1) |
|
7.4. Predicting extra-functional properties of an assembly |
|
|
152 | (5) |
|
7.4.1. Modeling a QoS-aware component with QoSCL |
|
|
152 | (2) |
|
7.4.2. Prediction of the GPS quality of service |
|
|
154 | (3) |
|
|
157 | (1) |
|
|
158 | (1) |
Chapter 8. The Think Components-Based Operating System |
|
159 | (20) |
|
J.-C. Tournier, J.-P. Fassino |
|
|
|
|
159 | (1) |
|
8.2. The fractal component model |
|
|
160 | (3) |
|
|
163 | (5) |
|
8.3.1. Interface description language |
|
|
163 | (2) |
|
8.3.2. Architecture description language |
|
|
165 | (1) |
|
|
166 | (1) |
|
8.3.4. Implementation of operating system services |
|
|
167 | (1) |
|
|
168 | (6) |
|
|
168 | (2) |
|
8.4.2. Framework extensions |
|
|
170 | (4) |
|
|
174 | (1) |
|
|
175 | (1) |
|
8.7. Acknowledgments and availability |
|
|
175 | (1) |
|
8.8. Bibliography/References |
|
|
176 | (3) |
Chapter 9. Model-Driven Schedulability Analysis |
|
179 | (26) |
|
|
|
|
179 | (1) |
|
9.2. Real-time scheduling |
|
|
180 | (7) |
|
|
180 | (1) |
|
9.2.2. Scheduling techniques |
|
|
181 | (2) |
|
|
183 | (3) |
|
9.2.4. Simulation and implementation |
|
|
186 | (1) |
|
|
187 | (10) |
|
|
187 | (1) |
|
9.3.2. Real-time model-driven development |
|
|
187 | (1) |
|
|
188 | (2) |
|
|
190 | (4) |
|
9.3.5. Execution semantics |
|
|
194 | (2) |
|
9.3.6. Formal development of real-time systems |
|
|
196 | (1) |
|
|
197 | (1) |
|
|
198 | (7) |
Chapter 10. Performance Analysis based on the UML SPT Profile |
|
205 | (20) |
|
|
|
|
205 | (2) |
|
|
207 | (4) |
|
10.2.1. Layered queueing networks |
|
|
209 | (2) |
|
10.3. UML models with performance annotations |
|
|
211 | (3) |
|
10.4. UML to LQN transformation |
|
|
214 | (5) |
|
10.4.1. Mapping the structure |
|
|
215 | (1) |
|
10.4.2. Mapping the behaviour |
|
|
215 | (4) |
|
10.5. Performance model validation |
|
|
219 | (2) |
|
|
221 | (1) |
|
|
222 | (1) |
|
|
222 | (3) |
Chapter 11. Code Generation for Embedded Systems |
|
225 | (20) |
|
D. Björklund, J. Lilius, I. Porres |
|
|
|
|
225 | (2) |
|
|
227 | (5) |
|
|
229 | (1) |
|
11.2.2. Constraints in input models |
|
|
229 | (2) |
|
|
231 | (1) |
|
11.3. Rialto as an interdemdiate language for code generation |
|
|
232 | (2) |
|
11.4. Rialto in code generation |
|
|
234 | (7) |
|
11.4.1. From UML to Rialto |
|
|
235 | (1) |
|
|
235 | (1) |
|
11.4.3. Activity diagrams |
|
|
235 | (1) |
|
11.4.4. Collaboration diagrams |
|
|
236 | (1) |
|
|
236 | (1) |
|
11.4.6. Constructing finite state machines from Rialto programs |
|
|
237 | (1) |
|
|
238 | (2) |
|
11.4.8. Generation of program code |
|
|
240 | (1) |
|
|
241 | (1) |
|
|
242 | (3) |
Chapter 12. Model-Driven Architecture for Intensive Embedded Systems |
|
245 | (24) |
|
L. Bondé, P. Boulet, A. Cuccuru, J.-L. Dekeyser, C. Dumoulin, P. Marquet S. Metfali, M. Samyn |
|
|
|
|
245 | (2) |
|
|
247 | (2) |
|
12.2.1. Metamodels for the "Y" design |
|
|
248 | (1) |
|
|
249 | (1) |
|
12.3. The Transformation engine: ModTransf |
|
|
249 | (5) |
|
|
250 | (1) |
|
|
251 | (2) |
|
|
253 | (1) |
|
12.4. Models and metamodels |
|
|
254 | (7) |
|
12.4.1. Application metaModel |
|
|
255 | (2) |
|
12.4.2. Hardware architecture metaModel |
|
|
257 | (1) |
|
12.4.3. Association metamodel |
|
|
258 | (1) |
|
12.4.4. Transactional level meta model |
|
|
259 | (2) |
|
12.5. Application of MDA transformations |
|
|
261 | (5) |
|
12.5.1. PIM to PSM transformation |
|
|
261 | (2) |
|
12.5.2. Transformation rule expression in ModTransf |
|
|
263 | (1) |
|
12.5.3. Code generation from the Tlm model |
|
|
264 | (2) |
|
|
266 | (1) |
|
|
267 | (2) |
Chapter 13. Spidergon: A NoC Modeling Paradigm |
|
269 | |
|
M. Copolla, R. Locatelli, G. Maruccia, L. Piéralilsi, M.D. Grammatikakis |
|
|
|
|
269 | (5) |
|
13.1.1. NoC: Communication infrastructure for MPSOC |
|
|
269 | (4) |
|
|
273 | (1) |
|
13.2. The Spidergon NoC architecture |
|
|
274 | (6) |
|
13.3. Spidergon NoC modeling |
|
|
280 | (2) |
|
13.4. Design space exploration using NoC metamodels |
|
|
282 | (2) |
|
13.4.1. Hot Spots - non uniform traffic spots |
|
|
282 | (1) |
|
13.4.2. Application traffic |
|
|
283 | (1) |
|
13.4.3. Remaining MODELING issues |
|
|
284 | (1) |
|
13.5. Conclusion and extensions |
|
|
284 | (2) |
|
|
286 | |