Overview .
This "COTS Software
Management Process" has been prepared as guidelines for the developer
and/or subcontractor software project manager for satisfying the requirements
for the projects when applied to incorporating COTS, GOTS, reused, and other
NDI products.
This document has been
prepared using the requirements determined by MIL-STD-498 and ISO/IEC 12207.
This process will also be continued for the process improvement and enhancement activities after the initial standards baseline has been established.
Commercial
Off-The-Shelf (COTS) Software Management Policy
Definition: COTS computer resources consist of
commercially-available software packages, readily available in identical form
to any developer/subcontractor.
The COTS software
management policy goals are to:
Ø
Promote acquisition
of COTS software as an alternative to in-house development;
Ø
Increase customer
satisfaction by ensuring availability of existing software capabilities;
Ø
Reduce software
development and maintenance costs and software delivery time by eliminating
redundant development;
Ø
Control modification
of COTS software to ensure standardization;
Ø
Ensure compliance
with this 'COTS Software Management Process' document.
Policy
is:
For each COTS software
package, the project office shall obtain a system/software identifier and data
system designator and appoint software project manager, in accordance with
established management procedures.
All managers for COTS
software acquisitions shall follow the guidance and procedures set forth in
this document.
Software project managers
shall co-ordinate COTS software acquisitions.
Project managers shall
ensure that appropriate licensing requirements are satisfied to authorize
operational use of the software at planned implementation sites.
Project managers for COTS
software acquisitions shall ensure acquired software resources are fully tested
and satisfy user requirements.
Project managers shall
not allow development or maintenance of local code that in any way changes the
use or functionality of the COTS software without approval. This includes, but shall not be limited
to, front-end or back-end processors and changes to vendor documentation. Waivers or deviations (if necessary)
shall be submitted i.a.w. the SCMP and co-ordinated with programme
organizations.
SMG shall maintain this
document. Users of this document
may report deficiencies and or corrections using the format provided by the
attached Document Change Request (DCR) form. SMG shall configuration manage this
data as part of the process improvements initiative.
Back to Home page MANAGING STANDARDS
Home page
Please send any
beneficial comments or identification of errors using the following form to: kenr@wysywig.airtime.co.uk
Copyright © Ken Rigby 2003, 2004