Transcript Tony Jordano - Center for Software Engineering

SAIC
COTS-Based Systems (CBS)
and
Lifecycle Models (LCM)
Tony Jordano
Corporate Vice President
for System and Software Engineering
2/7/01
01/25/01
1 of 7
Agenda
• About SAIC
• Corporate Guidance for LCMs
• COTS-Based Systems and LCMs
• Concluding Thoughts
01/25/01
2 of 7
About SAIC
•
•
•
•
•
Science Applications International Corporation (SAIC)
$5.5B Revenue - Half Government, Half Commercial
40,000 Employees
Largest Employee-Owned Hi-Tech Company
Business Sectors:
–
–
–
–
–
–
–
–
–
Criminal Justice
Energy - Oil & Gas & Utilities
Environment
Financial Services
Healthcare
National Security
Space
Telecommunications (including Telcordia Technologies)
Transportation & Logistics
01/25/01
3 of 7
Corporate Guidance on Lifecycles
• Established Corporate-Wide Working Group in 2/99
• Analyzed Wide Variety of Material and Experiences
• Identification, Definition and Selection Criteria for:
–
–
–
–
–
–
–
–
–
Waterfall
Incremental
Evolutionary
Spiral
COTS Integration
Automated Application Generation
Rehost/Port
Re-engineer
Maintenance
• Distributed in July 1999
NOTE: Consistent with IEEE/EIA 12207.2-1997
01/25/01
4 of 7
CBS and Spiral (1 of 2)
• CBS - Typically For Commercial Clients
– Very Common, Discussed As COTS Driven and RAD
– 40+ COTS Products in Some Systems (20+ Common)
– 6 Week to 6 Month Release Cycles Required
– Time to Market and COTS Products Drive All Tradeoffs and Risk
Considerations (Requirements Traded or Reprioritized)
– Invarients 1-3 Apply, but Driven by COTS & Release Dates
– Invarients 4-6 Have Less Application
– Really COTS Driven LCM With Spiral Overtones
01/25/01
5 of 7
CBS and Spiral (2 of 2)
• Spiral - Typically For Government Clients
– Some Understanding of Spiral Exists
– Broad Tradeoffs of Architecture, Performance, etc.
» Requirements More Important Than In CBS
– 3 to 10 COTS Products in Deliverable Systems
– All 6 Invarients Apply Broadly
– Attempts with Fixed Price Contracts Reduced to Waterfall
– Both Government PMO and Contractor need Domain
Experience and Process Maturity
– Really Spiral with Some COTS to Reduce Schedule & Cost
01/25/01
6 of 7
Concluding Thoughts
• The 2 LCMs Could be Driven Closer Together
– If Commercial Client Really Understands Spiral
– If Government Client Really Wants COTS Driven
• First Spiral Cycles
– COTS Survey, Initial Selection, and Function/Performance List
– Obtain Selected COTS for Testing, Measurement, Trial
Integrations, Determine Scalability, Interoperability, etc.
» Define and Estimate Glue Code
– COTS Selection, Function/Performance List, With Degree of
Maturity, Scalability, Interoperability Considered
» Then finalize Architecture and Release Schedule & Content
» Plan Releases Based on Anticipated COTS Releases
01/25/01
7 of 7