IBM Technical Summit 2013 - Desenvolvimento e Qualidade
Download as PPT, PDF1 like689 views
The document discusses IBM's approach to software development, emphasizing the importance of quality, particularly in the context of Agile methodologies and technical debt. It warns that IBM's statements regarding future products and performance are subject to change and should not be relied upon for purchasing decisions. Additionally, it highlights how cloud technologies affect development processes and the need for careful architectural management to avoid complications in code implementation.
IBM Technical Summit 2013 - Desenvolvimento e Qualidade
- 1. Receita da Qualidade Gustavo Grillo IT Specialist, IBM Rational ggrillo@br.ibm.com © 2013 IBM Corporation
- 2. Please note the following IBM’s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM’s sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remains at our sole discretion. Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will experience will vary depending upon many factors, including considerations such as the amount of multiprogramming in the user’s job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve results similar to those stated here. 2
- 3. Agile é para mim? Imagem: the table xi blog (http://www.tablexi.com/) 3
- 4. Agilidade em escala Continuous Improvement Framework (CIF™) 4
- 5. Débito técnico Metáfora para as consequêncis de um código mal desenvolvido ou sem uma boa arquitetura Toda vez que implantamos novo código em uma arquitetura evolutiva, adcionamos complexidade e deterioramos a estrutura – a menos que seja feito um trabalho para manter a arquitetura. 5
- 6. Enxergando o débito técnico 6
- 7. Só que não escala… 7
- 8. O Que é Qualidade? Processo? Testes? Aderência? 8 Produto?
- 9. Dá pra desenvolver sem qualidade? X 9
- 10. Teste de software: Modelo V Testes baseados na forma de construir Cascata Não é priorizado por risco ou TCO Architecture System Test ce Muito focados no software e não no negócio, nem sempre Acceptance Test ur an Requirements Design Integration Test As s Costuma gerar centenas ou milhares de casos pm Qu ali ty lo ve De t en Build Unit Test
- 11. Verificação de processos de negócio Testes baseados na forma como o software é usado Regras e interações de negócio são usadas para construir os casos Regras de redução geram poucas centenas de casos que cobrem 70% - 80% dos processos críticos de negócio Foca nos maiores riscos de negócio e na diminuição do TCO
- 12. Como a Nuvem afeta o desenvolvimento?
- 13. Como a Nuvem afeta o desenvolvimento? http://www.eclipse.org/orion/
- 14. Virtualização Developers & Testers Rational Test Workbench Rational Performance Test Server App Under Test Databases Mainframe applications Third-party Services Packaged apps, messaging services, etc. Rational Test Virtualization Server 14
- 15. Shift Left 15
- 16. Learning Circles Google: Google: Agile Learning Circle Integration Testing Learning Circle 17
- 17. 19
- 18. © Copyright IBM Corporation 2013. All rights reserved. The information contained in these materials is provided for informational purposes only, and is provided AS IS without warranty of any kind, express or implied. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, these materials. Nothing contained in these materials is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software. References in these materials to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product release dates and/or capabilities referenced in these materials may change at any time at IBM’s sole discretion based on market opportunities or other factors, and are not intended to be a commitment to future product or feature availability in any way. IBM, the IBM logo, Rational, the Rational logo, Telelogic, the Telelogic logo, and other IBM products and services are trademarks of the International Business Machines Corporation, in the United States, other countries or both. Other company, product, or service names may be trademarks or service marks of others. 21
Editor's Notes
- #2: Author Notes: This is the PowerPoint template for the IBM Technical Summit breakout sessions This template has been built in PowerPoint 2003. If you’re using PowerPoint 2007 or above, you may experience different usability results than what is provided as guidance here. To allow all masters of your exiting presentation to be updated correctly, download this template to your hard drive and copy your existing slides into the new template using slide sorter. IBMers can find additional information on presentation guidelines and resources at:https://w3-connections.ibm.com/wikis/home?lang=en-us#!/wiki/Rational%20Presentation%20Templates,%20Guidelines,%20and%20Resources IBM Rational presenters can leverage existing brand-level assets and sparklers (including Rational Brand Messaging Slides, Client Success Slides and Client Quotes, Statistics) from SSW’s Brand Content Page:https://w3-03.sso.ibm.com/software/xl/myportal/content?synKey=R789607U42052O71 Imagery guidelines: Avoid using cartoon like clip-art, use photo-art instead. Third party material cannot be used in a presentation without written permission (this includes product and Web page screen shots, and photos). Images must be acquired from a ‘royalty-free to use’ source such as: Microsoft or Lotus Symphony Clip Art library http://www.freebyte.com/clipart_images_photos_icons/#freevectorgraphics http://www.freedigitalphotos.net/ IBMers can use royalty-free images from the following repositories: IBM Brand Systems Center / Assets / PhotographyLogin instructions: https://w3-connections.ibm.com/forums/html/topic?id=c1082624-e54c-4e04-bad1-ddb150ac7540 IBM Software Story Imageshttps://w3-connections.ibm.com/files/app#/collection/b7570645-b2f8-4450-a27f-9269a163fc2d IBM Rational Presentation Image Library: https://w3-connections.ibm.com/wikis/home?lang=en_US#!/wiki/Rational%20Presentation%20Templates,%20Guidelines,%20and%20Resources/page/Presentation%20Image%20Library
- #3: Please note the following IBMers must include the next slide (verbatim) after your title slide. IBMers must also include the mandatory “Acknowledgements and Disclaimers” slide (see slide 10) at the end of your presentation before the closing “Thank You” slide. - You will need to customize the “Acknowledgements and Disclaimers” text in red appropriately.
- #4: Não é mais opcional Não é revolução do proletariado, é a nova engenharia de software Qtos já usam Ágil? Cedo ou tarde vai acontecer
- #5: Como escalar agilidade é a nova pergunta SAFe – Algumas práticas ‘prescritivas’, adaptável, alinhamento entre os diversos níveis DAD – goal-driven, foco em arquitetura, divisão por fases Kanban – evolução incremental, baseado em métricas acionáveis Mais importante do que qual framework é como será feita a transformação (exemplo do RUP, medo de falar de RUP em conferencias de agile)
- #6: Um outro impedimento para a escalabilidade Vira custo de propriedade Fica escondido nos prazos, custos e qualidade esperada É preciso visualizar o DT para atacá-lo (assim como tudo=princípio ágil)
- #7: Se o DT não for identificado e combatido, nenhuma implantação ágil escala
- #8: Tecnologias antigas, proprietárias e fechadas acabam virando DT O custo do débito técnico normalmente fica escondido, disfarçado como custo normal de operação, embutido nas estimativas, prazos e desculpas
- #9: Questão filosófico – Metodologista Mudar papel das áreas de metodologia – responsáveis pelo sucesso dos projetos Pode ser um pouco de cada coisa. A importância de cada item depende do contexto
- #10: O que é qualidade para Farma e para Apps mobile?
- #11: Testes baseados na forma de construir Cascata Costuma gerar centenas ou milhares de casos Muito focados no software e não no negócio, nem sempre Não é priorizado por risco ou TCO
- #12: Testes baseados na forma como o software é usado Regras e interações de negócio são usadas para construir os casos Regras de redução geram poucas centenas de casos que cobrem 70% - 80% dos processos críticos de negócio Foca nos maiores riscos de negócio e na diminuição do TCO
- #13: Quem já usa nuvem para alguma parte do desenvolvimento? Jazz hub – ger. de projetos gratuito com tecnologia Jazz Integra com GitHub
- #14: Eclipse Orion: IDE na nuvem
- #15: História de testes na Crivo Muitos serviços que usávamos não estavam sempre no ar Alguns bloqueavam após vários acesso do mesmo IP Teste às cegas Explicar virtualização É parte do conceito de Shift Left
- #16: Traz mais recursos de teste e simulação para o desenvolvedor Agiliza a descoberta de problemas, não só de bugs Época incrível para ser desenvolvedor
- #17: Statistics: We have a fairly large deployment. We are definitely enterprise level in terms of numbers of users, and a moderately large sized data envrionment. Deployment Characteristics: We have one team administering our entire deployment of RQM (and all jazz based products). All our RQM servers are hosted in one location. The teams that use the deployment are globally distributed and we have a true WAN experience. We are constantly upgrading our OS, application server, and DB. We also even switch platforms to broaden our understanding of customer experience. For example, we went form AIX to Redhat for the application server. We went from a physical to a virtualized environment.
- #20: Optional slide. Graphic is available in English only.
- #21: Mandatory closing slide (1 of 2) Acknowledgements and disclaimers IBMers must include This mandatory “Acknowledgements and Disclaimers” slide at the end of your presentation before the closing “Thank You” slide. - You will need to customize the “Acknowledgements and Disclaimers” text in red appropriately.
- #22: Mandatory closing slide (2 of 2) Thank You Slide (available in English only).