Download - The Software Estimation Approach of the JSF Autonomic ... · Joint Strike Fighter Track 2 April 29, 2003 Juan M. Gomez C. Patrice Roseland Lockheed Martin Information Systems Orlando,

Joint Strike Fighter Track 2April 29, 2003

Juan M. GomezC. Patrice Roseland

Lockheed Martin Information SystemsOrlando, FL

The Software Estimation Approach of the JSF Autonomic Logistics Information System

‘Joint Strike Fighter,’ ‘JSF,’ and the JSF Logo are Trademarks of the United States Government

Cleared for public release under provisions of PIRA AER200303010


Presentation

The Autonomic Logistics Information System (ALIS)

Software Development Challenges

Software Estimation Approach

Managing to the Estimation

Conclusion


...consists of the system, application, and network infrastructures required to provide global integrated and autonomic support for the operations, maintenance, supply and training support of the Joint Strike Fighter.

Autonomic Logistics Information System(ALIS)

...The capability of a system to demonstrate behavior predicated oninternal & external stimuli without human intervention


AUTONOMIC LOGISTICS SYSTEMTECHNICAL SOLUTION

Integrated JSF AL System - Affordable, Supportable, Survivable, & Lethal

Integrated JSF AL System - Affordable, Supportable, Survivable, & Lethal

TECHNOLOGICALLY-ENABLED

MAINTAINER

INTELLIGENT AIR VEHICLE• Prognostics & Health Management• Design for Supportability• High Reliability & Maintainability

INTEGRATED SUPPORT • Design Data → Direct to →

Support Information• Failure Prediction →

Remove Unit Before Failure

Joint Aircrew & Maintainer Training

INTEGRATED TRAINING• Common, Joint Pilot/Maintainer

Training• Modular, Flexible Training • Embedded Training

FLIGHT OPERATIONS• Integration for Optimal

Mission Performance• High Sortie Generation Rate• Low Logistics FootprintAUTONOMIC

LOGISTICSINFORMATION

SYSTEM


ALIS Provides a Single Integrated AL Information Environment

Training Services

Support Services

Off Board

Mission Support

Design Attributes• Provides Decision Support

• Enables Autonomic Processes


Training Services

Training Services

Support Services

Support Services

Off Board Mission Support

Off Board Mission Support

ALIS Provides a Single Integrated AL Information Environment


Where Does ALIS Fit into the JSF Lifecycle?

F-16CF-22

JSF-AF

F/A-18E/FAV-8B JSF-N

JSF-M C Potential Budget Range

Historical AvgTACAIR Share of Funding(per CBO Study)

CBO High-End Unit Cost Estimates* -F/A-18E/F, F -22, JSF

TACAIR Procurement Funding Requirements

Data Sources: DoD budget reports, LMTAS estimates using DoD

budgetdata derived cost factors

* CBO Testimony on Modernizing Tactical Aircraft,

Airland Subcommittee, SASC,10 March 1999

Billionsof

FY99$

2000 2002 2004 2006 2008 2010 2012 2014 2016 2018 2020

0

0

2

4

6

8

10

12

14

16

18

System Performance Assessment/Modeling & Simulation

Design

Manufacture

Operate

Supply, Support , Maintain, Train

Provide Situational Awareness IT

Provide Situational Awareness IT

Provide Prognostic Health IT

Provide Prognostic Health IT

Provide Integrated Management Framework

Provide Integrated Management Framework

Provide Distributed Product Design & Development Environment

Provide Distributed Product Design & Development Environment

Provide Configuration Control/Manufacturing Provisions

Provide Configuration Control/Manufacturing Provisions

Provide Training

Provide Training

Provide Integrated Support of Product

Provide Integrated Support of Product

Aircraft Performance Assessment/Test & Evaluation

Program Performance Assessment

Autonomic Logistics Performance Assessment

Aircraft Performance (Lines of Code within Airframe)


Presentation





Conclusion


Architecture and Software Drivers


The ALIS operating domains are integrated through shared data and processes that autonomically react to JSF status changes and events.

… selected to ensure optimal JSF, reliability, maintainability, availability and safety for the Warfighter.

• Support JSF Operations with air vehicle status and configuration.

• Support Mission Planning with air vehicle status and installation of theater data.

• Provide Maintenance Planning and Work Order Management.

• Provide Total Asset Visibility by integrating Supply Chain management.

• Provide current and accurate technical data to the JSF maintainer.

• Integrate Training with online help functions.

• Support Sustaining Engineering with performance and maintenance history.

• Provide Administration of ALIS assets.

System Architecture- ALIS Operating Domains


Technical View – “Standards”


Presentation LayerPresentation Layer(Win32, JTD & ALIS Browsers, Internet Devices)(Win32, JTD & ALIS Browsers, Internet Devices)

Off-Board

Components

Admin

ComponentsCRM

Components

COTS Application Foundation COTS Application Foundation

Application Server

J2EE, CORBA, WebServices,

DCOM

XML/HTTPHTML/HTTP

ORB/MOMORB/MOMSecurity

Components

IIOP/JMS

Java 2 Enterprise Edition Server (Weblogic)

Web Server Web Server Apache

BEA Weblogic

Java Server Pages

HTML/DHTML/XHTML

DCOM/.NETDCOM/.NET

InternetInternetApplicationsApplications

EnterpriseEnterpriseApplicationsApplications

Database LayerDatabase Layer

Customer Relations

Management

Supply Chain Management

System Administration

Maintenance Management

Operations Support

Off-Board Analysis

ALIS Reference Architecture


???

COTSProducts COTS-Based

System

???

COTS Vendors

• Frequent, continual change of COTS products and marketplace

• COTS products driven by marketplace, not your system context

• Varying architectural paradigms across components

• Dependencies between components

• Limited visibility into COTS code and behavior

• Limited control of frequency or content of COTS releases

• New “business” issues (licensing, data rights, warranties)

What Makes Using COTS Challenging?


Marketplace Architecture/Design

• COTS technology and products• NDI• Standards

• requirements• cost• schedule• business processes,

etc.

System Context

Traditional Development Approach Required COTS Approach

Requirements

Design

Code

simultaneous definition and

trade-offs

• Influenced by products• Essential elements of the system

Essential Paradigm Shift


A New Look at System Development and Evolution

Qualify Adapt Assemble Update COTS Market

E V O L U T I O N

Select products

are qualified to be “fit

for use” as components.

Qualified products are

adapted to be components that can be inte-

grated.

Adapted compo-

nents are assembled

by using architecture,

infrastructure, or middleware.

Upgrades to the system occur as needed and are facilitated by preceding steps.

The market supplies

products.


COTS Reuse and Developed Components LOCs

Create Inventory Part Characteristic

Create Purchase Part Supplier

Create Standard Name

Modify Part Catalog

Modify Inventory Part Planning

Create Part Catalog Alternative

Modify Inventory Part

Create Sales Part Characteristics

Create Sales Part

Create Part Catalog Manufacturer

Create Engineering Part Master

Create Part

New Part Definition

Mo

dified

Bu

siness P

rocess

(Develo

ped

Co

de)

COTS Foundation

COTS LOC Estimate: 19,600

Presen

tation

Layer

(Develo

ped

Co

de)

Developed Code Estimate: 1,020

LOCs – Java and 450 LOCs of XML

Presentation Layer Estimate: 1,600 Lines of

XML


Presentation





Conclusion



• A partial bottoms up model– Analysis

• Use Cases• Requirements

– Sizing• Architecture Allocation• Sizing Metrics

– Costing• Effort • Parametrics


Source Data Research

ALIS

COTS Vendors

Company IRAD

Contract Requirements

Books & Articles

Legacy Systems

-Intelligent Agents- Autonomic Engines

NALCOMISUSN

USAFCAMSCEMSGO81IMDSSBSS


Use Case Modeling

OperationsSupport

MaintenanceManagement

CustomerSupport

AdministrationSecurity

Supply ChainManagement

TrainingPresentation

Off BoardAnalysis

Command &Control

Pilot

Maintainer

Air VehicleAnalysis

ExternalMaintenance

Systems

SquadronCommander

External Supply Support

MilitaryCarrier

Transportation

SustainingEngineering


3 System Requirements3.1 System Description3.2 System Performance Requirements3.2.1 System Level Characteristics3.2.2 Graceful Degradation3.2.3 Critical Timelines3.2.4 Scalability3.3 System Functional Requirements3.3.1 Operations Support Requirements3.3.1.1 Process Flight Requests3.3.1.2 Process Flight Logistics3.3.1.3 Status Flight Progress3.3.1.4 Capture Debrief Data3.3.1.5 Asset Visibility and Control3.3.2 Maintenance Management Requirements3.3.2.1 Maintenance Work Order Planning3.3.2.2 Support to Maintenance Planner and Maintainer3.3.2.3 Maintenance Work Order Execution3.3.2.4 Maintenance Activity Visibility and Reporting3.3.2.5 Support Maintenance Deployment3.3.2.6 Other Maintenance Support

Proposal Requirements Specification from Use Case Diagram Analyses

Top Level Use Case

Lower Level Use Case


Sizing

Develop Use Cases

Function Point Analysis

Architecture Allocation

Develop Requirements

Source Data

Model Size Metrics

International Function Point Users Group (IFPUG) Function Point Counting Practices Manual

LMIS Systems Engineering Standards

LMIS Software Engineering Standards

StandardsFollowed:

Tools Used:

Rational Rose

MS WordDOORS

MS Excel Rational Rose


What is Function Point Analysis?

•Developed by IBM in mid-70’s to provide metrics independent of the amount of code in the software application

•Function Point Analysis (FPA)“Measures the size of any software deliverable in logical, user-oriented terms. Function point analysis does not concern itself directly with technology platforms, development tools, or generated lines of code. It simply measures the functionality being delivered to the end user.” ~David Garmus and David Herron

• External Inputs (EI)• External Outputs (EO)• External Inquiries (EQ)• Internal Logical Files (ILF)• External Interface Files (EIF)

FPA counts “what” functionality is required from a system to assist a user in doing their job….not “how” the function will be implemented.


Business Area: Maintenance Management Section: 3.3.1 Req. ID

Description Multiplier ILF EIF EI EO EQ Notes

MM001 Rule based configuration data

1 X

MM002 Work Request processing logs

1 X

MM002 Receiving Work Requests 1 X MM002 Work Request Cancellations 1 X MM003 User cancellation

Notifications 1

X

MM004 Operations Work Request 1 X X MM005 Work Order reports 5 X 5 different

reports MM006 Maintenance location data 1 X MM007 Work Request status 1 X MM007 Work Order status 1 X MM007 Work Order task status 1 X

Function Point Data Collection

Requirements IdentifierUsed in DOORs

Text from requirementUsed to identify FP component

Function Point Component TypeWhen more than 1 entityexpected


Architecture Definition

SYSTEM

....

CSCI CSCI CSCI CSCI CSCI

CSC CSC CSC

CSU CSU CSU

SYSTEM

....

CSCI CSCI CSCI CSCI CSCI

CSC CSC CSC

CSU CSU CSU

COTS

COTS

.... ....

.... ....


C. Patrice RoselandJuan M. Gomez -26

Autonomics

KitManager

SBSS Support

Supply W/OProcessor

InventoryManager

OEM Interfaces

Supply ChainModeling &

Optimization

Transportation

SC Browser

Schedule &Planning

Asset Manager

Notification

Supply ChainManagement

Maintenance

DOCUMENT/RECORDSMANAGEMENT

DECISIONSUPPORT

TRAININGPRESENTATION

SECURITYMANAGEMENT

SYSTEMSAFETY

BUSINESSRULES

Logical S/W Architecture

Foundation

CommonSupportApplications

CSCIs

COTS FOUNDATION

JSF Systems

DoDSystems

Services’Systems

Supplier Systems

EXTERNALINTERFACES

Technical Data Configuration

Asset Mgmt

ScheduleProcessor

Resource Management

Schedule Browser

CustomerReqts Mgmt

OperationsSupport

PHM Monitor

MaintenanceDebriefer

PHM Manager

Work OrderProcessor

Maintenance Autonomics

Maintenance Browser

Maintenance Manager Config

Work Request Generator

Planning and Scheduling Tool

Preventative Maintenance

ReportGenerator

AssetManager

Statistical & Trending Anal

Notification

Customer Support

Work OrderProcessor

ConfigurationManager

Trending Model,Analysis & Forecasting

Notification

SoftwareDistribution

Report Generator

Autonomics

Browser

Tools foragencies

Distribution

ComponentPerformance

A/V Support

StatusManager

MaturationSupport

Analysis

SupportTools

EngineDiagnostics

Inspector

ReportGenerator

Asset Manager

Notification

Intelligent HelpDesk

Data Mining

Administration

Std DesktopInterface

Data Mgmt& Admin

System Operation

ProblemReporting

Configuration Management

Failover

SecurityAdmin

SecurityAdmin

DeploymentTool

ApplicationConfig Tool

Tech Data

APPLICATION

MODULES



CORECOTS

Foundation

New

Ap

plic

atio

ns

Decision Support

Autonomics

Glu

e Co

deB

row

sersN

etwo

rk Interfaces

ALIS Software Architecture Makeup

I BM

Palm Devices

Laptops

Workstations

Main Frames

Servers


Architecture AllocationCSCI Name: Maintenance Management Req ID System Component

Description Type Complex MWP

CSC MMD CSC

Browser CSC

Autonomic CSC

COTS Reference

MM001 Rule based config Data

ILF A 1 1 1 X Reuse of autonomic engine

MM002 Work Request Processing logs

ILF L 1 1 X COTS Tool implements work orders

MM002 Receiving Work Requests

EI A 1 X COTS Tool implements work orders

MM002 Work Request Cancellations

EI L 1

MM003 User cancellation Notifications

EO L 1 1

MM004 Operations Work Request

EIF A 1 X COTS Tool implements work orders

MM005 Work Order Report1 EO A 1 1 X COTS Tool implements work orders





Requirements Identifier

Requirements Text

FP Component

Complexity

Allocation


SLOC versus Function Point

• SLOC estimates are performed by counting all source instructions, excluding comments and blanks.• Accurate when code is available; ie: development based on an old design.• Difficult to estimate early in development phase for new functionality, prior to

having written code.• Results are relative; based on the language used to code the software.

• Function points are indicators of size based on the 'logical' view of a piece of software• More complex than SLOC. Project requirements are examined for the number

and complexity of inputs, outputs, calculations and databases required. Values (points) are assigned and then summed to produce a function point rating for the project.

• Are NOT directly translatable to work effort• Can be low, average, or high complexity.


Development Analysis

• SEER-SEM modeling by Galorath, Inc.• Entering Size metrics

– New Development Software– Pre-existing software, not designed for Reuse

• Re-design, re-implementation, or retest required

– Pre-existing software, designed for Reuse• Re-design, re-implementation, or retest required

– COTS Tool Integration


SEER-SEM Model View


Applying Parametrics

• Knowledge BasesPre-defined set of input parameters which can be used to either define the parameters

in a newly created WBS element or modify the parameters in an existing WBS element.


Release Estimation

Software size allocated for each CSCI, CSC, CSU and COTS element to

releasesRelease modelsbuilt, size validated,effort hours defined for each release


Presentation





Conclusion


Estimation Support for Release Development

Size and Effort

Staffing

Schedule


Estimation in the Release Cycle

• Phase 1: Initial Rough Order of Magnitude (ROM) based of release requirements flow down and capabilities desired

• Phase 2: Update after release system requirements are baselined

• Phase 3: Update after architecture completion and software requirements baselined

• Phase 4: Deployment – gather actuals and use to calibrate the model. Use calibration factors for following releases.


Presentation





Conclusion


Conclusion

• ALIS is a complex system of systems providing estimating challenges to determine effort

• A partial bottoms up estimation approach allowed for a better understanding of the effort required

• Estimation modeling used during the release cycle will identify software growth and increase cost against proposal model.


Bibliography

Counting Use Cases with Function Points, Quality Plus Technoligies, Inc., 2002 Function Point Counting Practices Manual, Release 4.1, International Function Point Users Group (IFPUG), January 1999. Garmus, David & Herron, David, Function Point Analysis – Measurement Practices for Successful Software Projects, Addison Wesley, New York, NY, 2001. Jones, Jacqueline, FP-221 Estimating Project Size Early in the Life Cycle, International Function Point Users Group (IFPUG), September 30, 2001 SEER-SEM User’s Manual, Version 6.0, Galorath Incorporated, March 2001.


AcronymsA/V – Air Vehicle AL – Autonomic Logistics ALIS – Autonomic Logistics Information System ATO – Air Tasking Order C4ISR – Command, Control, Communication, Computers, Intelligence, Surveillance, and Reconnaissance CAMS – Core Automated Maintenance System (USAF) CEMS – Comprehensive Engine Management System (USAF) CORBA – Common Object Request Broker Architecture COTS – Commercial Off the Shelf CRM – Customer Resource Management CSC – Computer Software Component CSCI – Computer Software Configuration Item CSU – Computer Software Unit DCOM – Distributed Common Object Model DHTML – Dynamic Hypertext Markup Language DII COE – Defense Information Infrastructure and Common Operating Environment DoD – Department of Defense DOORS – Requirements Management tool by Telelogic, Inc. EI – External Input EIF – External Interface File EO – External Output EQ – External Inquiry FP – Function Point FPA – Function Point Analysis G081 – USAF Cargo Engine Maintenance System GTN – Global Transportation Network HTML – Hyper Text Markup Language IFPUG –International Function Point Users Group IFS – Industrial and Financial Systems IIOP – Internet Interoperability Protocol ILF – Internal Logical File IMDS – Integrated Maintenance Data System (USAF) J2EE – Java 2 Enterprise Edition JCS – Joint Contract Specification

JMS – Java Messaging Service JSF – Joint Strike Fighter JTD – Joint Technical Data LMIS – Lockheed Martin Information Systems LOC – Line of code MM – Maintenance Management MMD – Maintenance Management Debrief CSC MoD – Ministry of Defence (UK) MOM – Message Oriented Middleware MWP – Maintenance Work Order CSC NALCOMIS – Naval Air Logistics Command Maintenance Information System (USN) NDI – Non- development items ORB – Object Request Broker PDM – Product Data Manager PHM – Prognostics Health Management SBSS – Standard Base Supply System (USAF) SC – Supply Chain SCM – Supply Chain Management SEER-SEM – Software Estimation, Planning and Project Control Tool by Galorath, Inc. SLOC – Source Lines of Code USAF – United States Air Force USN – United States Navy VPN – Virtual Private Network XHTML – Extensible Hypertext Markup Language XML – Extensible Markup Language W/O – Work Order