• If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.

  • Stop wasting time looking for files and revisions. Connect your Gmail, DriveDropbox, and Slack accounts and in less than 2 minutes, Dokkio will automatically organize all your file attachments. Learn more and claim your free account.


Systems Engineering (Basic Game)

Page history last edited by tmckendree@socal.rr.com 11 years, 4 months ago



A "15 Minute" Game


Time to complete: ~5 minutes (to get idea fully worked out in my head) - 90 minutes (to create board, and read and proof the rules).


Theme: Systems Engineering (as represented by the classic "V" model).


The actually mechanics are a little unusual.  The rules are in the file, but I'll reproduce them here:



The Systems Engineering Game (Basic Game)


1.0 Introduction
This is a game about the systems engineering process, as represented by the “V” model.
2.0 Components
You will need a 6-sided die.  Each player will need their own copy of the player board, and a pen or pencil.  (Players can share a board if they write small, and in different colors.)
2.1 The Board
The board is a simple representation of the classic “V” model of systems engineering.  First you go down into deeper levels of design and analysis.  Then you integrate and test the smaller elements into larger elements, until you have completely built and tested your desired final system.
The board is divided into six regions.  You follow the “V” from Systems Analysis and Design to Component Analysis and Design, Component Integration and Test, and ultimately System Integration and Test.  You can get the board by printing out slide 3 of this file, The_SE_Game.ppt.
3.0 Moves
On your turn, roll the die, and then record your move on the board in your current region as described below.  Then pass the die to the player on your left, who takes the next move.
3.1 First Move
Each player starts at in the “System” Analysis and Design region (in the upper left).  Roll the die and write down in that region the value you rolled.  You may either accept that value (in which case you have completed System Analysis and Design, and successfully moved on to Subsystem Analysis and Design), or you can reject the value, which you indicate by “X”ing out the number.
3.2 Later Analysis and Design Moves
If you are still in a particular Analysis and Design region because you “X”ed your number on the previous turn, then roll again, and either accept that number (and move on), or “X” the new number
When you are at a lower level of design, you may not write down a value for that region larger than the value you accepted for your previous, next higher region.  Thus, if you are trying to complete “Subsystem” Analysis and Design, and your “System” Analysis and Design value is “4,” then if you roll a “5” you write down a “4,” not a “5.”
Numbers (including “X”d numbers) written down in the Analysis and Design regions represent attempts to leave those regions.
3.3 First Integration and Test Move
On the turn you complete “Component” Analysis and Design (i.e., you accept your value for that region), you have not yet fully entered “Component” Integration and Test.  On your next turn you roll the die, and write that number in the “Component” Integration and Test region.  If it is less than or equal to your value for “Component” Analysis and Design you have advanced to the “Component” Integration and Test region.  If it is equal to or greater than your value for “Component” Analysis and Design, then “X” the number out.  You have failed to advance.  
3.4 Later Integration and Test Moves
To enter an Integration and Test region, you must roll less than the value that you accepted for the corresponding Analysis and Design region.  Write the number rolled in the region you attempted to enter.  If the value is equal to or greater than the value of the corresponding “Analysis and Design” region, then “X” out the number; you have failed to enter the region.  If the value is less than the value of the corresponding “Analysis and Design” region, then leave the value as written; you have successfully completed that integration and test, and fully entered that region.
Numbers (including “X”d numbers) written down in an Integration and Test regions represent attempts to complete that integration and test, and thus enter that region.
4.0 Going Back
On any turn you may chose to go back.  This is indicated by “X”ing out the numbers for the spaces you are backing out of.  You may only back-up “in order” (i.e., if you are trying to enter “Component” Integration and Test you can only back up to redo “Subsystem” Analysis and Design if you back up through, and thus “X”s out, “Component” Integration and Test and “Component” Analysis and Design.  You “Goes Back”  before rolling, and then takes your turn from the region you have gone back to.
5.0 Winning
The winner is the first player to complete the entire track.  This occurs when the player have already successfully made it to the “Subsytems” Integration and Test Region and then rolls less than their “System” Analysis and Design value, allowing them to complete “System” Integration and Test, and thus enter that region.
6.0 Variations
The first player has a slight advantage, so players may instead agree see how many moves it takes each player to complete.  If two or more players complete in the same lowest number of moves, then they tie.
Players may agree use some random number generator other than a 6-sided die, as long as all players use the same device.  For examples, players could draw cards from a deck and use the card valued (treating face cards as 10 or counting J, Q, K as three values above 10).  Players could roll a 4, 8, 12, or 20-sided die.  Players could roll 2 six-sided dice and add them for the random value on their turn.
Players may also agree to play a more intricate version, with their own house rules if they wish.  For example, see “The Systems Engineering Game (Advanced Game).”
7.0 Acknowledgments
Thank you to Ian Schreiber for assigning “Invisible Barrier,” to Brenda Brathwaite for inventing this assignment, and to Ursula McKendree for everything.
© 2009, Tom McKendree

Comments (0)

You don't have permission to comment on this page.