Scope Statement for Group 10

Game of the Amazons

The software to be developed is inspired by the Game of the Amazons board game, with four queens to both players, of which move before firing an arrow that obstructs tiles. In short, the objective is to block off the movement of the opponents teams, and the game concludes whenever someone can no longer move any of their queens. This task requires the game to check many conditions before and after moves are made.

As follows, this is the scope of the aforementioned project:

• The application will be programmed in C#, and therefore should be able to operate on Windows platforms with the .NET framework.
• It functions as a standalone application without any network functionality.
• The application will support two player local play and player vs AI. The mouse should be implemented as a control that allows characters to select pieces and direct them to move or fire an arrow. The AI should at minimum should be able to move and fire arrows according to the rules.
• The application will consist of a GUI that allows a user to interact with it without need of a console. This includes a menu that allows players to start the game, designate game mode, and forfeit games, as well as a window that displays the grid in which the game takes place (10x10 grid).

Teams note:

These are the ideas that were pitched, ranked in order of most preferred to least:

1. Game of the Amazons
2. Text-based Adventure

While I don't expect you to have to get very detailed, you can see what the requirements involve right here in the deliverables file. It's the first thing listed under the Programmer's Manual. But to give it short requirements have the following sections: 1. Introduction - This contains the scope statement that we made, definitions/acronyms/abbreviations of terms we use, references to copyrighted material we used. 2. General Description - A paragraph describing why we're making the game and why it is useful (like, a paragraph that rattles on it being fun and such), product functions, user characteristics (essentially who will be using the game), limitations of our software (we aren't making an online game, so no network compatibility for example), dependencies that a user needs in order to play (.NET framework and windows probably, for a C# game) 3. Specific Requirements - Pretty much what the requirements are for the game. Think a list of rules in how the game operates. In terms of our game that pretty much means the rules and how the game is expected to function. (4 queens to each player, and each must move and fire an arrow to pass their turn, as a example) 4. Appendices - We probably won't need any of these, unless we feel it's necessary. You can ignore this one. 5. Index - We also probably won't use this one since indexes aren't very necessary and time consuming. I attached the scope statement that I updated for C# and the dependencies document. Don't sweat it too hard, we can refine the document together as time goes on together. The biggest thing will probably be Specific Requirements since that'll involve how we want the menus to work and how the game operates, but since the game has a relatively simple premise it should be fine- though there are a lot of conditions to check for once we get into programming- Like, for example, when someone's turn starts, we need to check if any of their queens can move. If not, they loose. If they can, let them move a queen, and fire an arrow (they should be able to fire an arrow if they were able to move, so we may not have to check for that) Another thing might be checking if they're allowed to move into a selected space (can't move into or past other queens/arrows) It's a bunch of jargon but the specific requirements will help us figure out how we want to structure our game. Again you probably won't have to be too detailed, it's mostly the rules of the game and what a player can do, it's not pseudocode.

what i need for you is to come up with the first three parts for me detailed: Introduction, General Description andSpecific requirements. Write it like in microsoft word.Word would probably be the best option, or you can use google docs. Either should work and they're compatible with each other, that way you can set up headers and tailor the font a little to make it easier to read.