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.
Because an ODBMS stores exactly the same object model that is used at the
application level, both development and maintenance costs can be reduced. With
an ODBMS, there is no need to:
Develop two data models: an object model in the
application and a relational model stored in the database. This is not
needed because an ODBMS uses the same object model as the application.
Maintain two data models. An ODBMS eliminates the
maintenance cost of keeping the to data models synchronized.
Develop mapping between the relational and the object
models. This is not needed because an ODBMS uses the same object model
as the application.
Maintain the mapping between the relational and object
models. An ODBMS eliminates the maintenance cost of maintaining the
mapping whenever there is a change to the object or relational model.
The result is that for a development team of six to seven, it is possible to
have a team with one less person when using an ODBMS. It is typical when
developing an object application with a RDBMS that one person is in charge of
keeping the relational model synchronized with an object model and the mapping
code. That person would not be needed in an ODBMS development project.
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: One model to reduce development and maintenance costs.
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.
