+ All Categories
Home > Documents > I n t e g r i t y - S e r v i c e - E x c e l l e n c e UML to OPNET SW Performance Modeling...

I n t e g r i t y - S e r v i c e - E x c e l l e n c e UML to OPNET SW Performance Modeling...

Date post: 13-Jan-2016
Category:
Upload: donna-simon
View: 215 times
Download: 1 times
Share this document with a friend
12
I n t e g r i t y - S e r v i c e - E x c e l l e n c e UML to OPNET SW Performance Modeling November 6, 2008 John James (E547) Greg Quinn (E547) Ed Walters (E546) ©2009 The MITRE Corporation. All rights reserved Approved for Public Release; Distribution Unlimited - 09-0001. This technical data was produced for the U. S. Government under Contract No. FA8721-09-C-0002, and is subject to the Rights in Technical Data-Noncommercial Items clause at (DFARS) 252.227-7013 (NOV 1995)
Transcript
Page 1: I n t e g r i t y - S e r v i c e - E x c e l l e n c e UML to OPNET SW Performance Modeling November 6, 2008 John James (E547) Greg Quinn (E547) Ed Walters.

I n t e g r i t y - S e r v i c e - E x c e l l e n c e

UML to OPNETSW Performance

ModelingNovember 6, 2008John James (E547)Greg Quinn (E547)Ed Walters (E546)

©2009 The MITRE Corporation.  All rights reservedApproved for Public Release; Distribution Unlimited - 09-0001.

This technical data was produced for the U. S. Governmentunder Contract No. FA8721-09-C-0002, and issubject to the Rights in Technical Data-NoncommercialItems clause at(DFARS) 252.227-7013 (NOV 1995)

Page 2: I n t e g r i t y - S e r v i c e - E x c e l l e n c e UML to OPNET SW Performance Modeling November 6, 2008 John James (E547) Greg Quinn (E547) Ed Walters.

I n t e g r i t y - S e r v i c e - E x c e l l e n c e

Objective

• Primary objective: Reduce the cost of modeling SW performance (specifically in OPNET)– Hand created Software Performance Models

• Effort intensive• Schedule intensive

– Improve correlation of model to design– Improve quality of model

Page 3: I n t e g r i t y - S e r v i c e - E x c e l l e n c e UML to OPNET SW Performance Modeling November 6, 2008 John James (E547) Greg Quinn (E547) Ed Walters.

I n t e g r i t y - S e r v i c e - E x c e l l e n c e

Methodology

• Directly interface between UML design tools and SW performance analysis tools

• Utilize contractor UML sequence diagrams augmented with Schedulability, Performance and Time (SPT) data

• Create OPNET Model using two MITRE Java routines – Translate Rhapsody XMI into Software Performance Model Interchange

Format (S-PMIF by Connie Smith)• Common XML representation to exchange models between UML-based tools and

Performance engineering tools– Convert S-PMIF into an XML model that is imported into OPNET to use

Detailed Server Model to model SW

UML – Unified Modeling LanguageSPT- Schedulability, Performance and TimeXMI – XML Metadata Interchange

Industry Standards

Runtime - Process

S-PMIF – Software Performance Model Interchange FormatPossible Standard

UML – Sequence Diagrams

Response Time Statistics

Page 4: I n t e g r i t y - S e r v i c e - E x c e l l e n c e UML to OPNET SW Performance Modeling November 6, 2008 John James (E547) Greg Quinn (E547) Ed Walters.

I n t e g r i t y - S e r v i c e - E x c e l l e n c e

Potential Program Impact

• Reduction of effort to analyze design performance– Given UML model w SPT: reduced effort and schedule

• From Months to Day(s) - initial model• From Weeks to Day - updates

• More accurate model of performance– Confidence in correlation of analysis to UML architecture– No hand changes in model for new steps in SW threads– Better use of performance tool

• Given less cost/schedule required to do performance analysis contractor more likely to do the analysis– More likely to meet performance requirements earlier in

development phase - less costly point to do this work– Reduce cost of changes to design to meet performance

requirements– Resulting in higher compliance with requirements

Page 5: I n t e g r i t y - S e r v i c e - E x c e l l e n c e UML to OPNET SW Performance Modeling November 6, 2008 John James (E547) Greg Quinn (E547) Ed Walters.

I n t e g r i t y - S e r v i c e - E x c e l l e n c e

Example Problem(Numbers are Notional)

{8 Hz, 60 ms} {120 ms}

Sensor_BAC SP_BAC Radio

Sensor_ABM

{10 ms}

Munition

SP_ABM

{80 ms for tracking,10 Hz IFTU update}

Tracker_ABM

{6 Hz, 60 ms} {120 ms}

{125 ms point topoint}

IFTU

Detections

IFTUI_Q_Data

Detections

Detections

I_Q_Data

@260ms 30ms 60ms

60ms@310ms 30ms 40ms Detection

5ms

40ms

@90ms 20msIFTU update

25ms IFTU

IFTU In-flight Target Update

Priority 7

Priority 8 Priority 9

Page 6: I n t e g r i t y - S e r v i c e - E x c e l l e n c e UML to OPNET SW Performance Modeling November 6, 2008 John James (E547) Greg Quinn (E547) Ed Walters.

I n t e g r i t y - S e r v i c e - E x c e l l e n c e

Two Sensor & One Munition Thread

ABM Sensor Scenario

BAC Sensor Scenario

IFTU Scenario

Augmented with SPT Data (not shown)

Page 7: I n t e g r i t y - S e r v i c e - E x c e l l e n c e UML to OPNET SW Performance Modeling November 6, 2008 John James (E547) Greg Quinn (E547) Ed Walters.

I n t e g r i t y - S e r v i c e - E x c e l l e n c e

OPNET Layout

Page 8: I n t e g r i t y - S e r v i c e - E x c e l l e n c e UML to OPNET SW Performance Modeling November 6, 2008 John James (E547) Greg Quinn (E547) Ed Walters.

I n t e g r i t y - S e r v i c e - E x c e l l e n c e

Utilization by Resource

OPNET 3 day

RapidRMA

PN (30 sec run)

R2 0.0507

R8 - 0.0983R6 - 0.1173

R12 - 0.1964

R10 - 0.2341

R4 - 0.3580

R14 - 0.4185

Page 9: I n t e g r i t y - S e r v i c e - E x c e l l e n c e UML to OPNET SW Performance Modeling November 6, 2008 John James (E547) Greg Quinn (E547) Ed Walters.

I n t e g r i t y - S e r v i c e - E x c e l l e n c e

Thread Response Time

PN Results (6 Min run)OPNET: After 3 day run

BAC

ABM

IFTU

RapidRMA

Page 10: I n t e g r i t y - S e r v i c e - E x c e l l e n c e UML to OPNET SW Performance Modeling November 6, 2008 John James (E547) Greg Quinn (E547) Ed Walters.

I n t e g r i t y - S e r v i c e - E x c e l l e n c e

Modeling SW in OPNET

• Used Modeler and Detailed Server Model– Custom Application Model

• Model thread behavior in Tasks • Steps on same resource are SW

– Detail Server Model • Timing and priority on server jobs in Task (Thread)

• Considered using ACE Whiteboard Custom Application– Easier to do by hand: attach Jobs to Tiers– Harder to automate; C API; No XML interface– Additional License Required

Page 11: I n t e g r i t y - S e r v i c e - E x c e l l e n c e UML to OPNET SW Performance Modeling November 6, 2008 John James (E547) Greg Quinn (E547) Ed Walters.

I n t e g r i t y - S e r v i c e - E x c e l l e n c e

More Complex SW Example

Page 12: I n t e g r i t y - S e r v i c e - E x c e l l e n c e UML to OPNET SW Performance Modeling November 6, 2008 John James (E547) Greg Quinn (E547) Ed Walters.

I n t e g r i t y - S e r v i c e - E x c e l l e n c e

Other Issues and Next Steps

• Have implemented Fork of given thread into two asynchronous threads

• Are looking to modify Detailed Server model to handle two-thread-Join and sw-Locks

• Analyze specific military system’s design threads by moving into an environment that supports use of Contractor performance parameters

• Other programs interested in technology when ready– Requires synchronization between threads

• Joins and Locks


Recommended