Embedded Software: The Works

Finding a logical flow for the chapters in this book proved challenging. I more or less gave up and simply grouped articles that seemed to belong together. Design and development methodologies and tools seem to fit alongside one another. But where should they all go in a sequence? After all, you do design first, but design methodologies are seen as "high level," so shouldn't the "low-level" stuff come before it? See what I mean?
What did prove interesting is that there are two "buzzwords" that are evoking a lot of interest in the embedded world at the beginning of the twenty-first century: UML and Eclipse. Both are addressed in articles in this chapter.
Crystal ball gazing is a hazardous occupation. No matter how well you know a technical subject, new developments will arise that you were unable to foresee. I wrote an "agenda setting" piece for NewBits in the late 1990s, and while reviewing it for use in this book, I was surprised at how much had "gone according to plan." This article for the 1990s needed surprisingly little adaptation to be developed into an article for the twenty-first century. The only key new technology is the UML, which is addressed in more detail in other articles in this chapter. (CW)
It is easy to think of embedded systems development as state of the art and leading edge. However, since microprocessors were first introduced in the early 1970s and the...