Resumen
This article focuses on the bottom-up design approach used for software development. As top-down design approaches give database designers little guidance with transforming a conceptual model into an active object-oriented database schema. A bottom-up design approach may provide a better perspective. Using this approach to Active Object-Oriented Databases (AOODB) two subtasks are needed, specifying application classes, and identifying business policies, which are generally spread over different classes. This approach enhance sequential message passing, so interactions are specifiable in a concurrent object-oriented (OO) environment based on multiple threads of control. Although such interaction mechanisms are built-in primitives in some concurrent OO systems, they must usually be defined by programmers. Two interaction rule patterns are, the abstraction from a single application-specific rule to a primitive rule pattern, and a composite rule pattern abstracting from more than one rule. To successfully apply rule patterns, they must include a proper design and development tool.