Abstract

This chapter provides an introduction to unified modeling language (UML) in the form of a complete case study. The case study concerns a simple model of a bank and its offering of two different types of account. The case study is a vehicle to examine key elements of UML notation. Nearly all object-oriented design methods now incorporate “use case models” to represent requirements. A use case model could comprise a number of use case diagrams and a number of other diagrams and text-based pieces of documentation. A number of common approaches to describing use cases and use case diagrams are summarized. The UML diagrams described in the chapter represent the core of notation that a typical modeler needs. A simple text-based analysis technique called the “noun clause” analysis is suggested, which can help the modeler to make a start with the class modeling activity. By following a fairly simple set of steps one can begin to determine a number of candidate classes and objects. Some key information is provided about the use of class, responsibility, and collaboration (CRC) cards to explore use cases and classes information box. The two types of interaction diagrams—the “sequence diagram” and the “collaboration diagram”—that are supported by the UML are described in brief. An example of the “activity diagram” is given. The UML standard suggests an application of variations of the core notation to model business processes, with existing UML diagrams being applied to model a different view of the business. This is summarized in the “application of core UML diagrams to business modeling” information box.

Full Text
Published version (Free)

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call