1 / 31

Battleship Visualization

Team Members: Zhen Cai Christopher Campbell Justin Doll Jason Miller Nicholas Rimer Raeginald Timones. Group 2 : Team Battleship . Battleship Visualization. Reggie Timones. Concept of Operations. Current System. Battleship board game by Milton Bradley Physical board g ame

stash
Télécharger la présentation

Battleship Visualization

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Team Members: Zhen Cai Christopher Campbell Justin Doll Jason Miller Nicholas Rimer RaeginaldTimones Group 2 : Team Battleship Battleship Visualization

  2. Reggie Timones Concept of Operations

  3. Current System • Battleship board game by Milton Bradley • Physical board game • 2 human players

  4. Proposed System • Needs • User modes • Operational Scenarios • 1 player • 2 players

  5. Operational Features

  6. Analysis

  7. Nicholas Rimer and Zhen Cai Project Management Plan

  8. Project Plan

  9. Timeline

  10. Tools and Computing Environment • Programmed in the Java Environment • Will run on any operating system with Java installed

  11. Software Life Cycle • There will be one final version that will have a lifetime warranty • Extensive testing will be done to find any errors • If a fatal error is found after release a new version may be released

  12. Quality Assurance • Two Phases of testing • All members will conduct their own tests • Errors will be compiled and fixed

  13. Training Plan • The program will have a tutorial on how to play • A user manual will list all other properties of the software including a how to on running the program • No other specific training is required

  14. Security • No implemented security • The software's warranty will be void if the code is modified

  15. Risk Management • Extensive testing to reduce failures • New version releases over the internet to reduce the cost of failures

  16. Maintenance Plan • Maintenance will only be done given that fatal errors occur after the final release • A new version will be released

  17. Jason Miller and Justin Doll Software Requirements Specifications

  18. Product Overview • Assumptions • Java Runtime • Stakeholders

  19. Samples from Event Table

  20. Use Case Diagram

  21. Sample Specific Requirements

  22. Christopher Campbell Test PLan

  23. Objective of the Test Plan • Identify activities that will help produce an application with the following: • Usability • Acceptable Performance • Functionality • Complete our objective through the following • Creating test cases • Identifying errors, bugs, issues • Regression and unit testing

  24. Test Environment • Software • Any OS that supports the Java Runtime Environment (Windows, Mac OSX, Ubuntu) • Hardware • Any modern PC with at least 512 MB of RAM and at least 1.6 GHz Processor • Testers • Developers • Users

  25. Stopping Criteria • Issues found, issue ticket created on Google Code page • Issues are discussed as a team, prioritized then tested individually • Critical issues are deemed solved after extensive regression testing

  26. Testing Cycle

  27. Issue Priority

  28. Sample Test Cases

  29. Sample Test Cases

More Related