Integrated Analytical Framework Overview

Document Sample
Integrated Analytical Framework Overview Powered By Docstoc
					SOA ,Technical Risks,
and Emerging Standards
             An examination of the relationship
             between SOA, the conceptual integrity
             of required of the attributes, and the
             associated impacts
Victor Harrison
Partner, Federal Consulting Practice
Computer Sciences Corporation




                           Anyone who isn’t confused really
                           doesn’t understand the situation.
                                           - Edward R. Murrow


                                                     7/29/2012 2:03:18 PM 5864_ER_WHITE.1
THE ASSERTION
                                                                                                                     Component “A” Service          Component “B”
                                                                                                                                   Registry
                                                                                                                                Publish   Publish

                                                                                                                                  Find     Find




                                                                                                                                     Dynamic
                                                                                                                                      Bind




                                                                                                                             2005 – Today
                                                                                                  Late 90s -                     SOA
                                                                                                 Early 2000s
                                                                                                                      BPEL, BPMN, Business
                                                                                                 Component/           Rules, SOAP, WSDL, Reuse,
                                                                        `           90s           Distributed         WS Specifications, C#, J2EE

                                                                                (mid-late)       Applications
                                                                                                 Components, CORBA, J2EE, DCOM, EAI, Analysis
                                                                   90s           Object
           XXXX   1234567   YYYYYYYY   ZZZ




                                                                                                 Patterns, WWW, XML, Agile Development, .NET,
           XXXX   1234567   YYYYYYYY   ZZZ

           XXXX   1234567   YYYYYYYY   ZZZ
           XXXX   1234567   YYYYYYYY   ZZZ...

           XXXX   1234567   YYYYYYYY   ...




                                                                                                 Workflow, Domain Modeling, MDA, Web Services,
                                                               (early-mid)                       BPM, UDDI
                                                   80s        Client/Server     Java, Design Patterns, Internet, Web Browser, HTML, Layers/Tiers,
                                                Interactive                     RUP, UML, Use Cases, COM, Iterative Development
          70s
                                                              Objects, Smalltalk, C++, OLE, Information Modeling, Reuse
         Online
                                                Workflow (Imaging), Relational Databases, PC’s, Rule-Based Systems, TCP/IP
60s
Batch    Transactions, Unit of Work, C, Structured Programming

Mainframes, Data Separated from Program, Waterfall Development

                                                                                                                             7/29/2012 2:03:18 PM OMG SwA Presentation. 2
THE BIG DEAL



  • Consumers are now in the Driver Seat, not the Producers


  • Buy by the Drink, not by the Keg


  • Autonomous Deployment


  • Concurrent Delivery


  • Continuous Evolution of Capability

                                                    7/29/2012 2:03:18 PM OMG SwA Presentation. 3
THE      Portfolio                                                                Foundations                           Engineering and Architecture
BIG     Management                                                                             Service Oriented
                                                                                                                                                       Frameworks
                                                                                                                                                                                   Systems of
                                                                                                Architectures                                                                       Systems
PROBLEM                                                                                                                                  Needs,
                                                               Visions, Objectives, Priorities
                                                                                                                                        Objectives
Legend                                                                                                                                  Principles

         “A” depends                                                                                                                                                              Case Study &
 “A” upon “B” for      “B”                                                                     ITIL Repository                        Design Basis
                                                                                                                                                                                    Example


                                                                                   Specification                                                     Railhead
                                                                                       Basis                                                           Lifecycle
                               Capabilities,
                                                                                                                                                      Methodology
                               User Stories

                                                                                                    Capability &                                               Establish       From RPO, SCD BPR, NCTC Ref
                                                                                                   Requirements                                               Capabilities       Arch., Constraints Doc. Etc.




                                                    1. Metadata and Semantics
                                                                                                                        Performance                                  Extend/ Specialize
                                                                                                    Information           & TPMs                                     SCD Target Arch.
                                                                                                       & Data


                                                                                                                    Its not
                                  Target                                                                                                                 Develop overall         Add IDP Detail plus
                               Architecture                                                                                                                  Model                    Features.
                                                                                                                        System
                                                                                  Business           Service                                                                                   Planning
                                                                                                                      Architecture
                                                                                  Processes         Component                                                                                 Architecture
                                                                                                                     Requirements
                                                                                                                                                          Build Features          Describe
                                                                                                                                                                                 Deliverable          Identification



                                                                                                                   Just One
                                                                                                                                                               List               Features.           of Features
                                                                                                                                                                                                      and Services to
                                Partitioned Basis                                                                          Assembly &                               Priority, IDP                     INCREMENT
                                                                                                     Interfaces                                                     association, and Tech.            and SPRINT
                                       for                                                                                 Deployment
                                                                                                                                                                    Dependencies.
                               Incremental                                                                                                                                                     Transition
                               Architecture                                     TOGAF/MDA View-based Specification Profiles                              Plan by Feature
                                                                                                                                                                                              Architecture
                                                     Management and

                              Value-derived and
                             Technology balanced
                                  planning
                                                                                   Governance
                                                                                                        Tailoring
                                                                                                       Framework
                                                                                                                   Problem  Integrated
                                                                                                                                                 Feature
                                                                                                                                                 allocation



                                                                                                                                                     Detail
                                                                                                                                                              Design by
                                                                                                                                                               Feature
                                                                                                                                                                                                     FEATURES to
                                                                                                                                                                                                     Open Source
                                                                                                                                                                                                     Implementation
                                                                                                                                                                                                     Specification

                                                                                Embedded                                                             Design        Implementation
                                                                                                       Agile PMP &         Master Plan &                           AoA and                  Implementation
                                                                                Governance                SEMP                                       Approach      Assembly                   Architecture
                                                                                                                             Schedule
                                                                                                                                                         Build by Feature
                                                                                Delivery for          Sprint-Based         Based                                                                     System
                                 Priorities &
                                                                                                     Delivery Control      Upon                                              How-to Build            Blueprint
                              Increment Plans


                                                    SPRINT       Managed                                                                                 Plan         Execute           Build
                                Operational                        by
                                Capabilities        Based Delivery                                                                                      Features




                                                                                                                                                                               7/29/2012 2:03:18 PM OMG SwA Presentation. 4
THE
JUNGLE




         See innoq.com for this chart
                                   7/29/2012 2:03:18 PM OMG SwA Presentation. 5
Agenda


  • Going Beyond a Definition of SOA – The Capabilities

  • SOA– The Problem of Evidence and Trust

  • The First Step: Characterize SOA – Views, Attributes, and
   Evidence

  • Conclusions




                                                     7/29/2012 2:03:18 PM OMG SwA Presentation. 6
Going Beyond a Definition of
SOA


The Characteristics




                         7/29/2012 2:03:18 PM 5864_ER_WHITE.7
No wonder SOA is so
confusing
     • There are Hundreds of SOA Definitions. Some
       emphasize –
        – Behaviors (A SOA delivers late binding and loosely coupled … )
        – Componentry (A SOA utilizes service registries, Interfaces, …)
        – Standards (a SOA is a set of web services that …)
        – So on and so on and so on…
     • Depending upon Point-of-View, Services of a SOA can
       be—
        – Pure business capabilities (Removing snow or ingesting a signal)
        – Software things (the Registry Service , logon Service, etc.)
        – Infrastructure things (amount of disk, CPUs, or networks)




           This is not another ‘this is what SOA is’ Workshop.

                                                              7/29/2012 2:03:18 PM OMG SwA Presentation. 8
Adopting the OMG’s
Harmonized SOA Definition
     • a SOA is an architectural style for a community
       of providers and consumers of services to
       achieve mutual value, that:
        – Allows participants in the communities to work together
          with minimal co-dependence or technology
          dependence
        – Specifies the contracts to which organizations, people
          and technologies must adhere in order to participate in
          specific communities
        – Provides for business value and business processes to
          be realized by the community
        – Allows for a variety of technologies to be used to
          facilitate interactions within the community”




                  But does this answer the question:
     How do you know a design is complete/incomplete or good/bad?
                                                             7/29/2012 2:03:18 PM OMG SwA Presentation. 9
A first step: Specify SOA
Capabilities necessary to
enable dynamic architectures
   Capability         Description and Design Principles                                      How Applied
 Late binding      The resolution of a service request as late as possible   Service Proxies; reflexive bindings, service
                   during execution.                                         registries, COIs
 Loose coupling    The low degree of mutual interdependence between          Data adapters, SOAP messages, generalized
                   components.                                               Metadata repositories
 Discrete          The specification of each method of a component is        SPRINT planning based upon which operations
 functions         independent of all other methods.                         are to be delivered, when.

 Service           Query, browse, offer, and select operations for           Short term: Service Proxies; long term:
 Discovery         specifying operations to satisfy a specific request.      “behavioral browsing”, reflection.

 Autonomous        The ability to deploy components and interfaces into      Our SCRUM-based delivery process.
 deployment/       production with minimal constraints on how, when, or      Usage of Service Delegates, Facades, and
 maintainability   how often the deployment occurs.                            Proxies.

 Message-Based     The usage of event-generated messages from                SOAP based message formats for the data
 Integration and   autonomous components to dynamically form                 packets; deep crawling; COIs and application
 Interaction       application contexts; Support for mediated and non-       specific ‘ontologies’; Support for mediated and
                   mediated messaging from all types of connected            non-mediated synch, asynch & pub-sub
                   services                                                  messaging.
 implementation-   Not associating a service with a specific set of          Interfaces abstraction, environment dispatching
 neutral           programming languages or implementations                  between enclaves; SAML

 Coarse grained    Design and selection of enabling components               Product-centric nature of delivery –each IDP
 components        represent classes of business entities.                   deliverable is a product.

 Dynamic service   Dynamic formation of a process or a service from          Usage of Orchestration (BPEL) to enable
 collaborations    autonomously defined and deployed services.               processes and Choreography (WS-CDL) to for
                                                                             composite services.

                                                                                                      7/29/2012 2:03:18 PM OMG SwA Presentation. 10
Capabilities necessary to
enable emergence and
conjunctive composition.
   Capability         Description and Design Principles                                                How Applied
Service contracts    The basis for finding and delivering a service that        Metadata defined application contexts represented
                     ‘fits’ by containing a detailed specification of actions   by model for information collection and COI
                     to be performed and data to be provided.                   specification.
Dynamic Process      Processes are created as dynamic service                   Dynamic (temporal and event driven) as well as pre-
Formation            collaborations (above) that result in time-dependent       defined process support via metadata description,
                     sequences that satisfy specific objectives.
Composite            Associations of services in a stateless and peer-to-       Best-practice formation of services to deliver IDP-
services             peer collaboration to satisfy a specific capability.       specified capabilities

Application-         Services are not designed to presume a specific            Usage of Facades, Delegates, Factories, and
neutral design       application context, but have application context          Containers; Interface Facades brokers.
                     imported as metadata during execution.
Consumer &           Metadata driven access/usage needs (consumer               Session objects of metadata. Ontologies registered
Provider Metadata    metadata) matched to provider description of               in service registry, Metadata usable by all services.
                     service (provider metadata).
Concurrently         Components, interfaces, and data are all capable of        Value-drive and feature based SPRINT planning
developed            being developed in parallel.                               with concurrent execution.

Interoperable in a   Components (1) exchange and use self-describing            Usage of Service Proxies, Adapters, Dispatching
heterogeneous        data (2) discover and then accept/post operational         Services between enclaves, SAML-based
environment          requests to components irrespective of how or              entitlement and attribute access; dynamic and static
                     where the components are enabled.                          COIs.
Reusable artifacts   Reuse is a measure of shared elements by,                  Support for design time reuse (e.g., shared library of
                     minimally, reuse of a service interface’s signature.       source and linkable objects as well as runtime reuse
                                                                                by the delivery of autonomous services.
Addressable          Means anyone, or any component, that is anywhere           Federated and replicated registries across domains;
Network Space        in the network addressable space should be able to         Dispatch services; Proxies for cross domain
                     participate in a service collaboration.                    services access.            7/29/2012 2:03:18 PM OMG SwA Presentation. 11
Evidence and Trust


The Problem with Dynamic architectures and enabling conjunctive
behaviors




                                                             7/29/2012 2:03:18 PM 5864_ER_WHITE.12
But there are Questions and
Problems

  • “Trust is established based upon sufficient and credible evidence
    leading to belief that the entity in some system context satisfies the
    specified requirements”
     – Which Requirements? The ones when the service was built, or the ones
       driving the selection of a Service for usage?
     – What, exactly, is THE SYSTEM that satisfies the requirements?
  • Which capabilities should a SOA Design include?
  • How do you deal with the multiple viewpoints regarding what the SOA
    characteristics are—
     – SOA describes business behaviors (emergence, interoperability, etc.)
     – SOA is a collection of behavioral characteristics (late binding, conjunctive,
       etc.)
     – SOA is a collection of artifacts (registries, metadata, contracts)
  • How do you design, or measure, when there is no commonly
    accepted basis for what a ‘good’ SOA design should contain?



                                                                         7/29/2012 2:03:18 PM OMG SwA Presentation. 13
And More Questions and
Problems


  • What specific threats are introduced by the addition of a SOA
    architecture and what are the specific services and protection points to
    address those threats?
  • What has to be added to the physical environment to ensure SOA
    security, given the above?
  • What can be reused, maybe with additions or adjustments, in the
    physical environment to ensure SOA security, given the above?
  • What references can be used to certify and accredit SOA services
    before they are added to ensure adequate security has been
    addressed?
  • What metric or monitoring can provide an indication of how well I'm
    securing the SOA?
  • What will the service provider, the infrastructure and the client be
    responsible for providing to secure the SOA?
  • How will authorizations be applied when authorization repositories must
    be accessed across domains?

                                                                7/29/2012 2:03:18 PM OMG SwA Presentation. 14
And yet more …
  • How will data encryption be handled in the service-oriented
    architecture?
  • How will SOA security 'fail over' for those services that don't/can't react
    to the SOA paradigm?
  • If services can be pulled from 'anywhere', how do we restrict service
    requests to only pull 'approved' service for the data sensitivity level?
  • How will SOAs perform in areas of limited bandwidth? (front line,
    wireless, dial up, etc)
  • How will the metadata attributes attached to a service be inseparable
    from the service?
  • How will the service repository be “self protecting”? What are the
    requirements for the repository? (Higher than the resulting network?)
  • How will the transformation be handled? (Specifically, how to manage
    and secure a GIG which is evolving and only partially SOA-compliant?)
  • What does a cross-domain service require of another service to
    accomplish information sharing across domains?
  • How will we maintain Situational Awareness of SOA functionality and
    performance?
                                                                   7/29/2012 2:03:18 PM OMG SwA Presentation. 15
Each Dynamic Architecture
Capability presents a
Challenge

       SOA Capability                                         Challenges
  Late binding                Processes are formed dynamically therefore never completely sure what
                              services will participate
  Loose coupling              Loose coupling / tight coupling balance; the more loosely coupled the less
                              deterministic the design.
  Discrete functions          Implies method level authentication / authorization, not Component or
                              Implementation level
  Service Discovery           Policy Enforcement Point and context selection; runtime not design time
                              selection; includes software agents and humans as event triggers
  Autonomous deployment       Component “hot swap” requires sophisticated software and hardware design
                              that does plug-and-play. How do you assure hot swap component valid?
  Message-Based Integration   Focused on correlating simple and complex relationships of events based on
  and Interaction             past trends and future predictions. Must react to new, external input arriving at
                              unpredictable times. Temporal and event based validation of the service vector.
  Implementation- neutral     In Object Management Group (OMG) parlance, how do you IA certify the
                              Platform Independent Model (PIM) and the Platform Specific Model (PSM)
  Coarse-grained              Resolve the paradox with ‘Discrete Functions’; and ‘Application Neutral
  components                  Design’; Requires proper domain analysis of business processing and
                              ontology;
  Dynamic service             What represents a ‘valid’ orchestration? PeP has to validate the collaboration
  collaborations              and service vector.


                                                                                           7/29/2012 2:03:18 PM OMG SwA Presentation. 16
And each Emergence &
Conjunctive Capability has a
challenge, too

           Capability                                         IA Challenges
   Service contracts            Designing and defining voluntary agreements that mutually bind the
                                participants to authorizations, obligations, and modes of interaction.
   Dynamic Process Formation    Determine the value proposition and rights of the consumer; identifying and
                                assembling services that will form a virtual service for the end consumer.
   Composite services           Centralized reuse repository and effective reuse management; what
                                represents a valid composition
   Application-neutral design   Proper domain analysis, and good ontology specification and management


   Consumer & Provider          How do you authenticate and authorize to Metadata? Proper domain
   Metadata                     analysis, and good ontology specification and management

   Concurrently developed       Application context in the metadata, not the software component – how do
                                you authenticate and authorize to Metadata?
   Interoperable in a           How do we assure the origin and content of self-describing data; how do we
   heterogeneous environment    know that the right context is being applied?

   Reusable artifacts           Centralized reuse repository and management but how is registration for
                                usage validated?
   Addressable                  What represents the ‘network addressable space?” How do we bridge air
   Network Space                gaps? Service Replicas? How do we assure they are safe?




                                                                                            7/29/2012 2:03:18 PM OMG SwA Presentation. 17
A Reference Implementation
for a Secure SOA from CSC–
Why is this ‘correct’?

                                               Does this
                                               accommodate                                                 1. Provider registers service
                                                                                                              (independent action, but done prior
Service Provider                               all the SOA                                                    to access)
                                                                                                           2. Consumer requests Service
                    9    HTTPS                 Capabilities?                                               3. System performs Registry lookup
                          XML
                         WSDL
                         SOAP                                                                              4. System can now route Service
                         SAML                  Web                                Enterprise                  Request in proper format
                            8    Firewall      Proxy                                Policy
         PEP                                              Policy Decision        Enforcement               5. Policy Enforcement Point redirects
      (SOAP Inter.)                                       6 Point                   Point                     message for Authorization check
                                 Encrypted /    WSDL
                        5
                                   Signed
              Web Service                                          SAML                                    6. Security Service sends an
                                               Register            Entry                                      Authorization Request to Federated
     Web
     Proxy
                                                                                                              Authorization source
                                                   1
                                  Request                                              7        Security   7. Federated Authorization source
                      WSDL                      WSDL
                                                                                               Databases      verifies ID, Role, Environment and
              Web                                          3                                       Auth.
              Proxy
                                 Firewall      Web UDDI            Certificate                     Subj.
                                                                                                              Service Authorization
                                               Proxy                                               Res.
                        SAML                                                                       Env.
                                                                                                           8. Federated Authorization source
Web Service
              4         SOAP                                   SOA Security Infrastructure                    sends Authorization Grant
       2                WSDL
                   10    XML                                                                               9. Service Provider accepts Service
                        HTTPS                                                                                 Request, processes request and
Consumer                                                                                                      returns Service
                                                               Source: Computer Sciences Corporation       10.Consumer receives Service
                                                                                                              requested


                                                                                                                             7/29/2012 2:03:18 PM OMG SwA Presentation. 18
A Reference IA Architecture
from the US Government–
Why is this ‘correct’?
          Operational
                User                                                       • Svc Arg 1
                                             • User Public Key                             • Results
                                                                           • Svc Arg 2
                                             • Calc Checksum
                                                                                              or                                                    Service A
                  User private key              and Encryption
                                                                           • Svc Arg N     • Denial                                               Policy Manager
          (for encryption and checksum)                                   • Public Key

                        • Validation
                                                       Authentication (Policy Enforcement Point)              Authorization Policy Mgr
                                       Service A
                                                               User ID                        Authorization
                    Service A private key                                                       Service
                                                                                                                 Policy Rules Service
                                                                                                                 AUT(Role)    F(Bus Obj)
                                          Public Key
                     User Attribute
                                                                   Physical Service A                            AUT(Org)     F(Bus Obj)
                                        Roles, D.P., Assign.        (Business Logic)                             AUT(D. P.)  F(Bus Obj)
                       Service
                                                                                                                 AUT(Assg)  F(Bus Obj)



                                                                         • Svc A Arg 1
                                         • Service A Public Key          • Svc A Arg 2     • Results
                                              • Checksum and                                  or                                                   Service B
 • Public Key                                        encryption          • Svc A Arg N     • Denial
                                                                           • Public Key                                                          Policy Manager


 Identity & Authentication
                                                       Authentication (Policy Enforcement Point)              Authorization Policy Mgr
          Service
                                       Service B
                               Service B                       User ID                        Authorization
                               private key                                                      Service
                                                                                                                 Policy Rules Service
                                                                                                                 AUT(Role)    F(Bus Obj)
 Certification                            Public Key
                     User Attribute                                Physical Service B                            AUT(Org)     F(Bus Obj)
  Authority            Service          Roles, D.P., Assign.        (Business Logic)                             AUT(D. P.)  F(Bus Obj)
                                                                                                                 AUT(Assg)  F(Bus Obj)



                                                                                          Source: DISA’s NECC Architecture Overview Systems Engineering
                                                                                                  and Integration Working Group, 15 Aug 2006
                                                                                                                                   7/29/2012 2:03:18 PM OMG SwA Presentation. 19
OASIS SOA Ontology–
Does this accommodate all
SOA Capabilities?




                            7/29/2012 2:03:18 PM OMG SwA Presentation. 20
The First Step: Characterize
SOA Characteristics Accurately


Establishing a Specification Basis




                                     7/29/2012 2:03:18 PM 5864_ER_WHITE.21
Views, Concepts,
Architecture Products, and
Representational Formats
                          View
                                                                       Example: Service Component View


                     1           -Point-of-View
                      *          -Characteristic

                     Concept
                                                                       Example: Component API

                                                   DODAF A.P.
                      *          -Knowledge                            Example: SV-6c & SV-4
                      *          -Descriptor

               Architecture Product                  RUP A.P.
                                                                       Example: Interface document artifact

                      *          -Contents
                                                   CSC Catalyst A.P.
                                                                       Example: Interface Control Document
                      *          -Rendering

              Representational Format                 UML
                                                                       Example: Parameterized
                                                                                Interface Class
                                                      IDEF
                                                                       Example: Mechanism
                                                                                        7/29/2012 2:03:18 PM OMG SwA Presentation. 22
One Effort: the TOGAF/MDA
Synergy Effort

                                     TOGAF/MDA
                                  Architecture Views
                        OMG MDA      Capabilities &
                         Models      Requirements

   TOGAF
                                   Business Process


                                  Service Components


                                       Interfaces
                                  System Architecture
                                     Requirements
                                      Deployment

                                  Performance & TPMs

                                  Sematics, Metadata

                                   Information & Data

                                       7/29/2012 2:03:18 PM OMG SwA Presentation. 23
Another Effort: the OMG
SOA UML Profile

                           SOA UML Profile
                          Architecture Views
                             Capabilities &
                             Requirements


                           Business Process


                          Service Components


                               Interfaces
                          System Architecture
                             Requirements
                              Deployment

                          Performance & TPMs

                          Sematics, Metadata

                           Information & Data

                               7/29/2012 2:03:18 PM OMG SwA Presentation. 24
The Objective: A View Based
Specification

                                            Capability and
                                            Requirements



                                                             Performance&
       Metadata and Semantics




                                            Information &        TPMs
                                                 Data




                                                                System
                                            Services and
                                Processes                     Architecture
                                            Components
                                                             Requirements




                                                                  Assembly &
                                              Interfaces
                                                                  Deployment
                                                                             7/29/2012 2:03:18 PM OMG SwA Presentation. 25
Relating the Viewset
to FEA and Kruchten
                          Added to
  Federal Enterprise      address BPMN              Integrated        Kruchten, RUP, EUP
  Architecture Views      outputs               Architecture Views    Architecture Views

                                                   Capabilities &           Use Case
                          Taxonomy
                                                   Requirements
                            Type
    Business Ref.      Operational Activities
                            and Tasks
                                                    Processes                 Logical
       Model
                                                    Service &
  Service Ref model     System Functions
                                                   Components
                                                                             Process
                                                     Interfaces
      Technical         Technical Standards System Architecture
                          and Technology       Requirements              Implementation
   Reference Model             Area             Assembly &
                                                    Deployment
    Performance            Performance                 PRM
   Reference Model         Parameters                                      Deployment

                                                Sematics, Metadata
   Data Reference          Information
       Model                Elements                                  Intelligence
                                                 Information & Data
                                                                      Knowledge
                                                                      Information
                       Added to document                                  Data
                       terms and concepts                                Signal

                                                                               7/29/2012 2:03:18 PM OMG SwA Presentation. 26
Relating the Viewset
to DoDAF
                                Integrated
              DoDAF         Architecture Views



                                Capabilities &
            Operational         Requirements
              View               Processes

                                 Service &
                                Components
            System View           Interfaces
                             Sematics, Metadata
                                                             Intelligence
                              Information & Data
           Technical View                                    Knowledge
                               Performance &                 Information
                                                                 Data
                                   TPMS                         Signal
                             System Architecture
                                Requirements
             All Views           Assembly &
                                 Deployment




                                                   7/29/2012 2:03:18 PM OMG SwA Presentation. 27
The Parts of a “Concept”
in this Model
 The concept has definition with
 terms such as actor-owner                               A concept expressed as a UML class
 (another Concept) or desirable
 outcome (a specific and
 measurable semantic) defined                                                                  Attributes of the
 in the model                                                                                  concept that must
                                                                                               be included in a
  Definition                                                                                   design
  A Capability is a discrete expression
  of a desired outcome that an Actor-
  Owner wants to see in a system.                                                              Actions that must be
  Capabilities are descriptions of                                                             supported by the
  behavior and for them to be                                                                  design
  unambiguous must be tangible and
  measurable
                                                                                                         Sometimes
                                                                                                         Concepts
                                                                                                         take specific
                                                                                                         forms (e.g., a
                                                                                                         Capability is
                                                                                                         either a
                                                                                                         Process,
                                                                                                         Function, or
                                                                                                         Goal)




                                          Sometimes a concept is composed of different things (e.g., a
                                          Function must have at least one goal)    7/29/2012 2:03:18 PM OMG SwA Presentation. 28
Capabilities and
Requirements View

                                     Capability and
                                     Requirements
         1. Metadata and Semantics




                                                          3. Performance&
   • Objective: clearly specify measurable
                                  5. Information &           TPMs (PRM)
     capabilities and relate constraining (I/DRM) Capabilities
                                     Data
     requirements to them.
   • Capability: Expression of a desirable
     outcome
   • Requirement: a constraints on                       8. System
     outcomes  4. Business         6. Service
                                                            Architecture
                  ProcessesBPMN
   • Uses the outputs of a             Component
                                                            Requirements
                  (BRM)                (SRM)       Requirements
                                                            (SAR)




                                      Interfaces               Deployment
                                         (IRM)                   (DRM)
                                                                       7/29/2012 2:03:18 PM OMG SwA Presentation. 29
Capabilities and
Requirements View:
Capabilities                A Capability is a
                            discrete expression
                            of a desired outcome
                            that a Stakeholder
                            wants to see in a
                            system. Capabilities
                            are descriptions of
                            behavior and for
                            them to be
                            unambiguous must
                            be tangible and
                            measurable




                     7/29/2012 2:03:18 PM OMG SwA Presentation. 30
Capabilities and
Requirements View:
Requirements


                     Requirements are constraints on
                     capabilities (behaviors) that limit
                     the domain of solution by providing
                     the provisioning definition
                     necessary for a particular
                     stakeholder viewpoint.




                                                           7/29/2012 2:03:18 PM OMG SwA Presentation. 31
Capabilities and
Requirements View:
Integrated
                                                                                                            Can reference and include other




   Requirement                                                                                                                     Capability
                                 Capabilities are constrained by requirements
(from Requirements)
              ...)                                                                                                                            ...)
                                                                                                                                (from Capabilities)
               +constraints and definitions                                                                        +desirable
                                                                                                                   behaviors




                                                                                                                                                                     Process
                                                                                                           is composed of other                                                ...)
                                                                                                                                                                 (from Capabilities)

                                                                                                                                     Fuction           is composed of
                                                                                                                                              ...)
                                                                                                                                (from Capabilities)      one or more

                                                                                                                                +Provider 1..n
                                                                                             Goal
                                                                                                          +justification is justified
                                                                                                      ...)
                                                                                       (from Capabilities)
                                                                                                           1..n                 by
                                                                                                                         satisfying
                                                              Conditions and states         Accepted Statement of
                                                               necessary for Goal                                  Expected acceptable outcomes
                                                                                             External         Value
                                                                  Acceptanace                 Events
                                                           GoalPreCondition           GoalEvent              GoalBenefit              GoalPostCondition
                                                           (from Capabilities)                   ...)
                                                                                  (from Capabilities) (from Capabilities)  ...)       (from Capabilities)



                                                                                                                                                                        workflow
     Mission Requirements        Infrastructure Requirements         Information Assurance Requirements                    Integration Constraints           System Effectiveness Requirements            Systems Assurance Requirements
      (from Requirements)             (from Requirements)                                                                   (from Requirements)                     (from Requirements)                              (from Requirements)
                                                                                Metric, threshold, objective value

                                                     Deployment Requirements              Mission Assurance Requirements                  Service Level Agreements                 Lifecycle Engineering Requirements
              Mission Enabling Requirements
                                                       (from Requirements)                      (from Requirements)                         (from Requirements)                            (from Requireme...
                   (from Requirements)




                                                                                                                                                                                                 7/29/2012 2:03:18 PM OMG SwA Presentation. 32
Semantics and Metadata
View

                                               Capability and
                                               Requirements



                                                                      3. Performance&
       Metadata and Semantics




                                               Information &            TPMs (PRM)
                                                     Data
                                                 • Objective: clearly specify the
                                                    Taxonomy and Ontologies of
                                                                                      Observations
                                                    the Problem Domain.
                                                 • Observation: A structured
                                                                      8. System
                                               6. Service classifying observable
                                                    way of
                                4. Processes                             Architecture
                                                  Component
                                                    items.               Requirements
                                                  (SRM)
                                                 • Ontology: The Taxonomy(SAR)
                                                    and context-specific
                                                    ontologies that the rest of the   Ontologies
                                                    views must abide by


                                                                             Assembly &
                                                Interfaces
                                                                             Deployment
                                                                                     7/29/2012 2:03:18 PM OMG SwA Presentation. 33
Semantics and Metadata
View: Integrated
                         ERD                                          Ontology
  Systems Engineering   Models                                        Subjects
       Semantics


                                            Data
   Mission/Business
                             This
                                          Element
      Semantcs           “classifies” a
                                                               Makes up an
                         Data Element
                                                                Ontology



                                                                         Value
                                                                        Domain




                                                    7/29/2012 2:03:18 PM OMG SwA Presentation. 34
Processes View

                                             Capability and
                                             Requirements



                                                                        Performance&
       Metadata and Semantics




                                            5. Information &                TPMs
                                                • Objective:
                                               Data (I/DRM) clearly specify
                                                   events and processes.             User Stories,
                                                • Scenarios & Vignettes: Event         Scenarios &
                                                   Sets and sets of use cases           Vignettes
                                             6. • Use Cases: One Event, One
                                                                     8. System
                                                 Service
                                Processes                               Architecture
                                                   Precondition, One Outcome
                                                 Component
                                                •(SRM) the specifications for
                                                   Drives               Requirements
                                                   what the system does –
                                                                        (SAR)        Use Cases,
                                                   Tasks become interfaces,          scenarios, and
                                                   Use Cases workflows, and              Tasks
                                                   Task specifications for rules

                                                                           Assembly and
                                             Interfaces
                                                                            Deployment
                                                                                    7/29/2012 2:03:18 PM OMG SwA Presentation. 35
Processes View:
Scenarios and Vignettes




A Thread is a partition of
Capability::Process into one or
more uniformly defined processes
that takes the associated
preconditions and event set and
transforms it into the post
conditions and associated benefit.

A Vignette is the partitioning of
the event set for a thread into
separate event set/pre-condition
sets.


                                     7/29/2012 2:03:18 PM OMG SwA Presentation. 36
Processes View: Use
Case
A Use Case represents the response to a single event resulting in a single benefit and having, on completion, a single PostCondition State.
   A Use Case Task is the
description of a step in the process
necessary to deliver an outcome
specified by the Use Case's Post
Conditions. It represents a
specification for a particular feature to
be performed in the application
context of the use case. In the case
of software-enabled tasks, it
represents the behavioral
specification for enablement by some
interface. Therefore, a use case task
relates to a single interface
specification, but interface
specifications may satisfy one or more
use case tasks.




                                                                                                                      7/29/2012 2:03:18 PM OMG SwA Presentation. 37
Processes View:
Integrated




                  7/29/2012 2:03:18 PM OMG SwA Presentation. 38
Information and Data
View

                                            Capability and
                                            Requirements



                                                                    Performance&
       Metadata and Semantics




                                            Information &               TPMs
                                                 Data


                                            • Objective: clearly specify how
                                               data and information is
                                                                         System
                                               designed for
                                             Services and a SOA.                Segmentation
                                Processes                             Architecture
                                            • Components
                                               Segmentation: Describes an
                                                                     Requirements
                                               ‘overlay’ on top of LDM for
                                               Services
                                            • Payload and Logical Data
                                               Components: Specifies
                                               information used by interfaces    Payloads and
                                            • Drives formation of interfaces      Logical Data
                                                                           Assembly &
                                               Interfaces
                                               and Services                       Components
                                                                           Deployment
                                                                                  7/29/2012 2:03:18 PM OMG SwA Presentation. 39
Information and Data
View: Segmentation




                       7/29/2012 2:03:18 PM OMG SwA Presentation. 40
Information and Data View:
Payloads and Logical Data
Components




                             7/29/2012 2:03:18 PM OMG SwA Presentation. 41
Performance and TPMS
View

                                    Capability and
                                    Requirements

  • Objective: clearly specify
    how the solution will be
                                                       Performance&
         Metadata and Semantics




    measures.                          Effectiveness
                                    Information &          TPMs
  • Effectivenss: How a
                                         Data
    capability and requirement is
    determined to be effective
  • Thresholds & Objective:
    minimum & Maximum
                                     Thresholds and       System
    expectations                    Services and
                                       Objectives
  • Drives how the solution will
                  Processes
                                    Components
                                                        Architecture
    be formed; not what the                            Requirements
    solution will do (the SAR)




                                                            Assembly &
                                      Interfaces
                                                            Deployment
                                                                       7/29/2012 2:03:18 PM OMG SwA Presentation. 42
Performance and TPMS
View: Effectiveness




                       7/29/2012 2:03:18 PM OMG SwA Presentation. 43
Performance and TPMS
View: Thresholds and
Objectives




                                                                  Availability TPM
                                                                              Cost

                                                                                       F
                                                                                    MTT TTR
                                                                                     F+M
                                                                                                          Component
                                                                                  MTT         Container   Restart,
                                                                                Fault Masking Managed     Activation,
                                                                                and Automated Services    And Migration




                       Risk Mitigation
                                                                     Storage    Failover
                                                                     Area
                                                                     Networks
                                                       Replication



                                              Backup
                                              and Recovery


                                         Application Solutions

                                         File and Volume        Data      99.999%                 Lights-out   Soft Real
                                         Management          Consistency Availability             Operations   Time QoS
                                                              Quality of Provided Service

                                                                            7/29/2012 2:03:18 PM OMG SwA Presentation. 44
Performance and TPMs
View: Integrated




                       7/29/2012 2:03:18 PM OMG SwA Presentation. 45
System Architecture
Requirements

                                   Capability and
                                   Requirements



                                                      Performance&
          Metadata and Semantics




  • Objective: Translate the           Standards,
                                   Information &          TPMs
    Performance and TPMs into           Directives,
                                        Data
    constraining Architecture           Mandates,
    Requirements.                       Principles
  • Standards & Directives:
    Those items that, by policy,
    drives constaints                Patterns,           System
                                   Services and
  • Patters, Specs, …: The
                  Processes         Specifications,
                                   Components
                                                       Architecture
    translation of TPMs into           Reusable       Requirements
    basis for specification             Assets




                                                           Assembly &
                                     Interfaces
                                                           Deployment
                                                                      7/29/2012 2:03:18 PM OMG SwA Presentation. 46
System Architecture
Requirements
                                                                                               Directives and Mandates
                                                                                                     + Directive
                                                                                                     + Policies



                                                                                                                                   <<View>>                           <<View>>                            <<View>>
        <<View>>                      <<View>>                      <<View>>                           <<View>>
                                                                                                                                                              Interface Reference Model            Service Reference Model
  Metadata and Semantics   Capabilities and Requirements   Performance Reference Model          Business Reference Model      Information and Data
     Reference Model                    Model                                                                                   Reference Model




                                                                                         Technical Standards, Patterns, and                                                                              <<View>>
                                                                                                    References                                                                                   Deployment Reference Model




                                                                                                                                                              <<AF>>
                                                                                                                                                                                                          <<IAF>>
                                                                                                                                                        Representational Format
                                                                                                                                                                                                       Programmatics




                                                                                                                                                Process-oriented Standards, Pattenrs and
                                                                                                                                                                                                           <<IAF>>
                                                                                                                                                              References
                                                                                                                                                                                                 Integrated Plan and Scehdule
                                                                                                                                               + Program Management Process Standards




                                                                                                                                                                                  7/29/2012 2:03:18 PM OMG SwA Presentation. 47
Services and Components
View
                                              • Objective: clearly specify
                                            Capability and
                                                 services and how they relate
                                            Requirements
                                                 to implementation.               Services
                                              • Services: Specifying a Service
                                                 and the context of usage
                                              • Components: Specifying a
                                                                     Performance&
                                                 component that implements
       Metadata and Semantics




                                                 one or &
                                            Informationmore Services TPMs
                                                 Data                            Components
                                              • Drives Assembly and
                                                 Interfaces.


                                                                     System
                                            Services and
                                Processes                          Architecture
                                            Components
                                                                  Requirements




                                                                       Assembly &
                                              Interfaces
                                                                       Deployment
                                                                                  7/29/2012 2:03:18 PM OMG SwA Presentation. 48
Services and Components
View: Services
                                                                                                                                         Can reference and
                                 Project                Capab ilities assigned to                      Capability                          include other
                           (f rom Programmatics)                                        (f rom Capabilities and Requirements Model)
                                                          projects for delivery

                                                                                    +Desirable Outcome 1..n

                              +Funded Delivery Source

                                                               delivers                                    +Planned
                                                                                                            Outcome
                                      +Software                                                                                         Can b e composed of many
                                                                                                            0..n
                                       Enabled Software Services must have                                                                   sm aller services
             1 Reference Specification Service   reference specifications         0..n                  Service
    +Basis for                                                             +Outcome
                                       1..n                                     +Something
   Detail Design                                                                                               +Outcome
                                                                                 that can be
                                                                                                              Specification Context of Usage
                                                                                     done
emented
                                                                                                                                                        ServiceType



tract Offers 1..n                                                                           How Service
  ExposedInterfaces                                                                          Specified
  (f rom ContainerTy pe)
                                                                                                                                        ServiceContextType             ServiceTaxonomy

               +Community
               for a Service                                                               +Outcome Mechanism


Service Community of Interest                                                                          Interface                  +Registered
                                                                                            (f rom Interf ace Ref erence Model)
                                                                                                                                                                  ServiceRegistry
  (f rom Interf ace Ref erence Model)                                                                                                Entry          0..n   (f rom Interf ace Ref erence Model)
                                                                                                                                           +Catalog of
                                                                                                                                             runtime
    +Domain of
                                                                                                                                            Interfaces
     services


                                                                                    APIs realize the Service Interface Cont...
                   +Service
            1..n                                                                                                                                     7/29/2012 2:03:18 PM OMG SwA Presentation. 49
                 Implementor                                                                           1..n
Services and Components                                                                                                                                                                              Project
                                                                                                                                                                                               (f rom Programmatics)
                                                                                                                                                                                                                                 Capab ilities assigned to
                                                                                                                                                                                                                                   projects for delivery
                                                                                                                                                                                                                                                                                     Capability
                                                                                                                                                                                                                                                                      (f rom Capabilities and Requirements Model)
                                                                                                                                                                                                                                                                                                                       Can reference and
                                                                                                                                                                                                                                                                                                                         include other



View: Components                                                                                                                                                                                 +Funded Delivery Source
                                                                                                                                                                                                                                                                  +Desirable Outcome 1..n




                                                                                                                                                                                                                       delivers                                   +Planned
                                                                                                                                                                                                                                                                   Outcome
                                                                                                                                                                                                        +Software                                                                     Can b e composed of many
                                                                                                                                                                                                                                                                   0..n
                                                                                                                                                                                                         Enabled Software Services must have                                                sm aller services
                                                                                                                                                                               1 Reference Specification Service   reference specifications         0..n       Service
                                                                                                                                                                      +Basis for                                                             +Outcome
                                                                                                                                                                                                         1..n                                     +Something
                                                                                                                                                                     Detail Design                                                                                  +Outcome
                                                                     +An                                                                                                                                                                           that can be
                                                                              0..n                                                                                                                                                                                Specification Context of Usage
                                                                 Implementor                                                                                                                                                                           done
                                                                Implementation Specification +Implementor Intent                             Which interfaces implemented
                                                                                                                                                                                                                                                                                                       ServiceType
                                                                     +Basis for 1                1 +Detail Design
                                                                                     0..1    1
                                                                       Reuse      +aComponent's
                                                                                  Implementation
                                                                                    Specification                                                           +Contract Offers 1..n                                                                                         How Service
                                                                          Reuse b y                                                                               ExposedInterfaces                                                                                        Specified
                                                                    incorporating another                                                                            (f rom ContainerTy pe)

                                                                         component                          An Implementation                                                                                                                                                                                         ServiceContextType            ServiceTaxonomy
                                                                                                          Specification must exist
                                                                                +Registration of              for a Consumer                                                      +Community
                                                                           0..n      Reuse                  Specification to Exist                                                for a Service                                                                          +Outcome Mechanism
                                                                      RegistrationOfReuse
                                                                                                                                                                   Service Community of Interest                                                                                     Interface                  +Registered
                                                                                            +Registration                                                                                                                                                                                                                                      ServiceRegistry
                                                                                                                      +aComponent's                                                                                                                                       (f rom Interf ace Ref erence Model)      Entry          0..n
                                                                                            1..n For Reuse                                                           (f rom Interf ace Ref erence Model)                                                                                                                                 (f rom Interf ace Ref erence Model)
                                                                                                                     Specification as a                                                                                                                                                                                  +Catalog of
                                                                                                                1  1 Service Consumer                                                                                                                                                                                      runtime
                                                                                                     +Registrant                                                       +Domain of
                                                                                                               ConsumerSpecification                                                                                                                                                                                      Interfaces
                                                                                                                                                                        services


                                                                                                                                                                                                                                                                 APIs realize the Service Interface Cont...
                                                                                                                        For Rutime
                                                                                                                                                                                   +Service
                                                                                                                        Invokation                                             1..n
             Collection type                                             <<Role>>                                                                           +Deliverable         Implementor                                                                                         1..n
                                                                                                                                                                              Component                    +Enabler        Communicates with the outside world via
                                                                                               <<Role>>                                                                                                                                                                      +Gateway
          Collection ManagerBusiness Component Type                                                          RegistrationOfInterfaceUsage
                                                                                                                                                                                                            1
                      +Data                                                         <<Role>>                                                                                                                                                                                     ComponentAPI
                     Manager                                                                                                                                                                                    create an instance
                            Business Component Manager                                                                                                                                                                                                                    +Type of API
                                                                                                                                                                                                                     for usage                   <<Role>>
                                                                                                                                                                           <<Role>>
                                                 1                                                                                                                            Provider                                        Client
                                                  +Data                                                                                                                             +Instance-
                                                 Manager            ContainerType                                                                                                                                                                                                           +Type of Interconnection
           +Content Spec.                                                                                                                                                              Based                      +Client
                                                                                                                                                                                                                         ComponentClientRole                          Inter-Process Communications
                                                                                                                                                                    ComponentServerRole
                                                                                                                                                                                                                                                                          (f rom Interf ace Ref erence Model)
        Knowledge Collection                                                                                                                                                           +Type-Based
                                                                                FunctionType                                                                                                    No need to request +Client
(f rom Inf ormation and Data Ref erence Model)
                                                                                                                                                                                                    instances
                                           +Content
                                            Spec.                                        Workflow Manager                                                                                  Instance Based
                                                 1                                                                                             Service Based
                                           DataSegment                                                                                                                                  InstanceBasedComponent
                             (f rom Inf ormation and Data Ref erence Model)                                                                 <<ContainerPattern>>
                                                                                                                                            TypeBasedComponent
                                                                                                                                                                  +Container                  1
                                                                                                                                            +Container
                                                                                                                                                               1            Collection of       One Instance per
                                                                                                                                                      Instances               Instances         Instance-b ased
                                                                                                                                                     +Manager                      +Instance       Component
                                                                                                                                                                                                 1
                                                                                                                                             <<FactoryPattern>>                      0..n
                                                                                                                                                                     Manages       InstanceOfaComponentClass
                                                                                                                                             ComponentManager       Lifecycle for

                                                                                                                                                                                                                                 Inter-connection rules affect registration of usage

                                                                                                                                                                                                             Interface to b e Invoked b y a Consumer Component
                                                                                                                                                                                              Dynamic Selection Criteria for Interface




                                                                                                                                                                                                                                                                                                   7/29/2012 2:03:18 PM OMG SwA Presentation. 50
Services and Components:
Integrated
                                                                                                                                                                                                                                                                                                                        Can reference and
                                                                                                                                                                                                      Project                     Capab ilities assigned to                           Capability                          include other
                                                                                                                                                                                                (f rom Programmatics)                                                  (f rom Capabilities and Requirements Model)
                                                                                                                                                                                                                                    projects for delivery

                                                                                                                                                                                                                                                                   +Desirable Outcome 1..n

                                                                                                                                                                                                   +Funded Delivery Source

                                                                                                                                                                                                                          delivers                                   +Planned
                                                                                                                                                                                                                                                                      Outcome
                                                                                                                                                                                                          +Software                                                                      Can be composed of many
                                                                                                                                                                                                                    Software Services must have                       0..n
                                                                                                                                                                                                           Enabled                                                                             smaller services
                                                                                                                                                                                 1 Reference Specification Service    reference specifications         0..n       Service
                                                                                                                                                                        +Basis for                                                              +Outcome
                                                                                                                                                                                                           1..n                                      +Something
                                                                                                                                                                       Detail Design                                                                                   +Outcome
                                                                       +An                                                                                                                                                                            that can be
                                                                                0..n                                                                                                                                                                                 Specification Context of Usage
                                                                   Implementor                                                                                                                                                                            done
                                                                  Implementation Specification +Implementor Intent                             Which interfaces implemented
                                                                                                                                                                                                                                                                                                         ServiceType
                                                                       +Basis for 1 0..1          1 +Detail Design
                                                                                              1
                                                                         Reuse +aComponent's
                                                                                   Implementation
                                                                                     Specification                                                            +Contract Offers 1..n                                                                                        How Service
                                                                            Reuse b y                                                                               ExposedInterfaces                                                                                       Specified
                                                                      incorporating another                                                                            (f rom ContainerTy pe)

                                                                           component                         An Implementation                                                                                                                                                                                         ServiceContextType            ServiceTaxonomy
                                                                                                           Specification must exist
                                                                                  +Registration of             for a Consumer                                                       +Community
                                                                             0..n     Reuse                  Specification to Exist                                                 for a Service                                                                         +Outcome Mechanism
                                                                        RegistrationOfReuse
                                                                                                                                                                     Service Community of Interest                                                                                    Interface                  +Registered
                                                                                              +Registration                                                                                                                                                                                                                                     ServiceRegistry
                                                                                                                       +aComponent's                                                                                                                                       (f rom Interf ace Ref erence Model)      Entry          0..n
                                                                                              1..n For Reuse                                                           (f rom Interf ace Ref erence Model)                                                                                                                                (f rom Interf ace Ref erence Model)
                                                                                                                      Specification as a                                                                                                                                                                                  +Catalog of
                                                                                                                 1 1 Service Consumer                                                                                                                                                                                       runtime
                                                                                                      +Registrant                                                        +Domain of
                                                                                                                ConsumerSpecification                                                                                                                                                                                      Interfaces
                                                                                                                                                                          services


                                                                                                                                                                                                                                                                  APIs realize the Service Interface Cont...
                                                                                                                         For Rutime
                                                                                                                                                                                     +Service
                                                                                                                         Invokation                                              1..n
               Collection type                                             <<Role>>                                                                           +Deliverable         Implementor                                                                                        1..n
                                                                                                                                                                                Component                    +Enabler       Communicates with the outside world via
                                                                                                 <<Role>>                                                                                                                                                                     +Gateway
            Collection ManagerBusiness Component Type                                                          RegistrationOfInterfaceUsage
                                                                                                                                                                                                             1
                        +Data                                                         <<Role>>                                                                                                                                                                                    ComponentAPI
                       Manager                                                                                                                                                                                   create an instance
                              Business Component Manager                                                                                                                                                                                                                   +Type of API
                                                                                                                                                                                                                      for usage                   <<Role>>
                                                                                                                                                                             <<Role>>
                                                   1                                                                                                                            Provider                                        Client
                                                    +Data                                                                                                                             +Instance-
                                                   Manager            ContainerType                                                                                                                                                                                                          +Type of Interconnection
             +Content Spec.                                                                                                                                                              Based                      +Client
                                                                                                                                                                                                                           ComponentClientRole                         Inter-Process Communications
                                                                                                                                                                      ComponentServerRole
                                                                                                                                                                                                                                                                           (f rom Interf ace Ref erence Model)
          Knowledge Collection                                                                                                                                                           +Type-Based
                                                                                 FunctionType                                                                                                     No need to request +Client
  (f rom Inf ormation and Data Ref erence Model)
                                                                                                                                                                                                      instances
                                             +Content
                                              Spec.                                        Workflow Manager                                                                                  Instance Based
                                                   1                                                                                             Service Based
                                             DataSegment                                                                                                                                  InstanceBasedComponent
                               (f rom Inf ormation and Data Ref erence Model)                                                                 <<ContainerPattern>>
                                                                                                                                              TypeBasedComponent
                                                                                                                                                                    +Container                  1
                                                                                                                                              +Container
                                                                                                                                                                 1            Collection of       One Instance per
                                                                                                                                                        Instances               Instances         Instance-based
                                                                                                                                                       +Manager                      +Instance       Component
                                                                                                                                                                                                   1
                                                                                                                                               <<FactoryPattern>>                      0..n
                                                                                                                                                                       Manages       InstanceOfaComponentClass
                                                                                                                                               ComponentManager       Lifecycle for

                                                                                                                                                                                                                                  Inter-connection rules affect registration of usage
                                                                                                                                                                                                                                                                                                           7/29/2012 2:03:18 PM OMG SwA Presentation. 51
Interfaces View

                                    Capability and
                                    Requirements


    • Objective: clearly specify
                                                          Performance&
         Metadata and Semantics




      Interfaces independent of           Specification
                                     Information &            TPMs
      Service Enablement.
                                          Data
    • Specification: specify the
      Interface
    • Enablement Selection: SLA
      to type-of-interface selection
    • Drives how components are            Enablement        System
                                      Services and
                Processes
      selected or formed                      Selection    Architecture
                                      Components
                                                          Requirements




                                                               Assembly &
                                      Interfaces
                                                               Deployment
                                                                          7/29/2012 2:03:18 PM OMG SwA Presentation. 52
Interfaces View:
Specification




                   7/29/2012 2:03:18 PM OMG SwA Presentation. 53
Interfaces View: Enablement
Selection




                              7/29/2012 2:03:18 PM OMG SwA Presentation. 54
Assembly and Deployment
View

                                            Capability and
                                            Requirements



                                                                      Performance&
                                             • Objective: clearly specify
       Metadata and Semantics




                                                                                    Assembly
                                                          &
                                            Informationassembled and TPMs
                                                What is
                                                 Data
                                                deployed.
                                             • Assembly: specification of
                                                the Installs
                                             • Deployment: Specification of
                                                qualification to a deployment
                                                                         System Deployment
                                             Services and
                                                site
                                Processes                              Architecture
                                             Components
                                                                      Requirements




                                                                         Assembly &
                                              Interfaces
                                                                         Deployment
                                                                                 7/29/2012 2:03:18 PM OMG SwA Presentation. 55
Assembly and Deployment
View: Assembly




                          7/29/2012 2:03:18 PM OMG SwA Presentation. 56
Assembly and Deployment
View: Deployment




                          7/29/2012 2:03:18 PM OMG SwA Presentation. 57
Conclusions


Finally, the End




                   7/29/2012 2:03:18 PM 5864_ER_WHITE.58
The End
     • We need patterns and specifications
     • Standards are only as good as knowing when to use them
     • Much work needs to be done to provide for trust



                   Thank you             !




                                                  7/29/2012 2:03:18 PM OMG SwA Presentation. 59

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:0
posted:7/29/2012
language:
pages:59