Service contracts between digital providers and consumers should be: (i) understood and verified by the business stakeholders, (ii) mechanically checked for consistency and (iii) automatically mapped to system implementations. This presentation sketches guidelines and templates for expressing service contract clauses as business rules, i.e. logical formulations in constrained natural language conforming to the OMG Semantics of Business Vocabulary and Business Rules (SBVR) specification.
When supported by the SBVR abstract notation, natural language business rules can be mechanically checked for consistency, and eventually processed for automated generation of technical model elements, machine-readable components, executable code and tests. The service contract clauses are established through a method that is inspired by the Design by contract™ approach: the signature of the service operation is expressed by means of a set of business vocabulary entries and its pre/post-conditions are stated as operative business rules. The method and the corresponding rule templates are included in a methodological framework for model driven engineering of services architectures (simpleSOA™), in which the service contract, as a bundle of rights and duties for service providers and consumers, is represented by a layered collection of formal models that work as a body of requirements for implementations. In this model-driven framework, the service contract vocabulary and rule-book constitute the service Computation Independent Model (CIM). We introduce the method guidelines and templates through an example and discuss the assumptions on the resulting conceptual model as well as some recommendations on the contract building enterprise.
simpleSOAD 2.0 Architecture and GovernanceLibero Maesano
This presentation introduces the simpleSOAD® methodological framework for design and implementation of services and services architectures, founded upon a contract-based, model-driven (MDA) approach and the OMG standards. Contract-based service orientation is presented first. The service contract is a first-class object, is independent from the systems that endorse it, and acts as a functional and behavioral specification for these systems. Furthermore, the principles of application of the model-driven engineering approach to service design are given. A service contract is a layered set of models: BMM (motivational), BM (conceptual), PIM (logical) and Interoperability PSM (physical). They are all based upon largely accepted OMG standards. The service contract is designed top-down with the help of methods and tools of model mapping and transformation. The Implementation PSM of a system that intends to provide the service can be partially generated by the contract model. Future work will concern phases and activities of the SOA life cycle till now poorly covered, such as Validation &Verification, Test and Governance.
IJERA (International journal of Engineering Research and Applications) is International online, ... peer reviewed journal. For more detail or submit your article, please visit www.ijera.com
The document discusses HL7's Service Aware Enterprise Architecture Framework (SAEAF). It provides an overview of SAEAF, explaining that it uses a multi-dimensional specification pattern to create standards that enhance healthcare interoperability. SAEAF defines specifications across various viewpoints, including enterprise, information, computational, engineering, and conformance levels. The goal of SAEAF and HL7 specifications is to define the information, functions, terminology and technology bindings needed for implemented systems to work interoperably.
The document outlines the key points of employment law, including that employment law comes from various sources such as statutes, common law, EU law, and codes of practice. It distinguishes between civil and criminal law as well as collective and individual law. The document also discusses how employment law is enforced through the court system and regulatory bodies, and the penalties for breaching contracts or statutory rights. It examines the different forms employment law takes and how the law has historically played a minor role but now impacts the employment relationship at many stages.
The document is a presentation about updates to the SAM II system from Pat Dotter, the Southwestern Area Manager at PTAC MN. It outlines new features of SAM II including updated pages and a new "Processing" message. It also reviews how to update an entity profile, manage role requests, and adjust account settings within the new version of SAM II. Contact information is provided for Pat Dotter and PTAC MN if users need assistance.
There have been slew of changes to employment-related requirements for government contractors. These changes mean more compliance concerns for you, the potential for Department of Labor audits, and the need to update your employment policies, employee notices and job postings, contract language, and more.
This presentation breaks down the major changes and will help you understand what you need to do to comply with the new rules that rolled out in 2015 and 2016. We cover the Service Contract Act (SCA), Fair Pay and Safe Workplaces Executive Order, changes to overtime rules, employee vs. independent contractor issues, and more.
You'll learn:
- The key areas of your employee handbook that need to be updated because of the new rules
- What needs to be updated in your non-compete and confidentiality agreements
- How to conduct a self-audit to make sure your employment practices are clean and ready for a potential DOL visit
- Actions that have been taken by the DOL against government contractors
- How to reduce the risk of future employment law violations
This document outlines the key records that contractors must maintain to demonstrate compliance with the Service Contract Act. It lists basic records like employee names and addresses that must be kept for three years after a contract's completion. Key records include accurate employee classifications and wage rates, as well as documentation of fringe benefit plans and hourly work records. Contractors must also be prepared to provide these compliance records upon request. Failure to provide up-to-date records may indicate potential non-compliance issues.
The McNamara-O’Hara Service Contract Act (SCA) applies to every contract entered into by the United States or the District of Columbia, the principal purpose of which is to furnish services in the United States through the use of service employees. Contractors performing on such Federal service contracts in excess of $2,500 must observe minimum wage and safety and health standards, and maintain certain records. Service employees on covered contracts in excess of $2,500 must be paid not less than the monetary wages and fringe benefits contained in wage determinations issued by the U.S. Department of Labor (DOL) for the contract work.
simpleSOAD 2.0 Architecture and GovernanceLibero Maesano
This presentation introduces the simpleSOAD® methodological framework for design and implementation of services and services architectures, founded upon a contract-based, model-driven (MDA) approach and the OMG standards. Contract-based service orientation is presented first. The service contract is a first-class object, is independent from the systems that endorse it, and acts as a functional and behavioral specification for these systems. Furthermore, the principles of application of the model-driven engineering approach to service design are given. A service contract is a layered set of models: BMM (motivational), BM (conceptual), PIM (logical) and Interoperability PSM (physical). They are all based upon largely accepted OMG standards. The service contract is designed top-down with the help of methods and tools of model mapping and transformation. The Implementation PSM of a system that intends to provide the service can be partially generated by the contract model. Future work will concern phases and activities of the SOA life cycle till now poorly covered, such as Validation &Verification, Test and Governance.
IJERA (International journal of Engineering Research and Applications) is International online, ... peer reviewed journal. For more detail or submit your article, please visit www.ijera.com
The document discusses HL7's Service Aware Enterprise Architecture Framework (SAEAF). It provides an overview of SAEAF, explaining that it uses a multi-dimensional specification pattern to create standards that enhance healthcare interoperability. SAEAF defines specifications across various viewpoints, including enterprise, information, computational, engineering, and conformance levels. The goal of SAEAF and HL7 specifications is to define the information, functions, terminology and technology bindings needed for implemented systems to work interoperably.
The document outlines the key points of employment law, including that employment law comes from various sources such as statutes, common law, EU law, and codes of practice. It distinguishes between civil and criminal law as well as collective and individual law. The document also discusses how employment law is enforced through the court system and regulatory bodies, and the penalties for breaching contracts or statutory rights. It examines the different forms employment law takes and how the law has historically played a minor role but now impacts the employment relationship at many stages.
The document is a presentation about updates to the SAM II system from Pat Dotter, the Southwestern Area Manager at PTAC MN. It outlines new features of SAM II including updated pages and a new "Processing" message. It also reviews how to update an entity profile, manage role requests, and adjust account settings within the new version of SAM II. Contact information is provided for Pat Dotter and PTAC MN if users need assistance.
There have been slew of changes to employment-related requirements for government contractors. These changes mean more compliance concerns for you, the potential for Department of Labor audits, and the need to update your employment policies, employee notices and job postings, contract language, and more.
This presentation breaks down the major changes and will help you understand what you need to do to comply with the new rules that rolled out in 2015 and 2016. We cover the Service Contract Act (SCA), Fair Pay and Safe Workplaces Executive Order, changes to overtime rules, employee vs. independent contractor issues, and more.
You'll learn:
- The key areas of your employee handbook that need to be updated because of the new rules
- What needs to be updated in your non-compete and confidentiality agreements
- How to conduct a self-audit to make sure your employment practices are clean and ready for a potential DOL visit
- Actions that have been taken by the DOL against government contractors
- How to reduce the risk of future employment law violations
This document outlines the key records that contractors must maintain to demonstrate compliance with the Service Contract Act. It lists basic records like employee names and addresses that must be kept for three years after a contract's completion. Key records include accurate employee classifications and wage rates, as well as documentation of fringe benefit plans and hourly work records. Contractors must also be prepared to provide these compliance records upon request. Failure to provide up-to-date records may indicate potential non-compliance issues.
The McNamara-O’Hara Service Contract Act (SCA) applies to every contract entered into by the United States or the District of Columbia, the principal purpose of which is to furnish services in the United States through the use of service employees. Contractors performing on such Federal service contracts in excess of $2,500 must observe minimum wage and safety and health standards, and maintain certain records. Service employees on covered contracts in excess of $2,500 must be paid not less than the monetary wages and fringe benefits contained in wage determinations issued by the U.S. Department of Labor (DOL) for the contract work.
The document discusses Malaysia's legal system and provides 3 topics for discussion: 1) It compares how English law was introduced differently in Borneo States, Malay States, and Straits Settlements. 2) It asks about the law making process in Parliament, specifically the voting requirement at the second reading in the Dewan Rakyat, Royal Assent, and Publication. 3) It asks to explain the differences between written law and unwritten law.
U.S. Department of Labor - Wage & Hour Divisionjpeabody
This document provides guidance from the U.S. Department of Labor Wage and Hour Division on complying with prevailing wage requirements on federal contracts. It addresses topics like laborers and mechanics coverage, fringe benefits, computing overtime pay, and investigation procedures. The guidance explains how to properly classify workers, pay prevailing wages and fringe benefits, handle multi-rate employees, and calculate back wages owed when violations are found.
This document provides an agenda and overview for a Small Business Liaison Officer training. It discusses the importance and goals of small business programs, defines key small business terms, outlines the roles and responsibilities of SBLOs, and reviews elements of subcontracting plans, agency reviews, and ISR/SSR reporting requirements. The training aims to educate SBLOs on effectively managing their organizations' small business programs and subcontracting compliance.
Contract of Service & Contract for ServiceHanif Zulkifli
This document discusses and compares contracts of service and contracts for service under Malaysian employment law.
A contract of service is an agreement, whether written or verbal, where one person agrees to employ another as an employee. It creates an employer-employee relationship. An apprenticeship is also considered a contract of service. The employer cannot unilaterally change terms and conditions of employment without the employee's agreement. Any terms less favorable than what is stipulated in employment law are invalid.
A contract for service involves supplying labor as an independent contractor rather than an employee. There is no employer-employee relationship. The individual works on a self-employed or freelance basis for a fee rather than as an employee.
The document provides an overview of the Malaysian legal system. It discusses that Malaysia has a dual legal system consisting of civil and sharia law. It also outlines the various sources of law in Malaysia including legislation passed by parliament and state assemblies, customary law, and precedents set by higher courts. The document describes the hierarchy of courts in Malaysia, starting with the Federal Court at the top, followed by the Court of Appeal, High Courts, Session Courts, Magistrate Courts, and Juvenile Courts which handle cases involving minors.
The document provides an overview of the analytical framework of contract law. It discusses the key elements in the formation of contracts, including offers, acceptance, consideration, and intention to create legal relations. It also covers the requirements of certainty, completeness, and form in contracts. The document is divided into five parts that will examine how contracts are formed, the content of contracts, who can enforce contracts, how contracts can be destroyed, and how contracts come to an end or are discharged.
This document discusses best practices for migrating to a service-oriented architecture (SOA). It recommends embracing heterogeneity and complexity by abstracting across different software systems using standards like XML and web services. A successful SOA migration requires changing organizational structures and skills to focus on reusable services, incremental changes, and architectural best practices. Service contracts that separate interface from implementation are also key to enabling reuse and flexibility.
The document discusses Service Oriented Architecture (SOA). It defines SOA as an architecture that relies on loosely coupled services to support business processes and users. The key benefits of SOA include reusability, linking of resources, and ability to respond quickly to changing market conditions. The document outlines various SOA principles, elements, objectives and technologies used for implementation including web services. It also discusses challenges in adopting SOA such as managing service metadata and security.
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.
This document provides an overview of service-based architectures and compares microservices architecture and service-oriented architecture (SOA). It discusses key topics for service-based architectures like service contracts, availability, security, and transactions. The document then compares characteristics of services and architectures between microservices and SOA, such as service granularity, ownership, orchestration, and capabilities. The goal is to understand the differences between microservices and SOA and which may be better suited for different situations.
Service Oriented & Model Driven ArchitecturesPankaj Saharan
The document discusses a seminar on combining Service-Oriented Architectures (SOA) and Model Driven Architectures (MDA). It first provides an overview of SOA and MDA individually, including their goals and characteristics. It then analyzes the similarities and differences between the two approaches when combining them. Some benefits are improved productivity and lower costs, while challenges include defining models and transformations between levels of abstraction. Overall, the document concludes that combining SOA with MDA's model-driven approach can provide benefits like business agility if key issues like semantics and metadata modeling are adequately addressed.
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...
The document discusses modeling services for a minor enterprise application called Contract first modeling Services using UML. It provides an overview of the contract-first modeling approach, including modeling business processes as use cases and technical services, and then generating interfaces and code from these models. The key benefits of the contract-first approach are that the contract remains stable over time and allows for loose coupling between interfaces and implementations.
This chapter discusses situating SOA in the overall architecture context. It examines different models for visualizing SOA-based landscapes, including logical, mixed, and technical models. The chapter also addresses integrating SOA with frontends and backends, such as dividing responsibilities, multi-channel scenarios, and future task management.
IJERA (International journal of Engineering Research and Applications) is International online, ... peer reviewed journal. For more detail or submit your article, please visit www.ijera.com
This chapter discusses services in the context of service-oriented architecture (SOA). It defines a service as a self-contained business function that accepts requests and returns responses through a standard interface. A service should represent discrete units of work from a business perspective rather than being technically driven. The interface of a service, including message signatures and semantics, is considered its contract. Additional common attributes of services discussed include being stateless, reusable, and having quality of service guarantees.
Why Coordination And Transactions Are Key To Building An Operational SoaDavid Linthicum
The document discusses the importance of transactions and coordination in building a service-oriented architecture (SOA). Transactions have ACID properties (atomicity, consistency, isolation, durability). There are standards like WS-Coordination and WS-AtomicTransaction that help coordinate distributed services. Coordination is needed to make distributed services function as a single service and reach consistent agreement on outcomes.
Microsoft BizTalk server seen by the programmer’s eyesSandro Pereira
The document discusses the benefits that the Microsoft BizTalk Server platform offers to programmers and developers. It provides details on job opportunities working with BizTalk, features that simplify programming tasks like the orchestration designer and rule engine, and how BizTalk handles transactions, exceptions, and data persistence to reduce programming work. Overall, BizTalk is presented as a tool that streamlines integration development by providing common features out of the box rather than requiring programmers to reimplement them for each project.
The document discusses service-oriented computing concepts including service-oriented architecture (SOA), service-oriented analysis and design, SOA characteristics, and SOA certifications. It provides an overview of key SOA concepts such as loose coupling, reusability, and autonomy. It also summarizes SOA goals like increased agility, interoperability, and return on investment. Sample exam questions are included to help understand SOA fundamentals.
Technology, Software, Architecture for P&C InsuranceGregg Barrett
This document summarizes Gregg Barrett's recommendations for technology platforms and standards/frameworks for Q1 2012. It recommends evaluating the Microsoft platform using SQL Server, BizTalk Server, and SQL Server Integration Services for ETL capabilities. If Microsoft is not suitable, it recommends considering Adeptia, Informatica, Software AG, TIBCO, and Progress Software. It outlines several relevant standards and frameworks in areas like insurance, data modeling, business processes, financial reporting, and more. It provides links and descriptions for some of the key standards.
TOWARDS AUTOMATION OF SOA-BASED BUSINESS PROCESSESIJCSEA Journal
This document presents the BPA-SOA methodology for automating SOA-based business processes. The methodology involves modeling the business process using a standard like BPMN, then defining how activities will be executed (e.g. via web services). It also includes detailing the business process data by associating data types and variables, and resolving any predicates. The goal is to take the high-level business process specification and transform it into an executable process that can be deployed and run on an orchestration engine.
Graph-Based Algorithm for a User-Aware SaaS Approach: Computing Optimal Distr...IJERA Editor
As a tool to exploit economies of scale, Software as a Service cloud models promote Multi-Tenancy which is the notion of sharing instances among a large group of tenants. However, Multi-Tenancy only satisfies requirements that are common to all tenants as well as the fact that tenants themselves hesitate about sharing. In a try to solve this problem, the present paper propose a User-Aware approach for Software as a Service models using Rich-Variant Components. The main contribution of this approach is a framework summarized in a graphbased algorithm enabling deduction of an optimal distribution of instances on application's tenants. To illustrate and evaluate the framework, the approach is applied on a Software as a Service Application for private school management
The document discusses Malaysia's legal system and provides 3 topics for discussion: 1) It compares how English law was introduced differently in Borneo States, Malay States, and Straits Settlements. 2) It asks about the law making process in Parliament, specifically the voting requirement at the second reading in the Dewan Rakyat, Royal Assent, and Publication. 3) It asks to explain the differences between written law and unwritten law.
U.S. Department of Labor - Wage & Hour Divisionjpeabody
This document provides guidance from the U.S. Department of Labor Wage and Hour Division on complying with prevailing wage requirements on federal contracts. It addresses topics like laborers and mechanics coverage, fringe benefits, computing overtime pay, and investigation procedures. The guidance explains how to properly classify workers, pay prevailing wages and fringe benefits, handle multi-rate employees, and calculate back wages owed when violations are found.
This document provides an agenda and overview for a Small Business Liaison Officer training. It discusses the importance and goals of small business programs, defines key small business terms, outlines the roles and responsibilities of SBLOs, and reviews elements of subcontracting plans, agency reviews, and ISR/SSR reporting requirements. The training aims to educate SBLOs on effectively managing their organizations' small business programs and subcontracting compliance.
Contract of Service & Contract for ServiceHanif Zulkifli
This document discusses and compares contracts of service and contracts for service under Malaysian employment law.
A contract of service is an agreement, whether written or verbal, where one person agrees to employ another as an employee. It creates an employer-employee relationship. An apprenticeship is also considered a contract of service. The employer cannot unilaterally change terms and conditions of employment without the employee's agreement. Any terms less favorable than what is stipulated in employment law are invalid.
A contract for service involves supplying labor as an independent contractor rather than an employee. There is no employer-employee relationship. The individual works on a self-employed or freelance basis for a fee rather than as an employee.
The document provides an overview of the Malaysian legal system. It discusses that Malaysia has a dual legal system consisting of civil and sharia law. It also outlines the various sources of law in Malaysia including legislation passed by parliament and state assemblies, customary law, and precedents set by higher courts. The document describes the hierarchy of courts in Malaysia, starting with the Federal Court at the top, followed by the Court of Appeal, High Courts, Session Courts, Magistrate Courts, and Juvenile Courts which handle cases involving minors.
The document provides an overview of the analytical framework of contract law. It discusses the key elements in the formation of contracts, including offers, acceptance, consideration, and intention to create legal relations. It also covers the requirements of certainty, completeness, and form in contracts. The document is divided into five parts that will examine how contracts are formed, the content of contracts, who can enforce contracts, how contracts can be destroyed, and how contracts come to an end or are discharged.
This document discusses best practices for migrating to a service-oriented architecture (SOA). It recommends embracing heterogeneity and complexity by abstracting across different software systems using standards like XML and web services. A successful SOA migration requires changing organizational structures and skills to focus on reusable services, incremental changes, and architectural best practices. Service contracts that separate interface from implementation are also key to enabling reuse and flexibility.
The document discusses Service Oriented Architecture (SOA). It defines SOA as an architecture that relies on loosely coupled services to support business processes and users. The key benefits of SOA include reusability, linking of resources, and ability to respond quickly to changing market conditions. The document outlines various SOA principles, elements, objectives and technologies used for implementation including web services. It also discusses challenges in adopting SOA such as managing service metadata and security.
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.
This document provides an overview of service-based architectures and compares microservices architecture and service-oriented architecture (SOA). It discusses key topics for service-based architectures like service contracts, availability, security, and transactions. The document then compares characteristics of services and architectures between microservices and SOA, such as service granularity, ownership, orchestration, and capabilities. The goal is to understand the differences between microservices and SOA and which may be better suited for different situations.
Service Oriented & Model Driven ArchitecturesPankaj Saharan
The document discusses a seminar on combining Service-Oriented Architectures (SOA) and Model Driven Architectures (MDA). It first provides an overview of SOA and MDA individually, including their goals and characteristics. It then analyzes the similarities and differences between the two approaches when combining them. Some benefits are improved productivity and lower costs, while challenges include defining models and transformations between levels of abstraction. Overall, the document concludes that combining SOA with MDA's model-driven approach can provide benefits like business agility if key issues like semantics and metadata modeling are adequately addressed.
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...
The document discusses modeling services for a minor enterprise application called Contract first modeling Services using UML. It provides an overview of the contract-first modeling approach, including modeling business processes as use cases and technical services, and then generating interfaces and code from these models. The key benefits of the contract-first approach are that the contract remains stable over time and allows for loose coupling between interfaces and implementations.
This chapter discusses situating SOA in the overall architecture context. It examines different models for visualizing SOA-based landscapes, including logical, mixed, and technical models. The chapter also addresses integrating SOA with frontends and backends, such as dividing responsibilities, multi-channel scenarios, and future task management.
IJERA (International journal of Engineering Research and Applications) is International online, ... peer reviewed journal. For more detail or submit your article, please visit www.ijera.com
This chapter discusses services in the context of service-oriented architecture (SOA). It defines a service as a self-contained business function that accepts requests and returns responses through a standard interface. A service should represent discrete units of work from a business perspective rather than being technically driven. The interface of a service, including message signatures and semantics, is considered its contract. Additional common attributes of services discussed include being stateless, reusable, and having quality of service guarantees.
Why Coordination And Transactions Are Key To Building An Operational SoaDavid Linthicum
The document discusses the importance of transactions and coordination in building a service-oriented architecture (SOA). Transactions have ACID properties (atomicity, consistency, isolation, durability). There are standards like WS-Coordination and WS-AtomicTransaction that help coordinate distributed services. Coordination is needed to make distributed services function as a single service and reach consistent agreement on outcomes.
Microsoft BizTalk server seen by the programmer’s eyesSandro Pereira
The document discusses the benefits that the Microsoft BizTalk Server platform offers to programmers and developers. It provides details on job opportunities working with BizTalk, features that simplify programming tasks like the orchestration designer and rule engine, and how BizTalk handles transactions, exceptions, and data persistence to reduce programming work. Overall, BizTalk is presented as a tool that streamlines integration development by providing common features out of the box rather than requiring programmers to reimplement them for each project.
The document discusses service-oriented computing concepts including service-oriented architecture (SOA), service-oriented analysis and design, SOA characteristics, and SOA certifications. It provides an overview of key SOA concepts such as loose coupling, reusability, and autonomy. It also summarizes SOA goals like increased agility, interoperability, and return on investment. Sample exam questions are included to help understand SOA fundamentals.
Technology, Software, Architecture for P&C InsuranceGregg Barrett
This document summarizes Gregg Barrett's recommendations for technology platforms and standards/frameworks for Q1 2012. It recommends evaluating the Microsoft platform using SQL Server, BizTalk Server, and SQL Server Integration Services for ETL capabilities. If Microsoft is not suitable, it recommends considering Adeptia, Informatica, Software AG, TIBCO, and Progress Software. It outlines several relevant standards and frameworks in areas like insurance, data modeling, business processes, financial reporting, and more. It provides links and descriptions for some of the key standards.
TOWARDS AUTOMATION OF SOA-BASED BUSINESS PROCESSESIJCSEA Journal
This document presents the BPA-SOA methodology for automating SOA-based business processes. The methodology involves modeling the business process using a standard like BPMN, then defining how activities will be executed (e.g. via web services). It also includes detailing the business process data by associating data types and variables, and resolving any predicates. The goal is to take the high-level business process specification and transform it into an executable process that can be deployed and run on an orchestration engine.
Graph-Based Algorithm for a User-Aware SaaS Approach: Computing Optimal Distr...IJERA Editor
As a tool to exploit economies of scale, Software as a Service cloud models promote Multi-Tenancy which is the notion of sharing instances among a large group of tenants. However, Multi-Tenancy only satisfies requirements that are common to all tenants as well as the fact that tenants themselves hesitate about sharing. In a try to solve this problem, the present paper propose a User-Aware approach for Software as a Service models using Rich-Variant Components. The main contribution of this approach is a framework summarized in a graphbased algorithm enabling deduction of an optimal distribution of instances on application's tenants. To illustrate and evaluate the framework, the approach is applied on a Software as a Service Application for private school management
WEB PORTAL INTEGRATION ARCHITECTURE APPROACHESijwscjournal
This document proposes a service-oriented architecture approach for web portal integration. It begins by describing a platform-independent integration architecture based on standards like UML, MOF, and XMI. This allows modeling integration independently of specific technologies. The document then discusses using WSMO as a specific implementation, describing how the platform-independent layers map to WSMO. It also discusses integrating agents and semantic web services using model transformations. Finally, it proposes additional "X-as-a-Service" layers that could be part of the architecture, like structure-as-a-service and process-as-a-service.
WEB PORTAL INTEGRATION ARCHITECTURE APPROACHESijwscjournal
Enterprise Modelling with Web portal integration architecture requires investment of advanced architectural thinking into definition of services before any development of services or service consumers can begin. Service Oriented Architecture (SOA) is gradually replacing monolithic architecture as the premier design principle for new business applications with its inherently systematic nature and capability. Earlier efforts of notable styles of SOA such as CORBA and XATMI have failed to be adopted as main stream projects because of demanding design process requirement with sense-making activities and even have been residing with the modern SOA or Web services middleware. In this paper it is aimed to incorporate sensemaking design activities with the proposed semantic web service based architecture. This paper tries to tackle the above problem by proposing a service-oriented architecture for web data and service integration. A gen-Spec architectural pattern has been suggested and adopted in order to tackle the problem.
Firstly, it proposes a service-oriented platform independent architecture and Secondly, it presents a specific deployment of such architecture for data and service integration on the web using semantic web services implemented with the WSMO (Web Services Modeling Ontology).
This document discusses service-oriented architecture (SOA) and related concepts. It defines SOA as a software design pattern based on discrete software modules called services that collectively provide application functionality. SOA allows services to easily cooperate over a network through standardized communication. The document outlines the evolution of SOA from earlier paradigms like object-orientation, different types of SOA, and key SOA concepts like loose coupling and interoperability. It also discusses merits and limitations of the SOA approach.
Similar to Service contract clauses as business rules (20)
This document discusses challenges in automating functional testing of complex distributed service architectures. It presents the MIDAS approach, which uses models of the service architecture under test to automatically generate and schedule test cases. Key aspects of the MIDAS approach include generating test suites from interaction path models, using model checking to generate test inputs and execute path models to generate oracles, and using probabilistic reasoning to intelligently prioritize and schedule test cases and generate new tests reactively based on past results. The approach has been prototyped and deployed on AWS, and is being evaluated on healthcare service architectures. Future work may include expanding the approach to additional domains and improving test reports, scheduling strategies, and integrated modeling tools.
This document discusses testing services in a service-oriented architecture (SOA) using the Model-Driven Internet Architecture for Services (MIDAS) platform. It describes how individual services, service architectures, and integrated service compositions can be tested through MIDAS' automated generation of test cases and execution across infrastructure, platform, and software as a service layers. The authors provide examples of modeling services and interactions using MIDAS to automate functional and security testing of a healthcare SOA implementation.
The document discusses extreme automation of testing distributed systems, services, and APIs. It proposes:
1) Automating all testing activities, including automated test input and oracle generation, intelligent test prioritization and scheduling, execution, arbitration and reporting.
2) Using models of the distributed system under test, including service models, architecture topology, and protocol state machines to generate test cases.
3) Intelligently scheduling and reactively planning tests by choosing the next test case to run based on past test verdicts and generating new test cases to diminish ignorance of system elements.
4) Providing these testing technologies and functional testing workflow as a cloud-native, on-demand testing as a service platform.
Steps towards an industrial implementation of HSSP standardsLibero Maesano
This document summarizes a project called HealthSOAF that aims to implement a framework of plug-and-play service components based on international health standards like HSSP. The project has a 3 year duration, €6.7M total cost with €4.3M in funding. It involves companies and universities working to design standard healthcare services, a testing framework, and a pilot implementation integrating clinical management of patients. The goals are to improve healthcare interoperability and efficiency through standardized service-oriented architecture approaches.
1) SOA Testing As A Service discusses the need for testing service-oriented architectures to ensure compliance with service contracts.
2) The MIDAS solution provides automated, elastic, and intelligent model-based and usage-based testing of service architectures as a pay-per-use service.
3) MIDAS aims to create a framework for automated SOA testing through generating test suites, executing tests, and dynamically scheduling tests based on probabilistic reasoning.
Steps towards model-based, inference-driven SOA TestingLibero Maesano
This presentation reports the progress of a project whose goal is to develop a model-driven, contract-based SOA testing environment in which grey-box testing strategies for large services architectures are driven by stochastic inference. In order to achieve this goal, a Bayesian network is built directly by mapping and model transformation from the services architecture design and test models. Because services architectures are complex and large systems, the generated BN and its associated probability tables may also be very large and the inference process may be excessively slow. Nevertheless, the structures of the services architecture design and test models let techniques of compilation improve the inference task, enabling the use of BN inference as a sustainable tool for driving failure discovering and troubleshooting strategies in large scale services architectures.
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.
Have you ever been confused by the myriad of choices offered by AWS for hosting a website or an API?
Lambda, Elastic Beanstalk, Lightsail, Amplify, S3 (and more!) can each host websites + APIs. But which one should we choose?
Which one is cheapest? Which one is fastest? Which one will scale to meet our needs?
Join me in this session as we dive into each AWS hosting service to determine which one is best for your scenario and explain why!
Session 1 - Intro to Robotic Process Automation.pdfUiPathCommunity
👉 Check out our full 'Africa Series - Automation Student Developers (EN)' page to register for the full program:
https://bit.ly/Automation_Student_Kickstart
In this session, we shall introduce you to the world of automation, the UiPath Platform, and guide you on how to install and setup UiPath Studio on your Windows PC.
📕 Detailed agenda:
What is RPA? Benefits of RPA?
RPA Applications
The UiPath End-to-End Automation Platform
UiPath Studio CE Installation and Setup
💻 Extra training through UiPath Academy:
Introduction to Automation
UiPath Business Automation Platform
Explore automation development with UiPath Studio
👉 Register here for our upcoming Session 2 on June 20: Introduction to UiPath Studio Fundamentals: https://community.uipath.com/events/details/uipath-lagos-presents-session-2-introduction-to-uipath-studio-fundamentals/
Northern Engraving | Modern Metal Trim, Nameplates and Appliance PanelsNorthern Engraving
What began over 115 years ago as a supplier of precision gauges to the automotive industry has evolved into being an industry leader in the manufacture of product branding, automotive cockpit trim and decorative appliance trim. Value-added services include in-house Design, Engineering, Program Management, Test Lab and Tool Shops.
What is an RPA CoE? Session 1 – CoE VisionDianaGray10
In the first session, we will review the organization's vision and how this has an impact on the COE Structure.
Topics covered:
• The role of a steering committee
• How do the organization’s priorities determine CoE Structure?
Speaker:
Chris Bolin, Senior Intelligent Automation Architect Anika Systems
Conversational agents, or chatbots, are increasingly used to access all sorts of services using natural language. While open-domain chatbots - like ChatGPT - can converse on any topic, task-oriented chatbots - the focus of this paper - are designed for specific tasks, like booking a flight, obtaining customer support, or setting an appointment. Like any other software, task-oriented chatbots need to be properly tested, usually by defining and executing test scenarios (i.e., sequences of user-chatbot interactions). However, there is currently a lack of methods to quantify the completeness and strength of such test scenarios, which can lead to low-quality tests, and hence to buggy chatbots.
To fill this gap, we propose adapting mutation testing (MuT) for task-oriented chatbots. To this end, we introduce a set of mutation operators that emulate faults in chatbot designs, an architecture that enables MuT on chatbots built using heterogeneous technologies, and a practical realisation as an Eclipse plugin. Moreover, we evaluate the applicability, effectiveness and efficiency of our approach on open-source chatbots, with promising results.
Must Know Postgres Extension for DBA and Developer during MigrationMydbops
Mydbops Opensource Database Meetup 16
Topic: Must-Know PostgreSQL Extensions for Developers and DBAs During Migration
Speaker: Deepak Mahto, Founder of DataCloudGaze Consulting
Date & Time: 8th June | 10 AM - 1 PM IST
Venue: Bangalore International Centre, Bangalore
Abstract: Discover how PostgreSQL extensions can be your secret weapon! This talk explores how key extensions enhance database capabilities and streamline the migration process for users moving from other relational databases like Oracle.
Key Takeaways:
* Learn about crucial extensions like oracle_fdw, pgtt, and pg_audit that ease migration complexities.
* Gain valuable strategies for implementing these extensions in PostgreSQL to achieve license freedom.
* Discover how these key extensions can empower both developers and DBAs during the migration process.
* Don't miss this chance to gain practical knowledge from an industry expert and stay updated on the latest open-source database trends.
Mydbops Managed Services specializes in taking the pain out of database management while optimizing performance. Since 2015, we have been providing top-notch support and assistance for the top three open-source databases: MySQL, MongoDB, and PostgreSQL.
Our team offers a wide range of services, including assistance, support, consulting, 24/7 operations, and expertise in all relevant technologies. We help organizations improve their database's performance, scalability, efficiency, and availability.
Contact us: info@mydbops.com
Visit: https://www.mydbops.com/
Follow us on LinkedIn: https://in.linkedin.com/company/mydbops
For more details and updates, please follow up the below links.
Meetup Page : https://www.meetup.com/mydbops-databa...
Twitter: https://twitter.com/mydbopsofficial
Blogs: https://www.mydbops.com/blog/
Facebook(Meta): https://www.facebook.com/mydbops/
inQuba Webinar Mastering Customer Journey Management with Dr Graham HillLizaNolte
HERE IS YOUR WEBINAR CONTENT! 'Mastering Customer Journey Management with Dr. Graham Hill'. We hope you find the webinar recording both insightful and enjoyable.
In this webinar, we explored essential aspects of Customer Journey Management and personalization. Here’s a summary of the key insights and topics discussed:
Key Takeaways:
Understanding the Customer Journey: Dr. Hill emphasized the importance of mapping and understanding the complete customer journey to identify touchpoints and opportunities for improvement.
Personalization Strategies: We discussed how to leverage data and insights to create personalized experiences that resonate with customers.
Technology Integration: Insights were shared on how inQuba’s advanced technology can streamline customer interactions and drive operational efficiency.
Taking AI to the Next Level in Manufacturing.pdfssuserfac0301
Read Taking AI to the Next Level in Manufacturing to gain insights on AI adoption in the manufacturing industry, such as:
1. How quickly AI is being implemented in manufacturing.
2. Which barriers stand in the way of AI adoption.
3. How data quality and governance form the backbone of AI.
4. Organizational processes and structures that may inhibit effective AI adoption.
6. Ideas and approaches to help build your organization's AI strategy.
Essentials of Automations: Exploring Attributes & Automation ParametersSafe Software
Building automations in FME Flow can save time, money, and help businesses scale by eliminating data silos and providing data to stakeholders in real-time. One essential component to orchestrating complex automations is the use of attributes & automation parameters (both formerly known as “keys”). In fact, it’s unlikely you’ll ever build an Automation without using these components, but what exactly are they?
Attributes & automation parameters enable the automation author to pass data values from one automation component to the next. During this webinar, our FME Flow Specialists will cover leveraging the three types of these output attributes & parameters in FME Flow: Event, Custom, and Automation. As a bonus, they’ll also be making use of the Split-Merge Block functionality.
You’ll leave this webinar with a better understanding of how to maximize the potential of automations by making use of attributes & automation parameters, with the ultimate goal of setting your enterprise integration workflows up on autopilot.
In the realm of cybersecurity, offensive security practices act as a critical shield. By simulating real-world attacks in a controlled environment, these techniques expose vulnerabilities before malicious actors can exploit them. This proactive approach allows manufacturers to identify and fix weaknesses, significantly enhancing system security.
This presentation delves into the development of a system designed to mimic Galileo's Open Service signal using software-defined radio (SDR) technology. We'll begin with a foundational overview of both Global Navigation Satellite Systems (GNSS) and the intricacies of digital signal processing.
The presentation culminates in a live demonstration. We'll showcase the manipulation of Galileo's Open Service pilot signal, simulating an attack on various software and hardware systems. This practical demonstration serves to highlight the potential consequences of unaddressed vulnerabilities, emphasizing the importance of offensive security practices in safeguarding critical infrastructure.
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/temporal-event-neural-networks-a-more-efficient-alternative-to-the-transformer-a-presentation-from-brainchip/
Chris Jones, Director of Product Management at BrainChip , presents the “Temporal Event Neural Networks: A More Efficient Alternative to the Transformer” tutorial at the May 2024 Embedded Vision Summit.
The expansion of AI services necessitates enhanced computational capabilities on edge devices. Temporal Event Neural Networks (TENNs), developed by BrainChip, represent a novel and highly efficient state-space network. TENNs demonstrate exceptional proficiency in handling multi-dimensional streaming data, facilitating advancements in object detection, action recognition, speech enhancement and language model/sequence generation. Through the utilization of polynomial-based continuous convolutions, TENNs streamline models, expedite training processes and significantly diminish memory requirements, achieving notable reductions of up to 50x in parameters and 5,000x in energy consumption compared to prevailing methodologies like transformers.
Integration with BrainChip’s Akida neuromorphic hardware IP further enhances TENNs’ capabilities, enabling the realization of highly capable, portable and passively cooled edge devices. This presentation delves into the technical innovations underlying TENNs, presents real-world benchmarks, and elucidates how this cutting-edge approach is positioned to revolutionize edge AI across diverse applications.
Dandelion Hashtable: beyond billion requests per second on a commodity serverAntonios Katsarakis
This slide deck presents DLHT, a concurrent in-memory hashtable. Despite efforts to optimize hashtables, that go as far as sacrificing core functionality, state-of-the-art designs still incur multiple memory accesses per request and block request processing in three cases. First, most hashtables block while waiting for data to be retrieved from memory. Second, open-addressing designs, which represent the current state-of-the-art, either cannot free index slots on deletes or must block all requests to do so. Third, index resizes block every request until all objects are copied to the new index. Defying folklore wisdom, DLHT forgoes open-addressing and adopts a fully-featured and memory-aware closed-addressing design based on bounded cache-line-chaining. This design offers lock-free index operations and deletes that free slots instantly, (2) completes most requests with a single memory access, (3) utilizes software prefetching to hide memory latencies, and (4) employs a novel non-blocking and parallel resizing. In a commodity server and a memory-resident workload, DLHT surpasses 1.6B requests per second and provides 3.5x (12x) the throughput of the state-of-the-art closed-addressing (open-addressing) resizable hashtable on Gets (Deletes).
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.
Your One-Stop Shop for Python Success: Top 10 US Python Development Providers
Service contract clauses as business rules
1. Service contract clauses as
business rules™
Fabio De Rosa1, Ariele P. Maesano2, Libero Maesano3
1 fabio.de-rosa@simple-eng.com - SIMPLE ENGINEERING, Rome, Italy
2 ariele.maesano@lip6.fr - Laboratoire d’Informatique de Paris 6 UPMC, Paris, France
(formerly SIMPLE ENGINEERING, Paris, France)
3 libero.maesano@simple-eng.com - SIMPLE ENGINEERING, Paris, France
24th International Conference on Software & Systems Engineering and their Applications
ICSSEA ‘12 – Paris Oct. 23-25
2. Table of contents
Problem statement
Elements of the solution
An example: Withdrawal
Conclusion
ICSSEA ‘12 – Paris Oct. 23-25 De Rosa et al., Service contract clauses as business rules 23/10/12 - 2
3. Problem statement
Contract-first Service Oriented Architecture
Services are not systems – they are activities carried out by systems (providers) that
bring value to other systems (consumers)
Each service shall be precisely defined by an artifact - the service contract - that
must be considered as a bundle of rights and duties by the service parties
The service contract is the formal model of the service that the parties must agree
MDA approach: the service model is layered
Computation Independent Model (CIM) – declarative model of the service
Platform Independent Model (PIM) – abstract computational model of the
and transformation
Model mapping
service – independent from a specific platform (UML/OCL Model)
Platform Specific Models (PSMs) – concrete computational models of the service
– dependent on the specific platform – halved in two parties
Interoperability Platform(s) SM – allowing interoperability of non
interoperable implementations (SOAP, REST, …) - included in the service
contract
Implementation Platform(s) SM – supporting the parties’ implementations
(JEE,.NET,…) – outside the service contract
The service model is not the system model !
ICSSEA ‘12 – Paris Oct. 23-25 De Rosa et al., Service contract clauses as business rules 23/10/12 - 3
4. Problem statement (II)
Service model modularity - separation of concerns
operation model - what the provider does for the consumer (not
how it does it!)
interaction model - how the provider and the consumer interact in
order to coordinate the service invocation, deliberation, delivery (or
refusal), reporting (conversations – choreographies)
security model - authentication, authorization, confidentiality,
integrity, accountability, non repudiation
performance model – volume, throughput, speed, scalability,
availability, reliability, integrity, maintainability
The service operation model is the core contract component – the
same service operation may be carried out through several different
interaction, security and performance agreements
The focus here is on the service operation expression at the CIM level
ICSSEA ‘12 – Paris Oct. 23-25 De Rosa et al., Service contract clauses as business rules 23/10/12 - 4
5. Problem statement (III)
Formality vs. understandability
Computation Independent Model: previously called Business Model
How to express the service operation in a notation that can be easily
understood and validated by the business stakeholders
natural language ?
How to express the service operation in a formal notation that allows:
mechanical checking (model checking for properties such as consistency)
automated transformation towards computational models (model-driven
engineering)
automated creation of test cases (model-based testing)
UML/OCL ?
Understandability vs. mechanical checking, transformation and automated
generation are conflicting exigencies:
Natural language is understandable but it is hard to be mechanically
checked and automatically transformed
UML/OCL is formal but not understandable by the business stakeholders –
it is suitable for the computational model (PMI)
ICSSEA ‘12 – Paris Oct. 23-25 De Rosa et al., Service contract clauses as business rules 23/10/12 - 5
6. Elements of the solution
Contract-based design formulation of the service operation
How to express a service operation in a declarative manner ?
Design by Contract™ by Bertrand Meyer, that we call ‘contract-
based design’1, is an approach for designing software that
prescribes that software designers should define not only syntactic
interface specifications for software components, but also semantic
ones that extend the ordinary definition of abstract data types with
pre-conditions, post-conditions and invariants
An operation, equipped with a signature, can be precisely defined
by:
Its pre-conditions – to be assumed on entry
Its post-conditions – to be guaranteed on exit
Its invariants – to be assumed on entry and guaranteed on exit
1 Design by Contract is a registered trademark of Eiffel Software in the United States - In order to avoid the
confusion between the general design approach and the specific Eiffel provisions and mechanisms, we will employ
the generic term ‘contract-based design’
ICSSEA ‘12 – Paris Oct. 23-25 De Rosa et al., Service contract clauses as business rules 23/10/12 - 6
7. Elements of the solution (II)
Business rules
Business rules are all around in the “real” economy, but yet for whatever
reason they are seldom featured in requirements for the digital economy
The very first goal of the business rule research field and practice has been
to give the rules the status of “first class” requirements and to distinguish
them from other requirement artifacts such as use cases and process
models
An essential feature of business rules is understandability
Controlled natural language - formulation style that
uses only words from a specified, relatively limited set of words in
some defined natural language
uses only specified forms of phrase, from a relatively limited set
Very important step: release by the OMG of the Semantics of Business
Vocabulary and Business Rules (SBVR – 2008) - controlled natural
language becomes formal (equipped with a formal meta-model) !
ICSSEA ‘12 – Paris Oct. 23-25 De Rosa et al., Service contract clauses as business rules 23/10/12 - 7
8. Elements of the solution (III)
Semantics of Business Vocabulary and Rules (SBVR)
SBVR-compliant Business vocabulary
contains all the specialized terms, names, and fact type forms of
concepts that a given organization or community uses in their talking
and writing in the course of doing business
supporting basis for expressing business rules
SBVR-compliant Business rules
Criteria for making decisions
Consistent with formal logics:
structural (definitional) rules are alethic claims (necessity)
operative (behavioral) rules are deontic claims (obligation)
Business rules are logical expressions, not CA or ECA rules !
SBVR does not mandate any particular notation
Specification includes a recommended proposal for expressing
business rules with controlled natural English language
ICSSEA ‘12 – Paris Oct. 23-25 De Rosa et al., Service contract clauses as business rules 23/10/12 - 8
9. An example: Withdrawal
Writing convention
terms - that design noun concepts - are underlined (term)
verbs - that design fact types - are in italics (verb)
names - that design individual concepts - are doubly underlined and
with the first letter capitalized (Name)
keywords - that design quantifiers, logical operators, modal
operators ... - are in boldface (keyword)
Bank vocabulary
the expression of operation clauses on a banking service needs the
definition of object-type and role entries such as ‘account’,
‘balance’, ‘amount’, ‘customer’ and of fact-type entries such as
‘customer withdraws amount from account’, ‘account number
identifies account’, ‘account has state’, ‘account has balance’ …
ICSSEA ‘12 – Paris Oct. 23-25 De Rosa et al., Service contract clauses as business rules 23/10/12 - 9
10. An example: Withdrawal (II)
Objectification (crucial formulation device)
Propositions based on the ternary fact type ‘customer withdraws amount from account’ can be objectified by adding
to the service vocabulary the noun concept ‘withdrawal’ and additional binary fact types such as ‘customer effects
withdrawal’, ‘withdrawal involves account’ and ‘withdrawal takes out amount’
The relationship between the objectified fact type and the objectifying object types and fact types is established
through a structural rule such as:
It is necessary that
each withdrawal that is effected by a customer and that involves an account and that takes out an amount
is an actuality that the customer withdraws the amount from the account
An actuality is a state of affairs that happens in the actual world
Withdrawal operation signature
Add vocabulary entries such as: ‘withdrawal operation’, ‘argument’, ‘result’, ‘withdrawal operation has argument’,
‘withdrawal operation has result’, ‘argument specifies account number’, ‘argument specifies amount’, ‘result specifies
account number’, ‘result specifies account balance’.
And a structural rule such as:
It is necessary that
each withdrawal operation has exactly one argument that specifies exactly one account number and
exactly one amount and has exactly one result that specifies exactly one account number and exactly one
account balance
ICSSEA ‘12 – Paris Oct. 23-25 De Rosa et al., Service contract clauses as business rules 23/10/12 - 10
11. An example: Withdrawal (III)
Withdrawal operation pre-condition
bearing on resources states and operation arguments
expressed as an operative rule
It is obligatory that
if
a withdrawal operation that has an argument that specifies an account number and that specifies an amount
handles a withdrawal
then
the account that is involved in the withdrawal is identified by the account number immediately before the
withdrawal occurs
and the account is in the extension of the concept ‘account’ immediately before the withdrawal occurs
and the account state of the account equals Active immediately before the withdrawal occurs
and the balance of the account is greater than the amount immediately before the withdrawal occurs
The keywords ‘if’ and ‘then’ respectively introduce the antecedent and consequent of a material implication.
With the fact type ‘state of affairs1 occurs immediately before state of affairs2 occurs’, the SBVR Structured English
supports objectification by proposing a convenient mechanism that is based on the word ‘occurs’ being in the
designation of a fact type after a placeholder. An implicit form of a fact type can be used that objectifies a
propositional expression in the position of the placeholder and leaves out the word ‘occurs’.
The fact type ‘state of affairs1 occurs immediately before state of affairs2 occurs’ conveys the meaning of the well-
known Allen’s “X meets Y” relation between the temporal interval X in which the state of affairs1 occurs and the
temporal interval Y in which the state of affairs2 occurs
ICSSEA ‘12 – Paris Oct. 23-25 De Rosa et al., Service contract clauses as business rules 23/10/12 - 11
12. An example: Withdrawal (IV)
Withdrawal operation post-condition
bearing on resources’ states “immediately after” and operation
results, and their relationships with resource states “immediately
before” and operation arguments
expressed as an operative rule
It is obligatory that
if
a withdrawal operation that has an argument that specifies an account number1 and that specifies an amount
and that has a result that specifies an account number2 and that specifies a balance1 handles a withdrawal
then
the account involved in the withdrawal has a balance2 immediately after the withdrawal occurs
and the account has a balance3 immediately before the withdrawal occurs
and the balance2 equals the balance3 minus the amount
and the account number2 identifies the account immediately after the withdrawal occurs
and the account is in the extension of the concept ‘account’ immediately after the withdrawal occurs
and the account number2 equals the account number1
and the balance1 equals the balance2
ICSSEA ‘12 – Paris Oct. 23-25 De Rosa et al., Service contract clauses as business rules 23/10/12 - 12
13. An example: Withdrawal (V)
Withdrawal operation invariant
bearing on the subsistence of states of the service world that
shall not change as an effect of the service operation execution
we consider that they are implicitly asserted (Common Sense
Law of Inertia)
there is no need of explicitly stating invariants as “dumb”
operative business rules such as:
It is obligatory that
if
a withdrawal operation handles a withdrawal
then
the account that is involved in the withdrawal and that is in the extension of the concept ‘account’
immediately before the withdrawal occurs is in the extension of the concept ‘account’ immediately after the
withdrawal occurs
and the account number that identifies the account immediately before the withdrawal occurs identifies the
account immediately after the withdrawal occurs
and the account state that is of the account immediately before the withdrawal occurs is of the account
immediately after the withdrawal occurs
and ...
ICSSEA ‘12 – Paris Oct. 23-25 De Rosa et al., Service contract clauses as business rules 23/10/12 - 13
14. Meta-requirements
The service operation must be realized by an activity that comply with the
(meta-)requirements:
Accuracy - the activity effects – state changes & service operation results –
shall satisfy the service operation post-condition rule
Robustness - the activity can be performed only if the service operation
pre-condition rule is satisfied
Atomicity - the activity shall be “all or nothing” and does not show
intermediate states - only the initial and the final ones are accessible
Isolation - the activity shall be conducted as the only one that accesses the
resources that are referred to by the service operation pre/post-condition
rules
Durability - the activity effects shall be permanent “all things being equal”
Integrity - the activity must not produce any “side” effect, i.e. that is not
explicitly mentioned by the service operation post-condition rule
Safety – the activity partial or total failure shall not lead to a non-compliant
state
ICSSEA ‘12 – Paris Oct. 23-25 De Rosa et al., Service contract clauses as business rules 23/10/12 - 14
15. Conclusion and future work
Service operation contract-based formulation with SBVR makes real the dream of
formality and understandability – these conceptual tools can be used now - hand-
made transformation to UML/OCL (PIM)
we are working on:
controlled natural French language
controlled natural Italian language – within HL7 Italia
Ongoing and future research programme in the MDA community:
editing tools and formal checkers that help formulating the vocabulary and the rules
tools supporting the automatic transformation of the vocabulary and rulebook into
artifacts based on PIM level notations, such as UML/OCL and eventually OWL
automatic transformation of elements of the service PIM (UML/OCL, OWL) into the
interoperability PSM (SOAP, REST platforms) and the implementation PSM (JEE, .NET
platforms) - this issue has already been broadly investigated in the research field and
by the authors, and henceforth can be considered an engineering rather than a
research task
model-based testing – automated, systematic (checking pre/post conditions,
unintended side effects …) and purpose-driven generation of test cases from the
service model (from SBVR – UML/OCL to TTCN-3 ….)
MIDAS project - www.midas-project.eu
ICSSEA ‘12 – Paris Oct. 23-25 De Rosa et al., Service contract clauses as business rules 23/10/12 - 15
16. Questions ?
Thank you for your attention
More information:
http://blog.simple-eng.com
ICSSEA ‘12 – Paris Oct. 23-25 De Rosa et al., Service contract clauses as business rules 23/10/12 - 16