Решения IBM Rational на базе Software Delivery Platform и Jazz
•
0 likes•561 views
http://cmcons.com http://ibm.com Решения IBM Rational на базе Software Delivery Platform и Jazz семинар 15 июня 2010 года - «ПРОГРАММНОЕ ОБЕСПЕЧЕНИЕ IBM RATIONAL ДЛЯ УЛУЧШЕНИЯ ПРОЦЕССОВ РАЗРАБОТКИ И СОПРОВОЖДЕНИЯ ПО»
![Содержание ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
Recommended
More Related Content
Viewers also liked
Viewers also liked (15)
More from Alexander Novichkov
More from Alexander Novichkov (20)
Решения IBM Rational на базе Software Delivery Platform и Jazz
- 1. Решения IBM Rational на базе Software Delivery Platform и Jazz Дмитрий Лапыгин технический специалист по продуктам IBM Rational , IBM EE/A email: dmitry_lapygin@ru.ibm.com
- 5. RSA - RequisitePro интеграция – до кода Model explorer Package explorer Requirements explorer RequisitePro трассировка – от Требования до java кода Трассировка выбранного требования Перенос ! Перенос !
- 7. Управление изменениями и релизами Эксплуатация Хранилище версий Артефакты сборки Реализация Сборка Настройка серверов Функциональное тестирование Утверждение Ошибки Нагрузочное тестирование Производство E-SIG Разработчик Инженер сборки Менеджер развертывания Тестировщик Руководитель
- 20. Технология Jazz и эволюция средств Rational Существующие решения Evolution to Jazz Technology Platform FUTURE IBM RATIONAL SOFTWARE DELIVERY PLATFORM Rational RequisitePro Rational ClearQuest Rational ClearCase Other Rational & Non-Rational Offerings Rational Build Forge Новые продукты Built on the Jazz Technology Platform Развитие IBM Rational Software Delivery Platform Rational Team Concert Quality Management Future Products Test Lab Management - - - Rational ClearQuest Rational RequisitePro Rational Build Forge Rational ClearCase Rational Team Concert Test Lab Management Quality Management Rational ClearCase Rational Build Forge Rational ClearQuest Rational RequisitePro
- 22. Решения на Jazz Расширение Collaborative Application Lifecycle Management Rational Requirements Composer Открытая интеграция сервисов ЖЦ JAZZ TEAM SERVER Rational Requirements Composer Rational Quality Manager Rational Team Concert Rational Quality Manager Rational Team Concert Rational ClearQuest Rational ClearCase Rational Build Forge Rational Requisite Pro Business Partner Jazz Offerings Поиск и запросы Кооперация в контексте Командное взаимодействие Оповещения Безопасность Отчетность Rational Project Conductor Rational Asset Manager Rational DOORS Offering Offering Offering Процессы на базе лучших методов Powered by
- 26. Планирование итераций Отображение прогресса в реальном времени Планирование и реализация с учетом индивидуальных особенностей Использование Drag-and-drop для изменения зависимостей
- 27. Преимущества RTC - Agile планирование и управление ресурсами
- 28. Оценка рисков при планировании Ранняя идентификация рисков Выделение рисков по задачам цветом Автоматический подсчет вероятности уложиться в расписание Детальная оценка сроков от разработчика .. Низкая, средняя. высокая
- 29. Доска работ для контроля статуса работ Текущие задачи в работе Изменение статуса перетаскиванием
- 34. Централизованное управление тестированием на всем ЖЦ для всех видов тестирования и платформ JAZZ TEAM SERVER Manage Test Lab Create Plan Build Tests Report Results Test Management and Execution Rational Quality Manager Quality Dashboard Open Lifecycle Service Integrations Best Practice Processes Собственные разработки Открытая платформа Java System z, i SAP .NET IBM Collaborative Application Lifecycle Management Функциональное тестирование Нагрузочное тестирование Тестирование сервисов Анализ кода Тестирование безопасности Обработка ошибок Управление требованиями
- 35. Управляемый процесс Руководитель Разработчик Тестировщик
- 36. Управление изменениями (задачами) Руководитель Разработчик Тестировщик
- 37. Взаимодействие в контексте задач Руководитель Разработчик Тестировщик
- 38. Планирование и выполнение итераций Руководитель Разработчик Тестировщик
- 39. Управление сборкой для команды Руководитель Разработчик Тестировщик
- 40. Web клиент Руководитель Разработчик Тестировщик
- 44. Улучшение процесса - IBM Rational Self Check for Software Teams Взгляд на состояние дел в целом Детализация по практикам Инструмент оценки Отчет о результатах 0.96 3.3 Not automated yet. Static Analysis 0.50 8.8 Need clear actions Reflections 1.91 4.5 Not enough TDD Test Early 0.50 9.3 Not Fridays Daily Scrum 0.50 8.3 Not well specified Time-Boxed Iterations 0.58 8.5 Want more Stakeholder Feedback 1.89 6.8 Not enough, not in build Unit Test 0.50 7.8 Use Stories instead Use Cases Deviation Average Comments Practice
Editor's Notes
- Message: Using the RSA - RequisitePro integration it is also possible to trace all the way to code! -- Note the package explorer on the left, which is where the code is managed (and the code editor on the right). -- The slide show dragging and dropping from a use case (requirement explorer) , to design (model explorer), to code (package explorer) to set up trace relationships. It is also be possible to trace directly from the use case to the code. -- The trace tree view on the lower right shows a RequisitePro view that shows traceability all the way from high level user needs, to features, to a use case, to a class to code. -- This level of traceability has 3 key benefits: 1 - It's easy to find the code associated with a given requirement 2 - It's possible to understand the impact a change in requirements will have on existing design and code 3 - It's possible to get a better understanding project status: you can easily see which requirements have design and code associated with them
- We already talk about lifecycle traceability, but equally important is the ability to enforce a process for your software development, from implementation through production. A good repeatable workflow that is enforced through tooling is critical to the success of any software project. And related to compliance, it is important that there is proper security and the ability to electronically sign off at critical steps within the process.
- An IBM Proof of Technology © 2006 IBM Corporation
- An IBM Proof of Technology © 2006 IBM Corporation
- BBryson : At the center of our solution is ClearQuest. It is our control and unification point for requirements, change requests, test cases and results. Centralized data facilitates reporting across domains. And across geographies – as CQ supports various models of distributed solutions (native interface, web interface and CQ Multisite for geographically distributed teams). Additional Slide Info: ClearQuest completes our Eclipse based testing trifecta joining Functional and Performance Tester in the same shell. Of course, the Eclipse shell is not the only interface to your data, there is also a web client, a native Windows client and an Eclipse RCP client. The test management capability of ClearQuest provides three main functional areas: Test Planning, Test Execution and Test Reporting. With Test planning you create your test plans and test cases. Test cases are turned into configured test cases when they are attached to a test script, such as a Rational Functional Tester or Rational Manual Tester script. You can then group configured test cases into Suites for execution, or alternatively, test cases can be run individually. Results are then collected into ClearQuest for reporting.
- BBryson : A nice, but not unique, feature of the tool is the ability to dynamically add users during a test run. Other tools can do this, so don’t over sell…also, we cannot schedule additional users – it has to be done ad hoc during test execution…however, it does give prospects the ability to crank up the load during a test to break a server.
- Looking at bi-direction traceability in greater detail, we see that all activities and artifacts need to be linked together. A good system should allow you to trace they entire process.
- We call these “entry points” --- I think of them very tangible ways of focusing on what it means to treat software delivery as a business The basics of efficiency where you’re focused on specific measurable application and project improvement The basics of control where you’re addressing the inherent risks of development and integration, of your Web-facing apps or compliance issues The basics of value where you start to move from development as purely a cost center to a value center where you reduce the amount of traditional development through better use of packaged software, less custom code development and greater reuse of existing legacy investments across mainframe and distributed systems TRANSITION: At each level, there are very clear areas of improvement that can be targeted….
- Process templates provide a starting point and guide for a project area process configuration and iteration structure. They can include process documentation in HTML format. You apply a process template when you create a project area; the process can then be modified in the project area or its team areas, independent of the template. You can create templates from scratch or from existing project areas. Templates are specified in XML using a schema that can be extended by configuration point declarations. You can edit templates using source and high-level editors.
- RTC originally provided for one estimate for task completion time, now you can optionally have 3 (low, expected, high) RTC then runs a computation (on the client) that calculates a probability based on the triangulation of the estimates provides by the developer. Known as the Monte Carlo analysis And you get a probability of it fitting into the current iteration like .85 or .60 RTC already has an iteration timeline (i.e. 6 or 8 weeks built into the iteration plan) so we then color code the high risk items for that iteration so an agile team can react and respond early in the planning cycle No other agile planning tool does this
- Eclipse rich client only and Windows platform only first release (not in web ui) There is no VS.NET integration Works with RTC, but not RQM or RRC at this time
- Integrations – RC to RP ----- then on to rest of tools (CQ, etc.) Can import models….
- Optional RTLM Demo (5mins 24 secs) – http://demos.dfw.ibm.com/view/rationaltestlabmanager/
- Business benefits: Ensures that Quality really means Meeting Business Requirements Traceability extends across the entire lifecycle and is adaptable to each customer’s needs Best practices can be advised or enforced, according to local preferences Automatic tracking and tracing ensures that project quality can be audited and proven Project visibility into bug trends allow for early intervention if problems are developing Result: Development organizations deliver better business results with lower variance
- Business benefits: Ensures that Quality really means Meeting Business Requirements Traceability extends across the entire lifecycle and is adaptable to each customer’s needs Best practices can be advised or enforced, according to local preferences Automatic tracking and tracing ensures that project quality can be audited and proven Project visibility into bug trends allow for early intervention if problems are developing Result: Development organizations deliver better business results with lower variance
- Business benefits: Ensures that Quality really means Meeting Business Requirements Traceability extends across the entire lifecycle and is adaptable to each customer’s needs Best practices can be advised or enforced, according to local preferences Automatic tracking and tracing ensures that project quality can be audited and proven Project visibility into bug trends allow for early intervention if problems are developing Result: Development organizations deliver better business results with lower variance
- Business benefits: Ensures that Quality really means Meeting Business Requirements Traceability extends across the entire lifecycle and is adaptable to each customer’s needs Best practices can be advised or enforced, according to local preferences Automatic tracking and tracing ensures that project quality can be audited and proven Project visibility into bug trends allow for early intervention if problems are developing Result: Development organizations deliver better business results with lower variance
- Business benefits: Ensures that Quality really means Meeting Business Requirements Traceability extends across the entire lifecycle and is adaptable to each customer’s needs Best practices can be advised or enforced, according to local preferences Automatic tracking and tracing ensures that project quality can be audited and proven Project visibility into bug trends allow for early intervention if problems are developing Result: Development organizations deliver better business results with lower variance
- Business benefits: Ensures that Quality really means Meeting Business Requirements Traceability extends across the entire lifecycle and is adaptable to each customer’s needs Best practices can be advised or enforced, according to local preferences Automatic tracking and tracing ensures that project quality can be audited and proven Project visibility into bug trends allow for early intervention if problems are developing Result: Development organizations deliver better business results with lower variance
- An IBM Proof of Technology Collaborative Development Using Rational Team Concert
- Once again, if we go a little bit further and we start mapping that into practices, we decided in order to be able to achieve the type of flexibility, the market experimentation, speed and predictability that we were looking for, we had to have an agile core. We started assembling best practices, we started analyzing or not whether or not we were actually using those particular best practices, and we started trying to understand how we map those best practices into what we needed to do in the next incremental iteration. The initial Rational focus areas were shared vision, use case driven development, team change management across the entire organization not just one project. Concurrent testing, test management and at the agile core, iterative development ‑‑ not surprising. Tool level project planning, whole team analysis, as well as continuous integration and test‑driven development... All of those things that we encourage you to adopt as practices, we went through and adopted them ourselves. And most importantly we started looking at two key elements, evolutionary architecture and performance measurement ‑‑ two key best practices that we knew in the long run were going to be core to our success.