1 5/20/2015 space cowboys team project final report defensive weapon subsystem mark foster
TRANSCRIPT
104/18/23 Space Cowboys Team Project Final Report
Defensive Weapon Subsystem
Mark Foster
204/18/23 Space Cowboys Team Project Final Report
Pneumatic “Jack Hammers”
All wheel drive4 wheel independent “off road” suspension (can climb over anything!)360 degree turningCapture device slams down on victim and pins it to floorJackhammer weapons rip it open
BattleBot Weapon Concept 1
304/18/23 Space Cowboys Team Project Final Report
Hook-n-Flippers
“Hook-n-Flippers” device “hooks” under victim and conveyer belt quickly rotatesVictim flipped over on back and is disabled
Conveyer Belt
BattleBot Weapon Concept 2
404/18/23 Space Cowboys Team Project Final Report
Tank Treads
Tank rolls over to victim and Pneumatic hammer activated when in rangeVictim disabled by repeated high impact hammer blowsTank treads provide 360 degree maneuverability and can roll over anythingTank treads can be sharpened steel to provide further damage capability
Pneumatic “Hammer”
Pneumatic “Hammer” Slams into Victim, and punches holes in it
BattleBot Weapon Concept 3
504/18/23 Space Cowboys Team Project Final Report
Pneumatic hammers on all six sides of vehicle for defense Pneumatic hammer activated when attacked – pushes attacker away (violently!)Attacker can also be disabled by repeated high impact hammer blows Can be converted to Offensive weapon - blunt hammer head can be replaced with sharpened point weapon
Pneumatic “Hammer”
Defensive “Hammer” Slams into Victim, and pushes it away or punches holes in it depending on weapon head
BattleBot Defensive Weapon - Final
604/18/23 Space Cowboys Team Project Final Report
Defensive (Def) Sub-system Requirements
req [Package] Defensive Weapon Subsystem.[Package]
«requirement»
id#Def2
txtThe Def sub-system shallphysically and electricallyinterface with thebattlebot system andsubsystems.
Interfaces
«requirement»
id#Def3
txtThe Defsub-system shallphysically interfacewith the Mobilitysubsystem.
Interface to Mobility
«requirement»
id#Def4
txtThe Def sub-systemshall physicallyinterface with thePneumaticsubsystem.
Interface toPneumatic
«requirement»
id#Def5
txt1. The Def sub-systemshall interface with thebattlebot systemCommand & Control(C&C) via the MobilityDiscrete CommandInterface.
2. The Def sub-systemshall acceptcommands from thebattlebot system C&Cvia the MobilityDiscrete CommandInterface.
Interface to C&C
«requirement»
id#Def7
txtThe Def sub-systemshall respond tocommands receivedfrom the battlebotC&C system.
Command & Control(C&C)
«requirement»
id#Def6
txt1. The Defsub-system shallelectrically interfacewith the battlebotPower subsystem.
2. The Defsub-system shallaccept power fromthe SCbb Powersubsystem.
Interface to Power«requirement»
id#Def8
txtThe Def sub-systemshall operate when a"FIRE" command isreceived from thebattlebot C&C.
Operational«requirement»
id#Def9
txtThe Def sub-systemshall remain passiveuntil a "FIRE"command isreceived from thebattlebot C&C.
Non-Operational
«requirement»
id#Def10
txtThe Def sub-systemshall Fail into a Safecondition.
Safety
«requirement»
id#Def11
txtThe Def sub-systemshall Fail into a Safecondition upon loss ofsystem power.
Fail Safe - Power
«requirement»
id#Def13
txtThe Def sub-systemshall Fail into a Safecondition upon loss of aDiscrete signal from theRC subsystem via theChassis DiscreteCommand Interface.
Fail Safe - C&C
«requirement»
id#Def12
txtThe Def sub-system shallFail into a Safe conditionupon loss of air pressurefrom the Pneumaticsubsystem.
Fail Safe - Air Pressure
«requirement»
id#Def1
txtThe Defensive Weapon (Def) sub-system shall Defend the Space Cowboysbattlebot against aggressors.
Defensive Weapon Subsystem Requirements
req [Package] Defensive Weapon Subsystem.[Package]
«requirement»
id#Def2
txtThe Def sub-system shallphysically and electricallyinterface with thebattlebot system andsubsystems.
Interfaces
«requirement»
id#Def3
txtThe Defsub-system shallphysically interfacewith the Mobilitysubsystem.
Interface to Mobility
«requirement»
id#Def4
txtThe Def sub-systemshall physicallyinterface with thePneumaticsubsystem.
Interface toPneumatic
«requirement»
id#Def5
txt1. The Def sub-systemshall interface with thebattlebot systemCommand & Control(C&C) via the MobilityDiscrete CommandInterface.
2. The Def sub-systemshall acceptcommands from thebattlebot system C&Cvia the MobilityDiscrete CommandInterface.
Interface to C&C
«requirement»
id#Def7
txtThe Def sub-systemshall respond tocommands receivedfrom the battlebotC&C system.
Command & Control(C&C)
«requirement»
id#Def6
txt1. The Defsub-system shallelectrically interfacewith the battlebotPower subsystem.
2. The Defsub-system shallaccept power fromthe SCbb Powersubsystem.
Interface to Power«requirement»
id#Def8
txtThe Def sub-systemshall operate when a"FIRE" command isreceived from thebattlebot C&C.
Operational«requirement»
id#Def9
txtThe Def sub-systemshall remain passiveuntil a "FIRE"command isreceived from thebattlebot C&C.
Non-Operational
«requirement»
id#Def10
txtThe Def sub-systemshall Fail into a Safecondition.
Safety
«requirement»
id#Def11
txtThe Def sub-systemshall Fail into a Safecondition upon loss ofsystem power.
Fail Safe - Power
«requirement»
id#Def13
txtThe Def sub-systemshall Fail into a Safecondition upon loss of aDiscrete signal from theRC subsystem via theChassis DiscreteCommand Interface.
Fail Safe - C&C
«requirement»
id#Def12
txtThe Def sub-system shallFail into a Safe conditionupon loss of air pressurefrom the Pneumaticsubsystem.
Fail Safe - Air Pressure
«requirement»
id#Def1
txtThe Defensive Weapon (Def) sub-system shall Defend the Space Cowboysbattlebot against aggressors.
Defensive Weapon Subsystem Requirements
704/18/23 Space Cowboys Team Project Final Report
Defensive (Def) Sub-system Requirements Table
Name Txt Rationale Satisfied By Parent Requirement
Defensive Weapon Subsystem RequirementsThe Defensive Weapon (Def) sub-system shall Defend the Space Cowboys battlebot against aggressors.
InterfacesThe Def sub-system shall physically and electrically interface with the battlebot system and subsystems.
«requirement» Defensive Weapon Subsystem Requirements (Defensive Weapon Subsystem - Mark::Requirements)
Command & Control (C&C) The Def sub-system shall respond to commands received from the battlebot C&C system. «requirement» Defensive Weapon Subsystem Requirements (Defensive Weapon Subsystem - Mark::Requirements)
Safety The Def sub-system shall Fail into a Safe condition. «requirement» Defensive Weapon Subsystem Requirements (Defensive Weapon Subsystem - Mark::Requirements)
Interface to Mobility The Def sub-system shall physically interface with the Mobility subsystem.«requirement» Interfaces (Defensive Weapon Subsystem - Mark::Requirements::Defensive Weapon Subsystem Requirements)
Interface to Pneumatic The Def sub-system shall physically interface with the Pneumatic subsystem. «requirement» Interfaces (Defensive Weapon Subsystem - Mark::Requirements::Defensive Weapon Subsystem Requirements)
Interface to C&C
1. The Def sub-system shall interface with the battlebot system Command & Control (C&C) via the Mobility Discrete Command Interface.
2. The Def sub-system shall accept commands from the battlebot system C&C via the Mobility Discrete Command Interface.
«requirement» Interfaces (Defensive Weapon Subsystem - Mark::Requirements::Defensive Weapon Subsystem Requirements)
Interface to Power1. The Def sub-system shall electrically interface with the battlebot Power subsystem.
2. The Def sub-system shall accept power from the SCbb Power subsystem.
«requirement» Interfaces (Defensive Weapon Subsystem - Mark::Requirements::Defensive Weapon Subsystem Requirements)
Operational The Def sub-system shall operate when a "FIRE" command is received from the battlebot C&C.«requirement» Command & Control (C&C) (Defensive Weapon Subsystem - Mark::Requirements::Defensive Weapon Subsystem Requirements)
Non-OperationalThe Def sub-system shall remain passive until a "FIRE" command is received from the battlebot C&C.
«requirement» Command & Control (C&C) (Defensive Weapon Subsystem - Mark::Requirements::Defensive Weapon Subsystem Requirements)
Fail Safe - Power The Def sub-system shall Fail into a Safe condition upon loss of system power. «requirement» Safety (Defensive Weapon Subsystem - Mark::Requirements::Defensive Weapon Subsystem Requirements)
Fail Safe - C&CThe Def sub-system shall Fail into a Safe condition upon loss of a Discrete signal from the RC subsystem via the Chassis Discrete Command Interface.
«requirement» Safety (Defensive Weapon Subsystem - Mark::Requirements::Defensive Weapon Subsystem Requirements)
Fail Safe - Air PressureThe Def sub-system shall Fail into a Safe condition upon loss of air pressure from the Pneumatic subsystem.
«requirement» Safety (Defensive Weapon Subsystem - Mark::Requirements::Defensive Weapon Subsystem Requirements)
804/18/23 Space Cowboys Team Project Final Report
Defensive (Def) Sub-system Level Domain (bdd)
bdd [Package] 8- Defensive Subsystem Structure
«block»Defensive Weapon Subsystem
«block»Plunger - Left
«block»Plunger - Right
«block»Plunger - Rear
«block»BattleBot Vehicle
«block»Plunger - Front
Ltpln RtplnRrplnFtpln
Defense
«requirement»
Weapons«satisfy»
bdd [Package] 8- Defensive Subsystem Structure
«block»Defensive Weapon Subsystem
«block»Plunger - Left
«block»Plunger - Right
«block»Plunger - Rear
«block»BattleBot Vehicle
«block»Plunger - Front
Ltpln RtplnRrplnFtpln
Defense
«requirement»
Weapons«satisfy»
904/18/23 Space Cowboys Team Project Final Report
Defensive (Def) Sub-system Package Structure
1004/18/23 Space Cowboys Team Project Final Report
Defensive (Def) Sub-system Interfaces (ibd)ibd [block] 9 - Defensive Weapon Subsystem Interfaces
Defensive Weapon Subsystem
«part»
Ltpln : Plunger - Left
1104/18/23 Space Cowboys Team Project Final Report
Defensive (Def) Sub-system Use Case Diagram
BattleBotOperator
FIREPlunger
Defend AgainstOpponent
Safe DefensiveSub-System
«include»
«include»BattleBotOperator
FIREPlunger
Defend AgainstOpponent
Safe DefensiveSub-System
«include»
«include»