Model Runway, Part 3 Design Best Practices at Blue Cross BlueShield
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

Model Runway, Part 3 Design Best Practices at Blue Cross BlueShield

on

  • 768 views

This is part 3 from the series: ...

This is part 3 from the series: https://www.ibm.com/developerworks/mydeveloperworks/blogs/669242b1-dd91-4d63-a08f-231314c793bb/entry/model_runway_see_the_latest_design_best_practices_at_bluecross_blueshield24?lang=en

Statistics

Views

Total Views
768
Views on SlideShare
738
Embed Views
30

Actions

Likes
0
Downloads
22
Comments
0

2 Embeds 30

http://www.podidoo.com 18
http://podidoo.com 12

Accessibility

Categories

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
  • Author Note: Optional Rational slide. Graphic is available in English only.

Model Runway, Part 3 Design Best Practices at Blue Cross BlueShield Presentation Transcript

  • 1. Good Design is Good Business Series (developerWorks)“Model Runway: Part 3”Design Best Practices at BlueCross BlueShieldGuest Speaker: Arman AtashiSenior Application ArchitectBlueCross BlueShield of North Carolinaarman.atashi@bcbsnc.com Host: Roger Snook IBM, Rational software WorldWide Enablement Leader, Mobile, Design, Agile, SOA +1.703.943.1170, RCSnook@us.ibm.com 2013 January 25 http://ibm.co/MEABT1 1
  • 2. Agenda• BRIEF Session 1, 2 Recap• M3 & TOGAF – Synergy – Concept Mapping – RSA Template• M3 Webstore Architecture Specification – Business Architecture – Information Architecture – Application Architecture• Framework Summary 2
  • 3. Application - Description• Problem Statement – A hosted eCommerce solution that provides product owners the tools they need to build an online business and sell their products online• Functional Requirements – System must allow customers to manage their product inventory – Customers make online purchases and products are delivered to the desired destination – System can only be accessed by authorized users – System must maintain information about products, customers, billing/shipping, & orders• M3 Webstore M3 Models – CIM • Domain Model • Use Case Model – PIM • Type Model • Component Model – PSM • Runtime Model 3
  • 4. Application – M3 Workflows 4
  • 5. Application - Framework Components Modeling Notation Integration Model M3 Framework Components ™MDA Principles and Disciplines Context for Enterprise Modeling Modeling Workflow View Aggregation Modeling Environment 5
  • 6. Agenda• Session 2 Recap• M3 & TOGAF – Synergy – Concept Mapping – RSA Template• M3 Webstore Architecture Specification – Business Architecture – Information Architecture – Application Architecture• Framework Summary 6
  • 7. Synergy TOGAF (The Open Group Architecture Framework) is a framework for developing an enterprise architecture TOGAF supports four architecture domains; Business, Data, Application, and Technology TOGAF ADM (Architecture Development Method) is a process for developing architectures and identifies eight phases/cycles 7
  • 8. Synergy M3 and TOGAF ADM complement each other in key areas The resources (models/views and framework) can be mapped to produce different types of architecture describing an overall Enterprise Architecture M3 models and views map on to the first four phases of ADM; A, B, C, and D 8
  • 9. Concept Mapping  M3 View Aggregation M3 UML package compositions constitute a generic model for enterprise architecture domains Enterprise Architecture Business Information Application Technical Architecture Architecture Architecture Architecture <<CIM>> <<CIM>> <<PIM>> <<PSM>> Domain Model Domain Model Component Model Data Model <<CIM>> <<PIM>> <<PSM>> <<PSM>> Use Case Model Type Model Data Model Deployment Model <<CIM>> <<PSM>> <<PSM>> Activity Model Data Model Runtime Model <<PIM>> <<PSM>> Service Model Deployment Model 9
  • 10. Concept Mapping  Enterprise Architecture Domains M3 Generic Enterprise Architecture Domains TOGAF Capability Architecture(s)Strategic Architecture Enterprise Architecture Architecture Segment Opportunities Vision Architecture(s) and Solutions Business Information Systems Technology Architecture Architectures Architecture Applications Data Architecture Architecture 10
  • 11. Concept Mapping  M3 Models & TOGAF ADM• Architecture Vision – Defines relevant stakeholders, key business requirements and the scope of architecture, and demonstrates how the vision responds to the requirements – Includes high-level M3 CIM and PIM Models• Business Architecture – Defines key business processes, business requirements ,and service strategy – Includes M3 CIM Models• Information Systems Architectures (Applications and Data) – Provides the blueprint for deployed systems showing their interactions and describes the structure of logical and physical data resources – Includes M3 PIM and PSM Models• Technology Architecture – Describes software and hardware infrastructure required to support the deployed application(s) – Includes M3 PSM Models 11
  • 12. Concept Mapping  Reference Guide TOGAF CIM PIM PSM ReferenceEnterprise Architecture ArchitectureArchitecture Vision Use Case Model Component Model Business Context [high-level] [high-level]Business Architecture Domain Model Service Model Domain Interaction Activity Model Context Use Case ModelInformation System Architecture Component Model Run Time Model ImplementationApplications Architecture Service Model ContextInformation System Architecture Domain Model Type Model Data Model Entity ContextData ArchitectureTechnology Architecture Run Time Model Technical Context Deployment Model 12
  • 13. RSA Template  Model Composition Similar to the other M3 RSA templates, M3 TOGAF is a distinct model (emx file) in RSA It consists of five UML packages reflecting the first four phases of TOGAF ADM 13
  • 14. RSA Template  Model Navigation  Each M3 TOGAF UML package includes a TOGAF right navigation bar  Information Systems Architecture is further divided into its perspective domains  Requirements Management may be linked to the requirements repository and/or documents 14
  • 15. Agenda• Session 2 Recap• M3 & TOGAF – Synergy – Concept Mapping – RSA Template• M3 Webstore Architecture Specification – Business Architecture – Information Architecture – Application Architecture• Framework Summary 15
  • 16. Business & System ActorsSource: M3 CIM Use Case Model 16
  • 17. System ContextSource: M3 CIM Use Case Model 17
  • 18. Key Use CasesSource: M3 CIM Use Case Model 18
  • 19. Buyer Use Case DiagramSource: M3 CIM Use Case Model 19
  • 20. Domain ModelSource: M3 CIM Domain Model 20
  • 21. Type ModelSource: M3 PIM Type Model 21
  • 22. Service Interfaces and OperationsSource: M3 PIM Component Model 22
  • 23. Data Access ComponentsSource: M3 PIM Component Model 23
  • 24. Service Components – External ViewSource: M3 PIM Component Model 24
  • 25. Service Components – Internal ViewSource: M3 PIM Component Model 25
  • 26. Deployment Module DependenciesSource: M3 PSM Runtime Model 26
  • 27. Server ArchitectureSource: M3 PSM Runtime Model 27
  • 28. Agenda• Session 2 Recap• M3 & TOGAF – Synergy – Concept Mapping – RSA Template• M3 Webstore Architecture Specification – Business Architecture – Information Architecture – Application Architecture• Framework Summary 28
  • 29. Methodology Summary Modeling Workflow Roles & Responsibilities RSA Model Project Templates UML Diagrams Used in Models Collaborator Owner Requirements Analysis M3 ModelsCIM  The Outside Specification Class CIM Level 1  Models describe the problem domain and business requirements Domain Model  Focus is UML behavioral Use Case Sequence modeling Use Case Model Activity Model Architectural Design ActivityPIM The Edge Specification PIM Level 2  Models specify supported and required, interfaces, Type Model components, and services Class  Focus is UML structural and Service Model interaction modeling Component Model ImplementationPSM  The Inside Component Class Sequence Deployment Specification PSM Level 3  Models describe software Runtime Model implementation and Package Deployment deployment for the selected Deployment Model computing platform  Focus is UML structural modeling Data Model State MachineISM  The Extension Class Package & State Machine Integration Levels ISM diagrams may be used in Enterprise Integration all models Specification Business CIM CIM Diagrams Diagrams  Models are subsets of CIM, PIM PIM PIM, PSM, and describe Interface Diagrams Diagrams supported levels of integration PSM PSM Platform Diagrams Diagrams 29
  • 30. A complete framework for enterprise modeling, integration, and architecture representation M3 MDA Models Enterprise Computation Independent Model (CIM) M3 IntegrationArchitecture Model Integration Specific <<EA>> Model (ISM) Business <<Integration Level>> Platform Independent Model (PIM) Business <<EA>> Information Service Model <<EA>> Application <<EA>> Platform Specific Model (PSM) Technical Modelin 3 ™ g Methodolo gy 30
  • 31. Thank You, Good Design is Good Business (developerWorks) http://ibm.co/MEABT1 Time (ET UPCOMING Webcasts Presenter Date USA) Good Design is Good Business: The Big Picture Roger Snook 2/7 12:15-1:15PM Good Design is Good Business: IBM and Design Karel Vredenburg 3/7 12:15-1:15PM Good Design is Good Business: SOA - Still Going Strong Claus Jensen, Roger Snook 4/4 12:15-1:15PM Good Design is Good Business: Design Management: Pictures are Worth…. Jean-Louis Marechaux 5/2 12:15-1:15PM Good Design is Good Business: DevOps: Deliver your production code faster Maneesh Goyal 6/13 12:15-1:15PM Good Design is Good Business: Mobile and Smartphone Apps Roger Snook 7/11 12:15-1:15PM Good Design is Good Business: Rational Software Architect Roger Snook 8/8 12:15-1:15PM Good Design is Good Business: Industry Models Accelerate Software Nick Norris, Roger Snook 9/12 12:15-1:15PM Good Design is Good Business: Business Design: SA and RSA Roger Snook, Steve Arnold 9/19 12:15-1:15PM Good Design is Good Business: Smarter Devices through MDD for realitime/embedded development Manohar Rao 10/4 12:15-1:15PM Good Design is Good Business: SysML & Industry Standards Irv Badr 11/14 12:15-1:15PM Good Design is Good Business: Rational Rhapsody Manohar Rao 12/5 12:15-1:15PM31 31