1 6/14/2015 space cowboys team project final report system-level modeling jim smith

104/18/23 Space Cowboys Team Project Final Report

System-Level Modeling

Jim Smith


Modeling ApproachPartitioned BattleBots project to a System with 5 “subsystems”SYSTEM – ALL: Jim Smith

Remote Controller Subsystem: Jim SmithPneumatic Subsystem: Mark FosterDefensive Weapon Subsystem: Mark FosterOffensive Weapon Subsystem: Chris HokansMobility Subsystem: Brett Padgett

Performed bulk of work at subsystem-level and used system-level modeling elements as “framework”

“System of Systems” paradigmSubsystems 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


Model Structure

Model Structure Aligned to SysML “Four Pillars”

pkg [Model] BattleBots [Model Organization]

System-Level - AllRemote ControllerSubsystem - Jim

Pneumatic Subsystem -Shared

Offensive WeaponSubsystem - Chris Mobility Subsystem - Brett

Defensive WeaponSubsystem - Mark

Behavior

Structure

Requirements

Parametrics

Behavior

Requirements

Structure

Parametrics

Behavior

Parametrics

Requirements

Structure

Behavior

Parametrics

Requirements

Structure

Behavior

Parametrics

Structure

Requirements

Behavior

Structure

Requirements

Parametrics

Value Types

System-Level Package DiagramLast Updated 22-Apr-2010

At the System-Level, we have a single BDD to define the BattleBots Domain, an IBD to define the subsystem-to-subsystem interfaces, a single Use Case Diagram to define system-level behavior, and a Requirements Diagram/Table for System-Level requirements

pkg [Model] BattleBots [Model Organization]

System-Level - AllRemote ControllerSubsystem - Jim

Pneumatic Subsystem -Shared

Offensive WeaponSubsystem - Chris Mobility Subsystem - Brett

Defensive WeaponSubsystem - Mark

Behavior

Structure

Requirements

Parametrics

Behavior

Requirements

Structure

Parametrics

Behavior

Parametrics

Requirements

Structure

Behavior

Parametrics

Requirements

Structure

Behavior

Parametrics

Structure

Requirements

Behavior

Structure

Requirements

Parametrics

Value Types

System-Level Package DiagramLast Updated 22-Apr-2010

At the System-Level, we have a single BDD to define the BattleBots Domain, an IBD to define the subsystem-to-subsystem interfaces, a single Use Case Diagram to define system-level behavior, and a Requirements Diagram/Table for System-Level requirements


req [Package] System-Level Requirements Diagram

«block»Remote Control Subsystem

«block»Mobility Subsystem



«requirement»«requirement»

id#SYS3.1.4

txtA BattleBots Robot’s remotecontrol equipment shall not:a. Cause interference with anyevent communications andbroadcast equipment.b. Be susceptible tointerference from any eventcommunications andbroadcast equipment.c. Interfere with the operationof any commercially-availableremote controllers.

Remote Control Interference

«requirement»

id#SYS3.3

txtThe Remote Controllershall use either a 900 Mhzor 2.4 GHz digital spreadspectrum frequency band.

Remote Control Frequency«requirement»

«requirement»

id#Sys1

txtThe Battlebot System shall conform to Battlebot Bulding Rules.

Battlebot

«requirement» «requirement»«requirement»


id#sys4.2.1

txtThe Battlebot Systemshall have an ActivationTime Less than 60seconds after initiation.

Activation Time

«requirement»

id#sys4.2.2

txtThe Battlebot Systemshall have aDe-Activation TimeLess than 60 seconds

De-Activation Time«requirement»

id#sys5.1.1

txtThe Battlebot Systemshall have a VoltageLimit of 36 VDC or 36AC RMS Voltsmaximum.

Voltage«requirement»«requirement»

«satisfy» «satisfy»«satisfy» «satisfy»

«satisfy»

«satisfy»

«satisfy»«satisfy»

«satisfy»«satisfy»«satisfy» «satisfy»

«satisfy»

«satisfy»

«satisfy»

«Rationale»

...«Ration ...BattleBot Building Rules 3.1.4

«Rati ...

BattleBot Building Rules 3.3 & 3.4

«Rationale»

req [Package] System-Level Requirements Diagram





«requirement»«requirement»

id#SYS3.1.4

txtA BattleBots Robot’s remotecontrol equipment shall not:a. Cause interference with anyevent communications andbroadcast equipment.b. Be susceptible tointerference from any eventcommunications andbroadcast equipment.c. Interfere with the operationof any commercially-availableremote controllers.

Remote Control Interference

«requirement»

id#SYS3.3

txtThe Remote Controllershall use either a 900 Mhzor 2.4 GHz digital spreadspectrum frequency band.

Remote Control Frequency«requirement»

«requirement»

id#Sys1

txtThe Battlebot System shall conform to Battlebot Bulding Rules.

Battlebot



id#sys4.2.1

txtThe Battlebot Systemshall have an ActivationTime Less than 60seconds after initiation.

Activation Time

«requirement»

id#sys4.2.2

txtThe Battlebot Systemshall have aDe-Activation TimeLess than 60 seconds

De-Activation Time«requirement»

id#sys5.1.1

txtThe Battlebot Systemshall have a VoltageLimit of 36 VDC or 36AC RMS Voltsmaximum.

Voltage«requirement»«requirement»

«satisfy» «satisfy»«satisfy» «satisfy»

«satisfy»

«satisfy»

«satisfy»«satisfy»

«satisfy»«satisfy»«satisfy» «satisfy»

«satisfy»

«satisfy»

«satisfy»

«Rationale»

...«Ration ...BattleBot Building Rules 3.1.4

«Rati ...

BattleBot Building Rules 3.3 & 3.4

«Rationale»

System-Level RequirementsSystem level requirements from the BB RulebookSystem level requirements from the BB Rulebook

Linked subsystem blocks to ensure the System

requirements were “Satisfied”


System-Level Domain (bdd)

bdd [Package] Structure [BattleBot Domain]

«block»BattleBot System

«block»BattleBot Vehicle



«block»Pit Crew Environment

«block»BattleBot Pit Crew Domain

«block»BattleBot Arena Domain

«block»BattleBot Domain

«block»Vehicle Environment

«block»Pneumatic Subsystem

«block»Defensive Weapon Subsystem

«block»Offensive Weapon Subsystem

Operator

Contestant

Pit Crew

JudgeRefereeCrewbot

Official

1

1RC

1

1battlebot

1

1

Vehicle

1

1PCE

1..2

1

OP

1

1PCD

1

1 AD

3..5

1

J1

1VE

*

2

R

1

1..*

C

1

1

BS

1..*

1

PC

1

1

Pneumatic

1

1

Defense

1

1

Offense

Jim Smith

Brett Padgett

Chris HokansMark Foster

Mark Foster

System-Level HierarchyLast Updated 22-Apr-2010














Operator

Contestant

Pit Crew

JudgeRefereeCrewbot

Official

1

1RC

1

1battlebot

1

1

Vehicle

1

1PCE

1..2

1

OP

1

1PCD

1

1 AD

3..5

1

J1

1VE

*

2

R

1

1..*

C

1

1

BS

1..*

1

PC

1

1

Pneumatic

1

1

Defense

1

1

Offense

Jim Smith

Brett Padgett


Mark Foster















Operator

Contestant

Pit Crew

JudgeRefereeCrewbot

Official

1

1RC

1

1battlebot

1

1

Vehicle

1

1PCE

1..2

1

OP

1

1PCD

1

1 AD

3..5

1

J1

1VE

*

2

R

1

1..*

C

1

1

BS

1..*

1

PC

1

1

Pneumatic

1

1

Defense

1

1

Offense

Jim Smith

Brett Padgett


Mark Foster















Operator

Contestant

Pit Crew

JudgeRefereeCrewbot

Official

1

1RC

1

1battlebot

1

1

Vehicle

1

1PCE

1..2

1

OP

1

1PCD

1

1 AD

3..5

1

J1

1VE

*

2

R

1

1..*

C

1

1

BS

1..*

1

PC

1

1

Pneumatic

1

1

Defense

1

1

Offense

Jim Smith

Brett Padgett


Mark Foster



Subsystem-Level Interfaces (ibd)

ibd [block] BattleBot System [Subsystem Interfaces]

«part»

RC : Remote Control Subsystem

This became our de-facto “Interface Control Document”


System-Level Interfaces / Value Types pkg [Package] Value Types for Battlebot

«FlowSpecification»

flowPropertiesout _GUID : Integerout Fire Hammer : Discreteout Fire Plunger : Discreteout Joystick X : Realout Joystick Y : Real

RF Energy

«valueType»Discrete

«valueType»Integer

«valueType»SysML Profile::Blocks::Blocks::Real

«Interface»Watts

«Interface»Analog

«Interface»Discrete

«Interface»CFM

«dataType»ARM


flowPropertiesin IN : Air Flowout OUT : Air Flow

AirFlow: CFM

«block»Air Flow

«use»

«use»

«use»«use»

pkg [Package] Value Types for Battlebot


flowPropertiesout _GUID : Integerout Fire Hammer : Discreteout Fire Plunger : Discreteout Joystick X : Realout Joystick Y : Real

RF Energy

«valueType»Discrete

«valueType»Integer

«valueType»SysML Profile::Blocks::Blocks::Real

«Interface»Watts

«Interface»Analog

«Interface»Discrete

«Interface»CFM

«dataType»ARM


flowPropertiesin IN : Air Flowout OUT : Air Flow

AirFlow: CFM

«block»Air Flow

«use»

«use»

«use»«use»


System-Level Use Case Diagram

Pit Crew

Operator

Judge

Referee

Crewbot

Defend AgainstOpponent

CoordinateMatch Stop

CoordinateMatch Start

Declare Fault

Monitor Match

DeclareTimeout

Start/StopMatch

DeclareMatch Winner

DisqualifyRobot

Maintain RemoteController

AttackOpponent

MaintainBattleBot

DriveBattleBot

Note: The Use Cases for the Officials are only shown for reference, and will not be modeled

Note: These Use Cases will not be elaborated at the System-Level, but will be elaborated in each of the Subsystem Packages

UCD [Package] Use Case [BattleBots Domain]

System-Level Use CaseLast Updated 18-Mar-2010

Pit Crew

Operator

Judge

Referee

Crewbot

Defend AgainstOpponent

CoordinateMatch Stop

CoordinateMatch Start

Declare Fault

Monitor Match

DeclareTimeout

Start/StopMatch

DeclareMatch Winner

DisqualifyRobot

Maintain RemoteController

AttackOpponent

MaintainBattleBot

DriveBattleBot

Note: The Use Cases for the Officials are only shown for reference, and will not be modeled

Note: These Use Cases will not be elaborated at the System-Level, but will be elaborated in each of the Subsystem Packages

UCD [Package] Use Case [BattleBots Domain]

System-Level Use CaseLast Updated 18-Mar-2010

1 6/14/2015 space cowboys team project final report system-level modeling jim smith

Documents