1 An Object Model for Business Applications By Fred A. Cummins Electronic Data Systems Troy, Michigan ## ## This presentation will focus on defining a model for objects--a generalized representation to be used in the development of business applications. In "business application" I am including any application used in the operation of an enterprise. The enterprise might be commercial business or it might be a government agency or an academic institution. My purpose is to define a level of abstraction to be supported by the Business Object Facility (BOF) that is the subject of the RFP issued by the OMG Business Objects Domain Task Force. My concern is that the BOF should greatly simplify the effort required by application developers to develop solutions to business problems. I am hopeful that this presentation will help potential submitters understand the requirements I see for the BOF from an application developer's perspective, so they can respond accordingly to the RFP.
2 Business Object Model A computational abstraction: The conceptual basis for implementation of a class of applications Incorporates general-purpose computational mechanisms as the Defining Entity in Object Technology 2 2 The Business Object Model I will be discussing is a computational abstraction. It is the conceptual basis for implementation of a class of applications. These applications represent problems that would exist with or without computers. They are problems where objects are used to represent business concepts and model problem situations. The Business Object Model incorporates general purpose computational mechanisms. As such, the model conceals computational problems from the concern of the application developer, allowing him or her to concentrate on modeling the business problem.
3 Need for a Business Object Model To minimize the transformation required to implement models of business domains To conceal computational mechanisms necessary to support applications in a distributed, heterogeneous environment To assure compatibility of independently developed components To enable integration of intelligence: constraints, agents, expert rules, adaptive mechanisms as the Defining Entity in Object Technology 3 3 Why do we need a Business Object Model that is different from the model of objects used for other computations? First, we should minimize the transformation effort required to implement models for business domains. This is important for development of flexible systems that meet user requirements. The more involved the transformation, the greater the difficulty in meeting user requirements. Second, we should conceal computational mechanisms necessary to support applications in a distributed, heterogeneous environment. OMG technology has introduced several new dimensions of complexity which will increase the effort and risk of application development if these problems must be solved in every project by application developers. Third, we must assure compatibility of independently developed components. Application developers must ensure the compatibility of the business concepts and methods, but there must also be compatibility of underlying mechanisms such as transaction management, concurrency, relationship management, notification and persistence. Without this compatibility, we cannot hope to develop a marketplace in sharable business application components. Fourth, with a higher level of abstraction and a stable architecture, we can begin to integrate intelligence into business applications with such mechanisms as constraints, agents, expert rules and adaptive mechanisms. Today, such capabilities are limited in scope and difficult to integrate because of inconsistencies and inaccessibility of information across business applications.
4 Enterprise Model Agent Objects User Interface Objects Application Objects Business Objects Enteprise Objects as the Defining Entity in Object Technology Cummins & Sadiq 4 4 This Enterprise Model illustrates where I see business objects used. This model is similar to the three-tiered model with a couple exceptions. First of all, the bottom layer is not data storage, but rather business objects that are shared across the enterprise. Data storage, or persistence, should be orthogonal to the design of business applications--it should be automatic. Secondly, agents are added as mechanisms for monitoring and directing activities in the other layers. These might be workflow management components, expert systems or intelligent tutors, for example. Business objects exist in the enterprise objects and application objects layers. As I mentioned, the enterprise objects implement concepts that are shared by many applications. They model the business as a whole. Application objects model a particular problem or segment of the business. Many of the application objects will be views of enterprise objects and there must be an active linkage between these layers. The use of views to separate the enterprise and application layers allows these models to evolve relatively independently. Because the interface is through methods, when changes occur in the enterprise model the affected view methods may be modified to adapt to the change without otherwise affecting the applications. When applications change, the effects need not extend to the enterprise model unless the extension should be shared across the enterprise. Views also allow applications to work with a simplified representation that is sufficient for the application but maps to a more robust representation for the enterprise-wide model. The same basic mechanism should be used to attach agents and user interfaces.
5 Business Objects Agent Objects User Interface Objects Application Objects Enteprise Objects Objects used to represent concepts that occur in an enterprise (business) for performing computations or maintaining information about the enterprise. Concepts Would exist in a non-computer solution Range from enterprise-independent to situation-unique Could be represented with large-grained or fine-grained objects Represented independent of programming language, operating system, database, or other computing facilities as the Defining Entity in Object Technology 5 5 This slide refines the concept of a business object for purposes of this discussion. Business objects are used to represent concepts that occur in an enterprise, or business, for performing computations or maintaining information about the enterprise. These concepts would exist in a non-computer solution to the business problem--they are not concepts that are necessary to make computers useful. For example, graphical display objects are not business objects. Business objects include large-grained and fine-grained objects. They implement a wide range of concepts. Finally, the concepts being represented are independent of programming language, operating system, database, or other computing facilities. The concepts do not depend on computational implementations, but on the nature of the enterprise.
6 A Business Object Example as the Defining Entity in Object Technology 6 6 Here is an example of a business object: a customer order. The smaller boxes represent functional interfaces to the order which will get or put information or perform operations. The, and interfaces will return elementary values--i refer to these as attributes. The and interfaces return references to other structured objects--i refer to the and interfaces as relationships. The objects they reference may have complementary references. The interface invokes an operation (i.e., ship the order). I refer to this object as a "composite" object because, semantically, the referenced by the order are part of the order. They represent the specification of parts and quantities requested by the customer. Generally, the order and the items will be used as a unit. I will use this object example in further discussions.
7 Business Object Model Context External Identifier Aspect Operation Transaction Composite object bounds View as the Defining Entity in Object Technology 7 7 These are characteristics of business objects that are important for the application developer. They represent the level of abstraction at which application developers should work. First, business objects are used in a context that must be accessible to the application. This context includes such things as user preferences, organizational affiliation, and default I/O devices such as the user's printer. This context must be available even though the processing associated with the application may extend to other computers in a distributed environment.
8 Business Object Model Context External Identifier Aspect Operation Transaction Composite object bounds View as the Defining Entity in Object Technology 8 8 Business objects, for the most part, have identifiers that are used by humans to reference the objects. For example, order number as well as social security number, employee number, vehicle ID, part number, customer name, city name, and product name are all external identifiers. These must be interpreted in a context since the identity of an employee or an order, for example, must be determined by reference to the enterprise. Whenever one of these objects becomes the target of processing, these external identifiers must be translated to the identity of an active object even though the object may not currently be active--it may only exist in a database.
9 Business Object Model Context External Identifier Aspect Operation Transaction Composite object bounds View as the Defining Entity in Object Technology 9 9 I use the term aspect to define interfaces associated with attributes or relationships of an object. At an elementary level, an aspect provides get and put methods for a value associated with the object. However, some aspects may return computed rather than stored values. For example, is probably a computed value. Furthermore, the implementation of aspects must include functionality to support related computational mechanisms which I will discuss later. For example, in order for aspects to support change notification, the put methods must generate appropriate notices when a value is changed.
10 Business Object Model Context External Identifier Aspect Operation Transaction Composite object bounds View as the Defining Entity in Object Technology Operations are methods that perform actions--they implement business processes. These processes should propagate to other computers and objects implemented in other programming languages without application programmer concern about destruction of objects inadvertently created, concurrency conflicts with other processes or retrieval of referenced objects from a database. Programming of these methods should be essentially the same as if all of the objects referenced were in a single computing environment.
11 Business Object Model Context External Identifier Aspect Operation Transaction Composite object bounds View as the Defining Entity in Object Technology Transactions must be visible to the application developer from the standpoint that the developer must define when a transaction starts and terminates, either successfully or unsuccessfully. Transactions are a business concern and must be defined in a manner that is consistent with the way the user does his or her work. At the same time, of course, transactions affect other mechanisms that should be concealed from the developer, such as concurrency control. For example, if a user is going to update information on an order, a transaction should be initiated for that activity. If the update is completed successfully, then the transaction should be committed, and the user should be aware of its acceptance. If the user attempts to enter unacceptable information or decides to abandon the changes, then the transaction should be terminated and any tentative changes should be backed out--the user should also be aware of this action.
12 Business Object Model Context External Identifier Aspect Operation Transaction Composite object bounds View as the Defining Entity in Object Technology I noted earlier that the customer order is a composite object--it has item objects that are part of the order. These item objects should be included when the order is copied or cancelled, but the parts that are referenced by the items should not be included in such operations. Consequently, the relationships between objects that are part of the order and other objects external to the order--such as parts--must, in some way, be identified as limiting the bounds of the order. Such specifications should be indicated on the aspects that define the boundary relationships, but the imlementation of this designation should be concealed from programmer concern.
13 Business Object Model Context External Identifier Aspect Operation Transaction Composite object bounds View as the Defining Entity in Object Technology Finally, application developers should be given views for their local representation of enterprise concepts. Views are a special form of application business objects. These views must participate in application processing as local objects and may have local aspects and operations. But they must also be linked to the corresponding enterprise objects so that updates to state directed to views are propagated to the enterprise objects, and updates to the enterprise objects are propagated to the views of other applications that are actively working with the shared information. Views may also simplify the representation of a business concept so that a complex structure in the enterprise model might be simplified to a single view for a particular application. For example, a participant in a project might be represented as a single object for a project management application, while that single object might incorporate information obtained from the full employee object and related person object in the enterprise model In addition to providing simplified representations and adaptive interfaces for applications, views also provide a mechanism for security control. A view will define those aspects and operations available to the user of the view. For example, a project manager view of an employee would exclude salary information.
14 Integrated Facilities as the Defining Entity in Object Technology Relationship management Persistence Concurrency control Change notification Constraint resolution Logical search Configuration management Reference resolution Garbage collection Now lets turn to the facilities that should be integrated into the Business Object Facility. The implementation of these facilities should not concern the application developer. Relationships between objects should be incorporated in the implementation of the aspects I mentioned earlier. When an object is added or removed from a relationship, complementary relationships should be updated appropriately without explicit programmer action. In the example, the addition of an item to the order should update the relationship including a reference from the new item object back to the order. Relationship management must also handle the difference between references to objects that are part of a composite object, and objects that are just referenced. When a non-part-of relationship is externalized--moved to a file or database, the references should be converted to the associated external identifiers. The elements of a composite object will generally be stored together and may be linked by local references appropriate to the storage medium. In the example, items are part of the order, but references between items and parts are not part of relationships.
15 Integrated Facilities as the Defining Entity in Object Technology Relationship management Persistence Concurrency control Change notification Constraint resolution Logical search Configuration management Reference resolution Garbage collection Persistence should be invisible to the application developer except that an object should be designated as persistent or non-persistent in a way that is independent of application logic. When a message is sent to a persistent object, the object should be automatically retrieved from the database if it is not already active. When an update transaction is committed, all persistent objects that were updated by that transaction should automatically be written to the database.
16 Integrated Facilities as the Defining Entity in Object Technology Relationship management Persistence Concurrency control Change notification Constraint resolution Logical search Configuration management Reference resolution Garbage collection Concurrency control should likewise be invisible to the application developer. Concurrency control, for this purpose, means assuring transaction serialization. The net effect of processing of a group of transactions should be the same as if they were executed serially, one after another. Locking and deadlock detection should be handled automatically.
17 Integrated Facilities as the Defining Entity in Object Technology Relationship management Persistence Concurrency control Change notification Constraint resolution Logical search Configuration management Reference resolution Garbage collection Change notification is a service that should be available for all business objects. For example, an account manager might be interested in knowing if the total price of an order changes. The monitoring facility would request change notification on the aspect for orders of interest. In general, most orders would not generate these events because nobody is interested. Change notification is not the same as event notification as currently defined in OMG. A request for change notification is directed to a specific object instance for notification of change to a particular aspect. OMG event notification is based on a request to a service for notice of any occurrence of an event type; it requires that all sources of events which may be of interest always notify the service of the occurrence of any such event. The granularity is very different. Change notification is necessary to drive displays, agents and active views. The notification mechanism should be automatically incorporated in object aspects.
18 Integrated Facilities as the Defining Entity in Object Technology Relationship management Persistence Concurrency control Change notification Constraint resolution Logical search Configuration management Reference resolution Garbage collection Constraints are a very important facility that has not been well developed for object-oriented applications. Constraints provide a declarative means to apply business rules and assure model consistency and integrity. For example, a constraint might limit the of an order based on the customer s credit limit. Constraint propagation provides a valuable mechanism for manipulation of complex models such as engineering designs. The mechanism for attachment and resolution of constraints should be invisible to the application developer.
19 Integrated Facilities as the Defining Entity in Object Technology Relationship management Persistence Concurrency control Change notification Constraint resolution Logical search Configuration management Reference resolution Garbage collection Searches in the business objects environment, i.e., queries, should be logical searches based on the conceptual model, not searches based on physical structures. For example, SQL queries require that the user understand the table structure of the database. The scope of an SQL query is the scope of the database. These are physical characteristics of the implementation which should not be visible to either the application user or the developer. A logical search should be based on the conceptual model, the context of the request and logical definitions of facts. The search should not be restricted to objects that are persistent. And the search mechanism should be integrated into the environment, not restricted by the boundaries of computer and data storage devices.
20 Integrated Facilities as the Defining Entity in Object Technology Relationship management Persistence Concurrency control Change notification Constraint resolution Logical search Configuration management Reference resolution Garbage collection Application developers also need facilities to support configuration management. Developers must be able to package application components and deploy versions of those components. Components and their versions will have dependencies on other components and versions. This is challenging when configuring a single-computer application; it can be a nightmare when dealing with a distributed computing environment with workstations of varying configurations depending upon user requirements and authorization. Configuration management should also consider security controls and workstation hardware constraints.
21 Integrated Facilities as the Defining Entity in Object Technology Relationship management Persistence Concurrency control Change notification Constraint resolution Logical search Configuration management Reference resolution Garbage collection Object references should be resolved without application developer involvement. If an application has a reference to an object, that reference should be guaranteed viable unless an unrecoverable error has occurred. If the object is persistent but is not currently active, then, if a message is sent to it, it should be automatically retrieved from the data base without explicit programming by the application developer.
22 Integrated Facilities as the Defining Entity in Object Technology Relationship management Persistence Concurrency control Change notification Constraint resolution Logical search Configuration management Reference resolution Garbage collection Finally, objects that are no longer in use should be automatically garbage collected. This applies to objects in computer memory and objects in databases. Application developers should not need to worry about explicit destruction of objects or memory leaks. When an object is no longer referenced in any environment then it should be destroyed. This is particularly critical when objects are shared by multiple applications and users. Automatic garbage collection requires mechanisms to resolve remote references and mechanisms to detect and update accounting for references by remote nodes that have failed. AGarbage collection and all of the above facilities must function consistently across ORB domains so that application developers need not be concerned with the distribution of their applications or related objects. This is essential for meaningful interoperability of business applications.
23 Summary Agent Objects User Interface Objects Application Objects Enteprise Objects Minimal modeling transformation Easy to develop applications Large-scale integration Compatible components Heterogeneous environments Build on accomplishments as the Defining Entity in Object Technology In summary, the implementation of this abstraction with the Business Object Facility will have very important benefits. The transformation of analysis models to application implementations will be minimal, improving the productivity of developers and the flexibility and effectiveness of applications. It will be easy to develop applications in distributed, heterogeneous environments because application developers generally will not need to be concerned about the added complexity. Such facilities will enable large-scale integration. The enterprise model described allows applications and enterprise objects to evolve while the scope of impact of changes is confined (using views as adaptors). This enables sharing across many applications and business functions. We can reasonably expect that independent developers will be able to produce compatible components because the architecture and computational mechanisms will be consistent, and developers need only concentrate on defining consistent business semantics and protocols. These systems can be expected to operate in heterogeneous environments because application developers will be shielded from the differences between environments. When new software releases or computing platforms are introduced, there will be no need to redevelop applications. Finally, we will be able to start building on our accomplishments instead of starting from scratch over and over again to adapt to new technology. We can start to exploit more sophisticated techniques to incorporate intelligence, facilitate collaborative work, and achieve enterprise-level optimizations rather than sub-optimal, local solutions. Thank you for your attention.
The ConTract Model Helmut Wächter, Andreas Reuter November 9, 1999 Overview In Ahmed K. Elmagarmid: Database Transaction Models for Advanced Applications First in Andreas Reuter: ConTracts: A Means for
The Service Revolution software engineering without programming languages Gustavo Alonso Institute for Pervasive Computing Department of Computer Science Swiss Federal Institute of Technology (ETH Zurich)
RUP Design Workflow Michael Fourman Introduction Design architecture that can meet all requirements Understand non-functional requirements and constraints related to technologies Identify subsystems (overall
ACSD ATPN Xi an China June 2008 Challenges and Opportunities for formal specifications in Service Oriented Architectures Gustavo Alonso Systems Group Department of Computer Science Swiss Federal Institute
COMPONENTS in a database environment DATA data is integrated and shared by many users. a database is a representation of a collection of related data. underlying principles: hierarchical, network, relational
Distributed Objects and Components Introduction This essay will identify the differences between objects and components and what it means for a component to be distributed. It will also examine the Java
D. SERVICE ORIENTED ARCHITECTURE PRINCIPLES 1. Principles of serviceorientation 2. Service exchange lifecycle 3. Service composition 4. Evolution of SOA 212 D.1 Principles of service-orientation 213 HISTORICAL
CST171 DB Management Approaches Page 1 1 2 3 4 5 6 7 Database Management Approaches CST171 Distributed DBMS (DDBMS) (Page 1) Computers at various sites can be connected with communications network or network
CHAPTER 2 MODELLING FOR DISTRIBUTED NETWORK SYSTEMS: THE CLIENT- SERVER MODEL This chapter is to introduce the client-server model and its role in the development of distributed network systems. The chapter
Unified Modeling Language (UML) for Database Systems and Computer Applications Sunguk Lee * Research Institute of Industrial Science and Technology Pohang, Korea email@example.com *Correspondent Author:
Software Engineering Component-Based Software Engineering Based on Software Engineering, 7 th Edition by Ian Sommerville Objectives To explain that CBSE is concerned with developing standardised components
-Oriented Architecture and Software Engineering T-86.5165 Seminar on Enterprise Information Systems (2008) 1.4.2008 Characteristics of SOA The software resources in a SOA are represented as services based
Effecting Data Quality Improvement through Data Virtualization Prepared for Composite Software by: David Loshin Knowledge Integrity, Inc. June, 2010 2010 Knowledge Integrity, Inc. Page 1 Introduction The
COURSE NAME: Database Management TOPIC: Database Design LECTURE 3 The Database System Life Cycle (DBLC) The database life cycle contains six phases; 1 Database initial study. Analyze the company situation.
Tier Architectures Kathleen Durant CS 3200 1 Supporting Architectures for DBMS Over the years there have been many different hardware configurations to support database systems Some are outdated others
CHAPTER 20 TESING WEB APPLICATIONS Overview The chapter describes the Web testing. Web testing is a collection of activities whose purpose is to uncover errors in WebApp content, function, usability, navigability,
Optimizing Performance Training Division New Delhi Performance tuning : Goals Minimize the response time for each query Maximize the throughput of the entire database server by minimizing network traffic,
Importance of Data Abstraction, Data Virtualization, and Data Services David S. Linthicum The management of data is core to successful IT. However, few enterprises have a strategy for the use of data assets,
Appendix M INFORMATION TECHNOLOGY (IT) YOUTH APPRENTICESHIP PROGRAMMING & SOFTWARE DEVELOPMENT AND INFORMATION SUPPORT & SERVICES PATHWAY SOFTWARE UNIT UNIT 5 Programming & and Support & s: (Unit 5) PAGE
Network Data Management Protocol (NDMP) White Paper Summary What is the primary goal of enterprise storage management? To back up and restore information in an intelligent, secure, timely, cost-effective
CSCI 275 Database Management Systems Informally: Database - Collection of related data Database Management System (DBMS) - Software that manages and controls access to the database Database Application
GEOG 482/582 : GIS Data Management Lesson 10: Enterprise GIS Data Management Strategies Overview Learning Objective Questions: 1. What are challenges for multi-user database environments? 2. What is Enterprise
The OMG BPM Standards Derek Miers CEO, BPM Focus +44 (20) 8742 8500 UK Office +44 (7703) 178 500 UK Cell +1 (714) 600 9010 US Cell firstname.lastname@example.org A BPM Definition Business Process Management is primarily
Stock Trader System Architecture Description Michael Stevens email@example.com http://www.mestevens.com Table of Contents 1. Purpose of Document 2 2. System Synopsis 2 3. Current Situation and Environment
Overview of Database Systems Kanda Runapongsa (firstname.lastname@example.org) Dept of Computer Engineering Khon Kaen University Overview What is a Database, in particular, a relational DBMS? Why should we consider
Technical Overview Enterprise Server 2.0 Enterprise Server Architecture The Enterprise Server (ES) platform addresses the HVTO business challenges facing today s enterprise. It provides robust, flexible
System types 1 Personal systems that are designed to run on a personal computer or workstation Distributed systems where the system software runs on a loosely integrated group of cooperating processors
Apache Web Server Execution Tracing Using Third Eye Raimondas Lencevicius Alexander Ran Rahav Yairi Nokia Research Center, 5 Wayside Road, Burlington, MA 01803, USA Raimondas.Lencevicius@nokia.com Alexander.Ran@nokia.com
ICS 434 Advanced Database Systems Dr. Abdallah Al-Sukairi email@example.com Second Semester 2003-2004 (032) King Fahd University of Petroleum & Minerals Information & Computer Science Department Outline
Three Fundamental Techniques To Maximize the Value of Your Enterprise Data Prepared for Talend by: David Loshin Knowledge Integrity, Inc. October, 2010 2010 Knowledge Integrity, Inc. 1 Introduction Organizations
Information Technology Standard Commonwealth of Pennsylvania Governor's Office of Administration/Office for Information Technology STD Number: STD-INF003B STD Title: Data Modeling Basics Issued by: Deputy
ECS 165A: Introduction to Database Systems Todd J. Green based on material and slides by Michael Gertz and Bertram Ludäscher Winter 2011 Dept. of Computer Science UC Davis ECS-165A WQ 11 1 1. Introduction
JOURNAL OF OBJECT TECHNOLOGY Online at www.jot.fm. Published by ETH Zurich, Chair of Software Engineering JOT, 2008 Vol. 7, No. 8, November-December 2008 What s Your Information Agenda? Mahesh H. Dodani,
COMP 378 Database Systems Notes for Chapter 1 of Database System Concepts Introduction A database management system (DBMS) is a collection of data and an integrated set of programs that access that data.
What is Data Virtualization? Rick F. van der Lans Data virtualization is receiving more and more attention in the IT industry, especially from those interested in data management and business intelligence.
Dynamism and Data Management in Distributed, Collaborative Working Environments Alexander Kipp 1, Lutz Schubert 1, Matthias Assel 1 and Terrence Fernando 2, 1 High Performance Computing Center Stuttgart,
METU Department of Computer Eng Ceng 302 Introduction to DBMS Basic Concepts by Pinar Senkul resources: mostly froom Elmasri, Navathe and other books Data Models Data Model: A set of concepts to describe
COMP5426 Parallel and Distributed Computing Distributed Systems: Client/Server and Clusters Client/Server Computing Client Client machines are generally single-user workstations providing a user-friendly
Database and Data Mining Security 1 Threats/Protections to the System 1. External procedures security clearance of personnel password protection controlling application programs Audit 2. Physical environment
Virginia Polytechnic Institute and State University No. 7100 Rev.: 4 Policy and Procedures Date: April 1, 2008 Subject: Administrative Data Management and Access Policy Contents 1. Premise and Purpose...
Introducción a la Programación Web con C# en Visual Studio 2010 Curso: Introduction to Web development Programming in C# with Microsoft Visual Studio 2010 Introduction to Web Development with Microsoft
- Analyzer 2007 Executive Summary Strategy Companion s Analyzer 2007 is enterprise Business Intelligence (BI) software that is designed and engineered to scale to the requirements of large global deployments.
Software Engineering Application Architectures Based on Software Engineering, 7 th Edition by Ian Sommerville Objectives To explain the organization of two fundamental models of business systems - batch
Agile Business Suite: a 4GL environment for.net developers DEVELOPMENT, MAINTENANCE AND DEPLOYMENT OF LARGE, COMPLEX BACK-OFFICE APPLICATIONS In order to ease the burden of application lifecycle management,
Business-Driven Software Engineering Lecture 3 Foundations of Processes Jochen Küster firstname.lastname@example.org Agenda Introduction and Background Process Modeling Foundations Activities and Process Models Summary
What is Data Virtualization? by Rick F. van der Lans, R20/Consultancy August 2011 Introduction Data virtualization is receiving more and more attention in the IT industry, especially from those interested
An ESRI White Paper May 2007 Mobile GIS for Homeland Security ESRI 380 New York St., Redlands, CA 92373-8100 USA TEL 909-793-2853 FAX 909-793-5953 E-MAIL email@example.com WEB www.esri.com Copyright 2007 ESRI
CMPT-354-Han-95.3 Lecture Notes September 10, 1995 Chapter 1 Introduction 1.0 Database Management Systems 1. A database management system èdbmsè, or simply a database system èdbsè, consists of æ A collection
4D and SQL Server: Powerful Flexibility OVERVIEW MS SQL Server has become a standard in many parts of corporate America. It can manage large volumes of data and integrates well with other products from
Product Data Sheet BEA AquaLogic Integrator Agile integration for the Enterprise Build, Connect, Re-use BEA AquaLogic Integrator delivers the best way for IT to integrate, deploy, connect and manage process-driven
TECHNICAL SPECIFICATION Draft v0.5 (For Public Review) A move to drive industry standardization of SOA concepts and terminology http://www.middlewareresearch.com The Middleware Company Research Team Steve
Chapter 3 Database Architectures and the Web Transparencies Database Environment - Objectives The meaning of the client server architecture and the advantages of this type of architecture for a DBMS. The
INFORMATION TECHNOLOGY Hynomics (formerly HyBrithms Corporation, formerly Sagent Corporation) Technology to Control Hybrid Computer Systems Businesses and industries, both large and small, increasingly
Service Virtualization: Managing Change in a Service-Oriented Architecture Abstract Load balancers, name servers (for example, Domain Name System [DNS]), and stock brokerage services are examples of virtual
Software Action Guide Dana Bredemeyer Bredemeyer Consulting Tel: (812) 335-1653 Fax: (812) 335-1652 Email: firstname.lastname@example.org Web: Why do we care about Software? Because we want to be a dominant player
Mitra Innovation Leverages WSO2's Open Source Middleware to Build BIM Exchange Platform May 2015 Contents 1. Introduction... 3 2. What is BIM... 3 2.1. History of BIM... 3 2.2. Why Implement BIM... 4 2.3.
Base One's Rich Client Architecture Base One provides a unique approach for developing Internet-enabled applications, combining both efficiency and ease of programming through its "Rich Client" architecture.
White Paper on CLOUD COMPUTING INDEX 1. Introduction 2. Features of Cloud Computing 3. Benefits of Cloud computing 4. Service models of Cloud Computing 5. Deployment models of Cloud Computing 6. Examples
COSC 304 Introduction to Systems Introduction Dr. Ramon Lawrence University of British Columbia Okanagan email@example.com What is a database? A database is a collection of logically related data for
Introduction to database management systems Database management systems module Myself: researcher in INRIA Futurs, Ioana.Manolescu@inria.fr The course: follows (part of) the book "", Fourth Edition Abraham
Software Engineering Architectural Design 1 Software architecture The design process for identifying the sub-systems making up a system and the framework for sub-system control and communication is architectural
Internet accessible facilities management A technology overview This overview is an outline of the major components and features of TotalControl, deployment possibilities and a list of terms that describe
Architectures Computing & 2009-11-06 Architectures Computing & SERVICE-ORIENTED COMPUTING (SOC) A new computing paradigm revolving around the concept of software as a service Assumes that entire systems
MANUFACTURING AND PROCESS CONTROL 293 WORKFLOW MANAGEMENT - FROM CHAOS TO SYNERGY Robert T. Leskovar, József Györkös, Ivan Rozman University of Maribor Faculty of Electrical Engineering and Computer Science;
Tik-109/110.300 Telecommunications architectures: Network management Hannu H. KARI/Helsinki University of Technology (HUT) TML-laboratory/CS/HUT Tik-109/110.300 Fall 2000 Hannu H. Kari Page 1 Agenda Telecom
SDN Architecture Overview Version 1.1 November, 2014 ONF TR-504 ONF Document Type: TR ONF Document Name: TR_SDN ARCH Overview 1.1 11112014 Disclaimer THIS SPECIFICATION IS PROVIDED AS IS WITH NO WARRANTIES
Chapter 1: Introduction Purpose of Database Systems View of Data Data Models Data Definition Language Data Manipulation Language Transaction Management Storage Management Database Administrator Database
Data governance is a means to define the policies, standards, and data management services to be employed by the organization. Information Management & Data Governance OVERVIEW A thorough Data Governance
Jini Kurzfassung als Kapitel für die Vorlesung Verteilte Systeme Friedemann Mattern (unter Nutzung von Teilen von Andreas Zeidler und Roger Kehr) Jini Infrastructure ( middleware ) for dynamic, cooperative,
Master Reference Data: Extract Value from your Most Common Data White Paper Table of Contents Introduction... 3 So What?!? Why align Reference Data?... 4 MDM Makes MDM Better... 5 Synchronize, Integrate
The EMSX Platform A Modular, Scalable, Efficient, Adaptable Platform to Manage Multi-technology Networks A White Paper November 2002 Abstract: The EMSX Platform is a set of components that together provide
Chapter 1: Introduction Database System Concepts, 5th Ed. See www.db book.com for conditions on re use Chapter 1: Introduction Purpose of Database Systems View of Data Database Languages Relational Databases
CACHÉ: FLEXIBLE, HIGH-PERFORMANCE PERSISTENCE FOR JAVA APPLICATIONS A technical white paper by: InterSystems Corporation Introduction Java is indisputably one of the workhorse technologies for application
s Design Chapter 1: Introduction Departamento de Engenharia Informática Instituto Superior Técnico 1 st Semester 2008/2009 Slides (fortemente) baseados nos slides oficiais do livro c Silberschatz, Korth
Messaging Solutions IT Solutions White Paper #1 on enterprise messaging First in a series on enterprise messaging and building corporate information services. IT Solutions I N F O R M A T I O N T E C H
The Availability Forum Specification for High Availability Middleware Timo Jokiaho, Fred Herrmann, Dave Penkler, Manfred Reitenspiess, Louise Moser Availability Forum Timo.Jokiaho@nokia.com, Frederic.Herrmann@sun.com,
Building a virtual marketplace for software development tasks Boris Kötting & Frank Maurer University of Kaiserlautern & University of Calgary firstname.lastname@example.org & email@example.com Abstract
Object Oriented Databases OOAD Fall 2012 Arjun Gopalakrishna Bhavya Udayashankar Executive Summary The presentation on Object Oriented Databases gives a basic introduction to the concepts governing OODBs
Gastcollege BPM Definition of SOA Services architecture is a specific approach of organizing the business and its IT support to reduce cost, deliver faster & better and leverage the value of IT. November
Concepts of Database Management Seventh Edition Chapter 7 DBMS Functions Objectives Introduce the functions, or services, provided by a DBMS Describe how a DBMS handles updating and retrieving data Examine
Introduction to CORBA 1. Introduction 2. Distributed Systems: Notions 3. Middleware 4. CORBA Architecture 1. Introduction CORBA is defined by the OMG The OMG: -Founded in 1989 by eight companies as a non-profit
WHIT EP AP ER Apex Code: The World s First On-Demand Programming Language Contents Extending the Power of the Apex Platform... 1 Multi-tenancy and Programming Languages... 1 Apex Code Design and Syntax...