Legal Considerations For Web Services, Federated Systems .

2y ago
30 Views
3 Downloads
211.35 KB
42 Pages
Last View : 3d ago
Last Download : 3m ago
Upload by : Grady Mosby
Transcription

Legal ConsiderationsforWeb Services,Federated SystemsandE-CommerceCopyright 2002 Mathet Consulting, Inc.

Current State of Affairs Business partners are increasingly seeking relieffrom failed expections in their businessrelationships Business partners are increasingly incorportingQuality of Service expections in theiragreements to do business Corportate security policies and procedures areincreasingly being owned by legal departments Clients are requesting functionality that addresslegal issuesCopyright 2002 Mathet Consulting, Inc.

The Proposition Architect and engineer (design, model) legallyoriented processes into federated systems. Themodels and software implemenations can be usedto help avoid litagation (and improve overallquality and security) Help reduce the time and costs of litagation byproviding evidenceCopyright 2002 Mathet Consulting, Inc.

Presentation Strategy Part I– Problem Presentation: High-level legal view ofneeds, requirements, and architecture for afederated bioinformatic system– Context for Analysis and Design Part II– Application of MDA and UML in architectingand engineering a solutionCopyright 2002 Mathet Consulting, Inc.

High-level Legal View of Needs,Requirements, and Architecturefor a Federated Bioinformatics SystemCopyright 2002 Mathet Consulting, Inc.

The Federated Bioinformatic System ProblemCommunity of PracticeKnowledge DomainBioinformatic Integration Support CenterCopyright 2002 Mathet Consulting, Inc.

High-level Properties and Characteristics ofFederated Bioinformatic System DistributedHeterogeneousApproximately 100 enterprisesEnterprises participate in multiple communities of practiceEnterprises belong to specific domains of knowledgeEnterprises belong to public and proprietary domainsEnterprises include government agencies, research labs, clinical labs,research consortiums, pharmaceuticals, hospitals Each enterprise has its own set of legal, quality, information, andsecurity standards, policies and procedures A mission (and “safety”) critical system to enhance the discovery andapplication of new medical therapiesCopyright 2002 Mathet Consulting, Inc.

High-level Requirements forFederated Bioinformatic System (Parital List) Requires shared data, information, knowledge and applications amongall parties Requires collaboration among all parties Requires stringent security/ privacy measures Open-source development must be embraced All standards, policies and procedures of each enterprise must berespected Data integrity must be maintained Data models must be flexible, extensible, adaptable, maintainable Both structured and unstructed data sources must be manipulated andshared Requires a bioinformatic technology support center Requires Peer-to-Peer and ASP modelsCopyright 2002 Mathet Consulting, Inc.

Questions Asked by the Legal View What is the nature of the relationship between enterprisesdoing business? Degree of coupling and coherency? What is the degree of trust? What are the boundaries between enterprises? Who owns what? What are the expections placed on each enterprise doingbusiness with each other? What kind of liability risks are there? At what points, in the process of doing business, is there aliability risk to each enterprise?Copyright 2002 Mathet Consulting, Inc.

Questions Asked by the Legal View Are there shared risks? Who’s accountable? What processes can be put in place to ensure quality ofservice expections are met? To what degree can a legal contract be modeled andembedded in a federated system?Copyright 2002 Mathet Consulting, Inc.

The Federated System , eKnowledge, rpriseData ExchangeEnterprise ACopyright 2002 Mathet Consulting, Inc.Enterprise-EnterpriseInteraction based onEnterprise-EnterpriseAgreementsEnterprise B

The Federated System ProblemSystems, Processes,Standards, SOPs, PoliciesSystems, Processes,Standards, SOPs, PoliciesShared systems, processes,standards, SOPs, erpriseData ExchangeEnterprise ACopyright 2002 Mathet Consulting, Inc.Enterprise-EnterpriseInteraction based onEnterprise-EnterpriseAgreementsEnterprise B

The Federated System ProblemPoints of Possible LiabilityPoints of liability riskPoints of liability riskShared liability riseData ExchangeEnterprise ACopyright 2002 Mathet Consulting, Inc.Enterprise-EnterpriseInteraction based onEnterprise-EnterpriseAgreementsEnterprise B

The Federated System ProblemPoints of Possible LiabilityPoints of liability riskDatabase Integrity - ACID transactionsSecurity (Non-repudiation, Identification, Authorization etc.),PrivacyData QualityNetwork PerformanceIntellectual Property, etc.WS,Shared liability risksWS,PortalPortalDBAPPEnterprise-EnterpriseData ExchangeEnterprise ACopyright 2002 Mathet Consulting, Inc.Enterprise-EnterpriseInteraction based onEnterprise-EnterpriseEnterprise BAgreements

The Federated System ProblemSemantic Variance (Semanitc Shift, Semantic Drift)Language DomainLanguage DomainIndustry DomainIndustry DomainKnowledge DomainContextsKnowledge DomainCommunity of PracticeCommunity of PracticeRoleDataRoleDataEnterprise-EnterpriseData ExchangeEnterprise ACopyright 2002 Mathet Consulting, Inc.Enterprise-EnterpriseInteractionEnterprise B

The Federated System ProblemJurisdictionEnterprise AGeography / JurisdictionEnterprise BContextEnterprise-EnterpriseData ExchangeEnterprise-EnterpriseInteraction based onEnterprise-EnterpriseAgreementsCopyright 2002 Mathet Consulting, Inc.Geography / Jurisdiction

Context for Analysis and DesignIntegrated and Collaborative EnterprisesSystems: Architecture an Engineering(ICESAETM, I- ’Say)Copyright 2002 Mathet Consulting, Inc.

Abstraction Layers for Integrated and CollaborativeEnterprises Systems: Architecture and Engineering(ICESAE )TMIntegrated and Collaborative Inter-Enterprise Systems(Architectures and Engineering for Federated Systems, E-Business)L3Integrated and Collaborative (Intra)Enterprise Systems(Architectures and Engineering for Integration and Collaborationof Foundation Systems)Foundation Sub-Systems(Architectures and Engineering for Integration and Collaborationof subsystems to create Foundation Systems)Copyright 2002. Mathet Consulting, Inc.L2L1

Integrated and Collaborative Intra-Enterprise Systems:Architectures and usinessStrategiesEmergentStrategiesTelecom, Manufacturing, Space, Finance,Healthcare Pharmaceutical, Insurance,Transportation, Chemical, Government,Education, Basic Research, etc.Business (Process,Workflow, Rules) SystemsStrategy Views Business Strategies Business IntelligenceStrategies Knowledge, Information,Data (KID) Strategies Application Strategies Technical Strategies Communications Strategies Security Strategies Quality Strategies Legal Strategies Management StrategiesBusiness DomainStrategiesKID SystemsL2Management SystemsBusinessIntelligence SystemsLegal SystemsIntegrated andCollaborativeEnterprise SystemsApplication SystemsTechnical SystemsBusiness Domain SystemsCRM, ERP, KM, Financials, Custom, etc.E-Commerce, Web Services, Enterprise Services, EAI,Marketplaces, Supply Network, Portals, Informatics, etc.Copyright 2002. Mathet Consulting, Inc.Enterprise Systems:Architecture and Engineering ViewsQuality SystemsSecurity SystemsCommunicationsSystemsEmergent SystemsModelsE-Commerce, Web Services, Enterprise Services, EAI,Marketplaces, Supply Network, Portals, Informatics, etc.

Integrated and Collaborative Intra-Enterprise Systems:Architectures and usinessStrategiesEmergentStrategiesTelecom, Manufacturing, Space, Finance,Healthcare Pharmaceutical, Insurance,Transportation, Chemical, Government,Education, Basic Research, etc.Strategy Views Business Strategies Business IntelligenceStrategies Knowledge, Information,Data (KID) Strategies Application Strategies Technical Strategies Communications Strategies Security Strategies Quality Strategies Legal Strategies Management StrategiesBusiness DomainStrategiesPIMs,PSMsEnterprise Systems:Architecture and Engineering ViewsBusiness (Process,Workflow, Rules) SystemsManagement SystemsBusinessIntelligence SystemsKID SystemsLegal SystemsIntegrated andCollaborativeEnterprise SystemsApplication SystemsTechnical SystemsBusiness Domain SystemsCRM, ERP, KM, Financials, Custom, etc.E-Commerce, Web Services, Enterprise Services, EAI,Marketplaces, Supply Network, Portals, Informatics, etc.L2Quality SystemsSecurity SystemsCommunicationsSystemsEmergent SystemsModels (PIMs, PSMs)E-Commerce, Web Services, Enterprise Services, EAI,Marketplaces, Supply Network, Portals, Informatics, etc.PIMS and PSMs can be considered to be enterprise components similar to hardware and software componentsCopyright 2002. Mathet Consulting, Inc.

Standards-based Integrated and Collaborative EnterpriseSystems: Architecture and EngineeringCWMCORBAXMISPEMData ParallelUnreliable MulticastLoad BalancingEnterprise Systems:Architecture and Engineering ViewsPIMs,PSMsBusiness (Process,Workflow, Rules)SystemsManagementSystemsBusiness ted andCollaborativeEnterprise SystemsQualityEDOCSystemsWorkflow ProcessDefinitionApplicationSecurityDocument RepositorySystemsSystemsIntegrationDistributed SimulationTechnicalCommunicationsRegistration and DiscoverySystemsSystemsGene ExpressionSurveillanceEmergent SystemBusiness Domain SystemsModels PIMs, PSMsGenomic MapsCRM, ERP, KM, Financials, Custom, etc.Organizational StructureE-Commerce, Web Services, Enterprise Services, EAI,PIDSSOAPXMLWSDLUDDIebXMLetcMarketplaces, Supply Network, Portals, Informatics, etc.PIMS and PSMs can be considered to be enterprise components similar to hardware and software componentsCopyright 2002. Mathet Consulting, Inc.

Systems and Systems Integration are Built on Ontologies /Semantics, and Measures and MetricsL2Integrated and Collaborative Enterprise Measures and MetricsIntegrated and Collaborative Enterprise Ontology / SemanticsCopyright 2002. Mathet Consulting, Inc.ManagementSystemsLegal SystemsQuality SystemsSecurity SystemsCommunicationSystemsTechnical SystemsApplication SystemsKID SystemsBusinessIntelligence SystemsIntegrated and Collaborative Enterprise Standards(e.g. PIMS and PSMs)Business SystemsIntegrated and Collaborative EnterpriseStandards (e.g. PIMs and PSMs)Integrated and Colloborative Enterprise Systems

Integrated and CollaborativeEnterprise SystemsIntegrated and CollaborativeInter-Enterprise Systems Federation of tionTechnicalApplicationKIDBusiness icalApplicationKIDIntegrated and Collaborative EnterpriseMeasures and MetricsIntegrated and Collaborative EnterpriseOntology / SemanticsEnterprise BIntegrated and Collaborative EnterpriseMeasures and MetricsIntegrated and Collaborative EnterpriseOntology / SemanticsEnterprise ACopyright 2002. Mathet Consulting, Inc.CommunicationIntegrated and Collaborative EnterpriseStandards (e.g. PIMs and PSMs)Integrated and Collaborative Enterprise Standards(e.g. PIMS and PSMs)Business Intell.L2BusinessIntegrated and CollaborativeEnterprise SystemsIntegrated and Collaborative Enterprise Standards(e.g. PIMS and PSMs)Integrated and Collaborative EnterpriseStandards (e.g. PIMs and PSMs)L3L2E-Commerce, Web Services, Enterprise Services, EAI,Marketplaces, Supply Network, Portals, Informatics, etc.

Integrated and CollaborativeInter-Enterprise Systems Federation of EnterprisesL3Management, Business, Intelligence, KID, Application,Technical, Communications, Security, Quality, Legal,Standards, Policies, SOPs,Measures and Metrics,Ontologies and SemanticsInter-enterprise Boundary /Integration and Collaboration PointL2Integrated and CollaborativeEnterprise SystemsEnterprise ACopyright 2002. Mathet Consulting, BusinessManagementL2Integrated and CollaborativeEnterprise SystemsEnterprise B

Integrated and CollaborativeInter-Enterprise Systems Federation of EnterprisesL3Inter-enterprise Boundary /Integration and Collaboration PointL2What is the nature of this inter-enterprise relationship?What is the contained in legal contract between enterprises?Integrated and CollaborativeEnterprise SystemsIntegrated and CollaborativeEnterprise SystemsEnterprise AL2What is contained in this software contract?Enterprise BE-communication channelWeb ServiceService Level AgreementWhat is the relationship between the legal contract and software contract?Copyright 2002. Mathet Consulting, Inc.

What is the Nature of theInter-Enterprise Relationship Legal Relationship Coupling - What do they, or must they, share?– Foundation systems (e.g. KID, applications, security, management,etc.) Cohesion - How well should they, do they, share?– Foundation Systems (e.g. KID, applications, security,management) Coupling and Cohesion affect expections of one enterprise by the other The more “supportive” information (data other than that directlyoperated on) contained in the software contract, the tighter thecouplingCopyright 2002 Mathet Consulting, Inc.

Integrated and CollaborativeInter-Enterprise Systems Federation of EnterprisesL3What is the nature of individual inter-enterprise relationships?What is the nature of the aggregation of the inter-enterprise relationships?L3Enterprise CL2L23L2 Enterprise B4255Enterprise D1E-communication channelL2 Enterprise AWeb ServiceWhat is contained in the legal contracts?What is contained in each software contract?Copyright 2002. Mathet Consulting, Inc.Enterprise EL2

Enterprise CL2L2L3Integrated and CollaborativeInter-Enterprise Systems FederationL3of EnterprisesL2 Enterprise B Management, Business, Intelligence, KID, ApplicationTechnical, Communications, Security, Quality, Legal,Standards, Policies, SOPs,Measures and Metrics,Ontologies and SemanticsL2 Enterprise ACopyright 2002. Mathet Consulting, Inc.Enterprise DL2Enterprise E

The Federated Bioinformatic System ProblemCommunity of PracticeKnowledge DomainBioinformatic Integration Support CenterCopyright 2002 Mathet Consulting, Inc.

Enterprise CL2Abstract out commonalitiesL2L3L2 Enterprise BL2 Enterprise ACopyright 2002. Mathet Consulting, Inc.Registries and Directory Services for theBioinformaticL3 FederationSecurity, Quality, Legal (contracts),Standards, Policies, SOPs,Measures and Metrics,Ontologies and SemanticsEnterprise DL2Enterprise E

Enterprise CL2L2L3Legally-oriented system for theBioinformatic FederationL2 Enterprise BL2 Enterprise ACopyright 2002. Mathet Consulting, Inc.Dependent on a federated securityL3 systemand qualityDatabase Integrity - ACID transactionsSecurity (Non-repudiation, Identification,Authorization etc.),PrivacyData QualityNetwork PerformanceIntellectual Property, etc.Enterprise DL2Enterprise E

Federated Bioinformatic Systems Platform The Internet Computing Model (object-oriented, service oriented)N-Tiered Distributed Systems (object-oriented, service oriented)Ontologies, Dictionaries, ThesauriFederated Registries (contracts, services, etc.)Federated AgentsFederated Directory ServicesFederated ICESAE systems– Legal– Management– Kid– etc. The GRID (where appropriate)Copyright 2002. Mathet Consulting, Inc.

Integrated and Collaborative Inter-EnterpriseSystems -Federation of EnterprisesApplicable Standards for Bioinformatics FederationEDOC, Document Repository Integration, Registration and Discovery, GeneExpression, Genomic Maps, Organizational Structure, PIDS, CWM, XMI,SOAP, XML, WSDF, WSFL, UDDI, ebXML, etc.L3L2Enterprise CL2L2 Enterprise BL2 Enterprise ACopyright 2002. Mathet Consulting, Inc.Enterprise DE-communication channelWeb ServiceEnterprise EL2

Architecting and EngineeringFederated Systems for EBusiness - a Legal ViewICESAE and MDACopyright 2002. Mathet Consulting, Inc.

Requirements for a Legal System of theFederated System (Partial List) Based on Legal requirements of individual enterprises, relationshipsbetween enterprises, and the federation as a whole Must have contract management (quality of service agreements, tradeagreements) Must be able to observe federation behavior and compare to contracts:gather, collate, flag, report based upon predetermined metrics - gatherevidence.– Determine nature of dispute (e.g. security-database access)– Determine the parties involved– Determine who owns what Must be able to mediate “e-disputes” - help disputing parties negotiatea resolution. Must be able to report on mediation of “e-disputes” Must be able to arbitrate “e-disputes” - make judgements. Must be ableto report on arbitration of “e-disputes”.Copyright 2002 Mathet Consulting, Inc.

UML and Model Driven Architecturefor Federated Systems - L3 LevelPSMPIMWSFLPSMPSMExecutionPSME / R Model,UML PSMXML Schema, DTD,UML PSMExecutionJava Object Model,UML PSMExecutionExecutionDatabase TablesXML DocumentCopyright 2002. Mathet Consulting, Inc.Entity BeanWeb ServicesProcess Flow

UML and Model Driven Architecturefor Federated Systems - L3 LevelExecutionExecutionExecutionExecutionXML DocumentEntity BeanDatabase TablesWeb ServicesProcess iseData ExchangeEnterprise-EnterpriseInteraction based onEnterprise-EnterpriseAgreementsCopyright 2002. Mathet Consulting, Inc.

Properties and Characteristics of a Legal Systemof the Federated System (Partial List) The Legal System for a federation exists at the L3 abstraction layer. Itis a foundaton system for the federation. It is “owned” by the federation It boundaries are the boundaries of the federation - the enterprises thatmake up the federation It utilizes ontologies, dictionaries and thesauri as references in “edisputes” It utilizes measures and metrics for “e-disputes” - observation,mitigation, and arbitrationCopyright 2002 Mathet Consulting, Inc.

UML and Model Driven Architecturefor Federated Systems - L3 LevelPIM-PIM relationshipPIMPIM-PSM relationshipPSMPSMExecution CodeCopyright 2002. Mathet Consulting, Inc.Relationship withinthe same modelRelationship betweenmodels in the same layerRelationship betweenbetween layersPSM

UML and Model Driven Architecturefor Federated Systems - L3 LevelHigh-level View of Legal SystemPSMPIMSecurity SystemPSMAgentsMediatorArbitratorPSMPIMLegal SystemWSFLPSMExecutionE / R Model,UML PSMWeb ServicesProcess FlowXML Schema, DTD,UML PSMJava Object Model,UML PSMExecutionExecutionExecutionXML DocumentBeanDatabase TablesCopyright 2002. Mathet Consulting, Inc.

L3L2Enterprise CDeploymentAgentsL2MediatorArbitratorL2 Enterprise BL2 Enterprise ACopyright 2002. Mathet Consulting, Inc.Enterprise DRegistriesDirectory Servicesetc.Bioinformatics IntegrationSupport CenterL2Enterprise E

Contact InformationMatthew K. Hettinger, President and Chief Architect / Engineer1450 E. American Lane, PMB 14004Schaumburg, IL 60173Office: 847-330-6375Direct: 847-877-6374hettinge@mindspring.comCopyright 2002. Mathet Consulting, Inc.

Business Intelligence Systems KID Systems Application Systems Technical Systems Communications Systems Legal Systems Quality Systems Security Systems Business Domain Strategies . L2. Emergent System Models PIMs,

Related Documents:

Bruksanvisning för bilstereo . Bruksanvisning for bilstereo . Instrukcja obsługi samochodowego odtwarzacza stereo . Operating Instructions for Car Stereo . 610-104 . SV . Bruksanvisning i original

10 tips och tricks för att lyckas med ert sap-projekt 20 SAPSANYTT 2/2015 De flesta projektledare känner säkert till Cobb’s paradox. Martin Cobb verkade som CIO för sekretariatet för Treasury Board of Canada 1995 då han ställde frågan

service i Norge och Finland drivs inom ramen för ett enskilt företag (NRK. 1 och Yleisradio), fin ns det i Sverige tre: Ett för tv (Sveriges Television , SVT ), ett för radio (Sveriges Radio , SR ) och ett för utbildnings program (Sveriges Utbildningsradio, UR, vilket till följd av sin begränsade storlek inte återfinns bland de 25 största

Hotell För hotell anges de tre klasserna A/B, C och D. Det betyder att den "normala" standarden C är acceptabel men att motiven för en högre standard är starka. Ljudklass C motsvarar de tidigare normkraven för hotell, ljudklass A/B motsvarar kraven för moderna hotell med hög standard och ljudklass D kan användas vid

LÄS NOGGRANT FÖLJANDE VILLKOR FÖR APPLE DEVELOPER PROGRAM LICENCE . Apple Developer Program License Agreement Syfte Du vill använda Apple-mjukvara (enligt definitionen nedan) för att utveckla en eller flera Applikationer (enligt definitionen nedan) för Apple-märkta produkter. . Applikationer som utvecklas för iOS-produkter, Apple .

och krav. Maskinerna skriver ut upp till fyra tum breda etiketter med direkt termoteknik och termotransferteknik och är lämpliga för en lång rad användningsområden på vertikala marknader. TD-seriens professionella etikettskrivare för . skrivbordet. Brothers nya avancerade 4-tums etikettskrivare för skrivbordet är effektiva och enkla att

Den kanadensiska språkvetaren Jim Cummins har visat i sin forskning från år 1979 att det kan ta 1 till 3 år för att lära sig ett vardagsspråk och mellan 5 till 7 år för att behärska ett akademiskt språk.4 Han införde två begrepp för att beskriva elevernas språkliga kompetens: BI

**Godkänd av MAN för upp till 120 000 km och Mercedes Benz, Volvo och Renault för upp till 100 000 km i enlighet med deras specifikationer. Faktiskt oljebyte beror på motortyp, körförhållanden, servicehistorik, OBD och bränslekvalitet. Se alltid tillverkarens instruktionsbok. Art.Nr. 159CAC Art.Nr. 159CAA Art.Nr. 159CAB Art.Nr. 217B1B