cdcaas-spmp-1.0

8/3/2019 CDCAAS-SPMP-1.0

1/223

Crime Data

and Assimi

Software 62

Submiss

Collection, Aggre

lation System (CDVersion 1.0

Team Crime Busters

Sonal VermaBrian H. ParkAkhil Pathania

John Kraus5 -Software Project Managemerofessor Ken Nidiffer

ion Date: December 8, 2008

ation

AAS)

nt


2/223

Crime Data Collection, Aggregation and Assimilation System (CDCAAS) Version 1.0

Team Crime Busters 12/08/2008SWE 625 - Professor Kenneth Nidiffer

ii

RevisionsRevisionNumber Date Section Name Description

SectionUndated Remarks

0.1 9/11/2008Preface and1.1 ProjectOverview

First draftPreface and

1.1

0.1 9/13/2008Preface and1.1 ProjectOverview

Updatedocument

based on teamreview

Preface,1.1.1 and

1.1.2

Decided projectname and team

name

0.1 9/14/2008Project

DescriptionAdded Figures All

0.12 9/18/2008Project

Description

Updated thepackage

description

1.1.1

0.12 9/21/2008Requirement

EstimateFirst Draft 5.3

0.12 9/28/2008ProcessModel

First Draft 2.1

0.13 10/25/2008 Productivity First Draft 3.4.4

0.14 11/09/2008Dependencies

First Draft 5.2

0.15 11/16/2008ReferenceMaterials

Final Draft 1.4

1.0 12/08/08 Complete


3/223



iii

PrefaceThe following preface is a short narrative on the purpose of the Crime Data

Collection, Aggregation and Assimilation System (CDCAAS) project.The CDCAAS will provide police officers and investigators with the ability toconveniently and quickly acquire and assimilate, from a variety of diverse electronicsources, information needed to help solve or prevent crimes or hunt down andapprehend criminals. CDCAAS will be a valuable tool for investigators seeking toconnect the dots in their efforts to protect the public and bring wrongdoers tojustice.

CDCAAS is the first in a new series of applications software suites for System XYZ.System XYZ will be the next major product line for our company, making this projectand this Software Project Management Plan (SPMP) extremely important to the

continued success of the organization.Furthermore, the CDCAAS project embodies our companys ambitious set of strategicredirection actions to strengthen our responsiveness to customers, increasecompetitiveness by reducing costs, build market share, and field quality products thatmeet or exceed customer requirements.

Our recent market study concluded that the features offered by the proposed set ofsoftware packages for the new System XYZ computer system will be crucial inachieving our goals for market penetration. This conclusion has been borne out by700 advance orders received for the CDCAAS.


4/223



iv

AbstractThe Software Project Management Plan (SPMP) contains detail documentation of the

technical and management aspects involved in various stages in the development ofthe Crime Date Collection, Aggregation and Assimilation System (CDCAAS). Thedocument adheres to the specification provided by the IEEE Standards (1058.1). Thisdocument serves as a controlling document for organizing and managing the resourcesin such a way that these resources deliver all the work required to complete theproject within define scope, time and cost constraints.

The document is intended to answer various challenges involved in managing theproject like meeting project deadlines, integration of inputs needed to meet pre-defined objectives of providing a cost effective, efficient and automated way ofassimilating data about the criminals from one place rather than from differentresources. This document will be subject to revisions as the project progresses.


5/223



v

Project Charter

Project Sponsor InformationSponsor Name: Susan Smith

Title: Vice President, New Software and Systems EngineeringDevelopment

Business Need: The Crime Data Collection, Aggregation and Assimilation system(CDCAAS) will provide enhanced functionality for more efficientsearches for the crime data stored in the different kinds of biometricdatabases. This system shall be used by country wide lawenforcement agencies. The primary goal is to provide users with aunified tool that will have the capability to work of differentplatforms, understand all secure formats, and communicate overbroad range of medium without compromising on the stringent level

of security that is specific to the government agencies and othercorporations. Secondary goals include reduction in operational costand increase in profit margin by providing stable and reliablesoftware.

Business Benefits: System XYZ will allow the corporation to become the leadingprovider of Crime Data Collection, Aggregation andAssimilation software at all levels of government and in thecommercial sector

Continued improvement in the quality of life Improved overall data integrity and speed of data access to

optimize decision making Faster and Higher rates case-closing through more efficient

gathering and analysis of crime- related data.

Table 1: Project Sponsor Information

Major Deliverables

Product(s) or Service(s)

Data Management Knowledge Distribution and Delivery

Analysis and Statistics Information Retrieval , Reports andNotification

Schedule Constraints and Assumptions

Planned Start Date:January 28, 2008

Planned End Date:January 28, 2010

Latest End Date:


6/223



vi

Major Deliverables

Schedule Assumptions: CDCAAS will be developed during the next 24 months with

many intermediate product releases during the abovementioned period. The alpha test is scheduled on orbefore Jan 28, 2010.

Schedule Constraints: Schedule Allocation is as follows:

24 months CDCAAS development

2 months alpha test at Fairfax, VA (in-house)

2 months beta test at Chelmsford, MA (customer site)

2 months rollout to customer sites which includesinstallation and training

6 months maintenance

Table 2: Major Deliverables

Key Staffing RequirementsProject Manager: Title: Date Available:

Project Manager: Title: Date Available:

Table 3: Key Staffing Requirements

Other Constraints and Assumptions

Constraints CDCAAS software will extend the System XYZ software. CDCAAS willextend the 11 existing System XYZ packages. Three modules will beextended through COTS packages, three will extend reusable portionsof software, and the remaining five modules will be custom written.

One of the five custom modules will be outsourced to Ivan Industries.

Table 4: Other Constraints and Assumptions


7/223



vii

Initial Cost Estimate for CDCAAS

Labor cost per hour: $200Hardware cost per unit: $1,500Number of Units: 700Kernel KSLOC 20

Application Software Cost

Equation I: (Number of Staff Hours) * Labor CostTotal Effort (Staff Months) = 1,030.05Total Effort (Staff Hours) = 164,807.34Staff Hours Per Month = 160.00Labor Cost per hour = $200.00

ApplicationSoftware Cost

=

$32,961,467.66

Cost Per PackagePackage Name Staff Months Cost

Database ManagementSystem

93.31 $2,985,839.13

Spreadsheet 41.14 1,316,356.25Reqm'ts & Config. Mgmt. 174.39 5,580,610.84Secure Communication 185.41 5,933,252.92Graphics Presentation 41.11 1,315,393.59

Word Processor 98.27 3,144,759.78Project Management 41.13 1,316,050.46GPS Navigation 135.15 4,324,790.21Compiler 41.09 1,315,009.16Debugger & Test 102.50 3,279,969.71Electronic Inventory &Tracking

76.54 2,449,435.62

Total 1,030.05 $32,961,467.66

System Kernel Software (assuming Kernel size is 20K SLOC)

COCOMO man-month effort = 7.39 * (KSLOC) ^ 1.2

Total Effort (Staff Months) = 269.08Total Effort (Staff Hours) = 43,052.70Labor cost per hour = $200.00

Kernel Cost = $8,610,540.45


8/223



viii

System XYZ Hardware

Equation 2: Cost per unit * No. of UnitsCost per unit = $1,500

No. of Units = 700Hardware Cost

=$1,050,000.00

Subtotal = $42,622,008.12

Table 5-Initial Cost Estimate for CDCAAS


9/223



ix

Project ScopeThe Crime Data Collection, Aggregation and Assimilation System (CDCAAS) project

provides police agencies such as the Federal Bureau of Investigation (FBI), Interpol,Department of Homeland Security, Law Enforcement and Corporations the capabilityfor a secure, efficient and reliable mechanism to acquire detailed crime-solvingrelated information in a cost-effective and time saving manner. All CDCAAS softwarewill be designed, implemented, purchased, or subcontracted during the life of thisproject. This project will extend the existing System XYZ software packages dividedinto various methods of implementation.

Three packages will be Commercial-Off-The-Shelf (COTS) products. Three packageswill leverage reusable components as building blocks. Five packages will be customdesigned and developed. One of the five custom packages will be outsourced to IvanIndustries. All sub-phases of the project including requirements, preliminary anddetailed design, code, and unit testing will be conducted during the CDCAAS project.Subsequently, the CDCAAS project will conduct alpha and beta tests and lead therollout of the software into production. Installation and user-training will be providedby the CDCAAS project. Additionally, this project will provide 24 hour help-deskservice and support for a six-month maintenance period after completing installationsat each site.

Exclusions to the project include any connectivity or supporting hardware installationsand delivery that are necessary for the CDCAAS software to function. Other notableexclusions include: Multi-Language Translation Packages, ability to edit CDCAASDocuments using other software, staffing support for Ivan industries, and extended

support and maintenance plans.CDCAAS Hardware (Notebook Configuration):

Two Universal 2009-B microprocessors, 3.4 GHz 20.1 inch display A three-button mouse point device 4 GB of main memory (SDRAM) 16 MB Video RAM 320 GB primary hard drive DVD/R/RW AMD CD-RW Combo Drive A 100 MB ZIP drive Integrated 2.0 MP camera Printer port Asynchronous port Integrated 802.11 g wireless LAN Four USB ports 1394/FireWire connector A LAN interface card


10/223



x

A 56,000 bps capable fax/modem Anti-virus/security suite Video Card

CDCAAS Notebook Bundled Devices Speakers Head phones Laser printer 9-cell lithium ion battery MP3 30 GB audio/video player A Bar Code scanner Personal Assistant Device (416 megahertz, 1 GB RAM) 48-bit Color Flatbed Scanner (2400 dpi optical resolution) System ABC enhanced keyboard

A CRT monitor (1,280 x 1,024 non-interlaced; high resolution; bit-mapped; 21inch color display)

Port replicator A stand for the CRT monitor Power connector Digital camcorder Internal Speakers Wireless Digital Phone with voice mail messaging and internet service

CDCAAS Application Packages:

CDCAAS Database Management System CDCAAS Spreadsheet CDCAAS Requirements and configuration Management CDCAAS Secure Communication CDCAAS Graphics Presentation CDCAAS Word Processor CDCAAS Project Management CDCAAS GPS Navigation CDCAAS Compiler CDCAAS Debugger & Test CDCAAS Electronic Inventory and Tracking


11/223



xi

Table of ContentsRevisions ........................................................................................... iiPreface ............................................................................................. iiiAbstract ............................................................................................ ivProject Charter .................................................................................... vInitial Cost Estimate for CDCAAS .............................................................. viiProject Scope ...................................................................................... ixTable of Contents ................................................................................. xiTable of Figures .................................................................................. xivIndex of Tables .................................................................................. xvii1. Introduction ..................................................................................... 1

1.1. Project Overview .......................................................................... 11.1.1. Project Description ................................................................... 11.1.2. Product Summary ................................................................... 10

1.2 Project Deliverables ..................................................................... 151.2.1 Software Applications, Computer Software Configuration Item (CSCI) ...... 151.2.2 Delivery Locations and Quantities ................................................ 161.2.3 Documentation....................................................................... 171.2.4 Delivery Customer Acceptance .................................................... 17

1.3 Evolution of the Software Project Management Plan ............................... 181.4 Reference Materials ...................................................................... 191.5 Definitions and Acronyms ............................................................... 19

1.5.1 Definitions ............................................................................ 191.5.2 Acronyms ............................................................................. 22

2. Project Organization ......................................................................... 272.1 Process Model ............................................................................. 27

2.1.1 Process Milestones .................................................................. 272.1.2 Baselines .............................................................................. 302.1.3 Reviews ............................................................................... 30

2.2 Organizational Structure ................................................................ 332.3 Organization Boundaries and Interfaces .............................................. 402.4 Project Responsibilities.................................................................. 42

2.4.1 Project Manager ..................................................................... 422.4.2 Assistant Project Manager .......................................................... 422.4.3 Chief Software Developer .......................................................... 422.4.4 Administrative Assistant ............................................................ 422.4.5 System Engineer/Analyst ........................................................... 422.4.6 Requirements Analysts.............................................................. 422.4.7 Technical Team Leader ............................................................. 422.4.8 Software Developers ................................................................ 422.4.9 Testers ................................................................................ 432.4.10 Help Desk Technician .............................................................. 432.4.11 Project Specialists ................................................................. 43


12/223



xii

3. Managerial Process ........................................................................... 573.1 Management Objectives & Priorities ................................................. 57

3.1.1 Goals & Objectives .................................................................. 573.1 Management Objectives & Priorities ................................................. 58

3.1.1 Goals & Objectives .................................................................. 583.1.2 Management Priorities .............................................................. 603.1.2 Management Priorities .............................................................. 61

3.2 Assumptions, Dependencies and Constraints ......................................... 623.2.1 Assumptions .......................................................................... 633.2.2. Dependencies ....................................................................... 633.2.3 Constraints ........................................................................... 63

3.2 Assumptions, Dependencies and Constraints ......................................... 643.2.1 Assumptions .......................................................................... 643.2.2. Dependencies ....................................................................... 643.2.3 Constraints ........................................................................... 65

3.3 Risk Management ......................................................................... 653.4 Monitoring and Controlling Mechanism ................................................ 67

3.4.1 Schedule .............................................................................. 673.4.2 Budget ................................................................................ 693.4.3 Quality Assurance ................................................................... 703.4.4 Productivity .......................................................................... 723.4.6 Measures .............................................................................. 76

3.5 Staffing Plan .............................................................................. 793.5.1 Obtaining ............................................................................. 793.5.2 Training ............................................................................... 793.5.3 Retaining.............................................................................. 793.5.4 Phasing out of personnel ........................................................... 803.5.5 Staff Expertise ....................................................................... 96

4. Technical Process ............................................................................. 984.1 Methods, Tools & Techniques ........................................................... 984.2 Software Documentation ............................................................... 1014.3 Project Support Functions ............................................................. 105

4.3.1 Configuration Management ....................................................... 1054.3.2 Quality Assurance .................................................................. 1074.3.3 Verification and Validation ....................................................... 1084.3.4 Test Evaluation ..................................................................... 1094.3.4 Test and Evaluation ................................................................ 109

5. Work Packages, Schedule, and Budget ................................................... 1105.1 Work Packages ........................................................................... 110

5.1.1 Work Breakdown Structure ....................................................... 1105.1.2 Work Package Specifications ..................................................... 116

5.2 Dependencies ............................................................................ 1185.3 Resource Requirement .................................................................. 1365.3 Resource Estimate ....................................................................... 145


13/223



xiii

5.4 Budget and Resource Allocation ....................................................... 1595.5 Schedule .................................................................................. 162

Additional Components ........................................................................ 1721.1. Subcontracting Process ................................................................ 172

1.1.1 Selection of Subcontractors ....................................................... 1721.1.2. Coordinating with Subcontractors .............................................. 1741.1.3. Integrating with Subcontractors ................................................. 1741.1.4. Controlling Subcontractors ....................................................... 175

2.1. Security Considerations ................................................................ 1753.1. Training Plans ........................................................................... 1764.1. Alpha & Beta Test Plan ................................................................ 176

4.1.1. Alpha Testing ...................................................................... 1764.1.2. Beta Testing ........................................................................ 178

5.1. Installation & Training Plans .......................................................... 1786.1. Post Deployment Support Procedures ............................................... 179

Index .............................................................................................. 180Appendix I ........................................................................................... 1

Detailed Resource Estimate Spreadsheet (23 columns plus intermediatecalculations) attached. ....................................................................... 1

Appendix II .......................................................................................... 1Detailed Resource Estimate Spreadsheet with formulas revealed--attached. ......... 1

Appendix III ......................................................................................... 1Work Package Specifications .................................................................. 1

Configuration Management ................................................................. 1Communication ............................................................................... 2Graphic Presentation ........................................................................ 3Word Processing .............................................................................. 4Project Management ......................................................................... 5Global Positioning System Gps .............................................................. 6Compile/Link/Runtime ...................................................................... 7Language Independent Debugging And Testing .......................................... 8Electronic Inventory and Tracking ......................................................... 9

Binder Back Cover ............................................................................... 10


14/223



xiv

Table of FiguresFigure 1: Operational Architecture ............................................................. 3Figure 2: Network Architecture .................................................................. 4Figure 3: Product Technical Architecture ...................................................... 5Figure 4: Software Architecture ................................................................. 6Figure 5: Notebook Hardware Architecture .................................................... 7Figure 6: Standalone Environment .............................................................. 8Figure 7: Mobile Client/Server Architecture Only ............................................ 8Figure 8: Client/Server Architecture with Central Location ................................ 9Figure 9: Activities, Benchmarks and Success Indicators .................................. 30Figure 10: CDCAAS Organization Chart ....................................................... 34Figure 11: Software Division Organization Chart ............................................ 35Figure 12: CDCAAS Project Organization Chart .............................................. 36Figure 13: Analysis Design and Development Team ......................................... 38Figure 14: CDCAAS Project Team Structure .................................................. 39Figure 15: Program Manager Organizational Interfaces .................................... 40Figure 16: Project Manager Organizational Interfaces ..................................... 41Figure 17: Responsibility Matrix Summary ................................................... 44Figure 18: Total Project Responsibility Matrix .............................................. 45Figure 19: Database Management System Package Responsibility Matrix ............... 46Figure 20: Compiler Package Staffing ........................................................ 81Figure 21: GPS Navigation Package Staffing ................................................. 83Figure 22: Graphics Package Staffing ......................................................... 87Figure 23: Total Project Staffing Chart ....................................................... 89Figure 24: Total Project Staffing by Package ................................................ 91

Figure 26: Document Production Process Flow Chart ..................................... 104Figure 27: Work Breakdown Structure (Overall) ........................................... 110Figure 28: Figure 27: Work Breakdown Structure (Secure Communication) ........... 111Figure 29: WBS GPS Navigation ............................................................... 111Figure 30: WBS Database Management System ............................................. 112Figure 31: WBS Spreadsheet .................................................................. 113Figure 32: Dependencies (Part 1) ............................................................ 118Figure 33: Dependencies (Part 2) ............................................................ 119Figure 34: Dependencies (Part 3) ............................................................ 120Figure 35: Dependencies (Part 4) ............................................................ 121Figure 36: Dependencies (Part 5) ............................................................ 122

Figure 37: Dependencies (Part 6) ............................................................ 123Figure 38: Dependencies (Part 7) ............................................................ 124Figure 39: Dependencies (Part 8) ............................................................ 125Figure 40: Dependencies (Part 9) ............................................................ 126Figure 41: Phase Distribution (Project Overall) ............................................ 127Figure 42: : Phase Distribution (Project Plans & Requirements)......................... 127Figure 43: : Phase Distribution (Project Programming) ................................... 128


15/223



xv

Figure 44: Distribution (Project Product Design) ........................................... 128Figure 45: Phase Distribution (Project Integration & Test) ............................... 129Figure 46: Project Maintenance (Part 1) .................................................... 129Figure 47: Project Maintenance (Part 2) .................................................... 130Figure 48: Project Maintenance (Part 3) .................................................... 130Figure 49: Project Maintenance (Part 4) .................................................... 131Figure 50: Module Overall (Database Management) ....................................... 131Figure 51: Module Plans & Requirements (Database Management) ..................... 132Figure 52: Module Programming (Database Management) ................................ 132Figure 53: Module Product Design (Database Management) .............................. 133Figure 54: Module Integration & Test (Database Management) .......................... 133Figure 55: Module Maintenance (Database Management Part 1) ....................... 134Figure 56: Module Maintenance (Database Management Part 2) ....................... 134Figure 57: Module Maintenance (Database Management Part 3) ....................... 135Figure 58: Module Maintenance (Database Management Part 4) ....................... 135Figure 59: Resource Loading Chart 1......................................................... 136Figure 60: Resource Loading Chart 2......................................................... 136Figure 61: Resource Loading Chart 3......................................................... 137Figure 62: Resource Loading Chart 4......................................................... 137Figure 63: Resource Loading Chart 5......................................................... 138Figure 64: Resource Loading Chart 6......................................................... 138Figure 65: Resource Loading Chart 7......................................................... 139Figure 66: Resource Loading Chart 8......................................................... 139Figure 67: Resource Loading Chart 9......................................................... 140Figure 68: Resource Loading Chart 10 ....................................................... 140Figure 69: Resource Loading Chart 11 ....................................................... 141Figure 70: Resource Loading Chart 12 ....................................................... 141Figure 71: Resource Loading Chart 13 ....................................................... 142Figure 72: Resource Loading Chart 14 ....................................................... 142Figure 73: Resource Loading Chart 15 ....................................................... 143Figure 74: Resource Work Summary Report Chart ......................................... 143Figure 75: Resource Work Availability Report Chart ....................................... 144Figure 76: Software Productivity (SLOC/SM) by Application Domains .................. 146Figure 77: COCOMO Summary Screen ........................................................ 149Figure 78: COCOMO Product Parameters .................................................... 150Figure 79: COCOMO Platform Parameters ................................................... 150Figure 80: COCOMO Personnel Parameters ................................................. 151Figure 81: COCOMO Project Parameters .................................................... 151Figure 82: COCOMO Scale Parameters ....................................................... 152Figure 83: COCOMO Equation Parameters ................................................... 152Figure 84: COCOMO Phase Distribution-Project Overall................................... 153Figure 85: COCOMO Phase Distribution-Project Plans & Requirements ................. 153Figure 86: COCOMO Phase Distribution-Project Programming ........................... 154Figure 87: COCOMO Phase Distribution-Project Product Design ......................... 154


16/223



xvi

Figure 88: COCOMO Phase Distribution-Project Integration & Test ..................... 155Figure 89: Resource Estimate Spreadsheet Part 1 ......................................... 157Figure 90: Resource Estimate Spreadsheet Part 2 ......................................... 158Figure 91: CDCAAS System Master Schedule ................................................ 162Figure 92: Debugger & Test Schedule ........................................................ 163Figure 93: CDCAAS Electronic Inventory & Tracking/Custom Development DetailedSchedule ......................................................................................... 164Figure 94: CDCAAS COTS Development Detailed Schedule ............................... 165


17/223



xvii

Index of TablesTable 1: Project Sponsor Information .......................................................... vTable 2: Major Deliverables ..................................................................... viTable 3: Key Staffing Requirements ........................................................... viTable 4: Other Constraints and Assumptions ................................................. viTable 5-Initial Cost Estimate for CDCAAS ................................................... viiiTable 6: Profile of Typical Product Users .................................................... 13Table 7: Software Applications, Computer Software Configuration Item (CSCI) ....... 16Table 8: Delivery Locations and Quantities .................................................. 17Table 9: Delivered Documentation ............................................................ 17Table 10: Spreadsheet Package Responsibility Matrix ...................................... 47Table 11: Requirements & Configurations Package Responsibility Matrix ............... 48Table 12: Secure Communications Package Responsibility Matrix ........................ 49Table 13: Graphics Extension Package Responsibility Matrix .............................. 50Table 14: Word Processor Package Responsibility Matrix .................................. 51Table 15: Project Management Package Responsibility Matrix ........................... 52Table 16: GPS Navigation Package Responsibility Matrix .................................. 53Table 17: Compiler Package Responsibility Matrix .......................................... 54Table 18: Debugger and Test Package Responsibility Matrix .............................. 55Table 19: Electronic Inventory and Tracking Package Responsibility Matrix ............ 56Table 20: Risk Management Description and Mitigation Strategies ....................... 67Table 21: Compiler Package Staffing ......................................................... 82Table 22: GPS Navigation Package Staffing .................................................. 84Table 23: Secure Communication Package Staffing ........................................ 86Table 24: Graphics Package Staffing .......................................................... 88

Table 25: Total Project Staffing ............................................................... 90Table 25: Total Project Staffing by Package................................................. 92Table 27: Document Table .................................................................... 104Table 28: Work Breakdown Structure ........................................................ 115Table 29: Resource Estimate-Method 1 ...................................................... 147Table 30: Resource Estimate-Method 2 ...................................................... 148Table 31: Resource Estimate-Method 3 ...................................................... 148Table 32: Budget and Resource Allocation .................................................. 161Table 33: Current Price-Breakeven Table ................................................... 168Table 34: Decreased Price Breakeven Table ................................................ 169Table 35: Increased Price-Breakeven Table ................................................ 170

Table 36: Optimum Price-Breakeven Table ................................................. 171Table 37: Training Plans ....................................................................... 176


18/223


Team Crime Busters 12/08/2008SWE 625 - Professor Ken Nidiffer

1

1. Introduction

1.1. Project Overview1.1.1. Project Description

Government Law Enforcement Agencies face new challenges everyday and tooutsmart these challenges their dependency on technology is growing proportionally.Crime Data Collection, Aggregation and Assimilation System (CDCAAS) are a tooldesigned with enhanced functionality which will give these agencies an upperhand against Criminals. Our objective is to come up with a unified tool that will havethe capability to work of different platforms, understand all secure formats, andcommunicate over broad range of medium without compromising on the stringentlevel of security that is specific to the government agencies and other corporations.

CDCAAS will provide the corporate user with a pool of utilities that enables to takecontrol of various technical and managerial aspects of the functionality, informationcontrol, data abstraction, easy access to information and scheduling. The system willalso have the capability to be customized depending upon the changing corporateneeds. The outcome of the project will be a unified system providing the governmentagencies with all the information ever collected for the entity under the scanner.

Our goal of delivering the project on time with the committed capabilities, will writea new chapter of success for us. Capabilities delivered will include access control,identification, and data mining.

Delivery of the system capabilities to the 700 advanced orders and subsequent orders

will give the corporation a foot hold with financial stability. In addition, for each ofthe sites that have preordered systems we must install at least 50% of the systems andprovide training on our application packages for 50 users.

The enhancement for this application will involve producing additions to the followingpackages:

1. CDCAAS Database Management System - Custom Developed

2. CDCAAS Spreadsheet -COTS

3. CDCAAS Requirements and Configuration Management - Reuse

4. CDCAAS Secure Communication - Custom Developed

5. CDCAAS Graphics Presentation - COTS

6. CDCAAS Word Processor - Reuse

7. CDCAAS Project Management - COTS

8. CDCAAS GPS Navigation - Outsourced to Ivan Industries

9. CDCAAS Compiler - Reuse


19/223



2

10.CDCAAS Debugger & Test - Custom Developed

11.CDCAAS Electronic Inventory and Tracking - Custom Developed

This system is designed to be marketable to a wide variety of clients as follows:

It can be used at all levels of government from the federal government levelorganizations such as DHS, FBI, CIA and DOD all the way down to local lawenforcement level.

It can be customized for implementation in any corporation whether big orsmall to provide a one stop resource to manage information access and control.

Wide customization capability of the CDCAAS system in addition to providingcontrol, abstraction, access, and management of information makes it a globalperformer, and should make us a preferred choice the world over in the yearsto come.

The Department of Defense provides a set of guidelines known as SecurityTechnical Implementation Guides (STIG) that provide a security configurationbaseline; systems must meet to be used within the Department of Defense. Byfollowing these guidelines less time and money will be required for integrationby our team and by our federal customers, increasing the competitiveness andmarketability of our product.


20/223



3

Figure 1: Operational Architecture


21/223



4

Figure 2: Network Architecture


22/223



5

Figure 3: Product Technical Architecture


23/223



6

Figure 4: Software Architecture


24/223



7

Figure 5: Notebook Hardware Architecture


25/223



8

Figure 6: Standalone Environment

Figure 7: Mobile Client/Server Architecture Only


26/223



9

Figure 8: Client/Server Architecture with Central Location


27/223



10

1.1.2. Product Summary

1.1.2.1. Product OverviewThe Crime Data Collection, Aggregation and Assimilation System (CSCAAS) isa criminals' data assimilation system that is flexible enough for Homeland Security,TSA, Corporate America, and law enforcement from the local to international levels.This tool collects the information about the criminal from the user and aggregates andassimilates the information from various databases and resources, and presentsaccurate information to the users. This will allow organizations an efficient way to geta more holistic view of criminal's information it can act on more rapidly. The mostimportant aspect of the system is to provide faster and higher rates of case-closingthrough more efficient gathering and analysis of crime related data.

The system will have the capability to study the criminal's pattern based on the dataavailable and present the user with highly graphical reports within a click of a button.The system will also have the ability to facilitate reporting on query by date, timeand location. The system is also capable of generating alerts when new data; for thequeries already processed; is fed to the database. These alerts can be sent throughmultiple channels including email and text messages to mobile devices.

The goal of CDCAAS is to provide a convenient and robust user interface to allow theusers to enter the information pertaining to the criminal, this interface will retrievethe information from various databases i.e. Fingerprint Database, DNA, DMV andother. This system will accommodate increased information processing and sharingdemands in support of anti-terrorism. This initiative will provide new services to the

state, local and federal partners.The implementation of CDCAAS should revolutionize the security and general crimedata collection industry. The system should reduce the monetary costs, and greatlyreduce the time involved in identifying individuals for security or other purposes. Thesystem also has the potential to reduce the risks to innocent civilians by allowingfaster identification of threats or the risk to corporations of losing company secretsdue to unauthorized individuals entering sensitive areas of the company.

The CDCAAS system will be developed by extending the System CDC softwarepackages to support:

Distributed Data Access with Access Control Information Exchange Management Interactive Input System Pattern Study and Reporting

Each of these functions will be built using the following packages:

General Purpose Database Package


28/223



11

Spreadsheet Package Requirements and Configuration Management Package Secure Communication Package

Graphics Presentation Package Word Processing Package Project Management Package GPS Navigation Package Compile/Link/Runtime Packages for BASIC, C, and C++ Language Independent Debugging and Testing Package Electronic Inventory and Tracking Package

Database Package: This package will provide the user not only with the bare bonefunctionality of designing tables, but also allow advanced users to import/export datain different files and formats. Package being supported by a high end graphical

interface will allow the users to manage the database within fraction of the time astaken by present day systems. The package will be able to handle concurrent userconnections whether local or remote. This is OLE, ODBC and InnoDB compliant.

Spreadsheet Package: Provide a custom 'spreadsheet wizard' which will allow dataanalysts or other users the customize reports for information updates, identificationand alerts in a generated reports. This package must be able to handle a minimum ofone hundred concurrent user connections and must be OLE and ODBC compliant.

Requirements and Configuration Management Package: Its ability to manageinformation scheduling, and providing contact information for users such as securitypersonnel and points of contact eliminates the need of any other application to be

used in conjuncture. This must be OLE, ODBC and InnoDB compliant.Secure Communications Package: Package has been designed to allow securetransfer of data packets from the input devices to the system and betweensystems. Keeping in mind the increase in security vulnerabilities every single day, thepackage has been fitted with self updating mechanism which will keep a tab on newthreats and update itself to counter them.

Information Exchange Management Package: This package enables the user to havea single point of resource to access all information available. It acts as a bridgebetween all the databases and allows conversion of one data format to another.Thismust be OLE, ODBC and InnoDB compliant.

Graphics Presentation Package: High end graphical interface enables the user tospend less time on configuration and handling. The package is also capable ofpresenting the generated reports in different graphical formats.

Word Processing Package: Provides generic macros and custom 'word processorwizard' which will allow the user to create custom and preformatted reports based ondata and logs in the system.


29/223



12

Project Management Package: This provides project managers with the ability togenerate real time information in the form of resource estimation and usage reports.This also allows them to generate other information such as WBS (Work breakdown

Structures), CPM (Critical Path Method), PERT (Program Evaluation and ReviewTechnique) and Gantt charts, etc available and used to develop CDCAAS. This must beOLE, ODBC and InnoDB compliant

GPS Navigation Package: Enables the dependent modules to study the patternsgenerated based on fetched information and then present in various graphicalformats. This package must be OLE, ODBC and InnoDB compliant.

Compile Link and Runtime Package: Provides the necessary additional softwarelibraries to perform executable building functions from C, C++, Basic ProgrammingLanguages to Java and Flash. Also provides additional libraries for utilizing the securecommunications package to communicate over the network.

Language Independent Debugging and Testing Package: Provides wizards to performusability and functionality testing through automation scripts. This also gives SystemAdministrators the ability to debug problems on the fly in production systemsdeployed in the field.

Electronic Inventory and Tracking Package: User will be able to track hardware andany other movable equipment. The user can log issues, comments and will bepermitted to generate any number of tracking statuses to be used.

1.1.2.2 Profile of Typical Product Users

The following table lists out the categories of system users, a brief description of

each and the knowledge and skill level expected for them.Profile of Typical Product Users

SystemAdministrators

Monitor and maintain the system. An individual whoconfigures the CDCAAS system by setting system datavalidation and searching policies, assigning and revokinguser authorizations , adding and removing lawenforcement agencies , among other duties.

Data Entry Person Have the ability to enter new and update existinginformation. For example, these could be security orhuman resources personnel adding individual profiles to

the system. It is assumed that these users will have atleast an intermediate level of computer knowledge andskill.

InformationAssurance Monitor

Monitor user access and system modification logs. It isassumed that these users will have at least a basic levelof computer knowledge and skill.


30/223



13

Profile of Typical Product UsersData Analysts An individual who has restricted ability to change

existing data. An analyst enters and modifies An

analysts enters and modifies biometrics and DNA data.This role is usually performed by a role is usuallyperformed by a forensic biologist.

Law EnforcementAgency

Perform real-time search to solve the criminal case.

Table 6: Profile of Typical Product Users

1.1.2.3 Development Environment

The CDCAAS system will be developed with system XYZ notebook computer withfollowing configuration:

CDCAAS Hardware (Notebook Configuration):

Two Universal 2009-B microprocessors, 3.4 GHz 20.1 inch display A three-button mouse point device 4 GB of main memory (SDRAM) 16 MB Video RAM 320 GB primary hard drive DVD/R/RW AMD CD-RW Combo Drive A 100 MB ZIP drive Integrated 2.0 MP camera Printer port Asynchronous port Integrated 802.11 g wireless LAN Four USB ports 1394/FireWire connector A LAN interface card A 56,000 bps capable fax/modem Anti-virus/security suite Video card

CDCAAS Notebook Bundled Devices:

Speakers Head phones Laser printer 9-cell lithium ion battery MP-3 30 GB audio/video player A Bar Code scanner


31/223



14

Personal Assistant Device (416 megahertz, I GB RAM) 48-bit Color Flatbed Scanner (2400 dpi optical resolution) System ABC enhanced keyboard

A CRT monitor (1,280 x 1,024 non-interlaced; high resolution; bit-mapped; 21inch color display)

Port replicator A stand for the CRT monitor Power connector Digital camcorder Internal Speakers Wireless Digital Phone with voice mail messaging and Internet service

1.1.2.4 Priorities and Constraints

Most Important Product features: Collect the information from the user and search all the available databases

which have criminals biometric information available and retrieve theinformation to the user in a fast and efficient way.

Ability to be a centralized place for data retrieval.

Providing access to the authorized users and also providing security, dataintegrity and user authentication to the users.

Environmental Conditions and Constraints:

The system should be able to handle a high user friendly interface with

available hardware and software resources.

The system must operate in available network.

Working prototypes are required to show demos to customers on a timely basisregarding the progress of the project.

1.1.2.5. Risk Factors

In managing the areas of risk from product planning to closeout, the followingactivities are ensured by the Product Manager:

Areas of risk are identified and maintained

Factors that contribute to the potential occurrence of each risk are identified

Specific tasks for monitoring identified risk factors and for reducing thepotential occurrences of each risk are documented

Appropriate mitigation plans for each area of risk are identified

Risk items, risk status, and risk mitigation plans are documented and reviewedby product and senior management on a regular basis


32/223



15

The following risk factors are only those assumed at the time of current versiondevelopment. The list will be continually updated

Inadequate requirements (e.g., unstable, conflicting, poorly defined)

Scope creep (e.g., continuing stream of additional requirements)

Unrealistic or dynamic schedules and budgets

Shortfalls in qualified personnel (e.g., unavailable when needed, novice whenexpert needed)

Delay in the procurement of software resources critical to project success

Budget Overrun.

Shortfalls in externally performed tasks (e.g., subcontractor failure to deliver,late delivery)

Shortfalls in externally furnished components (e.g., COTS software, hardwarecomponents)

Shortfalls in performance capability (e.g., inability of databases to scale-up)

Risks for each task are documented in the monthly Program Management Reviews.The risk tables include the identified risk; a qualitative assessment of whether therisk is considered low, medium, or high based on its likelihood of occurrence andimpact on the project; mitigation activities; and, whether the risk has changed statussince it was reviewed at the previous PMR. All participants in the PMR are responsiblefor reviewing the risks in their functional areas and updating them as necessary.

1.2 Project Deliverables

1.2.1 Software Applications, Computer Software Configuration Item(CSCI)

CDCAASSoftware

Product Name Code FunctionAcquisition

Type

Applicationand

Documentationdelivery date

DatabaseManagementSystem

(CSCI-08-NO1) Stores dataindividuals andhardware

Custom 28 January2010

Spreadsheet (CSCI-08-N02) View and createspreadsheets

COTS 28 January2010


33/223



16

CDCAASSoftware

Product Name Code Function

Acquisition

Type

Applicationand

Documentation

delivery dateRequirementsandConfigurationManagement

(CSCI-08-N03) Email andappointmentmanagement

Reuse 28 January2010

SecureCommunication

(CSCI-08-N04) Facilitate secureconnection to remotenetworks


GraphicsPresentation

(CSCI-08-N05) Generate and viewgraphical reports

COTS 28 January2010

Word Processor (CSCI-08-N06) Generate and view

written reports

Reuse 28 January

2010ProjectManagement

(CSCI-08-N07) Generate and controlprogram plans

COTS 28 January2010

GPS Navigation (CSCI-08-N08) Monitor and trackhardware andindividuals

Outsourcedto IvanIndustries

28 January2010

Compiler (CSCI-08-N09) Develop CDCAAS add-ons and plug-ins

Reuse 28 January2010

Debugger andTest

(CSCI-08-N10) Debug and testCDCAAS add-ons andplug-ins


ElectronicInventory andTracking

(CSCI-08-N11) Inventory and trackhardware andindividuals


Table 7: Software Applications, Computer Software Configuration Item (CSCI)

1.2.2 Delivery Locations and Quantities

We have received advanced orders for 700 systems to be deployed to the sites listed nTable 11 below. At each site, we are required to install at least 50% of the systemsand provide training on our application packages for 50 users.


34/223



17

Delivery Locations and Quantities

Location Quantity Success Metric

Norfolk, VA 100

Install at least 50%of systems orderedand train 50 users

Jacksonville, FL 100Memphis, TN 100

Dallas, TX 50

San Diego, CA 100

Mishawaka, In 150

Boston, MA 50

Mobile, AL 50

Total 700

Table 8: Delivery Locations and Quantities

1.2.3 Documentation

Document COTS Custom Re-Use Out-SourceRequirementsSpecification

X X

Detailed DesignDocuments

X X

Documented Source Code X X XTest Plan and Test Cases X X XTest Results (includingperformance benchmarks)

X X X

Traceability Matrices X X XUser Manuals X X X XTraining Manuals(including a GettingStarted User's Guide)

X X X X

Installation Instructions X X X XMaintenance Guide X X X XVersion Description

DocumentX X X

Table 9: Delivered Documentation

1.2.4 Delivery Customer Acceptance

Applications with corresponding documentation will be developed iteratively with aseries of internal product releases, to be reviewed by the customer, all local andstate government agencies, during the next 24 months, with a full set of packages


35/223



18

available in final version for alpha testing on August 29, 2008. COTS documentationwill be provided in the form it is available from the vendor(s).

The Requirements Specification will detail how the COTS applications are expected to

work based on open source documented vendor claims and how they will beintegrated in the extension to CDCAAS. Change pages will be made for reusedocumentation only for required changes made in the following applications: CSCI-08-N03, CSCI-08-N06, and CSCI-08-N09. Outsource application and documentation forCSCI-08-N08 will be provided as available during the series of internal productreleases.

During the two-month beta test, all applications and documentation will be subject tosigned-off customer acceptance based on the set of test performance benchmarkscorresponding to the system requirements. The procedures for unmet performancebenchmarks will be detailed in the Software Project Management Plan to achievecustomer acceptance by the subsequent two month customer roll-out at theremaining customer sites.

Any unmet critical performance benchmarks after customer roll-out will be handledon a customer assigned priority basis with the appropriate expertise (with ourcompany working on custom and reuse and our company integrating COTS andoutsourced software) during the six-month maintenance period.

1.3 Evolution of the Software Project Management Plan

Date Deliverable

February 11, 2008 Stage I -Project Definition, Project Charter, Product & Project Summaries

February 18, 2008Stage 2 -Management Objectives and Priorities, Assumptions, Dependenciesand Constraints, Resource Estimate, Schedule Estimate

February 25, 2008Stage 3 -Process Model, Organizational Structure, Organizational Interfaces,Project Responsibilities

March 17, 2008Stage 4 -Technical Methods, Tools, and Techniques, Software Documentation,Project Support Functions, Staffing Plan

March 31 , 2008 Stage 5 -Monitoring and Controlling Mechanisms

April 14, 2008Stage 6 -Work Packages, Dependencies, Resource Requirements, Budget andResource Allocation, Schedule

April 21 ,2008 Stage 7 -Risk Management, Reference Materials, Definitions and Acronyms

May 5, 2008 Stage 8 -Additional Components, Index, Appendices, CDCAAS End

Table 10: Evolution of the Software Project Management Plan


36/223



19

1.4 Reference Materials

The following documents were used as references when creating this software projectmanagement plan.

"COCOMO II Model Definition Manual", Version 1.4, University of SouthernCalifornia.

"CMMI for Development, Version 1.2", CMMI-DEV, V1.2, CMU/SEI-2006-TR-008,ESC-TR-2006-008, Carnegie Mellon University Software Engineering Institute.

"Database Security Technical Implementation Guide Version 8.1 ", September192007, Defense Information Systems Agency.

"IEEE standard for software project management plans", IEEE Std 1058.1-1987,Computer Society.

"Introduction to Software Risk Management", Carnegie Mellon UniversitySoftware Engineering Institute.

John/Jane Doe Manager, "Applications Software for System XYZ and Life-CycleSystem Delivery Expectations", January 28 2008, Applications SoftwareDevelopment.

Kenneth E. Nidiffer, "SWE 625 Course Notes", January 2008, George MasonUniversity.

Richard E. Fairley, "A Guide for Preparing Software Project Management Plans",November 1986, Wang Institute Tech Report TR-86-14.

"Secure Remote Computing Security Technical Implementation Guide Version1.2", August 10 2005, Defense Information Systems Agency.

"Sharing Peripherals Across the Network Security Technical ImplementationGuide Version 1.1", July 28 2005, Defense Information Systems Agency.

"USC COCOMOII.1997 Reference Manual", 1997, University of SouthernCalifornia.

"USC COCOMO 11.1999.0 Software", [http://sunset.usc.eduJresearch/COCOMOIII], USCCSE Center for Software Engineering.

"Wireless Security Technical Implementation Guide Version 5.2' November 15

2007, Defense Information Systems Agency.

1.5 Definitions and Acronyms

1.5.1 Definitions

Alpha Test In-house testing of pre-production products and eliminate most obviousdesign defects or deficiencies, either in a laboratory setting or in some part of thedeveloping firms regular operations.


37/223



20

Baseline A specification or product that has been formally reviewed and agreedupon, that thereafter serves as the basis for further development and that can bechanged only through formal change control procedure.

Beta Test In software development, a beta test is the second phase of softwaretesting in which a sampling of the intended audience tries the product out. Betatesting is considered "pre-release testing."

Capability Maturity Model (CMM) in software engineering is a model of the maturityof the capability of certain business processes. A maturity model can be described asa structured collection of elements that describe certain aspects of maturity in anorganization, and aids in the definition and understanding of an organization'sprocesses.

Capability Maturity Model Integration (CMMI) in software engineering andorganizational development is a process improvement approach, which wants to

provide organizations with the essential elements of effective process improvement.It can be used to guide process improvement across a project, a division, or an entireorganization.

Constructive Cost Model (COCOMO) is an algorithmic Software Cost EstimationModel developed by Barry Boehm. The model uses a basic regression formula, withparameters that are derived from historical project data and current projectcharacteristics.

Configuration Management The process of identifying and defining the deliverableproduct set in a system, controlling the release and change of these items throughoutthe system life cycle, recording and reporting the status of product items and change

request. Such information typically includes the versions and updates that have beenapplied to installed software packages and the locations and network addresses ofhardware devices.

Cost Calculated from the time variable in developing an internal project bymultiplying time with the cost of the team members involved. When hiring anindependent consultant for a project, cost will typically be determined by theconsultant or firms hourly rate multiplied by an estimated time to complete.

Commercial Off-The-Shelf (COTS) software or hardware products, which are ready-made and available for sale to the general public.

Detailed Design Process of refining and expanding the preliminary design of a

system or component to the extent that the design is sufficiently complete to beimplemented. See also: software development process.

Global Positioning System (GPS) is a Global Navigation Satellite System (GNSS)developed by the United States Department of Defense. It is the only fully functionalGNSS in the world. It uses a constellation of between 24 and 32 Medium Earth Orbitsatellites that transmit precise microwave signals, which enable GPS receivers todetermine their current location, the time, and their velocity.


38/223



21

Integration Testing Testingperformed to expose faults in the interfaces and in theinteraction between integrated components.

Kernel The guts of any operating system (OS). The system loads the kernel into the

main memory which stays there while other pieces of the OS go in and out of memory.The kernel control s all request for disks, processors, or other resources.

Lifecycle - Lifecycle refers to the process used to build the deliverables produced bythe project. There are many models for a project lifecycle.

Milestone A milestone is a scheduling event that signifies the completion of a majordeliverable or a set of related deliverables. A milestone, by definition, has duration ofzero and no effort. There is no work associated with a milestone. It is a flag in thework plan to signify that some other work has completed. Usually, a milestone is usedas a project checkpoint to validate how the project is progressing. In many casesthere is a decision, such as validating that the project is ready to proceed further,

that needs to be made at a milestone.Outsource Refers to a company that contracts with another company to provideservices that might otherwise be performed by in-house employees.

Peer Review A review of a software work product, following defined procedures, bypeers of the producers of the product for the purpose of identifying defects andimprovements.

Preliminary Design Process of analyzing design alternatives and defining thearchitecture, components, interfaces, and timing and sizing estimates for a system orcomponent.

Quality Assurance A planned and systematic pattern of all actions necessary toprovide adequate confidence that an item or product conforms to establishedtechnical requirements.

Requirements A condition or capability that must be met or possessed by a systemor system component to satisfy a contract, standard, specification, or other formallyimposed documents.

Scope Scope is the way you describe the boundaries of the project. It defines whatthe project will deliver and what it will not deliver. High-level scope is set in yourproject definition (charter) and includes all of your deliverables and the boundaries ofyour project. The detailed scope is identified through your business requirements.

Security Technical Implementation Guides (STIG) A Department Of Defensesecurity guideline for configuration of COTS software and hardware.

Software Life Cycle Process - Software Life Cycle Process is amethod and standardsfor improving and mastering development processes, supporting processes andmanagement processes throughout the software lifecycle.

Spiral Model The spiral model is a software development process combiningelements of both design and prototyping-in-stages, in an effort to combine advantages


39/223



22

of top-down and bottom-up concepts. The spiral model is intended for large,expensive and complicated projects.

Stakeholder Specific people or groups who have a stake in the outcome of the

project are stakeholders. Normally stakeholders are from within the company andmay include internal clients, management, employees, administrators, etc. A projectcan also have external stakeholders, including suppliers, investors, community groups,and government organizations.

System Testing Testing conducted on a complete, integrated system to evaluate thesystem's compliance with its specified requirements.

Unit Testing a method of testing that verifies the individual units of source code areworking properly. A unit is the smallest testable part of an application.

Virtual Private Network (VPN) computer network in which some of the linksbetween nodes are carried by open connections or virtual circuits in some largernetwork (e.g., the Internet) instead of by physical wires. The link-layer protocols ofthe virtual network are said to be tunneled through the larger network when this isthe case. One common application is secure communications through the publicInternet, but a VPN need not have explicit security features, such as authentication orcontent encryption. VPNs, for example, can be used to separate the traffic ofdifferent user communities over an underlying network with strong security features.

Waterfall Model The waterfall model is a sequential development process, in whichdevelopment is seen as flowing steadily downwards (like a waterfall) through thephases of requirements analysis, design, implementation, testing (validation),integration, and maintenance.

Work Breakdown Structure A work breakdown structure or WBS is a tree structure,which permits summing of subordinate costs for tasks, materials, etc., into theirsuccessively higher level parent tasks, materials, etc. It is a fundamental toolcommonly used in project management and systems engineering.

Work Package Like a project plan in miniature, a work package is a subset of aproject that can be assigned to a specific party for execution.

1.5.2 Acronyms

Acronyms Term1M Percentage of integration redone during reuse

3GL Third-Generation Programming LanguageAAF Adaptation Adjustment FactorAAM Adaptation Adjustment MultiplierACAP Analyst CapabilityACAP Analyst Capability (COCOMO)ACM Association for Computing MachineryACT Annual Change TrafficAEXP Applications Experience (COCOMO)


40/223



23

Acronyms TermASLOC Adapted Source Lines of CodeAT Automated Translation

BPS Bits per SecondBRAK

Breakage. The amount of controlled change allowed in a softwaredevelopment before requirements are unfrozen.

C4I (Command/Control/Communications/Computer and Intelligence)CASE Computer Aided Systems EngineeringCDCAAS Crime Data Collection, Aggregation, and Assimilation SystemCDRL Contract Data Requirements ListsCD-RW Compact Disc RewritableCEO Chief Executive OfficerCIO Chief Information OfficerCM Percentage of code modified during reuse

CM Configuration ManagementCMM Capability Maturity ModelCMMI Capability Maturity Model lntegrationCOCOMO COnstructive COst MOdelConops Concept of Operations DocumentCORBA Common Object Request Broker ArchitectureCOTS Commercial Off-the-ShelfCPI Cost Performance Index (COCOMO)CPLX Product ComplexityCSCI Computer Software Configuration HemCSTB Computer Science and Telecommunications Board

DATA Data Base Size I COCOMODBMS Database Management SystemDI Degree of InfluenceDM Percentage of design modified during reuseDOCU Documentation to match lifecycle needsDRC Direct Resource CodeDSI Delivered Source InstructionsDVD Digital Versatile Video DiscDVD-R DVD non-Rewriteable format Read onlyDVD-RW DVD Rewriteable format Read and WriteEAF Effort Adjustment Factor (COCOMO)

ECP Engineering Change ProposalsECR Exploration Commitment ReviewEDS Electronic Data SystemsEIA Electronic Industry AllianceEM Engineering ManagerESLOC Equivalent Source Lines of CodeEV Earned ValueFCIL Facilities


41/223



24

Acronyms TermFCR Foundation Commitment ReviewFLEX Development Flexibility (COCOMO)

FOUL Follow-Ons Unlimited".FP Function PointsGB GigabyteGFS Government Furnished SoftwareGHz GigahertzGNU Gnu not UnixGOTS Government Off the ShelfGPS Global Positioning SystemGUl Graphical User InterfaceH/W HardwareHWCl Hardware Configuration Item

ICASE Integrated Computer Aided Software EnvironmentIDE Integrated Development EnvironmentIEEE Institute of Electrical and Electronics Engineers, Inc.INCOSE International Council on Systems EngineeringISMS Information Security Management SystemISO Information Standards OrganizationIT Information TechnologyITIL Information Technology infrastructure LibraryKASLOC Thousands of Adapted Source Lines of CodeKEDSI Thousands of Estimated Delivered Source Instructions (COCOMO)KESLOC Thousands of Equivalent Source Lines of Code

KSLOC Thousands of Source Lines of CodeLAN Local Area NetworkLEXP Programming Language Experience (COCOMO)LTEX Language and Tool Experience (COCOMO)MHz MegahertzMIS Management Information SystemMLS Multi-level secureMM Effort in Programmer-MonthsMODP Modem Programming PracticesMS Master of Science DegreeN1ST National Institute of Standards and Technology

NDI Non-Development ItemNOP New Object PointsOCR Operations Commitment ReviewODBC Open Database ConnectivityOLE Object Linking and EmbeddingOPF Open Process FrameworkOS Operating SystemPCAP Programmer Capability (COCOMO)


42/223



25

Acronyms TermPCON Personnel Continuity (COCOMO)PDA Personnel Digital Assistant

PDlF Platform DifficultyPERS Personnel CapabilityPERT Program Evaluation and Review TechniquePEXP Platform ExperiencePL Product Line

PMPerson months, the unit of effort COCOMO II uses to expresseffort.

PMAT Process Maturity (COCOMO)PMBOK Project Management Body of KnowledgePMI Program Management InstitutePMP Project Management Plan

PREC Precedentedness (COCOMO)PREX Personnel ExperiencePROD Productivity rate

PSMPractical Software and Systems Measurement (Lecture Topics, Oct20)

PVOL Platform VolatilityQA Quality AssuranceRAM Random Access MemoryRCPX Product Reliability and ComplexityRELY Required Software ReliabilityRESL Architecture / Risk Resolution (COCOMO)

RFID Radio Frequency IdentificationRFP Request for ProposalRUSE Required Reusability (COCOMO)RVOL Requirements VolatilitySADT Structured Analysis and Design TechniqueSCAMPI Standard CMMI Assessment Method for ProcessSCED Required Development Schedule (COCOMO)SDLC Software Development Life CycleSECU Classified Security ApplicationSEI Software Engineering Institute at Carnegie Mellon UniversitySITE Multi-site Development (COCOMO)

SLA Service Level AgreementSLIM Software Lifecycle Management (Larry Putnam)SLOC Source Line of CodeSME Subject Matter ExpertSNAFU Situational Normal: All Fouled Up, or similarSOA Service Oriented ArchitectureSOO Statement of Operational ObjectivesSOW Statement of Work


43/223



26

Acronyms TermSPI Software Performance Index

SPICESoftware Process Improvement and Capability Determination, the

ISO 15504 software capability assessment standardSPMP Software Project Management PlanSQA Software Quality AssuranceSTOR Main Storage ConstraintSU Percentage of reuse effort due to software understandingSwSE Software System EngineeringT&E Test And EvaluationTEAM Team Cohesion (COCOMO)TIME Execution Time ConstraintTOOL Use of Software Tools (COCOMO)TR Technical Report

TURN Computer Turnaround TimeUML Unified Modeling LanguageUNFM Programmer UnfamiliarityUSAFIESD U.S. Air Force Electronic Systems DivisionUSB Universal Serial BusUSC University of Southern CaliforniaV&V Verification and ValidationVCR Valuation Commitment ReviewVEXP Virtual Machine ExperienceVIRT Virtual Machine VolatilityVMVH Virtual Machine Volatility: Host

VMVT Virtual Machine Volatility: TargetWAN Wide Area NetworkWBS Work Breakdown StructureWITS Worldwide Identity Tracking SystemWP Work PackageWWW World Wide Web


44/223



27

2. Project Organization

2.1 Process Model

Figure 15: CDCAAS Process Model

2.1.1 Process Milestones

This section identifies milestones for all activities for managing and performing the

work specified in the products contractual requirements including tasks, reviews, anddeliverables. These milestones include base lining requirement, generating baselines,formal and informal peer review, customer review, and getting feedback fromcustomer.The following milestones are planned for the CDCAAS release:

Project Kickoff Meeting

Completion of Requirements Specification


45/223



28

Completion of Design Phase

Completion of Sub-System Test Phase

Completion of System Test Phase

Conclusion of Alpha Deployment Gate includes Customer signoff

Conclusion of Beta Deployment Gate includes Customer signoff

Completion of Deployment Phase

Activities Procedures Exit Condition

Project KickoffMeeting

Administrating and resourceallocation between projectmembers Draft of software Project

Management Plan (SPMP)

Staff assigned with officespace, computers andcommunications Management team agrees on

draft of SPMP

Systems RequirementsReview

Define requirements forcustom, COTS, reuse/NDI,and outsourced packages

Estimate resources

Management signs off onestimate and resourcebaseline and approves finalSPMP

Systems PreliminaryDesign Review

Hold series of internalpreliminary design reviews

Get user agreement onfunctional baseline

Team leaders agree on designtemplates, documentationtemplates, commonfunctionality features to bedocumented for version 1.0

RequirementSpecification

Create and analyze usecases. Analyze and definerequirements for custom,COTS, reuse/NDI, andoutsourced packages Review requirements forfeasibility and testability. Establish and documentallocation baseline Produce final SPMP

Start developing test plan

Review closed andrequirement is base lined Customer agrees and signsoff baseline requirements. Management providesnecessary resources.

Preliminary DesignReview

Complete preliminarydesign for COTS, Custom andreuse packages. Conduct series ofpreliminary design reviews Get user agreement onfunctional baseline

Baseline PDD (PreliminaryDesign Document) Close PDD review Baseline Functionalspecification User agreement formallysigned and archived


46/223



29


Critical Design

Design detailed system

features including userinterface, data structure, andcommunication methodbetween modules. Conduct review on CriticalDesign artifact. Establish baselines forCritical Design Document. Ger user agreement onCritical Design baseline

Critical design document iscreated. Close Detail Design review User agreement formallysigned and archived

Coding and unit test

Coding and document

custom ,COTS and reusepackages Test COTS, custom, andreuse code, including maturereuse prototype

Software is developed and

source controlled Results of tests documentedand signed off by projectmanagement

Sub system test

Test outsourced packageand test all sub-systemfunctionality Validate components andsub-system functionality.

Results of tests documentedand signed off by projectmanagement User agreement formallysigned and archived

System test

Test full functionality basedon user work flow for all 11packages Fix bugs found duringintegration testing andfinalize baselines.

Results of tests documented

and signed off by projectmanagement User manual andmaintenance manualdocumented Product baseline established User agreement formallysigned and archived

Deployment andSupport

Alpha and beta testcompleted Start help desk operation

Deploy system at user sites Begin user training Begin softwaremaintenance activities

Customers sign off ondeployment System deployed at user

sites Scheduled for user training Help desk and maintenanceoperational


47/223



30


Phase out

Document best practices,

lessons learned, and futuremarketing opportunities Discontinue automaticlicense upgrades Close out supportingcontracts

Documentation submitted to

management and to corporateknowledge database. Close-out licensing andcontract information sent toFinance Office ContractingOffice, and managementpersonnel and acknowledged

Figure 9: Activities, Benchmarks and Success Indicators

2.1.2 Baselines

The essential idea of baselines is that in order to reach a destination it is necessary toknow your starting point. In CDCAAS project the following three baselines will be usedfor each component during its waterfall development lifecycle.

Functional Baseline: Describes a systems or items functional characteristics, and theverifications required to demonstrate the achievement of those specified functionalcharacteristics.

Allocated Baseline: Describes the functional and interface characteristics for CI(Configuration Item) that are allocated from those of the higher level CI and theverification required to demonstrate achievement of those specified characteristics.

Product Baseline: Defines the releasable contents of the project including the

application, test case, test results, system and user documentation during theproduction, fielding/deployment and operational support phases of its life cycle.

2.1.3 Reviews

Various internal reviews and customer reviews will be conducted as scheduled insection 5.5 and review comments and sign off will be documented for each review.Also additional review may be conducted if necessary or based on customer request toidentify possible problem in early stage. Those reviews will be Software RequirementSpecification Review, Preliminary Design Review, Critical Design Review, Various TestReadiness Review, and Deployment Readiness Review. Other activities also requiredcustomer review and sign off will be required before it is executed.

2.1.3.1 Software Requirements Review

A Requirements Review is one of a number of such reviews to verify and approve setsof system-level requirements as they are developed. The main purpose of this reviewis to ensure that the design is progressing in the correct to give the team a confidencein the design process through the progressive monitoring and approval of the system-


48/223



31

level requirements that are developed between the User Requirements Document andthe Functional Baseline.

A Requirements Review will be conducted as a formal review and end of the review

customer will sign off and approved the baseline Requirements. Re-review will beconducted if necessary.

2.1.3.2 Preliminary Design Review

Preliminary Design Reviews will be held at the conclusion of Preliminary Design in thesystems engineering process to evaluate the Preliminary Design effort and to reviewand approve the Allocated Baseline containing the Development Specifications. Asingle sy