
doi: 10.1007/bfb0017628
We argue for greater emphasis on design in software engineering courses, and for design under consideration of non-functional requirements. In particular we show that it is sometimes quite easy to determine early whether a design satisfies performance and reliability requirements. This is done by means of examples we have used in our courses. Performance and reliability analyses, which acquire particular importance with embedded real-time systems, require familiarity with probability and queueing theory. We recommend a special course on these topics.
| selected citations These citations are derived from selected sources. This is an alternative to the "Influence" indicator, which also reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | 2 | |
| popularity This indicator reflects the "current" impact/attention (the "hype") of an article in the research community at large, based on the underlying citation network. | Average | |
| influence This indicator reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | Top 10% | |
| impulse This indicator reflects the initial momentum of an article directly after its publication, based on the underlying citation network. | Average |
