Extração de Features Usando Compilação Condicional
•
1 gostou•820 visualizações
Monografia apresentada por Camilo Ribeiro como requisito parcial para a obtenção do título de Especialista em Engenharia de Software pela Universidade Federal de Minas Gerais
![Camilo Falcão Ribeiro Figueiredo [email_address] Prof. Dr. Marco Túlio de Oliveira Valente [email_address] EXTRAÇÃO DE FEATURES USANDO COMPILAÇÃO CONDICIONAL Engenharia de Software – DCC/UFMG – Brasil](https://image.slidesharecdn.com/monografiacei-es-2010camiloribeiro-100804203208-phpapp01/85/Extracao-de-Features-Usando-Compilacao-Condicional-1-320.jpg)
![SUMÁRIO (1/1) ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],Extração de Features Usando Compilação Condicional](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recomendados
Mais conteúdo relacionado
Destaque
Destaque (20)
Semelhante a Extração de Features Usando Compilação Condicional
Semelhante a Extração de Features Usando Compilação Condicional (20)
Mais de Camilo Ribeiro
Mais de Camilo Ribeiro (12)
Último
Último (6)
Extração de Features Usando Compilação Condicional
- 1. Camilo Falcão Ribeiro Figueiredo [email_address] Prof. Dr. Marco Túlio de Oliveira Valente [email_address] EXTRAÇÃO DE FEATURES USANDO COMPILAÇÃO CONDICIONAL Engenharia de Software – DCC/UFMG – Brasil
- 19. AVALIAÇÃO (3/5) Extração de Features Usando Compilação Condicional Transversalidade entre as features . Tabela: Métricas de Transversalidade do ArgoUML-SPL com as duas novas features. Fonte: Arquivo pessoal 0 0 Diagrama de Caso de Uso + Diagrama de Sequência 0 0 Diagrama de Estados + Diagrama de Caso de Uso 0 2 Diagrama de Estados + Diagrama de Sequência 11 26 Diagrama de Atividades + Diagrama de Estados 3 3 Diagrama de Atividades + Diagrama de Sequência 0 0 Diagrama de Atividades + Diagrama de Casos de uso 30 0 Diagrama de Caso de Uso + Logging 35 0 Diagrama de Sequência + Logging 30 0 Diagrama de Estados + Logging 9 0 Diagrama de Atividades + Logging 171 0 Suporte Cognitivo + Logging Aninhamento Entrelaçamento Features envolvidas
- 20. AVALIAÇÃO (4/5) Extração de Features Usando Compilação Condicional Granularidade das features . Tabela: Granularidade do código anotado para cada feature . Fonte: Arquivo pessoal 85,12% 1154 72 53 41 77 56 Statement 1,35% 14 0 0 0 4 5 MethodBody 2,52% 3 5 7 10 8 10 Method 0,18% 0 0 0 0 2 1 InterfaceMethod Use 0,12% 0 0 0 0 0 2 ClassSignature 10,02% 0 40 47 41 35 8 Class 0,70% 0 0 1 0 0 11 Package Implements % Logging Diag. De C. Uso Diag. De Sequ. Diag. De estado Diag. De Ativ. Suporte Cognitivo Features
- 21. AVALIAÇÃO (5/5) Extração de Features Usando Compilação Condicional Localização das features. Tabela: Tipo de localização do código anotado para cada feature Fonte: Arquivo pessoal 387 1 3 3 6 9 NestedCommand 0 0 0 0 0 2 InsideStaticBlock 1 0 0 0 0 0 EntireStaticBlock 1 0 0 0 0 0 EndStaticBlock 99 0 0 1 0 0 BeforeReturn 13 0 0 0 4 5 EntireMethod 23 0 0 0 1 5 EndMethod 138 1 2 1 1 3 StartMethod Logging Diag. De C. Uso Diag. De Sequ. Diag. De estado Diag. De Ativ. Suporte Cognitivo Tipo de Localização Features
- 22. CONCLUSÃO (1/1) Extração de Features Usando Compilação Condicional A adoção de compilação condicional para implementação de Linhas de Produtos de Software, apesar de possuir algumas desvantagens como dependência de tecnologias alternativas, aumento da complexidade do código fonte e difícil definição do escopo, demonstra-se como uma boa candidata para a implementação em sistemas legados desenvolvidos sem uma metodologia que suporte a criação de Linhas de Produtos de Software. Isso se deve a facilidade de implementação das marcações e da independência de padrões de desenvolvimento.
- 25. www.dcc.ufmg.br/~camilo www.camiloribeiro.com Perguntas??? Muito Obrigado!!! Engenharia de Software – DCC/UFMG – Brasil
Notas do Editor
- Good afternoon... My name is Ricardo Terra and I'm from PUC Minas at Brazil. I'm going to present a paper named "Towards a Dependency Constraint Language to Manage Software Architectures".
- First, I would like to briefly introduce the subject of this study. However, we have a recurrent problem in forcing architecture compliance: - The document architecture of a system – if available at all – doesn't reflect the implemented architecture
- First, I would like to briefly introduce the subject of this study. However, we have a recurrent problem in forcing architecture compliance: - The document architecture of a system – if available at all – doesn't reflect the implemented architecture
- First, I would like to briefly introduce the subject of this study. However, we have a recurrent problem in forcing architecture compliance: - The document architecture of a system – if available at all – doesn't reflect the implemented architecture
- First, I would like to briefly introduce the subject of this study. However, we have a recurrent problem in forcing architecture compliance: - The document architecture of a system – if available at all – doesn't reflect the implemented architecture
- First, I would like to briefly introduce the subject of this study. However, we have a recurrent problem in forcing architecture compliance: - The document architecture of a system – if available at all – doesn't reflect the implemented architecture
- First, I would like to briefly introduce the subject of this study. However, we have a recurrent problem in forcing architecture compliance: - The document architecture of a system – if available at all – doesn't reflect the implemented architecture
- First, I would like to briefly introduce the subject of this study. However, we have a recurrent problem in forcing architecture compliance: - The document architecture of a system – if available at all – doesn't reflect the implemented architecture
- First, I would like to briefly introduce the subject of this study. However, we have a recurrent problem in forcing architecture compliance: - The document architecture of a system – if available at all – doesn't reflect the implemented architecture
- First, I would like to briefly introduce the subject of this study. However, we have a recurrent problem in forcing architecture compliance: - The document architecture of a system – if available at all – doesn't reflect the implemented architecture
- First, I would like to briefly introduce the subject of this study. However, we have a recurrent problem in forcing architecture compliance: - The document architecture of a system – if available at all – doesn't reflect the implemented architecture
- First, I would like to briefly introduce the subject of this study. However, we have a recurrent problem in forcing architecture compliance: - The document architecture of a system – if available at all – doesn't reflect the implemented architecture
- First, I would like to briefly introduce the subject of this study. However, we have a recurrent problem in forcing architecture compliance: - The document architecture of a system – if available at all – doesn't reflect the implemented architecture
- First, I would like to briefly introduce the subject of this study. However, we have a recurrent problem in forcing architecture compliance: - The document architecture of a system – if available at all – doesn't reflect the implemented architecture
- First, I would like to briefly introduce the subject of this study. However, we have a recurrent problem in forcing architecture compliance: - The document architecture of a system – if available at all – doesn't reflect the implemented architecture
- First, I would like to briefly introduce the subject of this study. However, we have a recurrent problem in forcing architecture compliance: - The document architecture of a system – if available at all – doesn't reflect the implemented architecture
- First, I would like to briefly introduce the subject of this study. However, we have a recurrent problem in forcing architecture compliance: - The document architecture of a system – if available at all – doesn't reflect the implemented architecture
- First, I would like to briefly introduce the subject of this study. However, we have a recurrent problem in forcing architecture compliance: - The document architecture of a system – if available at all – doesn't reflect the implemented architecture
- First, I would like to briefly introduce the subject of this study. However, we have a recurrent problem in forcing architecture compliance: - The document architecture of a system – if available at all – doesn't reflect the implemented architecture
- First, I would like to briefly introduce the subject of this study. However, we have a recurrent problem in forcing architecture compliance: - The document architecture of a system – if available at all – doesn't reflect the implemented architecture
- First, I would like to briefly introduce the subject of this study. However, we have a recurrent problem in forcing architecture compliance: - The document architecture of a system – if available at all – doesn't reflect the implemented architecture
- First, I would like to briefly introduce the subject of this study. However, we have a recurrent problem in forcing architecture compliance: - The document architecture of a system – if available at all – doesn't reflect the implemented architecture
- First, I would like to briefly introduce the subject of this study. However, we have a recurrent problem in forcing architecture compliance: - The document architecture of a system – if available at all – doesn't reflect the implemented architecture
- First, I would like to briefly introduce the subject of this study. However, we have a recurrent problem in forcing architecture compliance: - The document architecture of a system – if available at all – doesn't reflect the implemented architecture
- I would like to thank you all... Thanks a lot.