Top Banner

Click here to load reader

1October 29, 2007 © 2007 BAE Systems Land & Armaments L.P. October 29, 2007 Tom Schroeder FCS MGV Software Engineering Manager BAE Systems, Ground Systems

Dec 19, 2015

ReportDownload

Documents

  • Slide 1
  • 1October 29, 2007 2007 BAE Systems Land & Armaments L.P. October 29, 2007 Tom Schroeder FCS MGV Software Engineering Manager BAE Systems, Ground Systems Integrating Systems and Software Engineering: Observations in Practice
  • Slide 2
  • 2October 29, 2007 2007 BAE Systems Land & Armaments L.P. Purpose Provide a perspective on: Integrating Systems and Software Engineering for Complex Systems. From the perspective of a major supplier and integrator Starting Build 2 What are the significant issues and concerns expressed by project suppliers? What works in practice? What doesnt? How can the Incremental Commitment Model be improved?
  • Slide 3
  • 3October 29, 2007 2007 BAE Systems Land & Armaments L.P. Protected Fighting Platforms for Todays Warfighter as well as the Battlefield of Tomorrow Predominant Supplier to the U.S. Army Heavy Brigades with Bradley, HERCULES, Paladin, M113 Mine-Protected Wheeled Vehicles FCS Manned Ground Vehicles and Armed Robotic Vehicle Key Technologies Advanced Protection and Mobility Solutions for Soldiers, Manned Vehicles and Robots Outstanding Program Management and Experienced Workforce 3,250 employees, including more than 600 technologists World-Class Development Processes CMMI Level 5 Software and Systems Engineering Process Physics-Based Models & Real-Time Simulation Capabilities Rapid Prototyping of Complex Systems Lean, Cost-effective Production Facilities Ground Systems A Summary GS is a modern, efficient, full-spectrum developer, integrator and supplier of survivable, lethal ground combat platforms and advanced technologies
  • Slide 4
  • 4October 29, 2007 2007 BAE Systems Land & Armaments L.P. FCS Brigade Combat Team (BCT) 18 Integrated Systems + 1 Network + 1 Soldier FCS is about the 21 st Century Soldier Approved for Public Release, Distribution Unlimited, TACOM 20 SEP 2006, case 06-208.
  • Slide 5
  • 5October 29, 2007 2007 BAE Systems Land & Armaments L.P. An MGV Vehicle Platform MGV Base Platform Software Context Base Vehicle Logistics / Sustainment ISR Training Integrated Platform: MGV Platform Integrated Platform: MGV Platform RealTime, Deterministic Software - Isolated from the C 2 Network C2C2 C2C2 Inter-Platform Behaviors: Brigade Combat Team SOS Vehicle Platforms Must be Designed for Integration and Evolution
  • Slide 6
  • 6October 29, 2007 2007 BAE Systems Land & Armaments L.P. Characteristics of Project from a Software Perspective Extremely large System of Systems project Target computing hardware developed concurrently with software Includes vehicle computers, remote interface units, servo control units Includes many additional subsystems internally produced/procured and externally provided Most final hardware not available during early build iterations Must substitute host and surrogate development environments Evolve Simulators to Emulators and Stimulators Many decisions not under platform suppliers control Interface contracts extremely important due to size of SOS Successive refinement and elaboration through multiple levels of Systems Engineering to Software Engineering At Software level, utilize IDL and interface code generators to minimize architecture dependencies Utilize common design patterns for communications across deployable software entities Pub-sub, proxy, etc. Ideally generate IDL directly from tagged attributes in shared design model Requires all groups to use same interface modeling approach Allows for one data dictionary
  • Slide 7
  • 7October 29, 2007 2007 BAE Systems Land & Armaments L.P. Software Build 1 Objectives Build initial prototype vehicles for one vehicle type (variant), the Non- Line of Sight Cannon (NLOS-C), to be assembled in 2008 Develop threshold path common components and software for a common chassis. Hybrid Electric Drive Powertrain, Driving functions, Vehicle Management Power Distribution, Remote Interface Units, Servo Control Units Embedded Training Develop threshold path mission equipment and software for the weapon and mission control functions Develop low-cost software and hardware surrogates to stand-in for functionality that is not yet available, such as the sustainment system, the displays and user interface system, etc. Develop and improve processes for software development and integration Reduce risk for objective vehicles and software development
  • Slide 8
  • 8October 29, 2007 2007 BAE Systems Land & Armaments L.P. Software Build 2 Objectives Build out software infrastructure for all MGV variants Ensure that MGV common components and common software can be configured for every MGV variant Develop vehicle and mission module control functions for all MGV variants Utilize and integrate externally provided software and subsystems Prove viability of layered software infrastructure Define peer interfaces at application level across SOS Continue to develop and improve processes for systems and software development and integration Better integrate MGV Systems and Software Engineering Workflows Improve Coordination with SOS Development Continue to reduce risk for objective vehicles and software development
  • Slide 9
  • 9October 29, 2007 2007 BAE Systems Land & Armaments L.P. VNT SW Test VNT SW Int VNT SW I&T Env CMN SW Test CMN SW Int CMN SW I&T Env SW I&T SW C&UT SW Design SW Rqmts SW Mgmt & Env SSys Spec/Alloc SSys Design SSys AL2 Rq Sys Spec/Alloc Sys Design Sys PIDS/AL1 Rq VNT SW Test VNT SW Int VNT SW I&T Env CMN SW Test CMN SW Int CMN SW I&T Env SW I&T SW C&UT SW Design SW Rqmts SW Mgmt & Env SSys Spec/Alloc SSys Design SSys AL2 Rq Sys Spec/Alloc Sys Design Sys PIDS/AL1 Rq VNT SW Test VNT SW Int VNT SW I&T Env CMN SW Test CMN SW Int CMN SW I&T Env SW I&T SW C&UT SW Design SW Rqmts SW Mgmt & Env SSys Spec/Alloc SSys Design SSys AL2 Rq Sys Spec/Alloc Sys Design Sys PIDS/AL1 Rq VNT SW Test VNT SW Int VNT SW I&T Env CMN SW Test CMN SW Int CMN SW I&T Env SW I&T SW C&UT SW Design SW Rqmts SW Mgmt & Env SSys Spec/Alloc SSys Design SSys AL2 Rq Sys Spec/Alloc Sys Design Sys PIDS/AL1 Rq VNT SW Test VNT SW Int VNT SW I&T Env CMN SW Test CMN SW Int CMN SW I&T Env SW I&T SW C&UT SW Design SW Rqmts SW Mgmt & Env SSys Spec/Alloc SSys Design SSys AL2 Rq Sys Spec/Alloc Sys Design Sys PIDS/AL1 Rq Engineering Cycle 2.n+2Engineering Cycle 2.n+1Engineering Cycle 2.n Integration of Systems and Software Engineering: MGV Sys/Sw Workflow Design 4 months Software Integration EC 2.n-1 Software EC 2.n Systems EC 2.n+1 Workflow Stages @ Points in Time
  • Slide 10
  • 10October 29, 2007 2007 BAE Systems Land & Armaments L.P. Idealized Systems and Software Integrated Build Life Cycle Year 2Year 1 S/SSSWSIT DI 2.1 Start S/SSSWSIT DI 2.2 S/SSSWSIT DI 2.3 S/SSSWSIT DI 2.4 S/SSSWSIT S/SSSWSIT DI 2.6 S/SSSWSIT DI 2.7 S/SSSW DI 2.8 SwLCO (ACR) SwLCA (DCR) SyLCO SyLCA Inception Phase Elaboration Phase Construction Phase Transition Phase TRRs Acronyms and Abbreviations DI b.cDevelopment Increment, Build b, Increment c IOCInitial Operational Capability LCALife Cycle Architecture Milestone LCOLife Cycle Objectives Milestone S/SSSystems/Subsystems (IPT) Engineering SISoftware Item SITSoftware Subsys/Sys Integration & Test SWSoftware Engineering (incl. SI-Level Int & Test) SwLCASoftware LCA SwLCOSoftware LCO SyLCASystems/Subsystems LCA SyLCOSystems/Subsystems LCO TRRTest Readiness Review (SI Level) IOC SIT DI 2.5 By adding Systems & Subsystems requirements and design engineering stages synchronized with Software development increments, upstream work products can be worked iteratively to support Software. Software can provide valuable implementation feedback to Systems & Subsystems teams, with pre- planned learning adjustments. Consider introduction of Systems LCO and LCA events. Need to keep as separate Sys/SW events to coordinate workflows?
  • Slide 11
  • 11October 29, 2007 2007 BAE Systems Land & Armaments L.P. Systems Engineering Support to LCO (ACR) LCO viewed by MGV Systems Engineering as a Software Event, but SE provided required support. Created internal RBR (Requirements Baseline Review) milestone to have the LCO equivalent for Systems within MGV. Created mappings from MGV System Use Cases to MGV Software Capabilities, and scheduled Systems, Software, and Integration Thread capabilities across all Development Iterations. What level of completion of Systems Engineering work products is needed for Software to have a successful LCO? Recent RBR Experience: All requirements allocated to software were specified at a broad level, with traceability to upper-level models. Challenge was leveling MGV IPTs to consistent levels of detail, and gaining consistent support across every team Factored out common use cases to ensure consistent requirements Some systems requirements were developed in greater depth Vehicle start-up, shut-down, mode changes Other documents were made available as reference (works in progress) which will be matured leading up to System PDR: System Architecture which may include applicable DDM's, such as Vehicle Electronics Architecture, System/Subsystem Schematics, Specialty Engineering Reports (Security, HFE/MANPRINT, Safety, Maintainability), Sustainment and Training Design Concepts Thread based performance analyses Current Version of Common Subsystem and Variant Level S/SDD's Vehicle External ICDs - Interfaces to all C4ISR, Sustainment, and Training supplied subsystems. Vehicle Internal ICDs Interfaces to MGV Subsystems HW Configuration Item Specifications (HW CIDS - as available)
  • Slide 12