1 / 11

Project Presentation (II) - Architecture Design

Project Presentation (II) - Architecture Design. Alexandre Martins – SQA Rodrigo Mendes - Software Architect Project: Starship. Summary. Planning Phase Activities Game State Machine Game Architecture Metrics Strong and Weak Points Learned Lessons References.

dillon
Télécharger la présentation

Project Presentation (II) - Architecture Design

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. Project Presentation (II) - Architecture Design Alexandre Martins – SQA Rodrigo Mendes - Software Architect Project: Starship

  2. Summary • Planning Phase Activities • Game State Machine • Game Architecture • Metrics • Strong and Weak Points • Learned Lessons • References

  3. Planning Phase Activities • New Activities: • Architecture Design • To Specify: • The Modules • The Classes • The Components • To Apply Design Patterns: • Gama • GRASP • To use the [2] approach • Guidelines

  4. Game State Machine

  5. Game Architecture

  6. Metrics • SPM - Effort

  7. Metrics • Time Foresight X Done

  8. Strong and Weak Points • Strong Points • Coherent and well defined division of the activities; • Software Architect experience in Games Domain • Reuse of OXE’s templates[1]; • Reuse of information from other teams; • Weak Points • How to build a general architecture for SPL?; • The [2] specify “examples” or “how to do” a few turns.

  9. Learned Lessons • Was not easy to guide the architecture developer by the article[2]. • Module Composition? • What is the module granularity? • Choose Patterns • What are the patterns that must can be used? Gamma or Grasp? Only “Bass” is cited, but where can to find them? • Measuring functional dependency • The game have one game only, thus, some calculus were not used. • Clustering • Should to explain how apply clustering algorithm • Allocating Classes to Components • The coupling and cohesion parts are for be equal eith the Use Case coupling?

  10. References • [1] IXI Process; • [2] An Approach for Domain Design Based on Component-Based Development;

More Related