Atomic Use Case: A Concept for Precise Modelling of Object-Oriented Information Systems
- 360 Downloads
We propose the concept of “atomic use case” and demonstrate how this concept can be used to bring the analysis of functional requirements of information systems to a much deeper level than usual, and ultimately to construct a precise specification of the system’s functionality. Specifically, the complete functionality of an information system is defined by a set of atomic use cases, which are consistently specified in terms of their input, output, pre- and postcondition.
We also show that the usefulness of the atomic use case concept goes beyond analysis. With this concept, a characterization of the business logic layer can be clearly formulated, and this layer can be systematically extended to effectively support the construction of graphical user interface.
KeywordsObject oriented analysis object-oriented modeling object-oriented information systems object database formal notation Object-Z prototyping user interface
Unable to display preview. Download preview PDF.
- 1.D’Souza, D., Wills, A.: Objects, Components, and Frameworks with UML – the Catalysis Approach. Addison-Wesley, Reading (1999)Google Scholar
- 2.Duke, R., Rose, G.: Formal Object Oriented Specification Using Object-Z. Macmillan, UK (2000)Google Scholar
- 3.Embley, D.: Object Database Development: Concepts and Principles. Addison-Wesley, Reading (1998)Google Scholar
- 5.Nguyen, K.: A Semi-formal Object-Oriented Method for the Analysis and Modelling of the Functional Requirements of Information Systems, Ph.D. Thesis, La Trobe University, Melbourne, Australia (2002)Google Scholar
- 6.Quatrani, T.: Visual Modeling with Rational Rose 2000 and UML. Addison-Wesley, Reading (2000)Google Scholar