• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
System Architect and Rhapsody
 

System Architect and Rhapsody

on

  • 844 views

A mammoth presentation of slides outlining how SA and Rhapsody can connect

A mammoth presentation of slides outlining how SA and Rhapsody can connect

Statistics

Views

Total Views
844
Views on SlideShare
844
Embed Views
0

Actions

Likes
1
Downloads
0
Comments
0

0 Embeds 0

No embeds

Accessibility

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • As you can see, Corso does look at the IBM suite of Rational products from a holistic view. As our platform continues to mature, we will continue to expand additional enhanced integration between the solutions. If you have a specific request, we are happy to have those discussions at any time.
  • If I want to create links between data in diverse repositories and report across those links then the data would have to be imported into whichever repository the analysis had to be done within. These importers would have to be written specifically for the purpose. If an object in one repository was to be linked to another such that the target object could be opened in the target tool then again a specific point to point integration would have to be created.
  • The time
  • Mix of federated data and imported data

System Architect and Rhapsody System Architect and Rhapsody Presentation Transcript

  • © Corso 2013 System Architect and Rhapsody Martin Owen
  • © Corso 20132 Network Centric Systems • Architects/Systems Engineers need a common vocabulary/taxonomy for communication of network centric architectures • Architects/Systems Engineers need a standard language for analyzing, specifying, designing, verifying and validating systems • Functional Analysis provides an approach to defining operational needs and systems functionality
  • © Corso 20133 Why do we model? • We build models to better understand what we are developing. • We build models to communicate across the team and enterprise. • Modelling achieves four aims. Modelling – Helps us to visualize an enterprise or system as we want it to be. – Permits us to specify the structure or behavior of an enterprise or system. – Gives us a template that guides us in constructing. – Documents the decisions we have made. • We build models of complex enterprises and systems because we cannot comprehend such things in their entirety.
  • © Corso 20134 The Importance of Modelling Paper Airplane F-15 Fighter Jet Less Important More Important Floyd’s Barber Shop Sam Walton Founder of Wal-Mart
  • © Corso 20135 The Power of Modeling “...by relieving the brain of all unnecessary work, a good notation sets it free to concentrate on more advanced problems, and in effect, increases the mental power of the race.” Alfred North Whitehead British mathematician, logician and philosopher
  • © Corso 20136 Modeling makes the Impossible Possible Things are being created that are almost incomprehensibly ‗vast‘ in scale. –Millions of lines of code –Uncountable pounds of steel, glass, titanium and copper –Billions of dollars –Thousands of developers, thousands of users –Years of development time –Decades of useful product life –Global deployment and connectivity
  • © Corso 20137 Modelling makes the Impossible Possible • Models aid in understanding and communication of a problem and its solution – Model airplane to be used in a wind tunnel – Blueprint for a house – Schematic diagram for an electronics circuit • Modeling is a proven technique – Orders of magnitude cheaper than ―build-break-redesign‖ – Drawings document a single state and are inflexible • Models can be simulated – Allow ―what if?‖ analyses – Early verification and validation
  • © Corso 2013 Rationale and history • System Architect (SA) and Rhapsody are market leaders within their respective fields – SA : Enterprise architecture and SoS for mission level process and analysis – Rhapsody : Technical systems/applications and real-time, embedded software • Benefits – Allows to users to share and synchronize information across modeling tools – Avoids duplication errors – Reduces development time and cost
  • © Corso 2013 Embedded Systems Development SA / Rhapsody interface Data exchange ―Report‖
  • 10 System Architect/Rhapsody Interface• Optimizes workflow from high-level SoS missions, strategies and operations to detailed embedded systems and real-time software development • Users can easily transfer model information between the two products and more closely align development of embedded and real-time systems with defense missions and strategies • Generic approach supports different end user workflows from System Architect (MODAF) to Rhapsody (SysML or DoDAF) and data synchronization between solutions
  • © Corso 2013 Corso and IBM Rational Support of OMG and Industry Standards • Corso and IBM Rational is 100% committed to the OMG standards for UML, SysML, UPDM and BPMN • Corso and IBM Rational is 100% committed to industry Architecture Framework standards such as DoDAF, MODAF and NAF. • Corso and IBM Rational have been active contributors to these standards, taking part in working groups, submission teams and sponsoring OMG activities and events. This will continue in the future. Recent activities include: – Contributing and participating in tool interchange working group – Sponsoring SysML certification program – Co-chair for UPDM team • Corso and IBM Rational are members of the Open Group – Participate in standards such as TOGAF and ArchiMate
  • © Corso 2013 Overview • Products • Lifecycles • Requirements Management • Documentation and Publishing • Future tooling landscape
  • © Corso 2013 Products
  • © Corso 2013 Products • System Architect • System Architect XT • Rhapsody • DOORS • Change Management • Rational Design Manager • Rational Publishing Engine • Rhapsody Gateway
  • Modeling product portfolio and positioning • Rational System Architect – For EA to support planning, change and transformation of the business/organization and its supporting technology – For customers wishing to use IDEF0 for the basis of AF modeling – For customer wishing to model business architecture – Key customers: Government agencies, System Integrators, Financial Services, large commercial cos.  Rational Rhapsody  Architecture definition down to technical systems  Single tool for real time and embedded software  Desire to use UML and SysML as basis for AF modeling  Key customers: Tier 1 supplier and below EnterpriseArchitectureSolutionArchitecture Embedded systems development Plan  Rational Software Architect  Architecture definition down to systems  Single tool for net-centric software, oversight programs/portfolios, & IT apps  Desire to use UML as basis for AF modeling and SysML (via E+ plugin)  Key customers: PEO, Program Office/FSI Tier 1 supplier and below  Business arch. to technical arch. integration (PEOs, Program Offices) Information systems development Build
  • © Corso 2013 System Architect • Multi user repository • Integrates with RTC • Supports workspaces
  • © Corso 2013 Rhapsody uses CM • Subversion or Dimensions • Integrates with RTC
  • © Corso 2013 Strategic Planning •Demand Management IBM Rational Focal Point •Enterprise Architecture IBM Rational System Architect •Project Delivery IBM Rational Team Concert BPM Solution Tools WebSphere Business Modeler Microsoft Visio Solution Tools Rational Software Architect Rational Rhapsody Rational Design Manager Harvesting Tivoli TADDM Tivoli CCMDB Services Discovery WebSphere Services Registry & Repository Requirements Tools Rational DOORS Rational Requirements Composer / Manager Change Management Rational Change Rational ClearQuest Rational Team Concert Reporting & BI Rational Insight Rational Publishing Engine Cognos BI Data Tools InfoSphere Data Architect Corso’s Rational Tool Alignment View
  • © Corso 2013 Lifecycles
  • © Corso 2013 Lifecycle(s) • Copying v Linking • Traceability – URLs – Trace from SA to Rhapsody and vice versa • Workspaces • OSLC
  • © Corso 2013 Copying v Linking
  • 22 Transition Planning Architecture Governance ProjectfocusEnterprisewidefocus Strategy Planning Design and Delivery Change Initiatives: Projects Enterprise Architecture = “the city plan” Solution Design = “the buildings” Strategy = “the city’s purpose & goals” Technology Availability Business Opportunity Hierarchical View of The Enterprise – Directing Change toward Strategic Goals
  • 23 Report and adjust Understandstrategy andmotivation Analyze and prioritize Managetransformation Targets to meet Are we on track? Harnessing Change - Separate Enterprise Planning concerns from Solution Delivery concerns (different time scales => synchronous coordination, NOT round trip engineering)
  • 24 Designs& Constructs Models Building Blocks Guidance and reuse Enterprise Planning planning and organizing Enterprise Blueprints Architecture Building Blocks, Principles, Reference Models and PatternsSolution Delivery building and implementing Solution Models and Constructs Constructions of things Collections of things Dynamicinteraction Dynamic, viable interaction between planning and delivery
  • 25 Designs& Constructs Models Building Blocks Guidance and reuse Enterprise Planning planning and organizing Enterprise Blueprints Solution Delivery building and implementing Solution Models and Constructs Constructions of things Collections of things Dynamicinteraction Two kinds of building blocks Transition Targets Solution Accelerators
  • 26 2.1 2.1.1 2.1.2 2.1.3 latest repository target version FEEDBACK & UPDATE (no common ancestor) feedback compliance & possibly improved target possibly updated target version 1.4 1.5 1.6 set target Solution model changes (may or may not originate in the target set) Planning model changes from continuous evolution (may or may not originate in feedback from solution model changes) 1.7 Delivery (continuous) Planning (continuous) cascade updated target by inference Building Codes City Plan Skyscraper Target & Feedback – Architecture Governance Pattern
  • © Corso 201327 Light weight link based Enterprise Governance – EA/Systems example • People-centric : collaboration across tools • Cross tool visibility – many-to-many relationships • Tool assisted management – managed relationships • Light weight coordination (focus on synergies) Process Blueprint Systems Model Enterprise Architecture Solution Delivery Inference links Information Blueprint Architectural Principle ..… Systems Model Systems Model ..… ―I do not want to go to another tool !!!‖ syndrome 
  • 28 Planned improvement Process portfolio optimization Multiple projects #1: Systems insight #2: EA governance #3: Accelerate design of new systems Transition Planning Architecture Governance Enterprise Architecture = “the city plan” Portfolio baseline Link Link Read & clone Three key scenarios
  • © Corso 2013 Traceability
  • © Corso 2013 #1: Systems insight • Link via URL to System Architect model element – Diagram – Definition
  • © Corso 2013 #2: EA governance • Link to System Architect to published model from Rhapsody
  • © Corso 2013 #3: Accelerate design of new systems • Import into Rhapsody model content from System Architect
  • © Corso 2013 #1: Systems insight Technique: URL linking
  • 34 Planned improvement Process portfolio optimization Multiple projects #1: Systems insight #2: EA governance #3: Accelerate design of new systems Transition Planning Architecture Governance Enterprise Architecture = “the city plan” Portfolio baseline Link Link Read & clone Three key scenarios
  • © Corso 2013 What is a System Architect URL? • System Architect XT URL – Diagram – Definition • SA Information Publisher URL • PowerPoint slides stored at URI • Rational Publishing Engine URL
  • © Corso 2013 Places to store System Architect urls • Rhapsody hyperlinks
  • © Corso 2013 Linking from Rhapsody to EA • If using System Architect/XT, set up your System Architect encyclopedia as an enterprise encyclopedia • Copy link from System Architect/XT or Published output
  • © Corso 2013 Rhapsody ReporterPLUS • Reporting capability in built in Rhapsody – HTML export – URLs up to SA
  • © Corso 2013 Rhapsody Web Output
  • © Corso 2013 #2: EA governance Technique: URL linking
  • 41 Planned improvement Process portfolio optimization Multiple projects #1: Systems insight #2: EA governance #3: Accelerate design of new systems Transition Planning Architecture Governance Enterprise Architecture = “the city plan” Portfolio baseline Link Link Read & clone Three key scenarios
  • © Corso 2013 System Architect to Solution Design(Create Link) • Use System Architect URL property in definition editor to point at Rhapsody web output or • Use System Architect XT to create URL in property
  • © Corso 2013 SA to Rhapsody (Navigate Links) • Navigate via System Architect • Navigate via System Architect XT • Navigate via System Architect Published Output
  • © Corso 2013 #3: Accelerate design of new Systems Technique: Read and Clone
  • 45 Planned improvement Process portfolio optimization Multiple projects #1: Systems insight #2: EA governance #3: Accelerate design of new systems Transition Planning Architecture Governance Enterprise Architecture = “the city plan” Portfolio baseline Link Link Read & clone Three key scenarios
  • © Corso 2013 Read and Clone • Use Rhapsody mapping to create mapping between System Architect metamodel and Rhapsody metamodel
  • © Corso 201347 New Feature Highlights in Rhapsody 7.5.1 • Import all diagrams • Import multiple diagrams in one session • Diagrams are now created and populated automatically • Import all attributes • Avoiding element duplications • Dynamic selection of import map • Improved Import wizard
  • © Corso 2013 How it works …. Lets import a SA SV-1 Diagram into Rhapsody System Architect SV-1 Diagram Launch SA, and open your chosen project In Rhapsody choose tools > Import from System Architect 1
  • © Corso 2013 How it works (2) Now, select the SV-1 System Architect Diagrams to import. (Note a filter is in use here to only show selected SA DoDAF diagrams) 2 3 .. and then pick which package in Rhapsody you want the System Architect DoDAF artifacts imported to.
  • © Corso 2013 How it works (3) 4 The System Architect DoDAF artifacts now appear within the Rhapsody model browser. If you chose to import the definitions, by using the populate diagram feature in Rhapsody, you can quickly visualize and build the SV-1 diagram ….
  • © Corso 2013 How it works (4)
  • © Corso 2013 End user customization The ―map file‖ allows you to customize the default mapping of artifacts between System Architect and Rhapsody for flexible workflow. C:Program FilesIBMRationalRhapsody7.5.1AddOnProductIntegratorRhpSAMap.xml
  • © Corso 2013 System Architect – Rhapsody Mappings
  • © Corso 2013 Default Mappings
  • © Corso 2013 SA SV1 DODAF (Non ABM) to Rhapsody SysML This map imports the selected Rational System Architect SV1 diagram into a Rational Rhapsody SysML project.
  • © Corso 2013 SA DODAF (Non ABM) to Rhapsody DODAF This map imports the selected DODAF Rational System Architect encyclopedia contents as Rational Rhapsody DODAF elements. When using this map, all diagrams that are not explicitly mapped are imported as OV-1.
  • © Corso 2013 Customising the import map • You can add your own custom imports to the mapper • RhpSAMap.xml – Located in {Rational Rhapsody}AddOnProductIntegrator • Need an XML Editor
  • © Corso 2013 Structure of the Import Map • A MAP block starts and ends with MAP – Name is the map name – Default set to "Yes" indicates that a map is selected as the default for import operations. – Rhapsody_domain describes the Rational Rhapsody model type such as DODAF or SysML – SA_domain describes the type of Rational System Architect model being imported. – Description explains the purpose of the map file.
  • © Corso 2013 Required Blocks • For each imported type, the map has an element or relation block – element defines any model element (including diagrams) that is not a relation – relation defines any line in a diagram that connects two elements • Each element and relation block includes the following parameters: – SA_Type identifies the Rational System Architect source. – Rhapsody_Metaclass indicates the type of Rational Rhapsody element that results from the import operation.
  • © Corso 2013 Optional Parameters • You might want to use these optional parameters for the element and relation map entries: – Rhapsody_Stereotype specifies which stereotype is attached to the imported element, and if the stereotype is specific to a Rational Rhapsody profile – Rhapsody_Profile completes the definition. (Adding the Rhapsody_Profile automatically adds the profile to the resulting model.)
  • © Corso 2013 Attributes • To identify the characteristics of each element and relation, use the attribute keyword with these parameters: – SA_Property indicates the attribute type being imported. – Rhapsody_Field indicates the attribute type set in the Rational Rhapsody model. • An attribute block might use the SA_AttribType optional parameter. If this property is held as a collection in Rational System Architect, this entry contains the Collection keyword. • Default maps – A default map element block contains the SA_Type parameter set to "*" – A default map relation block contains the SA_Type parameter set to "*"
  • © Corso 201362 Limitations • No Incremental import • No Export to SA • Be aware of conceptual differences between System Architect and Rhapsody
  • © Corso 2013 Clone Summary • Provides a generic approach using a external mapping table to support different end user workflows – Out of the box solution available for SA (DoDAF) to Rhapsody (SysML) – Out of the box solution available for SA (DoDAF) to Rhapsody (DoDAF) – End users can customize mapping – Report can be produced from Rhapsody to assist with SA updates as needed (SysMLDataFlowInPackage.tpl). • Produces most data relevant to SV-6 • Provide data synchronizing with Diff/Merge. • Uses APIs for speedy sync • SA and Rhapsody already tightly integrated with Rational DOORS for requirements traceability • Available in the ―base‖ Rational Rhapsody today
  • © Corso 2013 Workspaces
  • © Corso 201365 Overview of EA lifecycle
  • 66 Architecture enables organisations to “do the right things right” Deployment & DeliveryProject Scoping Build Cycle DeploymentExternal Design InternalDesign Project Scoping Build Cycle DeploymentExternal Design InternalDesign Project Scoping Build Cycle DeploymentExternal Design InternalDesign Strategic Intent Project Prioritisation & planning "These are the projects we should do” "These are the projects we will do” “Here you are!” The Enterprise’s Architecture Smart Strategy Smart Planning Smart Design, Develop ment, Delivery “Do the right things” “Do things right” SOA principles & platform
  • 67 Architecture… more detail… “Are our target architectures still right?” “Are we still moving the right direction?” Strategic Delivery Project Scoping Build Cycle DeploymentExternal Design InternalDesign Strategic Intent Enterprise IT Architecture Functional Operational Enterprise Business Architecture Project prioritisation & planning "These are the projects we should do” Enterprise Transition Initiatives “These are our roadmaps” UPSTREAM EA: Identifying viable projects (including those that will use BPM) to help realise the enterprise architecture requires a good set of “models”, capable of portraying the overall “as is” and “to be” architectural landscape DOWNSTREAM EA: Ensuring projects can exploit the architecture’s “standard components” or building blocks, including those that are doing things the BPM way requires each part to be described and published in an easy-to-use, easy- to-find “catalogue like” format "These are the projects we will do” “Here you are!” Business & IT solution design Project Scoping Build Cycle DeploymentExternal Design InternalDesign Business & IT solution design Project Scoping Build Cycle DeploymentExternal Design InternalDesign Business & IT solution design "This is the way these systems should be designed” Architecture Governance "Are we designing these systems the way we said we want them done?”
  • © Corso 201368 The EA Lifecycle • Techniques involved – Enterprise Architecture Modeling (Strategy, Business Process, High Level Architecture, Services and Capabilities, Roadmaps, Organizations, Plans) – Documentation & Reporting • Change is… – Continuous, slower (than change in s/w development), medium-high approval cycle (governance) • Change i/f, Audit IDs, Refined ACL – Multiple plans and programs are proposed • The main output is an architecture blueprint – Recommendations – Constraints • How to transition and decide between blueprints – Timelines/Roadmaps – Costs TOGAF 9 ADM
  • © Corso 201369 The Implementation & Deployment Lifecycle• We can contrast EA with the implementation & deployment lifecycle • Change is … – Frequent, rapid, reviewed quickly, light-medium approval cycle – Multiple simultaneous changes made to the same artifacts as common practice • The main output is ―something that runs or executes‖ – Multiple branches could exist – ….as multiple releases exist • Construction Tools are involved – Debuggers, Compilers, Editors – Test Suites, Modeling, Deployment • Change Management tools – Bug trackers, Task management – Source Control and Configuration
  • 70 Architecture… with frequency of change… Model to Plan Model to Build Low Frequency Changes Merge (from various sources) Reviewed manually, often with extended team High Frequency Changes Automated Merge
  • © Corso 201371 The Enterprise Architecture Workspace
  • © Corso 201372 What is an Enterprise Architecture Workspace ?• A container of EA modeling artifacts – Spans across Definitions, Diagrams, Symbols etc (SA terminology) – Spans across domains (Business Modeling, Strategy Mapping, Network Diagrams, Organization charts etc) • The workspace is isolated for the purpose of a dedicated project, program etc – Changes done in this workspace will not affect the master blueprint – Once approved, changes can be rolled up into the master blueprint • A workspace can be ―baselined‖ – A frozen snapshot in time of the entire architecture • New workspaces can be created from a ―baselined‖ workspace – Spawn a new project with pre populated content • Changes in Workspaces can be associated with tasks or change request in a change tracking system
  • 73 EA Workspace Patterns EA 1.3 EA V 1.2  Development, Deployment  Program Timelines  Business Process Set Constrains & Define Guidelines EA 1.3 EA V 1.3 Collect and Incorporate Feedback Outsourcing InitiativeCompliance Program EA 1.3 EA V 2.0 Acquisition E. Opportunities & Solutions G. Implementation Governance F. Migration Planning H. Architecture Change Management E. Opportunities & Solutions E. Opportunities & Solutions G. Implementation Governance
  • 74 Workspace Y Workspace XTo Be – Alternative X “AS IS” vs. “TO BE” Scenario: Zoom in EA 1.3 EA 1.3 EA V 1.4 Outsourcing Initiative As Is To Be – Alternative Y EA 1.3 EA V 1.3
  • © Corso 201375 What a workspace is not… • It is not a User Interface (UI) filter – Use the ―views‖ feature introduced in SA 11.0 to organise browser tree – Static & Dynamic views should be used as UI filters • It is not a folder – Using workspace as a folder may bring about undesired results • Users cannot report across workspaces • Users cannot link/relate items across workspaces – Examples: • DO: Create a Workspace to modify the existing EA Repository in order to develop a proposal • DON‘T: Create a workspace describing the HR department and another for the Finance department – You will not be able to relate the HR manager to the Finance data base
  • © Corso 2013 Cross Workspace Tools • Compare – Diagram Overlay – Side by Side • Merge/Extract • Audit Trail and History • Change Management • Roll based access control
  • © Corso 2013 OSLC
  • Jazz: The Simple Premise • Standards define references (URLs), protocols, and how to represent standard information types such as pictures and movies • Extensible via plug-ins such as PDF viewers Observation The Internet and the web works quite well despite many types of information and a loose, distributed structure What if tool vendors defined standard ways to reference objects, standard protocols for accessing those objects, and standard ways to represent those objects in an extensible manner?
  • Open Services for Lifecycle Collaboration An initiative aimed at simplifying collaboration across the software delivery lifecycle © Markus Angermeier@aperto.de An open invitation to collaborate on a common integration architecture for software delivery  An architecture for sharing lifecycle resources  Described on Jazz.net through illustrative resource definitions, service implementations, and use cases  Inspired by Internet architecture  Loosely coupled integration with ―just enough‖ standardization  Common resource formats and services  Innovation from the Jazz technology platform Open Services for Lifecycle Collaboration Barriers to sharing resources and assets across the software lifecycle  Multiple vendors, open source projects, and in-house tools  Private vocabularies, formats and stores
  • © Corso 2013 Jazz: Three Steps to Jazz Internet Architecture 1. Simple URLs to reference resources – Whether a requirement, architecture building block, test case, or something else 2. Shared resource formats – Now that I can reference anything, what is it that I‘m referencing? – Resource representations are agreed-upon ways to represent specific resource types in XML 3. Shared resource services – Standard ways to access and query resources with provisions for security such as access controls, all based on RESTful Web Services Tool on Jazz Jazz Server Assets & Metadata in Resource Representation Form Produce & Consume Resource Representations RESTful Web Services Representational state transfer (REST) is a style of software architecture for distributed hypermedia systems such as the World Wide Web. (Wikipedia)
  • Models and Data: Traditional versus Jazz Traditional • Links within model frequently tool-specific • Format on disk just a serialized form of in- memory format • References into models managed by other tools determined by those other tools Jazz • Links within model are URLs • Format on disk is carefully chosen and well-understood XML resource representation • References into models managed by other tools are also URLs – Uniform referencing simplifies collaboration Model or Tool Data
  • Application Model References in Jazz Requirements Test Cases Projects Operations View Business Motivation All references are URLs, both intra- and inter-model. Traditional import and export of data for tool point-to-point integrations no longer necessary, greatly simplifying traceability and impact analysis and copied/duplicate data.
  • © Corso 2013 Change Management Using OSLC
  • © Corso 2013 Creating a Change Request
  • © Corso 2013 Review Change Requests CCM Task SA Explorer SA Explorer Diagram Rich Hover Over Link icon
  • © Corso 2013 Log Changes against CR New SA Toolbar Object history shows all changes and which CR they are made against Model updated as usual
  • © Corso 2013 Link Items to SA artifacts from CCM CCM tasks have a links tab Select SA objects to link to CCM Task Linked objects can be opened in SA XT
  • © Corso 2013 Sandwich Model
  • © Corso 201389 Where do Requirements Come From? • Many levels of requirements: – Organizational Goals – Business Requirements – Functional Requirements – System Requirements – Software Requirements • Requirements are linked to models – To represent the problem or solution domain – to verify that the models meet the specified requirements • Oftentimes, while modeling the business, you will elucidate requirements that you didn‘t have before
  • 90 Models Bridge Layers of Requirements System of Systems Perspective Needs (problem) Modelling layer Capabilities (problem/solution) Modelling layer Requirements (solution) Modelling layer Requirements (solution) Functional modeling Functional modeling e.g Goal / Usage modeling e.g. Functional modeling Capability requirements System Requirements Architectural Design Statement of need Functional modeling e.g. Performance modeling
  • 91 Cost/Benefit Requirements documents Business Requirements Vision/Mission Enterprise Architecture Requirements documents Requirements documents Product Reqs Requirements documents Requirements documentsPortfolio Req Balanced Scorecard Requirements documents Requirements documents Product Reqs Product Arch Models Bridge Layers of Requirements Business Perspective Modeling ModelingRequirements
  • Deliverables (assets) 92
  • © Corso 2013 Three views of traceability DOORS System Architect Rhapsody System Engineer View Enterprise Architect View Requirements Engineer View
  • © Corso 2013 Tools of choice • Architects and engineers can use their tools of choice to manage traceability • However, traceability between architectural elements and requirements is best done through DOORS when using more than 2 tools
  • © Corso 2013 Define roles • Enterprise Architect • Requirements Management • Systems Engineer
  • © Corso 2013 Rhapsody Gateway • Rhapsody Gateway (add on) – Take requirements in DOORs and import them into the Rhapsody browser • UML/SysML, DODAF, MODAF Profiles • Publish
  • © Corso 2013 Requirements in Rhapsody • Relationship is called <<trace>> • Go back to Gateway • Show Matrix View Requirements to
  • © Corso 2013 Reporting and Documentation
  • © Corso 2013 99 Enterprise Business and Enterprise Reporting and Analysis Reporting (Documentation) Rational Insight Rational Publishing Engine BusinessIntelligence System Architect Publisher Report Generator In Tool Reporting EAM Cross Solution (Extension to APM, ALM, software/service dev, etc) System Architect Analysis ―Powered by Cognos‖ Rhapsody ReporterPLUS
  • © Corso 2013100 Documentation: Rhapsody ReporterPLUS
  • © Corso 2013 Rational Publishing Engine (RPE) • Create documents from within and/or extract data from Rational DOORS and Rational Rhapsody, System Architect, ClearCase, ClearQuest, Quality Manager, Test Manager, Requisite Pro, XML data sources…)
  • Rational Publishing Engine (RPE) • Build, share and reuse templates • Use out-of-the-box templates and integrated preview capability for quick ROI • Leverage templates for industry standards • Create and modify templates using intuitive editing environment – Drag and drop capability – Powerful scripting language support (Javascript) with expression editor for ease of use Customizable document generation
  • © Corso 2013 Model Based Requirements (optional)
  • © Corso 2013 Graphical Abstraction
  • © Corso 2013 Conceptual Collaboration in Text Engineer 1: ―Ok. That‘s what we need to do: System A will pass message X to System B and that will change B‘s state to Running from what it was before which was Idle. When B changes to Running it will send back an message Y to A and then wait for 2 second and then go back to Idle. System A will have started in Idle also and will go to Running after B sends back event Z which happens after the 2 seconds before going to Idle. All this should happen in less then 5 seconds.‖ Engineer 2: “Huh ?”
  • © Corso 2013 Conceptual Collaboration using UML/OMG SysML Engineer 1: ―Here look at this Sequence Diagram.‖ Engineer 2: ―Ahhh, now I see!‖
  • © Corso 2013 Essential diagrams Functionality Discover and describe what your System shall do. Requirements & Use Case Diagram Architecture Design the Architecture of your System and evaluate Alternatives. Block Diagrams Interactions / Activities Define how your system shall react and validate this behavior. Sequence Diagram Executable Behavior Specify formal behavior and execute it to validate. Statechart actor_0actor_0 S ys tem usecas e_1 class_2 object_01 object_11 object_01 11 E NV role_0 m es s age_0()m es s age_0() m es s age_1() role_1 m es s age_2() m es s age_3() m es s age_1() m es s age_2() m es s age_3() state_0 state_1 state_2
  • © Corso 2013 UML/SysML standard notation Team-based collaboration Requirements Analysis & Traceability Key enablers for model-based systems engineering Automated device generation Rational® Rhapsody® MDD Customizable Documentation Generation
  • Models and Requirements • Models and Requirements complement each other • Diagrams help clarify understanding of requirements • Modeling can help identify gaps and misunderstandings • A formalized but flexible graphical notation enables expressive, ‗people friendly‘ diagrams • Easily visualize, model and validate requirements to avoid costly rework
  • © Corso 2013 Visualize, capture and trace requirements • Improve understanding of complex requirements with visualization • Enhanced communication for reviews • Trace requirements to design and implementation Requirement information generated in code Trace requirements to design
  • © Corso 2013 Visualizing requirements
  • Requirements coverage analysis
  • Requirements impact analysisRequirements Analysis & Traceability
  • Standards-based modeling ―Rhapsody is the leading UML 2.1 compliant solution for embedded systems. Reducing OEM development Costs and Enabling Embedded Design Efficiencies Using the Unified Modeling Language (UML 2.1)‖ Source: ―Reducing OEM Development Costs and Enabling Embedded Design Efficiencies Using the Unified Modeling Language (UML 2.0)‖, Embedded Market Forecasters • UML – Industry standard notation for representing designs • SysML – Extends UML to address needs of the systems engineer • Visualize: – Requirements – Structure – Behavior – Interaction – Constraints • Compliance: DoDAF, MODAF, AUTOSAR, etc.
  • 115 Introduction to SysML 1.0 Shows how System stakeholders interact with the System Use Cases group requirements Example: Use Case Diagram
  • Use Case Diagram – for managers 116 Shows how System stakeholders interact with the System Use Cases group requirements Introduction to SysML 1.0
  • © Corso 2013 Example 1: Level of Abstraction (Behavioral)
  • © Corso 2013 Example 2: Levels of Abstraction (Structural)
  • © Corso 2013 SysML adds flow ports to UML Specifies Interconnection of Parts Focus is on Usage Port Item Flow Parts Connector
  • © Corso 2013 SysML IBD 120 Specifies Interconnection of Parts Focus is on Usage Introduction to SysML 1.0
  • 121  Balancing trade-offs between often conflicting stakeholder requirements  Data held in models can drive external simulations and help with trade studies  Early model execution and simulation helps to reduce costs Speed Model-driven Systems Development enables concurrent analysis of multiple related requirements Example: Vehicle speed vs. fuel-economy If the requirement for fuel economy increases, the top speed of the vehicle will decrease Fuel economy
  • © Corso 2013 Graphical panels • Create mock-ups of the interface to effectively communicate intended design behavior to customers • Modify, monitor and analyze data values during simulation to help ensure that the specification is correct — early in the process
  • © Corso 2013 Simulation, execution & animation • Execute early in development to validate design and/or requirements • Identify and address errors early when they are less costly to fix
  • © Corso 2013 Requirements-driven testing • Automatic regression testing • Change impact and analysis • Dramatically reduce time in the testing phase reducing overall development costs Pass/Fail results will be linked back to the scenario (requirement) Traceability of results to tests maintained in Rhapsody Results of pass/fail can be synchronized with RM tool Represents the textual requirements
  • © Corso 2013 Collaborative working using models • Rhapsody supports direct CM integration • When integrated the main features of CM can be made accessed directly from the Rhapsody browser • Supports team-based workflows, including parallel development
  • © Corso 2013 Comparing Diagrams To view diagram differences right-click on the icon and choose ―View diagrams‖. Differences in the diagrams are colour coated.
  • © Corso 2013 The Future
  • Jazz: The Simple Premise • Standards define references (URLs), protocols, and how to represent standard information types such as pictures and movies • Extensible via plug-ins such as PDF viewers Observation The Internet and the web works quite well despite many types of information and a loose, distributed structure What if tool vendors defined standard ways to reference objects, standard protocols for accessing those objects, and standard ways to represent those objects in an extensible manner?
  • Open Services for Lifecycle Collaboration An initiative aimed at simplifying collaboration across the software delivery lifecycle © Markus Angermeier@aperto.de An open invitation to collaborate on a common integration architecture for software delivery  An architecture for sharing lifecycle resources  Described on Jazz.net through illustrative resource definitions, service implementations, and use cases  Inspired by Internet architecture  Loosely coupled integration with ―just enough‖ standardization  Common resource formats and services  Innovation from the Jazz technology platform Open Services for Lifecycle Collaboration Barriers to sharing resources and assets across the software lifecycle  Multiple vendors, open source projects, and in-house tools  Private vocabularies, formats and stores
  • © Corso 2013 Jazz: Three Steps to Jazz Internet Architecture 1. Simple URLs to reference resources – Whether a requirement, architecture building block, test case, or something else 2. Shared resource formats – Now that I can reference anything, what is it that I‘m referencing? – Resource representations are agreed-upon ways to represent specific resource types in XML 3. Shared resource services – Standard ways to access and query resources with provisions for security such as access controls, all based on RESTful Web Services Tool on Jazz Jazz Server Assets & Metadata in Resource Representation Form Produce & Consume Resource Representations RESTful Web Services Representational state transfer (REST) is a style of software architecture for distributed hypermedia systems such as the World Wide Web. (Wikipedia)
  • Models and Data: Traditional versus Jazz Traditional • Links within model frequently tool-specific • Format on disk just a serialized form of in- memory format • References into models managed by other tools determined by those other tools Jazz • Links within model are URLs • Format on disk is carefully chosen and well-understood XML resource representation • References into models managed by other tools are also URLs – Uniform referencing simplifies collaboration Model or Tool Data
  • Application Model References in Jazz Requirements Test Cases Projects Operations View Business Motivation All references are URLs, both intra- and inter-model. Traditional import and export of data for tool point-to-point integrations no longer necessary, greatly simplifying traceability and impact analysis and copied/duplicate data.
  • © Corso 2013 What is OSLC and Jazz • OSLC (Open Services for Lifecycle Collaboration) – A standards based initiative aimed at simplifying collaboration across the software delivery lifecycle • IBM® Rational® Jazz® is a new technology platform for collaborative software delivery – For global and distributed teams • Jazz is designed to transform how people work together to build software, making software delivery more collaborative, productive, and transparent – Extensible framework that dynamically integrates and synchronizes people, processes, and assets
  • What is Jazz? www.jazz.net Innovation A major investment by IBM to create a scalable, extensible team collaboration platform Community Jazz.net – an online venue for open commercial development of the Jazz platform and Jazz-based products. Vision Our vision for the future of software delivery -- supporting diverse types of teams and a workforce that is increasingly organizationally and globally distributed, fluid and dynamic. Evolution Many Rational products will evolve to support the Jazz technology platform over time, bringing a host of next-generation capabilities to the Rational Software Delivery Platform. Jazz is a vision for integrating work across the software lifecycle, and a technology platform designed to enable that vision
  • Jazz: The Simple Premise • Standards define references (URLs), protocols, and how to represent standard information types such as pictures and movies • Extensible via plug-ins such as PDF viewers Observation The Internet and the web works quite well despite many types of information and a loose, distributed structure What if tool vendors defined standard ways to reference objects, standard protocols for accessing those objects, and standard ways to represent those objects in an extensible manner?
  • Open Services for Lifecycle Collaboration An initiative aimed at simplifying collaboration across the software delivery lifecycle © Markus Angermeier@aperto.de An open invitation to collaborate on a common integration architecture for software delivery  An architecture for sharing lifecycle resources  Described on Jazz.net through illustrative resource definitions, service implementations, and use cases  Inspired by Internet architecture  Loosely coupled integration with ―just enough‖ standardization  Common resource formats and services  Innovation from the Jazz technology platform Open Services for Lifecycle Collaboration Barriers to sharing resources and assets across the software lifecycle  Multiple vendors, open source projects, and in-house tools  Private vocabularies, formats and stores
  • © Corso 2013 Jazz: Three Steps to Jazz Internet Architecture 1. Simple URLs to reference resources – Whether a requirement, architecture building block, test case, or something else 2. Shared resource formats – Now that I can reference anything, what is it that I‘m referencing? – Resource representations are agreed-upon ways to represent specific resource types in XML 3. Shared resource services – Standard ways to access and query resources with provisions for security such as access controls, all based on RESTful Web Services Tool on Jazz Jazz Server Assets & Metadata in Resource Representation Form Produce & Consume Resource Representations RESTful Web Services Representational state transfer (REST) is a style of software architecture for distributed hypermedia systems such as the World Wide Web. (Wikipedia)
  • © Corso 2013 The Federated World • In the old days… Purpose Built interfacesCopy data to the analysis repository
  • © Corso 2013 The Federated World • In the new world of Jazz… Strategic Planning Platform DesignsRequirements Enterprise Architecture Projects Standardised interfaces using web technologyMake links between objects Links contain reportable data in a standard format Links are URLs
  • © Corso 2013 ??? The Federated World • Reality in the new world of Jazz… Strategic Planning Platform DesignsRequirements Enterprise Architecture Projects Reporting and analysis of federated data ??? ??? Non Jazz connected repositories imported into a Jazz connected repository
  • Ideas/Initiatives References in Jazz Requirements Architecture Projects Operations View Business Motivation All references are URLs, both intra- and inter-model. Traditional import and export of data for tool point-to-point integrations no longer necessary, greatly simplifying traceability and impact analysis and copied/duplicate data.
  • Tools collaboration based on middleware services Built on an extensible platform common repository Tool B Tool C Tool D Tool E Tool F Team Collaboration Services Tool ATool A
  • Strategic Planning Platform Enterprise Architecture Tools System Architect CMDB (Tivoli or not) Customer Data (DB2 or not) Other Corporate Data Corso Elements Federation BPM Solution Tools WBM/WID+ Information Management Solution Tools RDA+ Appl. Design & Construction Solution Tools Design Manager Technology & Deployment Solution Tools Requirements Tools Req Composer RequisitePro DOORS RAM on Jazz Asset Governance Jazz JRS Repository Replication Jazz JRS Repository EA Assets Solution Assets Federating Jazz Collaboration Platform Business Intelligence Cognos Family CUBI Read EA documents, consume architecture building blocks, create solution assets Principles, guidelines, views of infrastructure, processes, services, data, applications IBM Tools Centric View of SPP Portfolio Management Tools Focal Point Initiatives, Marke t Data, Plans, Sch edules, Priorities Socialization Corso Social Yammer Twitter LinkedIn Others Change and Configuration Mgt Team Concert
  • System Architect and Jazz: Interim Steps (an example) • For some heritage tools, Jazz is a journey… • SA must translate assets from its repository into resource representations • SA presents a REST API for other tools to access – Other tool should be able to dereference a URL that resolves to an SA repository – The dereference is received by SA, which returns a resource representation for the referenced item SA Repository System Architect Assets & Metadata in SA Form Produce & Consume Resource Representations Tool on Jazz Jazz Repository Assets & Metadata in Jazz Form Produce & Consume RESTful Web Services RESTful Web Services API
  • © Corso 2013 How does jazz help EA to Solution Delivery? • The process requires – A number of roles using different products. – Information to be joined between products • Jazz allows – User interface standards and mash up technologies to provide workbenchs for roles that are product independent. – Information to be joined Collaboration with boundaries Good user experience
  • © Corso 2013 Rational Design Manager and Rhapsody • Export – Indexed takes a while • Actively Managed – Model is stored on Design Manager – Indexed on Fly • Design Manager (SSC) installer – get from Jazz.net • Design Manager web client