Integrating Systems and Software Engineering: Observations in PracticePurposeGround Systems – A SummaryFCS Brigade Combat Team (BCT) 18 Integrated Systems + 1 Network + 1 SoldierMGV Base Platform Software ContextCharacteristics of Project from a Software PerspectiveSoftware Build 1 ObjectivesSoftware Build 2 ObjectivesIntegration of Systems and Software Engineering: MGV Sys/Sw Workflow DesignIdealized Systems and Software Integrated Build Life CycleSystems Engineering Support to LCO (ACR)Feasibility Rationale - Key Point: Need to Show EvidenceFeasibility Analysis Planning WorkshopSpan of Feasibility ConcernsSOS ChallengesOctober 29, 2007© 2007 BAE Systems Land & Armaments L.P.1October 29, 2007Tom SchroederFCS MGV Software Engineering ManagerBAE Systems, Ground SystemsIntegrating Systems and Software Engineering:Observations in PracticeOctober 29, 2007© 2007 BAE Systems Land & Armaments L.P.2PurposeProvide 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 doesn’t?How can the Incremental Commitment Model be improved?October 29, 2007© 2007 BAE Systems Land & Armaments L.P.3Protected Fighting Platforms for Today’s 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 FacilitiesGround Systems – A SummaryGS is a modern, efficient, full-spectrum developer, integrator and supplier of survivable, lethal ground combat platforms and advanced technologiesOctober 29, 2007© 2007 BAE Systems Land & Armaments L.P.4FCS Brigade Combat Team (BCT)18 Integrated Systems + 1 Network + 1 SoldierFCS is about the 21FCS is about the 21stst Century Soldier Century SoldierFCS is about the 21FCS is about the 21stst Century Soldier Century SoldierUnmanned Aerial VehiclesClass II Class III Class IV Class I ARV-A (L)Small (Manpackable) UGVMULE(Countermine)MULE(Transport)Unmanned Ground VehiclesUnattended Ground SensorsArmed Robotic Vehicle (ARV)Unattended MunitionsARV RSTAARV AsltIntelligent MunitionsSystemsNLOS LSInfantry CarrierVehicle (ICV)Manned SystemsCommand andControl Vehicle (C2V)Reconnaissance andSurveillance Vehicle (RSV)Mounted Combat System (MCS)Non-Line of SightCannon (NLOS-C)Non-Line of Sight Mortar (NLOS-M)Medical VehicleTreatment (MV-T)FCS Recovery and Maintenance Vehicle (FRMV)Medical VehicleEvacuation (MV-E)Approved for Public Release, Distribution Unlimited, TACOM 20 SEP 2006, case 06-208.October 29, 2007© 2007 BAE Systems Land & Armaments L.P.5An MGV Vehicle PlatformAn MGV Vehicle PlatformMGV Base Platform Software ContextMGV Base Platform Software ContextBase VehicleBase VehicleLogistics / SustainmentLogistics / SustainmentISRISRTrainingTrainingIntegrated Platform: “MGV Platform”Integrated Platform: “MGV Platform”Real–Time, Deterministic Software - Isolated from the C2 NetworkReal–Time, Deterministic Software - Isolated from the C2 NetworkC2C2Inter-Platform Behaviors: “Brigade Combat Team SOS”Inter-Platform Behaviors: “Brigade Combat Team SOS”Vehicle Platforms Must be Designed for Integration and EvolutionOctober 29, 2007© 2007 BAE Systems Land & Armaments L.P.6Characteristics 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 supplier’s 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 dictionaryOctober 29, 2007© 2007 BAE Systems Land & Armaments L.P.7Software 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 developmentOctober 29, 2007© 2007 BAE Systems Land & Armaments L.P.8Software 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