The document discusses Service Modelling and Representation Techniques from an Enterprise Architecture perspective, focusing on standards like VDM, USDL, and SoaML. It provides an agenda covering topics like business and IT architecture frameworks, service definitions, modeling languages, and how these techniques can influence emerging standards. Examples are given of modeling business processes and services using notations like e3Value, REA, SoaML, and USDL.
Service Modelling and Representation Techniques - a holistic Enterprise Arch...ServiceWave 2010
Service Modelling and Representation Techniques - a holistic Enterprise Architecture perspective on using and influencing the emerging standards of VDM, USDL and SoaML
Dr. Arne-Jørgen Berre
SINTEF
Networked Systems and Services
Ghent, Dec 13th, 2010
Service Wave 2010 - FIA
- This document discusses IT service industry in Korea and ways to enhance its international competitiveness.
- It introduces Professor June Sung Park from KAIST who will give a seminar on the history and recent trends of the IT service industry, characteristics of IT service business, key processes of IT service management, and plans to strengthen Korea's competitiveness in the global IT service industry.
- IT service industry has transitioned from custom development to cloud consulting and implementation, utilizing reusable services and frameworks. Leading companies invest in service R&D and build reusable asset platforms to improve process maturity, technology maturity and reuse of software assets.
The document discusses the future of work in the platform economy. It notes that network externalities will lead to more project-based and task-based job contracts as the job market becomes more fluid. Lower transaction costs from platforms will result in flatter organizational hierarchies and blurred boundaries between organizations. Digital service platforms that integrate into business processes will improve work productivity by taking over certain middle management and administrative tasks.
This document discusses how business model innovation for digital enterprises can be supported through the use of value models. It describes a modeling language called VDML (Value Delivery Modeling Language) that provides an underlying representation of business model innovation frameworks. VDML allows for the representation of value networks and business activity networks to support business model innovation. The document outlines how VDML relates to other areas like product, process and service innovation and how it can support business model analysis and simulation through a cloud-based platform.
MODELING SERVICE ORIENTED ARCHITECTURE- A COMPREHENSIVE COURSEAmit Midha
The document outlines an upcoming training course on service-oriented modeling. The 3-day course will cover topics such as service-oriented analysis and modeling frameworks, modeling service structures and contexts, using the SOAML language to model services in relation to organizational processes, and utilizing modeling tools like Sparx Systems Enterprise Architect. Attendees will learn how to visualize and model service-oriented architectures from initial concept through implementation. The course aims to provide a comprehensive understanding of service-oriented modeling concepts, techniques and deliverables.
Vdml guest lecture ugent, november 2013Henk De Man
This document introduces the Value Delivery Modeling Language (VDML), a new modeling language to support value-driven business design. VDML focuses on representing businesses as value networks by modeling the flow of deliverables and contributions of value. It provides a higher level of abstraction to model what a business does, how it operates, and who is responsible. VDML is intended to help businesses address challenges like finding the most profitable business models and efficient partnership arrangements through computerized modeling and analysis. The document outlines several key VDML concepts like capabilities, collaborations, and value propositions and shows some early examples of how VDML can be used to model business networks and value flows.
1. Service science, management, and engineering (SSME) is an interdisciplinary approach to studying, designing, and implementing complex service systems.
2. SSME aims to make productivity, quality, compliance, sustainability, learning rates, and innovation more predictable for organization-to-organization services.
3. There are several frameworks for conceptualizing service systems, including considering the front stage customer experience separately from the back office operations.
Service Modelling and Representation Techniques - a holistic Enterprise Arch...ServiceWave 2010
Service Modelling and Representation Techniques - a holistic Enterprise Architecture perspective on using and influencing the emerging standards of VDM, USDL and SoaML
Dr. Arne-Jørgen Berre
SINTEF
Networked Systems and Services
Ghent, Dec 13th, 2010
Service Wave 2010 - FIA
- This document discusses IT service industry in Korea and ways to enhance its international competitiveness.
- It introduces Professor June Sung Park from KAIST who will give a seminar on the history and recent trends of the IT service industry, characteristics of IT service business, key processes of IT service management, and plans to strengthen Korea's competitiveness in the global IT service industry.
- IT service industry has transitioned from custom development to cloud consulting and implementation, utilizing reusable services and frameworks. Leading companies invest in service R&D and build reusable asset platforms to improve process maturity, technology maturity and reuse of software assets.
The document discusses the future of work in the platform economy. It notes that network externalities will lead to more project-based and task-based job contracts as the job market becomes more fluid. Lower transaction costs from platforms will result in flatter organizational hierarchies and blurred boundaries between organizations. Digital service platforms that integrate into business processes will improve work productivity by taking over certain middle management and administrative tasks.
This document discusses how business model innovation for digital enterprises can be supported through the use of value models. It describes a modeling language called VDML (Value Delivery Modeling Language) that provides an underlying representation of business model innovation frameworks. VDML allows for the representation of value networks and business activity networks to support business model innovation. The document outlines how VDML relates to other areas like product, process and service innovation and how it can support business model analysis and simulation through a cloud-based platform.
MODELING SERVICE ORIENTED ARCHITECTURE- A COMPREHENSIVE COURSEAmit Midha
The document outlines an upcoming training course on service-oriented modeling. The 3-day course will cover topics such as service-oriented analysis and modeling frameworks, modeling service structures and contexts, using the SOAML language to model services in relation to organizational processes, and utilizing modeling tools like Sparx Systems Enterprise Architect. Attendees will learn how to visualize and model service-oriented architectures from initial concept through implementation. The course aims to provide a comprehensive understanding of service-oriented modeling concepts, techniques and deliverables.
Vdml guest lecture ugent, november 2013Henk De Man
This document introduces the Value Delivery Modeling Language (VDML), a new modeling language to support value-driven business design. VDML focuses on representing businesses as value networks by modeling the flow of deliverables and contributions of value. It provides a higher level of abstraction to model what a business does, how it operates, and who is responsible. VDML is intended to help businesses address challenges like finding the most profitable business models and efficient partnership arrangements through computerized modeling and analysis. The document outlines several key VDML concepts like capabilities, collaborations, and value propositions and shows some early examples of how VDML can be used to model business networks and value flows.
1. Service science, management, and engineering (SSME) is an interdisciplinary approach to studying, designing, and implementing complex service systems.
2. SSME aims to make productivity, quality, compliance, sustainability, learning rates, and innovation more predictable for organization-to-organization services.
3. There are several frameworks for conceptualizing service systems, including considering the front stage customer experience separately from the back office operations.
Cloud to crowd talk to COST Virtual work Bucharest 2014James Stewart
This document summarizes a presentation on online work exchanges and their present and future role in the network economy. It discusses how such exchanges provide new ways for people to find work and for clients to find workers. While often criticized as enabling "free labor," the presentation argues they provide opportunities for flexible employment. Potential policy areas impacted are identified as employment, skills, entrepreneurship, social policy and international development. Challenges discussed include how to support workers and platforms while addressing issues like insecure work. Overall the presentation explores both the opportunities and challenges of online work exchanges in redefining how people are employed and work gets done.
The Societal and Business Application Perspective ictseserv
The document discusses the evolution of service paradigms and business models towards a utility-based service infrastructure for the future internet. It explores key questions around developing and maintaining such infrastructure, preserving open competition, commoditizing basic services to stimulate innovation, and optimal governance models. The session aims to pave the way for architectures leveraging future internet technologies from an enterprise perspective.
The document discusses leveraging a service-oriented and model-driven approach to enterprise architecture. It introduces key concepts like enterprise architecture, service-oriented architecture, and model-driven architecture. It provides an example of modeling a "Dealer Network" as a services architecture using these concepts.
The document discusses perspectives on service innovation and innovative services. It notes that services were traditionally dismissed as playing a small role in innovation but that perspective has changed as services have adopted new technologies. The document outlines different approaches to conceptualizing service innovation, including whether services are qualitatively distinct from manufacturing. It also discusses challenges in measuring service innovation using traditional metrics focused on products and R&D. Finally, it explores whether different models and metrics are needed to study innovation in services.
The Content Assembly Mechanism specification provides an open XML based system for using business rules to define, validate and compose specific business documents from generalized schema elements, attributes and structures. A CAM rule set and document assembly template defines the specific business context, content requirement, and transactional function of a document. A CAM template must be capable of consistently reproducing documents that can successfully carry out the specific transactional function that they were designed for. CAM also provides the foundation for creating industry libraries and dictionaries of schema elements and business document structures to support business process needs.
The Digital economy's next Top e-Business ModelIan Miles
The document discusses the evolution of digital economies and business models over time, from mainframes in the 1960s to ubiquitous mobile services today. It also discusses the boom in business model thinking and mentions in the 1990s and 2000s due to the rise of e-business and dot-com bubble. Additionally, the document outlines some of the key elements of business models, including value propositions, key resources, key activities and processes, customer relationships, channels, customer segments, and revenue streams.
This document discusses Microsoft's vision and strategy around service-oriented architecture (SOA) and integration. It outlines how Microsoft platforms like .NET 3.0, Windows Workflow Foundation, and BizTalk Server enable the development of composite and integrated applications using SOA principles. The document also provides examples of how major financial institutions are using Microsoft technologies in mission-critical applications.
The document discusses moving from silo-based development to a modular, open architecture based on service-oriented architecture (SOA). It notes that typical IT budgets spend 70-90% on maintenance due to rigid, monolithic applications. SOA defines services as modular, loosely coupled units that can be reused. The document recommends a phased approach to SOA implementation and provides examples of SOA adoption in Israel, highlighting challenges around monitoring, operations, and organizational issues.
Value Creation from IS Integration: From ASP to Web Services?webhostingguy
The document discusses the transition from ASPs to web services and the benefits of web services for integration. It notes that early ASP models were flawed as they focused too much on marketing and commoditized applications rather than creating value. Web services allow for greater customization, integration across business processes, and many-to-many relationships that facilitate collaboration and innovation across organizations. The transition to web services represents a shift from application-centric to process-centric systems and will drive changes in business models and industry structures.
Value Creation from IS Integration: From ASP to Web Services?webhostingguy
The document discusses the transition from ASPs to web services and the benefits of web services for integration. It notes that early ASP models were flawed as they focused too much on marketing and commoditized applications rather than creating value. Web services allow for greater customization, integration across business processes, and many-to-many relationships that facilitate collaboration and innovation across organizations. The transition to web services represents a shift from application-centric to process-centric systems and will drive changes in business models and industry structures.
The document summarizes a presentation given by Simeon Simeonov of Polaris Venture Partners on the status and future of web services from both end user and investor perspectives. Key points discussed include the current state of web services adoption, market analysis of web services categories and companies, case studies of large companies implementing web services, and lessons learned for startups, end users, and the industry.
The document discusses how service-oriented architecture (SOA) impacts IT infrastructure and introduces new considerations for performance, security, availability, service management, and virtualization. Key points include:
- SOA introduces new infrastructure components like XML gateways and introduces challenges for monitoring distributed applications and isolating performance bottlenecks.
- Security must be implemented across multiple layers to secure messages in SOA environments while propagating identities among partners.
- High availability, disaster recovery, and scalability require techniques like clustering, workload management, and data replication across SOA components.
- Service management requires monitoring all components and closing the loop between infrastructure events and business services.
- Virtualization can help decouple applications from infrastructure
Introduction to Service Oriented ArchitectureDATA Inc.
The document introduces SOA and discusses its key concepts. It describes why organizations adopt SOA, defines what SOA is, and outlines some of its benefits including reuse, flexibility and cost savings. It also discusses components of a SOA system like services, service contracts and an enterprise service bus.
Callatay & Wouters is a software company that provides banking solutions such as Thaler, Kyudo, and Teran. These are service-oriented architecture core banking solutions that can support retail, wholesale, treasury and other banking operations. The company proposes these solutions to Vietnamese banks as a way to gain benefits such as low risk, quick implementation, and high customer satisfaction.
Um Case de Implantação de SOA em uma Telco brasileiraDavi Silva
Presentation about the approach used in order to implement SOA in a Telco.
Presented during "SOA and BPM Event" (IQPC), December 2006, São Paulo, Brazil.
Author: Davi Carvalho (CIO)
This document provides an overview of service-oriented architecture (SOA) and related concepts. It discusses SOA principles like loose coupling and implementation neutrality. It describes the roles involved in SOA like providers, registries, and requestors. Core Web services standards like SOAP, WSDL, and UDDI are explained. Examples of synchronous and asynchronous messaging between services are also provided.
Semantic Web Process Lifecycle: Role of Semantics in Annotation, Discovery, C...Amit Sheth
“Semantic Web Process Lifecycle: Role of Semantics in Annotation, Discovery, Composition and Orchestration,” Keynote/Invited Talk, WWW 2003 Workshop on E-Services and the Semantic Web, Budapest, Hungary, May 20, 2003.
Here is the paper based on this talk:
Kaarthik Sivashanmugam, Kunal Verma,Amit Sheth, and John Miller, 'Adding Semantics to Web Services Standards,'International Conference on Web Services 2003 (ICWS'03), Las Vegas, NV, June 23-26, 2003.
http://knoesis.org/library/resource.php?id=00174
While going through in-depth on Service Oriented Architecture (SOA) and Enterprise Architecture (EA) as part of my Oracle SOA and TOGAF certification, I had questions as to how SOA fits in the EA, and how TOGAF for EA support adopting SOA.
Here is an attempt to address that...
I'm presenting the IBM CIO 2010 Outlook at IBM iForum, Zurich (26th November 2007). I can't take the credit for writing it; Dave Newbold did the hard work on this one.
This document provides an overview of service-oriented architecture (SOA). It defines SOA as a design paradigm that specifies the creation of automation logic in the form of discrete, autonomous services. The key benefits of SOA include enabling flexible, federated business processes and optimization through reuse of services across organizations. The document discusses SOA concepts like loose coupling, service contracts, and different service types. It also outlines the layers of a service architecture and some core SOA principles.
Cloud to crowd talk to COST Virtual work Bucharest 2014James Stewart
This document summarizes a presentation on online work exchanges and their present and future role in the network economy. It discusses how such exchanges provide new ways for people to find work and for clients to find workers. While often criticized as enabling "free labor," the presentation argues they provide opportunities for flexible employment. Potential policy areas impacted are identified as employment, skills, entrepreneurship, social policy and international development. Challenges discussed include how to support workers and platforms while addressing issues like insecure work. Overall the presentation explores both the opportunities and challenges of online work exchanges in redefining how people are employed and work gets done.
The Societal and Business Application Perspective ictseserv
The document discusses the evolution of service paradigms and business models towards a utility-based service infrastructure for the future internet. It explores key questions around developing and maintaining such infrastructure, preserving open competition, commoditizing basic services to stimulate innovation, and optimal governance models. The session aims to pave the way for architectures leveraging future internet technologies from an enterprise perspective.
The document discusses leveraging a service-oriented and model-driven approach to enterprise architecture. It introduces key concepts like enterprise architecture, service-oriented architecture, and model-driven architecture. It provides an example of modeling a "Dealer Network" as a services architecture using these concepts.
The document discusses perspectives on service innovation and innovative services. It notes that services were traditionally dismissed as playing a small role in innovation but that perspective has changed as services have adopted new technologies. The document outlines different approaches to conceptualizing service innovation, including whether services are qualitatively distinct from manufacturing. It also discusses challenges in measuring service innovation using traditional metrics focused on products and R&D. Finally, it explores whether different models and metrics are needed to study innovation in services.
The Content Assembly Mechanism specification provides an open XML based system for using business rules to define, validate and compose specific business documents from generalized schema elements, attributes and structures. A CAM rule set and document assembly template defines the specific business context, content requirement, and transactional function of a document. A CAM template must be capable of consistently reproducing documents that can successfully carry out the specific transactional function that they were designed for. CAM also provides the foundation for creating industry libraries and dictionaries of schema elements and business document structures to support business process needs.
The Digital economy's next Top e-Business ModelIan Miles
The document discusses the evolution of digital economies and business models over time, from mainframes in the 1960s to ubiquitous mobile services today. It also discusses the boom in business model thinking and mentions in the 1990s and 2000s due to the rise of e-business and dot-com bubble. Additionally, the document outlines some of the key elements of business models, including value propositions, key resources, key activities and processes, customer relationships, channels, customer segments, and revenue streams.
This document discusses Microsoft's vision and strategy around service-oriented architecture (SOA) and integration. It outlines how Microsoft platforms like .NET 3.0, Windows Workflow Foundation, and BizTalk Server enable the development of composite and integrated applications using SOA principles. The document also provides examples of how major financial institutions are using Microsoft technologies in mission-critical applications.
The document discusses moving from silo-based development to a modular, open architecture based on service-oriented architecture (SOA). It notes that typical IT budgets spend 70-90% on maintenance due to rigid, monolithic applications. SOA defines services as modular, loosely coupled units that can be reused. The document recommends a phased approach to SOA implementation and provides examples of SOA adoption in Israel, highlighting challenges around monitoring, operations, and organizational issues.
Value Creation from IS Integration: From ASP to Web Services?webhostingguy
The document discusses the transition from ASPs to web services and the benefits of web services for integration. It notes that early ASP models were flawed as they focused too much on marketing and commoditized applications rather than creating value. Web services allow for greater customization, integration across business processes, and many-to-many relationships that facilitate collaboration and innovation across organizations. The transition to web services represents a shift from application-centric to process-centric systems and will drive changes in business models and industry structures.
Value Creation from IS Integration: From ASP to Web Services?webhostingguy
The document discusses the transition from ASPs to web services and the benefits of web services for integration. It notes that early ASP models were flawed as they focused too much on marketing and commoditized applications rather than creating value. Web services allow for greater customization, integration across business processes, and many-to-many relationships that facilitate collaboration and innovation across organizations. The transition to web services represents a shift from application-centric to process-centric systems and will drive changes in business models and industry structures.
The document summarizes a presentation given by Simeon Simeonov of Polaris Venture Partners on the status and future of web services from both end user and investor perspectives. Key points discussed include the current state of web services adoption, market analysis of web services categories and companies, case studies of large companies implementing web services, and lessons learned for startups, end users, and the industry.
The document discusses how service-oriented architecture (SOA) impacts IT infrastructure and introduces new considerations for performance, security, availability, service management, and virtualization. Key points include:
- SOA introduces new infrastructure components like XML gateways and introduces challenges for monitoring distributed applications and isolating performance bottlenecks.
- Security must be implemented across multiple layers to secure messages in SOA environments while propagating identities among partners.
- High availability, disaster recovery, and scalability require techniques like clustering, workload management, and data replication across SOA components.
- Service management requires monitoring all components and closing the loop between infrastructure events and business services.
- Virtualization can help decouple applications from infrastructure
Introduction to Service Oriented ArchitectureDATA Inc.
The document introduces SOA and discusses its key concepts. It describes why organizations adopt SOA, defines what SOA is, and outlines some of its benefits including reuse, flexibility and cost savings. It also discusses components of a SOA system like services, service contracts and an enterprise service bus.
Callatay & Wouters is a software company that provides banking solutions such as Thaler, Kyudo, and Teran. These are service-oriented architecture core banking solutions that can support retail, wholesale, treasury and other banking operations. The company proposes these solutions to Vietnamese banks as a way to gain benefits such as low risk, quick implementation, and high customer satisfaction.
Um Case de Implantação de SOA em uma Telco brasileiraDavi Silva
Presentation about the approach used in order to implement SOA in a Telco.
Presented during "SOA and BPM Event" (IQPC), December 2006, São Paulo, Brazil.
Author: Davi Carvalho (CIO)
This document provides an overview of service-oriented architecture (SOA) and related concepts. It discusses SOA principles like loose coupling and implementation neutrality. It describes the roles involved in SOA like providers, registries, and requestors. Core Web services standards like SOAP, WSDL, and UDDI are explained. Examples of synchronous and asynchronous messaging between services are also provided.
Semantic Web Process Lifecycle: Role of Semantics in Annotation, Discovery, C...Amit Sheth
“Semantic Web Process Lifecycle: Role of Semantics in Annotation, Discovery, Composition and Orchestration,” Keynote/Invited Talk, WWW 2003 Workshop on E-Services and the Semantic Web, Budapest, Hungary, May 20, 2003.
Here is the paper based on this talk:
Kaarthik Sivashanmugam, Kunal Verma,Amit Sheth, and John Miller, 'Adding Semantics to Web Services Standards,'International Conference on Web Services 2003 (ICWS'03), Las Vegas, NV, June 23-26, 2003.
http://knoesis.org/library/resource.php?id=00174
While going through in-depth on Service Oriented Architecture (SOA) and Enterprise Architecture (EA) as part of my Oracle SOA and TOGAF certification, I had questions as to how SOA fits in the EA, and how TOGAF for EA support adopting SOA.
Here is an attempt to address that...
I'm presenting the IBM CIO 2010 Outlook at IBM iForum, Zurich (26th November 2007). I can't take the credit for writing it; Dave Newbold did the hard work on this one.
This document provides an overview of service-oriented architecture (SOA). It defines SOA as a design paradigm that specifies the creation of automation logic in the form of discrete, autonomous services. The key benefits of SOA include enabling flexible, federated business processes and optimization through reuse of services across organizations. The document discusses SOA concepts like loose coupling, service contracts, and different service types. It also outlines the layers of a service architecture and some core SOA principles.
Service Oriented Government: 7th SOA For E-Govdavemayo
Dave Mayo presented on driving government transformation through service oriented architecture. He discussed how SOA can help address problems like inconsistencies, redundancy, and lack of interoperability in government. SOA provides agility to respond to constant change through reusable services. He outlined keys to implementing SOA, including establishing governance, funding mechanisms, and aligning IT with business goals. He argued for treating the entire federal government as an enterprise and developing shared services and processes across agencies rather than focusing on individual agencies.
This document summarizes the evolution of SOA strategies and practices at IBT, an investment bank. It discusses how IBT initially took small steps with basic web services before embarking on a broader implementation of SOA across the organization. A key case study described how an early content management service provided centralized, standard access to document repositories while reducing costs.
Similar to Dr Berre - Service Modelling and Representation Techniques (20)
This document discusses the role of European Technology Platforms (ETPs) in shaping the future of the Internet. It notes that ETPs like NESSI focus on software and services, NEM focuses on content, and others focus on communications, satellites, and more. The document states that ETPs will play a key role in the future Internet by delivering end-to-end experiences to users, providing underlying technologies and research results, and ensuring coherence and sustainability of research projects. ETPs are described as important communities and convergence points that can contribute to both Internet research and the adoption of new technologies.
The document discusses the role of European Technology Platforms (ETPs) in shaping the future internet. It notes that ETPs represent key industrial sectors like software/services, content, communications, and nanoelectronics. The ETPs have historically focused on their individual sectors but are now working together synergistically on converging topics like the future internet. The future internet serves as both a major application area for ETP research and an opportunity for ETPs to access users. ETPs are well-positioned to contribute to the future internet both individually through their separate work, and collectively by facilitating coherence across projects.
Massonet Philippe Panel - Security in the clouds: An Academic PerspectiveServiceWave 2010
The document discusses security challenges in cloud computing from an academic perspective. It notes that cloud providers are offering different security levels and obtaining certifications to improve trust. However, key challenges remain around loss of user governance, compliance, managing risks from jurisdiction changes, and lack of transparency. The responsibilities between users and providers are also still incompletely defined regarding accountability and control. The document suggests research directions could improve trust by giving users more control and verifying the provider's isolation of virtual infrastructure.
Usman Wajid: Service-based Application Development by Ordinary End Users and ...ServiceWave 2010
The document summarizes the findings of focus groups conducted with ordinary end users and IT professionals regarding their perceptions of service-based application development. The focus groups aimed to understand users' mental models of software services and gauge the likelihood of non-technical end users composing applications from available services. Key findings included higher experience levels with development among IT professionals; interest but also risks like security and technical difficulties perceived by both groups; and recommendations to promote, simplify, guide and secure service composition to encourage uptake by ordinary end users.
D. Meiländer, S. Gorlatch, C. Cappiello,V. Mazza, R. Kazhamiakin, and A. Buc...ServiceWave 2010
D. Meiländer, S. Gorlatch, C. Cappiello,V. Mazza, R. Kazhamiakin, and A. Bucchiarone: Using a Lifecycle Model for Adaptable Interactive Distributed Applications
Maryam Razavian: A Frame of Reference for SOA MigrationServiceWave 2010
This document summarizes research on approaches to migrating legacy systems to service-oriented architectures (SOAs). It conducted a systematic literature review that identified 8 families of SOA migration approaches. It also conducted interviews with industry practitioners that found companies primarily used "bowl-shaped" migration approaches focused on integration and reuse. The research provides a framework to categorize SOA migration approaches found in both academic literature and industry practice.
Security in the Clouds Panel Chair: Mike SurridgeServiceWave 2010
This document discusses security issues related to cloud computing. It outlines both the pros and cons of cloud-based information and communication technology. The pros include low upfront costs, low maintenance costs, and scalability. However, there are also legal, financial, societal and technical security risks to consider. These include issues around authentication, access control, accountability, and isolation of users. The document then describes the architecture of the Edutain@Grid project, which had four layers: the client layer for single sign-on, the business layer for trust and security federations, the management layer for access control and billing, and the real-time layer for secure application protocols. Finally, it lists the panelists who will discuss challenges
Martine Lapierre - Security in Cloud computing: sharing more than resourcesServiceWave 2010
Cloud computing provides opportunities but also implies a loss of control over data and infrastructure. When choosing a cloud offering, considerations include the provider's reputation for protecting confidentiality and their ability to prove no loss of control. Sensitive healthcare data processed in the cloud must satisfy strict regulatory requirements regarding data protection, access controls, and ensuring data does not leave its country of origin. Both customers and providers face legal and security challenges in ensuring compliance with privacy laws and protecting against threats in shared cloud environments.
Chen Wang, Pazat, Di Napoli, Giordano: A Chemical Based Middleware for Workf...ServiceWave 2010
1) The document describes a middleware architecture for instantiating and executing workflows at runtime based on quality of service constraints.
2) The middleware selects appropriate services for each workflow activity based on offers published to a registry and binds them to generate a concrete workflow execution plan.
3) Workflow execution is decentralized by distributing workflow instance information to participating services, which invoke each other to continue execution in a self-coordinated manner.
Andreas Wolke: TwoSpot. A Cloud Platform for Scaling out Web Applications dyn...ServiceWave 2010
TwoSpot is a cloud platform that allows for the automated horizontal scaling of web applications. It provides dynamic scaling of applications across multiple servers with a small resource footprint using existing software standards and multiple programming languages. The document discusses TwoSpot's architecture, how it starts and distributes application instances, and how it scales applications out or in based on load.
Scott Kirkpatrick (Hebrew University): OneLab: Federation and TestbedsServiceWave 2010
The document discusses federation of internet testbeds to enable testing across different geographic locations, technologies, and networks. It proposes extending federation support through middleware across control planes and experimental planes to facilitate resource discovery, monitoring, and data sharing. Several existing federated testbeds and measurement tools are described that have been used for topics like internet topology mapping, capacity measurements in Europe, and testing non-IP autonomous networks.
Jacques Magen (FIRESTATION): Testbeds for Service Deployment. FIRESTATION’s v...ServiceWave 2010
FIRESTATION aims to coordinate and support stakeholders involved in the Future Internet Research and Experimentation (FIRE) initiative. It establishes an Architecture Board to bring together representatives from FIRE projects to coordinate common actions and developments. This includes working towards a high-level federation model for FIRE facilities, developing a common FIRE portal, and addressing sustainability and business models. FIRESTATION also serves as an entry point for external relations and provides support for other coordination actions like FIREBALL and PARADISO2.
This document discusses testbeds for service deployments and summarizes a panel discussion on the topic. The panel motivation was that fast prototyping, testing, and experimentally driven research are key to speeding up and leveraging new application and service deployments. Testbeds can offer existing solutions and determine if they are usable and adequate. Some issues discussed were matching or mismatching between needs, requirements, and available solutions both open and commercial. Questions addressed why common open activities and solutions may need to be developed for service platforms, what concrete form an offering could take, and how academic and industrial objectives could be reconciled along with business models and sustainability.
Martine Lapierre - Security & Privacy trends for Urban & transport applications ServiceWave 2010
This document summarizes a presentation on security and privacy trends for urban transportation applications. It discusses future applications enabled by technologies like universal geo-location and mobile communications. An example application is described that provides multi-modal transportation routing and updates in real-time. Key security and privacy issues are identified, such as location privacy, customer data privacy and integrity, payment integrity, and ensuring safety. Content-driven security approaches are proposed that tag data with security and privacy metadata to control usage and ensure compliance. The document also discusses how the FI PPP project can help deliver generic security services to enable smart applications and generate trust.
Mário Campolargo - Services and clouds as cornerstones of the Digital AgendaServiceWave 2010
Mário Campolargo - Services and clouds as cornerstones of the Digital Agenda
Share
* Twitter
* Facebook
* email
Embed
Dr. Thierry Priol, INRIA, ServiceWave General Chair - Opening Welcome (edit)
Tags Description Dr. Thierry Priol, INRIA, ServiceWave General Chair - Opening Welcome Service Wave 2010 - Tuesday Dec 14th 2010
Mário Campolargo - Services and clouds as cornerstones of the Digital Agenda
Dr Berre - Service Modelling and Representation Techniques
1. Service Modelling and Representation Techniques - a holistic Enterprise Architecture perspective on using and influencing the emerging standards of VDM, USDL and SoaML Dr. Arne-Jørgen Berre SINTEF Networked Systems and Services Keynote at SMART’2010, Ghent, December 13 th , 2010
9. NEFFICS Community of highly innovative networked enterprises Networked innovation community services (Induct) Applications for highly innovative networked enterprises Virtual Factory Network (Vlastuin) Connected Retail Network (Telecom Italia) Enterprise SaaS Cloud business operations and orchestration platform (Cordys) Google Apps/Waves, Cloud computing & Web 2.0 platform Networked Enterprises on Internet of Services (COIN) and Things (ASPIRE) Networked enterprises MashApp applications and process support (Cordys) Networked process and service models (SINTEF) BPMN 2.0, SoaML, OSM, CMPM Networked business value analysis models (IC Focus) VDM BEI Networked innovation models, leadership and management processes (ICI) CEN/389
11. REMICS (2010-2012) SoaML VDM SoaML Recover Legacy Artifacts Source Architecture Migrate Target Architecture for Service Cloud platform Forward MDA through PIM 4 Cloud Service Cloud Implementa tion Model Driven Interoperability Validate , Control and Supervise Knowledge : REMICS KDM Business Process and Rules Components : SoaML Implementation : UML , U 2 TP Knowledge Discovery , Reverse Engineering Source code , binaries , documentation , users knowledge , configuration files , execution logs and traces . SOA and Cloud Computing Patterns applied , Legacy Components Replacement and Wrapping , Design by Service Composition Service mediation for adaptation SoaML with REMICS extensions for Service Clouds , Links to Business Models Model Transformation , Code Generation , Traceability RESERVOIR , Joyant , Amazon , Google , Microsoft Models @ Runtime for application management , Model Checking , Model - based Testing for validation
22. Business model innovation Timmers, 1998 “ Business model stands for the architecture for the product, service and information flows, including a description of the various business actors and their roles, the potential benefits for these actors and the sources of revenues……… the business model includes competition and stakeholders” Stewart and Zao, 2000 “ Business model is a statement of how a firm will make money and sustain its profit stream over time”. Weill and Vitale, 2001 “ A description of the roles and relationships among a firm’s consumers, customers, allies and suppliers that identifies major flows of product, information and money and the major benefits to participants”. Osterwalder et al. 2004 “ A blueprint of how a company does business. It is a conceptual tool that contains a set of elements and their relationships and allows expressing a company’s logic of earning money. It is a description of the value a company offers to one or several segments of customers and the architecture of the firm and its network of partners for creating, marketing and delivering this value and relationship capital, in order to generate profitable and sustainable revenue stream” Chesbrough 2006 “… is a useful framework to link ideas and technologies to economic outcomes”… “It also has value in understanding how companies of all sizes can convert technological potential [e.g. products, feasibility, and performance] into economic value [price and profits]”….. “Every company has a business model, whether that model is articulated or not”. Skarzynski and Gibson 2008 “… is a conceptual framework for identifying how a company creates, delivers, and extracts value. It typically includes a whole set of integrated components, all of which can be looked on as opportunities for innovation and competitive advantage”.
25. Value Delivery Modeling Language (OMG RFP) (2009 – 2011 – 2012) Ongoing work on a Value Delivery Metamodel RFP to OMG – with initial submission in May 2011 VDM - Value Delivery Metamodel
26. Business partner relationships Merchant Customer Internet Publisher Participation Participation Participation Value Prop’n Value Prop’n Value Prop’n Value Prop’n Value Prop’n Value Prop’n Each business entity must realize a net gain Diagram for illustration, not a proposed notation Value Exchange Provide Content Purchase Goods Clicks Purchase Ad Publish Ad Sell Goods
30. People naturally network as they work. So why not model the work itself as a network? December 15, 2010 Value Network Analysis models value creation with a powerful human network approach to managing any business activity.
39. Examples of Services Related to a Service ~ Product ~ Business Process as a Unique Asset Service ~ Product ~ Business Process Analyse Design Simulate Sell Buy Rent Lease Finance Execute Monitor Implement
40.
41.
42. USDL – The Unified Service Description Language (USDL) See: http://www.internet-of-services.com/ See also: http://www.w3.org/2005/Incubator/usdl/wiki/Main_Page
55. SOA in Model Driven Architecture (MDA) Business Concerns Goals Policy Customers Costs Agility Technology Specification JMS, JEE, Web Services WSDL, BPEL, XML Schema Logical System Model Technology Services (t-SOA) Software Components Interfaces, Messages & Data Business Model Enterprise Services (e-SOA) Roles, Collaborations & Interactions Process & Information Refinement & Automation Line-Of-Sight Computation Independent Model Platform Independent Model Platform Specific Model MDA Terms
65. Services architecture (Participant-level) Order Conformation Shipped Ship Req Shipped Delivered Participant-level services architecture for the Manufacturer OrderHandler Invoicing Productions
66. Choreography: Place order (Service contract behaviour) (Service interface behaviour) Service choreography can be specified using any UML behaviour, e.g, interaction or activity Service choreography can be specified using any UML behaviour, e.g, interaction or activity
74. Mappings SoaML Term BPMN Mapping ServicesArchitecture (a UML Collaboration) or a specification Participant Overview Choreography Participant Participant representing PartnerEntity (within definitional collaboration Service Port One end of a communication between participants in a communication diagram: Interface of the above participant Request Port The other end of the communication, the one sending the first message ServiceInterface (defining the type of a Service or Request Port) Interface, but doesn’t support service protocols. Alternatively, a communication in a communication diagram, including the corresponding messages in a collaboration diagram, and the choreography of those messages in a choreography diagram Interface (realized or used by a ServiceInterface) Interface, but not clear how this relates to a communication Operation or Reception (of an Interface) Operation of an Interface or Message, but not clear how this relates to an operation of an interface Parameter (of an Operation) Message inputs and outputs for an Operation
79. Service Modelling and Representation Techniques - a holistic Enterprise Architecture perspective on using and influencing the emerging standards of VDM, USDL and SoaML Dr. Arne-Jørgen Berre SINTEF Networked Systems and Services Keynote at SMART’2010, Ghent, December 13 th , 2010
Editor's Notes
ICT Proposer's Day 01.02.2007
INF5120 Modellbasert Systemutvikling 27.01.2005
The Value Delivery Modeling Language is under development in response to the OMG Value Delivery Metamodel (VDM) RFP issued March 27, 2009. This PPT provides an overview of the current concepts and capabilities of the specification.
This diagram illustrates the role of value propositions in exchanges between business entities, typically independent companies. The relationship between these business entities is defined as a value exchange. Each participant gives and receives a value proposition with each of the other participants with which they interact. The illustration incorporates an Internet business relationship between three participants. An Internet Publisher provides an information service of interest to customers. An advertiser pays the publisher to include advertisements for its products along with the information sought by the customer. The customer then clicks on ads of interest and potentially purchases goods from the advertiser. For this business relationship to survive, each of the participants must experience a net gain. In this case, each participant provides two value propositions and receives two value propositions. There may not be a net gain between any two participants, alone, but each has a net gain for the overall exchange.
These are the primary dimensions represented by a VDML model. The activity network defines the roles of activities. Activities are linked by the transfer of deliverables, so the nature of each deliverable and its producers and consumers are of interest. Organization relationships define how capabilities are managed and coordinated. The contributions to value propositions define the sources of value and their impact on value propositions. Exchange networks represent the relationships between business entities. Performance monitoring provides visibility of the composite performance and the effects of changes in the model.
These are business design and modeling techniques that are influencing the development of VDML. We hope to integrate the best aspects of these techniques.
A BPMN Collaboration diagram describes the messages exchanged between the participants. The Collaboration diagram provides an ungrouped view of the messages exchanged between the participants. A Communication diagram can be used to show how the messages are grouped. The BPMN 2.0 FTF is in the process of merging the Collaboration and Conversation diagrams.
A BPMN Conversation shows the grouping of messages between collaborating participants and provides a means to correlate interactions between specific instances of these participants at runtime. These groupings correspond to the messages shown in the collaboration diagram. The choreography of these groups of messages can be shown using a Choreography diagram The grouping of messages, plus the corresponding choreography corresponds to the ServiceInterface in SoaML. The connections between the communication and participants in a communication diagram corresponds to the service and request ports in SoaML.
This is a new type of drill down into a Conversation. It not only shows the Message Flow, it shows a Choreography of the Conversation. We will have to consider if we need BPMN 2.0 FTF issues to do this, since there could be a Choreography for each Conversation. The convergence of Collaboration and Conversation will help, but only one Choreography is allowed in a Collaboration. But that Choreography could have multiple Start Events. What is needed is a way to visually and semantically connect the messages, their grouping and their sequencing captured in a BPMN collaboration, communication and choreography. One possible approach is to support drill-down into a communication to see the messages and their choreography. This could be done through naming conventions where the names of the communication and collaboration are the same, as well as the start activity in the choreography.
Participant is a definition in SoaML. A part (or typed element) is a reference to some instance of a participant, the actual instance would be established by an assignment statement that usually happens at runtime and is not usually modeled. Again the normalization of message-oriented vs procedure-call-oriented is not yet covered by BPMN. These are currently completely separate concepts in BPMN with message-oriented interactions being covered by collaboration, communication and choreography, and specific send and receive message activities in an orchestration. Procedure-call-oriented is covered by interface and service activity in an orchestration. BPMN’s modeling of services is limited to simple interfaces as in WSDL. Service protocols and complex service interactions would have to be modeled using the message-oriented approach.
Rollen erklären, mit Beispiel (Entwickler, solution Manager) Vokabeln klären: modeldriven, basemodel…