Your SlideShare is downloading. ×
0
5.2.2013 2013   2013 - Software, System, & IT Architecture - Good Design is Good Business: Design Management: Pictures are Worth….
5.2.2013 2013   2013 - Software, System, & IT Architecture - Good Design is Good Business: Design Management: Pictures are Worth….
5.2.2013 2013   2013 - Software, System, & IT Architecture - Good Design is Good Business: Design Management: Pictures are Worth….
5.2.2013 2013   2013 - Software, System, & IT Architecture - Good Design is Good Business: Design Management: Pictures are Worth….
5.2.2013 2013   2013 - Software, System, & IT Architecture - Good Design is Good Business: Design Management: Pictures are Worth….
5.2.2013 2013   2013 - Software, System, & IT Architecture - Good Design is Good Business: Design Management: Pictures are Worth….
5.2.2013 2013   2013 - Software, System, & IT Architecture - Good Design is Good Business: Design Management: Pictures are Worth….
5.2.2013 2013   2013 - Software, System, & IT Architecture - Good Design is Good Business: Design Management: Pictures are Worth….
5.2.2013 2013   2013 - Software, System, & IT Architecture - Good Design is Good Business: Design Management: Pictures are Worth….
5.2.2013 2013   2013 - Software, System, & IT Architecture - Good Design is Good Business: Design Management: Pictures are Worth….
5.2.2013 2013   2013 - Software, System, & IT Architecture - Good Design is Good Business: Design Management: Pictures are Worth….
5.2.2013 2013   2013 - Software, System, & IT Architecture - Good Design is Good Business: Design Management: Pictures are Worth….
5.2.2013 2013   2013 - Software, System, & IT Architecture - Good Design is Good Business: Design Management: Pictures are Worth….
5.2.2013 2013   2013 - Software, System, & IT Architecture - Good Design is Good Business: Design Management: Pictures are Worth….
5.2.2013 2013   2013 - Software, System, & IT Architecture - Good Design is Good Business: Design Management: Pictures are Worth….
5.2.2013 2013   2013 - Software, System, & IT Architecture - Good Design is Good Business: Design Management: Pictures are Worth….
5.2.2013 2013   2013 - Software, System, & IT Architecture - Good Design is Good Business: Design Management: Pictures are Worth….
5.2.2013 2013   2013 - Software, System, & IT Architecture - Good Design is Good Business: Design Management: Pictures are Worth….
5.2.2013 2013   2013 - Software, System, & IT Architecture - Good Design is Good Business: Design Management: Pictures are Worth….
5.2.2013 2013   2013 - Software, System, & IT Architecture - Good Design is Good Business: Design Management: Pictures are Worth….
5.2.2013 2013   2013 - Software, System, & IT Architecture - Good Design is Good Business: Design Management: Pictures are Worth….
5.2.2013 2013   2013 - Software, System, & IT Architecture - Good Design is Good Business: Design Management: Pictures are Worth….
5.2.2013 2013   2013 - Software, System, & IT Architecture - Good Design is Good Business: Design Management: Pictures are Worth….
5.2.2013 2013   2013 - Software, System, & IT Architecture - Good Design is Good Business: Design Management: Pictures are Worth….
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

5.2.2013 2013 2013 - Software, System, & IT Architecture - Good Design is Good Business: Design Management: Pictures are Worth….

164

Published on

Series Name: Software, System, & IT Architecture …

Series Name: Software, System, & IT Architecture

Webinar Name: 2013 - Software, System, & IT Architecture - Good Design is Good Business: Design Management: Pictures are Worth….

Date: May 2, 2013

Presneter: Roger Snook

Published in: Technology, Education
1 Comment
2 Likes
Statistics
Notes
  • What was so special in the presentation that you had to lock it?
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total Views
164
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
1
Likes
2
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Author Notes: This is the IBM Rational standard template for internal and external Rational presentations. It was created in Microsoft PowerPoint Standard Edition 2003. This template is also converted and provided in Lotus Symphony v3.0. Additional IBM Rational presentation assets and resources can be found on Rational’s Managing the Brand W3 Intranet site: https://w3-03.ibm.com/software/marketing/marksite.nsf/AllMarketingPages/Brand-Rational-rt_rtb?opendocument?opendocument If internal presentations are confidential, please add: “IBM Confidential” to the slide masters Select: View / Master / Slide Master and add “IBM Confidential” to both the title master and slide master Use sentence case capitalization for presentation titles, slide titles, category labels and bullets: Format / Change Case / Sentence Case. Initial capitalization is limited to our products and offerings. Applying this template to your existing presentation Task Pane needs to be viewable: Select View / Task Pane Select Slide Design - Design Templates from the Task Pane pull-down menu Select “Browse” at the bottom, and find “Rational_Standard_Template.pot” on your hardrive and click Apply Please note that not all slides will reformat appropriately once template is applied. Some reformatting will be necessary Printing your presentation on a black and white printer Prior to printing your presentation, view the slides in grayscale mode: Select View / Color/Grayscale / Grayscale Select problem graphics or text and right-click and select Grayscale Setting Select the grayscale setting that displays the problem graphic/text the best Note: Changing the greyscale setting does not affect the color view Return to Normal View by selecting View / Color/Grayscale / Color
  • Value Stream Mapping (VSM) is a Lean process tool that can help teams to get an understanding of where some of their biggest problems are. When done correctly, value stream maps are produced by collaborative, high touch, low ceremony session that can lightly apply a structured method to identifying organizational waste and potential areas for improvement. Test open up a defect record in CMVC (takes between 10 and 60 minutes) The defect goes onto a triage queue waiting for assignment to a programmer (wait is typically 1 day) Chief programmer assigns defect to the right person (takes 1 minute) Programmer sees defect appear on his/her queue, and waits for it to become a top priority (can be immediate if it’s a sev 1, but up to 2 weeks) Now that defect is top priority, programmer fixes code, unit tests and checks in  and puts track in integrate state (between 1 hour and 1 week of valuable work) Since builds are done on Fridays, we wait between 0 and 7 days for the build to actually include the fix. A developer start the zOS portion of the build which takes about 3 hours.  One developer is needed to babysit the build since it can fail at many points and you don’t want to come back after 3 hours to find that it failed in the first minute. Once the zOS portion of the build is complete, a script is run to FTP some key zOS files since these files are needed for the distributed portion of the build.  The FTP takes about 1 minute. The build engineer logs on to the BigB UI and manually initiates the distributed portion of the build.  It only takes a minute to create the build request. The Tivoli Development Services team's central build system picks up the build request, extracts the code from CMVC onto an ITCS104 compliant machine that they maintain for Omegamon and the distributed portion of the build runs.  It takes about 10 minutes to extract and build the code. Once the build has completed, the build engineer checks the logs to see if the ‘track stacking’ issue has appeared. If it has (which happens every other build), then it can take 2 hours to resolve it and resubmit the build. The build engineer runs a script to sent the built binaries from the build machine to TIB for packaging.  This can take between 45 mins and 10 hours although the packaging work is itself incredibly simple and could be done much more quickly. Once packaging is complete, a script copies the package back to the BVT machine and installs the image. This takes about 30 mins. The build engineer notifies developers that the build is available for testing and developer manually verify that there fixes are working (can be as fast as 30 minutes, but this typicall takes one day). Assuming that the build, packaging, installing and BVT all worked, test are notified by email that the build is good and can be picked up. If the fix is blocking Test progress, then they will pick up the build after 1 or 2 days and take a few hours to deploy it onto their test systems (time depends on exactly how much changes in the build – some times, if only minor things have changes, deploy times can be fast) Between 6 hours and 1 day later, they Test set up their tests to validate that the original problem was really resolved.  This generally takes a few hours. Most of the time, the tests complete in about an hour, but some times it can take 3 days before the test results come back and can be verified. Approximately once out of every three defects, Test find that the problem was not resolved and so they reopen the defect and the cycle repeats.
  • Provide higher level of abstraction to communicate and as a team arrive at the best and simplest solution possible, only adding additional design aspects when required in an iterative fashion Early analysis and validation, some of that might be through patterns, best practices, and automation and other aspects is through collaboration with SMEs, experienced team members, domain specific experts Once you have those blueprints of the system they enable informed & iterative change going forward, additions as needed, understand change and being able to respond quickly … agility
  • RSA has very deep capabilities and we’ve been working on broader capabilities to address the phases of development…
  • What is Lifecycle Traceability? Lifecycle Traceability is the ability to provide both forward- and backwards visibility across your project lifecycle. The Rational solution for CLM allows you to identify with confidence that the software you are delivering to a customer includes a specific requirement that was developed using a specified process, associated with a specific software build, and validated by a specific set of test cases and test case results. Anything less and you really don’t know what you are delivering and whether what you are delivering will meet your quality or regulatory compliance requirements.
  • Author Note: Mandatory Rational closing slide (includes appropriate legal disclaimer). Graphic is available in English only.
  • 06/12/13 IBM IOD 2011 05/31/12 Prensenter name here.ppt 05/31/12 12:26
  • Proprietary designs formats are difficult to share between teams Difficult to search, view, and analyze; leads to multiple design silos Information becomes stale; stakeholders end up working with outdated design information Valuable design data is lost; no reuse, teams constantly duplicate efforts Existing design solutions are task-specific and limited Don’t scale, difficult to customize and maintain Limited ability for creating reports and documentation Limited product support, may not include all tools in customer’s environment (what does this mean??) Collaborating with stakeholders on design is tedious, manual, and error prone No direct stakeholder access to designs, designers must create external review documents Collaboration is done via email, f2f, or 3rd party collaboration software (like Sharepoint) Comments are not linked to the original design and are lost; designers must manually collect Difficult for stakeholders to verify if their comments were incorporated into subsequent designs Reporting is expensive and inefficient Individual tools have their own reporting solutions Information may be located in multiple sources; generating documentation from multiple tools and merging the results is a manual and tedious task
  • Transcript

    • 1. © 2012 IBM CorporationSoftware and SystemsEngineering | RationalA Picture is Worth….(Tame the Complexity with Lifecycle Integrations)Improve on Time to market, Quality and reduce RiskIBM RationalMay 2nd2013Host: Roger SnookWorldwide Enablement Leader, Mobile, SOA, DesignManagement+1.703.943.1170, RCSnook@us.ibm.comSpeaker: Manish KumarProduct Manager: RSA & Design Managermanishksingh@in.ibm.com
    • 2. © 2012 IBM CorporationSoftware and Systems Engineering | RationalValue Stream Map (VSM): Where did the time go?An Example of how Rational improves productivity
    • 3. © 2012 IBM CorporationSoftware and Systems Engineering | RationalAnother value stream view – expressed as % of time reductionSoftware Architecture and Design Solution (RSA) – Benefit MatrixActivity Approximate ValueRealizedReduced labor for Coding ( due to use of Transformations & Code generation,patterns and asset reuse)22%Reduced efforts during modeling using visual editors, support for patterns,templates to make UML diagrams (class, sequence)25%Better Communication, collaboration with teams and customer and identifyingdefects early15%Reduced Defect costs (Better Quality of code as a result of ArchitectureDiscovery, Visualizations, Model Analysis)15%Improved Documentation using visualization, in built reporting (Model-CodeSynchronization, Javadoc, BIRT and other publishing options)18%Reduced labour for Reverse Engineering to develop models of existing code(using Code Visualization and Reverse Engineering)20%Improved database design using inbuilt database design and developmentfeatures10%Average Value Realized 17.86%
    • 4. © 2012 IBM CorporationSoftware and Systems Engineering | Rational Teams need to broaden their understanding of architecture and designgoals, reducing costly architectural mistakes but…Tame the Design Complexity with Lifecycle IntegrationsImprove on Time to market, Quality and reduce Risk Design tools often focus on practitioner and often lack team integration. Teams cannot easilyshare designs and get feedback from stakeholders Linking designs to other lifecycle artifacts is difficult, leading to a lack of traceability andunderstanding of the impact of changes Companies are constantly reinventing the wheel because of difficulty searching for informationacross multiple designs that are locked in filesWith Rational Software Architect Design Manager Allows teams to collaborate and iterate on designs in real-time. Produce better quality designwith less time. Delivers on the value of good design, by improving connectivity and linkages of the design to allteams and lifecycle artifacts. Integrated designs and design process with the rest of the lifecycle. Automate Impact analysis, Design Review and Searching & Re-usabilityHow do you link your design artifacts with rest of the lifecycle?How do you asses the traceability and perform the changeimpact? How do you share your designs with the stakeholders and teammembers?How much time do you spend to search and reuse your designs?How do you link your design artifacts with rest of the lifecycle?How do you asses the traceability and perform the changeimpact? How do you share your designs with the stakeholders and teammembers?How much time do you spend to search and reuse your designs?RTC WIRRC requirement
    • 5. © 2012 IBM CorporationSoftware and Systems Engineering | RationalWhy Software Design?Good Designs. Better Outcomes.Iterative and collaborative software design helps teams address these challenges by:– Providing a higher level of abstraction to evaluate alternatives and arrive at the bestand simplest solution– Communicating a shared understanding across independent & distributed teams– Improving quality with early analysis and validation– Reducing development time by generating implementation resources– Enabling informed decisions on changes from blueprints of IT systemsDesign is important across the application lifecycle– Quickly capture and collaborate on initial design ideas with sketching– Define solution architectures and identify reusable services– Ensure successful and repeatable deployments with deployment planning
    • 6. © 2012 IBM CorporationSoftware and Systems Engineering | RationalDesign Management and CollaborationDM Team ServerModels Change ManagementCross Lifecycle linksComments & MarkupsReviewsWeb ClientWeb ClientRSA ClientRSA ClientDesignCollaborateManageLinkReviewCollaborateLinkReviewCollaborateLinkDesignCollaborateManageLinkChangeManagement ServerRTCRequirements ServerDOORS / RRCQuality ServerRQMOSLC
    • 7. © 2012 IBM CorporationSoftware and Systems Engineering | RationalExpressing Architecture and Design GoalsRational Software Architect Types of ExpressionAgile SketchingRich text documentsBusiness Process Model Notation (BPMN)UML models + domain and implementationsextensionsDeployment Topologies
    • 8. © 2012 IBM CorporationSoftware and Systems Engineering | RationalEveryone can access designs• Increase team knowledge through anenterprise-wide software designrepository• Analysts, SMEs, testers, and otherextended team members can accessdesigns through a Web client• Designs become URL addressable• Search across all of the organizationsexisting designs to discoverknowledge• Navigate designs and visualizerelationships
    • 9. © 2012 IBM CorporationSoftware and Systems Engineering | RationalEveryone stays connected Dashboardsprovide an easyway to stayconnected withdesign activities Designcomments,recent links, mostactive, designreviews, designchanges Create mashupdashboards withviewlets fromacross theapplicationlifecycle
    • 10. © 2012 IBM CorporationSoftware and Systems Engineering | RationalLifecycle Traceability improves quality Establish relationships between software artifacts Identify and close artifact gaps, ensuring coverage across disciplines Provides visibility into the completeness of planned items by inspecting all related artifacts Provides easy access to related artifacts ensuring everyone shares the same view Delivers transparency which enables everyone to make fully informed decisions based businessprioritiesCustomer FinalProductBuildArtifactsEnvironment SupportingSystemsRequirementsManagementInitial IdeaInstant access to details from any point in development process10
    • 11. © 2012 IBM CorporationSoftware and Systems Engineering | RationalDesign and Lifecycle Traceability Design and Requirements (Rational RequirementsComposer & Rational DOORS)– Analysis– Coverage Designs and Test Artifacts (Rational QualityManager)– Test coverage of designs Design and Change Management (Rational TeamConcert)– Planning– Design Changes– Implementation– Defects
    • 12. © 2012 IBM CorporationSoftware and Systems Engineering | RationalLearn from the past Quickly search across all of your organizations designs on the server for learning, review,analysis, or to identify potential reuse Search directly on the server; no need to load designs into a client first Simple full text search over model content (name, description, type) Powerful query based searchingAdditional filteringon results if needed
    • 13. © 2012 IBM CorporationSoftware and Systems Engineering | RationalAutomate Impact Analysis New graphical impact analysis diagram thatincludes design and linked lifecycle artifacts Analysis Configuration defines theparameters for the analysis• Upstream level, downstream level, which linkstypes to include• Can be used be shared by multiple analysis Analysis applies the configuration to aselected element to perform the impactanalysis• Save and re-run at a later time13
    • 14. © 2012 IBM CorporationSoftware and Systems Engineering | RationalAutomate Document Generation Generate documents from templates Author templates with RPE DocumentStudio Configure and generate documents fromtemplates in Design Manager Create living design documents Rich text documents with embeddeddesign links Add to any design project Keep current as designs change Editable from the Web client All the features of Design Management:linking, change control, searching,commenting, and design reviews14
    • 15. © 2012 IBM CorporationSoftware and Systems Engineering | RationalDesign CollaborationCollaborating with Stakeholders in the Context of DesignsDifferent types of design collaboration may be required depending on theamount of formality required:Design Collaboration Ongoing stakeholderinvolvement in the designprocess. Starts early in the processand stakeholder input helps toshape the evolution of thedesign. Improve quality and gainstakeholder buy-inInformal Design Reviews Gather feedback fromstakeholders on a specific set ofdesigns at a point in time suchas a milestone. Review occurs over a limitedperiod of time. Does not typically requireformal signoff on designs.Formal Design Reviews Obtain approval for designs oridentify issues that must beresolved before approval can begiven. Review occurs over a limitedperiod of time Requires tracking of formalsignoff on designs.FormalizationTime, effort, & costs increase
    • 16. © 2012 IBM CorporationSoftware and Systems Engineering | RationalDesign Collaboration Engaging team members in the design process with Web client access to designs Improve quality with in-context design collaboration through commenting and visual markup Automate manual and time consuming design reviews with a more guided process Comments can be posted and accessed from Web client and RSA desktop client
    • 17. © 2012 IBM CorporationSoftware and Systems Engineering | RationalAutomate Design Reviews Automate manual and time consuming design reviews Users notified via email of the review and access their reviews from the dashboard Design Manager tracks progress of design review Link review to Team Concert work items for more formalized approvalsWhoWhatWhen&Why
    • 18. © 2012 IBM CorporationSoftware and Systems Engineering | RationalDesigner Reviewer1. Designer modelssystem, and delivers toSCM1. Designer modelssystem, and delivers toSCM3. Reviewer logs on toweb, and examines thecurrent model.3. Reviewer logs on toweb, and examines thecurrent model.2. Models publishedto Design Manager2. Models publishedto Design Manager4. New Requirement isadded in RRC4. New Requirement isadded in RRC7. Model is synched onDM and reviewed7. Model is synched onDM and reviewedDemonstration Scenario – Lifecycle Integration5. User adds a WI basedon new Requirement5. User adds a WI basedon new Requirement6. Designer does theImplementation6. Designer does theImplementation
    • 19. © 2012 IBM CorporationSoftware and Systems Engineering | RationalDesign ManagementDesign Management is an ALM and discipline thatintegrates software and systems design into the lifecycleJust like requirements management, change &configuration management, and quality managementRational Software Architect and Rational Rhapsodyare IBM Rational’s industry leading software and systemsdesign solutionsDesign Management capabilities have been added toRational’s Rhapsody and RSA product families to enhancetheir design capabilities with new team collaboration andlifecycle capabilities
    • 20. © 2012 IBM CorporationSoftware and Systems Engineering | RationalNext Steps Ask questions RSA Community:https://www.ibm.com/developerworks/mydeveloperworks/groups/service/html/communityview?communityUuid=a8b06f94-c701-42e5-a15f-e86cf8a8f62e Design Management Community: http://jazz.net/projects/design-management/ Design Management articles and videos: https://jazz.net/library/#project=design-management Try it out: https://jazz.net/downloads/design-management/releases/4.0.2
    • 21. © 2012 IBM CorporationSoftware and Systems Engineering | Rational21 Last Updated: 24 August 2011© Copyright IBM Corporation 2011. 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 havethe 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 IBMsoftware. 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 capabilitiesreferenced 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 featureavailability 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 MachinesCorporation, in the United States, other countries or both. Other company, product, or service names may be trademarks or service marks of others.www.ibm.com/software/rational
    • 22. © 2012 IBM CorporationSoftware and Systems Engineering | RationalAcknowledgements and disclaimers© Copyright IBM Corporation 2012. All rights reserved.• U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.IBM, the IBM logo, ibm.com, Rational, the Rational logo, Telelogic, the Telelogic logo, Green Hat, the Green Hat logo, and other IBM products andservices are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. Ifthese and other IBM trademarked terms are marked on their first occurrence in this information with a trademark symbol (® or ™), these symbolsindicate U.S. registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registeredor common law trademarks in other countries. A current list of IBM trademarks is available on the Web at “Copyright and trademark information” atwww.ibm.com/legal/copytrade.shtmlOther company, product, or service names may be trademarks or service marks of others.Availability: References in this presentation to IBM products, programs, or services do not imply that they will be available in all countriesin which IBM operates.The workshops, sessions and materials have been prepared by IBM or the session speakers and reflect their own views. They are provided forinformational purposes only, and are neither intended to, nor shall have the effect of being, legal or other guidance or advice to any participant.While efforts were made to verify the completeness and accuracy of the information contained in this presentation, it is provided AS-IS withoutwarranty of any kind, express or implied. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, thispresentation or any other materials. Nothing contained in this presentation is intended to, nor shall have the effect of, creating any warranties orrepresentations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use ofIBM software.All customer examples described are presented as illustrations of how those customers have used IBM products and the results they may haveachieved. Actual environmental costs and performance characteristics may vary by customer. Nothing contained in these materials is intended to,nor shall have the effect of, stating or implying that any activities undertaken by you will result in any specific sales, revenue growth or other results.
    • 23. © 2012 IBM CorporationSoftware and Systems Engineering | RationalBack Up
    • 24. © 2012 IBM CorporationSoftware and Systems Engineering | RationalDesign ChallengesHowever, design tools often focus on the practitioner and lack team integrationTeams cannot easily share designs and get feedback from stakeholdersLinking designs to other lifecycle artifacts is difficult, leading to a lack of traceability andunderstanding of the impact of changesToo many tasks are tedious, manual, and inefficient such as:Conducting design reviewsCreating reports across multiple designs and lifecycle elements forspecifications, communication, regulatory compliance, and auditingUltimately this leads to teams working in silos,limiting the value designs provide to othersCustomers use design tools today to: Simplify application and systemscomplexity Analyze software and systems for defects,impact analysis, and potential reuse Document and communicate tostakeholders

    ×