System Architecture with XML (The Morgan Kaufmann Series in Software Engineering and Programming)
Format: PDF / Kindle (mobi) / ePub
XML is bringing together some fairly disparate groups into a new cultural clash: document developers trying to understand what a transaction is, database analysts getting upset because the relational model doesn't fit anymore, and web designers having to deal with schemata and rule based transformations. The key to rising above the confusion is to understand the different semantic structures that lie beneath the standards of XML, and how to model the semantics to achieve the goals of the organization.
A pure architecture of XML doesn't exist yet, and it may never exist as the underlying technologies are so diverse. Still, the key to understanding how to build the new web infrastructure for electronic business lies in understanding the landscape of these new standards.
If your background is in document processing, this book will show how you can use conceptual modeling to model business scenarios consisting of business objects, relationships, processes, and transactions in a document-centric way. Database designers will learn if XML is subject to relational normalization and how this fits in with the hierarchical structure of XML documents. Web designers will discover that XML puts them into a position to automatically generate visually pleasing web pages and rich multimedia shows from otherwise dry product catalogues by using XSLT and other transformation tools. Business architects will see how XML can help them to define applications that can be quickly adapted the ever changing requirements of the market.
“marriage with Mary” becomes a property of John. “marriage with” is the name of the property, and “Mary” is the value. Note that this statement does not tell us anything about Mary! It is a statement about John. To make this relationship bidirectional we would have to issue an additional statement “Mary has marriage with John”. These are more or less the basics of RDF. Simple, easy to understand, and very powerful. Before we discuss some advanced features, let us summarize the basic concepts and
only for part of the cardinality mandatory (1,1), (1,m), optional (0,n) constraints but not for (0,1) and (0,1), (0,m) (1,m) constraints. constraint concept. Mutual exclusion constraint Not supported in original ERM Possible via the Alt construct User−defined constraints Not supported in ERM Possible through extension mechanism MetaModel (stereotypes) Not supported in ERM RDF allows making statements about anything, including RDFS definitions. RDF and UML are fairly equivalent when it comes to
event if there are 162 alternative outcomes of an action. The result event of one action usually serves as the starting event for the next one, or result events of several actions are somehow connected to start an action. Alternative paths (i.e., mutually exclusive paths) and parallel paths through this kind of event−action−chaining net are distinguishable only by the kind of “connectors” (with propositional logic semantics) at path branches or junctions. Well−known examples are event−driven
changes. Change management is a structured procedure for performing all necessary organizational transformations that keep an enterprise competitive. Usually short−term changes are considered that are supposed to meet current client demands, technological innovations, political or economic circumstances, and so on. Long−term changes Additionally we may also consider long−term changes that influence “long transactions,” using an IT−related term. As an example, we can think of a process that
us in so many different ways at the various stages in the writing of this book. First we would like to thank Morgan Kaufmann Publishers and dpunkt.verlag for giving us the opportunity to publish our work. It has been a great pleasure, indeed, to work with the people at MKP and dpunkt. Thanks go especially to Tim Cox and Stacie Pierce from Morgan Kaufmann, who patiently helped us through the materialization and publication of the book and had to put up with our slightly Teutonic English, and to