Using Information Modeling to Define Business Requirements

  • Mark A. Shafer
Part of the The Springer International Series in Engineering and Computer Science book series (SECS, volume 523)


For the most part, developing business requirements is still treated as an art as opposed to a science. The concept of using the rigor and precision necessarily associated to code with the process of defining business requirements is not widely known or accepted. In a few instances atUSAA, we have attempted to use our limited knowledge of Information Modeling to achieve that goal and make explicit all of the information necessary to develop systems that satisfy the business requirements. This document describes a small instance.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. [FS97]
    M. Fowler, K. Scott. UML Distilled, Applyingthe Standard Object Modeling Language. Addison-Wesley, 1997.Google Scholar
  2. [KA97]
    H. Kilov, A. Ash. How to ask questions: Handling complexity in a business specification. In: Proceedings of the OOPSLA’ 97 Workshop on object-oriented behavioral semantics (Atlanta, October 6th, 1997), ed. by H. Kilov, B. Rumpe, I. Simmonds, Munich University of Technology, TUM-19737, pp.99–114.Google Scholar
  3. [KR94]
    H. Kilov, J. Ross, Information Modeling: an Object-oriented Approach. Prentice-Hall, 1994.Google Scholar
  4. [KS96]
    H. Kilov, I. Simmonds. How to correctly refine business specifications, and know it. In: Proceedings of the Fifth Workshop on Specification of Behavioral Semantics (at OOPSLA’ 96), ed. by H. Kilov and V.J. Harvey, Robert Morris College, 1996, pp. 57–69.Google Scholar

Copyright information

© Springer Science+Business Media New York 1999

Authors and Affiliations

  • Mark A. Shafer
    • 1
  1. 1.United Services Automobile AssociationGermany

Personalised recommendations