The document discusses the EPTS Reference Architecture Working Group's work to define a reference architecture for event processing systems. It provides an introduction to event processing architectures and outlines the group's agenda, which includes examining existing member architectures, developing a skeleton reference architecture, and defining terminology and methodology. The goal is to create architecture patterns that are compatible with EPTS members' solutions and identify best practices for technical architecture descriptions.
Presentation of functional design patterns for event processing with examples from TIBCO, Oracle, IBM and Prova event processing technologies. Superset of the Tutorial at DEBS2012. Editors Alex Alves, Catherine Moxey
Debs2009 Event Processing Languages TutorialOpher Etzion
The document outlines a tutorial on event processing languages. It discusses different styles of event processing languages including stream processing languages, rule oriented languages, and agent oriented languages. For stream processing languages, it covers key concepts like events, state, computational models, and programming models. It provides examples of stream processing languages like Esper, Coral8, and CCL.
The document discusses the FLIRT model for crowdsourcing which consists of five elements - Focus, Language, Incentives, Rules, and Tools. It provides details on each element and how they relate to defining a crowdsourcing activity. Focus relates to determining the business objectives, scope, scale, and depth of the activity. Language considers the social aspects that engage participants such as social objects and nature of interactions. Incentives, Rules, and Tools provide the framework for participants in terms of compensation, policies, and tools to complete tasks. The model provides a way to strategically plan a crowdsourcing initiative by considering each element.
At the core of all usability is a design—the one being used by your customer. The blueprint or foundation of that design is found in the interaction design. Over the years, I’ve worked with many people, from clients to co-workers, who are involved in design but who don’t consider themselves “designers”. They usually have good design instincts, but don’t have a “design” background—and they are always asking me how they can become better “designers”.In this presentation, I distill the concepts of interaction design down to just the basics, to focus on what is most useful for non-interaction designers. Using the design process as a framework, I’ll provide an overview of the basic building blocks, design principles, and underlying structure of interaction design, and illustrate them using familiar real-world examples. Through these basic elements, I’ll discuss how design decisions are made, how to evaluate them at each level of an interaction design, and more importantly, what makes a “good” design decision. I will also discuss one or two emerging trends in interaction design and show how these basic elements can also be used to understand and evaluate them.This presentation won’t turn everyone into an interaction designer, but it will give you an understanding of the basics, and hopefully move you further along the road to being a better “designer”.
Organizational X-Ray: two ONA case studies in the Italian Public SectorAndrea Pesoli
The document summarizes two case studies of organizational network analyses conducted in public sector organizations in Italy. Key findings from the analyses of the daily interaction networks, problem-solving networks, and innovation networks in the two organizations are presented. The analyses identified contractors as central players, structural holes, and the importance of tenure for innovation. Graphs are provided to illustrate aspects like roles, supply and demand gaps, and outliers.
Model-driven prototyping for corporate software specification Thomas Memmel
Model-driven prototyping is proposed as an approach to address increasing complexity in automotive human-machine interface development. Currently, development processes are predominantly paper-based and supported by heterogeneous tools. This leads to communication problems, unnecessary work, and delays. The proposed approach defines a domain-specific modeling language for automotive interfaces based on concepts identified by domain experts. Formal specifications can then be used to generate interactive prototypes early in development, allowing for rapid feedback. This standardized and model-driven process aims to improve flexibility, avoid duplicate work, and facilitate cross-discipline collaboration.
Presentation of functional design patterns for event processing with examples from TIBCO, Oracle, IBM and Prova event processing technologies. Superset of the Tutorial at DEBS2012. Editors Alex Alves, Catherine Moxey
Debs2009 Event Processing Languages TutorialOpher Etzion
The document outlines a tutorial on event processing languages. It discusses different styles of event processing languages including stream processing languages, rule oriented languages, and agent oriented languages. For stream processing languages, it covers key concepts like events, state, computational models, and programming models. It provides examples of stream processing languages like Esper, Coral8, and CCL.
The document discusses the FLIRT model for crowdsourcing which consists of five elements - Focus, Language, Incentives, Rules, and Tools. It provides details on each element and how they relate to defining a crowdsourcing activity. Focus relates to determining the business objectives, scope, scale, and depth of the activity. Language considers the social aspects that engage participants such as social objects and nature of interactions. Incentives, Rules, and Tools provide the framework for participants in terms of compensation, policies, and tools to complete tasks. The model provides a way to strategically plan a crowdsourcing initiative by considering each element.
At the core of all usability is a design—the one being used by your customer. The blueprint or foundation of that design is found in the interaction design. Over the years, I’ve worked with many people, from clients to co-workers, who are involved in design but who don’t consider themselves “designers”. They usually have good design instincts, but don’t have a “design” background—and they are always asking me how they can become better “designers”.In this presentation, I distill the concepts of interaction design down to just the basics, to focus on what is most useful for non-interaction designers. Using the design process as a framework, I’ll provide an overview of the basic building blocks, design principles, and underlying structure of interaction design, and illustrate them using familiar real-world examples. Through these basic elements, I’ll discuss how design decisions are made, how to evaluate them at each level of an interaction design, and more importantly, what makes a “good” design decision. I will also discuss one or two emerging trends in interaction design and show how these basic elements can also be used to understand and evaluate them.This presentation won’t turn everyone into an interaction designer, but it will give you an understanding of the basics, and hopefully move you further along the road to being a better “designer”.
Organizational X-Ray: two ONA case studies in the Italian Public SectorAndrea Pesoli
The document summarizes two case studies of organizational network analyses conducted in public sector organizations in Italy. Key findings from the analyses of the daily interaction networks, problem-solving networks, and innovation networks in the two organizations are presented. The analyses identified contractors as central players, structural holes, and the importance of tenure for innovation. Graphs are provided to illustrate aspects like roles, supply and demand gaps, and outliers.
Model-driven prototyping for corporate software specification Thomas Memmel
Model-driven prototyping is proposed as an approach to address increasing complexity in automotive human-machine interface development. Currently, development processes are predominantly paper-based and supported by heterogeneous tools. This leads to communication problems, unnecessary work, and delays. The proposed approach defines a domain-specific modeling language for automotive interfaces based on concepts identified by domain experts. Formal specifications can then be used to generate interactive prototypes early in development, allowing for rapid feedback. This standardized and model-driven process aims to improve flexibility, avoid duplicate work, and facilitate cross-discipline collaboration.
The document provides a template for a Software Design Document (SDD) that describes the architecture and design of a software system. The SDD template includes sections for an introduction, system overview, system architecture, data design, component design, human interface design, requirements matrix, and appendices. The system architecture section further breaks down the system into subsystems and modules and explains how they interact. The data and component design sections describe how data structures and algorithms implement the required functionality.
The document discusses the Architecture Tradeoff Analysis Method (ATAM) for evaluating software architectures. ATAM is a qualitative methodology that identifies tradeoffs between quality attributes like performance, security, and modifiability. It facilitates communication between stakeholders to clarify requirements and provide a framework for concurrent system design and analysis. The key outputs of ATAM include prioritized quality requirements, architectural approaches used, analysis questions, mapping of approaches to attributes, and risks, sensitivities, and tradeoffs identified.
A Reference Architecture for IoT: How to create a resilient, secure IoT cloudWSO2
This document discusses creating a secure Internet of Things (IoT) architecture. It recommends three rules for IoT security: don't be stupid, be smart, and think about what's different for IoT devices. It also notes unique challenges for IoT security like long device lifecycles and limited capabilities. The document advocates for using federated identity and access control to securely manage devices and data. It presents a reference architecture for IoT that incorporates real-time stream processing, analytics, identity management, and open source components.
by Brad Appleton,
Presented August 2006 at Architecture & Design World 2006; Chicago, IL USA
Software Configuration Management Patterns for Agile Software Architectures.
This presentation is about a lecture I gave within the "Software systems and services" immigration course at the Gran Sasso Science Institute, L'Aquila (Italy): http://cs.gssi.infn.it/.
http://www.ivanomalavolta.com
Software Architecture Views and ViewpointsHenry Muccini
This document discusses views and viewpoints in software architecture. It defines a viewpoint as a way of looking at a system that defines conventions for constructing views. A view is the result of applying a viewpoint to a system. The document discusses how stakeholders have different concerns that shape the viewpoints and views. It provides examples of viewpoints like the Rational Unified Process 4+1 views. The document emphasizes that using multiple views aligned with stakeholder concerns has become a standard practice in architecture description.
Fundamentos de la arquitectura de softwareRoger Villegas
Este documento presenta una breve historia de la arquitectura de software desde 1960 hasta la actualidad, destacando conceptos clave como estilos, lenguajes de descripción arquitectónica, marcos y vistas, procesos y metodologías, abstracción, escenarios, campos de investigación, arquitecturas comunes, modalidades y tendencias, y las diferencias entre arquitectura y diseño.
El documento presenta una introducción a las arquitecturas de software, definiendo conceptos básicos, los beneficios de una arquitectura de software y la arquitectura 4+1 vista. Proporciona una bibliografía de referencias y un mapa conceptual de tópicos de conocimiento sobre ingeniería de software.
Este documento describe los fundamentos de la arquitectura de software, incluyendo conceptos como el análisis de requisitos, lineamientos de calidad, estilos arquitectónicos como capas y flujo de datos, y métodos para el diseño arquitectónico como mapeo de flujos de datos. La arquitectura de software proporciona un marco coherente para guiar el desarrollo de software mediante el uso de patrones y abstracciones.
More and more organizations are moving their ETL workloads to a Hadoop based ELT grid architecture. Hadoop`s inherit capabilities, especially it`s ability to do late binding addresses some of the key challenges with traditional ETL platforms. In this presentation, attendees will learn the key factors, considerations and lessons around ETL for Hadoop. Areas such as pros and cons for different extract and load strategies, best ways to batch data, buffering and compression considerations, leveraging HCatalog, data transformation, integration with existing data transformations, advantages of different ways of exchanging data and leveraging Hadoop as a data integration layer. This is an extremely popular presentation around ETL and Hadoop.
Reference architecture for Internet of ThingsSujee Maniyam
What kind of a data infrastructure is needed, to support Internet of Things?
This talk presents a reference architecture.
We are actually building this architecture as open source project. See here : bit.ly / iotxyz
Open API and API Management - Introduction and Comparison of Products: TIBCO ...Kai Wähner
In October 2014, I had a talk at Jazoon in Zurich, Switzerland: "A New Front for SOA: Open API and API Management as Game Changer"
Open API represent the leading edge of a new business model, providing innovative ways for companies to expand brand value and routes to market, and create new value chains for intellectual property. In the past, SOA strategies mostly targeted internal users. Open APIs target mostly external partners.
This session introduces the concepts of Open API, its challenges and opportunities. API Management will become important in many areas, no matter if business-to-business (B2B) or business-to-customer (B2C) communication. Several real world use cases will discuss how to gain leverage due to API Management. The end of the session shows and compares API management products from different vendors such as TIBCO API Exchange, IBM, Apigee, 3scale, WSO2, MuleSoft, Mashery, Layer 7, Vordel
A reference architecture for the internet of thingsCharles Gibbons
The document proposes a reference architecture for the Internet of Things (IoT). It consists of distributed devices that communicate using various protocols. These devices are supported by a distributed service layer that provides functions like messaging, data transformation and protocol support. This service layer connects to business support systems providing capabilities like fulfilment, assurance and billing. The architecture supports various channels for device management and integration with identity management systems.
The document presents an overview of Internet of Things (IoT) concepts and proposes a reference architecture for IoT. It discusses core IoT concerns like connectivity, device management, data handling and security. It describes common IoT device types like Arduino, Raspberry Pi and communication protocols like HTTP, MQTT, CoAP. The proposed reference architecture aims to provide a scalable and secure way to interact with billions of connected devices by addressing issues like management, data processing and disaster recovery. An example implementation of the architecture for an RFID attendance tracking system is also presented.
Structured Vs, Object Oriented Analysis and DesignMotaz Saad
This document discusses structured vs object-oriented analysis and design (SAD vs OOAD) for software development. It outlines the phases and modeling techniques used in SAD like data flow diagrams, decision tables, and entity relationship diagrams. It also outlines the phases and modeling techniques used in OOAD like use cases, class diagrams, sequence diagrams, and state machine diagrams. The document compares key differences between SAD and OOAD, discusses textbooks on software engineering and UML, and references papers on using UML in practice and evaluating the impact and costs/benefits of UML in software maintenance.
The 4+1 view model was designed by Philippe Kruchten as a framework for describing the architecture of software systems using multiple views. It defines four primary views - logical, development, process, and physical - as well as a supplementary scenarios or use cases view. Each view represents a different stakeholder perspective and allows separation of architectural concerns through the use of modeling diagrams like UML.
Seminar about Semantic Complex Event Processing and Reaction RuleML presented at the School of Computer Science at McGill University on Sept. 9th, 2013 as part of the Transatlantic Business Process Management Education Network (http://bpmedu.net/) and presented at the DemAAL 2013 - Dem@Care Summer School on Ambient Assisted Living, 16-20 September 2013, Chania, Crete, Greece.
This document provides an overview of software architecture. It defines software architecture as the fundamental organization of a system embodied in its components, their relationships to each other, and to the environment, and the principles guiding its design and evolution. The document discusses software vs building architecture, architectural styles like layered, pipes and filters, and data-centered styles. It also covers standards, frameworks and methodologies used for software architecture. Finally, it discusses the human aspects of practicing software architecture and provides some case studies.
Event Driven Architecture : Managing Business Dynamics for Adaptive EnterpriseDassana Wijesekara
The slides used in the Talk delivered in WSO2Con Asia 2016 conference held on 18th February 2016 in Colombo, Sri Lanka. This talk was delivered under Architecture Patterns track.
Event Driven Architecture : Managing Business Dynamics for an Adaptive Enterp...Dassana Wijesekara
Event Driven Architecture (EDA) is a software architecture pattern that promotes the production, detection, consumption of and reaction to events. EDA is composed of events, event channels like message queues and pub/sub, and event processing paradigms. It supports agile, adaptive and responsive systems by broadcasting and asynchronously processing events. EDA can help IT systems adapt to increased business pressures and dynamics through loose coupling, timeliness, scalability and real-time event processing. Example use cases include the Internet of Things and cognitive computing applications.
The document provides a template for a Software Design Document (SDD) that describes the architecture and design of a software system. The SDD template includes sections for an introduction, system overview, system architecture, data design, component design, human interface design, requirements matrix, and appendices. The system architecture section further breaks down the system into subsystems and modules and explains how they interact. The data and component design sections describe how data structures and algorithms implement the required functionality.
The document discusses the Architecture Tradeoff Analysis Method (ATAM) for evaluating software architectures. ATAM is a qualitative methodology that identifies tradeoffs between quality attributes like performance, security, and modifiability. It facilitates communication between stakeholders to clarify requirements and provide a framework for concurrent system design and analysis. The key outputs of ATAM include prioritized quality requirements, architectural approaches used, analysis questions, mapping of approaches to attributes, and risks, sensitivities, and tradeoffs identified.
A Reference Architecture for IoT: How to create a resilient, secure IoT cloudWSO2
This document discusses creating a secure Internet of Things (IoT) architecture. It recommends three rules for IoT security: don't be stupid, be smart, and think about what's different for IoT devices. It also notes unique challenges for IoT security like long device lifecycles and limited capabilities. The document advocates for using federated identity and access control to securely manage devices and data. It presents a reference architecture for IoT that incorporates real-time stream processing, analytics, identity management, and open source components.
by Brad Appleton,
Presented August 2006 at Architecture & Design World 2006; Chicago, IL USA
Software Configuration Management Patterns for Agile Software Architectures.
This presentation is about a lecture I gave within the "Software systems and services" immigration course at the Gran Sasso Science Institute, L'Aquila (Italy): http://cs.gssi.infn.it/.
http://www.ivanomalavolta.com
Software Architecture Views and ViewpointsHenry Muccini
This document discusses views and viewpoints in software architecture. It defines a viewpoint as a way of looking at a system that defines conventions for constructing views. A view is the result of applying a viewpoint to a system. The document discusses how stakeholders have different concerns that shape the viewpoints and views. It provides examples of viewpoints like the Rational Unified Process 4+1 views. The document emphasizes that using multiple views aligned with stakeholder concerns has become a standard practice in architecture description.
Fundamentos de la arquitectura de softwareRoger Villegas
Este documento presenta una breve historia de la arquitectura de software desde 1960 hasta la actualidad, destacando conceptos clave como estilos, lenguajes de descripción arquitectónica, marcos y vistas, procesos y metodologías, abstracción, escenarios, campos de investigación, arquitecturas comunes, modalidades y tendencias, y las diferencias entre arquitectura y diseño.
El documento presenta una introducción a las arquitecturas de software, definiendo conceptos básicos, los beneficios de una arquitectura de software y la arquitectura 4+1 vista. Proporciona una bibliografía de referencias y un mapa conceptual de tópicos de conocimiento sobre ingeniería de software.
Este documento describe los fundamentos de la arquitectura de software, incluyendo conceptos como el análisis de requisitos, lineamientos de calidad, estilos arquitectónicos como capas y flujo de datos, y métodos para el diseño arquitectónico como mapeo de flujos de datos. La arquitectura de software proporciona un marco coherente para guiar el desarrollo de software mediante el uso de patrones y abstracciones.
More and more organizations are moving their ETL workloads to a Hadoop based ELT grid architecture. Hadoop`s inherit capabilities, especially it`s ability to do late binding addresses some of the key challenges with traditional ETL platforms. In this presentation, attendees will learn the key factors, considerations and lessons around ETL for Hadoop. Areas such as pros and cons for different extract and load strategies, best ways to batch data, buffering and compression considerations, leveraging HCatalog, data transformation, integration with existing data transformations, advantages of different ways of exchanging data and leveraging Hadoop as a data integration layer. This is an extremely popular presentation around ETL and Hadoop.
Reference architecture for Internet of ThingsSujee Maniyam
What kind of a data infrastructure is needed, to support Internet of Things?
This talk presents a reference architecture.
We are actually building this architecture as open source project. See here : bit.ly / iotxyz
Open API and API Management - Introduction and Comparison of Products: TIBCO ...Kai Wähner
In October 2014, I had a talk at Jazoon in Zurich, Switzerland: "A New Front for SOA: Open API and API Management as Game Changer"
Open API represent the leading edge of a new business model, providing innovative ways for companies to expand brand value and routes to market, and create new value chains for intellectual property. In the past, SOA strategies mostly targeted internal users. Open APIs target mostly external partners.
This session introduces the concepts of Open API, its challenges and opportunities. API Management will become important in many areas, no matter if business-to-business (B2B) or business-to-customer (B2C) communication. Several real world use cases will discuss how to gain leverage due to API Management. The end of the session shows and compares API management products from different vendors such as TIBCO API Exchange, IBM, Apigee, 3scale, WSO2, MuleSoft, Mashery, Layer 7, Vordel
A reference architecture for the internet of thingsCharles Gibbons
The document proposes a reference architecture for the Internet of Things (IoT). It consists of distributed devices that communicate using various protocols. These devices are supported by a distributed service layer that provides functions like messaging, data transformation and protocol support. This service layer connects to business support systems providing capabilities like fulfilment, assurance and billing. The architecture supports various channels for device management and integration with identity management systems.
The document presents an overview of Internet of Things (IoT) concepts and proposes a reference architecture for IoT. It discusses core IoT concerns like connectivity, device management, data handling and security. It describes common IoT device types like Arduino, Raspberry Pi and communication protocols like HTTP, MQTT, CoAP. The proposed reference architecture aims to provide a scalable and secure way to interact with billions of connected devices by addressing issues like management, data processing and disaster recovery. An example implementation of the architecture for an RFID attendance tracking system is also presented.
Structured Vs, Object Oriented Analysis and DesignMotaz Saad
This document discusses structured vs object-oriented analysis and design (SAD vs OOAD) for software development. It outlines the phases and modeling techniques used in SAD like data flow diagrams, decision tables, and entity relationship diagrams. It also outlines the phases and modeling techniques used in OOAD like use cases, class diagrams, sequence diagrams, and state machine diagrams. The document compares key differences between SAD and OOAD, discusses textbooks on software engineering and UML, and references papers on using UML in practice and evaluating the impact and costs/benefits of UML in software maintenance.
The 4+1 view model was designed by Philippe Kruchten as a framework for describing the architecture of software systems using multiple views. It defines four primary views - logical, development, process, and physical - as well as a supplementary scenarios or use cases view. Each view represents a different stakeholder perspective and allows separation of architectural concerns through the use of modeling diagrams like UML.
Seminar about Semantic Complex Event Processing and Reaction RuleML presented at the School of Computer Science at McGill University on Sept. 9th, 2013 as part of the Transatlantic Business Process Management Education Network (http://bpmedu.net/) and presented at the DemAAL 2013 - Dem@Care Summer School on Ambient Assisted Living, 16-20 September 2013, Chania, Crete, Greece.
This document provides an overview of software architecture. It defines software architecture as the fundamental organization of a system embodied in its components, their relationships to each other, and to the environment, and the principles guiding its design and evolution. The document discusses software vs building architecture, architectural styles like layered, pipes and filters, and data-centered styles. It also covers standards, frameworks and methodologies used for software architecture. Finally, it discusses the human aspects of practicing software architecture and provides some case studies.
Event Driven Architecture : Managing Business Dynamics for Adaptive EnterpriseDassana Wijesekara
The slides used in the Talk delivered in WSO2Con Asia 2016 conference held on 18th February 2016 in Colombo, Sri Lanka. This talk was delivered under Architecture Patterns track.
Event Driven Architecture : Managing Business Dynamics for an Adaptive Enterp...Dassana Wijesekara
Event Driven Architecture (EDA) is a software architecture pattern that promotes the production, detection, consumption of and reaction to events. EDA is composed of events, event channels like message queues and pub/sub, and event processing paradigms. It supports agile, adaptive and responsive systems by broadcasting and asynchronously processing events. EDA can help IT systems adapt to increased business pressures and dynamics through loose coupling, timeliness, scalability and real-time event processing. Example use cases include the Internet of Things and cognitive computing applications.
Learn about the Open Data Center Alliance Workgroups, Usage Models and Roadmap Structure from the perspective of the Alliance Technical Coordination Committee. This presentation was used in the Nov. 18, 2010 Alliance Webcast delivered by Howard Grodin, VP of Strategic Programs, Terrermark; Alliance Technical Coordination Committee Member, and Ravi Subranamiam, Intel Corporation; Alliance Technical Advisor.
For more information about the Open Data Center Alliance, visit www.opendatacenteralliance.org. You will also find the Webcast recording that accompanies this presentation there.
The document discusses software architecture and the Rational Unified Process (RUP). It provides definitions of key terms:
1) Software architecture is a structural plan that describes system elements, how they fit together, and how they work together to fulfill requirements. It guides implementation and sets expectations.
2) The RUP is an iterative process focusing on requirements and design. Each iteration captures requirements, performs analysis/design, implements, and tests to evolve the system. Risks are assessed and prioritized to guide iterations.
3) The RUP uses multiple "views" including use cases, components, and interactions to represent a system from different stakeholder perspectives.
This document provides an overview of the Agile Software Architecture course offered by NISI in 2017. The course consists of 8 sessions covering topics like agile architecture, architectural decision making, quality attributes, feedback and monitoring, and architecture evolution. It is taught by professors from Utrecht University and industry architects. The goal is to help architects think more strategically and discuss real-world cases. Participants come from various roles and companies in consulting, transportation, ERP, public sector and healthcare. They hope to improve their skills and address challenges regarding privacy, security and agility. More information can be found on the course website or by contacting the lead instructor, Slinger Jansen.
This document summarizes a discussion on improving standards development processes in the learning, education, and training domain. It outlines the current Process and Product Legitimacy model used to analyze standards. Participants identified opportunities like increasing stakeholder involvement and recognizing diverse standards bodies. Barriers included a lack of inclusiveness and understanding of standards scopes. Solutions proposed were learning from agile specification processes, improving adoption support, and managing expectations of policymakers. The document concludes by outlining an improved model with multiple perspectives to better understand standards development drivers and motivate diverse stakeholders.
Thales has been deploying Arcadia and Capella MBSE methods and tools for the past 15 years. As for any journey, there have been many joys and not less difficulties.
During this webinar, Thales presents the foundations of their MBSE approach, how their engineering practices have been improved with the use of models, and what are they doing now to sustain and drive this model-based transformation.
---------
This webinar was driven by Juan Navas (from Thales)
Juan Navas is a Systems Architect with +10 years’ experience on performing and implementing Systems Engineering practices in industrial organizations. He accompanies systems engineering managers and systems architects implement Model-Based Systems Engineering and Product Line Engineering approaches in operational projects, helping them defining their engineering strategies, objectives and practices.
Modular Documentation Joe Gelb Techshoret 2009Suite Solutions
Designing, building and maintaining a coherent content model is critical to proper planning, creation, management and delivery of documentation and training content. This is especially true when implementing a modular or topic-based XML standard such as DITA, SCORM and S1000D, and is essential for successfully facilitating content reuse, multi-purpose conditional publishing and user-driven content.
During this presentation we will review basic concepts and methods for implementing information architecture. We will then introduce an innovative, comprehensive methodology for information modeling and content development that employs recognized XML standards for representation and interchange of knowledge, such as Topic Maps and SKOS. In this way, semantic technologies designed for taxonomy and ontology development can be brought to bear for creating and managing technical documentation and training content, and ultimately impacting the usability and findability of technical information.
EDA With Glassfish ESB Jfall IEP Intelligent Event ProcessingEugene Bogaart
Presentation talks about theory of Event Driven Architecture and Complex Event Processing. Afterwards Intellligent Event Processing with GlassFish ESB is explaind.
Towards tool support for situational engineering of agile methodologySandhiya Rajagopal
The document discusses agile methodologies and situational method engineering (SME) approaches. It notes that SME aims to develop software methodologies tailored to specific project situations. It also discusses the need for computer-aided method engineering (CAME) tools to support SME and the development of agile methodologies. Specifically, it describes the Eclipse Process Framework Composer (EPFC) as an open source SME tool that addresses formalism and provides an extensible platform for assembly-based method engineering.
Knowledge-Based Analysis and Design (KBAD): An Approach to Rapid Systems Engi...Elizabeth Steiner
The document describes Knowledge-Based Analysis and Design (KBAD), a methodology developed by Systems and Proposal Engineering Company for rapid systems engineering and architecture development. KBAD combines system engineering and program management disciplines to develop an executable knowledge base that can support decision-making across a system's lifecycle. It utilizes a modified form of Model-Based Systems Engineering (MBSE) with simplified constructs and relationships between elements. The goal is to reduce complexity and capture the essential information needed for analysis and design in a more cost-effective manner than traditional approaches.
An Introductory Session on Enterprise Architecturekeshav2011
This document provides an introduction to enterprise architecture. It defines architecture as the organizational structure of a system and explains that enterprise architecture aims to align IT with business needs by taking a transverse view of the enterprise. The document outlines the TOGAF framework for enterprise architecture, which involves developing business, information, application, and infrastructure architectures through iterative phases. It provides examples of organizations that have implemented enterprise architecture and realized benefits like improved IT products and cost savings. Finally, it offers practical steps for getting started with enterprise architecture, such as choosing a framework, determining scope, and getting executive approval.
The document discusses the enterprise mobility viewpoint for IT architecture. It introduces enterprise mobility and presents a conceptual model for a mobile enterprise architecture (MEA). It describes key elements of the MEA including mobility sub-viewpoints, views, and stakeholders. Research was conducted on mapping the TOGAF architecture development method to the MEA and developing models to support enterprise mobility planning and initiatives.
CASE tools stand for Computer Aided Software Engineering tools. They are computer programs that help software engineers and analysts during the development process. CASE tools can generate diagrams, perform consistency checks between models, and integrate development across phases of the software lifecycle. They aim to improve productivity, quality, and management of the software development process.
This document discusses the role of architects in capability-based planning for the Department of Defense (DoD). It notes that DoD's capability value chain is missing a link between capability planning and development. The architect's role is to fill this gap by developing an architecture specification and engineerable requirements that can translate capability needs into systems that deliver capabilities. The document contrasts this role with platform-based planning of the past, where requirements and development focused more on individual platforms.
The document discusses software architecture, including its definition, types of architectures, views, and documentation. It defines software architecture as the fundamental organization of a system, including its components, relationships, and design principles. The document outlines different types of architectures like business, technical, and enterprise architectures. It also discusses common architecture views used in frameworks like RUP, RM-ODP, and DODAF. Finally, it covers architecture documentation and modeling techniques.
The following presentation covers the basics of Software Architecture and the related topics. Most of the information provided is given in short phrases. Refer to Wikipedia article on the same for more information.
This is meant to be a brief slideshow only.
Similar to Debs2010 tutorial on epts reference architecture v1.1c (20)
Main news related to the CCS TSI 2023 (2023/1695)Jakub Marek
An English 🇬🇧 translation of a presentation to the speech I gave about the main changes brought by CCS TSI 2023 at the biggest Czech conference on Communications and signalling systems on Railways, which was held in Clarion Hotel Olomouc from 7th to 9th November 2023 (konferenceszt.cz). Attended by around 500 participants and 200 on-line followers.
The original Czech 🇨🇿 version of the presentation can be found here: https://www.slideshare.net/slideshow/hlavni-novinky-souvisejici-s-ccs-tsi-2023-2023-1695/269688092 .
The videorecording (in Czech) from the presentation is available here: https://youtu.be/WzjJWm4IyPk?si=SImb06tuXGb30BEH .
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdfMalak Abu Hammad
Discover how MongoDB Atlas and vector search technology can revolutionize your application's search capabilities. This comprehensive presentation covers:
* What is Vector Search?
* Importance and benefits of vector search
* Practical use cases across various industries
* Step-by-step implementation guide
* Live demos with code snippets
* Enhancing LLM capabilities with vector search
* Best practices and optimization strategies
Perfect for developers, AI enthusiasts, and tech leaders. Learn how to leverage MongoDB Atlas to deliver highly relevant, context-aware search results, transforming your data retrieval process. Stay ahead in tech innovation and maximize the potential of your applications.
#MongoDB #VectorSearch #AI #SemanticSearch #TechInnovation #DataScience #LLM #MachineLearning #SearchTechnology
How to Get CNIC Information System with Paksim Ga.pptxdanishmna97
Pakdata Cf is a groundbreaking system designed to streamline and facilitate access to CNIC information. This innovative platform leverages advanced technology to provide users with efficient and secure access to their CNIC details.
Your One-Stop Shop for Python Success: Top 10 US Python Development Providersakankshawande
Simplify your search for a reliable Python development partner! This list presents the top 10 trusted US providers offering comprehensive Python development services, ensuring your project's success from conception to completion.
UiPath Test Automation using UiPath Test Suite series, part 6DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 6. In this session, we will cover Test Automation with generative AI and Open AI.
UiPath Test Automation with generative AI and Open AI webinar offers an in-depth exploration of leveraging cutting-edge technologies for test automation within the UiPath platform. Attendees will delve into the integration of generative AI, a test automation solution, with Open AI advanced natural language processing capabilities.
Throughout the session, participants will discover how this synergy empowers testers to automate repetitive tasks, enhance testing accuracy, and expedite the software testing life cycle. Topics covered include the seamless integration process, practical use cases, and the benefits of harnessing AI-driven automation for UiPath testing initiatives. By attending this webinar, testers, and automation professionals can gain valuable insights into harnessing the power of AI to optimize their test automation workflows within the UiPath ecosystem, ultimately driving efficiency and quality in software development processes.
What will you get from this session?
1. Insights into integrating generative AI.
2. Understanding how this integration enhances test automation within the UiPath platform
3. Practical demonstrations
4. Exploration of real-world use cases illustrating the benefits of AI-driven test automation for UiPath
Topics covered:
What is generative AI
Test Automation with generative AI and Open AI.
UiPath integration with generative AI
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Webinar: Designing a schema for a Data WarehouseFederico Razzoli
Are you new to data warehouses (DWH)? Do you need to check whether your data warehouse follows the best practices for a good design? In both cases, this webinar is for you.
A data warehouse is a central relational database that contains all measurements about a business or an organisation. This data comes from a variety of heterogeneous data sources, which includes databases of any type that back the applications used by the company, data files exported by some applications, or APIs provided by internal or external services.
But designing a data warehouse correctly is a hard task, which requires gathering information about the business processes that need to be analysed in the first place. These processes must be translated into so-called star schemas, which means, denormalised databases where each table represents a dimension or facts.
We will discuss these topics:
- How to gather information about a business;
- Understanding dictionaries and how to identify business entities;
- Dimensions and facts;
- Setting a table granularity;
- Types of facts;
- Types of dimensions;
- Snowflakes and how to avoid them;
- Expanding existing dimensions and facts.
Project Management Semester Long Project - Acuityjpupo2018
Acuity is an innovative learning app designed to transform the way you engage with knowledge. Powered by AI technology, Acuity takes complex topics and distills them into concise, interactive summaries that are easy to read & understand. Whether you're exploring the depths of quantum mechanics or seeking insight into historical events, Acuity provides the key information you need without the burden of lengthy texts.
Skybuffer SAM4U tool for SAP license adoptionTatiana Kojar
Manage and optimize your license adoption and consumption with SAM4U, an SAP free customer software asset management tool.
SAM4U, an SAP complimentary software asset management tool for customers, delivers a detailed and well-structured overview of license inventory and usage with a user-friendly interface. We offer a hosted, cost-effective, and performance-optimized SAM4U setup in the Skybuffer Cloud environment. You retain ownership of the system and data, while we manage the ABAP 7.58 infrastructure, ensuring fixed Total Cost of Ownership (TCO) and exceptional services through the SAP Fiori interface.
Monitoring and Managing Anomaly Detection on OpenShift.pdfTosin Akinosho
Monitoring and Managing Anomaly Detection on OpenShift
Overview
Dive into the world of anomaly detection on edge devices with our comprehensive hands-on tutorial. This SlideShare presentation will guide you through the entire process, from data collection and model training to edge deployment and real-time monitoring. Perfect for those looking to implement robust anomaly detection systems on resource-constrained IoT/edge devices.
Key Topics Covered
1. Introduction to Anomaly Detection
- Understand the fundamentals of anomaly detection and its importance in identifying unusual behavior or failures in systems.
2. Understanding Edge (IoT)
- Learn about edge computing and IoT, and how they enable real-time data processing and decision-making at the source.
3. What is ArgoCD?
- Discover ArgoCD, a declarative, GitOps continuous delivery tool for Kubernetes, and its role in deploying applications on edge devices.
4. Deployment Using ArgoCD for Edge Devices
- Step-by-step guide on deploying anomaly detection models on edge devices using ArgoCD.
5. Introduction to Apache Kafka and S3
- Explore Apache Kafka for real-time data streaming and Amazon S3 for scalable storage solutions.
6. Viewing Kafka Messages in the Data Lake
- Learn how to view and analyze Kafka messages stored in a data lake for better insights.
7. What is Prometheus?
- Get to know Prometheus, an open-source monitoring and alerting toolkit, and its application in monitoring edge devices.
8. Monitoring Application Metrics with Prometheus
- Detailed instructions on setting up Prometheus to monitor the performance and health of your anomaly detection system.
9. What is Camel K?
- Introduction to Camel K, a lightweight integration framework built on Apache Camel, designed for Kubernetes.
10. Configuring Camel K Integrations for Data Pipelines
- Learn how to configure Camel K for seamless data pipeline integrations in your anomaly detection workflow.
11. What is a Jupyter Notebook?
- Overview of Jupyter Notebooks, an open-source web application for creating and sharing documents with live code, equations, visualizations, and narrative text.
12. Jupyter Notebooks with Code Examples
- Hands-on examples and code snippets in Jupyter Notebooks to help you implement and test anomaly detection models.
Introduction of Cybersecurity with OSS at Code Europe 2024Hiroshi SHIBATA
I develop the Ruby programming language, RubyGems, and Bundler, which are package managers for Ruby. Today, I will introduce how to enhance the security of your application using open-source software (OSS) examples from Ruby and RubyGems.
The first topic is CVE (Common Vulnerabilities and Exposures). I have published CVEs many times. But what exactly is a CVE? I'll provide a basic understanding of CVEs and explain how to detect and handle vulnerabilities in OSS.
Next, let's discuss package managers. Package managers play a critical role in the OSS ecosystem. I'll explain how to manage library dependencies in your application.
I'll share insights into how the Ruby and RubyGems core team works to keep our ecosystem safe. By the end of this talk, you'll have a better understanding of how to safeguard your code.
Ivanti’s Patch Tuesday breakdown goes beyond patching your applications and brings you the intelligence and guidance needed to prioritize where to focus your attention first. Catch early analysis on our Ivanti blog, then join industry expert Chris Goettl for the Patch Tuesday Webinar Event. There we’ll do a deep dive into each of the bulletins and give guidance on the risks associated with the newly-identified vulnerabilities.
Debs2010 tutorial on epts reference architecture v1.1c
1. epts
event processing technical society
Tutorial v1.1
epts
event processing technical society
Content by: members of the
EPTS Reference Architecture Working Group
Event Processing Architectures
leading to an EPTS Reference Architecture
Courtesy of: Adrian Paschke (Freie Universitaet Berlin)
Paul Vincent (TIBCO Software)
Catherine Moxey (IBM)
Alex Alves (Oracle)
Themis Palpanas (University of Trento)
2. epts
event processing technical society
Tutorial
• Event Processing is an increasingly important area in
the field of IT
• Event Processing Architectures have evolved to
handle the needs of low-latency / high-throughput
event processing
• Event Processing Architecture diagrams are used to
describe the functions and component layouts of
event processing systems
• Various providers and suppliers use their own
architectural descriptions, and EPTS has collated and
refined these into a candidate “reference” architecture
2
3. epts
event processing technical society
Agenda
• Introduction to architectures, architecture
methodologies, and event processing
• Member architectures and salient features
• Skeleton reference architecture from EPTS
Reference Architecture Working Group
• Summary and future work of the EPTS Reference
Architecture Working Group
3
4. epts
event processing technical society
Agenda
• Introduction to architectures, architecture
methodologies, and event processing
• Member architectures and salient features
• Skeleton reference architecture from EPTS
Reference Architecture Working Group
• Summary and future work of the EPTS Reference
Architecture Working Group
4
5. epts
event processing technical society
Introduction to Event Processing
• Event-centric view of IT
• Events are
– Sent and Received
– Aggregated, Transformed into Data, Deleted
– Processed in queries, rules etc
– Cause actions like processes, service invocations, etc
5
6. epts
event processing technical society
Introduction to Event Processing
Event Processing,
Complex Event Processing,
Event Stream Processing
Event Processing Rules, etc.
Event Type Definitions,
Event Abstraction, Event Pattern
Detection, Event Composition
Event Management
etc. etc.
Events Derived
Events
Event Producer Event Consumer
(Event Source, (Event sink, event
Event Emitter) handler, event
listener)
Design time Run time Administration
7. epts
event processing technical society
About the EPTS Reference Architecture Working Group
• Started March, 2009
– 18 members, co-chairs are Adrian Paschke (RuleML) and Paul Vincent (TIBCO)
– July 09 added responsibilities from Metamodel Working Group
• Scope
– Define architecture patterns that are compatible with EPTS members’ Event
Processing solutions and products.
– Define terminology and components regarding Event Processing in
accordance with EPTS
– Identify and utilize best practices and methods for Technical Architecture
descriptions and interchange
– Liaise with relevant standards bodies for EP metamodels and reference
architectures
• Current work is focused on
– Discovery of existing Event Processing Architectures
• collected RAs from e.g. IBM, Oracle, Tibco, Streambase, Aleri, Microsoft…
– Definition of Terminology and Methodology for comparing and describing
Event Processing Reference Architectures
7
8. epts
event processing technical society
Relationship with the other EPTS Groups / Areas
• Application and Analysis
– EPTS Use Case WG
• Value and ROI
– EPTS Business Value WG
• Terminology
– EPTS Glossary WG
• Architecture & Metamodels
– EPTS Reference Architecture WG
• Features and Components
– EPTS Language WG
9. epts
event processing technical society
Reference Architecture and Reference Model
• Reference Architecture
A reference architecture models the abstract
architectural elements in the domain independent of
the technologies, protocols, and products that are used
to implement the domain.
• Reference Model
A reference model describes the important concepts
and relationships in the domain focusing on what
distinguishes the elements of the domain.
9
10. epts
event processing technical society
Motivation and Benefits
• Motivation
– Event Processing is evolving from many existing technologies
and creating or adapting different tools
– Potential adopters (stakeholders) may have problems
understanding and adequately defining EP-based
architectures and solutions.
• Benefits
– a Reference Architecture aids efficient Event Processing
solution development, by predefining
customizable abstract frames of reference
for specific stakeholder concerns and application domains.
• aids in reusability of successful EP architectures for frequently
occurring EP design problems
• enables easier comparison of proposed EP solutions
– Underlying Reference Model defines / explains the
terminology and components in Event Processing architectures
11. epts
event processing technical society
ANSI/IEEE Std 1471 :: ISO/IEC 42010 Methodology
• Recommended Practice for Architectural
Description of Software-intensive Systems
– Now an ISO/IEC 42010:2007 standard
– Includes 6 elements
1. Architectural description
2. System stakeholders and their concerns
3. One or more architectural views
4. Viewpoints
5. A record of all known inconsistencies among the architectural
description’s required constituents
6. A rationale for selection of the architecture
11
12. epts
event processing technical society
ISO/IEC 42010:2007 Terminology (1)
• Architecture
– The fundamental organization of a system embodied in its
components, their relationships to each other, and to the
environment, and the principles guiding ist design and
evolution.
• Architectural Description
– A collection of products that document the architecture.
• System
– A collection of components organized to accomplish a
specific function or set of functions.
• System Stakeholder
– A system stakeholder is an individual, team, or
organization (or classes thereof) with interests in, or
concerns relative to, a system
12
13. epts
event processing technical society
ISO/IEC 42010:2007 Terminology (2)
• View
– A representation of the whole system from the perspective
of a related set of concerns.
• Viewpoint
– A specification of the conventions for constructing and
using a view - a pattern or template which to develop
individual views by establishing the purposes and audience
for a view and the techniques for its creation and analysis.
• Model
– A view may consist of one or more models and a model
may participate in one or more views.
– Each model is defined according to the methods
established in the corresponding viewpoint definition.
13
14. epts
event processing technical society
Conceptual model of architectural description
from IEEE Std 1471- 2000 (ISO/IEC 42010:2007 )
14
15. epts
event processing technical society
Declaring a Viewpoint
• Each viewpoint is specified by:
– Viewpoint name
– The stakeholders addressed by the viewpoint
– The stakeholder concerns to be addressed by the viewpoint
– The viewpoint language, modeling techniques, or analytical methods
used
– The source, if any, of the viewpoint (e.g., author, literature citation)
• A viewpoint may also include:
– Any consistency or completeness checks associated with the
underlying method to be applied to models within the view
– Any evaluation or analysis techniques to be applied to models within
the view
– Any heuristics, patterns, or other guidelines which aid in the synthesis
of an associated view or its models
15
16. epts
event processing technical society
Architecture Views - Examples
• Domain Architecture
domain models represent domain requirement and logic
• e.g. process representation, use case analysis, free text
• Application Architecture
structural, logic architecture
– Functional Layering, e.g. functional multi-tier structure
– Functional Decomposition, e.g. Component Architecture, UML
(class/activity/sequence)
• System Architecture
– Concrete implementation of an architecture in a target platform
16
17. epts
event processing technical society
Example UML Architectural Views and Diagrams
UML defines 13 diagram models that describe 4+1 architectural views
4+1 architectural views model by Philippe Kruchten, IBM
18. epts
event processing technical society
Event Processing Reference Architecture Viewpoints
Viewpoint
Viewpoint Engineering EP Managing EP Business with EP
Element Architecture Architecture Architecture
Concepts How to How to apply? How to utilize / sell /
implement? own?
Stakeholders Architects / Project Manager Decision Maker,
Engineers Customer, Provider
Concerns Effective Operational Strategic and
construction and Management tactical
deployment management
Techniques / Modeling, IT (service/appl) Monitoring,
Languages Engineering management, Enterprise Decision
project Management,
management Governance
18
19. epts
event processing technical society
Agenda
• Introduction to architectures, architecture
methodologies, and event processing
• Member architectures and salient features
• Skeleton reference architecture from EPTS
Reference Architecture Working Group
• Summary and future work of the EPTS Reference
Architecture Working Group
19
20. epts
event processing technical society
Overview – Sample Member Architectures
• University of Trento - Themis Palpanas
• TIBCO – Paul Vincent
• Oracle - Alex Alves
• IBM - Catherine Moxey
21. epts
event processing technical society
Example Use Case
Courtesy of Opher Etzion
& Peter Niblett, IBM
21
22. epts
event processing technical society
Use Case Detail: FFD delivery and bid requests
GPS
Delivery Location
Request Van
Florist System
Bid Driver
Request
22
23. epts
event processing technical society
FDD Use Case: Stakeholders, Events, and Details
23
24. epts
event processing technical society
Overview – Sample Member Architectures
• University of Trento - Themis Palpanas
• TIBCO – Paul Vincent
• Oracle - Alex Alves
• IBM - Catherine Moxey
25. epts
event processing technical society
Entity Name System Service for CEP
Entity Identification
• what is the problem?
– different pieces of data may refer to the same real world entity
• entity: person, organization, location, conference, piece of hardware, etc
– references to entities are often in an event’s payload
25
26. epts
event processing technical society
Entity Identification
• what is the problem?
– different pieces of data may refer to the same real world entity
• entity: person, organization, location, conference, piece of hardware, etc
– references to entities are often in an event’s payload
• why is this problem important?
– incorrect identification of entities may lead to
• erroneous decisions in subsequent processing steps
• reduced overall performance quality
26
27. epts
event processing technical society
Entity Identification
• what is the problem?
– different pieces of data may refer to the same real world entity
• entity: person, organization, location, conference, piece of hardware, etc
– references to entities are often in an event’s payload
• why is this problem important?
– incorrect identification of entities may lead to
• erroneous decisions in subsequent processing steps
• reduced overall performance quality
• why is this problem relevant?
– events originate from several different sources
– sources may refer to same real-world entity in different ways
– if entity identification problem not tackled, event
filtering/correlation/etc. will produce wrong results
27
28. epts
event processing technical society
Our solution
• the Entity Name System (see References [1][2])
– scalable infrastructure for assigning and managing unique global
identifiers for named entities
• basic ideas
– any description of an entity is “resolved” into its global ID
– not a universal knowledge base about entities
• stores minimal amount of information about an entity for
– distinguishing entities one from another
– finding entities and their identifiers as a result of a query
– similar to lightweight master data management system
28
29. epts
event processing technical society
Entity Name System (ENS)
entity
repository
29
30. epts
event processing technical society
Entity Name System (ENS)
entity e1 id
repository
event event
source A
… • e1 … event
source B e1 source C
e1 •…
•… … 30
...
31. epts
event processing technical society
Entity Name System (ENS)
Event Processing
System
entity e1 id
repository
event event
source A
… • e1 … event
source B e1 source C
e1 •…
•… … 31
...
32. epts
event processing technical society
Entity Name System (ENS):
Reference Architecture
Event Processing
System
ENS node
Access Services
Matching Component
Lifecycle
Storage Management
entity e1 id
Component
repository
event event
source A
… • e1 … event
source B e1 source C
e1 •…
•… … 32
...
33. epts
event processing technical society
Entity Name System Service
event consumer
event modeler
event processing medium
event-entity identification ENS node
event originator
33
34. epts
event processing technical society
Entity Name System Service: Use Case
…
correct entity identification:
single driver dispatched for
both events
event processing medium customers X and Y
locations A and B
are two different persons
are the same address!
delivery
event-entity identification ENS node
location A(=B)
event originator
customer X customer Y
event entities from
delivery delivery
event 1 location A event 2 location B different data sources
34
35. epts
event processing technical society
Overview – Sample Member Architectures
• University of Trento - Themis Palpanas
• TIBCO – Paul Vincent
• Oracle - Alex Alves
• IBM - Catherine Moxey
36. epts
event processing technical society
TIBCO Reference Architecture(s)
36
38. epts
event processing technical society
TIBCO Example Architecture
Input
Events Complex / Event Processor:
+
Content -Event relationships
- Complex Event patterns and sequences
- (Optional) Inference Rules
- (Optional) Business Decisions Output
Events
(including
UI)
Services Input Data
Svc
38
39. epts
event processing technical society
TIBCO Example Architecture for FFD
Input
Events Complex / Event Processor:
+
Content -Event relationships
- Complex Event patterns and sequences
Operations:
- (Optional) Inference Rules
Channels:
TBA
Enrich Delivery Request
- (Optional) Business Decisions Output
Create + filter Bid List Events
Events: Create Bid Request
Delivery Request (including
GPS Location UI)
Channels:
Services Input Data TBA
Events:
Bid Request
Svc Data: Rejection
Florist Minimum Ranking
Driver Ranking
Van Region Location
Van-Driver association
Bid List, Driver List
39
40. epts
event processing technical society
TIBCO Example Architecture detail
Agent
Arrangement
Events and + Choreography
Data Event Operations
components for detecting patterns
Input includes
via queries, rules (ECA, inference,
static
Channel relationships
constraint etc),
+Destination / hierarchies
orchestrations (process, state), Display
with optional reactions and decisions
+Payload / ontology
+Metadata
+Timestamp(s) Complex / Event Processor
Outbound
Channel
+ Destination
+ Payload
Svc
+ Metadata
Data
Services (Services) Event and
+ Interfaces + Interfaces Data State
+ + Local Store
Choreographies Choreographies + Choreographies
required required / locks required
40
41. epts
event processing technical society
TIBCO Architecture – FFD detail
Agent
Arrangement
Events and + Choreography
Event Operations Agent structure:
Data
components for detecting patterns based on process load /
Input includes
via queries, rules (ECA, inference, freq requirements
static
Channel relationships
constraint etc),
+Destination
orchestrations (process, state),
Data / Event structures:
/ hierarchies
Display
with optional reactions and decisions
depends on operations
+Payload / ontology
+Metadata needed
+Timestamp(s) Complex / Event Processor
Processing operations:
Event format: rules, states etc based on
depends on channel and operations needed
Outbound
source requirements etc
Channel
TimeToLive : + Destination
depends on processing + Payload
approach used Svc
+ Metadata
Data
Services (Services)
Data location:
Event and
+ Interfaces + Interfaces latency, State
depends on Data
+ + Local Store
+ external sharing
Choreographies requirements + Choreographies
Choreographies
required required / locks required
41
42. epts
event processing technical society
Example Deployment Architecture
Distributed Event Processing Agents – see ref.
43. epts
event processing technical society
Overview – Sample Member Architectures
• University of Trento - Themis Palpanas
• TIBCO – Paul Vincent
• Oracle - Alex Alves
• IBM - Catherine Moxey
49. epts
event processing technical society
Overview – Sample Member Architectures
• University of Trento - Themis Palpanas
• TIBCO – Paul Vincent
• Oracle - Alex Alves
• IBM - Catherine Moxey
50. epts
event processing technical society
IBM Conceptual Architecture for EP
51. epts
event processing technical society
IBM EP Architecture – mapping to methodology
System: event processing system – event emitter, event bus, event handler
Environment: initial producers of events and their ultimate consumers
Stakeholders Concerns Architectural View
Event consumers – use Receive correct events in Event Handler (adapters, consumer-side EP
events to get information, consumable format, with services, orchestration), Event Processing
take action, detect problems, relevant data Services, Repositories, Event Emitters.
etc. Publication, Subscription, Notification services to
receive events
Event “Analysts” – create Means to specify the Event Instantiator, Event Processing Services,
and understand event events to be produced, Event Information Management and Query
specifications and the patterns to be Services, Event Security Services, Event
definitions, how events identified, event Registries. Event Repositories to do pattern-
should be processed, etc. enrichment etc. matching over time
Event System managers – Security, Performance, Event Security Services, Event Governance and
manage and control the EP Configurability related Security Services
system
Event System operators – Abilities to monitor and Event Monitoring and Analytic Infrastructure,
operate the EP system configure system, Event Channels, Publication, Subscription,
diagnose and solve Notification Services
problems
Event Producers Generated events are Event Instantiator, producer-side EP services,
made use of in some way Event Adapters, Event Bus…
52. epts
event processing technical society
IBM Conceptual Architecture for Decision Maker stakeholder
53. epts
event processing technical society
IBM Conceptual Architecture for Architect stakeholder
54. epts
event processing technical society
FFD Use Case mapped to IBM RA
Showing some of the Event Flows and Event Processing Agents
55. epts
event processing technical society
Agenda
• Introduction to architectures, architecture
methodologies, and event processing
• Member architectures and salient features
• Skeleton reference architecture from EPTS
Reference Architecture Working Group
• Summary and future work of the EPTS Reference
Architecture Working Group
55
56. epts
event processing technical society
Step 1: collect Event Processing Reference Architectures…
EP Network
Events: Downstre (parallel & pipelined)
Tuples, am
Packets Respons
, Data Applicati e/Applicat
Stream ion
s
on Layer
API’s,
Plug-ins
Query
Clients
Data Management Q Subscription
Layer: Q Clients
Q
Networked
Networked
StreamSystem
Processing
Adapter
Adapter
Output Event
Destinations
Input Event
Sources
Calls
Analysis
Modules
In-Process
System
In-Process
Adapter
Adapter
Event
Resource Processin
g
Layer Engine
Historical & Reference Data Event Storage
56 Aleri RA
Streambase RA Microsoft RA
…
TIBCO RA
IBM RA
57. epts
event processing technical society
Step 2: identify methodology to abstract an EPTS version…
Recipe
eventZero RA
Aleri RA
Streambase RA
Microsoft RA
TIBCO RA
IBM RA Progress RA
Oracle RA
58. epts
event processing technical society
Step 3: distil the common EPTS Reference Architecture(s)
59. epts
event processing technical society
Reference Architecture Viewpoints recap
Viewpoint Viewpoint
Element Engineering EP Managing EP Business with EP
Architecture Architecture Architecture
Concepts How to How to apply? How to utilize / sell /
implement? own?
Stakeholders Architects / Project Manager Decision Maker,
Engineers Customer, Provider
Concerns Effective Operational Strategic and
construction and Management tactical
deployment management
Techniques / Modeling, IT (service/appl) Monitoring,
Languages Engineering management, Enterprise Decision
project Management,
management Governance
59
60. epts
event processing technical society
Stakeholders and Viewpoints covered
Viewpoints (for CEP / stateful EP)
Stakeholder Component Functional
Decision Maker [Not applicable] Inputs, Outputs and
/ End User Processing Requirements
View
Architect / Solution Components Functions carried out in
Designer View CEP View
60
61. epts
event processing technical society
Stakeholders and Viewpoints covered
Viewpoints (for CEP / stateful EP)
Stakeholder Component Functional
Decision Maker [Not applicable] Inputs, Outputs and
/ End User Processing Requirements
View
Architect / Solution Components Functions carried out in
Designer View CEP View
61
62. epts
event processing technical society
Logical View
• View of the Event Processing Network?
• A Network Diagram?
• Currently under consideration!
63. epts
event processing technical society
Example Logical View
63
Source: WestGlobal
64. epts
event processing technical society
Stakeholders and Viewpoints covered
Viewpoints (for CEP / stateful EP)
Stakeholder Component Functional
Decision Maker [Not applicable] Inputs, Outputs and
/ End User Processing Requirements
View
Architect / Solution Components Functions carried out in
Designer View CEP View
64
65. epts
event processing technical society
Functional View
• Architect and Developer perspective
– includes the 3 main functions
(development, run-time and administration),
– targets primarily the automated event processing
operations
• Run-time functions in 2 main groups:
– the event infrastructure (sources and consumers)
external to the event processor under consideration,
– the event processor.
66. epts
event processing technical society
Functional View source: definitions of EP
Event Processing, Complex
Event Processing, Event
Stream Processing
Event Processing Rules, etc.
Event Type Definitions,
Event Abstraction, Event Pattern
Detection, Event Composition
Event Management
etc. etc.
Events Derived
Events
Event Producer Event Consumer
(Event Source, (Event sink, event
Event Emitter) handler, event
listener)
Design time Run time Administration
67. epts
event processing technical society
Reference Architecture: Functional View
Definition, Modeling, (continuous) Improvement
Event Reaction
Assessment, Routing, Prediction,
(Pattern, Control, Rule, Query, RegEx.etc)
Discovery, Learning
Event Process Monitoring, Control
0..*
State Management
State Management
Complex Event Detection
Event and Complex Event
Process Monitoring, Control
Consolidation, Composition,
Aggregation
0..*
Event Analysis
Analytics, Transforms, Tracking,
Scoring, Rating, Classification
0..*
Event Preparation
Identification, Selection, Filtering,
Monitoring, Enrichment
0..*
Event Production Event Consumption
Publication, Dashboard, Apps,
Retrieval External Reaction
Design time Run time Administration
68. epts
event processing technical society
Reference Architecture: Functional View / Runtime
Event Reaction
Assessment, Routing, Prediction,
Discovery, Learning
0..*
State Management
State Management
Complex Event Detection
Consolidation, Composition,
Aggregation
0..*
Event Analysis
Analytics, Transforms, Tracking,
Scoring, Rating, Classification
0..*
Event Preparation
Identification, Selection, Filtering,
Monitoring, Enrichment
0..*
Event Production Event Consumption
Publication, Dashboard, Apps,
Retrieval External Reaction
Run time
69. epts
event processing technical society
Reference Architecture: Functional View / Runtime
Event Production: the source of events for event processing.
• Event Publication: As a part of event production, events may be published
onto a communication mechanism (eg event bus) for use by event
consumers (including participants in event processing). This is analagous to
a "push" system for obtaining events.
• Event Retrieval: As a part of event production, events may be explicitly
retrieved from some detection system. This is analagous to a "pull" system
for obtaining events.
Event Production Event Consumption
Publication, Dashboard, Apps,
Retrieval External Reaction
70. epts
event processing technical society
Reference Architecture: Functional View / Runtime
Event Consumption: the process of using events from event publication and
processing. Event processing itself can be an event consumer, although for
the purposes of the reference architecture, event consumers are meant to
indicate downstream consumers of events generated in event processing.
• Dashboard: a type of event consumer that displays events as they occur to
some user community.
• Applications: a type of event consumer if it consumes events for its own
processes.
• External Reaction: caused through some event consumption, as the result
of some hardware or software process.
Event Production Event Consumption
Publication, Dashboard, Apps,
Retrieval External Reaction
71. epts
event processing technical society
Reference Architecture: Functional View / Runtime
Event Preparation: the process of preparing the event and associated payload and
metadata for further stages of event processing.
• Entity Identification: incoming events will need to be identified relative to prior events, such
as associating events with particular sources or sensors.
• Event Selection: particular events may be selected for further analysis. Different parts of
event processing may require different selections of events. See also event filtering.
• Event Filtering: a stream or list of events may be filtered on some payload or metadata
information such that some subset is selected for further processing.
• Event Monitoring: particular types of events may be monitored for selection for further
processing. This may utilise specific mechanisms external to the event processing such as
exploiting event production features.
• Event Enrichment: events may be "enriched" through knowledge gained through previous
events or data.
Event Preparation
Identification, Selection, Filtering,
Monitoring, Enrichment
72. epts
event processing technical society
Reference Architecture: Functional View / Runtime
Event Analysis: the process of analysing suitably prepared events and their
payloads and metadata for useful information.
• Event Analytics: the use of statistical methods to derive additional information about an
event or set of events.
• Event Transforms: processes carried out on event payloads or data, either related to
event preparation, analysis or processing.
• Event Tracking: where events related to some entity are used to identify state changes in
that entity.
• Event Scoring: the process by which events are ranked using a score, usually as a part of
a statistical analysis of a set of events. See also Event Analytics
• Event Rating: where events are compared to others to associate some importance or
other, possibly relative, measurement to the event.
• Event Classification: where events are associated with some classification scheme for
use in downstream processing.
Event Analysis
Analytics, Transforms, Tracking,
Scoring, Rating, Classification
73. epts
event processing technical society
Reference Architecture: Functional View / Runtime
Complex Event Detection: the process by which event analysis results in the
creation of new event information, or the update of existing complex events.
• Event Consolidation: combining disparate events together into a "main" or "primary"
event. See also event aggregation.
• Event Composition: composing new, complex events from existing, possibly source,
events.
• Event Aggregation: combining events to provide new or useful information, such as trend
information and event statistics. Similar to event consolidation.
Complex Event Detection
Consolidation, Composition,
Aggregation
74. epts
event processing technical society
Reference Architecture: Functional View / Runtime
Event Reaction: the process subsequent to event analysis and complex event
detection to handle the results of analysis and detection.
• Event Assessment: the process by which an event is assessed for inclusion in some
process, incorporation in some other event, etc.
• Event Routing: the process by which an event is redirected to some process, computation
element, or other event sink.
• Event Prediction: where the reaction to some event processing is that some new event is
predicted to occur.
• Event Discovery: where the reaction to some event processing is the disclosure of a new,
typically complex, event type.
• Note that event prediction is predicting some future event, usually of a known type, whereas event
discovery is the uncovering of a new event type. See also event-based learning.
• Event-based Learning: the reaction to some event processing that uses new event
information to add to some, typically statistical-based, understanding of events.
• Note that event-based learning is a specialisation of
general machine learning and predictive analytics.
Event Reaction
Assessment, Routing, Prediction,
Discovery, Learning
75. epts
event processing technical society
Reference Architecture: Functional View / Design time
Definition, Modeling, (continuous) Improvement
Covers the definition, modeling, improvement /
(Pattern, Control, Rule, Query, RegEx.etc)
maintenance of the artifacts
used in event processing:
Event and Complex Event
• event definitions, including event metadata and payloads,
• event and event object organisations and structures,
• event processing transformations / queries / rules /
procedures / flows / states / decisions /
expressions (although these can sometimes be
considered as administrative updates in some situations)
Design time
76. epts
event processing technical society
Reference Architecture: Functional View / Administration
Administrative concepts of
Event Process Monitoring, Control
monitoring and control. This may involve
• starting and stopping the application and event
Process Monitoring, Control
processing elements, including application monitors
• providing and updating security levels to event inputs and
outputs (also can design-time)
• management of high availability and reliability resources,
such as hot standby processes
• resource utilisation monitoring of the event processing
components
• process updates, such as how-swapping of event
processing definitions to newer versions.
Administration
77. epts
event processing technical society
Agenda
• Introduction to architectures, architecture
methodologies, and event processing
• Member architectures and salient features
• Skeleton reference architecture from EPTS
Reference Architecture Working Group
• Summary and future work of the EPTS Reference
Architecture Working Group
77
78. epts
event processing technical society
Current Works
• Terminology and Methodology
– ANSI/IEEE Std 1471 :: ISO/IEC 42010 Terminology
– EPTS-RA Terminology
– Concepts from the EPTS Glossary
• Reference Architecture Discovery
• Reference Architecture Comparison
– Identify commonalities in proposed architectures
– Collect core and additional CEP system functions and components
• Member Reference Architecture Descriptions
– Using the EPTS-RA Methodology and Terminology
• Application of RA Descriptions to Use Cases
79. epts
event processing technical society
Next Steps
• Generalize the EPTS Reference Architecture descriptions
– addressing important stakeholders and their views
– using rigorous RA methodology and terminology (+ glossary)
• Evaluate the EPTS-RA descriptions
– apply on selected EPTS use cases and compare to member experience
– compare with Best Practice Guidelines
• Review Logical Architecture requirements for Reference purposes
• Possible Outputs:
– EPTS-RA Description document
– EPTS-RA Design Patterns and Best Practice Guidelines document
– Wiley Book "Pattern Oriented Software Architecture: Architectures,
Models and Patterns for Event Processing" (already in preparation)
– Input for Event Processing Metamodels and associated standards
80. epts
event processing technical society
Summary
• Reference Architecture provides a common set of
EP Functions that may be included in
– EP systems
– EP-related tools
• Describes the mapping from Glossary of Terms to
Implementation
• Provides the basis for EP agents, operators and
languages
80
81. epts
event processing technical society
Thank you !
Acknowledgment to the Event Processing Technical Society
Reference Architecture working group: David Tucker (Event
Zero), John Morrell (Coral8, Inc.), Baden Hughes (Event Zero),
Dieter Gawlick (Oracle), Alex Alves (Oracle), Anand Srinivasan
(Oracle), Shailendra Mishra (Oracle), Zbigniew Jerzak (TU
Dresden), Hans-Arno Jacobsen (University Toronto), Albert
Mavashev (Nastel Technologies Inc.), Simon Courtenage
(University of Westminster), Catherine Moxey (IBM United
Kingdom Limited), Richard Tibbetts (Streambase), Brian Connell
(WestGlobal), Guy Sharon (IBM), Themis Palpanas (University
of Trento)
81
82. epts
event processing technical society
References
• EPTS Glossary
http://www.ep-ts.com/component/option,com_docman/task,doc_download/gid,66/Itemid,84/
• University of Trento Architecture section:
1. Heiko Stoermer, Themis Palpanas, George Giannakopoulos. The Entity Name System:
Enabling the Web of Entities. International Workshop on Data Engineering meets the
Semantic Web (DESWeb), in conjunction with the IEEE International Conference on Data
Engineering (ICDE), Long Beach, CA, USA, March 2010
2. Zoltan Miklos, Nicolas Bonvin, Paolo Bouquet, Michele Catasta, Daniele Cordioli, Peter
Fankhauser, Julien Gaugaz, Ekaterini Ioannou, Hristo Koshutanski, Antonio Mana,
Claudia Niederee, Themis Palpanas, Heiko Stoermer. From Web Data to Entities and
Back. International Conference on Advanced Information Systems Engineering (CAiSE),
Hammamet, Tunisia, June 2010
• IBM Architecture section:
Conceptual Architecture paper: http://www.redbooks.ibm.com/redpapers/pdfs/redp4642.pdf
• TIBCO Architecture section:
Sergio Gonik & Dan Buchko, BusinessEvents Distributed Processing
Implementation Patterns, Tips, and Techniques, TUCON TIBCO User Conference, Las
Vegas, May 2010