Object-Oriented System Design
John E. Gessford · Journal of Database Management · 1992
The reason for a different approach to systems analysis and designed is explained in cases where an objectoriented approach is to be taken to application programming. The paradigm of the object-oriented approach is shown to be a generalization of the paradigm used in the traditional approach to application software design. A new object-oriented approach to systems analysis and design is defined and illustrated. The design of an accounts receivable system is used to illustrate the methodology. The object-oriented approach described divides the work into three phases. In the first phase, the application is defined in terms of the entity types and relationships to be included in the system. In the second phase, the business objects to be simulated are identified and categorized as permanent, event, or dependent business objects. In the third phase, the program modules for each business object are specified. A message flow diagramming technique is defined and illustrated that has proven useful in specifying the programs required for business event object classes. The need is pointed out for action diagrams to define processing logic for customized program modules if a CASE tool is to be used to generate the code. The fact that this approach does not use data flow diagrams is noted. Message flow diagrams take the place of data flow diagrams in providing an overview of the system.Request access from your librarian to read this article's full text.