<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
V petek 27. junija bo ob 10h v Oranzni predavalnici IJS 262.
Solomonov seminar. Oranzna predavalnica je v drugem nadstropju
glavne stavbe IJS. Posnetki preteklih seminarjev so na <a
moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://videolectures.net/solomon/">http://videolectures.net/solomon/</a>
<br>
<br>
<br>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<br>
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<p class="MsoNormal"
style="margin-top:.3pt;margin-right:0cm;margin-bottom:0cm;
margin-left:0cm;margin-bottom:.0001pt;line-height:13.0pt;mso-line-height-rule:
exactly;mso-layout-grid-align:none;text-autospace:none"><span
style="font-size:13.0pt;font-family:"Times New
Roman","serif"" lang="SL"><o:p> <br>
The engineering of real-‐time embedded systems <br>
<br>
Why software needs to be developed using rigorous
engineering-‐based methods <br>
<br>
<br>
Dr Jim Cooling -‐ Lindentree Associates <br>
<br>
The microprocessor arrived circa 1970 and initially, was a
very expensive device. However, by the end of that decade its
cost had fallen dramatically, thanks mainly to improvements in
design and fabrication methods. Suddenly cost was no longer a
barrier to using it as a replacement for conventional analogue
and digital electronic systems. And now prices have reached a
point where we do, in fact, manufacture throwaway units. The
result is that vast areas of our everyday life depends on
microcomputer technology: <br>
<br>
White goods -‐ washing machines, food mixers, microwave
ovens, etc. Autos -‐-‐ engine management, vehicle
stability, infotainment, etc. <br>
Home security – smoke detectors, intruder alarms, perimeter
monitoring, etc. <br>
Medical – personal health monitoring, dosage control,
body/brain scanning, etc. <br>
<br>
I could go on, the list is immense. And all of these rely on
their software for <br>
correct and safe functioning. So, how good is this software?
How much reliance can we place on it? How safe is it? Based
on real experience the answers are a mixed bunch.
Unfortunately we’ve found that, on many occasions, we just
don’t do it very well; improvements are badly needed in many
areas. <br>
<br>
Broadly speaking, the purpose of this presentation is to: <br>
1. Persuade you that we really do have serious problems in
the embedded <br>
world. <br>
2. Show what leads to such problems in the first place. <br>
3. Make a case for the use of discipline and
engineering-‐style practices when <br>
developing software. <br>
4. Provide an overview of practical methods for implementing
such <br>
practices. <br>
This is not an in-‐depth technical presentation so don’t look
for cookbook solutions. Instead it seeks to get you to think
really carefully about how you should be developing software
for embedded applications. Most of you will be familiar with
CASE, computer-‐aided software engineering. This talk aims to
get you develop better techniques for BASE, brain-‐aided
software engineering. <br>
<br>
=============================================================
<br>
Jim Cooling has had many years experience in the area of
real-‐time embedded systems, including electronic, software
and system design, project management, consultancy and course
development. He has published extensively on the subject, his
books covering many aspects of embedded-‐systems work such as
real-‐time interfacing, programming, software design and
software engineering. Currently he is a partner in Lindentree
Associates (which he formed in 1998), providing consultancy
and training for real-‐time embedded systems.
<a class="moz-txt-link-abbreviated" href="http://www.lindentreeuk.co.uk">www.lindentreeuk.co.uk</a> <br>
<br>
<br>
</o:p></span></p>
</body>
</html>