09.08.2013 Views

Architecture Modeling - SPES 2020

Architecture Modeling - SPES 2020

Architecture Modeling - SPES 2020

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>Architecture</strong> <strong>Modeling</strong><br />

tasks Command1 and Monitor1 are not met. To get more detailed information about a deadline<br />

violation one may choose a red skull and a window opens as it is depicted in Figure 5.23<br />

for the task Command1. At the top of the window, we see beside the name, period and deadline<br />

of the node a list of different results of the analysis. First of all, this is the response time and<br />

how it is composed of different aspects as the blocking time by tasks with higher priority. This<br />

is depicted at the bottom of Figure 5.23. The red line represents the deadline that is obviously<br />

violated here.<br />

One possible counter-measure to solve this violation would be two replace one or both ECUs<br />

by other ones where the respective tasks have less execution times. In this example, the initial<br />

architecture consists of two ECUs of an ARM7 type. When replacing both ECUs by an ARM9<br />

type leading to less execution times, all deadline violations can be successfully removed. Another<br />

possible measure would be to change the splitting of global deadlines into local deadlines<br />

(deadline synthesis) in the <strong>SPES</strong> model.<br />

5.2 On the role of contracts in system development<br />

processes 5<br />

In this section we discuss key design challenges<br />

• Coping with complexity of systems<br />

• Coping with the complexity of the supply chain<br />

• Getting initial requirements right<br />

• Coping with multi-layer design optimization<br />

• Managing Risk<br />

facing systems companies, and discuss industrial solutions in place to cope with these, and<br />

point out how conservative extensions of current processes exploiting contract-based design<br />

could tackle such weaknesses. We wrap up by condensing the essence of what we call contractbased<br />

design.<br />

5.2.1 Coping with complexity of systems<br />

Multiple lines of attack have been developed by industry to cope with the exponential growth<br />

in systems complexity:<br />

1. Model-based development<br />

2. Virtual integration<br />

3. Layered design<br />

4. Component-based design<br />

5. Platform-based design<br />

5 This section is co-authored with Alberto L. Sangiovanni-Vincentelli, University of California at Berkeley<br />

93/ 156

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!