Link |
Unknown macro: {div} http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.133.761&rep=rep1&type=pdf |
Title |
30 Pitfalls for Real-Time Software Developers. Embedded Systems Programming, |
SWE or Topic |
SWE-147, |
Citation |
Stewart, David (1999). |
Notes |
|
Example Reference as it will appear to end user:
- Title
, Citation
where:
- Title = Title
- Link = http://www.nasa.gov
- Citation = Citation
Quotes used in SWEs and Topics
- SWE-147 - Specify Reusability Requirements - from item 25 in paper
#25 Reusing code not designed for reuse
Code that is not designed for reuse will not be in the form of an abstract data type or object. The code may have interdependencies with other code, such that if all of it is taken, there is more code than needed. If only part is taken, it must be thoroughly dissected, which increases the risk of unknowingly cutting out something that is needed, or unexpectedly changing the functionality. If code isn’t designed for reuse, it’s better to analyze what the existing code does, then redesign and re-implement the code as well-structured reusable software components. From there on, the code can be reused. Rewriting this module will take less time than the development and debugging time needed to reuse the original code.
