l

l

l

l

l

1

a. How does it maximize the use of COTS technology? [Ref. Matrix+ #4a]

b. To what extent are (will) COTS/GOTS (be) utilized to satisfy the system requirements? Describe. [Ref. Matrix+ #4a] (See 1.1-4)

c. How will core functions and military-unique requirements be satisfied? Indicate where COTS/GOTS will be considered. [Ref. Matrix+ #1b]

d. Based on remaining questions in this section, describe how the COTS/GOTS approach is appropriate.

l

l

l

l

l

2

a. How does the system support core/primary mission functions as documented in the Department of Defense (DoD) Strategic Plan, Army Strategic Plan, and the Army Investment Strategy? Which functions? [Ref. Matrix+ #1a]

b. Does the system perform inherently Government functions? Which function(s)? [Ref. Matrix+ #2a]

c. Does the system require unique capabilities? Which capabilities and why? [Ref. Matrix+ #2b] (See 1.1-4a)

d. What percentage of the requirements are truly "military unique"? [Ref. Matrix+ #2c]

e. What needs or restrictions could preclude use of COTS (or GOTS)? [Ref. Matrix+ #4c]

l

l

l

l

l

3

a. What is the approach for the market survey? What were the results?

b. How often has the Program Management Office (PMO) or the developer resurveyed available GOTS/COTS to assess new or changing products, market trends, and support reliability? Describe the results and changes.

l

l

l

l

l

l

4

a. What capabilities and percentage of the requirements can be satisfied by GOTS? By COTS*?

b. What desired capabilities are not available, and how critical are they?

c. Does the program require the reuse of specific COTS or GOTS software products (e.g., Common Operating Environment) in the system? Describe the rationale and progress made to date.

(*If COTS products meet 85% of the solution, COTS should be used.)

l

l

l

l

5

a. Is there adequate consideration of the issues, including: insufficient documentation to determine interfaces, size, or performance; poor performance; requires a large share of memory or data storage; difficult to interface with application software; not thoroughly tested; not bug free; not maintained adequately; responsiveness of support; cumbersome license-checking; insufficient capacity [Mod TBQ29]?

b. Are there adequate workarounds for problems and serious problems?

l

l

l

l

6

a. Has a plan been developed to integrate and test updates, revisions, or replacement COTS after deployment? Describe the approach. Provide a copy. (See 7.3-2) [Ref. Matrix+ #4g]

b. Describe the process used to validate long-term supportability of the COTS/GOTS software. (See 7.3-4d; see also 7.3-4e) [Ref. Matrix+ #4i]

c. Were any products or component parts made obsolete by other commercial products? Do replacement products need to be acquired? Describe. What provisions are there for period monitoring and acquisition of COTS products?

d. What provisions are there for periodic monitoring and acquisition of COTS products?

e. How long will the COTS products be viable and adequately supported? Are there any anticipated new products or upgrades in the near term or foreseeable future? Describe.

f. What is the projected life for each COTS software product? (See 7.1-8b)

g. How is Y2K compliance assured? (See 1.2-4)

l

l