UML and Data Modeling A Reconciliation First Edition David C. Hay

Visit ebookfinal.com to download the full version and
explore more ebooks or textbooks
UML and Data Modeling A Reconciliation First
Edition David C. Hay
_____ Click the link below to download _____
https://ebookfinal.com/download/uml-and-data-modeling-a-
reconciliation-first-edition-david-c-hay/
Explore and download more ebooks or textbook at ebookfinal.com

Here are some recommended products that we believe you will be
interested in. You can click the link to download.
Modeling Survival Data Using Frailty Models 1st Edition
David D. Hanagal
https://ebookfinal.com/download/modeling-survival-data-using-frailty-
models-1st-edition-david-d-hanagal/
Exploring Data Tables Trends and Shapes David C. Hoaglin
https://ebookfinal.com/download/exploring-data-tables-trends-and-
shapes-david-c-hoaglin/
Advanced Standard SQL Dynamic Structured Data Modeling and
Hierarchical Processing Michael M. David
https://ebookfinal.com/download/advanced-standard-sql-dynamic-
structured-data-modeling-and-hierarchical-processing-michael-m-david/
Turbulence Modeling for CFD Third Edition David C. Wilcox
https://ebookfinal.com/download/turbulence-modeling-for-cfd-third-
edition-david-c-wilcox/

The object primer Agile Modeling driven development with
UML 2 3rd ed Edition Ambler
https://ebookfinal.com/download/the-object-primer-agile-modeling-
driven-development-with-uml-2-3rd-ed-edition-ambler/
Atmospheric modeling data assimilation and predictability
1st Edition Eugenia Kalnay
https://ebookfinal.com/download/atmospheric-modeling-data-
assimilation-and-predictability-1st-edition-eugenia-kalnay/
Modeling Count Data 1st Edition Joseph M. Hilbe
https://ebookfinal.com/download/modeling-count-data-1st-edition-
joseph-m-hilbe/
Modeling and Verification Using UML Statecharts A Working
Guide to Reactive System Design Runtime Monitoring and
Execution based Model Checking 1st Edition Doron Drusinsky
https://ebookfinal.com/download/modeling-and-verification-using-uml-
statecharts-a-working-guide-to-reactive-system-design-runtime-
monitoring-and-execution-based-model-checking-1st-edition-doron-
drusinsky/
Hierarchical Modeling and Analysis for Spatial Data 1st
Edition Sudipto Banerjee
https://ebookfinal.com/download/hierarchical-modeling-and-analysis-
for-spatial-data-1st-edition-sudipto-banerjee/

UML and Data Modeling A Reconciliation First Edition
David C. Hay Digital Instant Download
Author(s): David C. Hay
ISBN(s): 9781935504191, 1935504193
Edition: First
File Details: PDF, 4.53 MB
Year: 2011
Language: english

UML & Data
Modeling:
A Reconciliation
David C. Hay
Foreword by Sridhar Iyengar

Published by:
Technics Publications, LLC
966 Woodmere Drive
Westfield, NJ 07090 U.S.A.
www.technicspub.com
Edited by Carol Lehn
Cover design by Mark Brye
Cover Origami:
Designed by Tomako Fusé
Folded by David C. Hay
Photographed by Włodzimersz Kurniewicz
All rights reserved. No part of this book may be reproduced or
transmitted in any form or by any means, electronic or mechanical,
including photocopying, recording or by any information storage and
retrieval system, without written permission from the publisher, except
for the inclusion of brief quotations in a review.
The author and publisher have taken care in the preparation of this book,
but make no expressed or implied warranty of any kind and assume no
responsibility for errors or omissions. No liability is assumed for
incidental or consequential damages in connection with or arising out of
the use of the information or programs contained herein.
All trade and product names are trademarks, registered trademarks, or
service marks of their respective companies, and are the property of their
respective holders and should be treated as such.
This book is printed on acid-free paper.
Copyright © 2011 by David C. Hay
ISBN, print ed. 978-1-9355041-9-1
Printing ( 4 5 6 7 8 9)
Library of Congress Control Number: 2011938560
ATTENTION SCHOOLS AND BUSINESSES: Technics Publications
books are available at quantity discounts with bulk purchase for
educational, business, or sales promotional use. For information, please
write to Technics Publications, 966 Woodmere Drive, Westfield, NJ
07090, or email Steve Hoberman, President of Technics Publications, at
me@stevehoberman.com.

Dedicated in memory of my college roommate and
life-long friend:
Mark Rumsey MacHogan
1947-2010

Table of Contents
Foreword 1
Preface 3
Acknowledgements 7
Chapter 1: Introductions 9
The Structure of the Book 9
Observations 10
Introduction for Data Modelers 10
Introduction for UML Modelers 15
Combined Introduction 18
Historical Threads 18
Architectural Framework 19
Views of the Business 20
Views of Technology 20
Business Owner’s View 22
Architect’s View 23
Designer’s View 24
Summary 24
Chapter 2: UML and Essential Data Models 27
Impedance Mismatch 27
Architecture vs. Object-oriented Design 31
Limiting Objects to Business Objects 31
Behavior 32
Relationships and Associations 34
Entity/Relationship Predicates 36
Specifying Role Names in UML 39
A Fundamental Change to UML 41
One Solution: Stereotypes 46
Second Solution: Conversion 46
Domains, Data Types, and Enumerations 48
Namespaces 52
Object Oriented Design vs. Relational Database Design 52
Persistent Data 52
Inheritance 53
Security 54
Summary 55

Chapter 3: How to Draw an Essential Data Model in UML 57
Summary of the Approach 57
1. Show Domain-Specific Entity Cases Only 59
2. Use Symbols Selectively 60
Use Appropriate Symbols 60
Class (Entity Class) 60
Attribute 62
Association (Relationship) 63
Cardinality 65
Exclusive or (XOR) Constraint 67
Use Some UML-specific Symbols with Care 68
Entity Class Sup-types and Relationship Sub-types 69
<<Enumeration>> 71
Derived Attributes 72
Package 74
Add One Symbol 75
Do Not Use Any Other Symbols 79
3. Define Domains 82
4. Understand “Namespaces” 84
5. Follow Display Conventions 85
Name Formats 85
Role Positions 85
“Exclusive or” Relationship Constraint 86
Cardinality Display 86
Summary 86
Chapter 4: Aesthetic guidelines and Best Practices 89
Introduction – Aesthetic Considerations 89
Place Sub-types Inside Super-types 91
Condensed Entity/Relationship Approach 91
The UML (and that of some entity/relationship notations) Approach 92
One Problem 95
Solution 95
Constraints 95
Categories 97
Eliminate Bent Lines 98
Orient “Many” End of Relationships to Top and Left 101
Presentation 102
Summary 104

Chapter 5: An Example: Party 107
Parties 109
Party Relationships 111
Party Identifiers and Names 113
Constraints 120
Summary 123
Appendix A: A Brief Summary of The Approach 125
Appendix B: A History of Modeling Objects and Data 127
Data Processing 128
Early Programming Languages 129
Object-oriented Programming Languages 130
Structured Techniques 131
Structured Programming 131
Structured Design 132
Data Architecture 133
Early Data Modeling 133
CODASYL 133
Dr. Edward Codd (1970) 134
Early Relational Databases 135
Three Schema Architecture (1972) 136
Dr. Peter Chen (1976) 138
Business Analysis 141
Structured Analysis 141
Business Process Reengineering 142
Later Data Modeling 144
Richard Barker and Harry Ellis (1980) 148
IDEF1X 149
Object-Role Modeling (ORM) 150
About Discipline in Data Modeling 151
Data Model Patterns 151
David Hay (1995) 151
Len Silverston, Kent Graziano, Bill Inmon (1997) 152
Architecture Frameworks 152
John Zachman (1979) 152
David Hay (2003, 2006) 153
Business Rules 154
Ron Ross (1987) 155
Business Rule Group (1995) 155
Object Management Group (2008) 156
Data Management 156

Object-oriented Development 157
Early Object Modeling 157
Shlaer & Mellor (1988) 157
Coad and Yourdon (1990) 159
Rumbaugh, et. al. (1991) 161
Embley/Kurtz/Woodfield (1992) 164
Booch (1994) 166
Object Patterns 167
Design Patterns 167
Martin Fowler – Analysis Patterns 167
UML 168
The Internet and the Semantic Web 169
Computer Time-sharing 170
ARPANET 171
The Internet 174
The World Wide Web 177
The Semantic Web 182
Summary – The “Reconciliation” 187
Glossary 191
Bibliography 223
Index 231

1
Foreword
By Sridhar Iyengar
I had the interesting experience of initially meeting David Hay in the late
1990s a couple of years after Unified Modeling Language (UML) became
an Object Management Group (OMG) standard. I was giving a talk at
the DAMA Data Warehouse Conference on the topic of modeling and
metadata management using UML and a related standard at OMG called
the Meta Object Facility (MOF). The audience was interested to learn
about UML but somewhat skeptical because the use of Peter Chen’s E/R
modeling notation was well known and established in the data modeling
community. There was one particular attendee (you guessed right - it
was David!) who was a little more vocal than the rest and challenged me
when I asserted that UML and its notation was not just for object
modelers but could also help data modelers. I thoroughly enjoyed the
debate but confess I was a bit irritated because the flow of my talk was
interrupted a bit!
What followed back and forth at this conference and again in a couple of
follow on conferences was an indication of how widespread the
‘impedance mismatch’ was that existed between the community of data
modelers/data architects and object modelers/object architects. There
were several debates during talks and also after talks during cocktails on
this clash of data/object modelers and I challenged the audience to be
more open minded about UML in part because there was a lot more to
UML than just simple structural modeling of objects.
I was extremely pleased to see David join the effort at OMG in
establishing a new Information modeling and Metadata Management
standard. David was determined to do something that others had tried
but given up too soon. He really wanted to bridge the data modeling and
object/UML modeling community not just by using the UML notation in
a superficial manner, but also by addressing concerns that data architects
and data modelers actually faced in their daily work – concerns about
structure and semantics, as well as notation and methodology familiar to
data modelers. I have followed the debates on OMG mailing lists where
David over the years has earned the respect of his object modeling
colleagues (he clearly already did this in the data modeling community

2 UML and Data Modeling: A Reconciliation
years ago) and ultimately influenced the standard and along the way
finished this much needed book – a practical handbook.
David has pulled off the impossible – balancing the need to keep the
notation familiar enough to data modelers but acknowledge the audience
already familiar with UML – and explaining not just the notation, but also
the best practices in data modeling as he leads the reader using practical
and simple to understand examples. In that sense, David is ‘with the
reader’ in his/her journey to use the UML notation (with or without
UML tools) effectively for data modeling and architecture. The author’s
experience, pragmatism and a community building expertise are well
demonstrated in this book. He has even included a historical background
of the two communities involved. (We are both showing our years of
experience and gray hair!)
This book comes at a time when data modelers, object modelers and
semantic web modelers are all beginning to realize the value of modeling
and architecture. My hope is that this book brings those communities
together, because in this world of big data and deep analytics, and the
need to understand both structured and unstructured data – attention to
design and architecture is key to building resilient data intensive systems
for the mobile and connected world. We are realizing more and more
that the value we derive is not just from the programs that run on various
devices and servers, but from the underlying data. The better we
understand the data, the more we can gain from the designing, using and
analyzing internet scale data systems.
David – You have done it! Thanks for taking on the this very important
work of bridging data modelers and UML modelers, extending the state
of the art and for writing about this important notation and technique
that will guide data modelers for years to come.
I hope you learn and gain as much from reading this book as I did.
Enjoy!
Sridhar Iyengar, an IBM Distinguished Engineer, serves on the OMG Board of
Directors and is working on the development and integration of Architecture, Business
and IT Modeling standards. He leads the technical strategy for Software Tools &
Methods Research at the IBM TJ Watson Research Center. Sridhar is also a member
of the IBM Software Group Architecture Board Steering Committee helping drive
software tools direction across IBM.

3
Preface
Since Leibniz there has perhaps been no man who has had
a full command of all the intellectual activity of his day. Since
that time, science has been increasingly the task of
specialists, in fields which show a tendency to grow
progressively narrower. A century ago there may have been
no Leibniz, but there was a Gauss, a Faraday, and a Darwin.
Today there are few scholars who can call themselves
mathematicians or physicists or biologists without restriction.
A man may be a topologist or an acoustician or a
coleopterist. He will be filled with the jargon of his field, and
will know all its literature and all its ramifications, but, more
frequently than not, he will regard the next subject as
something belonging to his colleague three doors down the
corridor, and will consider any interest in it on his own part
as an unwarrantable breach of privacy.
- Norbert Wiener, Cybernetics; 1948.
1
This book is about two “camps” in the information management world
that each represent large bodies of specialized knowledge. Those in each
camp suffer from the specialization phenomenon described above by Dr.
Wiener. Each seems to be seriously unenlightened about the other.
Data modeling or object modeling? Whose side are you on? Why are
there sides? What’s going on here?
After a decade of various people’s trying to represent data structures
graphically, the entity/relationship version of the data model was
formalized in 1976,2
and variations on it have followed. The Unified
1
Norbert Wiener. 1948, 1961. Cybernetics: of Control and Communication in
the Animal and the Machine, second edition. (Cambridge, MA, The MIT
Press). 2.
2
Peter Chen. 1977. “The Entity-Relationship Approach to Logical
Data Base Design”. The Q.E.D. Monograph Series: Data
Management. Wellesley, MA: Q.E.D. Information Sciences, Inc. This
is based on his article, “The Entity-Relationship Model: Towards a

Modeling Language (UML) was officially released a little over twenty
years later, in 1997.3
Its adherents claim that UML’s “Class Model” is the
rightful successor to the data model. Others are not convinced.
The fact of the matter is that the intellectual underpinnings and the
orientation of UML’s object-oriented model are very different from
those of the data modelers’ entity/relationship model. There appears to
be a kind of intellectual “impedance mismatch” between the two
approaches.
This is partially technological, as object-oriented programmers
attempt to save persistent object data in relational databases—which have
significantly different structures from them.4
It’s also a cultural mismatch,
however, coming from significant differences in world views about
systems development.5
UML, after all, was originally intended to support
object-oriented design, while data (entity/relationship) modeling was
intended to support the analysis of business structures. These are very
different things.
Unified View of Data”, ACM Transactions on Database Systems,
Vol. 1, No. 1, (March 1976), pages 9-36.
3
Object Management Group (OMG). 1997. “UML Specification
version 1.1”. (OMG document ad/97-08-11). Published at
http://www.omg.org/cgi-bin/doc?ad/97-08-11.

The analogy is derived from electrical engineering, where the term
“impedance matching” refers to the use of a transformer to make the
load (impedance) required on a target device (such as a loudspeaker)
match the load produced on a source device (such as an amplifier).
This is described in (among other places): American Radio Relay
League, 1958. The Radio Amateur’s Handbook: The Standard Manual of
Amateur Radio Communication. (Concord, New Hampshire: The
Rumford Press).
4
Ted Neward. 2006. “The Vietnam of Computer Science”, The Blog
Ride: Ted Neward’s Technical Blog. June 26, 2006. Retrieved from
http://blogs.tedneward.com/2006/06/26/The+Vietnam+Of+Com
puter+Science.aspx, 7/10/2011.
5
Scot Ambler. 2009 “The Cultural Impedance Mismatch”, The Data
Administration Newsletter. August 1, 2009. Available at:
http://www.tdan.com/view-articles/11066.

Preface 5
In 1960, my father observed that up until about 1949, he knew
everything there was to know about radio technology. Never again would
he be able to say that.
In 1969, when I began my career in information technology, the body of
knowledge I looked forward to mastering seemed pretty formidable. I
had learned Fortran in college, but now I would have to master Basic and
COBOL. And then there was IBM’s Job Control Language, which was
required if I was to use the operating system. This was too much!
Little did I know…
What ultimately happened was that a very large proportion of what is to
be known now in this industry concerns things that did not exist in 1969.
Each of the two “camps” being alluded to in this book is responsible for
a profoundly huge body of relatively new knowledge. Each body of
knowledge and its associated disciplines have come into existence only in
the last 40 years—but each is immense. Maintaining mastery of either is
sufficiently challenging that it is easy to ignore those in other—even
adjacent—disciplines.
Moreover, the interaction of the two disciplines has also followed Dr.
Wiener’s prediction:
“These specialized fields are continually growing and invading new
territory. The result is like what occurred when the Oregon country was
being invaded simultaneously by the United States settlers, the British,
the Mexicans, and the Russians—an inextricable tangle of exploration,
nomenclature, and laws.”6
We all, however, ignore those adjacent disciplines at our peril. It
behooves data modelers to learn enough about object-oriented design to
understand the implications of the assertions made in their models. It
would also benefit object-oriented designers to understand enough about
the challenges of data and database administration to be able to make
sense out of the data-oriented specifications (and problems) they have to
respond to.
More significantly, both groups are encouraged at least to understand the
differences between their worlds if they are to fully understand how
business requirements can become system requirements.
6
Norbert Wiener. 1948, 1961. Op. cit. 2.

Oh, and did I mention that the Semantic Web is lurking out there? You
understand, don’t you, that this is an entirely new body of knowledge–that
will change everything yet again.
The assignment today is to try to reconcile the object-oriented and the
data groups. On the one hand, it is for data modelers to learn how to use
a new technique–a sub-set of the UML notation–to produce the
business-oriented entity/relationship models they know. On the other
hand, it is for object-oriented UML modelers to improve their knowledge
of a technique they already know, in order to expand their understanding
just what a data model could be. Moreover, after reading this book, both
groups should have a better understanding of just what makes a “good”
business data model.
David C. Hay
Houston, Texas

7
Acknowledgements
After 20 years as a data modeling bigot, and 5 of those being UML’s
worst critic, I must thank Dagna Gaythorpe and DAMA International
for signing me up to work with the Object Management Group, in order
to work with them on the Information Metadata Model (IMM). I must
admit that I felt a little like a KGB agent in the CIA the first time I
attended an OMG meeting, but all were most friendly and helpful, so the
experience turned out to be profound and extremely valuable.
This of course leads me to offer my true thanks to the OMG IMM team
for finally forcing me to really understand what UML is all about, and
why it is like it is.
In particular, I want to thank Jim Logan, Ken Hussey, and Pete Rivet for
helping me come to grips with the different thought processes that are
behind UML. Learning a new language––especially when it means
learning a new culture and a new way of looking at the world––is
difficult, and I really appreciate their patience.
I only hope that I have represented that point of view fairly.
My gratitude also goes to my mentors in the data modeling world:
Richard Barker, Cliff Longman, and Mike Lynott. They are the ones who
introduced me to the conceptual (“semantic”) way of looking at the
world. Meeting them as an adult finally showed me what I wanted to do
when I grew up.
In particular, Mike has put in a great deal of effort editing and helping to
shape this book.
Thanks also to Bob Seiner, publisher of The Data Administration Newsletter,
for publishing a series of four articles in 2008, “UML as a Data Modeling
Notation”. These articles served as the seeds for this book.
Much appreciation goes to the people who read the manuscript and
provided useful comments and suggestions: Roland Berg, Harry Ellis,
William Frank, Allan Kolber, Kent Graziano, Frank Palmeri, and Russell
Searle.
Thanks also must go to my Publisher, Steve Hoberman and Editor Carol
Lehn-Dodson for helping put this whole work together.

And as always, my greatest appreciation goes to my wife, Jola for her
patience, and to my children Bob and Pamela for their inspiration.

9
Chapter 1:
Introductions
This book has two audiences:
 Data modelers (both analysts and database designers) who are
convinced that UML has nothing to do with them; and
 UML experts who don’t realize that architectural data modeling
really is different from object modeling (and that the differences
are important).
Your author’s objective is to finally bring these groups together in peace.
The easy part of the book (for all audiences) is to understand the
notation required for this joint approach. More difficult is the change in
attitude required in each case. The objective here is to become successful
architectural entity/relationship modelers—who happen to use the UML
notation. The idea is to provide all modelers with guidance on how to
produce a high quality entity/relationship model to describe the
underlying data architecture for an organization. The notation we will be
using happens to be the Unified Modeling Language Class Diagram.
The Structure of the Book
This book is in four parts:
 Chapter One: Introductions – Separate Introductions for data
modelers and UML modelers, along with an introduction for all.
 Chapter Two: UML and Architectural Models – A detailed
description of the underlying issues between UML Class notation
and conceptual entity/relationship models.
 Chapter Three: How to Draw a Data Model in UML – A
systematic description of the steps and best practices for making
the entity/relationship model using (a slightly modified version
of) the UML notation. Specifically, how to create a model to be a
powerful tool, to support both the definition of requirements and
the systems development process overall.

 Chapter Four: An Example – An excerpt of the model presented
in the companion book to this one. This shows both the
mechanics of using UML, as well as demonstrating best practices
for presentation.
 Appendix A – A brief summary of the approach.
 Appendix B – A history of modeling in the information
technology industry, including the divergent paths that led to the
current impasse.
This chapter contains three introductions: one directed to each of the
communities involved, followed by one describing the nature of the
issues that have traditionally separated the two groups. This third
introduction, for both audiences, includes a bit of history, plus a
description of an architectural framework to put the various points of
view in context.
All of this is in preparation for the heart of the effort: how to use a
modified version of the Unified Modeling Language (UML) to produce
an effective business-oriented conceptual entity/relationship model.
Observations
Before proceeding, three observations should be kept in mind:
 There are better and worse data modelers.
 There are better and worse UML modelers.
 Neither “community” is as homogeneous as the previous
paragraphs would suggest.
Introduction for Data Modelers
Premise: A class model in UML is not the same thing as an
entity/relationship model.
The Unified Modeling Language (UML) began as a collection of
elements to support object-oriented design. It was derived from an
assortment of existing approaches and, as a result, it is not a single
notation. Rather, it is an array of notations for modeling elements as
diverse as classes, behaviors, events, and others.
By the time object (class) models appeared in the early 1990s, the use of
models to support the discovery of system requirements for business was

Introductions 11
already highly developed. Both data flow diagrams and entity/relationship
data models were nearly 20 years old. Modeling in that context (whether it
was data flows, processes, events, or data structures) clearly distinguished
between modeling the nature of the business and modeling the systems
that would support that business.
Then, in 1990, Peter Coad and Edward Yourdon coined the term
“object-oriented analysis” to describe a merging of the “semantic data
modeling” approach (as they described entity/relationship modeling)
with object-oriented programming concepts such as services and
messages.7
They claimed that semantic data modeling did not provide
adequately for inheritance, and asserted that classification structure and
assembly structure were not adequately treated.
In their view, object-
oriented analysis would address both of these shortcomings.
To their credit, they still viewed the assignment as one of addressing the
problem space (the business) rather than the solution space (the
computer and its programs). To them an “object” was “an encapsulation
of Attributes and exclusive Services; an abstraction of something in the
problem space, with some number of instances in the problem space.”
(Emphasis added.)8
Unfortunately, over the successive years, the connections with the
problem space became more distant. By the time UML came into
existence, the aspect of analyzing the world outside the computer appears
to have been lost.
In 1999, the “three amigos” of UML (James Rumbaugh, Ivar Jacobson,
and Grady Booch), defined an object as a “discrete entity with a well-
defined boundary and identity that encapsulates state and behavior; an
instance of a class”.9
A class, in turn, is “the descriptor for a set of
7
Peter Coad and Edward Yourdon. 1990. Object-Oriented Analysis
(Englewood Cliffs, NJ: Yourdon Press).

As it happens, they were wrong on both counts. Semantic data
modeling does account for inheritance through sub-types and super-
types. And classification and assembly structures can be represented
as well.
8
Ibid. page 31.
9
James Rumbaugh, Ivar Jacobson, and Grady Booch. 1999. The
Unified Modeling Language Reference Manual. Reading, Massachusetts:
Addison-Wesley. 30.

Discovering Diverse Content Through
Random Scribd Documents

here has not stuck close to his text. M. heterophyllum is very distinct from
either, is a free growing species, and flowers from June to September, the
blossom open early in the morning, and shut in the afternoon. It is
propagated both by seeds and parting the roots. The fruit is divided into eight
loculaments for the seed, separated longitudinally by double elastic
partitions, which are reflected above, so that the edges come in contact
together and cover the seeds. Eight elastic valves attached to the margin of
the fruit, and adhering firmly to the part containing the seeds, and to one
another until mature, again enclose these. Two cartilaginous coloured bodies,
jointed near the base, and arising from the outer edge of the partitions, are
prominent upon the interior of each of those valves, which have their edges
always more or less reflected to facilitate the entrance of moisture to the
seeds, above which they continue to lie close so long as the atmosphere
continues dry: but, when it rains, or water is poured upon them, it enters by
the openings between the valves, and is imbibed by the receptacles of the
seeds and cartilaginous partitions, which presently become much dilated,
and the diameter of the fruit is considerably increased. The upper valves also
by this extension are drawn outwards, and being pressed at the same time by
the edges of the partitions, resting against the elastic rigid bodies on their
interior surface, gradually rise to be perpendicular upon the margin, when
the fruit somewhat resembles a little cup with a Vandyke edge; but this is of
short duration, as the less elastic and hygrometrical exterior of the valves
(for their interior parts imbibe water and dilate rapidly) soon draws them
backwards into the form of a star or polypetalous flower, with colours as
vivid as if really vegetating. The edges of the partitions now become more
erect, leaving the seeds uncovered; and the water being led towards the
centre by channels in the valves, and retained by an elevated margin, the
seeds are floated out of their cells. The fruit when dry, again contracts as
before, and the experiment may be repeated ad libitum. What a wonderful
œconomy of Nature to produce the seeds just at the moment proper for their
germination, and preventing them until that time from falling on the parched
sands and rocks upon which those plants vegetate! In some plants, natives of
cold regions, where seeds are in danger of perishing by moisture, and there
is seldom sufficient warmth for their vegetation, an œconomy the direct
reverse takes place. The cones of pines, being most hygrometrical externally,
close firmly in moisture, and expand only in dry heat! The singular qualities
of the fruits of Mesembryanthema, we find first mentioned by Dillenius—

see his Hortus Elthamensis, vol. ii. p. 237. It has since been noticed by Dr.
Sims, who has described the fruit M. pinnatifidum in the Medical Journal
for 1799, and also by Mr. Konig in the Annals of Botany, but we believe no
elucidation of the phenomenon has been given before. Dr. Hagen, a German,
who possessed the fruits of three species without knowing what they were,
imagined they were the whole plants, and described them as a new and
extraordinary reviviscent genus in Cryptogamia. Others have taken them for
the Rose of Jericho, which is not a fruit, but a plant. The fruits of most
Mesembryanthema exhibit the same metamorphosis, but with great variety.
M. hispidum has the upper valves double, the inner membrane beautifully
transparent. The fruit of this perfectly ripened, if put into tepid water, will fly
open as if with a spring. We have made experiments with the fruits of M.
latum, scalpratum, cordatum, and pugioniforme, all of which are very fine.
Our specimen is from the collection of A. B. Lambert, esq.

PLATE DXLI.
P R OT E A CONI F E RA.
Cone-bearing Protea.
CLASS IV. ORDER I.
TETRANDRIA MONOGYNIA. Four Chives. One Pointal.
ESSENTIAL GENERIC CHARACTER.
Corolla 4-fida, seu 4-petala. Antheræ lineares, petalis infra apices insertæ.
Calyx proprius, nullus. Semina solitaria.
Blossom four-cleft, or of four petals. Tips linear, inserted into the petals below
the points. Cup proper, none. Seeds solitary.
SPECIFIC CHARACTER.
Protea foliis acinaciformibus, glabris, callosis: floribus in capitulis
terminalibus, pallide luteis: involucro patente, late lanceolato, concolore.
Protea with scimitar-shaped leaves, smooth and hard. Flowers grow in
terminal heads of a pale yellow colour: the involucrum is spreading, broadly
lance-shaped, and the same colour as the blossoms.
REFERENCE TO THE PLATE.
1. A flower.
2. A chive magnified.
3. Seed-bud and pointal, summit magnified.
Our figure represents part of a plant in the collection of G. Hibbert, esq.
in the year 1803, and the smaller specimen a branch from the same plant in
1807. So considerable a latitude of growth is certainly deserving notice, as,
upon a slight examination, they might easily be mistaken for distinct species.
In the first year of its inflorescence its appearance is uninteresting; but in a
year or two afterwards it displays such an abundance of bloom, that it then
becomes a very ornamental little shrub. It is a Cape species, and requires no
particular treatment more than what is common to the generality of this
extensive family.

PLATE DXLII.
R UE L L I A I NF UNDI BUL I F ORMI S .
Funnel-flowered Ruellia.
CLASS IV. ORDER I.
Calyx 5-partitus. Corolla monopetala, limbo 5-lobo, inæquali. Stamina
biconjugata. Stylus filiformis. Stigma bifidum. Capsula dissepimentis
dentatis, elasticis, dehiscentibus. Semina pauca.
Empalement 5-parted. Blossom one petal: border 5-lobed, unequal. Chives by
pairs. Shaft thread-shaped. Summit two-cleft. Capsule with the partitions
toothed, elastic, and splitting. Seeds few.
SPECIFIC CHARACTER.
Ruellia foliis oppositis, alternis, lanceolatis, undulatis, costatis, lucidis:
floribus in spicis terminalibus, confertis. Corolla infundibuliformis: laciniis
limbi quinquefidis, crenatis, patentibus, rugosis, coccineis, ad basin luteis.
Ruellia with opposite alternate leaves, lance-shaped, waved, ribbed, and
shining. Flowers grow in terminal spikes, crowded together. Blossom funnel-
shaped: segments of the border five-cleft and notched, spreading, wrinkled,
of a scarlet colour, and yellow at the base.
1. The empalement.
2. A blossom spread open.
3. Seed-bud and pointal.
Few of the small plants that adorn the stove are superior in beauty to this
elegant little shrub, whose successive bloom continues from June till
January. It is the Justicia infundibuliformis of Linnæus, but must, according
to his own system, be removed to the class Tetrandria. We have seen it in
many collections in great luxuriance. It is a native of the East Indies, and
was introduced by the Right Hon. C. Greville, four or five years ago. As yet,

we believe, it has not perfected its seed with us, but propagates freely by
cuttings.

PLATE DXLIII.
P R OT E A S P E CI OS A PAT E NS .
Spreading Showy Protea.
CLASS IV. ORDER I.
SPECIFIC CHARACTER.
Protea foliis lanceolatis, undulatis, pilosis: squamis calycinis rotundato-
ovatis, marginibus fimbriatis nigricantibus. Caulis patens.
Habitat in Caput Bonæ Spei.
Protea with lance-shaped leaves, waved and hairy. Scales of the empalement
roundedly oval, with fringed margins of a black brown colour. Stem
spreading.
Native of the Cape of Good Hope.
1. A flower, one tip magnified.
This fine fringed Protea in the foliage is very nearly allied to the P.
speciosa, but the flower is more spread open than any of that section we
have as yet seen. It is naturally so averse to grow upright, that it is with
difficulty prevented from bending downwards, which the branches always
do till they are tied up. In this particular it very much resembles the P.
repens, and, if left at liberty, would no doubt, like that species, creep or
spread itself about on the earth. Our figure was made from a plant lately in
the conservatory of G. H. Hibbert, esq., but recently consigned to J. Knight,

his botanic gardener, who has commenced nurseryman in the King’s Road,
Chelsea, with the whole of that well known valuable collection.

PLATE DXLIV.
MI MOS A P UDI CA.
Bashful Mimosa.
CLASS XXIII. ORDER I.
POLYGAMIA MONŒCIA. Various Dispositions upon one Plant.
Hermaph. Calyx 5-dentatus. Corolla 5-fida. Stamina 5, sive plura. Pistillum 1.
Legumen.
Mascul. Calyx 5-dentatus. Corolla 5-fida. Stamina 4, 5, 10, sive plura.
Hermaph. Empalement 5-toothed. Blossom five-cleft. Chives 5, or more.
Pointal 1. A pod.
Male. Empalement 5-toothed. Blossom 5-cleft. Chives 4, 5, 10, or more.
SPECIFIC CHARACTER.
Mimosa foliis sensitivis palmato-pinnatis, pinnulis, multijugis. Caulis pilosus,
aculeis paucis instructus. Petioli et pedunculi pilosi. Fructus echinatus.
Habitat in Brasiliâ.
Mimosa with sensitive leaves palmately winged, the pinnulæ many-paired.
Stem hairy, and furnished with a few prickles. Petioles and peduncles hairy.
Fruit prickly.
Native of the Brazils.
1. A flower.
3. Seed-bud and pointal magnified.
4. The ripe capsule, with a seed detached.
Five distinct genera were once included under the generic title of
Mimosa, but separated by Willdenow into 102 Acacias, 58 Ingas, 9
Desmanthuses, 3 Shrankias, and 32 Mimosas. This susceptible species of
Mimosa is an old inhabitant of the stove, and well known to cultivators by
the appellation of the Sensitive Plant (but not to be confounded with the M.

sensitiva, a very different species). Although this Mimosa is neither new nor
rare, it is nevertheless very interesting, and has not hitherto made its
appearance in any modern publication; nor is there any coloured figure of it
extant. Our representation of it, therefore, is in part a novelty, however old
and familiar the plant itself may be. According to the observations of
Linnæus, it opens or expands its foliage at three in the morning, and closes it
about six in the evening. Its singular quality of shrinking from the touch is
supposed to be owing to its being strongly saturated with oxygen gas, which
it disengages upon the slightest provocation, and its place for a short time is
supplied by the atmospheric air; which retiring, the leaves again resume their
former appearance, and so remain expanded till the evening, unless disturbed
by design or accident; for the rude approach of the common air disorganises
its foliage.
The leaf is mostly composed of four divisions, but sometimes five and six
may be found in plants of a luxuriant growth. Each division is supplied with
numerous little leaflets, in pairs of an oblong form, with a small yellow
gland at their base, which when carefully touched will close up separately,
and leave the surrounding leaflets undisturbed. It may be considered either
as an annual or a biennial, dying after ripening its seeds. Our drawing was
made from fine plants in the collection of J. Vere, esq.

PLATE DXLV.
P R OT E A AB ROTANI F OL I A, odorata .
Sweet-scented Southernwood-leaved Protea.
CLASS IV. ORDER I.
SPECIFIC CHARACTER.
Protea foliis multifidis, filiformibus, acutis, pilosis: floribus in capitulis
terminalibus, lucidis, odoratis.
Habitat in Caput Bonæ Spei.
Protea with many-cleft leaves, thread-shaped, pointed, and hairy: flowers
grow in terminal heads, shining, and sweet-scented.
Native of the Cape of Good Hope.
1. A flower, one tip magnified.
2. Seed-bud and pointal.
This species of Protea well deserves a place in any collection, as, in
addition to its light and graceful appearance, it is possessed of a most
agreeable fragrance. There is a variation of it with white flowers, but exactly
the same in every other particular. It remains a considerable time in bloom,
but not many umbels of flowers are expanded at the same time. We have
seen it in several collections. It is a Cape species, and appears to be of easy
culture.

PLATE DXLVI.
MONARDA P UNCTATA.
Dotted-flowered Monarda.
CLASS II. ORDER I.
DIANDRIA MONOGYNIA. Two Chives. One Pointal.
Calyx tubulosus, quinque-dentatus. Corolla ringens, labio superiore lineari,
filamenta involvente.
Empalement tubular, five-toothed. Blossom gaping: the upper lip linear, and
enfolding the threads.
SPECIFIC CHARACTER.
Monarda foliis lanceolatis, dentatis, minutè punctatis: floribus verticillatis,
flavis, rubro punctatis: foliis involucri ovato-lanceolatis, glabris, incarnatis.
Habitat in Americâ Boreali.
Monarda with lance-shaped leaves, toothed, and minutely dotted. Flowers
grow in whorls, are of a yellow colour, and dotted with red: the involucrate
leaves are ovately lance-shaped, smooth, and flesh-coloured.
Native of North America.
1. A flower.
2. A blossom spread open, one tip magnified.
4. Seed-bud magnified.
The only figure of the Monarda punctata we have seen is an uncoloured
one in Plukenet’s Phytographia. It is a perfectly new species to the garden,
and the only Monarda with yellow flowers at present known. Its specific title
is particularly applicable to its bloom, as all the species yet enumerated are
more or less punctured in the foliage, some so minutely as scarcely to be
perceived without the aid of a magnifier. It is a native of Virginia in North
America, but by whom introduced we have not been able to learn. Our

drawing was made from plants in the nursery of Messrs. Whitley and
Brames, who raised it from seed last year, 1807; but it did not flower till the
latter part of the present summer. It is a hardy perennial, and certainly a
handsome addition to the genus.

PLATE DXLVII.
PAS S I F L ORA P E RF OL I ATA.
Perfoliate-leaved Passion-flower.
CLASS XX. ORDER V.
GYNANDRIA PENTANDRIA. Chives on the Pointal. Five Chives.
Trigyna. Calyx 5-phyllus. Petala 5. Nectarium corona. Bacca pedicellata.
Three Styles. Cup 5-leaved. Petals 5. Honey-cup forming a crown. Berry
standing on a footstalk.
SPECIFIC CHARACTER.
Passiflora foliis bilobis: lobis oblongis, divaricatis, subtus punctatis, glaucis:
laciniis calycinis linearibus.
Habitat in Caribbæis.
Jacquin’s Hort. Schœn. vol. 2. tab. 182.
Passion-flower with leaves two-lobed: lobes oblong and straddling, dotted
beneath, and glaucous: segments of the cup linear.
Native of the Caribbee Islands.
1. A flower spread open.
The most graceful ornament to the hot-stove is the elegant and favourite
genus Passiflora, whose branches meandering against the interior sides of
the building adorn it to the greatest advantage. From a branch of the
Passiflora perfoliata thus situated in the collection of the Countess de Vandes
our drawing was taken. The only coloured figure of it we have seen in the
Hortus Schœnbrunnensis of Jacquin. It flowers in great luxuriance during the
months of July and August.

PLATE DXLVIII.
C UCUMI S DUDAI M.
Sweet-scented Melon.
CLASS XXI. ORDER VIII.
MONŒCIA MONADELPHIA. Chives and Pointals separate. One Brotherhood.
Masculini flores.
Calyx 5-dentatus. Corolla 5-partita. Filamenta 3.
Fœminei flores.
Calyx 5-dentatus. Corolla 5-partita. Pistillum 3-fidum.
Male flowers.
Empalement 5-toothed. Blossom 5-parted. Filaments 3.
Female flowers.
Empalement 5-toothed. Blossom 3-parted. Pointal 3-cleft.
SPECIFIC CHARACTER.
Cucumis foliorum angulis rotundatis, dentatis, bispidis: fructu sphærico,
aurantio, variegato, odoratissimo.
Melon with leaves angular, rounded, toothed, and hispid: fruit spherical, of a
gold colour, variegated, and very sweet-scented.
1. A blossom spread open.
3. Empalement, seed-bud, and pointal.
4. A horizontal section of the fruit.
5. A female flower spread open.
This curious little species of Melon, although no new introduction to the
English gardens, is but rarely met with, yet well deserves a place in every

curious collection for the beauty and fragrance of its fruit; which, when cut
before quite ripe, will continue fragrant nearly a fortnight. It is however only
to be valued for its odour and beauty, the flavour being insipid. It is said to
have been first introduced by Lord Petre, who sent the seeds from Morocco
to Peter Collinson, F.R.S. It is also cultivated in Persia, and a figure of the
fruit taken there is given in Gmelin’s Travels, vol. iii. tab. 49. fig. 6. Its
Hebrew appellation of Dudaim seems to have been bestowed by Linnæus,
from the fantastical idea that it was the fruit mentioned in the Bible by the
name of mandrake, with which Jacob’s neglected wife purchased her
husband’s favours for one night of her rival. Another plant with perennial
roots descending 6 or 8 feet into the earth, was taken be his pupil Hasselquist
(sent to the East on purpose to illustrate the natural history of that country)
for the celebrated Dudaim;—Which is the right one, let critics in Hebrew
decide! The Melo Ægypticus minor of Tournefort, or Ægyptian Abdelavi,
which Linnæus supposed to be the same as the Melo aurantii figura
odoratissimus of Dillenius, and might partly have occasioned the name, is a
very different species. Indeed the claim of our plant to Ægyptian origin
seems doubtful, but we would reluctantly change a name that has been
applied for more than half a century. Our specimens are from the collection
of A. B. Lambert, esq.

Welcome to our website – the ideal destination for book lovers and
knowledge seekers. With a mission to inspire endlessly, we offer a
vast collection of books, ranging from classic literary works to
specialized publications, self-development books, and children's
literature. Each book is a new journey of discovery, expanding
knowledge and enriching the soul of the reade
Our website is not just a platform for buying books, but a bridge
connecting readers to the timeless values of culture and wisdom. With
an elegant, user-friendly interface and an intelligent search system,
we are committed to providing a quick and convenient shopping
experience. Additionally, our special promotions and home delivery
services ensure that you save time and fully enjoy the joy of reading.
Let us accompany you on the journey of exploring knowledge and
personal growth!
ebookfinal.com

UML and Data Modeling A Reconciliation First Edition David C. Hay

More Related Content

Similar to UML and Data Modeling A Reconciliation First Edition David C. Hay (20)

Recently uploaded (20)

UML and Data Modeling A Reconciliation First Edition David C. Hay