1 00:00:04,333 --> 00:00:15,899 With that i'm going to go ahead and transition this over to Todd Dunnovan and Todd thank you for co-presenting today. 2 00:00:15,900 --> 00:00:25,100 Thank you very much roger Jean-Louis and I will be passing the baton back and forth a couple times during this presentation; I'll be 3 00:00:25,100 --> 00:00:32,766 taking the first two sections: the introduction and the lifecycle integration; I'll then be passing onto jean-louis for in context 4 00:00:32,766 --> 00:00:41,032 collaboration. I'll comeback for lifecycle traceability and then Jean-Louis will take us home. 5 00:00:41,033 --> 00:00:50,499 One thing to note is that the title here is "Designed Management with RSA v8.5." The focus here is not so much 6 00:00:50,500 --> 00:00:58,566 Rational Software Architect as it is the design manager extension for Rational Software Architect. We wanted to set your expectations 7 00:00:58,566 --> 00:01:07,032 correctly and the design management capability which we introduced about a year ago is as appropriate say for 8 00:01:07,033 --> 00:01:15,166 Rational Rhapsody as it is for RSA, so if you if you are interested in systems engineering and you hear something here that appeals 9 00:01:15,166 --> 00:01:21,199 to you with respect to design management you're not locked out; we have the same capabilities coming down the track for 10 00:01:21,200 --> 00:01:25,133 Rhapsody, as we have for Rational Software Architect. 11 00:01:25,133 --> 00:01:32,666 One thing to note is that we are we are going to be talking about some capabilities here which have not been formally released yet. 12 00:01:32,666 --> 00:01:40,799 and so this disclaimer stands is that are statements regarding our plans, directions, and intent are subject to 13 00:01:40,800 --> 00:01:48,666 change or withdrawal without notice at IBM's sole discretion and because we are talking about the capabilities which have not yet been 14 00:01:48,666 --> 00:01:56,766 formally released that is in the next upcoming versions of design manager, we can't tell you when its coming, for one thing, 15 00:01:56,766 --> 00:02:03,632 Jean-Louis and I are not part of the core development teams; we don't have that information but company policy constrains us 16 00:02:03,633 --> 00:02:15,633 from providing that information anyway. So what is design management? It's an application lifecycle management discipline 17 00:02:15,633 --> 00:02:26,999 that basically brings software and system design to an equal level of footing with the previous disciplines which have been 18 00:02:27,000 --> 00:02:36,133 addressed by IBM Rational's architecture lifecycle management solution so you might have heard of our Jazz products: 19 00:02:36,133 --> 00:02:45,766 Requirements Composer, Quality Manager, Team Concert; they were the initial three in our ALM solution, also known as 20 00:02:45,766 --> 00:02:53,732 CLM: collaborative lifecycle management. So what we have done over the past year or so is we have appropriately lifted Architecture 21 00:02:53,733 --> 00:03:02,233 Management to be an equal partner with these. You may be familiar with Rational Software Architect, Rational Rhapsody; 22 00:03:02,233 --> 00:03:10,033 They are our industry leading software and system design solutions and what we have done is we have added server-based 23 00:03:10,033 --> 00:03:18,766 capabilities in the form of our Design Manager products that enhance their design capabilities with new team 24 00:03:18,766 --> 00:03:24,932 collaboration and lifecycle management capabilities. 25 00:03:24,933 --> 00:03:35,333 Here are some of the things which you can see in the current RSA and Rhapsody Design Management v4.0 betas and if you're 26 00:03:35,333 --> 00:03:44,066 interested in exploring these after the session you can go to jazz.net and download the beta software, load it on your machine, and 27 00:03:44,066 --> 00:03:52,966 play with it. Starting with the upper left hand corner, going down, that left column is switching over to the right: common 28 00:03:52,966 --> 00:04:00,766 administration with the other collaborative lifecycle management tools. Everything is managed now from one 29 00:04:00,766 --> 00:04:12,666 management console; more robust lifecycle integrations so for instance, you can take elements of RSA or Rhapsody models and 30 00:04:12,666 --> 00:04:19,532 robustly link them to requirements assets, quality management assets and also change management assets and the 31 00:04:19,533 --> 00:04:26,599 linkages in the upcoming version are bi- directional so you can do these linkages from any of the tools and you can see the linkages 32 00:04:26,600 --> 00:04:39,833 from any of the tools. One thing which is a real winner to me in the in the v4.0 is the fact that I can actually build my models directly 33 00:04:39,833 --> 00:04:48,799 in the Design Manager repository. With 3.0, you could build a model say in Rational Software Architect or Rhapsody and then you 34 00:04:48,800 --> 00:04:56,800 would publish it to the Design Manager repository for subsequent use in collaborative review. We still have that mode of operation 35 00:04:56,800 --> 00:05:08,100 with v4.0, but if you want to model directly into the design manager repository you can do so and one thing which is really exciting to me is 36 00:05:08,100 --> 00:05:17,366 that we also support version management of the models in the design manager repository so you actually can have multiple 37 00:05:17,366 --> 00:05:29,832 people out working in a Design Manager managed model, a lot of particular pieces once your changes are made, save in fact, 38 00:05:29,833 --> 00:05:40,666 repository-to-parallel development just as if you're using the tools in their current file- based paradigms using an SCM solution 39 00:05:40,666 --> 00:05:50,532 such as Rational Team Concert. Another major addition in the v4.0 beta is formal impact analysis and we'll talk more about this 40 00:05:50,533 --> 00:05:57,266 in subsequent slides but we now have a built- in capability, a first class capability 41 00:05:57,266 --> 00:06:08,332 for determining what is going to be impacted among all of the artifacts that I am linked to, if say something in my design model changes. 42 00:06:08,333 --> 00:06:16,699 Would a requirement be impacted? Would a work item be impacted, would a test case or test plan be impacted? To me that's a very big 43 00:06:16,700 --> 00:06:26,300 winner. Looking at the righ-hand column: in- context collaboration with commenting and review: this is a v3.0 capability which we 44 00:06:26,300 --> 00:06:33,566 retain. It's a very nice capability because it means that you can have a distributed people who perhaps do not have RSA licenses 45 00:06:33,566 --> 00:06:44,599 themselves who can participate in the review of RSA artifacts or Rhapsody artifacts. Centralized design repository: we've alluded 46 00:06:44,600 --> 00:06:55,533 to this: you can build models directly in your centralized repository. As we'll talk about later, the elements of the model are rendered 47 00:06:55,533 --> 00:07:06,233 in the repository as OSLC: Open Services for Lifecycle Collaboration objects conforming to the architecture management standard and 48 00:07:06,233 --> 00:07:14,599 then once they are there you can reuse them in different models and you can also link them to other ALM artifacts and you can also 49 00:07:14,600 --> 00:07:25,733 do multi-domain reporting if you wish to do so. Searching and design reuse, a very nice capability in the v4.0 version for readily 50 00:07:25,733 --> 00:07:32,499 identifying including say by specific types of elements; items which are of most concern to you. 51 00:07:32,500 --> 00:07:41,566 and as I alluded to before you can actually then reuse those elements in other design models. We also include in this 52 00:07:41,566 --> 00:07:51,566 particular version a nice capability to create RTF documents directly in Design Manager and then as I mentioned we also had 53 00:07:51,566 --> 00:08:00,866 improved ability to do multi-domain reporting so if you need to create a report, for instance, which includes design elements as well as 54 00:08:00,866 --> 00:08:07,832 requirement elements, work item elements, and quality management elements which related to the design elements, you can do 55 00:08:07,833 --> 00:08:22,933 so. Next let's talk about the Lifecycle Integration just for a minute and so some of you perhaps are familiar with the Rational 56 00:08:22,933 --> 00:08:32,899 Jazz space solutions and you're aware of the fact that we have a centralized application called that the Jazz Team Server 57 00:08:32,900 --> 00:08:40,300 which manages the other applications which are involved in a collaborative lifecycle management solution. So previously with 58 00:08:40,300 --> 00:08:52,900 Design Manager v3.0 you could not have Design Manager 3.0 being owned so to speak, by the same Jazz Team Server as the 59 00:08:52,900 --> 00:09:02,800 other CLM tools we're using. We have improved substantially upon that with design manager v4.0 beta in that now we can share 60 00:09:02,800 --> 00:09:11,133 the same Jazz Team Server with the other CLM tools. As a matter of course that means that you have to have well, less server 61 00:09:11,133 --> 00:09:19,233 infrastructure, less admin, which is always a good thing. As the second bullet indicates we have common user administration. You now 62 00:09:19,233 --> 00:09:27,833 can, if you wish, define new users once for all and use them across all the CLM applications and another real win which we'll 63 00:09:27,833 --> 00:09:36,366 talk about in just another slide or so, is this concept of lifecycle projects. With the other CLM tools we've had this for a while; 64 00:09:36,366 --> 00:09:44,432 where you could, once for all, create a lifecycle project which automatically created for instance, a Rational Team Concert project, 65 00:09:44,433 --> 00:09:52,133 a Quality Manager project, Requirements Composer project, link them together in a relatively seamless way. 66 00:09:52,133 --> 00:10:02,566 We have now added Design Manager into this particular paradigm, again reducing the amount of Admin overhead which exists in the 67 00:10:02,566 --> 00:10:10,932 overall Collaborative Lifecycle Management Solution. This screenshot is just an illustration of what we mean by design and 68 00:10:10,933 --> 00:10:19,533 lifecycle projects. One of the things I really like here, so for instance if you take a look at the item which is highlighted, this is where Jean- 69 00:10:19,533 --> 00:10:30,433 Louis needs lifecycle project, so what he's focusing on is a project he's going to create for the quality professional, the analyst, the 70 00:10:30,433 --> 00:10:37,199 developer with architecture management. So what this particular item would do is it would create a lifecycle project configuration 71 00:10:37,200 --> 00:10:47,866 which incorporate the capabilities of all four tools. There are other lifecycle project types as you can take a look down here which also 72 00:10:47,866 --> 00:10:54,132 include some aspect of architecture management, for instance as I look toward the bottom of the list I see one for architect 73 00:10:54,133 --> 00:11:00,933 and analyst, and I also see one for architect and developer. So if you wanted to create a project for instance with just Rational 74 00:11:00,933 --> 00:11:07,099 Requirements Composer and Design Manager, you might choose the one for architect and analyst. If you wanted to create 75 00:11:07,100 --> 00:11:16,600 one just with Design Manager and with say Rational Team Concert you would choose the project for Architect and Developers. 76 00:11:16,600 --> 00:11:25,700 Again, what we're doing here is making a very concerted effort to reduce the administrative overhead of using the tools and make it much 77 00:11:25,700 --> 00:11:49,666 simpler to get started. and with this I will pass the baton to Jean-Louis, so JL just bear with me .... 78 00:11:49,666 --> 00:12:03,632 Thank You Todd. What we cover in the next section the in-context collaboration is really the different DM capabilities to help the 79 00:12:03,633 --> 00:12:17,099 different teams collaborate on design activities. The very first capability is the ability to share designs on a centralized design 80 00:12:17,100 --> 00:12:27,800 management repository. This is not something new it already existed in v3. in the next Design Management release what is 81 00:12:27,800 --> 00:12:38,600 improved is that you can import existing designs from Rational Software Architect but you can also create Design resources 82 00:12:38,600 --> 00:12:51,166 and models directly on the server, the Design Management server. And once you have shared your designs on the server then 83 00:12:51,166 --> 00:13:04,032 the team can access the designs from the web, a web browser and they can start adding comments on the design resources 84 00:13:04,033 --> 00:13:16,066 and not only can they add text comments but they can also add growing real world mock- ups on the design diagrams for instance on 85 00:13:16,066 --> 00:13:26,632 the slide we have a sequence diagram and the circle, the red circle is not something added with PowerPoint, this is really part of 86 00:13:26,633 --> 00:13:38,033 Design Management from the growing palette and of course people can answer to the different comments just like they can 87 00:13:38,033 --> 00:13:48,033 have a discussion which is captured on the design resource. JL, I did post the link in the chat; something similar to what you're 88 00:13:48,033 --> 00:13:57,866 describing; we did a youtube video on faster design reviews; being able to use this rather than the traditional sort of back and forth 89 00:13:57,866 --> 00:14:07,499 over the shoulder especially when designers can often be in different locations sometimes; so a great way to speed up the whole 90 00:14:07,500 --> 00:14:21,466 design process. Another addition to the next design management release is the ability to create sketches and rich text document 91 00:14:21,466 --> 00:14:31,099 directly on the server so from the web UI you you can create a new sketch diagram and you can create a rich text document the rich 92 00:14:31,100 --> 00:14:41,966 text document can include links to other design resources and for instance you can explain what are your architectural 93 00:14:41,966 --> 00:14:54,299 decisions in a document and include also diagrams directly in the document; this is a really nice feature to be able to document 94 00:14:54,300 --> 00:15:15,066 designs on the server. Moving on to the next slide. Design reviews have been improved compared to v3. It's pretty similar to what you 95 00:15:15,066 --> 00:15:26,532 were able to do in the past: you create a review, you can add a couple of resources to that review so the different design resources 96 00:15:26,533 --> 00:15:37,433 that you want to review, you also specify the different participants, people from the team that are going to be reviewing the assets and 97 00:15:37,433 --> 00:15:50,333 you can manage the review which has a lifecycle so it starts and you can track the progress of the review during the entire 98 00:15:50,333 --> 00:15:58,499 review lifecycle and when everyone completes the review, then the review is over and captured on the design management 99 00:15:58,500 --> 00:16:15,933 server for references later. Dashboards are not new either, they were already there in design management v3, as some new 100 00:16:15,933 --> 00:16:31,033 widgets have been added to customized dashboards and bottom line, a dashboard is really helpful to capture project information on 101 00:16:31,033 --> 00:16:41,999 an central web page and so you've got two different dashboards that you can use: project dashboards for the whole team; you can also 102 00:16:42,000 --> 00:16:53,433 create a personal dashboard to gather your own information on a project and you can decide to share your personal dashboard 103 00:16:53,433 --> 00:17:02,899 with others if you want to do so. On a dashboard you can have the design management specific information, but if you 104 00:17:02,900 --> 00:17:16,033 are in a CLM environment you can also mate your design information with requirement information quality management information 105 00:17:16,033 --> 00:17:28,566 and RTC Team Concert tasks information project progress on your dashboard and everything on a dashboard is real-time 106 00:17:28,566 --> 00:17:37,866 information extracted from the Design Management or other CLM repositories. 107 00:17:37,866 --> 00:17:46,566 Jean-Louis, we have a question: Is the review lifecycle itself customizable? 108 00:17:46,566 --> 00:17:58,399 The Lifecycle itself is not customizable as far as I know in the current beta release. 109 00:17:58,400 --> 00:18:17,566 But for everything that does not exist yet I encourage people to go to Jazz.net and everyone can submit enhancement requests. 110 00:18:17,566 --> 00:18:28,832 If you feel something should really be part of the Design Management Next release you can contribute to the product from Jazz.net 111 00:18:28,833 --> 00:18:41,899 Jean-louis, one thing to note is the fourth bullet; you can actually take a Link item from Design Manager and link it to a Team Concert 112 00:18:41,900 --> 00:18:51,366 work item if you need to take advantage of the more robust work flow management capabilities that the Team Concert work item 113 00:18:51,366 --> 00:19:05,032 would offer. Absolutely, and this is new in the beta release, because in Team Concert work items you also have approvals; you can mix 114 00:19:05,033 --> 00:19:16,299 the two of them; the approval at the project level and the approval at the design management level. 115 00:19:16,300 --> 00:19:28,466 Moving onto slide number 14: new capability in Design Management. Todd already talked about it before; is the configuration 116 00:19:28,466 --> 00:19:43,166 management capability. This is to support parallel development; you can create multiple streams, so basically you have multiple 117 00:19:43,166 --> 00:19:51,132 workspaces. You can have one workspace for a given team; one other workspace for another team, each team working in isolation 118 00:19:51,133 --> 00:20:02,133 from the other and then you can deliver the different changes as you can merge the stream and compare the different versions so 119 00:20:02,133 --> 00:20:13,633 we do have versioning now in Design Management and as any configuration management tool, when you modify 120 00:20:13,633 --> 00:20:25,033 something it creates a change set and before you commit your changes, nobody can can see them so you do not impact other 121 00:20:25,033 --> 00:20:44,899 project members as long as you do not deliver the changes. Moving on, next capability, reporting. So we've got two 122 00:20:44,900 --> 00:20:58,700 different reporting approaches in the design management: one is to create documents out of the design management repository so you 123 00:20:58,700 --> 00:21:09,966 can extract a couple of information from the design management server like all the different classes of some diagrams for all 124 00:21:09,966 --> 00:21:22,866 the different information stored in the design management server; you can also... so to create a report you don't need an external 125 00:21:22,866 --> 00:21:33,632 tool; design management reporting comes with a couple of predefined templates and you reuse those templates from the design 126 00:21:33,633 --> 00:21:43,633 management server to create a report. If you want to go one step further then you need to have a rational publishing engine license and 127 00:21:43,633 --> 00:21:55,999 you can create additional templates and import those templates in design management. As Todd mentioned at the very 128 00:21:56,000 --> 00:22:06,233 beginning you can with Rational Publishing Engine template you can create a report that extracts data from design management but 129 00:22:06,233 --> 00:22:18,399 also requirements management and change and configuration management repositories so you can create reports through the whole 130 00:22:18,400 --> 00:22:36,200 lifecycle. In the next slide I gather some information on additional capabilities; I'm going to go very quickly on those ones, but we 131 00:22:36,200 --> 00:22:52,166 could have additional sessions to deep dive on some of them. With Design Management v4, beta release are you can extend the 132 00:22:52,166 --> 00:23:04,499 design management capabilities with custom domains so you can create your own common domains to document your 133 00:23:04,500 --> 00:23:17,033 business design so custom domain can be created on anything and we provide an example on custom domain, part of DM, 134 00:23:17,033 --> 00:23:31,366 The example is a library example where out of the box you've got different profiles to create authors, groups and create the modeling 135 00:23:31,366 --> 00:23:45,632 around a library; we have improved the search capabilities in addition to being able to search with key words you can also create 136 00:23:45,633 --> 00:23:59,699 extensive queries on design resources so as an example you can search for all the different interfaces in your design management 137 00:23:59,700 --> 00:24:16,533 repository or you can search for a specific type of stereotype or a specific method name and you can even search on OSLC links so 138 00:24:16,533 --> 00:24:28,066 you have an extensive graphical environment to create queries and the queries are then stored in design management and you can 139 00:24:28,066 --> 00:24:41,199 leverage those queries to find information from the repository; you can even reuse those queries in the dashboards so you can expose 140 00:24:41,200 --> 00:24:52,066 the result of a query as a widget on a dashboard. With the next Design Management query, the 3rd bullet point, you 141 00:24:52,066 --> 00:25:04,466 can also create transformation from Rational Software Architect client; the transformation will run on the information stored in the 142 00:25:04,466 --> 00:25:16,599 server repository so you can create a transformation locally which extracts the information from the server and as Todd will 143 00:25:16,600 --> 00:25:30,000 cover in a couple of slides you can create extensive impact analysis diagrams from any design management resource; one other 144 00:25:30,000 --> 00:25:41,633 aspect that we don't really cover in the slide but we could have a session on that later on is the Rational Software Architect Design 145 00:25:41,633 --> 00:25:54,699 Management extension so almost everything we've seen in the slides so far can be done from the web UI obviously but also from the 146 00:25:54,700 --> 00:26:05,600 Eclipse clients with the Design Management Extension so you can use the Eclipse client to access the Design Management repository 147 00:26:05,600 --> 00:26:22,133 and add new model elements as search goes through the different diagrams the comments, add new comments, everything 148 00:26:22,133 --> 00:26:37,899 And now I will make you presenter Todd; I will try at least; thank you Jean-Louis; yes i'm going to discuss briefly the lifecycle 149 00:26:37,900 --> 00:26:47,100 traceability capabilities of the Design Manager application. Many of you may have heard of open services for lifecycle 150 00:26:47,100 --> 00:27:01,600 collaboration; this is an open industry effort to define a set of reusable specifications for managing the interchange of information 151 00:27:01,600 --> 00:27:12,166 between software development tools. We're also working, OSLC consortia is also working to extend this into other domains, for instance 152 00:27:12,166 --> 00:27:21,432 to create linkages between product management capabilities such as electronics/automotive and software 153 00:27:21,433 --> 00:27:33,466 development. As it indicates here there's over 400 registered community members, 34 different organizations participate and as I 154 00:27:33,466 --> 00:27:42,399 indicated we're pulling in interest from a wide range of domains: traditional software development as well as other domains as I 155 00:27:42,400 --> 00:27:51,333 mentioned before such as product development; an interesting aspect of the specifications for OSLC is they are developed 156 00:27:51,333 --> 00:28:07,433 on the basis of user scenarios so we don't necessarily specify the world but we focus on what is needed in the OSLC specifications to 157 00:28:07,433 --> 00:28:20,499 address common user scenarios for cross- domain data access, querying, and such as that. The interesting aspect about this is that 158 00:28:20,500 --> 00:28:29,833 over the past couple years or so the specifications have been extended to include specifications for interfaces for architecture 159 00:28:29,833 --> 00:28:39,499 management as you might suspect based upon the pace of which our original OSLC- enabled tools came out, the original domains 160 00:28:39,500 --> 00:28:47,233 which were supported included change management, requirements management, and quality management; there is always the 161 00:28:47,233 --> 00:28:59,099 understanding that additional domains were needed, so architecture management has now come to the fore. And so what the OSLC 162 00:28:59,100 --> 00:29:12,333 capabilities enable us to do is to incorporate design management robustly into full lifecycle traceabilities as this diagram indicates via 163 00:29:12,333 --> 00:29:20,199 OSLC you can do things such as take RSA models and Rhapsody models when enhanced with the Design Manager 164 00:29:20,200 --> 00:29:29,566 capabilities and link them to requirements which are managed by Requirements Composer or DOORS. You also have the 165 00:29:29,566 --> 00:29:38,732 ability to associate design elements with various flavors of work items which are managed by tools such as Rational Team 166 00:29:38,733 --> 00:29:49,399 Concert and you also have the ability to establish relationships between design elements and quality management items 167 00:29:49,400 --> 00:29:59,400 such as test plans and test cases; now this diagram we're showing right here, it is architecture management-centric but as you 168 00:29:59,400 --> 00:30:06,800 suspect we also support linkages between all the other domains as well: change management, links to quality management, 169 00:30:06,800 --> 00:30:18,833 links to requirements, etc., and here are some questions which the link ability can help you address: so iteration planning 170 00:30:18,833 --> 00:30:29,833 design work can be an important input into iteration planning so now this enables project managers to begin to incorporate design 171 00:30:29,833 --> 00:30:41,066 work into their iteration planning; further linkability between requirements and design: how kind of impact analyses across those? 172 00:30:41,066 --> 00:30:52,732 This enables you to do that. I have developers who perhaps are focused on their particular work items; how can they identify design 173 00:30:52,733 --> 00:31:02,266 elements which are germain for their particular assigned work items? This enables them to do that. And clearly how 174 00:31:02,266 --> 00:31:15,199 can I ensure traceability across entire life cycle? Link all of the domains together using tools that are enabled with OSLC. 175 00:31:15,200 --> 00:31:25,066 One capability with which I was a very excited when I first got wind of what we are doing with DM v4.0 beta is what we're looking at right 176 00:31:25,066 --> 00:31:35,132 here which is impact analysis from a design- centric point of view so what we can do for instance in this particular diagram as it 177 00:31:35,133 --> 00:31:43,499 indicates is that you can include both design elements in the impact analysis and also elements which are linked in from other 178 00:31:43,500 --> 00:31:56,066 OSLC-enabled repositories so for instance if I wanted to focus on a particular, say, interface; that perhaps, maybe I have fifteen different 179 00:31:56,066 --> 00:32:06,132 developers or fifteen different architects who are building a SOA models and they have very service interfaces to find. What I want to do 180 00:32:06,133 --> 00:32:16,766 is I want to identify all of the services that can possibly be impacted if I change a particular interface. You can do that with the impact 181 00:32:16,766 --> 00:32:25,132 analysis capabilities of Design Manager so you're not limited as you are say with Rational Software Architect to doing an impact 182 00:32:25,133 --> 00:32:33,666 analysis within a given model for a given project or a given workspace but you can do a pervasive impact analysis across all the 183 00:32:33,666 --> 00:32:44,332 assets that are managed within your design manager repository and also you are able to do an impact analysis which goes out to the 184 00:32:44,333 --> 00:32:57,133 OSLC items which are directly linked to your design manager elements. To facilitate the impact analysis we create what's referred to 185 00:32:57,133 --> 00:33:04,899 as analysis configuration and as the bullet indicates this defines the parameters for the analysis which is what type of linkages do I 186 00:33:04,900 --> 00:33:14,233 want to consider. Also gives us the ability to control how far out from my central element do I want to go in my impact analysis. 187 00:33:14,233 --> 00:33:20,066 Do I want to take a look at elements that I depend upon, elements that depend upon me, or both? 188 00:33:20,066 --> 00:33:28,366 and you can define an analysis configuration once for all so to speak and reuse it pervasively to support a number of impact 189 00:33:28,366 --> 00:33:37,432 analyses. Another interesting capability let's say that you want to do the impact analysis and then at some point it may be 190 00:33:37,433 --> 00:33:45,366 taking a snapshot of the diagram which have been created; if you wish, you can create an impact analysis which captures a certain 191 00:33:45,366 --> 00:33:52,332 amount of information, these types of linkages, this level of depth and such, and if it is too much information then you can simply 192 00:33:52,333 --> 00:34:02,533 prune the tree so to speak and focus on the pieces of the impact analysis that are most germain for you. 193 00:34:02,533 --> 00:34:08,233 And Jean-Louis is going to take us home. JL, let me pas the baton back to you... 194 00:34:08,233 --> 00:34:17,966 So I just wanted to cover briefly the Money That Matters 2012; so Money That Matters 195 00:34:17,966 --> 00:34:29,732 contains, regarding Design Management, there are three different aspects related to money that matters; first, Design 196 00:34:29,733 --> 00:34:40,433 Management contains Money That Matters sample application so out of the box when you install DM, Design Management 197 00:34:40,433 --> 00:34:54,766 you can push a button and the server will deploy a project for you and this is the JKE banking sample application but that 198 00:34:54,766 --> 00:35:07,432 projects contains a number of artifacts that you can leverage, you can test the different DM capabilities through this sample 199 00:35:07,433 --> 00:35:20,433 application and everything is preconfigured for you. If you install Design Management in an CLM environment with Requirements 200 00:35:20,433 --> 00:35:30,666 Management, quality management, and change, and configuration management, then the Money That Matters sample app is also 201 00:35:30,666 --> 00:35:46,199 linked being used to a couple of assets from the lifecycle application, so we provide a rich set of examples to work with and to try out 202 00:35:46,200 --> 00:35:59,933 the Design Management server capabilities; the second aspect of the Money That Matters is the scenario; we have documented the full 203 00:35:59,933 --> 00:36:19,833 lifecycle scenario on Jazz.net which is a genuine scale scenario where we created, documented all of the different steps during 204 00:36:19,833 --> 00:36:32,333 a journey that a typical team will go through in a new CLM, collaborative lifecycle management environment. So there are 205 00:36:32,333 --> 00:36:44,699 tasks and activities for the analyst, the business analyst, for the scrum master, for the architects, the developers, the testers, 206 00:36:44,700 --> 00:36:56,900 and a couple of others I don't remember off the top of my head; this scenario is based on the money that matters sample application 207 00:36:56,900 --> 00:37:07,533 that I mentioned before so if you have the application installed then you can go through this scenario and experiment this scenario 208 00:37:07,533 --> 00:37:21,466 on your server and the scenario description or documentation is available from jazz.net and there is a link on the slide that will redirect you 209 00:37:21,466 --> 00:37:32,799 on the first, on the home page of the scenario and the 3rd aspect regarding Design Management and Money That Matters 210 00:37:32,800 --> 00:37:47,800 is the self-paced training that is part of the Design Management next release; the self- paced training is based on the money that 211 00:37:47,800 --> 00:38:01,500 matters scenario and it leverages the money that matters sample applications so if you do have Design Management server available 212 00:38:01,500 --> 00:38:15,833 then from the Design Management Help you can go through the self-paced training and learn about design management and the 213 00:38:15,833 --> 00:38:33,533 different Design Management capabilities from the free self-paced training. A brief summary before we start the Q&A session... 214 00:38:33,533 --> 00:38:44,266 So Design Management is really part of the application lifecycle management descipline. It complements the requirement 215 00:38:44,266 --> 00:38:55,966 management, quality management, and change management capabilities from an IBM offering point of view, Design 216 00:38:55,966 --> 00:39:08,532 Management offering can integrate with requirement management and with the CLM offering so as an example you can have 217 00:39:08,533 --> 00:39:18,999 Rational Requirements Composer, you can have Rational Quality Manager and Rational Team Concert and you installed the 218 00:39:19,000 --> 00:39:32,366 Design Management in addition to those three offerings and you have a full CLM offering with full lifecycle integration, 219 00:39:32,366 --> 00:39:47,132 everything, the integration itself is based on OSLC just like Todd mentioned before and the Design Management capabilities extend 220 00:39:47,133 --> 00:40:05,133 what already exists in Rational Software Architect or Rational Rhapsody. The last slide is really some additional information if you 221 00:40:05,133 --> 00:40:20,966 want to download the beta version of Design Management or any other CLM product you can go on Jazz.net and from the home page 222 00:40:20,966 --> 00:40:38,199 you're going to have a link to the design part of it. The design part of CLM contains the product feeds but also some articles, demos, 223 00:40:38,200 --> 00:40:52,666 the help which is beta help under development, so you can access all that and try out the Design Management capability.