Skip to main content Accessibility help
×
Hostname: page-component-78c5997874-mlc7c Total loading time: 0 Render date: 2024-11-10T05:35:52.851Z Has data issue: false hasContentIssue false

CHAPTER 2 - OBJECT-ORIENTED DATA MANAGEMENT

Published online by Cambridge University Press:  06 July 2010

Ari Jaaksi
Affiliation:
Nokia Telecommunications
Juha-Markus Aalto
Affiliation:
Nokia Telecommunications
Ari Aalto
Affiliation:
Nokia Telecommunications
Kimmo Vättö
Affiliation:
Nokia Telecommunications
Get access

Summary

It is hardly possible to imagine real-life information systems that would not need to store the information they manipulate onto some persistent storage media. Practically all applications need to either share common data with each other or store information on disk to make the data accessible—even when the application that created the data no longer exists. Just think about the variety of management information systems that support the value chains of every company: sales and marketing support systems, planning systems, manufacturing support systems, process automation, and so on. Good data management is the key to creating useful applications. The novel application areas such as multimedia and video-on-demand are setting requirements that are even more demanding for storing and manipulating complex data.

It is justified to say that succeeding with data management is by far one of the most critical aspects in modern software development, be it based on the object paradigm or not. However, it has been somewhat surprising to notice that object-oriented data management solutions have been poorly covered in the plethora of textbooks, articles, and magazines written to describe objectoriented software engineering.

During the last few years, we have looked into a number of unsuccessful object-oriented software projects. Some of the reasons for failure appear to relate to data management solutions. Failed development efforts seem to fall into three categories:

  • Lip Service Projects: These are projects where the phrase object-orientation has been used to give the project a credible and fashionable flavor. In these cases, practical deeds and object-oriented software development ideology do not necessarily meet at all.

  • […]

Type
Chapter
Information
Tried and True Object Development
Industry-Proven Approaches with UML
, pp. 107 - 184
Publisher: Cambridge University Press
Print publication year: 1998

Access options

Get access to the full version of this content by using one of the access options below. (Log in options will check for institutional or personal access. Content may require purchase if you do not have access.)

Save book to Kindle

To save this book to your Kindle, first ensure [email protected] is added to your Approved Personal Document E-mail List under your Personal Document Settings on the Manage Your Content and Devices page of your Amazon account. Then enter the ‘name’ part of your Kindle email address below. Find out more about saving to your Kindle.

Note you can select to save to either the @free.kindle.com or @kindle.com variations. ‘@free.kindle.com’ emails are free but can only be saved to your device when it is connected to wi-fi. ‘@kindle.com’ emails can be delivered even when you are not connected to wi-fi, but note that service fees apply.

Find out more about the Kindle Personal Document Service.

Available formats
×

Save book to Dropbox

To save content items to your account, please confirm that you agree to abide by our usage policies. If this is the first time you use this feature, you will be asked to authorise Cambridge Core to connect with your account. Find out more about saving content to Dropbox.

Available formats
×

Save book to Google Drive

To save content items to your account, please confirm that you agree to abide by our usage policies. If this is the first time you use this feature, you will be asked to authorise Cambridge Core to connect with your account. Find out more about saving content to Google Drive.

Available formats
×