fthts
commented
8 years ago CS319 Analysis Report - Revised V1.docx
- Unnecessary level design has been fixed - Overview
- Dots have been used instead of numbering for pointing subheads - Gameplay Elements
- Spelling error has been fixed - Miscellaneous
- Grammatically incorrect statement has been fixed in Functional Requirements - Play Game
- Unnecessary itemization has been fixed - System Models
- The flow is between the player and the system - Use Case Model / Change Settings/Successful Scenario Event Flow
- Successful scenario event flow has been fixed - Use Case Model / Display Instructions
- Added introduction to diagram - Figure 1 (Use Case Diagram)
- Missing caption has been fixed - Figure 1 (Use Case Diagram)
- Sequence diagrams have been fixed, class names and user type have been corrected, method names have been corrected, and diagrams have been made more readable. - Dynamic Models / Scenario 1
- Update method has been described on the Figure 2.2 by adding a new explanation - Dynamic Models / Scenario 1
- CollisionGrid and EntityGrid has been explained, notation for destruction of an object has been fixed into the sequence diagrams - Dynamic Models / Scenario 3
- DependentObject has been explained below the Figure 2.5 - Dynamic Models / Scenario 5
- Figure has been made more readable - Dynamic Models / Scenario 5 / Figure 2.5
- Use of synchronization has been corrected - Dynamic Models / Figure 3
- Wait for user input” has been fixed - Dynamic Models / Figure 3
- Decision after “Check for User Mouse Input” has been fixed - Dynamic Models / Figure 3
- Initialization step (“InitializeGame”) has been corrected - Dynamic Models / Figure 3
- Unnecessary “1” multiplicities have been removed - Object and Class Models / Figure 4
- Role names have been fixed - Object and Class Models / Figure 4
- Starting point has been added - User Interface-Navigational Paths and Mock up Screens / Figure 5
- Some arrows have been changed from one side to the two side in order to stop confusion - User Interface-Navigational Paths and Mock up Screens / Figure 5
6.analysis.docx