https://ideawaza.com/api.php?action=feedcontributions&feedformat=atom&user=70.110.42.176 2026-09-30T01:48:10Z User contributions MediaWiki 1.46.0 https://ideawaza.com/index.php?title=Archive:CisLunarFreighter/Initial_splashscreen,_launcher,_menu&diff=48303 2007-01-29T04:22:35Z

<p>70.110.42.176: add a go to main components link</p> <hr /> <div>go to main component list[http://en.wikiversity.org/wiki/CisLunarFreighter_A_Requirements_Analysis_and_High_Level_Design_Exercise]<br /> <br /> <br /> Component Name:Launcher<br /> <br /> Responsibilities: This is the main java file which calls the splash animation, initializes the game, then calls the main menu for initial player interaction. When the player is done this module terminates the program.<br /> <br /> Collaborators:<br /> <br /> * Animation player<br /> * Background display<br /> * Main Menu</div>

70.110.42.176 https://ideawaza.com/index.php?title=Archive:CisLunarFreighter/Initial_splashscreen,_launcher,_menu&diff=48302 2007-01-29T04:19:27Z

<p>70.110.42.176: Initial cut at launcher responsibilities</p> <hr /> <div>Component Name:Launcher<br /> <br /> Responsibilities: This is the main java file which calls the splash animation, initializes the game, then calls the main menu for initial player interaction. When the player is done this module terminates the program.<br /> <br /> Collaborators:<br /> <br /> * Animation player<br /> * Background display<br /> * Main Menu</div>

70.110.42.176 https://ideawaza.com/index.php?title=Archive:CisLunarFreighter/Requirement_analysis_and_high_level_design&diff=48293 2007-01-29T04:12:29Z

<p>70.110.42.176: break page into sections</p> <hr /> <div>Object Oriented Software Engineering<br /> :Component, Responsibility, Collaborators (&lt;b&gt;CRC&lt;/b&gt;)Cards - 4&quot; X 6&quot; note cards<br /> ::Design, Code, or Case Scenario Walkthroughs<br /> <br /> ==CRC Cards==<br /> <br /> This exercise is based loosely upon the technique demonstrated in Chapter One of Classic Data Structures in C++ by Timothy A. Budd, cp1994 by Addison-Wesley Publishing Company, Inc. In a local object orieted design project using C++ CRC (Component, Responsibility, Collaborating Objects) cards are used to jot down names and bullets outlining the high level components identified in walkthrough as required for the project design.<br /> <br /> ==Local Adaptation==<br /> <br /> The procedure we shall use here for asnychronous, distributed, walkthroughs is as follows: Individual files shall be created for proposed components. Responsibilities for that component jotted down in bullet form at the top of the screen, simulating a 4&quot; X 6&quot; note card. When another component is called a link will be created to that component. Actions the component must complete are list in the bottom half of the computer screen/file.<br /> <br /> For the highest level walkthough or design Budd designates the most important characteristics of potential design components as:<br /> 1. A small set of well defined responsibilities must result. If the component has too many responsibilities then it should be busted into multiple components and the walkthrough reaccomplished.<br /> 2. Interactions with other components should be minimalized to the greatest extent possible.<br /> <br /> Effort expended achieving the two characteristics above will provide large benefits in the coding process and final code.<br /> <br /> ==Draft Component/Card Set==<br /> <br /> * [[cisLunarFreighter CRC Card Initial Splashscreen, Launcher, Menu]]<br /> * [[cisLunarFreighter CRC Card Load and Mission Generator]]<br /> * [[cisLunarFreighter CRC Card Ship]]<br /> * [[cisLunarFreighter CRC Card Ship Designer]]<br /> * [[cisLunarFreighter CRC Card Personal Game Data]]<br /> * [[cisLunarFreighter CRC Card Terran Spaceport]]<br /> * [[cisLunarFreighter CRC Card Spacecraft Freight Load Planner]]<br /> * [[cisLunarFreighter CRC Card Planetary Takeoff or Lander Screen]]<br /> ::Terran, Lunar, Asteroid, or Saturn Pirate Base<br /> * [[cisLunarFreighter CRC Card Pilot's Cockpit Screen]]<br /> ::Mini Map Radar Overview, Cockpit Menu, Headsup Communicator<br /> * [[cisLunarFreighter CRC Card 2D Overview Asteroids or Meteor Shower Flythrough]]<br /> * [[cisLunarFreighter CRC Card Solar System Game Controller]]<br /> * [[cisLunarFreighter CRC Card User Keyboard Interface Controller]]<br /> * [[cisLunarFreighter CRC Card User Mouse Interface Controller]]<br /> * [[cisLunarFreighter CRC Card Background Music Selection and Player]]<br /> * [[cisLunarFreighter CRC Card Lunar Spaceport]]</div>

70.110.42.176 https://ideawaza.com/index.php?title=Archive:CisLunarFreighter/Requirement_analysis_and_high_level_design&diff=48292 2007-01-29T04:10:32Z

<p>70.110.42.176: fix formatting of card list</p> <hr /> <div>Object Oriented Software Engineering<br /> :Component, Responsibility, Collaborators (&lt;b&gt;CRC&lt;/b&gt;)Cards - 3&quot; X 5&quot; note cards<br /> ::Design, Code, or Case Scenario Walkthroughs<br /> <br /> This exercise is based loosely upon the technique demonstrated in Chapter One of Classic Data Structures in C++ by Timothy A. Budd, cp1994 by Addison-Wesley Publishing Company, Inc. In a local object orieted design project using C++ CRC (Component, Responsibility, Collaborating Objects) cards are used to jot down names and bullets outlining the high level components identified in walkthrough as required for the project design.<br /> <br /> The procedure we shall use here for asnychronous, distributed, walkthroughs is as follows: Individual files shall be created for proposed components. Responsibilities for that component jotted down in bullet form at the top of the screen, simulating a 3&quot; X 5&quot; note card. When another component is called a link will be created to that component. Actions the component must complete are list in the bottom half of the computer screen/file.<br /> <br /> For the highest level walkthough or design Budd designates the most important characteristics of potential design components as:<br /> 1. A small set of well defined responsibilities must result. If the component has too many responsibilities then it should be busted into multiple components and the walkthrough reaccomplished.<br /> 2. Interactions with other components should be minimalized to the greatest extent possible.<br /> <br /> Effort expended achieving the two characteristics above will provide large benefits in the coding process and final code.<br /> <br /> ==Draft Component/Card Set==<br /> <br /> * [[cisLunarFreighter CRC Card Initial Splashscreen, Launcher, Menu]]<br /> * [[cisLunarFreighter CRC Card Load and Mission Generator]]<br /> * [[cisLunarFreighter CRC Card Ship]]<br /> * [[cisLunarFreighter CRC Card Ship Designer]]<br /> * [[cisLunarFreighter CRC Card Personal Game Data]]<br /> * [[cisLunarFreighter CRC Card Terran Spaceport]]<br /> * [[cisLunarFreighter CRC Card Spacecraft Freight Load Planner]]<br /> * [[cisLunarFreighter CRC Card Planetary Takeoff or Lander Screen]]<br /> ::Terran, Lunar, Asteroid, or Saturn Pirate Base<br /> * [[cisLunarFreighter CRC Card Pilot's Cockpit Screen]]<br /> ::Mini Map Radar Overview, Cockpit Menu, Headsup Communicator<br /> * [[cisLunarFreighter CRC Card 2D Overview Asteroids or Meteor Shower Flythrough]]<br /> * [[cisLunarFreighter CRC Card Solar System Game Controller]]<br /> * [[cisLunarFreighter CRC Card User Keyboard Interface Controller]]<br /> * [[cisLunarFreighter CRC Card User Mouse Interface Controller]]<br /> * [[cisLunarFreighter CRC Card Background Music Selection and Player]]<br /> * [[cisLunarFreighter CRC Card Lunar Spaceport]]</div>

70.110.42.176 https://ideawaza.com/index.php?title=Archive:CisLunarFreighter/Requirement_analysis_and_high_level_design&diff=48291 2007-01-29T04:08:44Z

<p>70.110.42.176: Begin high level design process for cisLunarFreighter</p> <hr /> <div>Object Oriented Software Engineering<br /> :Component, Responsibility, Collaborators (&lt;b&gt;CRC&lt;/b&gt;)Cards - 3&quot; X 5&quot; note cards<br /> ::Design, Code, or Case Scenario Walkthroughs<br /> <br /> This exercise is based loosely upon the technique demonstrated in Chapter One of Classic Data Structures in C++ by Timothy A. Budd, cp1994 by Addison-Wesley Publishing Company, Inc. In a local object orieted design project using C++ CRC (Component, Responsibility, Collaborating Objects) cards are used to jot down names and bullets outlining the high level components identified in walkthrough as required for the project design.<br /> <br /> The procedure we shall use here for asnychronous, distributed, walkthroughs is as follows: Individual files shall be created for proposed components. Responsibilities for that component jotted down in bullet form at the top of the screen, simulating a 3&quot; X 5&quot; note card. When another component is called a link will be created to that component. Actions the component must complete are list in the bottom half of the computer screen/file.<br /> <br /> For the highest level walkthough or design Budd designates the most important characteristics of potential design components as:<br /> 1. A small set of well defined responsibilities must result. If the component has too many responsibilities then it should be busted into multiple components and the walkthrough reaccomplished.<br /> 2. Interactions with other components should be minimalized to the greatest extent possible.<br /> <br /> Effort expended achieving the two characteristics above will provide large benefits in the coding process and final code.<br /> <br /> Draft Component/Card Set<br /> <br /> [[cisLunarFreighter CRC Card Initial Splashscreen, Launcher, Menu]]<br /> [[cisLunarFreighter CRC Card Load and Mission Generator]]<br /> [[cisLunarFreighter CRC Card Ship]]<br /> [[cisLunarFreighter CRC Card Ship Designer]]<br /> [[cisLunarFreighter CRC Card Personal Game Data]]<br /> [[cisLunarFreighter CRC Card Terran Spaceport]]<br /> [[cisLunarFreighter CRC Card Spacecraft Freight Load Planner]]<br /> [[cisLunarFreighter CRC Card Planetary Takeoff or Lander Screen]]<br /> :Terran, Lunar, Asteroid, or Saturn Pirate Base<br /> [[cisLunarFreighter CRC Card Pilot's Cockpit Screen]]<br /> :Mini Map Radar Overview, Cockpit Menu, Headsup Communicator<br /> [[cisLunarFreighter CRC Card 2D Overview Asteroids or Meteor Shower Flythrough]]<br /> [[cisLunarFreighter CRC Card Solar System Game Controller]]<br /> [[cisLunarFreighter CRC Card User Keyboard Interface Controller]]<br /> [[cisLunarFreighter CRC Card User Mouse Interface Controller]]<br /> [[cisLunarFreighter CRC Card Background Music Selection and Player]]<br /> [[cisLunarFreighter CRC Card Lunar Spaceport]]</div>

70.110.42.176 https://ideawaza.com/index.php?title=Archive:CisLunarFreighter/Detailed_requirements_analysis&diff=48367 2007-01-29T03:26:02Z

<p>70.110.42.176: An exercise to shake out high level requirements and design</p> <hr /> <div>An overview of major requirements: What do we and the users want from a/the game?<br /> <br /> 1. Entertainment -- should be fun.<br /> *Hands on ship control against fairly realistic g fields is fun<br /> *Dodging debris and asteroids is fun<br /> *Blasting asteroids to mine for valuable ore or artifacts is fun<br /> *Working together as a team to accomplish some giant task is fun.<br /> *Communicating with online buddies<br /> <br /> 2. Social -- Interaction with other people via <br /> * chat -- most mud environments allow this<br /> * email -- useful or not?<br /> * game consequences -- makes the game more interesting<br /> ::Loads delivered begin to pile up or generate demand for missions. Player or others may undertake new missions.<br /> <br /> 3. Educational - Exposure to some science, engineering, and operations concepts<br /> ::Links to applicable background reading of various levels<br /> ::Internal math and reading requirements<br /> <br /> * Math practice - Examples<br /> :: Loading of feul and cargo mass vs. destination decisions in math assistance screen demonstrating use of spreadsheets in load balancing calculations with easy reference and reading showing sample problem solutions to control the center of mass. Java applet with sliders to allow easy selection for within specification loading.<br /> :: MalFunction might occasionally require mission abort or manual calculations.<br /> :: Misfortune (hijacked to Saturn by pirates) might require decisions about how much cargo to abandon or redistribute manually as feul.<br /> <br /> * Reading around the web<br /> * Use of open source tools for modding<br /> * Software design and coding techniques<br /> [[Category:Game Design]]<br /> <br /> 4. Reinforcement of Societal Norms<br /> <br /> *Aliens and Pirates are best avoided but blasting is ok for self defense. Self defense applies only if your ship has taken demonstrable damage from the other side of the battle.<br /> *Mistakes blasting other freighters results poor reputation, Space Patrol pursuit, and eventual game session loss or incarceration, ship lockdown.<br /> *Responding successfuly to distress signals can improve standing with police.<br /> *Mistakenly blasting a Space Patrol ship is not survivable since escalting levels of Space Patrol show up to capture or blast miscreants.<br /> <br /> <br /> [[cisLunarFreighter A Requirements Analysis and High Level Design Exercise]]</div>

70.110.42.176