TEAM-ADA Archives

Team Ada: Ada Programming Language Advocacy

TEAM-ADA@LISTSERV.ACM.ORG

Options: Use Forum View

Use Monospaced Font
Show HTML Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Sender:
"Team Ada: Ada Advocacy Issues (83 & 95)" <[log in to unmask]>
Date:
Wed, 7 Apr 1999 11:07:08 -0500
Reply-To:
Content-type:
text/plain; charset=US-ASCII
Subject:
From:
Phillip Johnson <[log in to unmask]>
Content-transfer-encoding:
7BIT
In-Reply-To:
Organization:
PEI Electronics Inc
MIME-Version:
1.0
Parts/Attachments:
text/plain (21 lines)
> > I was told that none of the software could be written in Ada,
> > even if it came as part of a COTS product.
>
> The latter restriction doesn't make sense. Isn't the whole
> idea with COTS software that you never see the source code
> and that you definitely don't care about such details as
> programming language? The software just has to work and the
> should include a life-time service contract in the price.

I spoke to one of our contracts people and she said if it is COTS
they only can say it does the required task or it doesn't.  They can
not specifiy any restriction on how the product is produced.  This is
per the FAR (Federal Acquisition Regulation).  Who ever wrote this
requirement has set the project up to be ripe for protests and
adjudication that could tie the project up for a long time.  Can you
doomed for failure?


Phil Johnson
[log in to unmask]

ATOM RSS1 RSS2