23.08.2013 Views

Specification of Reactive Hardware/Software Systems - Electronic ...

Specification of Reactive Hardware/Software Systems - Electronic ...

Specification of Reactive Hardware/Software Systems - Electronic ...

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.

38 Concepts for Analysis, <strong>Specification</strong> and Design<br />

orthogonality <strong>of</strong> concepts is therefore hard to carry out.<br />

There are many dependencies and relations between concepts. Corresponding to the<br />

different development activities, concepts can be distinguished for:<br />

initial requirements capturing;<br />

functional analysis and specification;<br />

architecture design;<br />

implementation modelling;<br />

hardware/s<strong>of</strong>tware realisation.<br />

An important condition for a smooth path from product idea to realisation is a clear<br />

mapping between the concepts and descriptions used to support the different development<br />

activities. Descriptions must be consistent and verifiable. A semantic gap between<br />

descriptions <strong>of</strong>ten leads, even with today’s CAE/CAD support, to manual translations<br />

<strong>of</strong> design descriptions. Concepts simply do not match, unless a method is carefully<br />

designed to bridge the gap.<br />

Our specification method as a whole is composed from formal as well as from informal<br />

concepts. The consistency <strong>of</strong> the formal concepts are verified using a formal semantical<br />

model (see Chapter 7). Unfortunately, such an approach is not directly applicable to<br />

check the compatibility <strong>of</strong> the informal method concepts. Nevertheless, by establishing<br />

mappings between the informal concepts and the formal ones, we are able to check their<br />

compatibility as good as possible. Using this approach we narrow the semantical gaps<br />

between the different descriptions.<br />

3.6 Practical Use <strong>of</strong> Concepts<br />

In the previous subsection we stated that the method SHE is the result <strong>of</strong> the careful<br />

joining <strong>of</strong> concepts. The concept approach is interesting from a scientific point <strong>of</strong> view<br />

and therefore it is the most important part <strong>of</strong> this thesis. A precise description <strong>of</strong> all<br />

concepts, and motivation for their need, can give a deeper understanding <strong>of</strong> our work<br />

and the method. However, it is hard to understand the need for concepts without<br />

an understanding <strong>of</strong> the global ideas for our method. Therefore we present a quick<br />

overview <strong>of</strong> the use <strong>of</strong> the method for a real industrial application. This application<br />

is elaborated in Chapter 12. The overview will enable readers which are less familiar<br />

with existing (object-oriented) analysis and design methods to form an idea <strong>of</strong> the global<br />

flow <strong>of</strong> a specification modelling process. It will give an understanding for the need<br />

for various concepts that we describe in Chapters 4, 5 and 6. In these chapters we give<br />

small examples that are also derived from the industrial application presented here.

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

Saved successfully!

Ooh no, something went wrong!