 |
GetTextbooks.co.uk
Compare Prices & Save up to 90% |
|
|
|
| Login | Sign up | My Wish List |
 | | Object Database Development: Concepts and Principles by David W. Embley ISBN-10: 9780201258295 ISBN-10: 0-201-25829-3 ISBN-13: 9780201258295 ISBN-13: 978-0-201-25829-5 Hardcover 1997-09 Addison-Wesley Find Lowest Price |
Editorials | ||
Book Description Object-oriented database development is one of the best ways to build software for many advanced applications. In this book Professor Embley shows how to model an application and systematically transform an application model into code for a database system. Aimed at both university students and sophisticated practicing professionals, Object Database Development presents the fundamental concepts and principles needed for developing advanced database applications, and it shows how to apply these principles successfully. This book emphasizes application development for object-relational, object-oriented, and active databases as well as for relational databases, making it suitable for both introductory and advanced courses on database application development. FEATURES Takes an object-oriented approach to modeling and developing database applications. Provides a seamless way to move from analysis through specification and design into implementation. Focuses on concepts and principles that provide a sound theoretical foundation for database application development. Presents several case studies (Oracle, UniSQL, O2, ObjectStore, and Ode), that show how to turn theory into practice. | ||
Reviews | ||
Intelligent Book About OSM (Object Oriented System Model) First I like this book. It is intelligent and sound. Well done in every respect. Just a WARNING: the title is somewhat misleading. The focus is on the OSM model and design methodology. The database examples at the end are treated only in an extremely thin way. This book is strongly routed in theory with a keen eye on practical requirements. Even some original research of the author is first published here. OSM is a true alternative to the methodologies commonly used. Also the notation shows a true perspective from outside UML. It helps prevent you from stopping to think what UML can't express. Too bad, there is no tool supporting OSM. | ||