• Aucun résultat trouvé

Cost and Risk Considerations for Testing Unmanned and Autonomous Systems of Systems

N/A
N/A
Protected

Academic year: 2021

Partager "Cost and Risk Considerations for Testing Unmanned and Autonomous Systems of Systems"

Copied!
1
0
0

Texte intégral

(1)

Indira Deonandan

1

and Dr. Ricardo Valerdi

2

, Department of Aeronautics and Astronautics

1

and Engineering Systems Division

2

Current Work

Future

Work

Introduction

Massachusetts Institute of Technology, Cambridge, MA, 02139

Indira@mit.edu

Current Work

Future

Work

Introduction

Unmanned and Autonomous Systems of Systems (UASoS) have become increasingly complex and bring interesting

Literature

review

Studies

Case

Interviews

Surveys

acquisition to minimize risk by continue knowledge

have become increasingly complex and bring interesting challenges to testing and evaluation. Currently no traditional testing techniques or programs of record exist.

review

Studies

Surveys

acquisition to minimize risk by

developing PATFrame as a decision support system for testing and evaluating UASOS

SPHERES

Case

Study

To ensure UASoS are effective, safe, suitable

and survivable the

The Synchronized Position Hold Engage

Reorient Experimental Satellites testbed

testing and evaluating UASOS

Case

Study

and survivable the

Prescriptive and Adaptive Testing Framework for

Reorient Experimental Satellites testbed

serves a dual role as both a risk mitigation unit

and distributed satellite system of systems Figure 5: Preliminary

mockups for tools

Problem Focus

Testing Framework for UASoS is being created.

Figure 1: PATFrame Approach Principles of

Risk Mitigation

 Modularity

 Requirements Balance

mockups for tools

use both

qualitative data

Problem Focus

Figure 2: PATFrame Focus and Contributions

Figure 3: SPHERES at International Space Station

Risk Mitigation

 Enabling field of study  Iterative Research

 Incremental Technology Maturation

 Optimized utilization of Resources develop the inputs for a tool to be

qualitative data from subject

matter experts and quantitative data

Figure 2: PATFrame Focus and Contributions International Space Station

 Optimized utilization of Resources develop the inputs for a tool to be used by test planners and testers to determine the effort required for testing

quantitative data from test projects to validate inputs and ultimate stop

PATFrame covers

include parameters that will calculate the probability of accomplishing a task in given resources and test cost driver

and ultimate stop point for testing

PATFrame covers five domains – space, air, land, sea and undersea

R

is

k

in given resources and test cost driver inputs

Number of interfaces, requirements and systems Integration complexity

Time Constraints Personnel experience

and capability

Problem Statement

Degree of autonomy of systems

Acknowledgements

Hierarchy of initial

Interoperability of manned and unmanned systems and capability Multisite coordination, particularly geographic locations

Problem Statement

Sponsors

Current T&E processes lack the ability to determine the

effort required for testing UASoS. The questions arises, Organizational Cost Drivers Cost DriversTechnical

Hierarchy of initial

survey responses Diversity and coordination of system platforms

Varying levels of system maturity locations

Stakeholder team cohesion

Transition

Partners

effort required for testing UASoS. The questions arises, “When am I done testing?” We hypothesize that the effort required for testing is directly related to the risks as well as technical and organizational cost drivers, which influence

Cost Drivers Cost Drivers

Drivers developed based on case studies, interviews

Complexity of test

Communication breakdown Changes in requirements/budget

Varying levels of system maturity cohesion

Number of organizations involved

Collaborators

technical and organizational cost drivers, which influence the testing and evaluation process. By using a risk based

testing and cost model approach we seek to answer this Rate of test data collection

on case studies, interviews and workshops

Changes in requirements/budget Maturity level of test

involved

Architecture

understanding of SoS

testing and cost model approach we seek to answer this question to determine the ultimate test stop point.

Rate of test data collection

Power availability for adapting new technologies

Security level of project This material is based upon work supported by the Department of Defense, United States Army, White Sands Missile Range, NM Under

Contract No. W9124Q-09-P-0230. Any opinions, findings and conclusions or recommendations, expressed in this material are those of the authors(s)and do not necessarily reflect the views of the Department of Defense, United States Army, While Sands Missile Range, NM.

Références

Documents relatifs

The packing problem seeks the maximum number of points with the distance between any two points greater than a given minimal distance, or, equivalently, the maximum

Within the graph topology, we prove that, if the plant admits a coprime factorization in the algebra of BIBO-stable systems, any linear distributed parameter plant can be ap-

A regularization algorithm allowing random noise in derivatives and inexact function val- ues is proposed for computing approximate local critical points of any order for

Overall, the uncertainty on the deduced fossil fuel flux is comparable to the uncertainty on the deduced NEE, using measurements at 25 m in July, because while the uncertainty of

We made the choice to distribute the different steps in three main activities, as shown in Figure 2, each performing a specific task in the testing of mobile applications:

Model testing tackles the untestability challenge by enabling software engineers to (1) execute and validate a much larger number of test scenarios, (2) develop test strategies

2. By strengthening the quality of components by taking into account their involvement in the global system that encapsulates them. The main idea consists in showing how to

Our contributions include (1) a DSL and supporting tools for specifying MRs for security testing, (2) a set of MRs in- spired by OWASP guidelines, (3) a data collection