SystemLevel Modeling Jim Smith 12232021 Space Cowboys Team

System-Level Modeling Jim Smith 12/23/2021 Space Cowboys Team Project Final Report 1

Modeling Approach Partitioned Battle. Bots 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 12/23/2021 Space Cowboys Team Project Final Report 2

Model Structure Aligned to Sys. ML “Four Pillars” 12/23/2021 Space Cowboys Team Project Final Report 3

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

System-Level Domain (bdd) 12/23/2021 Space Cowboys Team Project Final Report 5

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

System-Level Interfaces / Value Types 12/23/2021 Space Cowboys Team Project Final Report 7

System-Level Use Case Diagram 12/23/2021 Space Cowboys Team Project Final Report 8

12/23/2021 Space Cowboys Team Project Final Report 9