M From:	HENRY::IN%"NYBERG%ada20.isi.EDU%relay.cs.net@rca.com" 10-MAR-1987 08:03 0 To:	info-ada@ada20.isi.edu, ada-sw@simtel20.arpa1 Subj:	Does the DoD Really Want Reusable Software?     > Nearly two decades after Doug McIlroy described the need for a= software components industry, software reusability is finally F receiving some attention. One of the promises that the U.S. DepartmentE of Defense (DoD) made when it introduced the Ada programming language D and its associated technology, was that Ada would help to facilitateF software reusability. Apparently, someone within the bowels of the DoD6 feels that software reusability is an important issue.  B A quick study of the possible benefits of reusing software revealsF that there is much more to be gained than a simple cost savings duringB the development of a software product. For example, the reuse of aE software component which is known to be reliable introduces less risk ? than re-designing and re-coding the same component for each new E application. Efficiency issues can also be more effectively addressed E if one can focus attention on optimizing a set of reusable components D rather than having to continually re-optimize newly recoded versions of previously existing modules.   E However, it seems that both the DoD and their contractors are greatly F confused about just what an increased emphasis on software reusability@ might mean. While they both might acknowledge that some existingE software development practices will have to change, they seem unaware E of which specific items will be different. There are a number of very @ large roadblocks to software reusability on DoD projects, and it* should be useful to mention a few of them.  6 One of the largest roadblocks to software reuse is theF cost-plus-fixed-fee (CPFF) style of contract now commonplace among DoDE contracting styles. In effect, the more people a contractor can place F on a project, the greater the financial reward. Hence there is a greatE incentive to "re-invent the wheel." While fixed-price contracts would E go a long way towards fixing this "problem," we need to examine other 
 alternatives.   : Current and past DoD software development standards (e.g.,F DOD-STD-2167, 490, 1679A, etc.), or their interpretations, are another> set of roadblocks to software reuse. While the words "softwareD reusability" might be "buried in the DIDs" (Data Item Descriptions),A the standards themselves discourage software reuse on a number of  fronts, e.g.,:    F    1) the encouragement of software development methodologies which doB       not facilitate reuse (e.g., functional decomposition), whileD       discouraging others that seem to encourage reuse (e.g., object       oriented approaches), and   B    2) requiring that every piece of code produce for a project, beF       relevant specifically to that project. While this might seem to H       be a perfectly reasonable demand, it violates one of the axioms of$       reusability, i.e., generality.  F While the DoD has standards of acceptance for reusable hardware, thereA is little in the way of standards or certification mechanisms for > reusable software. For example, there is no currently existing< organization charged with certifying software for reuse. YesD repositories of "reusable" software exist, but there is no generallyD recognized (much less mandated) certification mechanism for reusableC software components (e.g., an Ada Component Verification Capability  (ACVC)).  D In the past year, I have given a number of presentations on software8 reusability. During the discussions which followed these= presentations, I became acutely aware that either the DoD was A actively *discouraging* the concept of software reuse or that the D contractors (and the DoD) did not know that an increased emphasis onD software reuse would involve significant changes in the state of the
 practice.   D Until both the DoD and their contractors come to grips with the factC that software reusability does not mean business as usual, software : reusability will be relegated to the status of a buzzword.   				-- Ed Berard 				   (301) 695 - 6960   ? (r) Ada is a registered trademark of the U.S. Government (AJPO)  ------- 