| |
| |
| |
| Systems Architecture | |
| |
| |
| Introduction | |
| |
| |
| |
| Object-Oriented Data Integration: Running Several Generations of Database Technology in Parallel | |
| |
| |
| Abstract | |
| |
| |
| Introduction | |
| |
| |
| Integration Frame | |
| |
| |
| Programmer's View | |
| |
| |
| Layered Model | |
| |
| |
| Object Layer | |
| |
| |
| Tuple Interface | |
| |
| |
| Some Performance Considerations | |
| |
| |
| Further Reading | |
| |
| |
| Product Categories | |
| |
| |
| Remote Database Access Products | |
| |
| |
| Objectified Relational Databases | |
| |
| |
| Federated Databases | |
| |
| |
| Object-Oriented Databases with Relational Gateways | |
| |
| |
| Object-Oriented Access Layers | |
| |
| |
| Object-Relational Databases | |
| |
| |
| Case Study: Persistent Objects in a Large Bank | |
| |
| |
| Situation, Requirements and Software Environment | |
| |
| |
| Why Products Failed in 1995. Our Architecture | |
| |
| |
| Experiences and Summary | |
| |
| |
| References | |
| |
| |
| |
| An Access Layer for Object Databases: Experience Report | |
| |
| |
| Abstract | |
| |
| |
| A Database Access Layer for ODBMS? | |
| |
| |
| The Architecture | |
| |
| |
| Database | |
| |
| |
| Transactions | |
| |
| |
| Error Management | |
| |
| |
| Interface to the Application Kernel | |
| |
| |
| Filters and Iterators | |
| |
| |
| Referencing Transient Objects | |
| |
| |
| Software Production Environment | |
| |
| |
| Experiences and Summary | |
| |
| |
| References | |
| |
| |
| |
| A Use of the EndGame Design Strategy | |
| |
| |
| Abstract | |
| |
| |
| Introduction | |
| |
| |
| Teaching Our Newcomers a Design Style | |
| |
| |
| Design a Persistent Account Class | |
| |
| |
| The Simple Problem | |
| |
| |
| The Harder Problem | |
| |
| |
| The EndGame Design Technique ("squeegee") | |
| |
| |
| Application of the EndGame Strategy | |
| |
| |
| Move 0: Problem SetupIdentify the Possible Area of Containment | |
| |
| |
| Move 1: Secure the End-Client's Interface | |
| |
| |
| Move 2: Secure the Workstation Object's Internal Design | |
| |
| |
| Move 3: Secure the Distribution Service | |
| |
| |
| Move 4: Secure the Server's Internal Design | |
| |
| |
| Results of Applying the EndGame Technique | |
| |
| |
| How Would One Decide It Is Time to Try EndGame? Comparison of EndGame with Other Design Strategies | |
| |
| |
| Summary | |
| |
| |
| References | |
| |
| |
| |
| Building a Push-Based Information System Using an Active Database | |
| |
| |
| Abstract | |
| |
| |
| Introduction | |
| |
| |
| Related Work | |
| |
| |
| Design Rationale | |
| |
| |
| Predicate Maintained Collections | |
| |
| |
| Using Predicate Maintained Collections | |
| |
| |
| An Example | |
| |
| |
| Experiences and Summary | |
| |
| |
| Problems | |
| |
| |
| Future Work | |
| |
| |
| References | |
| |
| |
| |
| Applications And Design | |
| |
| |
| Introduction | |
| |
| |
| |
| Flight-Simulator Database: Object-Oriented Design and Implementation | |
| |
| |
| Abstract | |
| |
| |
| Introduction | |
| |
| |
| Why Object-Oriented Flight Simulator Technology? Computing Infrastructure | |
| |
| |
| Complex Objects: Airplane Model | |
| |
| |
| Type Constructors: Airport Model | |
| |
| |
| Polymorphism and Covariance | |
| |
| |
| Control System Modeling | |
| |
| |
| Behavioral Modeling: Aerodynamics | |
| |
| |
| Queries | |
| |
| |
| Persistence and Dynamic Binding | |
| |
| |
| Constraints and Triggers | |
| |
| |
| Analysis | |
| |
| |
| Experiences and Summary | |
| |
| |
| References | |
| |
| |
| |
| An Object-Oriented Image Database For Biomedical Research | |
| |
| |
| Abstract | |
| |
| |
| Problems to be Solved | |
| |
| |
| Image Boss System Overview | |
| |
| |
| Software and Hardware | |
| |
| |
| Various Applications and Tools Implemented | |
| |
| |
| Image Boss Design | |
| |
| |
| Data Abstraction | |
| |
| |
| Class Hierarchy | |
| |
| |
| Future Design Plans | |
| |
| |
| Justification For Selecting OODB | |
| |
| |
| Problems Encountered | |
| |
| |
| Integration of Other Tools | |
| |
| |
| Archiving | |
| |
| |
| Filename Translation | |
| |
| |
| Locking | |
| |
| |
| Queries | |
| |
| |
| Server Crashes | |
| |
| |
| Primary Applications of Image Database | |
| |
| |
| Conclusions | |
| |
| |
| References | |
| |
| |
| |
| The OSEF (Object-Oriented Software Engineering Flow) Framework | |
| |
| |
| Abstract | |
| |
| |
| OSEF Architecture | |
| |
| |
| General Criteria | |
| |
| |
| Software Development Method | |
| |
| |
| Bought Components | |
| |
| |
| CASE Tool | |
| |
| |
| Database Management System | |
| |
| |
| Source Code Administration Tool | |
| |
| |
| Debugging and Tuning Tools | |
| |
| |
| GUI Builder | |
| |
| |
| Built Components | |
| |
| |
| Framework Class Library | |
| |
| |
| Rational Rose Metaschema Model | |
| |
| |
| Perl Filters and Preprocessors | |
| |
| |
| OSEF Runtime Kernel and Application Control Interface | |
| |
| |
| The Development Cycle | |
| |
| |
| Step A: Modeling | |
| |
| |
| Step B: Implementation | |
| |
| |
| Rational Rose C++. Diagrams | |
| |
| |
| Exportation/Importation of Items | |
| |
| |
| Code Generation Property Sets | |
| |
| |
| Preserved Code Regions | |
| |
| |
| Tool Evaluation | |
| |
| |
| Release History | |
| |
| |
| Objectivity DB. Data Definition Language | |
| |
| |
| Storage Classes | |
| |
| |
| References and Handles | |
| |
| |
| Iterators | |
| |
| |
| Associations | |
| |
| |
| Variable-Size Arrays | |
| |
| |
| Physical Clustering of Objects | |
| |
| |
| Indexes | |
| |
| |
| Transactions and Locking | |