Proposed Unified ility Definition Framework. Andrew Long October 2012

Similar documents
REST Best Practices D. Keith Casey, Jr

Sustaining Lifecycle Value: Valuable Changeability Analysis with Era Simulation. Matthew Fitzgerald and Adam Ross IEEE Syscon 2012

DoD Strategy for Cyber Resilient Weapon Systems

A Method for Selecting Affordable System Concepts: A Case Application to Naval Ship Design

Non Functional Product Requirements (illeties)

Product Quality Engineering. RIT Software Engineering

Systems 2020 Strategic Initiative Overview

Implementing a Modular Open Systems Approach (MOSA) to Achieve Acquisition Agility in Defense Acquisition Programs

UNCLASSIFIED R-1 ITEM NOMENCLATURE FY 2013 OCO

UNCLASSIFIED R-1 ITEM NOMENCLATURE FY 2013 OCO

Helping the Military Integrate, Innovate and Secure Networks across the Enterprise

Raytheon Mission Architecture Program (RayMAP) Topic 1: C2 Concepts, Theory, and Policy Paper #40

Procedia Computer Science

Defense Engineering Excellence

IT Risk & Compliance Federal

Air Force Institute of Technology

TESTING SOFTWARE QUALITY CHARACTERISTICS

The Perfect Storm Cyber RDT&E

The NIST Cybersecurity Framework

Comparative Study of Software Quality Attributes in Perspective of Usability with Generalized Classification

Net-Centric Systems Design and Requirements Development in today s environment of Cyber warfare

Software Quality Engineering Tackles Security Issues

Mei Nagappan. How the programmer wrote it. How the project leader understood it. How the customer explained it. How the project leader understood it

Beyond Technical Interoperability Introducing a Reference Model for Measures of Merit for Coalition Interoperability

UNCLASSIFIED. UNCLASSIFIED Office of Secretary Of Defense Page 1 of 8 R-1 Line #18

UNCLASSIFIED. R-1 Program Element (Number/Name) PE D8Z / Software Engineering Institute (SEI) Applied Research. Prior Years FY 2013 FY 2014

Cyber Challenges and Acquisition One Corporate View

10 Steps to Building an Architecture for Space Surveillance Projects. Eric A. Barnhart, M.S.

UNCLASSIFIED FY 2016 OCO. FY 2016 Base

SUBMARINE CABLE DEVELOPMENTS. Karthik Kailasam Jan 16, 2017; PTC Hawaii

International Software & Systems Engineering Standards

Applying Context to Web Authentication

MODEL-DRIVEN DEVELOPMENT OF COMMAND AND CONTROL CAPABILITIES FOR JOINT AND COALITION WARFARE

ENTERPRISE ARCHITECTURE FOR THE AIR FORCE SATELLITE CONTROL NETWORK

UNCLASSIFIED FY 2016 OCO. FY 2016 Base

AMRDEC CYBER Capabilities

Cybersecurity ecosystem and TDL Antonio F. Skarmeta

Architecting for Resiliency Army s Common Operating Environment (COE) SERC

RDT&E BUDGET ITEM JUSTIFICATION SHEET (R-2 Exhibit) February 2000

QUALITY METRICS IMPLEMENTATION IN COMPONENT BASED SOFTWARE ENGINEERING USING AI BACK PROPAGATION ALGORITHM SOFTWARE COMPONENT

A Roadmap-Based Framework for Acquiring More Agile and Responsive C4I Systems. GMU-AFCEA C4I Symposium 19 May 2010 Eric Yuan

Inmarsat Global Xpress Global. Mobile. Trusted. U.S. Government > Services > Global Xpress

Lecture 19 Engineering Design Resolution: Generating and Evaluating Architectures

Trends in Migration to Enterprise Space Ground Systems SMC-IT* Mini-workshop Summary

UNCLASSIFIED R-1 ITEM NOMENCLATURE. FY 2014 FY 2014 OCO ## Total FY 2015 FY 2016 FY 2017 FY 2018

USSTRATCOM Global C2. Mr Dave Gelenter USSTRATCOM/J86 Mar This Briefing is UNCLASSIFIED

Introducing Cyber Resiliency Concerns Into Engineering Education

Software & Supply Chain Assurance: Enabling Enterprise Resilience through Security Automation, Software Assurance and Supply Chain Risk Management

Modularity and Open Systems: Meaningful Distinctions

Test Architect A Key Role defined by Siemens

DoD Software Assurance Initiative. Mitchell Komaroff, OASD (NII)/DCIO Kristen Baldwin, OUSD(AT&L)/DS

Systems Engineering Division

UNCLASSIFIED. FY 2016 Base FY 2016 OCO

How to Perform a Rapid Assessment of any Software Architecture

CS 307: Software Engineering. Lecture 10: Software Design and Architecture

Approaches to Achieve Benefits of Modularity in Defense Acquisition

Graduate Systems Engineering Programs: Report on Outcomes and Objectives

Cybersecurity Testing

Forecasting Technology Insertion Concurrent with Design Refresh Planning for COTS-Based Electronic Systems

STRENGTHENING THE CYBERSECURITY OF FEDERAL NETWORKS AND CRITICAL INFRASTRUCTURE

Naval Surface Warfare Center,

Trusted Components. Reuse, Contracts and Patterns. Prof. Dr. Bertrand Meyer Dr. Karine Arnout

A Hierarchical Model for Object- Oriented Design Quality Assessment

EXPERT SERVICES FOR IoT CYBERSECURITY AND RISK MANAGEMENT. An Insight Cyber White Paper. Copyright Insight Cyber All rights reserved.

Service Vs. System. Why do we need Services and a Services Viewpoint in DM2 and DoDAF? Fatma Dandashi, PhD March 4, 2011

Innovation policy for Industry 4.0

Security and resilience in Information Society: the European approach

Corso di Progettazione di Applicazioni Web e Mobile

INFORMATION ASSURANCE DIRECTORATE

Cyber Security Maturity Model

SDDC CAMPAIGN PLAN OVERVIEW MILITARY SURFACE DEPLOYMENT AND DISTRIBUTION COMMAND

Achieving DoD Software Assurance (SwA)

Improved Situational Awareness with OSIsoft PI for the U.S. Nuclear Regulatory Commission (NRC)

What Is a Distributed Simulation (i.e., A Federation)?

Systems Engineering for Software Assurance

Information Security Continuous Monitoring (ISCM) Program Evaluation

Roles and Responsibilities on DevOps Adoption

Protecting the Nation s Critical Assets in the 21st Century

Panel: Research on Complex Enterprise Systems of Systems. Complex Adaptive Systems Conference 14-NOV-2013

SPAWAR FLEET READINESS DIRECTORATE STRATEGIC PLAN STATEMENT A: Approved for public release, distribution is unlimited (JANUARY 2017)

Service-Oriented Architecture for Command and Control Systems with Dynamic Reconfiguration

Integrated C4isr and Cyber Solutions

Tailoring and Combining the CMMI-ACQ and Quality Models to Improve the Military s Requirements Process

Integration and Interoperability Models for Systems of Systems

Department of Homeland Security

Health Information Technology - Supporting Joint Readiness

CALL FOR PAPERS. Armed Forces Communications and Electronics Association (AFCEA), Erie Canal Chapter

Space Cyber: An Aerospace Perspective

The software lifecycle and its documents

SECURING THE UK S DIGITAL PROSPERITY. Enabling the joint delivery of the National Cyber Security Strategy's objectives

Agile Security Adaptable to Attack Evolution

STRATEGIC PLAN

Monitoring and Managing IIoT Security

DARPA Perspective on Space

Review Software Engineering October, 7, Adrian Iftene

National Information Exchange Model (NIEM):

SOFTWARE ARCHITECTURE & DESIGN INTRODUCTION

EMP Protection Validation Testing Approaches

The Next-Gen ISR Conference brought to you by:

Delimited. Interfaced. Readable. Modifiable. Verifiable. Prioritized* Endorsed

Transcription:

Identify, Innovate Explore, Engineer - Execute 1 1 Proposed Unified ility Definition Framework Andrew Long October 2012

Identify, Innovate Explore, Engineer - Execute 2 2 Motivation Increased interest in system ilities Lack of common understanding among practitioners Definitions Relationships between one ility and another Metrics Objective: Provide a framework to promote shared discussion of system ilities

Identify, Innovate Explore, Engineer - Execute 3 3 What are system ilities? -ility Latin: a suffix; meaning, ability, ability to [do something] In systems engineering ilities are desired system properties ilities describe the system (non-functional) rather than specific system behaviors (functional) Functional requirements define what a system is supposed to do; e.g. Performance Non-functional requirements define how a system is supposed to be.

Identify, Innovate Explore, Engineer - Execute 4 4 Some examples? Accessibility Accountability Adaptability Administrability Affordability Auditability Availability Credibility Compatibility Configurability Correctness Customizability Debugability Degradability Determinability Demonstrability Dependability Deployability Distributability Durability Effectiveness Evolvability Extensibility Fidelity Flexibility Installability Integrity Interchangeability Interoperability Learnability Maintainability Manageability Mobility Modifiability Modularity Operability Portability Predictability Provability Recoverability Reliability Repeatability Reproducibility Resilience Responsiveness Reusability Robustness Safety Scalability Sustainability Serviceability (a.k.a. supportability) Securability Simplicity Stability Survivability Sustainability Tailorability Testability Timeliness Traceability Ubiquity Understandability Upgradability Usability Versatility List of system quality attributes Wikipedia, May 2012

Identify, Innovate Explore, Engineer - Execute 5 5 Examples of ilities within the DoD Safety, Reliability, Availability, Maintainability, Testability (Traditional Systems Engineering) Interoperability (Net-Centric Warfare) Scalability / Extensibility (Software Design) Survivability (Military Platforms: Aircraft, Maritime, Ground) Resiliency (Space Systems, Cyber) Engineering Resilient Systems OSD(SE) initiative Flexibility (DARPA F6) Adaptability (Defense Science Board 2010 Report, DARPA AVM/ META) Affordability (Defense Acquisitions) USD/AT&L 2010 Better Buying Power memo Affordability as a requirement Sustainability (Supply Chain, Industrial Base, Work Force)

Identify, Innovate Explore, Engineer - Execute 6 6 Common element: Uncertainty In system engineering, uncertainties occur in performance & value expectations Performance: Variance between actual and desired system performance resulting from uncertainty within contexts (e.g. design, production, operations, etc.) Value: Variance in expected value resulting from feedback of delivered value, resulting from changing context, stakeholders, needs, etc. ilities account for a system s ability to change / react to uncertainty Figure adapted from: Ross, A.M., and Rhodes, D.H., "Using Natural Value-centric Time Scales for Conceptualizing System Timelines through Epoch-Era Analysis," INCOSE International Symposium 2008, Utrecht, the Netherlands, June 2008

Identify, Innovate Explore, Engineer - Execute 7 7 Designing for Uncertainty System changeability taxonomy (Ross et al.) provides start for defining system ilities Change Agent Change Effect Change Objective Change Enablers Change Considerations Ross, A.M., Rhodes, D.H., and Hastings, D.E., "Defining Changeability: Reconciling Flexibility, Adaptability, Scalability, Modifiability, and Robustness for Maintaining Lifecycle Value," Systems Engineering, Vol. 11, No. 3, pp. 246-262, Fall 2008.

Identify, Innovate Explore, Engineer - Execute 8 8 Change Agents Instigator, or force, which employs a given change mechanism in order to achieve a desired change effect Two approaches to choosing a change agent Internal: System self-imposed change (Adaptability) Associated with upfront / current decisions to respond to change (i.e. Pre-planned / Baked in) Commonly used to address known - knowns External: Decision-maker imposed change (Flexibility) Associated with future / delayed decisions to respond to change (i.e. Real options) Used to address known - knowns & known - unknowns

Identify, Innovate Explore, Engineer - Execute 9 9 Change Effect The difference in system states (performance or value) before and after a change has taken place Three choices of change effects Expandability(Do More / Less) Ross et al. references scalability, but expandability used to de-conflict w/ more common scalability definitions Modifiability (Add, Remove, Alter ) Robustness (No Change)

Identify, Innovate Explore, Engineer - Execute 10 10 Change Objectives The specific approach / plan / goal / strategies employed to achieve a desired change effect Objectives enabled by change enablers and must account for change considerations Think of these as common ility families. Change Effect Robustness Performance Objectives (Static) Quality (Assurance and control) Safety Reliability Availability Maintainability Testability Value Objectives (Dynamic) Resiliency Awareness Survivability Susceptibility Vulnerability Recoverability Expandability Scalability Extensibility Modifiability Configurability Evolvability

Identify, Innovate Explore, Engineer - Execute 1 11 Change Enablers Change enablers (e.g. design elements) enable desired objective How is the system is designed to change Any one, or combination of, enablers can satisfy an objective Any enabler can satisfy one or more objectives Change Enablers Accessibility Compatibility Commonality Distributability Durability Homogeneity Heterogeneity Interchangeability Interoperability Mobility Modularity Portability Repairability Reusability Serviceability (a.k.a. supportability) Understandability Usability / operability

Identify, Innovate Explore, Engineer - Execute 12 12 Change Considerations Design considerations (e.g. conditions, resources, constraints, etc.) applied to design / operational approaches Affordability (Budget) Sustainability (Resources) Agility / Responsiveness (Schedule / Response time) Manufacturability (Technology) Manageability (Organizational)

Identify, Innovate Explore, Engineer - Execute 13 13 Proposed ility Framework Change Agents Flexibility (External) Adaptability (Internal) Change Effect Change Enablers Robustness Change Considerations Performance Change Objectives Quality (Assurance and control) Safety Reliability Availability Maintainability Testability Value Change Objectives Resiliency Awareness Susceptibility Vulnerability Recoverability Expandability Scalability Extensibility Modifiability Configurability Evolvability Accessibility Compatibility Commonality Distributability Durability Homogeneity Heterogeneity Interchangeability Interoperability Affordability Sustainability Mobility Modularity Portability Repairability Reusability Serviceability (a.k.a. supportability) Understandability Usability / operability Agility / Responsiveness Manufacturability

Identify, Explore, Execute 14 Innovate Engineer - Execute 14 Questions?