Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

TES-SAVi MBSE for SoSEnI Opportunities

190 views

Published on

  • Be the first to comment

  • Be the first to like this

TES-SAVi MBSE for SoSEnI Opportunities

  1. 1. Future Challenges (Opportunities) of (for) Systems Engineers Model-Based Systems Engineering (MBSE) Developing and Qualifying Open Systems and Applications onto US Army Aviation Systems Copyright (C) Tucson Embedded Systems, 2015 – All Rights reserved Presented to SoSE&I 2015 Senior Acquisition Engineering Leadership Workshop 20 August 2015 Stephen M. Simi VP & PM for Military Aviation Programs TES-SAVi AWESUMTM StephenS@TucsonEmbedded.com
  2. 2. What If? Copyright (C) Tucson Embedded Systems-System Architecture Virtual Integration (TES-SAVi), 2015 – All Rights reserved What if a ~90% Process Improvement awaits SoS E&I?
  3. 3. Future Challenges / Opportunities • Open Systems (standards like FACE and VICTORY) will – Expand the Military Developer Marketplace – Encourage reuse of portable capabilities (applications) – Increase interoperability (of advance capabilities) – Ensure Dominance of the Battle Space • MBSE (Model-based Systems Engineering) processes and tools present systems engineers with opportunities – They can be used to efficiently “manufacture and deploy” RSCs and RVCs • RSC - reusable software components – defined by FAA’s AC 20-148 • RVC - reusable verification components – i.e., reusable test harness, that is used to support Platform integration efforts • Challenges and Gaps – Airworthiness (Safety) is accessed at the Systems Level • not at the device/component-level, software library (< RSCs live here) – Gaps exist for MBSE tools, especially at the Component, Systems and SoS levels that support efficient Airworthiness. SoSE&I and the Army should leverage MBSE 3(UNCLASSIFIED / TES Copyrighted – SEE TITLE PAGE)
  4. 4. Future Challenges / Opportunities • Army Airworthiness guidelines AR 70-62, FAA AC-115c, DO-178c/DO-331 – Requires evidence (artifacts/demonstrations) that the design assurance level (DAL) objectives are satisfied – PSAC through SAS – Clarify the Roles of the Developer vs. Platform Systems Integrator – (??) DO-178c DAL A Objectives – this is the lifecycle LOE – (??) DO-178c Objectives can be demonstrated by the Developer – (?) DO-178c Objectives can be demonstrated by the Integrator 4(UNCLASSIFIED / TES-SAVi Copyrighted – SEE TITLE PAGE)
  5. 5. Future Challenges / Opportunities • Army Airworthiness guidelines AR 70-62, AC-115c, DO-178c/331 – Requires evidence (artifacts/demonstrations) that the design assurance level (DAL) objectives are satisfied – PSAC through SAS – Clarify the Roles of the Developer vs. Platform Systems Integrator – 72 DO-178c DAL A Objectives – this is the lifecycle LOE – (??) DO-178c Objectives can be demonstrated by the Developer – (?) DO-178c Objectives can be demonstrated by the Integrator 5(UNCLASSIFIED / TES-SAVi Copyrighted – SEE TITLE PAGE) MBSE Dashboard quantifies progress toward completion
  6. 6. Future Challenges / Opportunities • Army Airworthiness guidelines AR 70-62, AC-115c, DO-178c/331 – Requires evidence (artifacts/demonstrations) that the design assurance level (DAL) objectives are satisfied – PSAC through SAS – Clarify the Roles of the Developer vs. Platform Systems Integrator – 72 DO-178c DAL A Objectives – this is the lifecycle LOE – 65 DO-178c Objectives can be demonstrated by the Developer – (?) DO-178c Objectives can be demonstrated by the Integrator 6(UNCLASSIFIED / TES-SAVi Copyrighted – SEE TITLE PAGE)
  7. 7. Future Challenges / Opportunities • Army Airworthiness guidelines AR 70-62, AC-115c, DO-178c/331 – Requires evidence (artifacts/demonstrations) that the design assurance level (DAL) objectives are satisfied – PSAC through SAS – Clarify the Roles of the Developer vs. Platform Systems Integrator – 72 DO-178c DAL A Objectives – this is the lifecycle LOE – 65 DO-178c Objectives can be demonstrated by the Developer – 7 DO-178c Objectives can be demonstrated by the Integrator 7(UNCLASSIFIED / TES-SAVi Copyrighted – SEE TITLE PAGE)
  8. 8. Future Challenges / Opportunities • Army Airworthiness guidelines AR 70-62, AC-115c, DO-178c/331 – Requires evidence (artifacts/demonstrations) that the design assurance level (DAL) objectives are satisfied – PSAC through SAS – Clarify the Roles of the Developer vs. Platform Systems Integrator – 72 DO-178c DAL A Objectives – this is the lifecycle LOE – 65 DO-178c Objectives can be demonstrated by the Developer – 7 DO-178c Objectives can be demonstrated by the Integrator 8 ~90% Process Improvement awaits if we Recognize & Adopt the value and role of Partial Qualifications (of RSCs) Align AR 70-62 with AC 20-148 (RSCs) AR 70-62 (Developer) & AR 70-62 (Integrator) (UNCLASSIFIED / TES-SAVi Copyrighted – SEE TITLE PAGE)
  9. 9. Summary Future Challenges Opportunities • Incorporate a SoSE&I Modular Open Systems Approach (MOSA) (like FACE) – Promotes application portability • Embrace MBSE Tools and Processes -- enables Model-Based Development Benefits – Auto-generate artifacts that support Airworthiness Certification (RSCs) – Auto-generate and execute test sequences, with coverage reporting (RVCs) – RSC certification artifacts re-usable for multiple platform certifications • Embrace the Adoption / Recognition of Partial Qualifications (of RSCs) – Modify AR70-62 to allow, AR70-62 (Developer) + AR70-62 (Integrator) • ~90% Process Improvement awaits – Enable efficient capability use/re-use across the Aviation fleet e.g., reuse FACE Applications in FACE Library provided they are developed with Army Airworthiness considerations • Army Aviation can leverage Reusable Software Component (FAA AC 20-148) Guidelines 9(UNCLASSIFIED / TES=SAVi Copyrighted – SEE TITLE PAGE) Initial AWR FACE Artifact Repository • Plans • Specs • Software • Test Results Conformance Reuse Platform Specific ~90% SoS E&I
  10. 10. Conclusion Future Challenges Opportunities • Open Systems (standards like FACE and VICTORY) will – .. Benefit the Warfighter, for they help • Expand the Military Developer Marketplace • Encourage reuse of portable capabilities (applications) • Increase interoperability (of advance capabilities) • Ensure Dominance of the Battle Space • MBSE (Model-based Systems Engineering) processes and tools present systems engineers with opportunities – Efficiently “manufacture” and deploy RSCs and RVCs – One day soon they will assist optimizing the qualifications of RSCs, and Systems, and SoSs – if we adopt FAA’s AC 20-148, and modify AR 70-62 (RSCs) • Challenges and Gaps – TES-SAVi is working to fill these GAPs 10(UNCLASSIFIED / TES-SAVi Copyrighted – SEE TITLE PAGE)

×