M From:	HENRY::IN%"NYBERG%ada20.isi.EDU%relay.cs.net@rca.com" 10-MAR-1987 08:06 0 To:	info-ada@ada20.isi.edu, ada-sw@simtel20.arpa( Subj:	DoD and Reusable Software - Part 2     1.0   Introduction  > Earlier, I posted a message about the roadblocks that the U.S.> Department of Defense (DoD) is placing in the path of software@ reusability. This message describes a specific example of how an? attempt to encourage the reuse of Ada software on an actual DoD @ project is being thwarted. Neither the contractor (a very large,C well-known west coast aerospace firm) nor the contracting branch of B the service (the Navy) has said that software reusability is a bad; thing. Both, however, are prevented by well-established DoD ? regulations from both creating and reusing "reusable software."    2.0   Brief Technical Analogy   B In the computer hardware industry, reuse is the norm. For example,E there are standard CPU chips (e.g., M68020, Intel's 8088, and various A versions of the 1750a). There are also standard RAM, mathematical B co-processor, and ROM chips. These, and other, chips are used in aD wide variety of applications. A long time ago, electronics engineersC discovered that one of the most important axioms of reusability was  generality.   E Unlike their software counterparts, electronics engineers do not have F to verify, for example, that every "op-code" supported by a particular> CPU is executed in a specific application. Nor do they have toF demonstrate that every last byte of RAM is utilized. While the reasonsE for this should be obvious, it would be helpful to point out a few of  them:   E    1) Once a CPU chip is created and verified, a known (and typically F       very high) level of reliability can be established for the chip.@       When this chip is reused in another application, its knownE       reliability can be factored into a determination of the overall E       reliability of the new system. [While a great deal is currently @       known about software reliability, much more is known about       hardware reliability.]  E    2) If a change is introduced into the software which is running on E       a particular CPU chip, specifically a change which now requires @       that a previously unused "op-code" come into use, there isF       little need to replace (or alter) the CPU chip. [Think of an Ada?       package as a chip, and the operations in its interface as E       "op-codes."] A similar argument could be made for the amount of =       random access memory incorporated in a computer system.   C    3) As new engineers are assigned to a project, it is likely that E       they may have experience with standard, reusable chips. Even if E       they do not have experience with the specific chips being used, @       there are certain fundamental concepts which are common toF       particular classes of chips, and the new engineers are likely to!       be aware of these concepts.   E    4) With the demand for computer hardware (everything from embedded B       systems to stand-alone computers) at an ever increasing highF       level, the cost and time required to custom-design chips so thatC       they are optimized for a specific application is prohibitive. E       [Notice that since few organizations track real software costs, D       that it is often difficult to make a similar justification for'       not overly-customizing software.]   C How does one apply the above analogy to reusable software? Consider D the design of a reusable software component. To be truly reusable, aF software component must be usable in some place other than its currentA specific application (or part of an application). To increase the > chances of this happening, the software engineer must make the= component more general. In fact, there are well-known ways of @ increasing the generality of a software component to a very high level.    > Of course, there are trade-offs. Increasing the generality mayD decrease the efficiency, or even increase the complexity. These, andB other considerations, must be balanced against such factors as theE potential increased reliability resulting from using a known verified A component, and the cost and times savings resulting from software  reuse.  + 3.0   A Description of the Specific Problem   E In the past year there has been no shortage of "software reusability" E presentations. Those of us on the "Software Reusability Circuit" seem D to take our show to an every widening audience. If you have attendedF any software reusability presentations, or if you have read any of the@ increasing numbers of articles on the subject, you have probablyA noticed a pattern. Typically, the presenter or author describes a B "research project," or describes what sounds like a good idea, but$ "hasn't yet been put into practice."  ; This points out one of the interesting human aspects of new E technology. Since introduction of new technology requires change, and C human beings are, by nature, conservative, it almost always takes a D certain minimal amount of time before new technology can actually beB introduced into the workplace. So we go about our "dance." We have? meeting after meeting on the topic, and everyone seems to be in A general agreement (software reusability sounds like a nice idea). B However, nothing gets done until someone actually demonstrates the, validity of the concept on a "real" project.  C At my company, we have both discovered (probably re-discovered) and F demonstrated some of the fundamental concepts of software reusability.D Further, since we often find ourselves in a teaching role, we try toE communicate these concepts to our clients during the normal course of A our classroom instruction. Almost always, our students have "real E projects" to which they must immediately apply the technology covered D in our classes. As you are probably aware, teaching in industry must+ be very pragmatic, and real world oriented.   E Recently, one of us was describing how to increase the reusability of D software components during a class at the previously mentioned large@ aerospace firm. He was informed that while the techniques he wasA describing might indeed increase the reusability of Ada software, F there were forbidden by specific DoD policy. I asked the instructor to< have the students document the problem. What follows is that documentation:  C    1) MIL-HDBK-272 requires that there be no "extraneous code" in a C       program that is involved in the Nuclear Safety community. The B       "extra" functions which might make a software component moreC       general, and hence more reusable, are forbidden. [Notice that D       this (unknowingly) trades off one kind of software reliabilityF       (i.e., the increased reliability resulting from less code in theE       software product) against another (i.e., the potential increase @       in software reliability resulting from the use of a known,       verified component.]  E    2) C/SCSC - AFPRO/DCAA (no, unfortunately, I don't know what these D       acronyms stand for, however they refer to an auditing agency).G       There are audits to insure that the contractor is only doing what @       the contract states. [This is part of a classic "Catch 22"F       phenomenon. Specifically, it may be permissible for a contractorC       to reuse software (although given the current hostile climate C       for "extraneous code," this may be difficult), however no new D       reusable software may be generated on a project if it requiresD       any generality outside of the scope of the immediate problem.]  =    3) The original contract had *no* requirement for reusable ?       software. If any resources are expended on increasing the C       reusability of any of the software components, the contractor D       will not be compensated for these expenditures. [Another axiomE       of reusability is that the original design, implementation, and ?       verification of a reusable component are more costly than @       similar processes carried out without reusability in mind.?       However, the more reusable the component, the quicker the 2       payback and the greater the future savings.]  A    4) A particular danger, according to the contractor, (one that	A       DCAA/AFPRO will look for) is that if the contractor createseE       reusable software on a cost-plus-fixed-fee contract, he may notgA       reuse the software on a fixed price contract and charge thesB       government (again) for the software. [This is an interestingF       paradox. The government would rather pay the much larger cost ofD       a completely original piece of software, than be charged twiceD       for the same reusable software components -- even if the reuse=       of software components results in a greatly reduced neww       product.]s  D    5) The cost of documenting and distributing the reusable softwareF       would not be an allowable cost on any contract. [Here, I have noA       sympathy for the contractor. This is merely a cost of doinge@       business, and further, such costs can be factored into the       contractors fee.]a  
 4.0   Summaryo  B Both the DoD and the contractors which provide software to the DoDD will have to change the way they do business if they wish to realizeF the promised benefits of reusable software. Much more thinking will beB required on both sides. In the end, governmental software policiesF will have to change, or their interpretations will have to become moreF liberal. The contractors have as much to change (if not more) than the government.u  A Software reusability, unlike a great deal of software engineeringeF technology, can show a payback in a relatively short period of time. ID hope that both the government, and the software community as a whole$ expend the time and effort required.   				-- Ed Berard 				   (301) 695 - 6960l -------e