Software IMprovement using Product LinEs Project Presentation (III) - Implementation Liana Lisboa – PM Project: Starship

2 Summary Components OSGi Tests Metrics Strong and Weak Points

3 Components New definition of components  Audio  Actions  Entity  Event  Graphic  Movement  Screen  New component -> Strategies

4 Components (cont.) Actual stage:  Audio  Events  Graphic  Movement  Strategies  Level Demonstration!

5 OSGi 2 Components with OSGi  Audio -> the factory pattern was ignored  Movement A sample example of these components in an application

6 Tests Issues:  Implementation is not totally finished (de-coupling);  It is not hard to validate a component contract if you have: Proper component specification; A process to validate then; Tools to support the activity.  But, it is hard to create automated tests for components that have basically user interaction (i.e. audio, image quality...)  Ideally, the component must come with a test bed for anyone who wants to see if that component fulfills its own acceptance criteria.

7 Tests Practice (applied to Movement component): JUnit to validate contract using mock objects; JUnitPerf for performance measuring; Weak Points (tests)  Integration Tests Strong Points (tests)  It is possible to test components

8 Metrics SPM - Effort

9 Metrics Time Foresight X Done DoneForesight 77:19:0067:10:00 Construction #3 Gerenciar Projeto1:00:00 Gerenciar Processo6:55:00 Gerenciar Requisitos0:00:00 Gerenciar Configuração0:00:00 Planejar Testes0:00:00 Gerenciar Arquitetura0:00:00 Implementar Componentes69:24:00 Acompanhar Projeto0:00:00

10 Strong and Weak Points Strong  Architecture well defined  Team commitment Weak  Lack of experience with components and OSGi