1 6/14/2015 Space Cowboys Team Project Final Report System-Level Modeling Jim Smith

2 6/14/2015 Space Cowboys Team Project Final Report Modeling Approach Partitioned BattleBots project to a System with 5 “subsystems” SYSTEM – ALL: Jim Smith Remote Controller Subsystem: Jim Smith Pneumatic Subsystem: Mark Foster Defensive Weapon Subsystem: Mark Foster Offensive Weapon Subsystem:Chris Hokans Mobility Subsystem: Brett Padgett Performed bulk of work at subsystem-level and used system-level modeling elements as “framework” “System of Systems” paradigm Subsystems developed from top-level SYSTEM-ALL blocks (top-down “cascading” development approach) Configuration managed each subsystem (and system-level) on package boundaries via Artisan import/export Weekly (or more as needed) export of subsystems were imported into the SYSTEM - ALL model (from Google Site) SYSTEM - ALL model Exported to team (on Google Site) Each team member was always in sync with entire system this way

3 6/14/2015 Space Cowboys Team Project Final Report Model Structure Model Structure Aligned to SysML “Four Pillars”

4 6/14/2015 Space Cowboys Team Project Final Report System-Level Requirements System level requirements from the BB Rulebook Linked subsystem blocks to ensure the System requirements were “Satisfied”

5 6/14/2015 Space Cowboys Team Project Final Report System-Level Domain (bdd)

6 6/14/2015 Space Cowboys Team Project Final Report Subsystem-Level Interfaces (ibd) This became our de-facto “Interface Control Document”

7 6/14/2015 Space Cowboys Team Project Final Report System-Level Interfaces / Value Types

8 6/14/2015 Space Cowboys Team Project Final Report System-Level Use Case Diagram

9 6/14/2015 Space Cowboys Team Project Final Report