7irene Application Reference Model - Presented at OT2004

29 March 2004

The Application Reference Modelfor successful Enterprise Software Development

John Cheesman, Greg Hodgkinsonwww.7irene.com

Agenda

What is an Application Reference Model?

Enterprise Application RequirementsEnterprise Application Concepts– Functional Component, Service– Assembly, Application Platform

Applying the Reference ModelSoftware Lifecycle ManagementDemonstration

Business Requirements from IT

Seamless technology-independent, software development life-cycleAccelerated development, integration and management of EnterpriseapplicationsGreater quality, flexibility and reliabilityFaster ROI for business solutions

What is an Enterprise Application?

BusinessCross-discipline: Large, distributed teams which involve multiple stakeholdersHigh-level visibility and sign-off: large budgets and large numbers of resources are involved.Mission-critical

TechnicalTransaction-based; Large number of transactionsOne to Many and Many to One TransactionsLarge volumes of dataLarge numbers of usersRelatively simple user interactionSecure, reliable, available, scalable, …

Enterprise Application Requirements

Flexibility / AgilityReconfiguration, Loose-couplingInteroperability standards

Asset reuse – IntegrationCOTS, DBs, Components, …

Technology-independenceDesign-time -> Runtime continuity

Scalable Application Development process

The Core Concepts

Functional Component (Design Time)Assembly Element (Run Time)Loose-couplingApplication PlatformApplication Layering

Application Reference Model

Functional Component (FC)provided

requiredspec

realization

*instance

0..1 1

source

FunctionalComponent Spec

FunctionalInterface Spec

FunctionalComponent

FunctionalComponent Object

FunctionalComponent

Implementation

FunctionalComponent Module

1..*module

Specification Unit

Implementation Unit

Deployment Unit

Execution Unit

Component Levels

OrderMgr

FunctionalComponent

OrderEJB

TechnologyComponent

FC Design Pattern

ServiceBinding

TechnologyPort

BusinessLogic

FunctionalInterface

Technology-specificBinding (e.g. JNDI Lookup)

Technology-specific Interface (e.g. EJB Home Interface)

J2EE FunctionalComponent Implementation

Refinement Stages

Refine – Apply:- Language Constraints- Application Platform Standards

Java FunctionalComponent Specification

Refine/Implement – Apply:- Technology Platform-specific Design Patterns

“Pure” FunctionalComponent Specification

UML + Java

Source

CustomerMgtBean

CustomerMgtBean()ejbActivate() : voidejbPassivate() : voidejbRemove() : voidsetSessionContext(sessioncontext : SessionContext) : void<<EJBRemoteMethod>> createCustomer(inContext : IContext, inCustomer : ICustomerTO) : IIDTO<<EJBRemoteMethod>> getCustomer(inContext : IContext, inCustomerId : IIDTO) : ICustomerTO

(from e jb)

<<EJBSession>>

CustomerManagerCS(from spec)

<<Interface>>ICustomerMgt

getCustomer(inContext : IContext, inCustomerId : IIDTO) : ICustomerTOcreateCustomer(inContext : IContext, inCustomer : ICustomerTO) : IIDTO

(from provided)

<<Interface>>

ICustomerMgtEJB(from e jb)

<<EJBRemoteInterface>>

EJBObject(from ejb)

<<Interface>>

SessionBean(from ejb)

<<Interface>>

CustomerMgtServiceBinding

(from service)FC

FC Implementation - Example

FunctionalInterface

Technology-specificBinding (e.g. JNDI Lookup)

Technology-specific Interface

Service and Component

ComponentService Definition

Component:ObjectService

instance-of

Service –Client’s View

Design Time

Run Time

Component –Supplier’s View

What does it do for me? What is the unit of change?

Defining the runtime – Assembly Elements

ApplicationAssembly

Technical Environment

ProvisionFunctionalComponent

Service

Assembly

LocationManager

DataSource:SouthEast

Functional Specification Architecture

CarInsuranceServices<<ComponentSpec>>

CustomerManager<<ComponentSpec>>

HouseInsuranceServices<<ComponentSpec>>

MarketingPrograms<<ComponentSpec>>

Functional Component Reuse -Does this give application integration?

Runtime Assembly Example

: CarInsuranceServices : HouseInsuranceServices

CarInsCustomers : CustomerManager

HouseInsCustomers : CustomerManager

: MarketingPrograms

Different Assembly ElementsSame Functional Component (Spec)

Interoperability Standards

Runtime Component ModelConstrains Functional Component Spec

Loose-couplingConnectors (Service Mappings)

Application Platform

Runtime Component ModelInterface Language (Java)DataType standard (ITransferObject)Exception standardInteraction Context (IContext)

Context-sensitivity enables an application to adapt at runtime

IContext

setPlatformContext()getPlatformContext()setImplementationContext()getImplementationContext()

<<Interface>>

IImplementationContext<<Interface>>

IPlatformContext

getAssemblyDefinition() : IAssemblyInfosetAssemblyDefinition(inAssemblyDefinition : IAssemblyInfo) : voidgetUserInfo() : IUserInfosetUserInfo(inUserInfo : IUserInfo) : void

<<Interface>>

Loose-Coupling – Service Discovery

ICustMgt Separate Service Request from Service Provision via a Service Discovery Service

Client depends only on service spec, Assembler decides which instances.

IClaims : Insurance

InsuranceCustomers:CustomerManager

3. provide2. request 1. publish

:Service Discovery

technology-platform-independent. Keep service connection

platform-independent to allow for alternative suppliers using different implementations

Service binding binds the service specification to the implementation.Only the binding needs to be published to the Discovery Service.

Insurance Customers: Customer Manager Imp

: InsuranceClaim Imp

IClaims ICustMgt

:Service Discovery

2. request 1. publish3. provide

ServiceBinding

Service Implementation

Loose-Coupling – Service Mappings

Service requests can be fulfilled by “functionally-equivalent” services using service mappings. Service mappings are technology-platform-independent.Useful when assembling elements developed independently.

Insurance Customers: Customer Manager Imp

: InsuranceClaim Imp

IClaims ICustMgt

:Service Discovery

2. request (1. publish)3. provide

ServiceBinding

Service ImplementationICustMgt2

ServiceMapping

1. publish

Application PlatformAssembly Assembly

Element

ServiceBinding

Assembly Element

Assembly ElementService

Mapping

Application Platform

Other Services…

Service Discovery Service

Runtime Component Model

Technology Platform

Application Layers - Example

APPLIC

User Interface

User Dialogue

System Services

Domain Services

InfrastructureServices

What the user sees.UI Logic.

Workflow dialogue.Use Case Logic.

Business process transactions.

SYSTEM

Domain entity services.

Domain-independent services.

Application Reference ModelBusiness Process

Application User Interface

automatesUser Dialogue

ServiceBinding

Technology Platform

System Services

Domain ServicesApplication Platform

InfrastructureServices

supports

Service Discovery Service

Runtime Component Model applies

Concept Examples

Topics

What is an Application Reference Model?

Enterprise Application RequirementsEnterprise Application Concepts– Functional Component, Service– Assembly, Application Platform

Applying the Reference ModelSoftware Lifecycle MgtDemonstration

Multiple concept applications

FC implementation exchangeLife-cycle traceabilityTechnology-abstractionAsynchronous service bindingsData IntegrationEnvironment DeploymentCOTS integration…

Software Lifecycle traceability

How do you link what is assembled and

deployed back to your original architecture?

Do your logical constructs get

“compiled away”?

Can you distinguish the logical runtime

architecture from your physical runtime environments?

Is your lifecycle broken?

Linking Architecture and Assembly

Architect

Provision

Assemble

Logical Assembly Definition

Deploy

Technology Independent Architecture

: MarketingPrograms

Architect

FunctionalComponent Specs

CarInsuranceServices<<ComponentSpec>>

CustomerManager<<ComponentSpec>>

HouseInsuranceServices<<ComponentSpec>>

MarketingPrograms<<ComponentSpec>>

Logical Assembly Definition

Managing Technology Dependencies

Provision

FunctionalComponent Specs Functional Component

Modules

Functional Component Deployment Descriptor

Technology Component Deployment Descriptor

CustomerMgtBean

CustomerMgtBean()ejbActivate() : voidejbPassivate() : voidejbRemove() : voidsetSessionContext(sessioncontext : SessionContext) : void<<EJBRemoteMethod>> createCustomer(inContext : IContext, inCustomer : ICustomerTO) : IIDTO<<EJBRemoteMethod>> getCustomer(inContext : IContext, inCustomerId : IIDTO) : ICustomerTO

(f rom e jb)

<<EJBSes sion>>

CustomerManagerCS(from spec)

<<Interface>>ICustomerMgt

(from provided)

<<Interface>>

ICustomerM gtEJB(from e jb)

<<EJBRemoteInterface>>

EJBObject(from ejb)

<<Interface>>

SessionBean(from ejb)

<<Interface>>

CustomerMgtServiceBinding

(from service)

Functional Component Publication

Functional Component Modules

Assembly – Pulling it all together

TechnicalArchitecture Logical Assembly

Definition

AssembleFunctional Component Modules

Linking Architecture and Assembly

FCSpec

ConnectionFunc Spec

ConnectorImp

Functional Spec Architecture

FCOFCO ConnectionQoS

FCFCImp

Connection

Functional Componentfunctional-component.xmlejb-jar.xml

ConnectorSpec

Logical Assembly Definitionlogical-assembly.xml

Technical Environmentstate/

config

Assembly Element Definitionassembly-element.xmlejb-jar.xmlweblogic*.xml/ibm*.xml

Physical Assemblyphysical-assembly.xml

logical assembly xml

<logical-assembly><name>CarInsuranceAssembly</name><version>1-0</version>

<name>CarInsServToCarInsuranceCustomersConnection</name><requesting-assembly-element>CarInsuranceServices-A</requesting-assembly-element><required-interface>

com.sevenirene.demo.component.carInsuranceServices.spec.required.ICarInsCustomerMgt</required-interface><providing-assembly-element>CarInsuranceCustomers-A</providing-assembly-element>

</connection></connections>

</logical-assembly>

: MarketingPrograms

assembly element xml

<assembly-element name="CarInsuranceCustomers-A" type="functional-component"><functional-component-specification name="CustomerManager" version="1-0"/><functional-component name="CustomerManager" version="1-0-0"/>

<service-binding><class-name>

com.sevenirene.demo.component.customerManager.impl.service.CustomerMgrServiceBinding</class-name><properties>

<property><name>jndi-name</name><value>ejb/insurancecompany/CustomerManager</value>

</property></properties>

</service-binding></assembly-element>

Service BindingImplementation

Technology Platform link

physical assembly xml<physical-assembly>

<name>CarInsuranceAssembly</name><version>1-0</version>

</logical-assembly>

<assembly-elements><assembly-element>

<name>CarInsuranceCustomers-A</name></assembly-element><assembly-element>

<name>CarInsuranceServices-A</name></assembly-element>

</assembly-elements>

<name>CarInsServToCarInsuranceCustomersConnection</name><connector>

<name>CarInsServToCustomerMgr</name><version>1-0-0</version>

</connector></connection>

</connections></physical-assembly>

Logical Assembly

Assembly Elements

Connectionimplementations

Optimise Your Software Lifecycle-Demonstration

For more information…

John Cheesmanjohn.cheesman@7irene.com

Greg Hodgkinsongreg.hodgkinson@7irene.com

www.7irene.com

7irene Application Reference Model - Presented at OT2004

Software

Model Reference Adaptive Control Survey of Control Systems (MEM 800) Presented by Keith Sevcik

Cell Reference Training PRESENTED BY RICHARD SNAPP – NOVEMBER 4, 2014

A look at ACRL-LA’s new Open-Access Journal presented by Megan Lowe, Reference Librarian (ULM), Editor Karen Niemla, Reference Librarian (ULM), Webmaster

10/7/2015 1 Realities of Virtual Reference Presented by: Kathy Dabbour Doris Helfer Lynn Lampert California State University Northridge Presented at Internet

IM Reference @ APL Staff Training Presented by Marissa M. Priddis

PLAGIARISM WHAT IT IS AND HOW TO AVOID IT Presented by the ULM Library Reference Department

Presented by Emily Linde & Maria Koszalka...Presented by Emily Linde & Maria Koszalka ... -Letters of Reference - PHS 398 Checklist -Research & Related Budget -PHS 398 Training Budget

Reference in Japanese-English Machine Translation€¦ · Reference in Japanese-English Machine Translation Francis Bond and Kentaro Ogura Presented by: Manuel Medina Gonz alez. Department

INFRARED REFERENCE SPECTRA - 独立行政法人 ... REFERENCE SPECTRA The infrared reference spectra presented here were obtained by the use of Fourier-trans-form infrared spectrophotometers

A LinkStation QUICK REFERENCE GUIDE - …„¢ MINI QUICK REFERENCE GUIDE B A C D E ... The information presented in this quick reference guide is intended to demonstrate effective

Goodbye Snail Mail, Hello Email Presented by Julie Rhea Reference Librarian

INFRARED REFERENCE SPECTRA - PmdaINFRARED REFERENCE SPECTRA The infrared reference spectra presented here were obtained by the use of Fourier-trans-form infrared spectrophotometers

. . . . . . . . . . . . . . . . . . . . . . . . . . . .€¦ · The LotusScript Language Reference, a comprehensive summary of the LotusScript language, presented in A-Z format

Reference Database Presented by Fabrice Evangelisti

GEOWISSENSCHAFTLICHE MITTEILUNGEN€¦ · Papers presented at the . EGS XXVll General Assembly, Nice, France, 2002 . ... Celestial reference frame, terrestrial reference frame, Earth

Model For Relating PM 2.5 Federal Reference Method & Nephelometer Measurements Presented by Jenny Parikh

MlCFlOFlCHE REFERENCE LIBRARY - PSSurvival.com€¦ · MlCFlOFlCHE REFERENCE LIBRARY ... 4.1.1 Soap Boiling Tanks ... attention was also given to the form in which the soap was presented

Retirement Reference Manual (RRM) Training Presented by: Retirement Education Division

Functional Reference Architecture for Corporate Master ... · The Functional Reference Architecture for corporate MDM presented and discussed in this paper is an outcome of applied

Fast Solutions to CSPsweb.mit.edu/16.412j/www/html/Advanced lectures/2004/R. Effinger.d… · Presented by: Robert Effinger Presented To: 16.412J Cognitive Robotics MIT Reference: