1 / 23

SOLO TEST MOBILE GAME PROJECT

SOLO TEST MOBILE GAME PROJECT. M . Fatih Akbulut Gokberk Ergun Melim Guler Mahmut Subasi Tuna Toksoz Yigit Yildirim. Table of Contents. The Project Game Space - Solo Test Android Mobile Game Goals Software Development Methodology Software Model Design Decisions Architecture

quang
Download Presentation

SOLO TEST MOBILE GAME PROJECT

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. SOLO TEST MOBILE GAME PROJECT M.FatihAkbulut Gokberk Ergun MelimGuler MahmutSubasi Tuna Toksoz YigitYildirim

  2. Table of Contents • The Project • Game Space - Solo Test Android Mobile Game • Goals • Software Development Methodology • Software Model • Design Decisions • Architecture • 3 - Tier Architecture • The End Product • Functionality • Testing • Quality • Lessons Learned

  3. Game Space – Solo Test Android Mobile Game • The Need • Entertainment Purposes • Brain Training • The Solution - A system for • Simulating the real peg solitaire game • The Set-up • Global Software Development • Remote Customer • In conjunction with Software Engineering Course

  4. Goals • Our Objective • Customer Satisfaction • Quality • Product • Process

  5. OurModel • The Spiral Model • Abstract Specifications • Refine With Customer Input • Documentation • Project Plan • 3 Calendar Months & 2 Man Months • Documentation • Multiple Version of Documents: RAD, ODD, SDD, Test Document, Database Design Document, IUM, Standards Security and Quality Document

  6. Critical Design Decisions • Simple and user-friendly GUI • Scalability • Abstraction of database operations • Compatibility with core issues • Conformity of Software Product Line

  7. Architecture • Presentation Tier • GUI • Bussiness Tier • Game Logic • Calculations • Database Operations • Database Tier • DB Tables

  8. The Game Process

  9. The Game Process

  10. The Game Process

  11. The Game Process

  12. The Game Process

  13. The Game Process

  14. The Game Process

  15. Unique Features Of Our Game • Easy and Medium Configuration Types

  16. Game Ending Conditions • Only one peg left on the board • There no possible move • The user presses the home button

  17. Algorithms • Score Calculation Algorithm • Calculates the score according to time and pegs left • Move Validation Algorithm • Checks the possible moves of the selected peg • Game Finish Check Algorithm • Checks whether there is possible move

  18. Testing • Automated Unit Testing • Performed by coders based on test cases by using Eclipse • Integration Testing • Code reviews by independent test team • Testing for non-functional requirements

  19. Measurement And Product Quality • The Tool • PREST 1 2 • Tool by SoftLab • Static code metrics extraction and analysis based on NASA code standarts 1 E. Kocaguneli, A. Tosun, A. Bener, B. Turhan, B. Caglayan, Prest: An Intelligent Metrics Extraction, Analysis and Defect Prediction Tool, in proceedings of SEKE 2009. 2 http://code.google.com/p/prest/

  20. Measurement And Product Quality • Measurements • Raw code analysis of our software product using PREST • Standart Range: • Level • Structural Complexity • Below the Standart Range: • Volume • Total operators and operands • Difficulty • Time • Cyclomatic Complexity • Unique operands and operators • Vocabulary • Effort

  21. Process Quality • Measurement and Monitoring • Repeatable Processes • Defined Processes B. Turhan and A. Bener, ”A Template for Real World Team Projects for Highly Populated Software Engineering Classes”, in Proceedings of the 29th International Conference on Software Engineering (ICSE 2007), pp. 748-753, 2007

  22. Lessons • Team Work • Software Product Line • Non-functional requirements • Software Development Process Maturity and Measurement

  23. Questions

More Related