path---assignments-sprint-1-b7c04c909ff851b9c9e8.js.map

{"version":3,"sources":["webpack:///path---assignments-sprint-1-b7c04c909ff851b9c9e8.js","webpack:///./.cache/json/assignments-sprint-1.json"],"names":["webpackJsonp","341","module","exports","data","markdownRemark","html","frontmatter","path","title","pathContext"],"mappings":"AAAAA,cAAc,iBAERC,IACA,SAAUC,EAAQC,GCHxBD,EAAAC,SAAkBC,MAAQC,gBAAkBC,KAAA,4sKAAAC,aAAgvKC,KAAA,uBAAAC,MAAA,cAAmDC","file":"path---assignments-sprint-1-b7c04c909ff851b9c9e8.js","sourcesContent":["webpackJsonp([235015747780086],{\n\n/***/ 341:\n/***/ (function(module, exports) {\n\n\tmodule.exports = {\"data\":{\"markdownRemark\":{\"html\":\"<p><strong>DUE DATE: Friday, October 12, 5 PM</strong></p>\\n<p>For Sprint 1, you and your team are charged with creating a proof of concept demo of a card game called Battleships using the <a href=\\\"http://www.ninjaframework.org/\\\">Ninja Framework.</a></p>\\n<h1>Game Rules</h1>\\n<h2>Game Objective</h2>\\n<p>The object of Battleship is to try and sink all of the other player's before they sink all of your ships. All of the other player's ships are somewhere on his/her board.  You try and hit them by calling out the coordinates of one of the squares on the board.  The other player also tries to hit your ships by calling out coordinates.  Neither you nor the other player can see the other's board so you must try to guess where they are.  Each board in the physical game has two grids:  the lower (horizontal) section for the player's ships and the upper part (vertical during play) for recording the player's guesses.</p>\\n<h2>Starting a New Game</h2>\\n<p>Each player places the 3 ships somewhere on their board.  The ships can only be placed vertically or horizontally. Diagonal placement is not allowed. No part of a ship may hang off the edge of the board.  Ships may not overlap each other.  No ships may be placed on another ship.\\nOnce the guessing begins, the players may not move the ships.\\nThe 3 ships are:  Battleship (4), Cruiser (3) and Destroyer (2).  </p>\\n<h2>Playing the Game</h2>\\n<p>Player's take turns guessing by calling out the coordinates. The opponent responds with \\\"hit\\\" or \\\"miss\\\" as appropriate.  Both players should mark their board with pegs:  red for hit, white for miss. For example, if you call out F6 and your opponent does not have any ship located at F6, your opponent would respond with \\\"miss\\\". You record the miss F6 by placing a white peg on the lower part of your board at F6. Your opponent records the miss by placing. When all of the squares that one your ships occupies have been hit, the ship will be sunk. You should announce \\\"hit and sunk\\\". In the physical game, a red peg is placed on the top edge of the vertical board to indicate a sunk ship. As soon as all of one player's ships have been sunk, the game ends.</p>\\n<p>Your boss wants to know if it is possible to implement this game using the ninja framework.  You will have two weeks to implement this game. Since this is just a proof of concept, we will not be developing an extensive UI at this time.</p>\\n<h2>Requirements</h2>\\n<p>The complete requirements document can be found <a href=\\\"/docs/battleship-requirements.pdf\\\">here.</a></p>\\n<p>To complete this assignment, each group needs to do the following:</p>\\n<ol>\\n<li>\\n<p>Start the assignment from the GH classroom, at this <a href=\\\"https://classroom.github.com/g/y6LTfIcq\\\">link.</a> This will initialize the repo with the starter code.</p>\\n</li>\\n<li>\\n<p>Setup the project in IntelliJ IDEA. You can find resources on how to do that <a href=\\\"/resources\\\">here.</a></p>\\n</li>\\n<li>\\n<p>Turn the assignment into User Stories.\\nFrom the assignment, each team should turn the assignment into a series of user stories.  We will talk about them in class, but a good introduction to User Stories can be found <a href=\\\"http://www.subcide.com/articles/how-to-write-meaningful-user-stories/\\\">here.</a> Once you create your user stories, create a page on your Github Project wiki called “User Stories”, where you will record all the user stories. You must have a minimum of 4 user stories.</p>\\n</li>\\n<li>\\n<p>Decide on your definition of done. Record it on a wiki page called \\\"Definition of Done.\\\" You need to follow this definition everytime you finish a user story.</p>\\n</li>\\n<li>\\n<p>Create Tasks from User Stories.\\nFrom the user stories, each team will create a series of features that need to be implemented in the code. These will be added to the Github issue tracking system. Each of these must be assigned to a specific team member, as well as have a time estimate given in the body of the issue. The issues will be tagged with <code>feature</code>.</p>\\n</li>\\n<li>\\n<p>Create a new milestone, called <code>Sprint 1</code>, with the deadline being the assignment due date. As a team, decide on what you are going to implement this sprint, by adding the milestone to each relevant issue.</p>\\n</li>\\n<li>\\n<p>Each team member will then create a branch for each feature they are going to implement.  When the feature is completed, create a pull request (PR) to the <code>master</code> branch. Another team member has to review the changes. If they require any changes, implement the feedback and repeat the review cycle. Once the changes have been approved, merge the PR and close the issue. Follow the same process when you fix a bug. First, create an issue in the tracking system. Then, create a separate branch, and create a Pull Request (PR) when done, review and merge.</p>\\n</li>\\n<li>\\n<p>Tag the final version with <code>sprint-1</code>. Don’t forget to push the tags to GitHub, with <code>git push --tags</code>. <strong>This is the version we will grade!</strong></p>\\n</li>\\n<li>\\n<p>(Optional) Complete <a href=\\\"https://goo.gl/forms/jzvDOPanWHOMLjBq1\\\">this survey</a> to give feedback regarding your team member's contribution to the sprint. Complete one survey for each team member you would like to give feedback for.</p>\\n</li>\\n</ol>\",\"frontmatter\":{\"path\":\"/assignments/sprint1\",\"title\":\"Sprint 1\"}}},\"pathContext\":{}}\n\n/***/ })\n\n});\n\n\n// WEBPACK FOOTER //\n// path---assignments-sprint-1-b7c04c909ff851b9c9e8.js","module.exports = {\"data\":{\"markdownRemark\":{\"html\":\"<p><strong>DUE DATE: Friday, October 12, 5 PM</strong></p>\\n<p>For Sprint 1, you and your team are charged with creating a proof of concept demo of a card game called Battleships using the <a href=\\\"http://www.ninjaframework.org/\\\">Ninja Framework.</a></p>\\n<h1>Game Rules</h1>\\n<h2>Game Objective</h2>\\n<p>The object of Battleship is to try and sink all of the other player's before they sink all of your ships. All of the other player's ships are somewhere on his/her board.  You try and hit them by calling out the coordinates of one of the squares on the board.  The other player also tries to hit your ships by calling out coordinates.  Neither you nor the other player can see the other's board so you must try to guess where they are.  Each board in the physical game has two grids:  the lower (horizontal) section for the player's ships and the upper part (vertical during play) for recording the player's guesses.</p>\\n<h2>Starting a New Game</h2>\\n<p>Each player places the 3 ships somewhere on their board.  The ships can only be placed vertically or horizontally. Diagonal placement is not allowed. No part of a ship may hang off the edge of the board.  Ships may not overlap each other.  No ships may be placed on another ship.\\nOnce the guessing begins, the players may not move the ships.\\nThe 3 ships are:  Battleship (4), Cruiser (3) and Destroyer (2).  </p>\\n<h2>Playing the Game</h2>\\n<p>Player's take turns guessing by calling out the coordinates. The opponent responds with \\\"hit\\\" or \\\"miss\\\" as appropriate.  Both players should mark their board with pegs:  red for hit, white for miss. For example, if you call out F6 and your opponent does not have any ship located at F6, your opponent would respond with \\\"miss\\\". You record the miss F6 by placing a white peg on the lower part of your board at F6. Your opponent records the miss by placing. When all of the squares that one your ships occupies have been hit, the ship will be sunk. You should announce \\\"hit and sunk\\\". In the physical game, a red peg is placed on the top edge of the vertical board to indicate a sunk ship. As soon as all of one player's ships have been sunk, the game ends.</p>\\n<p>Your boss wants to know if it is possible to implement this game using the ninja framework.  You will have two weeks to implement this game. Since this is just a proof of concept, we will not be developing an extensive UI at this time.</p>\\n<h2>Requirements</h2>\\n<p>The complete requirements document can be found <a href=\\\"/docs/battleship-requirements.pdf\\\">here.</a></p>\\n<p>To complete this assignment, each group needs to do the following:</p>\\n<ol>\\n<li>\\n<p>Start the assignment from the GH classroom, at this <a href=\\\"https://classroom.github.com/g/y6LTfIcq\\\">link.</a> This will initialize the repo with the starter code.</p>\\n</li>\\n<li>\\n<p>Setup the project in IntelliJ IDEA. You can find resources on how to do that <a href=\\\"/resources\\\">here.</a></p>\\n</li>\\n<li>\\n<p>Turn the assignment into User Stories.\\nFrom the assignment, each team should turn the assignment into a series of user stories.  We will talk about them in class, but a good introduction to User Stories can be found <a href=\\\"http://www.subcide.com/articles/how-to-write-meaningful-user-stories/\\\">here.</a> Once you create your user stories, create a page on your Github Project wiki called “User Stories”, where you will record all the user stories. You must have a minimum of 4 user stories.</p>\\n</li>\\n<li>\\n<p>Decide on your definition of done. Record it on a wiki page called \\\"Definition of Done.\\\" You need to follow this definition everytime you finish a user story.</p>\\n</li>\\n<li>\\n<p>Create Tasks from User Stories.\\nFrom the user stories, each team will create a series of features that need to be implemented in the code. These will be added to the Github issue tracking system. Each of these must be assigned to a specific team member, as well as have a time estimate given in the body of the issue. The issues will be tagged with <code>feature</code>.</p>\\n</li>\\n<li>\\n<p>Create a new milestone, called <code>Sprint 1</code>, with the deadline being the assignment due date. As a team, decide on what you are going to implement this sprint, by adding the milestone to each relevant issue.</p>\\n</li>\\n<li>\\n<p>Each team member will then create a branch for each feature they are going to implement.  When the feature is completed, create a pull request (PR) to the <code>master</code> branch. Another team member has to review the changes. If they require any changes, implement the feedback and repeat the review cycle. Once the changes have been approved, merge the PR and close the issue. Follow the same process when you fix a bug. First, create an issue in the tracking system. Then, create a separate branch, and create a Pull Request (PR) when done, review and merge.</p>\\n</li>\\n<li>\\n<p>Tag the final version with <code>sprint-1</code>. Don’t forget to push the tags to GitHub, with <code>git push --tags</code>. <strong>This is the version we will grade!</strong></p>\\n</li>\\n<li>\\n<p>(Optional) Complete <a href=\\\"https://goo.gl/forms/jzvDOPanWHOMLjBq1\\\">this survey</a> to give feedback regarding your team member's contribution to the sprint. Complete one survey for each team member you would like to give feedback for.</p>\\n</li>\\n</ol>\",\"frontmatter\":{\"path\":\"/assignments/sprint1\",\"title\":\"Sprint 1\"}}},\"pathContext\":{}}\n\n\n//////////////////\n// WEBPACK FOOTER\n// ./~/json-loader!./.cache/json/assignments-sprint-1.json\n// module id = 341\n// module chunks = 235015747780086"],"sourceRoot":""}