The UML can be used to describe the complete development of relational and object relational
from business requirements through the physical data model. However, modeling of the
physical data model must express a detailed description of the database. This is done using Rational’s
Data Modeling Profile for the UML2
All geographic information systems (GIS) are built
using formal models that describe how things are
located in space. A formal model is an abstract and
well-defined system of concepts. It defines the
vocabulary that we can use to describe and reason
about things. A geographic data model defines the
vocabulary for describing and reasoning about the
things that are located on the earth. Geographic data
models serve as the foundation on which all
geographic information systems are built.
We are all familiar with one model for geographic
Chapter 3 - Data modeling. After reading this chapter, you should be able to: Understand the purpose of structure models, understand and apply the building blocks for UML class (structure) diagrams, describe multiplicities for a UML class diagram, understand how to implement a relational database from a UML class diagram, describe business rules and the various forms of rules.
Chapter 7 - Entity-relationship model. This chapter provides an overview of the database-design process, with major emphasis on database design using the entity-relationship data model. The entity-relationship data model provides a high-level view of the issues in database design, and of the problems that we encounter in capturing the semantics of realistic applications within the constraints of a data model. UML class-diagram notation is also covered in this chapter.
The Class Model in the UML is the
main artefact produced to represent the
logical structure of a software system.
It captures the both the data
requirements and the behaviour of
objects within the model domain. The
techniques for discovering and
elaborating that model are outside the
scope of this article, so we will assume
the existence of a well designed class
model that requires mapping onto a
The class is the basic logical entity in
the UML. It defines both the data and
the behaviour of a structural unit.
Chapter 8 - System models. This chapter include objectives: To explain why the context of a system should be modelled as part of the re process, to describe behavioural modelling, data modelling and object modelling, to introduce some of the notations used in the Unified Modeling Language (UML), to show how CASE workbenches support system modelling.
Functional and flexible, this guide takes an objects-first approach to Java programming and problem using games and puzzles. Updated to cover Java version 1.5 features, such as generic types, enumerated types, and the Scanner class. Offers independent introductions to both a command-line interface and a graphical user interface (GUI). Features coverage of Unified Modeling Language (UML), the industry-standard, object-oriented design tool. Illustrates key aspects of Java with a collection of game and puzzle examples. Instructor and Student resources available online.