byrley@NTSC-74.ARPA.UUCP (05/15/87)
OK, I threatened, and here it is! Another chance for industry
to help government write better RFPs. Please give me your ideas
and criticisms. I have thick skin and am providing the straw man
below as only a starting place. I certainly will also accept
ideas from other Govt folks.
Paul
------------------------------------------------------------
Subject: Issue 2
Issue: Ada Methodology Requirements For Contracts
The Government wishes to encourage contractors to use the most
life cycle cost effective means of developing Ada code. This
desire certainly will include use of methodologies other than
those used with older HOLs (e.g. functional decomposition).
The methodologies to be used may include commercial software tools
or other modern improvements. [anything else?]
While the best methologies for any particular job are desired,
some consideration must be given to DoD's competition in contracting
act requirements; we will not (normally) be able to sign up to
methodologies which "lock in" a given contractor for the whole
life cycle. I would like to know if there is a real problem here
for the contractors.
What kind of contractual language might allow industry to propose
the best methodologies for an Ada development and yet let bid teams
know that they shouldn't propose a method which would preclude
competition for work later in the life cycle? Also, how can the
government evaluate obscure but very good methodologies when they
are proposed? Is industry willing to provide a written tutorial
on their proposed methodologies (tutorial will be proprietary in
proposal) so government evaluator can decide which is "best"?
How can Govt perform a valid risk assessment if one of the
obscure but innovative methodologies is proposed?
as a strawman, consider the following and build on it:
_________________________________________________________________
SOW Language-
1.3.6.1.1 The contractor shall design and develop or produce software
using modern methodologies in an integrated APSE suitable for Ada
development under this contract.
***[there must be more than this!]***
___________________________________________________________________
Specification Language-
3.6.8.6 The software methodologies used shall be (or shall be
clearly based on ) commonly known methodologies
such as Object Orientated Design (OOD), or commercially available
methodologies. Other methods (such as rapid prototyping or structured
analysis) may also be used in conjunction with the
selected software methodologies.
Formal training in each methodology used shall be available
and shall be provided for each of the software development personnel
assigned to this contract except those personnel already experienced in
the methodology.
[note: is this too restrictive of the new "magnificent" innovative
approach? remember, I have to be able to throw out the "buy in" contractor
who doesn't know anything about Ada, else you folks who paid your
dues won't win any contracts.]
3.6.9.2.1 APSE Integration- The methodologies used to design/develop
software under this contract shall be fully integrated with the APSE
provided.
****[does anyone know how to talk about integration in a spec?
I want to include going from user requirements to top level
design as well as top lev. design, detailed design and code.]****
____________________________________________________________________
Technical Proposal Requirements (The Govt's instruction to the bidder
for required content of his proposal)
4.4 SOFTWARE METHODOLOGY(IES)
4.4.1 The offeror shall describe each methodology proposed and the
interface between them. Design methology(ies) shall trace requirements
from the user through high level and detailed design. Coding and
testing methodologies shall be desribed as a continuation of the design
process, with particular attention being given to the integration
of all steps in the process.
4.4.2 The offeror shall describe, in detail, the training offered
for the proposed methodologies and the training required for each
experience level personnel. The offeror shall describe the length
and degree of detail of the training and who, of the proposed
software personnel will take the training. State when, in the
contract life, will the various training be given. State previous
experience of personnel who have been trained in or used the
proposed methodologies.
------