You might have seen the recent news reports about the collision between U.S. and Russian communication satellites. The U.S. satellite was one of the Iridium satellites. What wasn’t reported and you probably don’t know is that an object database management system (ODBMS) is an important part of the Iridium system. Even though ODBMSs are a [...]
February 13, 2009
I am now also posting on the Cutter Blog. My initial posting is (The Acronym) SOA is (Perhaps) Dead (at Some Companies); Long Live Services. It is a response to Anne Thomas Manes’ SOA is Dead; Long Live Services on her blog at the Burton Group.
January 9, 2009
The typical definition of an atomic task or process is one that cannot be decomposed further. This is vague and subject to interpretation. The Decomposition Matrix on this site uses a specific definition: A task (for business process diagrams) or a process (for data flow diagrams) is atomic if every input relates to every output [...]
December 3, 2008
My last posting referenced the criteria for a well-formed business process diagram mentioned in Business Process Driven SOA using BPMN and BPEL by Matjaz B. Juric and Kapil Pant. I am going to expand on their criteria to create a more comprehensive definition of a well-formed business process diagram.
To start, here are three criteria from [...]
November 18, 2008
I recently received two new books on business process modeling. Both books looked interesting because they had great titles. As it turns out, one book is great and the other not so good.
The not so good book is Business Process Driven SOA using BPMN and BPEL by Matjaz B. Juric and Kapil Pant. There are [...]
October 9, 2008
The Design Decomposition Blog is written by Doug Barry.
Unlike the object model, the traditional relational model does not support many-to-many relationships. In this XML model for example, a cardigan sweater (men's, size medium) could refer to many color swatches. Inversely, a given color swatch could refer to many different types of sweaters of various sizes. This is a many-to-many relationship.
In the relational model, these relationships are represented using intersection entities.
This figure illustrates the schema with the intersection entity of Size Color.
These intersection entities, if they are left in the model in this way, will require additional joins that slow down the mapping process to the XML model. One approach to this situation is to "de-normalize" these intersection entities by restricting the number of colors that a catalog item can have. The outcome of such an approach might be to increase maintenance costs; the model no longer accurately represents the real world, which might require a change in the future. Data changes such as these can also have ripple effects on the code.
There are nearly 400 pages of articles on this site with over 50 pages on object-oriented database management systems.
Search this site for more articles
Custom Search
Browse this site for more articles
Click on the topics below to browse the articles on this site. You can see more detail by clicking on the arrows. This highlights the location of the current
article: More on many-to-many relationships.
Related recent articles from Google News
Facebook Scores A Win In Patent Lawsuit DaniWeb (blog) The tool uses one or both of a relational and object database engine that facilitates at least many-to-many relationships among data elements. ... and more » 29 Jul 2010 at 1:10pm
Control Microsystems Releases ClearSCADA 2010 Water and Wastewater In addition to standard features such as object-oriented database, scalable client/server architecture optimized for wide area networks and integrated ... and more » 19 Jul 2010 at 11:42am
GIS Does Serviceability, Monitoring Cable360.net GE Smallworld is an object-oriented database that natively handles complex network topology, said Baker. The MSO has a fully connected topology from ... and more » 19 Jul 2010 at 10:46am
Intersystems Ensemble integrated into Calif. healthcare network CMIO ... to Ensemble for SHC began with integrating clinical applications to the hospital's EpicCare EMR system; built on the InterSystems Cache object database. ... 14 Jul 2010 at 11:26am
The Object Data Standard: ODMG 3.0 (The Morgan Kaufmann Series in Data Management Systems) by R. G. Cattell, Douglas K. Barry, Mark Berler, Jeff Eastman, David Jordan, Craig Russell, Olaf Schadow, Torsten Stanienda, Fernando Velez Average Customer Review: based on 2 reviews. Customer Review: A well-written, concise reference covering a diverse range of topics that will be of interest to all who know the frustration of cramming complex OO systems into relational tables. From a complete design pattern for Object and Object Relational database systems, to design patterns for declarative language symantics; from C++ and Java...
Object-Oriented Database Design Clearly Explained by Jan L. Harrington Average Customer Review: based on 7 reviews. Customer Review: "Object Oriented Database Design" is a book for beginners and, as far as I have been able to investigate, it is a perfect walkthrough along the background of object structures. Figures, exemples, syntax of codes and clear explanations lead the learner through theory towards practice. Exemples are often very nice.
Data Access Patterns: Database Interactions in Object-Oriented Applications by Clifton Nock Average Customer Review: based on 7 reviews. Customer Review: I have to disagree with the previous review. I will try to explain why I think 'b88zhou' review is inadequate after presenting my overview of this book. After reading numerous pattern books, it is nice to see a pattern book with very good organization. Each pattern is presented with the following subsections. * Description * Context ...
based on 2 reviews.
based on 7 reviews.
