5. ADDITIONAL SYSTEM SOFTWARE FACTORS (Describe any additional factors that could affect the cost and/or size of the software
being developed for the system.)
SECTION II - LOWER-LEVEL CHARACTERISTICS
6. CSCI (CSC)-LEVEL CHARACTERISTICS
a. CSCI (CSC) NAME
b. FUNCTIONAL DESCRIPTION (When available, this description should map to the functional allocation document)
7. GENERAL INFORMATION
a. APPLICATION TYPE (X all that apply)
b. APPLICATIONS DOMAIN (Enter percentage of all that apply)
(1) Prototype to be discarded later
(1) Command and Control
(8) Environment/Tools
(2) Prototype to be built into delivered program
(2) Graphics, Image Processing
(9) Training Software
(3) Complete stand-alone program
(3) Communications
(10) Other Support Software
(4) Component within a system
(4) Signal Processing
(11) Avionics
(5) Reusable component for multiple programs
(5) Process Control
(12) Other (Specify)
(6) System with multiple components
(6) Interface Systems
(7) Additional Comments
(7) Test Systems
(13) Additional Comments
c. SOURCE CODE MIX (Enter percentage of all that apply)
(1) Operating Systems
(4) Mathematical Operations
(7) String Manipulation
(8) Other (Specify)
(2) Real-Time Command & Control
(5) Interactive Operations
(3) Data Storage and Retrieval
(6) On-Line Communications
(9) Additional Comments
d. DEVELOPMENT METHOD
e. SOFTWARE INTENDED USE (X one)
(1) Embedded - identify associated hardware system(s)
(1) Ada Development
(4) Prototype
(7) Waterfall
(2) Ada Incremental
(5) Spiral
(2) Other (Specify)
(3) Ada Full Use
(6) Traditional Incremental
(8) Additional Comments
f. SOFTWARE NOVELTY. Is this the first CSCI or CSC of its kind, or are the functions and characteristics well understood and used
elsewhere in the system? (X one)
Yes
No
g. PROGRAMMING PERSONNEL CAPABILITIES AND EXPERIENCE
(1) Does programming personnel have analysis capabilities experience?
(3) Identify staff programming capabilities.
(Indicate yes or no; indicate number of years experience.)
(2) Does programming personnel have analysis application experience?
(4) Identify programmer language experience (by language and
(Indicate yes or no; indicate number of years experience.)
number of years experience)
h. SOFTWARE SCHEDULE
i. SCHEDULE AND STAFFING CONSTRAINTS (X one)
(3) Extended
(1) Attach software schedule to this form
(1) Accelerated schedule
schedule
(2) Identify start date for requirements phase
(2) Normal schedule
k. REQUIRED DOD-STDS
j. SECURITY CLASSIFICATION (DoDD 5200.28 (reference (g)) classification)
(X one)
(1) Complete 2167A (reference (h)) documentation
(1) Class D
(3) Class C2
(5) Class B1
(7) Class B3
(2) Subset of 2167A (reference (h))
(2) Class C1
(4) Class C3
(6) Class B2
(3) Other (Specify)
DD Form 2630, AUG 92
Page 2 of 4 Pages