120 likes | 244 Views
Draft 02. X Paradigm layered architecture. Starting Point. S. Lotti HL7 Italia Chair Enterprise Architect at Invitalia – Government Agency for Inward Investment Promotion and Enterprise Development. Objective of Layered Architecture ( from wiki ). Initial ideas are:
E N D
Draft 02 X Paradigm layered architecture Starting Point S. Lotti HL7 Italia Chair Enterprise Architect at Invitalia – Government Agency for Inward Investment Promotion and Enterprise Development HSSP
Objective of Layered Architecture (from wiki) • Initial ideas are: • Map artefacts into the SAIF framework as was done in Practical Guide Part II with an eye to separating platform independent elements from platform specific ones. • A decision tree through the stack will be graphed. The output of task #1 may or may not be appropriate as a starting point. Particular paths of choices through the stack may represent particular existing artifact choices (example: IHE XDS profile). Again the purpose is to find the common elements vs. differences and provide raw material for generating a deployment that enables disparate systems to interoperate. HSSP
X Paradigm specs in SAIF ISM Common part (Platform indipendent) Conformance assertion analysis Platform Specific part ? ? • Mixed implementation environments are also theoretically possible HSSP
Logical progession (partial) Bottom up With existing specs HSSP
e.g. Service architecture design • Layered Service Inventory • BPMN2 Choreograpy • BPMN2 Collaboration • Service Architecture (SoaML from STMs PIM) - Use case (narrative) • Business Vocabulary (SBVR) Process Services Entity services Utility services HSSP
Business Vocabulary (SBVR) • The Vocabulary will be designed with SBVR (with a simple UML profile) • SBVR will be used for role/actor modeling and also for conceptual information modeling HSSP
BPMN2 Collaboration • Business Vocabulary (SBVR) Narrative Use Case • The processes will be derived from narrative use cases and vocabulary (participants) HSSP
Service Architecture • BPMN2 Collaboration • Service Contracts & • From BPMN collaborations will be identified the operations and mapped on the service architecture and contracts (from SFMs/STMs PIM) Service architecture Contract Retro-modeling from existing standard specs is necessary HSSP
BPMN2 Collaboration • BPMN2 Choreograpy • From BPMN collaborations will be defined the choreography or the orchestration(s) (if possible or useful) HSSP
Resulting Service Inventory Layered Service Inventory Paradigm X use Inform IHE Profile OMG Standards … HSSP Services (logicaldimension PIM) Implementabledimension (PSMs) HSSP