A Chemical Informatics Domain Analysis Object Model

A Chemical Informatics Domain Analysis Object Model [Pg.61]

Use case specifications document functional requirements. The next step is to design the partial system that the current iteration is supposed to deliver. The gap between requirements and design is not trivial, and a bridge between the two is desired. This bridge is what object-oriented analysis is about. The domain analysis object model is not the final design. However, it provides a starting point for the design process. [Pg.61]

A domain object model is a model that describes key domain concepts and their relationships. Many of these concepts come from tangible objects in the real world of the problem domain. In the chemical informatics space, these are the objects that chemists are dealing with on a daily basis, such as compounds, structures, notebooks, and libraries. The domain analysis model being presented here focuses on those objects that are involved in the compound registration process. [Pg.61]

One technique that can help you to capture domain objects is to look for nouns in the use case specifications—those terms in bold in UC1 of Chapter 9. The following are the key domain objects from UC1. [Pg.61]

Developing Chemical Information Systems An Object-Oriented Approach Using Enterprise Java, by Fan Li Copyright 2007 John Wiley Sons, Inc. [Pg.61]

Big Chemical Encyclopedia