Book A.

Book B.
7150 Requirements Guidance

Book C.

References, & Terms

(NASA Only)

Leave blank if none exists

This is the text which will be hyperlinked, if a link exists

30 Pitfalls for Real-Time Software Developers. Embedded Systems Programming,

SWE or Topic


This contains additional information, which will appear after the title, separated by a comma

Stewart, David (1999).

More specific directions where to look in the resource for relevant content

Example Reference as it will appear to end user:

  1. Title, Citation


Quotes used in SWEs and Topics

#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.