![FOOTNOTES:
[143:A] Persons who are known to possess property, are called
upon to pay for seats in the temple. A lady residing in one of the
northern settlements, was cajoled into paying £50 for that
purpose. The good lady, upon arriving in Utah, found that the
famous temple, in which she had purchased a seat, was scarcely
above its foundations.
[147:A] Jour. of Dis., Vol. I. p. 340.
[148:A] Jour. of Dis. Vol. I. p. 202.](https://image.slidesharecdn.com/738786-250516050724-7b62765a/85/Serviceoriented-Modeling-Soa-Service-Analysis-Design-And-Architecture-Michael-Bell-57-320.jpg)
![recognized and honored as such! This announcement created some
consternation among the Mormon theologians, and some of them
had the courage to oppose it. The following is the "Revelator's" own
exposition of this doctrine:—
"When the Virgin Mary conceived the child Jesus, the
Father had begotten him in his own likeness. He was not
begotten by the Holy Ghost. And who is the Father? He is
the first of the human family; and when he took a
tabernacle, it was begotten by his Father in heaven, after
the same manner as the tabernacle of Cain, Abel, and the
rest of the sons and daughters of Adam and Eve. . . . It is
true that the earth was organized by three distinct
characters, namely: Elohim, Yahovah, and Michael,
[Adam;] these three forming a quorum, as in all heavenly
bodies, and in organized element perfectly represented in
the Deity, as Father, Son, and Holy Ghost.
"When our Father Adam came into the garden of Eden,
he came with a celestial body, and brought Eve, one of his
wives, with him. He helped to make and organize this
world. He is Michael, the Archangel, the Ancient of Days.
He is our Father and our God, and the only God with
whom we have to do. . . . Jesus, our elder brother, was
begotten in the flesh by the same character that was in
the garden of Eden, and who is our Father in heaven."
[157:A]
It is manifest that Young is not so much at home in theology as
when engaged in financial schemes and money speculations. So
disgusting and blasphemous are these ideas, and so unacceptable
were they, even to Mormons, who were not prepared to see the
basis of their religion thus rudely overthrown, that Brigham finally
felt compelled to caution the Elders not to preach the new doctrine
concerning Deity, until the people should be better prepared to
receive them.](https://image.slidesharecdn.com/738786-250516050724-7b62765a/85/Serviceoriented-Modeling-Soa-Service-Analysis-Design-And-Architecture-Michael-Bell-62-320.jpg)
![Mahomet is the great exemplar and prototype whom Brigham
Young aims to imitate, and doubtless he took from the Koran his
ideas about the deity of Adam. Thus in chapter two of the Koran, we
have the following:—
"And when we said unto the angels, 'worship Adam,'
they all worshipped him, except Eblis, [Lucifer,] who
refused."
From the following affidavit of John Stiles, father of Judge Stiles,
formerly one of the United States Judges in Utah, a man of much
probity of character, and well known in Salt Lake City as "Father
Stiles," it appears that the blasphemous pretensions of Brigham
Young do not stop with Adam, but that, among the brethren, he has
encouraged a doctrine, which he dare not put in print;—no less than
to arrogate to himself the attributes of Deity.
"Territory of Utah,
Great Salt Lake City.
ss.
"In the spring of 1856," John Stiles says, "I resided in
the 11th Ward of Great Salt Lake City, in the Territory of
Utah. I was appointed by the quorum to which I then
belonged, as a Missionary High-Priest for the said Ward.
My duty was to look after the morals of the people of the
Ward, and especially to see that there was no false
doctrine taught there. I subsequently found that there
were not only immoralities, but also false doctrines among
some of the people, as I supposed at the time. Many
people believed and taught the doctrine, that Brigham
Young was all the God that we were amenable to. I found
by opposing that doctrine, that I gave offence to the
authorities of the Ward, and was consequently called to
answer for my opposition before the Bishop of the Ward,](https://image.slidesharecdn.com/738786-250516050724-7b62765a/85/Serviceoriented-Modeling-Soa-Service-Analysis-Design-And-Architecture-Michael-Bell-63-320.jpg)
![Another doctrine of a startling character, promulgated by one of
Young's counsellors and endorsed by him, is that of human sacrifice
for the remission of sins.
It was first announced by Jedediah M. Grant, Second Counsellor
to the President, in the following language:—
"Brethren and sisters, we want you to repent and
forsake your sins. And you who have committed sins that
cannot be forgiven through baptism, let your blood be
shed, and let the smoke ascend, that the incense thereof
may come up before God as an atonement for your sins,
and that the sinners in Zion may be afraid."[159:A]
Again:—
"We have been trying long enough with this people,
and I go in for letting the sword of the Almighty be
unsheathed, not only in word, but in deed."[159:B]
In accordance with such bloody teaching, it is said that an altar
of sacrifice was actually built by Grant, in the temple block, upon
which these human sacrifices were to be made. On the 21st of
September, 1856, Grant said:—
"I say there are men and women here that I would
advise to go to the President immediately, and ask him to
appoint a committee to attend to their case; and then let
a place be selected, and let that committee shed their
blood."[159:C]
This horrible proposal to immolate upon the altar of sacrifice the
erring saints, was fully endorsed by Brigham Young as follows:—
"There are sins that men commit for which they cannot
receive forgiveness in this world, or in that which is to
come; and if they had their eyes open to see their](https://image.slidesharecdn.com/738786-250516050724-7b62765a/85/Serviceoriented-Modeling-Soa-Service-Analysis-Design-And-Architecture-Michael-Bell-65-320.jpg)
![condition, they would be perfectly willing to have their
blood spilt upon the ground, that the smoke thereof might
ascend to Heaven as an offering for their sins, and the
smoking incense would atone for their sins; whereas, if
such is not the case, they will stick to them, and remain
upon them in the spirit-world.
"I know, when you hear my brethren telling about
cutting people off from the earth, that you consider it is
strong doctrine. It is to save them, not to destroy them. I
will say further, I have had men come to me, and offer
their lives to atone for their sins. It is true that the blood
of the Son of God was shed for sins, through the fall, and
those committed by man, yet men can commit sins which
it can never remit. As it was in ancient days, so it is in our
day; and though the principles are taught publicly from
this stand, still the people do not understand them; yet
the Law is precisely the same. There are sins that can be
atoned for by an offering upon the altar, as in ancient
days, and there are sins that the blood of a lamb, of a
calf, or of turtle-doves cannot remit, but they must be
atoned for by the blood of the man. That is the reason
why men talk to you as they do from this stand. They
understand the doctrine, and throw out a few words about
it."[160:A]
But the greatest change of all in the Mormon religion, made by
Brigham Young, was the introduction and establishment of
polygamy.
This was no part of the Mormon system of religion as originally
established. On the contrary, it was expressly repudiated by all the
Mormon writers and speakers, previous to 1852, and in Europe for
some years afterward.
The Mormon religion was founded by Joseph Smith and his
coadjutors, and the principles and doctrines of the religion were, in](https://image.slidesharecdn.com/738786-250516050724-7b62765a/85/Serviceoriented-Modeling-Soa-Service-Analysis-Design-And-Architecture-Michael-Bell-66-320.jpg)
![the first instance, such as they established. The Book of Mormon is
the historical foundation, corresponding with the Old Testament of
the Christian Bible. Afterward, a volume of revelations to Smith and
others was collected and published, called the Book of Doctrine and
Covenants. This corresponds to the Christian's New Testament. It
may be safely asserted, therefore, that previous to the innovations
of Young, the Mormon religion was embodied in these two volumes.
Their authority in the church is universal and unquestioned.
Let us examine these volumes, and see whether they teach or
countenance polygamy.
The Book of Mormon nowhere contains a word in favor of it. On
the contrary all of its principal characters were monogamists. Such
was Lehi, the patriarch of Mormon history. Such also were Ishmael
and Nephi.[161:A] That the people of Zarahemla were monogamists,
is evident from what is said concerning them on page 146.
But we are not left to inference as to the testimony of this
volume concerning this practice. On page 119 we have the
following:—
"Behold the Lamanites, your brethren, whom ye hate
because of their filthiness and the cursings which hath
come upon their skins, are more righteous than you; for
they have not forgotten the commandment of the Lord,
which was given unto our fathers, that they should have,
save it were one wife; and concubines they should have
none; and there should not be whoredoms committed
among them. And now, this commandment they observe
to keep; wherefore, because of this observance, in
keeping this commandment, the Lord God will not destroy
them, but will be merciful unto them; and one day they
shall become a blessed people."[161:B]
Again:—](https://image.slidesharecdn.com/738786-250516050724-7b62765a/85/Serviceoriented-Modeling-Soa-Service-Analysis-Design-And-Architecture-Michael-Bell-67-320.jpg)
!["And it came to pass that Riplakish did not do that
which was right in the sight of the Lord, for he did have
many wives and concubines, and did lay that upon men's
shoulders which was grievous to be borne; yea, he did tax
them with heavy taxes; and with the taxes he did build
many spacious buildings."[162:A]
And again:—
"And he [Noah] did not walk in the ways of his father.
[Zeniff.] For behold, he did not keep the commandments
of God, but he did walk after the desires of his own heart.
And he had many wives and concubines. And he did cause
his people to commit sin, and to do that which was
abominable in the sight of the Lord. Yea, and they did
commit whoredoms and all manner of wickedness. And he
laid a tax of one fifth part of all they possessed." . . . "All
this did he take to support himself, and his wives and his
concubines; and also his priests, and their wives and their
concubines; thus he had changed the affairs of the
kingdom."[162:B]
"And it came to pass that he placed his heart upon his
riches, and he spent his time in riotous living, with his
wives and his concubines; and so did also his priests
spend their time with harlots."[162:C]
As if to place this matter beyond any question, we have the
following still more explicit testimony, on pages 115 and 118:—
"And now it came to pass that the people of Nephi,
under the reign of the second king, began to grow hard in
their hearts and indulge themselves somewhat in wicked
practices, such as like unto David of old, desiring many
wives and concubines, and also Solomon his son." . . .](https://image.slidesharecdn.com/738786-250516050724-7b62765a/85/Serviceoriented-Modeling-Soa-Service-Analysis-Design-And-Architecture-Michael-Bell-68-320.jpg)
!["The word of God burdens me because of your grosser
crimes. For behold, thus saith the Lord, this people begin
to wax in iniquity; they understand not the Scriptures; for
they seek to excuse themselves in committing
whoredoms, because of the things which were written
concerning David, and Solomon his son. Behold David and
Solomon truly had many wives and concubines, which
thing was abominable before me, saith the Lord:
wherefore, thus saith the Lord, I have led this people forth
out of the land of Jerusalem, by the power of mine arm,
that I might raise up unto me a righteous branch from the
fruit of the loins of Joseph. Wherefore, I the Lord God, will
not suffer that this people shall do like unto them of old.
Wherefore, my brethren, hear me, and hearken to the
word of the Lord; for there shall not any man among you
have, save it be one wife; and concubines he shall have
none; for I, the Lord God, delighteth in the chastity of
women. And whoredoms are an abomination before me;
thus saith the Lord of Hosts."[163:A]
Here it is stated as coming from God himself, that the polygamy
and concubinage of David and Solomon were abominable before the
Lord. And yet we every day hear David and Solomon, as well as
Abraham, Jacob, and others, cited by those practising polygamy, as
their illustrious prototypes, whose example is worthy of all imitation.
Orson Pratt, the ablest writer on Mormon theology, is compelled
to admit that the Book of Mormon is opposed to polygamy. He says:
—
"Do you believe that the Book of Mormon is a divine
revelation? We do. Does that book teach the doctrine of
plurality of wives? It does not. Does the Lord in that book
forbid the plurality doctrine? He forbid the ancient
Nephites to have any more than one wife."[163:B]](https://image.slidesharecdn.com/738786-250516050724-7b62765a/85/Serviceoriented-Modeling-Soa-Service-Analysis-Design-And-Architecture-Michael-Bell-69-320.jpg)
![Elder Pratt then endeavors to blunt the force of this testimony in
the following manner:—
"Why were the ancient Nephites restricted to the one-
wife system? Because, first, the number of males and
females among them, at the time the command was
given, was about equal. Secondly, there was no probability
that judgments, wars, or any other calamities which were
to befall their nation, would produce a disproportionate
number of males and females. Thirdly, this small remnant
of the tribe of Joseph, were, at that time, about equally
righteous; and one was about as capable of raising up a
family in righteousness as another. And, lastly, the Lord
himself informs them, in the same connection with the
quotation which I have just made, that if He would have
them practise differently from what He had previously
taught them, it must be by His command."[164:A]
Thus, in the attempt to weaken the force of the evidence
furnished by the Book of Mormon against polygamy, Pratt
acknowledges, in the most explicit manner, the validity of the
argument against it, founded upon the equality in the numbers of
each sex. Two of the four reasons why the Nephites were to retain
monogamy, relate to the equality in the numbers of the sexes. But
there is a substantial equality in the numbers of the sexes, not only
in the United States, but in Utah Territory. (See U. S. Census.)
Let us now turn to the Book of Doctrine and Covenants, and see
if we can find in that volume any authority for polygamy. The
following passages will determine the question:—
"Thou shalt love thy wife with all thy heart, and shalt
cleave unto her, and none else; and he that looketh upon
a woman to lust after her, shall deny the faith, and shall
not have the spirit; and if he repents not he shall be cast
out."[164:B]](https://image.slidesharecdn.com/738786-250516050724-7b62765a/85/Serviceoriented-Modeling-Soa-Service-Analysis-Design-And-Architecture-Michael-Bell-70-320.jpg)
![Again. In 1845, the year after Smith's death, an Appendix was
authoritatively added to the Book of Doctrine and Covenants,
containing the following, which is extracted from the section entitled
"Marriage":—
"2. Marriage should be celebrated with prayer and
thanksgiving; and at the solemnization, the persons to be
married standing together," etc., "he [the person
officiating] shall say, calling each by their names, 'you
both mutually agree to be each other's companion,
husband and wife, observing the legal rights belonging to
this condition; that is, keeping yourselves wholly for each
other, and from all others, during your lives.' And when
they have answered 'yes,' he shall pronounce them
'husband and wife,' in the name of the Lord Jesus Christ
and by virtue of the laws of the country, and authority
vested in him. . . .
"4. . . . Inasmuch as this church of Christ has been
reproached with the crime of fornication and polygamy;
we declare that we believe that one man should have one
wife; and one woman but one husband, except in case of
death, when either is at liberty to marry again."[165:A]
Can anything be more explicit than this? Polygamy is not only
expressly repudiated by the church, but is classed by the side of
fornication as a crime.
Thus we find that polygamy is contrary to both books of the
Mormon Bible. That it is, in fact, strongly condemned in those
volumes.
It is, therefore, no part of the Mormon religion, as given to the
world by Joseph Smith.
But polygamy is practised in Utah. Whence did it arise, and upon
what foundation does it rest?](https://image.slidesharecdn.com/738786-250516050724-7b62765a/85/Serviceoriented-Modeling-Soa-Service-Analysis-Design-And-Architecture-Michael-Bell-71-320.jpg)
![Like slavery, and all other great social evils, it had its origin,
doubtless, in an abuse of the passions of man.
It was first publicly announced and recommended in Utah
Territory on the 29th of August, 1852, by Orson Pratt and Brigham
Young, at a politico-religious meeting, held in Great Salt Lake City.
On that occasion, President Young said:—
"You heard Brother Pratt state, this morning, that a
Revelation would be read this afternoon, which was given
previous to Joseph's death. It contains a doctrine a small
portion of the world is opposed to; but I can deliver a
prophecy upon it. Though that doctrine has not been
preached by the Elders, this people have believed in it for
years.
"The original copy of this Revelation was burnt up.
William Clayton was the man who wrote it from the mouth
of the Prophet. In the mean time it was in Bishop
Whitney's possession. He wished the privilege to copy it,
which Brother Joseph granted. Sister Emma (wife of
Joseph Smith) burnt the original. The reason I mention
this is, because that the people who did know of the
Revelation, suppose it was not now in existence.
"The Revelation will be read to you. The principle
spoken upon by Brother Pratt this morning, we believe in.
. . . "Many others are of the same mind. They are not
ignorant of what we are doing in our social capacity. They
have cried out proclaim it; but it would not do a few years
ago; everything must come in its time, as there is a time
to all things. I am now ready to proclaim it.
"This Revelation has been in my possession many
years; and who has known it? None but those who should
know it. I keep a patent lock on my desk, and there does
not anything leak out that should not."[166:A]](https://image.slidesharecdn.com/738786-250516050724-7b62765a/85/Serviceoriented-Modeling-Soa-Service-Analysis-Design-And-Architecture-Michael-Bell-72-320.jpg)
![The Revelation, so called, which was read at the close of this
sermon, purports to have been given to Joseph Smith, July 12, 1843.
It is very lengthy, consisting of twenty-five sections or paragraphs. It
is published in full, in Burton's "City of the Saints," and in various
other publications. The following synopsis exhibits all that is
essential of this extraordinary Revelation.
THE REVELATION.
Section 1. "Verily, thus saith the Lord unto you, my servant
Joseph, that inasmuch as you have inquired of my hand to know and
understand wherein I, the Lord, justified my servants Abraham,
Isaac, and Jacob, as also Moses, David, and Solomon, my servants,
as touching the principle and doctrine of their having many wives
and concubines: Behold, and lo, I am the Lord thy God, and will
answer thee as touching this matter." [The balance of this section is
prefatory, declaring that a new law and everlasting covenant is about
to be revealed, and that he who abides not that covenant shall be
damned.]
Sec. 2. All covenants, contracts, vows, etc., not made and sealed
by the Holy Spirit of promise, of him who is anointed (Joseph Smith)
both as well for time and for all eternity, are of no efficacy or force
after the resurrection.
Sec. 3 represents the necessity of having everything sanctioned
by the Almighty.
Secs. 4 and 5. Persons married for life only, or for time and
eternity, but not by the proper authority, not bound to each other
after this life.
Sec. 6 provides that if a man marry a wife by the law of God, and
by the new and everlasting covenant, and if they abide in the
covenant, and do not shed innocent blood, then the covenant shall
be binding throughout time and eternity, "and they shall pass by the
angels, and the gods which are set there, to their exaltation and
glory in all things."](https://image.slidesharecdn.com/738786-250516050724-7b62765a/85/Serviceoriented-Modeling-Soa-Service-Analysis-Design-And-Architecture-Michael-Bell-73-320.jpg)
![If a husband has lost his wife by death, before he had the
opportunity of attending to this holy ordinance, and securing her as
his lawful wife for eternity, then it is the duty of the second wife,
first, to be sealed or married to the husband, for and in the name of
the deceased wife, for all eternity; and, secondly, to be married for
time and eternity herself, to the same man. Thus, by this holy
ordinance, both the dead and the living wife will be his in the eternal
worlds. But if, previous to marriage for eternity, a woman lose her
husband by death, and marry a second, and if her first husband was
a good man, then it is the duty of the second husband to be married
to her for eternity, not for himself, but in the name of her deceased
husband, while he himself can only be married to her for time; and
he is obliged to enter into a covenant to deliver her up, and all her
children, to her deceased husband, in the morning of the first
resurrection.
Thus, by these refinements, a religious veil, captivating to the
fancy, is thrown over the institution to hide its deformity. The same
distinctions are carried through all the various relations of life; hence
in case a widow is married to a widower, three ceremonies are
necessary, in order fully to establish the eternal relations of all the
parties.
Incest is the practical result of some of the branches of this new-
fangled system of sealing and marriage. It has already been shown,
by the report of the Committee on Territories in the United States
Senate, and the Message of Gov. Harding, that a mother and her
daughters (by a former husband) all live together, as wives of the
same husband.[173:A]
A still more revolting relation is sometimes maintained. It is
called "heirship," and is plainly enough sanctioned by Young, as
follows:—
"The text is, the right of heirship. I will, however, make
an addition to the scripture, before I proceed further with](https://image.slidesharecdn.com/738786-250516050724-7b62765a/85/Serviceoriented-Modeling-Soa-Service-Analysis-Design-And-Architecture-Michael-Bell-80-320.jpg)
Serviceoriented Modeling Soa Service Analysis Design And Architecture Michael Bell
- 1. Serviceoriented Modeling Soa Service Analysis Design And Architecture Michael Bell download https://ebookbell.com/product/serviceoriented-modeling-soa- service-analysis-design-and-architecture-michael-bell-1477572 Explore and download more ebooks at ebookbell.com
- 2. Here are some recommended products that we believe you will be interested in. You can click the link to download. Soa Modeling Patterns For Serviceoriented Discovery And Analysis Michael Bell https://ebookbell.com/product/soa-modeling-patterns-for- serviceoriented-discovery-and-analysis-michael-bell-4107720 Business Process Driven Soa Using Bpmn And Bpel From Business Process Modeling To Orchestration And Service Oriented Architecture Kapil Pant https://ebookbell.com/product/business-process-driven-soa-using-bpmn- and-bpel-from-business-process-modeling-to-orchestration-and-service- oriented-architecture-kapil-pant-4633594 Speech Acts And Prosodic Modeling In Serviceoriented Dialog Systems 1st Edition Christina Alexandris https://ebookbell.com/product/speech-acts-and-prosodic-modeling-in- serviceoriented-dialog-systems-1st-edition-christina- alexandris-51355876 Handson Ethical Hacking And Network Defense Modeling To Orchestration And Service Oriented Architecture Michael T Simpson https://ebookbell.com/product/handson-ethical-hacking-and-network- defense-modeling-to-orchestration-and-service-oriented-architecture- michael-t-simpson-5498668
- 3. Requirements Modelling And Specification For Service Oriented Architecture Ian Graham https://ebookbell.com/product/requirements-modelling-and- specification-for-service-oriented-architecture-ian-graham-1404636 Serviceoriented And Cloud Computing 9th Ifip Wg 612 European Conference Esocc 2022 Wittenberg Germany March 2224 2022 Proceedings Fabrizio Montesi https://ebookbell.com/product/serviceoriented-and-cloud-computing-9th- ifip-wg-612-european-conference-esocc-2022-wittenberg-germany- march-2224-2022-proceedings-fabrizio-montesi-47223088 Serviceoriented Computing 20th International Conference Icsoc 2022 Seville Spain November 29 December 2 2022 Proceedings Javier Troya https://ebookbell.com/product/serviceoriented-computing-20th- international-conference-icsoc-2022-seville-spain- november-29-december-2-2022-proceedings-javier-troya-48673104 Service Oriented Holonic And Multiagent Manufacturing Systems For Industry Of The Future Proceedings Of Sohoma 2022 Theodor Borangiu https://ebookbell.com/product/service-oriented-holonic-and-multiagent- manufacturing-systems-for-industry-of-the-future-proceedings-of- sohoma-2022-theodor-borangiu-49111418 Serviceoriented Architecture Analysis And Design For Services And Microservices Thomas Erl https://ebookbell.com/product/serviceoriented-architecture-analysis- and-design-for-services-and-microservices-thomas-erl-50194916
- 6. SERVICE-ORIENTED MODELING SERVICE ANALYSIS, DESIGN, AND ARCHITECTURE MICHAEL BELL JOHN WILEY & SONS, INC.
- 8. SERVICE-ORIENTED MODELING SERVICE ANALYSIS, DESIGN, AND ARCHITECTURE MICHAEL BELL JOHN WILEY & SONS, INC.
- 9. This book is printed on acid-free paper. Copyright 2008 by Michael Bell. All rights reserved. Published by John Wiley & Sons, Inc., Hoboken, New Jersey. Published simultaneously in Canada. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, scanning, or otherwise, except as permitted under Section 107 or 108 of the 1976 United States Copyright Act, without either the prior written permission of the Publisher, or authorization through payment of the appropriate per-copy fee to the Copyright Clearance Center, Inc., 222 Rosewood Drive, Danvers, MA 01923, 978-750-8400, fax 978-646-8600, or on the web at www.copyright.com. Requests to the Publisher for permission should be addressed to the Permissions Department, John Wiley & Sons, Inc., 111 River Street, Hoboken, NJ 07030, 201-748-6011, fax 201-748-6008, or online at http://www.wiley.com/go/permissions. Limit of Liability/Disclaimer of Warranty: While the publisher and author have used their best efforts in preparing this book, they make no representations or warranties with respect to the accuracy or completeness of the contents of this book and specifically disclaim any implied warranties of merchantability or fitness for a particular purpose. No warranty may be created or extended by sales representatives or written sales materials. The advice and strategies contained herein may not be suitable for your situation. You should consult with a professional where appropriate. Neither the publisher nor author shall be liable for any loss of profit or any other commercial damages, including but not limited to special, incidental, consequential, or other damages. For general information on our other products and services, or technical support, please contact our Customer Care Department within the United States at 800-762-2974, outside the United States at 317-572-3993 or fax 317-572-4002. Wiley also publishes its books in a variety of electronic formats. Some content that appears in print may not be available in electronic books. For more information about Wiley products, visit our Web site at http://www.wiley.com. Library of Congress Cataloging-in-Publication Data: Bell, Michael, 1951— Service-oriented modeling : service analysis, design, and architecture / Michael Bell. p. cm. Includes index. ISBN 978-0-470-14111-3 (cloth) 1. Business enterprises—Computer networks—Management. 2. System design. 3. Computer software—Development. 4. Computer simulation. 5. Computer network architectures. I. Title. HD30.37.B45 2008 004.068—dc22 2007033463 Printed in the United States of America. 10 9 8 7 6 5 4 3 2 1
- 10. For Yvonne, whose love, patience, and support carried me through this project.
- 12. Service-Oriented Modeling Framework Abstraction Practice Realization Practice Conceptual Environment Service Conceptualization Discipline Conceptual Architecture Discipline Business Integration Discipline Service Discovery and Analysis Discipline Analysis Environment Service Design Discipline Logical Architecture Discipline Logical Environment Conceptual Service Analysis Service Design Service Conceptual Architecture Logical Architecture Physical Environment Solution Service Physical Architecture Modeling Practices Modeling Environments Modeling Disciplines Modeling Artifacts Modeling Solutions Service Typing Model Service-Oriented Analysis Typing Model Service-Oriented Analysis Asset Notation Service-Oriented Analysis Notation Abstraction Context Source Legacy Portfolio Business Technical Other Composite Cluster Other Atomic Service-Oriented Analysis Typing Model Structure Atomic Service Composite Service Service Cluster
- 13. Service-Oriented Analysis Operation Notation Aggregated Subtracted Decomposed Unified Intersected Transformed Overlapped Comment Service-Oriented Business Integration Operations Notation Service-Oriented Business Integration Asset Notation Business Domain Contextual Perspective Business Tier Atomic Service Composite Service Service Cluster Business Architecture Integration Elements Service-Oriented Software Assets Perspective of... Separated Contained Comment Integrated Disintegrated
- 14. Service-Oriented Design Notation Service-Oriented Design Asset Notation Service-Oriented Logical Design Relationship Connectors Atomic Service Composite Service Service Cluster Consumer Apparent Unidirectional Implied Bidirectional Apparent Bidirectional Comment Implied Unidirectional Service-Oriented Design Composition Style Beams Logical Design Composition Styles Star Beam Circular Beam Network Beam Hierarchical Beam Circular Hierarchical Network Star
- 15. Service-Oriented Conceptual Architecture Notation Conceptual Architecture Solution Elements Conceptual Architecture Operations Notation Business Domain Packaged Technological Asset Architectural Concept (conceptual machine) Technological Function (attribute descriptor) Conceptualized as... Function of... Extended Owner of... Recognized Comment Service-Oriented Logical Architecture Notation Logical Architecture Assets Notation Logical Architecture Operations Notation @ EXC Utilized Executed Comment Packaged Technological Asset Business or Technological Process
- 16. CONTENTS Preface xv Acknowledgments xvii CHAPTER 1 Introduction 1 Service-Oriented Modeling: What Is It About? 2 Driving Principles of Service-Oriented Modeling 4 Organizational Service-Oriented Software Assets 6 Service-Oriented Modeling Process Stakeholders 7 Modeling Services Introduction: A Metamorphosis Embodiment 8 Service-Oriented Modeling Disciplines: Introduction 14 Modeling Environments 21 Service-Oriented Modeling Framework 23 Summary 27 PART ONE Service-Oriented Life Cycle 29 CHAPTER 2 Service-Oriented Life Cycle Model 31 Service-Oriented Life Cycle Model Principles 31 Service-Oriented Life Cycle Model Structure 34 Service-Oriented Life Cycle Disciplines 42 Summary 48 CHAPTER 3 Service-Oriented Life Cycle Perspectives 49 Service-Oriented Life Cycle Workflows: Introduction 49 Planning Service-Life Cycle Workflows 53 Service Life Cycle Progress View 59 Service Life Cycle Iteration View 61 Service Life Cycle Touch-Points View 66 Summary 67 PART TWO Service-Oriented Conceptualization 69 What Is a Conceptual Service? 70 Service-Oriented Conceptualization Model 71 Guiding Principles of Service-Oriented Conceptualization 72 ix
- 17. x CONTENTS CHAPTER 4 Attribution Analysis 75 Establishing Core Attributes 75 Establishing an Attribution Model 78 Attribution Analysis 80 Attribute Selection 82 Deliverables 85 Summary 86 CHAPTER 5 Conceptual Service Identification 87 Service Conceptualization Toolbox 88 Conceptual Service Identification and Categorization 89 Conceptual Service Association Process 96 Conceptual Service Structure 103 Deliverables 109 Summary 110 PART THREE Service-Oriented Discovery and Analysis 111 CHAPTER 6 Service-Oriented Typing and Profiling Model 115 Service-Oriented Typing 115 Service Typing Namespaces 124 Service-Oriented Profiling 124 Deliverables 126 Summary 128 CHAPTER 7 Service-Oriented Discovery and Analysis: Implementation Mechanisms 131 Service-Oriented Analysis Assets 131 Service Discovery and Analysis Toolbox 133 Granularity Analysis 135 Aggregation Analysis 139 Decomposition Analysis 140 Unification Analysis 143 Intersection Analysis 145 Subtraction Analysis 147 Combining Service Analysis Methods 150 Deliverables 153 Summary 153 CHAPTER 8 Service-Oriented Analysis Modeling 155 Analysis Modeling: Guiding Principles 156
- 18. CONTENTS xi Analysis Proposition Diagrams 157 Analysis Notation 157 Analysis Modeling Rules 159 Analysis Modeling Process 160 Service-Oriented Analysis Modeling Operations 160 Deliverables 167 Summary 167 PART FOUR Service-Oriented Business Integration 169 Service-Oriented Business Integration Principles 169 Service-Oriented Business Architecture Perspectives Introduction 170 CHAPTER 9 Business Architecture Contextual Perspectives 177 Business Model Perspectives 177 Problem-Solving Perspectives 187 Deliverables 189 Summary 190 CHAPTER 10 Business Architecture Structural Perspectives 191 Business Architecture Structural Integration Model 192 Business Architecture Integration Structures 192 Business Domain Geographic Boundaries 199 Business Tier Distribution Formations 203 Business Control Structures 207 Deliverables 208 Summary 209 CHAPTER 11 Service-Oriented Business Integration Modeling 211 Service-Oriented Business Integration Modeling Principles 211 Service-Oriented Business Integration Diagram 213 Modeling Process 215 Deliverables 228 Summary 228 PART FIVE Service-Oriented Design Model 229 Service-Oriented Logical Design General Model 230 Service-Oriented Logical Design Assets 232 CHAPTER 12 Service-Oriented Logical Design Relationship 233 Major Influences on Service Relationships 234
- 19. xii CONTENTS A Formal Service Logical Relationship Notation 235 Roles in the Service-Oriented Design Context 237 Service Design Visibility Aspects 237 Service Cardinality 243 Synchronization 247 Tagging Intermediaries 249 Service-Oriented Logical Design Relationship Diagram 252 Deliverables 255 Summary 255 CHAPTER 13 Service-Oriented Logical Design Composition 257 What Is a Service-Oriented Logical Design Composition? 257 Service-Oriented Design Composition Components 258 Service-Oriented Design Composition Styles 259 Logical Design Composition Strategies 270 Deliverables 281 Summary 282 CHAPTER 14 Service-Oriented Transaction Model 283 Service-Oriented Transaction Planning Success Criteria 284 Logical Design View: Service-Oriented Transaction Diagram 284 Conveying Functionality in the Activity Section 291 Planning Service-Oriented Transactions 295 Deliverables 304 Summary 305 PART SIX Service-Oriented Software Architecture Modeling Principles 307 Service-Oriented Conceptual Architecture Modeling 308 Service-Oriented Logical Architecture Modeling 309 Service-Oriented Physical Architecture 309 CHAPTER 15 Service-Oriented Conceptual Architecture Modeling Principles 311 Conceptual Architecture Layers 312 Architectural Concepts as Machines 320 Modeling Conceptual Architecture 329 Deliverables 339 Summary 339
- 20. CONTENTS xiii CHAPTER 16 Service-Oriented Logical Architecture Principles 341 Logical Architecture Building Blocks 341 Logical Architecture Perspectives 342 Asset Utilization Diagram 342 Reusability Perspective 347 Discoverability Perspective 348 Behavioral Perspective 349 Loose Coupling Perspective 351 Interoperability Perspective 354 Deliverables 357 Summary 357 Index 359
- 22. PREFACE Not long after the beginning of the current decade, the new service-oriented architecture (SOA) paradigm picked up steam and was established as a leading business and technology organiza- tional concept. Lack of software asset reusability standards, absence of software interoperability disciplines, and incoherent business and technology strategies drove the enterprise to establish a more suitable model that promised to foster business agility and increase return on investment. This model also galvanized the development of SOA governance best practices, introduced SOA products, and promoted new service-oriented modeling disciplines. The enterprise is still seeking mechanisms that can alleviate alignment challenges between business and information technology (IT) organizations. This effort includes the establishment of a common service taxonomy and vocabulary—an easy-to-understand language that can fill in the communication gaps between the problem and solution domain entities and establish a proper service development life cycle. Unlike other SOA books on the market, this one introduces a service-oriented modeling framework that employs an agile and universal business and technology language to facilitate analysis, design, and architecture initiatives. The service-oriented modeling disciplines presented will enable practitioners to integrate existing legacy applications and to incorporate new ideas and concepts to address organizational concerns. These proposed best practices can be applied to all technologies, software platforms, and languages despite their physical location or ownership. Furthermore, business and IT professionals, such as managers, business analysts, business archi- tects, technical architects, team leaders, and developers can now share the burden of software development initiatives as they are commissioned to bear equal responsibility and accountability. The service-oriented modeling research presented in this book was driven by the following vision statements: • Introduce a state-of-the-art and holistic modeling language that can facilitate an SOA implementation • Introduce advanced service life cycle concepts and processes that can be employed to manage service-oriented projects • Enable business and IT personnel to equally partner in service-oriented modeling efforts and to represent their unique perspectives This book’s mission focuses on the following service-oriented modeling disciplines that also offer an easy-to-understand modeling language and a notation that is simple to use: • Service-oriented conceptualization • Service-oriented discovery and analysis • Service-oriented business integration • Service-oriented design • Service-oriented conceptual architecture • Service-oriented logical architecture Chapter 1 introduces the proposed service-oriented modeling framework and outlines its components. This chapter targets business and technology personnel who seek to establish and implement a service-oriented modeling language that can be employed during projects to guide, monitor, and control service development life cycles. xv
- 23. xvi PREFACE Part One discusses the service life cycle model and its various building blocks. It elaborates on service evolution management mechanisms during given projects and business initiatives. It also discusses various life cycle perspectives that enable monitoring and assessment of a project’s process. Chapters 2 and 3 set the stage for the management of service-oriented modeling disciplines that are discussed throughout the book. They provide a solid framework for the service-oriented modeling environment and will be practical for business and IT executives, product managers, project managers, architects, and lead developers. Part Two is dedicated to the service-oriented conceptualization process and elaborates on various mechanisms that can help organizations to establish common concepts and identify conceptual services and establish enterprise taxonomies. This Part is targeted at product managers, business architects, business analysts, technical architects, technical managers, team leaders, and developers. Chapters 4 and 5 introduce a step-by-step and an easy-to-employ concept discovery process that yields conceptual solution propositions to organizational problems. Part Three delves into service-oriented discovery and analysis mechanisms. This Part furnishes best practices and procedures that should be used to discover new services and even employ legacy applications to provide viable business and technological solutions. Chapter 6 provides unique mechanisms to establish services’ identities and to categorize them based on their distinctive characteristics. Chapter 7 enables product managers, business architects, technical architects, business analysts, technical leaders, and developers to perform service-oriented analysis on identified software assets. Chapter 8 introduces an analysis proposition modeling process that employs a service-oriented analysis language that can be further used in future service design, architecture, and construction phases. Part Four depicts service-oriented business integration mechanisms and furnishes a busi- ness modeling language that can be used to integrate services with business domains and business products. Chapters 9, 10, and 11 expand on industry-standard business architecture and propose an implementation of business architecture disciplines. Business product managers, business man- agers, IT managers, business architects, technical architects, business analysts, and developers will find these chapters useful for alignment initiatives between business and technology organizations. Part Five focuses on service-oriented design strategies, service relationships, logical com- positions of services, and service behavior analysis. Chapters 12, 13, and 14 target analy- sis, architecture, and development personnel; these individuals must understand the nature of service-oriented software relationships as well as prepare packaged solutions for the architecture and construction teams, study service behaviors, and devise service-oriented transactions. Finally, Part Six elaborates on fundamental aspects of service-oriented software archi- tecture. These topics include conceptual and logical architecture modeling disciplines. Chapters 15 and 16 offer a conceptual architecture modeling language that can be employed to describe organizational technological abstractions, as well as a logical architecture topic that depicts the fundamental service-oriented building blocks that will be deployed to production and become an integral part of an organization’s physical architecture.
- 24. ACKNOWLEDGMENTS For all of those who have helped shape this book by contributing their ideas, vision and strategies, many thanks. Without their involvement, enthusiasm, and the coherent direction they provided, this book would not have been possible to accomplish. The valuable insights and feedback that were extended through the research and the actual writing process were concerned with many fundamental aspects of business and technology prac- tices. These include the general strategy of the book, business modeling aspects, business process disciplines, business architecture policies, enterprise and application architecture standards, com- puter programming topics, and even editorial contributions. Charu Bansal, Donald Buckley, Dolly Dsa, Donald Mahaya, Eric Marks, Boris Minkin, Lisa Nathan, Mark Penna, Hormazd Pochara, Monica Roman, Jeff Schneider, and Alex Rozen. To all of you thank you for your time and commitment to the success of this book. Special thanks to Mr. Sheck Cho, the executive editor that not only encouraged this project, but also provided strategic and tactical support throughout the publishing process. xvii
- 26. CHAPTER 1 INTRODUCTION As human beings, we are passionate about new ideas that promise to transform our lives and create new opportunities. We also tend to rapidly replace old technologies with new ones. Ours is a versatile society that runs on tomorrow’s software piled on top of the technology layers of yesterday and today. Try to imagine the next breakthrough that will supersede today’s examples of human ingenuity. Will it be miniature software installed on microwave ovens or refrigerators that monitors a diet prescribed by a personal nutritionist? Could it be a smart software component that not only designs itself but also architects its own operating production environment? Or perhaps a virtual software development platform that enables business and technology personnel to jointly build applications with goggles and gloves? These futuristic software concepts would probably contribute yet another layer to our already complex computing environments, one requiring resources to maintain and budgets to support. This layer would sit on top of technological artifacts accumulated over the past few decades that are already difficult to manage. Not long after the new millennium, discontent over interoperability, reusability, and other issues drove the software community to come up with the service-oriented architecture (SOA) paradigm. Even readers who are not familiar with SOA will probably agree that it is rooted in tra- ditional software development best practices and standards. To fulfill the promise of SOA, superb governance mechanisms are necessary to break up organizational silos and maximize software asset reusability. The SOA vision also addresses the challenges of tightly coupled software and advocates an architecture that relies on the loose coupling of assets. On the financial front, it tackles budgeting and return-on-investment issues. Another feature that benefits both the techno- logical and business communities is a reduction of time to market and business agility. Indeed, the list of advantages continues to grow. But does the promise of SOA address software diversity issues? Does it offer solutions to the integration and collaboration hurdles created by the accumulation of generations of het- erogeneous computing landscapes? Will the SOA vision constitute yet another stratum of ideas and technologies that will be buried beneath future innovations? Will SOA be remembered as a hollow buzzword that failed to solve one of the most frustrating technological issues of our time? Or will it serve as an inspiration for generations to come? It is possible that SOA may fail to deliver on its promise, but if it does, we, business and IT personnel, must shoulder some of the blame. SOA may turn out to be little more than a technological fire drill if we are ambivalent about the roles and responsibilities of legacy software in our existing and future organizational strategies; if we fail to tie together past, present, and future software development initiatives; and if we disregard the contributions of previous generations of architectures to today’s business operations. Indeed, the idea of properly bridging new and old software technologies is a novel one. But what about establishing a more holistic view of the technological inventory that we have been building up for years? Can we treat all our software 1
- 27. 2 Ch. 1 Introduction assets equally in terms of their analysis, design, and architectural value propositions? Can we understand their collaborative contribution to our environment without being too concerned about their underlying languages and implementation detail? Can we name these assets services? Can we conceive of them as service-oriented entities? Are they not built on similar SOA strategies and principles? This book introduces service-oriented modeling mechanisms that will enable us to con- ceive software products that we have been constructing, acquiring, and integrating during the past few decades as service-oriented constituents. These entities—either legacy applications written in languages such as COBOL, PL1, Visual Basic, Java, C++, C#, or diverse empowering platforms and middleware—should all take part in an SOA modeling framework. Most important, they should be treated equally in the face of analysis, design, and architectural initiatives, and should simply be recognized as services. A new SOA modeling language will be unveiled in this book that is not based on any particular programming language paradigm, constrained by language structure barriers, or limited to a language syntax. As a result of this universal language, the modeling process becomes more accessible to both the business and technology communities. This SOA modeling approach is well suited to provide tactical, short-term solutions to enterprise concerns, yet it furnishes strategic remedies to persistent organizational problems. So what is service-oriented modeling? Service-oriented modeling is a software development practice that employs modeling disci- plines and language to provide strategic and tactical solutions to enterprise problems. This anthropomorphic modeling paradigm advocates a holistic view of the analysis, design, and architecture of all organizational software entities, conceiving them as service-oriented assets, namely services. SERVICE-ORIENTED MODELING: WHAT IS IT ABOUT? Modeling activities are typically embedded in the planning phase of almost any project or soft- ware development initiative that an organization conducts. The modeling paradigm embodies the analysis, design, and architectural disciplines that are being pursued during a given project. These major modeling efforts should not center only on design and architectural artifacts such as diagrams, charts, or blueprints. Indeed, modeling deliverables is a big part of a modeling process. But the service-oriented modeling venture is chiefly about simulating the real world. It is also about visualizing the final software product and envisioning the coexistence of services in an interoperable computing environment. Therefore, the service-oriented modeling paradigm advocates first creating a small replica of the “big thing” to represent its key characteristics and behavior—in other words, plan small, dream big; test small, execute big! A VIRTUAL WORLD. How is it possible to simulate such a business and technological environ- ment that offers solutions to organizational business and technology problems? “Simulating” does not necessarily mean starting with the construction of a software executable. It does not imply instantly embarking on an implementation initiative to produce source code and build components and services. The service-oriented modeling process begins with the construction of a miniature replica on paper. This may involve modeling teams in whiteboard analysis, design, and architec- ture sessions, or even the employment of software modeling tools that can visually illustrate the solutions arrived at. Thus, the simulation process entails the creation of a virtual world in which software constituents interface and collaborate to provide a viable remedy to an organizational concern. A STRATEGIC ENDEAVOR GUIDED BY MODELING DISCIPLINES. Creating a miniature mockup of a final software product and its supporting environment can obviously reduce investment risk by ensuring the success of the impending software construction initiative. This can be achieved
- 28. Service-Oriented Modeling: What Is It About? 3 by employing analysis, design, and architectural disciplines that are driven by a modeling strategy that fosters asset reusability, a high return on investment, and a persuasive value proposition for the organization. Service-oriented modeling disciplines enable us to focus on modeling strategies rather than being concerned with source code and detailed programming algorithms. By employing this modeling paradigm we raise the bar from the granular constructs of our applications, yet we must accommodate the language requirements of the underpinning platforms. We focus on identifying high-level business and technological asset reusability and consolidation opportunities, but we must also foster the reuse of software building blocks such as components and libraries. We rigorously search for interoperability solutions that can bridge heterogeneous technological envi- ronments, but we also concentrate on integration and message exchange implementation detail. A LEARNING AND VALIDATION PROCESS. By producing a small version of the final artifact we are also engaging in a learning and verification process. This activity characteristically would enable us to validate the hypothesis that we have made about a software product’s capability and its ability to operate flawlessly later on in a production environment. We are also being given the opportunity to inspect key aspects of software behavior, examine the relationships between software components, and even understand their internal and external structures. We are involved in a software assessment process that validates the business and technological motivation behind the construction of our tangible services. To better understand the key characteristics of a future software product and its environ- ment, the assessment effort typically leads to a proof-of-concept, a smaller construction project that concludes the service-oriented modeling initiative. This small-scale software executable, if Furnishes Modeling Disciplines that Provide Modeling Standards Modeling Process Modeling Best Practices Offers a Language that Provides Is About Behavior, Structure, and Relationship Inspection Construction of a Virtual Computing World Feasibility and Capability Analysis Simulation Motivation Assessment Hypothesis Verification Service-Oriented Modeling Contributes to Alignment of Business and IT Organizations Loosening Structure of Silo Organizations Strategic and Tactical Organizational Solutions Reduction of Time-to-Market Software Asset Reusability Enhancement Loosely-Coupled Computing Environment Software Assets Consolidation Expenditure Reduction Simple Vocabulary and Taxonomy Intuitive Syntax Universal Terminology EXHIBIT 1.1 ESSENCE OF THE SERVICE-ORIENTED MODELING PARADIGM
- 29. 4 Ch. 1 Introduction approved and agreed on, can later serve as the foundation for the ultimate service construction process. EVERYBODY’S LANGUAGE: A UNIVERSAL LANGUAGE FOR BUSINESS AND TECHNOLOGY. We are often driven by tactical decisions to alleviate organizational concerns and to provide rapid solutions to problems that arise. The proposed service-oriented modeling language is designed to ease time to market by strengthening the ties between business and technology organizations. This can accelerate the delivery process of software assets to the production environment. Furthermore, the service-oriented modeling language can also be employed to fill in communication gaps and enhance alignment between the problem and solution domain bodies. To achieve these goals, the service-oriented modeling language offers an intuitive syntax, a simple vocabulary, and a taxonomy that can be well understood and easily employed by various business and technology stakeholders during service life cycle phases and projects. The language can be utilized not only by professional modelers, architects, or developers, but by managers, business executives, business analysts, business architects, and even project administrators. Exhibit 1.1 depicts the service-oriented modeling activities, language, disciplines, and benefits. DRIVING PRINCIPLES OF SERVICE-ORIENTED MODELING Service-oriented modeling principles capitalize on devised SOA standards already in use by orga- nizations and professionals. These are best practices that are designed to foster strategic solutions to address enterprise concerns, and to overcome the shortsightedness that is frequently attributed to organizational tactical decisions. The following modeling principles promote business agility, software asset reuse, loosely coupled service-oriented environments, and a universal modeling language that can address software interoperability challenges: • Virtualization • Metamorphosis • Literate modeling VIRTUALIZATION. Modeling software is essentially a process of manipulating intangible enti- ties. These are typically nonphysical assets that reside in peoples’ minds or appear on paper. An effective modeling process should be as visual as possible, enabling business and technology personnel to view software elements as if they were concrete assets. The virtuality and reality aspects of our surroundings have been debated by numerous philosophers going back to the eighteenth century. The traditional assertions that “everything has a reality and a virtuality” or “everything other than what is virtual is reality” are in agreement with sociologist, philosopher, and information technology pioneer Ted Nelson’s claim that virtuality is the focal point of software design.1 He further argued that virtuality is about designing software conceptual structure and feel.2 The visual aspect of the service-oriented modeling paradigm is driven by the construction of a virtual world in which elements seem almost as tangible as real physical objects. This world that we create to simulate reality is made up of two major elements: (1) the landscape that “glues” all pieces together; meaning the environment that empowers and executes services and (2) the services that communicate, interact, and exchange information to provide business value. Moreover, a virtual world can effectively simulate a heterogeneous computing landscape by treating software assets as equal partners in a modeling endeavor. This effect is called federated modeling.
- 30. Driving Principles of Service-Oriented Modeling 5 The visualization process that we pursue enables us to model relationships, structures, and behaviors of services that would provide satisfying solutions to organizational problems. These goals can be achieved by fostering asset reusability, promoting a loosely coupled computing environment, and resolving interoperability challenges across organizations. METAMORPHOSIS. The business environment that we all share is a dynamic market that keeps evolving and changing direction and also influences technological trends and application develop- ment. This vibrant business landscape often dictates alterations to a service’s behavior, structure, and relationship to its environment during its life span. These modifications typically start at a service’s inception, when it manifests as an intangible entity—an idea—and then continue as the service evolves into a physical software asset that executes business functionality in pro- duction. This transformation process is the essence of the metamorphosis paradigm driven by service-oriented modeling disciplines that ensure software elasticity, and ultimately, business agility. But the transformation process does not stop with the deployment of services to production. Imagine how frequently a valuable application is involved in multiple project iterations that lead to software upgrades. Think about the myriad instances of a service finding its way back to the drawing board to be redesigned and then ferried back to the production environment again. This is typical of the software development life cycle, during which software products are upgraded, enhanced, and redistributed. LITERATE MODELING. Should a programming language offer a simple syntax that is easy to understand, and is intuitive and readable? Or should it offer formal grammar, rules, and symbols that only developers can handle? Should a programming language be based on machine-readable source code that is easy to debug and optimize? Or should it be considered a scientific artifact, a mathematical formula that only experts on the subject can deliver? This long-running debate is believed to have begun in the early 1980s and encompasses two major approaches to software development that have major ramifications for the service-oriented modeling paradigm. The first was introduced by Donald Knuth’s theory of “literate programming” in which he argues: “I believe that the time is ripe for significantly better documentation of programs, and that we can best achieve this by considering programs to be works of literature. Hence, my title: ‘Literate Programming’.” The second approach was introduced by Edsger Dijkstra in his 1988 article “On the Cruelty of Really Teaching Computer Science,” in which he claims that programming is merely a branch of mathematics.3 He writes: “Hence, computing science is—and will always be—concerned with interplay between mechanized and human symbol manipulation, usually referred to as ‘computing’ and ‘programming’ respectively.” This debate further informs the discussion about the modeling paradigm. Should service- oriented modeling be founded on a specific programming platform structure that only developers and modelers can utilize? Or should modeling disciplines offer universal and easy to understand notations that are independent of language? Should a service-oriented modeling approach be tied to fashionable technologies? Or should a modeling language offer tools to design and architect multiple generations of legacy platforms, applications, and middleware? The service-oriented anthropomorphic modeling approach provides easy mechanisms to address analysis, design, and architectural challenges and perceives software assets as hav- ing human characteristics. In the virtual world that we are commissioned to create, services “interact,” “behave,” “exchange information,” and “collaborate;” they are “retired,” “promoted,” “demoted,” and “orchestrated.” Inanimate software entities are often treated as though they had
- 31. 6 Ch. 1 Introduction human qualities. This “literate modeling” approach obviously enhances the strategies that are pursued during business initiatives and projects. ORGANIZATIONAL SERVICE-ORIENTED SOFTWARE ASSETS The service-oriented modeling paradigm regards all organizational software assets as candidates for modeling activities. We not only conceive them as our service-oriented modeling elements, meaning services, but we also evaluate them based on their contribution to a service-oriented environment, in terms of integration, collaboration, reusability, and consumption capabilities. These assets are also subjected to the modeling discipline activities depicted throughout this book. They are the enduring artifacts of the service-oriented modeling process and are regarded as units of concern, discovery, analysis, design, and architecture in a business initiative or a service-oriented project. Exhibit 1.2 illustrates the various service-oriented software assets that can be involved in providing solutions to organizational concerns: concepts, foundation software, legacy software, repositories, and utility software. ORGANIZATIONAL CONCEPTS. Business or technical concepts embody an organization’s for- malized ideas, which are regarded as components of propositions to organizational concerns. These abstractions typically capture enterprise problems and offer remedies to alleviate nega- tive effects on business execution. Concepts characteristically offer direction and strategy to the service-oriented analysis, discovery, design, and architectural disciplines. They also contribute to the establishment of a common organizational business and technical terminology that can be employed to fill in the communication gaps between business and information technology (IT) organizations. Agriculture Community Center, Business Community, and Pals’ Community are examples of concepts that identify the financial prospects and marketing targets of a business goal. Here, the Community business concern is the driving aspect behind a particular organization’s culture and strategy. FOUNDATION SOFTWARE. Organizational empowering middleware and platform products are the basic software ingredients of the service-oriented modeling practice. Middleware products offer integration, hosting, and network environment support, including message orchestration and routing, data transformation, protocol conversion, and searching and binding capabilities. This software asset category may include application servers, portal products, software proxies, Software Assets Foundation Software Legacy Software Repositories Utility Software Concepts EXHIBIT 1.2 ORGANIZATIONAL SERVICE-ORIENTED SOFTWARE ASSETS
- 32. Service-Oriented Modeling Process Stakeholders 7 SOA intermediaries, gateways, universal description, discovery and integration (UDDI) registries, and even content management systems. Message-oriented middleware (MOM) technologies are also regarded as middleware, which may include traditional message busses or enterprise ser- vice busses (ESBs). Conversely, software platforms are akin to frameworks that enable lan- guages to run. This category may also include operating systems, runtime libraries, and virtual machines. LEGACY SOFTWARE. “Legacy” refers to existing software assets that are regarded as applica- tions. These include business and technology software executables that already operate in the production environment. The term “legacy” also includes deployed organizational services such as Web services and even services that are running on a mainframe or other platforms and do not comply with Web service technologies and standards. Third-party vendor applications, ser- vice consumers, and partner services that operate outside of an organization are also conceived as legacy software assets. Customer Profile Service, Accounts Payable Application, or Trading Consumer are examples of existing and operating legacy software products, offered by third-party vendors or custom built by an organization’s internal development personnel. REPOSITORIES. Repositories play a major role in most service-oriented modeling activities. This software category is characteristically provided by third-party vendor products that require organizational adoption and integration policies. These are software entities that offer storage facilities, such as relational databases, data warehouse repositories, and various database storage management products, such as data optimization and replication. The repository category can also include data-about-data, meaning repositories that do not necessarily store the actual data but describe it. These are known as meta-data repositories. We employ these storage facilities for a variety of management and data organization purposes. For example, meta-data repositories are used for governance rules, service life cycle management, security policies, search categories, and document management. SOFTWARE UTILITIES. Utility executables are typically regarded as nontransactional software assets employed to facilitate flawless system operations in a production environment. These utilities chiefly offer performance-monitoring services, enforce service-level agreements (SLAs) between consumer and producers, track security infringements, and provide alert mechanisms in case of contract violations or system intrusions. Moreover, software utilities also provide provi- sioning and asset portfolio management facilities and even message mediation policy management between message exchange parties. SERVICE-ORIENTED MODELING PROCESS STAKEHOLDERS The service-oriented modeling process is characteristically overseen by SOA governance and SOA Center of Excellence enterprise bodies that provide best practices, standards, guidance, and assistance to service-oriented modeling activities. Moreover, the modeling process involves two major stakeholders, the problem and the solution domain organizations, typically managed by business and IT personnel that partner in an array of business and technological initiatives, such as a small project or a large service life cycle venture that may include a number of smaller projects. The involvement of two major stakeholder groups is anticipated, each of which rep- resents a different perspective; they are both vital contributors to a service-oriented modeling effort. In addition, they must collaborate and jointly facilitate alignment between business and IT organizations. Exhibit 1.3 illustrates these two major views that collaboratively contribute to the service-oriented modeling process: the business view and the technological view. Note the overseeing governance and Center of Excellence bodies that drive modeling activities.
- 33. 8 Ch. 1 Introduction Business Modeling View Technological Modeling View Service-Oriented Modeling Process SOA Governance and Center of Excellence EXHIBIT 1.3 SERVICE-ORIENTED MODELING PERSPECTIVES BUSINESS STAKEHOLDERS MODELING VIEW. This perspective represents business personnel who not only understand the financial implications of a project or a larger business initiative but have mastered the various business processes of an organization. They typically elaborate on the problem domain, present business requirements, and propose business solutions. Business professionals, however, should be equal participants in the discovery, analysis, design, and archi- tecture modeling sessions. They should be familiar with the service-oriented modeling language and able to provide valuable input to the resulting modeling artifacts. The business organization can be represented by product managers, business managers, financial analysts, business analysts, business architects, business modelers, and even top-level executives, such as chief information officers (CIOs) or chief technology officers (CTOs). TECHNOLOGY STAKEHOLDERS MODELING VIEW. The IT organization is intrinsically engaged in the technological aspects of the service-oriented modeling process. IT personnel contribute both to the analysis and design aspects of services and to the various architecture modeling activ- ities. These functions include the establishment of asset integration strategies, consumption and reusability analysis, and service deployment planning. The IT organization must also ensure align- ment with the organizational business model, business strategies, and business requirements. The technology perspective should be represented by technical management, application architects, system analysts, developers, service modelers, data modelers and database architects. MODELING SERVICES INTRODUCTION: A METAMORPHOSIS EMBODIMENT One of the most common questions people ask themselves when they are commissioned to pro- vide a solution to an organizational problem is “What should be modeled?” The modeling world constitutes a blend of old and new software assets, ideas, formulated concepts, processes, and even people. Typically a remedy is being sought to an organizational concern that involves a thorough analysis of the existing physical operating environments and also requires the integration of new propositions to form viable business and technological solutions. This brings us to the understand- ing that service-oriented assets—whether they are abstractions, legacy applications, middleware, or software platforms—must be both conceived as services and categorized according to their role in the modeling process. Which standard should be used to classify modeling services? The answer to this question is rooted in the necessity to establish a modeling language—a vocabulary—along with disciplines
- 34. Modeling Services Introduction: A Metamorphosis Embodiment 9 Conceptual Service Design Service Analysis Service EXHIBIT 1.4 MODELING SERVICES that can be utilized to implement service-oriented modeling tasks. Thus, the service-oriented mod- eling paradigm treats services according to their life cycle state and their corresponding disciplines. We thus propose three distinct categories: conceptual service, analysis service, and design ser- vice (see Exhibit 1.4). Consequently, the conceptual service originates during the service-oriented conceptualization phase; the analysis service is treated during the service-oriented discovery and analysis process, and the design service is employed during the service-oriented design stage. The driving disciplines behind these modeling processes are further discussed in the Service-Oriented Modeling Disciplines: Introduction section of this chapter. CONCEPTUAL SERVICE: AN ABSTRACTION. A modeling process must offer a communication language, provide a distinct vocabulary that different stakeholders can use to collaborate and interface, to establish an organizational taxonomy that can be easily learned and enhanced as time goes by, and to support a terminology that depicts business and technological abstractions. These generalized idioms embody the requirements to provide solutions to an enterprise concern while reflecting the approach to solving a problem. We conceive these abstractions as concep- tual services that are an essential deliverable in the service-oriented conceptualization phase. For example, the data aggregator concept can be regarded as a conceptual solution that aims to solve information collection problems that occur in an enterprise Web portal. The commission calcula- tor is another conceptual service that exemplifies an essential solution to a business requirement to enable commission calculations for stockbrokers in an equity trading system. Where does a conceptual service originate from? An undocumented idea or an informal enterprise proposal to solve a problem can be established as a conceptual service. These con- cepts can simply be expressed in meetings or whiteboard design sessions. A business process can also be regarded as a conceptual service candidate. A more formalized process, however, that takes place during service conceptualization facilitates the identification of new concepts derived from business and technological requirements (see Chapters 4 and 5 for a complete service conceptualization process). Consider the following major attributes of a conceptual service: It • Embodies business or technical context. • Must be elastic enough to accommodate future business changes. • Should focus on a solution rather than propose remedies to a wide range of problems, and should avoid business or technological context ambiguity. • Corresponds to a business or technological requirement and depicts a coherent proposition. • Represents a business or technological abstraction that can be added to an organization’s language dictionary. • Contributes to an organizational business or technological taxonomy.
- 35. 10 Ch. 1 Introduction ANALYSIS SERVICE: A UNIT OF ANALYSIS. A modeling process must offer a platform on which solution propositions to organizational concerns are verified for their viability and capacity to solve problems; enable proper validation of the assumptions that business and technology personnel make to address business requirements; and permit further analysis of the supporting services that take part in a solution, a project, or a business initiative. During the service-oriented discovery and analysis phase, we are allowed to test service collaboration and conduct further experiments in the search for the best possible offered resolution. An analysis service is the vehicle that enables us to reexamine these preliminary proposed remedies that were brought to the table in the first place. But where does an analysis service originate from? The rule of thumb suggests that all services that participate in the analysis process should be regarded as analysis entities. In other words, all service-oriented assets are conceived of as units of analysis because of their involvement in a solution proposition during the analysis phase. To read more about the service-oriented discovery and analysis process, refer to the Service-Oriented Modeling Disciplines: Introduction section in this chapter, or the service-oriented discovery and analysis method discussed in Chapters 6, 7, and 8. Consider the following major attributes of an analysis service. It • Represents tangible (legacy software) or intangible (abstraction) service-oriented assets that participate in a solution. • Can be associated with business or technical context. • Must present a lucid internal structure. • Should be composed of service-oriented software assets that can be decomposed during the service-oriented analysis modeling process to achieve a loose-coupling architectural effect. • Or, should have a flexible internal structure that would allow aggregation of external services during the analysis modeling process. DESIGN SERVICE: A LOGICAL SOLUTION PROVIDER AND A CONTRACTUAL ENTITY. All service-oriented assets that take part in a design process can be regarded as design services. A design service is a modeling element that enables us to visualize and plan future service behavior, structure, and peer relationships in a production environment. This service-oriented design asset, whose collaborators are peer services and consumers—bound by a stipulated contract—participates in a group effort to provide a viable design solution to a business or technological problem. To achieve this goal, we primarily focus on the message and information exchange capabilities of a service. This would contribute to its future capacity to interact and collaborate with its surrounding environment, and most important, to its ability to abide by the service level agreement (SLA) that it is committed to. This scheme is called a logical solution, and the design service that participates in this venture is known as logical solution provider. A design service must also be a part of a service orchestration initiative, during which we coordinate and synchronize service functionality to enable flawless message exchange and efficient transaction execution. This logical design effort would ensure the quality of service offerings and contribute to the creation of a harmonized interactive environment. Consider the following major attributes of a design service; it • Can be associated with business or technical context. • Can represent a tangible (legacy software) or an intangible (abstraction) service-oriented asset. • Should be interfaceable, containing one or more interfaces to be utilized by potential consumers.
- 36. Modeling Services Introduction: A Metamorphosis Embodiment 11 • Is bound by a service-oriented contract that depicts its interfaces and other important requirements, such as accessibility, consumption, reusability, and security. • Must participate in an orchestration design initiative. SOLUTION SERVICE: PHYSICAL SOFTWARE ASSET. A solution service is a tangible software asset, constructed by business and technology development teams, that has concluded its devel- opment life cycle and is deployed and integrated in a production environment. This asset may be a custom-built software product designed in house, an acquired third-party vendor solution package, or a component custom built by an outsourcing firm. It is the ultimate deliverable of a software development process. Regardless of its origin, we typically employ a solution service to participate in a business or a technological solution devised by the service-oriented modeling prac- tice. The following section, which elaborates on the aspects of service-oriented metamorphosis, describes in detail the role of a solution service in the service-oriented modeling process. SERVICE-ORIENTED MODELING DISCIPLINES DRIVE SERVICE METAMORPHOSIS. During the service-oriented modeling process, a service’s state changes from intangible to physical. This transformation is driven by the service-oriented disciplines that we are commissioned to pursue. The normal course of evolution starts at a service’s inception, during which a service emerges as a concept, continues through its analysis and design phases, and finally evolves as a solu- tion service—a physical executable. By and large, this path is implemented with newly created services. But can a physical solution service transform back into its previous intangible state? The necessity to iterate through service modeling cycles leads to the conclusion that a service, no matter how physical and established it is, will likely revert to an intangible state down the road. Subsequently, it will find its way back to the production environment to continue carrying out its operation. This path is not uncharacteristic of a software product. In fact, we often find that a service is “cloned” and simultaneously appears in two environments: in a production environment to ensure business or technological continuity, and in a design environment in which it is being examined for future enhancements. Our service-oriented modeling practice advocates the transformation of a service from one state to another to maximize analysis, design, and architectural flexibility. This modeling elasticity often facilitates business agility, due to the service metamorphosis model. Exhibit 1.5 illustrates this concept. It depicts a service-oriented asset that undergoes four transformations: Conceptual Service Design Service Solution Service Analysis Service EXHIBIT 1.5 SERVICE-ORIENTED METAMORPHOSIS SCENARIOS
- 37. 12 Ch. 1 Introduction from a conceptual service to analysis, to design, and finally to solution service. Note that a solution service can also revert to the conceptual, analysis, and design service states. From Solution Back to Conceptual Service. Under what circumstances should a solution ser- vice be transformed from its physical state back to an intangible formation—a conceptual service? The scenario, under which it may be required to treat a concrete service as an abstraction, is char- acteristically related to service redesign initiatives driven by changing business or technological requirements. Imagine a customer support service that must undergo functionality modification in light of a newly introduced electronic bill-payment feature. Or a fundamental change to a business model of an equity trading firm whose mission is to launch a new fixed-income line of products. Obviously, these reengineering efforts would require design and architecture teams to identify new concepts and expand on the existing ones. These efforts pertain to small- or large-scale projects. Thus, the urge to reevaluate a concept on which a solution service is based is a substantial undertaking for any organization; a concrete service that must undergo a “surgery” of this nature is in essence set to restart its development life cycle. This reincarnation would also require reevaluation of the service’s initial technology or an implementation that it is founded on. Exhibit 1.6 depicts the four major reasons why a solution service may devolve into a con- ceptual service: modification to business or technological requirements, modification to business model and mission, concept reevaluation, and restructuring and reengineering. From Solution Back to Analysis Service. Service reengineering initiatives do not always require the transformation of a solution service to its initial state—conceptual service. In many instances, the physical service’s conceptual foundation may be sound enough and will not require altering the concepts it presents. However, if a solution service that executes a business or technological solution requires a functionality reevaluation, we should consider reverting it to its analysis state. Why would an organization reexamine the performance inadequacies of a solution ser- vice? The chief reason is related to a particular service operation or another as well as to the collaborative efforts of services to provide a solution. For example, imagine the dissatisfaction Conceptual Service Solution Service Restructuring and Reengineering Modification to Business or Technological Requirements Concept Reevaluation Modification to Business Model and Mission EXHIBIT 1.6 SOLUTION TO CONCEPT TRANSFORMATION
- 38. Modeling Services Introduction: A Metamorphosis Embodiment 13 Analysis Service Solution Service Solution Reevaluation Granularity Alignment Functionality Redundancy Reduction Reusability Enhancement EXHIBIT 1.7 SOLUTION TO ANALYSIS SERVICE TRANSFORMATION that can be caused to a banking institution consumer who receives a monthly statement that includes savings and checking account information but excludes trading account transactions. Larger-scale business initiatives can also spur solution reevaluation through pursuing analysis activities. These activities can be triggered by events such as a business expansion requiring additional functionality, application decommissioning, or even a merger or acquisition. Other driving aspects behind the transformation of a solution service to an analysis asset are related to reusability enhancement, reduction of functionality redundancy, and even perfor- mance improvement. We can achieve these goals by reexamining a solution service’s internal and external structures and validating its granularity. Granularity pertains to the level of business or technological functionality and the number of processes executed by a service. A coarse-grained service contains a large number of pursued activities. Conversely, a smaller-scale service that offers fewer processes is known as a fine-grained entity. Thus, reanalyzing service granularity would enable us to fine-tune its size and the scale of its functionality. Exhibit 1.7 illustrates the four major reasons for the transformation of a solution service into an analysis entity: (1) granularity alignment, (2) reusability enhancement, (3) functionality redundancy reduction, and (4) solution reevaluation. From Solution to Design Service. A solution service should be reverted back to its design state if a contract with its corresponding consumer is about to be modified. More specifically, this transformation should take place if requirements dictate modification to a service’s collabora- tion, interaction, and integration with its peer services and subscribing consumers. This alteration of service behavior obviously can influence the coexistence conditions in a service community. “Behavior,” for that matter, is associated with business or technical functionality activities man- aged and executed during transactions. This includes frequency of message delivery, coordination of message transmissions, reaction to message requests and responses, management of service availability, and even the method by which a service manages allowable consumption rates. The following three major conditions suggest redesign of a solution service: 1. Changes in associations between services due to message exchange route alterations, the consolidation or decommission of a service that may affect the operating environment,
- 39. 14 Ch. 1 Introduction Design Service Solution Service Transaction Remodeling Revision to Service Visibility and Accessibility Modification to External Structure and Packaging Alteration to Service Relationship Service-Consumer Contract Changes EXHIBIT 1.8 SOLUTION TO DESIGN TRANSFORMATION and the addition of a service that delivers new functionality. These aspects may influence a service’s accessibility and visibility in the environment in which it operates. 2. Changes that influence external service structures and a packaging solution that is deployed to production. External structures pertain to an overall logical composition of a solution in which services are arranged in certain formations (patterns) to achieve a design strategy, such as interoperability, reusability, asset consolidation, and loose coupling. This stylized arrangement of solution services is discussed in greater detail in Chapter 13. 3. Changes to business or technological functionality that triggers transaction redesign or enhancements, which characteristically would require reorchestration of transaction activ- ities. Orchestration is typically affiliated with the overall workflow of message exchange between consumers and services. This includes coordination of message exchange oper- ations and synchronization of message request and response activities. Exhibit 1.8 illustrates the major conditions that lead to the redesign of solution service: revision to service visibility and accessibility, modification to external structure and packaging, contract changes, alteration to service relationship, and transaction remodeling. SERVICE-ORIENTED MODELING DISCIPLINES: INTRODUCTION A modeling discipline is a field of knowledge that offers best practices, standards, and policies to facilitate service-oriented development activities during a service’s life cycle. We typically practice modeling disciplines prior to a service’s construction and deployment to a production environment. We follow modeling discipline policies to avoid premature commitments to large budget allocations and lengthy service development periods. Modeling disciplines also enable us to analyze business and technological solution propositions formulated in a project inception phase to satisfy business and technological requirements. Service-oriented modeling disciplines identify the core processes in which business and IT personnel must be engaged when producing design and architectural artifacts. These may include a variety of project deliverables, such as diagrams, charts, and documents. In addition, we are commissioned to prepare a working prototype, a software executable that implements some business or technological functionality regarded as a core challenge of the modeling process; this
- 40. Service-Oriented Modeling Disciplines: Introduction 15 Service-Oriented Conceptualization Service-Oriented Discovery and Analysis Service-Oriented Business Integration Service-Oriented Design Conceptual Architecture Service-Oriented Modeling Disciplines Logical Architecture EXHIBIT 1.9 SERVICE-ORIENTED MODELING DISCIPLINES is known as proof-of-concept. These deliverables will be handed to the service construction and deployment teams later on in the service-oriented development life cycle. (The service life cycle is described in detail in Chapters 2 and 3.) What are these modeling disciplines that must be rigorously followed throughout the ser- vice development life cycle? Service-oriented modeling disciplines intrinsically focus on six areas of expertise, as depicted in Exhibit 1.9: (1) service-oriented conceptualization, (2) service-oriented discovery and analysis, (3) service-oriented business integration, (4) service-oriented design, (5) conceptual architecture, and (6) logical architecture. These disciplines are preliminarily presented in the sections that follow and are discussed in detail throughout the book (see Chapters 4 through 16). SERVICE-ORIENTED CONCEPTUALIZATION. The service-oriented modeling process starts from the service conceptualization phase in which the driving concepts behind future solution services are identified. But here the focus is not on concrete software implementation. What is required is to establish a set of abstractions, a general terminology that offers solutions to business or technological requirements. It is important to remember that the conceptualization discipline advocates following a concept discovery methodology and process that ultimately yields intangible service-oriented assets known as conceptual services. Exhibit 1.10 illustrates the two major milestones in the service conceptualization process: attribution analysis and conceptual service identification. (For more about the service-oriented conceptualization process, refer to Chapters 4 and 5, which provide a step-by-step activity guide and a set of deliverables recommended by this discipline.) Attribution Analysis. To be able to efficiently ascertain concepts, it is necessary to scrupulously study business requirements, problem domain statements, and product specification documents to facilitate remedies to business or technological concerns. This inspection process requires that we identify the various attributes that a software product must possess. Hence, the attribution analysis process yields a set of core attributes that will be utilized to identify conceptual services. Conceptual Services Identification. As a part of the conceptual services identification process it is necessary to 1. Ascertain conceptual services by utilizing the core attributes set that is established in the attribution analysis phase. This derivation process also facilitates the establishment
- 41. 16 Ch. 1 Introduction Service-Oriented Conceptualization Activities Attribution Analysis Conceptual Service Identification EXHIBIT 1.10 SERVICE-ORIENTED CONCEPTUAL MODELING PROCESS of service taxonomies that can serve as organizational common language and glossary to enable future service categorization activities. 2. Find out how concepts are related to each other in terms of their business context and the process they embody. This concept association activity would enable us to understand service commonalities, analyze dissimilarities, and even foster reusability strategies early in the game. 3. Identify conceptual service internal and external structures. The most rudimentary forma- tion is the atomic structure, which presents an indivisible conceptual service. The internal structure pertains to containment aspects of a conceptual service and its capacity to aggre- gate other concepts named composite structure. Conversely, the external service structure identifies formation of service groups known as the service cluster. SERVICE-ORIENTED DISCOVERY AND ANALYSIS. The service discovery and analysis process is yet another discipline that enables us to continue identifying services that can contribute to a business or technological solution. We pursue this goal by analyzing the business and technological propositions presented thus far. More important, service-oriented analysis best practices advocate that we verify that the proposed service abstractions—the conceptual services devised in the conceptualization phase—do indeed provide a viable and valuable solution to the arising business or technological problems. But the conceptual services that we have discovered so far may not provide a complete remedy to an organizational concern. Therefore, the general rule of thumb should be to continue to inspect existing legacy software assets and examine their capability to augment the solution that is being proposed. To accomplish this task, all service-oriented assets that participate in a solution are regarded as analysis services and engage in three service-oriented discovery and analysis activities, as depicted in Exhibit 1.11: service typing and profiling, service analysis, and service analysis modeling. Chapters 6, 7, and 8 discuss these processes in detail and elaborate on various discovery and analysis best practices. Service Typing and Profiling. To be able to efficiently manage an organizational service port- folio and identify a service’s potential contribution to a solution—either a conceptual or a legacy asset—we should be engaged in a service classification process. This service typing activity
- 42. Service-Oriented Modeling Disciplines: Introduction 17 Service-Oriented Discovery and Analysis Activities Service Typing and Profiling Service Analysis Service Analysis Modeling EXHIBIT 1.11 SERVICE-ORIENTED DISCOVERY AND ANALYSIS MODELING PROCESS enables us to label a service based on its organizational identity and business or technological context, its internal structure, and its origin. The information that is collected by this process will facilitate the establishment of a service profile that can be utilized in future projects and business ventures. Service Analysis. The service-oriented analysis process is the next activity that we need to pursue. Here we determine whether a service is viable to participate in the solution proposition. To accomplish this task we start with a service granularity assessment that reveals the business and technological functionality that each participating service contributes to the solution. We then continue with an analysis process that both validates the practicality of our services and explores service reusability, loose coupling, and asset consolidation opportunities. Service Analysis Modeling. The analysis modeling activity concludes the service-oriented dis- covery and analysis process. The provided language is employed to facilitate a service analysis proposition diagram that captures aggregated and distributed service formations and identifies a collaborative service process scheme that proposes a solution to a problem that is being addressed. This modeling process fosters reuse of organizational software assets by utilizing enterprise legacy software and even organizational concepts represented by conceptual services. SERVICE-ORIENTED BUSINESS INTEGRATION. A service-oriented business integration process is a discipline that should be practiced continuously throughout the service development life cycle. This is an ongoing activity that assures a close tie between the business and technology organizations. Most important, it fosters alignment between technological direction and an enter- prise’s business model and business strategy. But how can services be integrated with business imperatives? What does it mean to “align” an organizational technology strategy with business necessities? The answers to these questions have been studied by various institutions, and the conclusions were straightforward: To enable efficient integration between business and technology initiatives, enterprise business architecture practices must exist. What is business architecture and how can it facilitate service-oriented business integration activities? Business architecture is simply organizational best practices and standards that describe what type of firm-wide architectures must exist for an enterprise to promote its business and
- 43. 18 Ch. 1 Introduction Service-Oriented Business Integration Activities Contextual Business Integration Structural Business Integration Business Integration Modeling EXHIBIT 1.12 SERVICE-ORIENTED BUSINESS INTEGRATION MODELING PROCESS increase revenue. It is “architecture about architectures.” This is a business framework that not only depicts high-level business requirements but also identifies business functions, activities, and processes, along with business domains such as lines of business, geographic locations, and management control structure. Exhibit 1.12 illustrates the three major activities that make up the service-oriented business integration process: contextual business integration, structural business integration, and business integration modeling. We regard all service-oriented assets that participate in a business integration venture as analysis services. Readers can learn more about these mechanisms and their best practices in Chapters 9, 10, and 11, which elaborate on service-oriented business integration process and modeling techniques. Contextual and Structural Business Integration. The service-oriented business integration dis- cipline advocates that we integrate our discovered services with two distinct views of our organizational business architecture: (1) a contextual perspective, in which we align our ser- vices with the enterprise business model and business strategies and (2) a structural perspective, which typically depicts the various business domains, such as lines of business and organizations, and business federation structures, such as geographic locations and management control. Business Integration Modeling. Finally, the service-oriented business integration discipline offers an integration language that can facilitate various views of service alignment with business architecture perspectives. Here, the services that integrate with business domains are aligned with lines of business, business organizations, existing business products, enterprise business model, and business strategies. SERVICE-ORIENTED DESIGN. The service-oriented design discipline is a logical perspective of the modeling process. It represents a wireframe version of the solution that is being proposed. “Wireframe” means simply connecting the dots by planning the message and information exchange flow between services and their corresponding consumers—this is typically dictated by the con- tracts that these involved parties committed to. The design modeling discipline also facilitates the establishment of logical relationship, interface, interaction, collaboration, and structural aspects of the participating consumers and services in the final design artifacts. Here, the focus is on the
- 44. Service-Oriented Modeling Disciplines: Introduction 19 Service-Oriented Design Activities Service Relationship Modeling Logical Structure Modeling Service Behavioral Modeling EXHIBIT 1.13 SERVICE-ORIENTED DESIGN MODELING DISCIPLINE PROCESS capacity of services and consumers to comply with the SLA established prior to the modeling phase. Exhibit 1.13 illustrates the three major service-oriented design modeling activities that establish the relationship, structure, and behavioral logical design aspects: service relationship modeling, logical structure modeling, and service behavioral modeling. These service-oriented design modeling aspects are discussed primarily in Chapters 12, 13, and 14. There readers will find the modeling implementation detail and best practices that will guide their service design phase. Service Relationship Modeling. One of the most important aspects of the service-oriented design discipline is the various associations that a service maintains with its peer services and consumers. The major best practices and standards offered by the design modeling discipline address the following service relationship design concerns: • How can we efficiently coordinate message and information exchange between consumers and services? • How can we manage public exposure of services and yet grant safe access to subscribed consumers? • Can we isolate services by limiting their visibility? • How can we design an overall relationship view of our participating service-oriented assets? Logical Structure Modeling. Remember, the relationship aspect of our service-oriented design, discussed previously, does not address an overall view of all the services and consumers that par- ticipate in a solution. Therefore, besides the service association discovery activity, it is also neces- sary to represent the solution that is being proposed from a structural perspective. Specifically, this effort pertains to building a logical formation, a design composition in which services are “glued” together to form a packaged structure that proposes a design modeling strategy. This approach pertains to service reusability, loose coupling, and solutions to interoperability challenges. Service Behavioral Modeling. The service-oriented design discipline advocates that we also view a service and consumer interaction from a behavioral perspective; meaning the logical
- 45. 20 Ch. 1 Introduction design paradigm must also present business and technical functionality that services offer to their subscribed consumers. Therefore, the design modeling discipline advocates that such a perspective should be described by a transaction context. A transaction embodies service functionality, activ- ities, message coordination, and interaction. These aspects are managed by message orchestration between service-oriented assets. CONCEPTUAL AND LOGICAL ARCHITECTURE. What does it mean to architect a service-oriented environment? What are the major activities advocated by the service architecture modeling dis- cipline? The service architecture process not only relies on conceptualization, analysis, business integration, and design artifacts; it also combines all the deliverables to create a service and consumer community. A service-oriented ecosystem is established in which services, consumers, and their empowering platforms can coexist, collaborate, and interface to provide viable busi- ness and technology solutions. Yes, we are engaged in an architectural endeavor that simulates a deployment environment, a production landscape that fosters our business model and strategies. We no longer address internal service structures, we merely tackle interaction and collaboration challenges between packaged solutions. This process offers two major architecture modeling dis- ciplines, as depicted in Exhibit 1.14: the conceptual and the logical. For additional information, refer to Chapters 15 and 16, which provide in-depth service architecture modeling mechanisms and best practices. Conceptual Architecture Modeling. The underlying physical construct of an architectural blue- print must be a sound technological environment that complies with architecture strategies, best practices, and standards. But even before the tangible aspects of a proposed architecture can be addressed, a strategy and a general direction must be devised that provide guidance for future technological implementation. The service-oriented conceptual architecture process is designed to undertake such tasks. This activity can assist in the discovery of the main architecture concepts that can drive future development and production projects. The architecture abstraction discovery process can even start at the inception phase of a given project and continue throughout the development life cycle. Here, architecture abstractions are discovered that describe the technological environment. It is simply a matter of generalizing technology needs to facilitate an implementation plan for the future production landscape. These Service Architecture Activities Conceptual Architecture Modeling Logical Architecture Modeling EXHIBIT 1.14 SERVICE ARCHITECTURE MODELING DISCIPLINE PROCESS
- 46. Modeling Environments 21 architecture imperatives may include service-oriented assets, such as third-party vendor products, existing services, middleware, and software platforms. Logical Architecture Modeling. The other important driving aspect of the service-oriented architecture modeling discipline is a logical architecture perspective in which asset utilization, consumption, reusability, interoperability, and loose coupling best practices are being addressed. This process is chiefly concerned with the logical aspect of the production environment, in which service-oriented assets (services, legacy applications, language platforms, and middleware) must coexist and collaborate. Therefore, an asset utilization diagram provides detailed interaction between the deployed software packages and further elaborates on consumption and reusability requirements of a logical architecture. MODELING ENVIRONMENTS A modeling environment is not necessarily a physical location where the service-oriented model- ing process takes place. In fact, it is a management framework that not only facilitates practicing service-oriented modeling disciplines, but also leads to recruiting personnel with the right exper- tise to manage the modeling process. To better understand a modeling environment, remember that each modeling discipline cannot be practiced in a vacuum. Surroundings are the major contributors to modeling activities. These may include modeling facilities such as software modeling tools, training aids, available documentation, and even a laboratory to test modeling assumptions. Thus, a modeling environment is about the four Ps: people, planning, process, and policies. People denotes the personnel involved in guiding and enforcing modeling disciplines. These are typically the organizational center of excellence group or the SOA governance organization. In addition, business and technology personnel are also a part of the modeling efforts. The planning identifies the strategic or tactical aspects of the process and the required deliverables of the corresponding modeling discipline. These can include project plans, strategy documents, design and architectural blueprints, and diagrams. The process aspect is related to the sequence of activities that business and technology personnel pursue to achieve modeling goals. In addition, the policies pertain to how a solution can be proposed in the environmental framework. This reflects the management perspective, checks and balances, control of a modeling environment, and modeling discipline best practices and standards. The service-oriented modeling paradigm supports three major modeling environments: conceptual, analysis, and logical, as depicted in Exhibit 1.15. Note that each of these frameworks Conceptual Environment Analysis Environment Logical Environment Service Conceptualization Discipline Service Discovery and Analysis Discipline Service Design Discipline Conceptual Architecture Discipline Business Integration Discipline Logical Architecture Discipline EXHIBIT 1.15 MODELING ENVIRONMENTS AND THEIR CORRESPONDING DISCIPLINES
- 47. 22 Ch. 1 Introduction also facilitates their corresponding modeling discipline activities. For example, the conceptual modeling environment provides a supporting framework for the discovery of conceptual services when one pursues the service conceptualization discipline. In the same fashion, the analysis environment facilitates all service discovery and analysis and business integration discipline tasks. CONCEPTUAL ENVIRONMENT. An established methodology that can facilitate the formaliza- tion of undocumented ideas and propose solutions to enterprise concerns is a necessity for most organizations. A conceptual environment provides a management framework that promotes proper analysis of the problem domain and business and technical requirements and also assists with doc- umenting solution propositions. This framework intrinsically drives two major service-oriented modeling initiatives that are pursued at different times during the service life cycle: constituting enterprise conceptual services during the service-oriented conceptualization phase, and establish- ing architectural concepts devised during the conceptual architecture process. The major activities that a conceptual environment can assist with include: • Facilitating the studies of the organizational business model, business strategies, and problem domain. This effort includes inspecting the state of business, business analysis, and business activities. • Involving business and technology personnel in whiteboard and conceptualization sessions to formalize ideas and establish organizational concepts. This may include generaliza- tion of problems, abstraction identification, and consolidation of ideas that emerge from various organizational sources, such as people, business processes, and existing docu- mentation. • Helping business and service-oriented architects, modelers, and developers to establish enterprise conceptual services. • Facilitating the conceptual architecture process, in which technological abstractions are identified and categorized. • Enabling the constitution of an organizational service-oriented taxonomy consisting of conceptual services and architectural concepts and managed by an asset portfolio manager software package. ANALYSIS ENVIRONMENT. The analysis environment facilitates the transformation of a service from its initial conceptual state to an analysis service for further inspection and categorization. This process is pursued to encourage discovery and profiling activities of services that may participate in a service-oriented solution. The analysis environment framework also provides a platform for analysis modeling, allowing architects, asset portfolio managers, business archi- tects, business analysts, and developers to conduct sessions that yield an analysis proposition model. In addition, the analysis environment management framework supports analysis activi- ties throughout the service-oriented business integration phase, during which business integration modeling disciplines are applied. This alignment activity requires the collaboration of business and IT personnel to identify proper service integration opportunities and to establish a business integration model that depicts the alignment scheme between services and business domains. Consider the following analysis environment facilitation activities: • Fostering research initiatives that identify analysis modeling and visualization tools. • Assisting with asset portfolio analysis to identify service-oriented asset candidates that can participate in a solution. This activity typically involves portfolio managers, product managers, business analysts, and architects.
- 48. Service-Oriented Modeling Framework 23 • Coordinating analysis sessions to enable analysis operations such as service decomposi- tion, aggregation, and unification. • Facilitating analysis modeling sessions to devise an analysis proposition. These activities yield a service-oriented analysis model that can be further utilized in the design and architecture phases. • Encouraging alignment of business and technology strategies that can facilitate proper service-oriented business integration. LOGICAL ENVIRONMENT. A logical environment supports the transformation of analysis ser- vices into more tangible assets called design services. This environment also depicts a visual view of the logical landscape in which service relationship, structures, and behaviors illustrate a wireframe solution to an organizational concern. Moreover, on the service architecture front, the logical environment framework facilitates the creation of a logical architecture that depicts an integrated service-oriented ecosystem where packaged services collaborate to provide a viable solution. This includes the following activities: • Conducting service-oriented design and architecture training sessions to promote best practices and standards • Encouraging research integrated development environments (IDEs) that offer service rela- tionship establishment capabilities, service structure modeling, and transaction modeling • Utilizing software tools to enable efficient message orchestration and expression of logic flow • Providing laboratory facilities so that a proof-of-concept can be conducted to examine the proposed service ecosystem • Facilitating the establishment of contracts between consumers and their corresponding services SERVICE-ORIENTED MODELING FRAMEWORK Before moving on to the chapters that describe in detail the modeling disciplines and their activi- ties, let us take an overall view of the service-oriented modeling framework. This work structure is chiefly a high-level map depicting the various components that contribute to a successful service-oriented modeling approach. It illustrates the major elements that identify the “what to do” aspects of a service development scheme. These are the modeling pillars that will enable a practitioner to craft an effective project plan and to identify the milestones of a service-oriented initiative—either a small- or large-scale business or a technological venture. Exhibit 1.16 depicts the four sections of the modeling framework that identify the general direction and the corresponding units of work that make up a service-oriented modeling strategy: practices, environments, disciplines, and artifacts. Remember, these elements uncover the context of a modeling occupation and do not necessarily describe the process or the sequence of activities needed to fulfill modeling goals. These should be ironed out during the project plan that typically sets initiative boundaries, timeframe, responsibilities and accountabilities, and achievable project milestones. MODELING PRACTICES. A framework practice describes an occupation, a major function that should be pursued to drive modeling activities. The practitioners, for that matter, are the busi- ness and technology personnel engaged in analysis, design, and architectural aspects of services. They also offer vital input into the management process of the modeling efforts. A collabora- tive approach to furnishing solutions in the business and technology–specific area of expertise would yield successful modeling artifacts. The typical participants who address the concerns of
- 49. 24 Ch. 1 Introduction Abstraction Practice Realization Practice Conceptual Environment Service Conceptualization Discipline Conceptual Architecture Discipline Business Integration Discipline Analysis Environment Service Design Discipline Logical Architecture Discipline Logical Environment Conceptual Service Conceptual Architecture Logical Architecture Physical Environment Solution Service Physical Architecture Modeling Practices Modeling Environments Modeling Disciplines Modeling Artifacts Modeling Solutions Analysis Service Design Service Service Discovery and Analysis Discipline EXHIBIT 1.16 SERVICE-ORIENTED MODELING FRAMEWORK a framework practice are business and technology managers, service-oriented strategists, asset portfolio managers, business analysts, business architects, technical architects, developers, and, of course, software modelers, such as service and database modelers. This service-oriented modeling framework identifies two major modeling practices that drive and influence all modeling activities during a project or any business initiatives: abstraction and realization. ABSTRACTION PRACTICE. What are the major modeling concerns addressed by the abstraction practice? Why is such a practice vital to any modeling effort? Every software development initia- tive will reveal new ideas and establish the driving concepts that the project and its deliverables will be founded on. Remember, the major concerns of the abstraction practice, on the one hand, revolve around the discovery aspects of services, and on the other, depict an architectural envi- ronment based on abstractions. These two major activities may not take place in any sequence, but they are well embedded in the abstraction practice activities category. The major questions that are typically asked by those engaging in the abstraction practice are • What are the major business concerns that drive this initiative? • What do the business or technological requirements recommend? • What services do we actually build? • What assets do we reengineer? • What kind of metaphors do we use to describe our services? • How do we conceptualize our architectural environment? • How do we identify our service architecture needs and landscape? • Which personnel are involved?
- 50. Service-Oriented Modeling Framework 25 Separating Concerns and Generalizing Problems. The service-oriented abstraction practice enables practitioners to generalize private instances of organizational problems and ignore, for the time being, implementation details of the current services and the supporting technological environment. They will be able to break down organizational concerns into more manageable abstracted areas of interests. This process is known as separation of concerns. Practitioners will also be encouraged to inspect the problem domain and understand the “big picture” scenario by analyzing the business imperative, the business model of their organization, and the strategies designed to generate revenue for the organization. Employing a Horizontal Modeling View. The abstraction practice, also known as horizontal practice, typically engages the cross-organization stakeholders that represent various silo oper- ations in the enterprise to collaborate on service-oriented modeling activities. Imagine how beneficial it would be to involve representatives from different lines of business to discuss how they can collaborate to foster asset reusability opportunities and to encourage function- ality redundancy and consolidation of future assets. They should also be able to identify mutual organizational concerns and propose remedies that can be reused across the enterprise. Imagine how advantageous it would be if these business and technological practitioners partner to meet service interoperability challenges and to enable a holistic view of all modeling assets regardless of their origin, geographic location, or empowering technologies. Visualizing Abstraction Practice Process and Artifacts. Can the abstraction practice enable one to visualize the activities and deliverables involved? Can concepts be visible? Indeed, concepts are invisible entities. They originate from peoples’ ideas and propositions. But the abstraction process should be mechanical and well formulated, driven by a well-defined process and should employ tools to enable visualization of intangible software assets. By “mechanical,” we mean that the abstraction process employs conceptualization best practices that yield conceptual services, which, despite their intangibility, are treated like the other valuable assets in an organization. Employing Corresponding Service-Oriented Modeling Disciplines. To ensure the success of the service-oriented modeling process, modeling practices must be guided and enforced by mod- eling disciplines. They were previously introduced in the Service-Oriented Modeling Disciplines: Introduction section, and they are discussed in further detail in Chapters 4 through 16. But these disciplines cannot operate in a vacuum. They require one to create the proper modeling environ- ment. What are the corresponding disciplines of the abstraction practice? Take a second look at Exhibit 1.16. The depicted abstraction practice spans two modeling environments: • Conceptual environment. As previously discussed in the section on service-oriented modeling environments, this supporting landscape facilitates two distinct disciplines that are chiefly concerned with the service-oriented conceptualization process. These are the best practices and standards that assist with the “how to do” aspects of a conceptual environment: First, the service-oriented conceptualization discipline facilitates the identi- fication of conceptual services and establishment of organizational taxonomies. Second, the conceptual architecture discipline provides guidance for the discovery of technolog- ical abstractions that describe architectural imperatives and service-oriented assets, such as services, middleware, and platforms. • Analysis environment. Remember, some activities that are pursued in the analysis envi- ronment are also regarded as a part of the abstraction practice, as is noted in Exhibit 1.16. The abstraction practice advocates that we pursue conceptualization activities and that we also identify, type, profile, and evaluate services by complying with service-oriented discovery and analysis disciplines, which are facilitated by the analysis environment. Fur- thermore, some of the service-oriented business integration discipline activities also fall
- 51. 26 Ch. 1 Introduction within the abstraction practice domain. Here we are commissioned to align our services with business strategies and structures such as geographic locations and even management structure. REALIZATION PRACTICE. The realization practice typically starts when the abstraction practice runs its course, during which most ideas have been formalized and established as organizational concepts. These abstractions then transform into more tangible software entities that are regarded as logical units of analysis. The realization practice addresses these tangibility aspects that are articulated by the logical design of services, such as message exchange patterns, business or technological functionality, service structure, and the overall workflow and process orchestration. The questions that are typically asked during the realization process are: • What is the process of transforming an analysis service to a design service? • What does a logical design process entail?; What is a logical architecture? • Who is involved? The realization practice obviously overlaps with the abstraction practice because of some process commonalities that are typically pursued in both domains. This pertains to activities that are managed during the service-oriented discovery and analysis phase and business integration. Creating a Virtual World. The ultimate goal of the realization practice is to transform intan- gible entities into more concrete software assets. However, this process should stop short of the construction of physical services. This practice is not about source-code building and deployment to production. Its main charter is to depict a virtual world of software assets that simulates a prospective technological solution that may be materialized by the end of the service life cycle. This is a virtual world in which services not only interact and collaborate to achieve a defined goal but also provide a supporting environment that empowers the business and technological functionality. Centering on the Solutions. Modeling shortsightedness can only hamper the efforts to find a conclusive resolution to a business or technological concern. But along with recognizing what the large-scale problems are, we must first pinpoint the burning issues facing an organization. Furthermore, to be able to focus on a particular solution, business or technological requirements should be the driving motivation behind any modeling activity. In particular, these imperatives should guide modeling practitioners to tackle vital aspects of a solution and avoid propositions to a wide range area of concerns. Employing Corresponding Service-Oriented Modeling Disciplines. The realization process sup- ports two major modeling environments: analysis and design. As discussed previously, some analysis activities are pursued during the abstraction process, but they are also common to the realization practice. Therefore, the modeling analysis environment and its corresponding dis- ciplines are regarded as shared modeling aspects for both modeling practices. The abstraction practice accentuates the discovery and establishment of services, while the realization practice yields design services that resemble a more concrete world. • Analysis environment. The analysis environment facilitates analysis activities by em- ploying the service-oriented discovery and analysis discipline. The realization practice, however, focuses more on the analysis modeling part of this discipline, in which an analysis proposition is crafted. (Again, the discovery activities are more of a concern to the abstraction practice that was discussed previously.) Moreover, the analysis envi- ronment enables the service-oriented business integration activities in which services are
- 52. Summary 27 aligned with business imperatives. Here the realization practice is concerned more with the business integration-modeling portion and less with the discovery of business alignment perspectives. • Logical environment. The logical environment facilitates two disciplines that contribute to the design and architecture logical foundation: service-oriented design and logical architecture. These disciplines contribute the most to the formation of a virtual world that mimics the service ecosystem that we are about to construct. PHYSICAL ENVIRONMENT. Service-oriented modeling activities can always be repeated to per- fect the resulting artifacts that the modeling disciplines require for delivery. This perpetual process is called iteration. Iterating through the various disciplines should promote one major modeling agenda: to transform services from their intangible state to concrete entities. There are two major physical artifacts that make up a physical environment: 1. Deployable service-oriented software assets that should be integrated with a production environment. (These tangible entities are called solution services.) 2. A physical architecture that emerges from our logical architecture. This concrete architec- ture depicts an integrated and configurable production environment that typically consists of infrastructure, networks, management facilities such as monitoring and security, and, of course, solution services. SUMMARY The service-oriented modeling driving principles are virtualization, metamorphosis, and literate modeling. Enterprise concepts—foundation software (such as middleware and language platforms), legacy software (such as applications and services), repositories, and utility software—are all conceived as organizational service-oriented software assets. The service-oriented modeling process stakeholders are business and technology personnel that equally share the burden of software development in the organization. They also present two service-oriented modeling perspectives: business and technological views. The service-oriented paradigm recognizes three distinct modeling services: conceptual, analysis, and design. They contribute to the establishment of a physical solution service. There are seven modeling disciples that drive service development efforts: conceptual- ization, discovery and analysis, business integration, design, conceptual architecture, and logical architecture. The service-oriented paradigm supports three modeling environments: conceptual, analy- sis, and logical. The service-oriented modeling framework identifies the “what to do” aspects of a service development environment. Endnotes 1. Journal of Digital Information, Vol. 5, Issue 1, Article No. 298, July 16, 2004. 2. www.en.wikipedia.org/wiki/Virtuality 3. Edsger W. Dijkstra, “On the Cruelty of Really Teaching Computer Science”, December 1988, p. 16. (http://www. cs.utexas.edu/users/EWD/ewd10xx/EWD1036.PDF)
- 54. PART ONE SERVICE-ORIENTED LIFE CYCLE A service is something that originates at a certain time for accomplishing goals that may or may not be achieved. A service is an entity that lives for a certain reason, may endure for a time, and may or may not be retired because of various circumstances. A service is a software solution embodiment that is created in pursuit of resolving a business or a technological problem but is also a piece of implementation that must coexist with other software assets. This journey, which commences at the first appearance of an organizational concern, is shaped by service-oriented modeling disciplines, and concludes as a physical solution, is the crux of the service-oriented life cycle. But how can service-oriented modeling activities influence the course of service evolution? Do services have their own life span? Do they really live and perish? Do we understand how a service evolves during its lifetime? These questions and others are widely debated in today’s service-oriented architecture (SOA) industry, which is still struggling to define services, clarify their behaviors, and identify what is required for their survival. Before we move on to the technical aspects of the service life span, we should understand why life cycles are such compelling frameworks for driving service development. There is nothing “cyclical” about the service life cycle, and as much as we would like them to, services do not live forever. While services continue to evolve and provide value to their con- sumers and greatly contribute to businesses in production environments, they are always subject to perfection and enhancements. This usually requires a second look under the hood to determine whether a service should be ferried back to the drawing board for redesign, re-architecture, and reconstruction initiatives. This repetitive process is called the service life cycle. Exhibit P.1 illus- trates a service life cycle, in which the run-time and design-time sections, respectively, represent service development and production processes. When do services die? Services perish when they no longer provide viable solutions to the problems of business or technology organizations. Service-oriented software entities that become irrelevant to the enterprise—because of business or technology trends and alterations to business models and strategies—should be demoted and eventually discontinued. The demise of enterprise services indicates the termination of their life cycle. Therefore, they should be removed from production environments and replaced with more appropriate solutions. Modeling disciplines are the major contributors to the service life cycle paradigm, in which a service undergoes major transformation during its lifetime. Nonmodeling disciplines that
- 55. Random documents with unrelated content Scribd suggests to you:
- 56. Every day witnessed the death of large numbers by cold and starvation. Those who survived were more like walking skeletons than human beings. They were covered with vermin, and loathsome to behold. Some were so badly frozen that their flesh fell from their bones. Many remained disabled for life. "Oh Religion! what crimes are perpetrated in thy name!" When Mormons speak of the hand-cart company, they shudder and grow pale. All this suffering was the result of an attempt, on the part of the leaders of the church, to save a still larger sum from the emigration fund. It was a speculative experiment, which was never repeated. These people bought their carts with their own money; but on their arrival in Salt Lake, the carts were claimed by Brigham, in behalf of the church, and were afterwards sold from the tithing- office at five dollars each.
- 57. FOOTNOTES: [143:A] Persons who are known to possess property, are called upon to pay for seats in the temple. A lady residing in one of the northern settlements, was cajoled into paying £50 for that purpose. The good lady, upon arriving in Utah, found that the famous temple, in which she had purchased a seat, was scarcely above its foundations. [147:A] Jour. of Dis., Vol. I. p. 340. [148:A] Jour. of Dis. Vol. I. p. 202.
- 58. CHAPTER IX. BRIGHAM AS PROPHET, SEER, AND REVELATOR. Brigham's Position as Head of the Church.—Mormon Theology.—Brigham's Theology, or Utah Mormonism.— Adam as God.—Brigham Young as God.—Human Sacrifice.—Introduction of Polygamy.—Polygamy no part of the original Mormon Religion.—The Revelation, or Celestial Marriage.—The Ceremony of Sealing.— Consequences and Incidents of the Doctrine.—Incest. —Summary of the Mormon Religion. Not only is Brigham Young the temporal head of the church, its chief business agent, and the sole custodian of its funds, but he is the spiritual head, the established fountain, in whom is gathered from on high all spiritual blessings, and from whom they are expected to flow through the various officers of the priesthood, and thus be distributed to the faithful among the masses. Standing in this capacity between the people and the Supreme Being, he is at once Prophet, Seer, and Revelator. As Prophet and Seer, he sees and foretells to the people what is to befall them, as the result of certain courses of action. As Revelator, he reveals and translates, to the comprehension of the people, the hidden will of God concerning them. An acknowledgment of this relationship of Brigham with the Divine Being is made a test of fellowship; as in the case of the Morrisites, who, although they admitted his right to preside over the church as its temporal head, denied him the attributes of prophet and revelator. Hence they were cut off from the church. Acting in this capacity, he not only prescribes a course of conduct for his followers, but promulgates, from time to time, doctrines, to
- 59. be received, believed, and advocated. Thus the theology or creed of the church changes, from time to time, to suit the changing opinions, the whims and caprices, or the passions and lusts, of its head and leader. What is here said, therefore, of the Mormon religion, must be understood in reference to the received doctrines and tenets of the church in former years,—many of which still remain, but incorporated with new dogmas, and any part or all of which are liable at any time to be changed, modified, or entirely overthrown. Mormon Theology. There are many Gods, and they are of both sexes. But to us there is but one God,—the Father of mankind, and the Creator of the earth. Men and women are literally the sons and daughters of God,— our spirits having been literally begotten by God, in the heavenly world, and having been afterwards sent to the earth, and invested with these tabernacles. God is in the form of man. He has a body, composed of spiritual matter. There is no difference between matter and spirit, except in quality. Spirit is matter refined. God is omnipotent, but not personally omnipresent. He is everywhere present by his Holy Spirit. His personality is generally expressed by the phrase, "He has body, parts, and passions." He resides in the centre of the universe, near the planet Kolob. This planet revolves on its axis once in a thousand of our years, and one revolution of Kolob is a day to the Almighty. Jesus Christ was the Son of God, literally begotten by the Father, and had the Spirit of God in the body of a man. After his resurrection, he had a body of flesh and bones only, typical of man's resurrected body. He differs in nothing from the Father, except in
- 60. age and authority,—the Father having the seniority, and consequently the right to preside. The Holy Spirit is a subtle fluid, like electricity. It is the subtlest form of matter, and pervades all space. By its agency all miracles, so called, are performed. Miracles are simply the effects of the operation of natural laws. But they are laws of a higher character than those with which we are acquainted. This Holy Spirit is communicated by the laying-on of hands by one of the properly authorized priesthood, and the recipient is then enabled to perform wonderful things, according to his gift,—some having the gift of prophecy, some of healing, some of speaking in unknown tongues, etc. There are three heavens,—the telestial, the terrestrial, and the celestial. The telestial and terrestrial heavens are to be occupied by the various classes of persons who have neither obeyed nor rejected the gospel. The telestial is typified by the stars,—the terrestrial, by the moon. The celestial, or highest heaven, has for its type the sun, and is reserved for those who received the testimony of Jesus, and believed on His name, and were baptized by one having authority from Him, and who afterwards lived a holy life. The earth, as purified and refined, after the second coming of Christ, is to be the final habitation of those entitled to the glories of the celestial kingdom. Jerusalem is to be rebuilt, and Zion, or the New Jerusalem, is to be built in Jackson County, Missouri, whence the saints were expelled in 1833. There is a fourth class of persons, not entitled to either of these heavens. They are those who sin against the Holy Ghost; that is, those who apostatize after receiving the Holy Spirit. These go into everlasting punishment, to remain with the devil and his angels. The gospel, which people are called upon to obey, in order to gain a place in the celestial kingdom, is,—First, They must believe in
- 61. Jesus Christ as the Son of God, and in His authorized priesthood. Secondly, They must repent of their sins; Thirdly, They must be baptized by immersion for the remission of their sins; and, Fourthly, They must receive the laying-on of hands for the gift of the Holy Ghost. God, having become nearly lost to man, revived His work, by revealing himself to Joseph Smith, and conferring upon him the keys of the everlasting Priesthood,—thus making him the mediator of a New Dispensation, which is immediately to precede the second coming of Christ. All those who recognize the divine authority of Smith, and are baptized by one having authority, are the chosen people of God, who are to introduce the Millennium, and to reign with Christ, on earth, a thousand years. Previous to the year 1852, it was also an orthodox principle of the Mormon religion, that a man should have but one wife, to whom he should be true and faithful. Those who have any curiosity to pursue the subject further, will find these views and doctrines fully explained and illustrated in the religious writings of the Mormons,—of which the following are some of the principal: Book of Mormon; Book of Doctrine and Covenants; Works of Orson Pratt; Key to Theology, by P. P. Pratt; The Only Way to be Saved, etc., by L. Snow; Pearl of Great Price; Voice of Warning, by P. P. Pratt; Catechism for Children, by John Jaques; Deseret News, 14 vols.; Journal of Discourses, 6 vols.; Latter-Day Saints' Millennial Star, London, 26 volumes. Brigham's Theology; or Utah Mormonism. The doctrines taught and practised by the present head of the Mormon Church differ so much from the previously established tenets of the church, that they require a separate consideration. One of the most important innovations upon the established doctrines of the church, is in relation to the Godhead. In April, 1852, Brigham put forth the startling doctrine that Adam is God, and to be
- 62. recognized and honored as such! This announcement created some consternation among the Mormon theologians, and some of them had the courage to oppose it. The following is the "Revelator's" own exposition of this doctrine:— "When the Virgin Mary conceived the child Jesus, the Father had begotten him in his own likeness. He was not begotten by the Holy Ghost. And who is the Father? He is the first of the human family; and when he took a tabernacle, it was begotten by his Father in heaven, after the same manner as the tabernacle of Cain, Abel, and the rest of the sons and daughters of Adam and Eve. . . . It is true that the earth was organized by three distinct characters, namely: Elohim, Yahovah, and Michael, [Adam;] these three forming a quorum, as in all heavenly bodies, and in organized element perfectly represented in the Deity, as Father, Son, and Holy Ghost. "When our Father Adam came into the garden of Eden, he came with a celestial body, and brought Eve, one of his wives, with him. He helped to make and organize this world. He is Michael, the Archangel, the Ancient of Days. He is our Father and our God, and the only God with whom we have to do. . . . Jesus, our elder brother, was begotten in the flesh by the same character that was in the garden of Eden, and who is our Father in heaven." [157:A] It is manifest that Young is not so much at home in theology as when engaged in financial schemes and money speculations. So disgusting and blasphemous are these ideas, and so unacceptable were they, even to Mormons, who were not prepared to see the basis of their religion thus rudely overthrown, that Brigham finally felt compelled to caution the Elders not to preach the new doctrine concerning Deity, until the people should be better prepared to receive them.
- 63. Mahomet is the great exemplar and prototype whom Brigham Young aims to imitate, and doubtless he took from the Koran his ideas about the deity of Adam. Thus in chapter two of the Koran, we have the following:— "And when we said unto the angels, 'worship Adam,' they all worshipped him, except Eblis, [Lucifer,] who refused." From the following affidavit of John Stiles, father of Judge Stiles, formerly one of the United States Judges in Utah, a man of much probity of character, and well known in Salt Lake City as "Father Stiles," it appears that the blasphemous pretensions of Brigham Young do not stop with Adam, but that, among the brethren, he has encouraged a doctrine, which he dare not put in print;—no less than to arrogate to himself the attributes of Deity. "Territory of Utah, Great Salt Lake City. ss. "In the spring of 1856," John Stiles says, "I resided in the 11th Ward of Great Salt Lake City, in the Territory of Utah. I was appointed by the quorum to which I then belonged, as a Missionary High-Priest for the said Ward. My duty was to look after the morals of the people of the Ward, and especially to see that there was no false doctrine taught there. I subsequently found that there were not only immoralities, but also false doctrines among some of the people, as I supposed at the time. Many people believed and taught the doctrine, that Brigham Young was all the God that we were amenable to. I found by opposing that doctrine, that I gave offence to the authorities of the Ward, and was consequently called to answer for my opposition before the Bishop of the Ward,
- 64. although he had no jurisdiction over me. As a High-Priest I was amenable to a higher authority, but not to him. "In a public assembly he wished me to state my views on the question, whether if Brigham Young was not God, who was? I told him I would do so. I rose and stated that my idea of the being of God was expressed in a passage of Scripture, and I need only repeat the passage to explain the idea. The passage was: 'To us there is but one God, the Father, of whom are all things, and we in Him, and one Lord Jesus Christ, by whom are all things, and we by Him.' I subsequently, in explanation, cited this passage of Scripture: 'This is life eternal, that we might know thee, the only living and true God, and Jesus Christ whom thou hast sent.' I then sat down, and the Bishop rose and said: 'Brethren, we perceive that Father Stiles runs round Brigham.' I replied, 'Yes; I do not mention Brigham Young on the same day with God, as of the same Godhead.' His (the Bishop's) First Counsellor, then moved that Father Stiles be cut off from the church. This was seconded by the Second Counsellor. This was proposed to the assembly as a question by the Bishop, and I was cut off accordingly. I subsequently discovered that by my opposition and explanation, I gave offence to the authorities of the Mormon Church, and was cut off from the church and dismissed from the place of Missionary High-Priest of that Ward. I have never been restored as Missionary High- Priest. (Signed,) John Stiles. "Sworn to and subscribed before me at Great Salt Lake City, this April 26th, 1864. "John Titus, Ch. Justice of Utah."
- 65. Another doctrine of a startling character, promulgated by one of Young's counsellors and endorsed by him, is that of human sacrifice for the remission of sins. It was first announced by Jedediah M. Grant, Second Counsellor to the President, in the following language:— "Brethren and sisters, we want you to repent and forsake your sins. And you who have committed sins that cannot be forgiven through baptism, let your blood be shed, and let the smoke ascend, that the incense thereof may come up before God as an atonement for your sins, and that the sinners in Zion may be afraid."[159:A] Again:— "We have been trying long enough with this people, and I go in for letting the sword of the Almighty be unsheathed, not only in word, but in deed."[159:B] In accordance with such bloody teaching, it is said that an altar of sacrifice was actually built by Grant, in the temple block, upon which these human sacrifices were to be made. On the 21st of September, 1856, Grant said:— "I say there are men and women here that I would advise to go to the President immediately, and ask him to appoint a committee to attend to their case; and then let a place be selected, and let that committee shed their blood."[159:C] This horrible proposal to immolate upon the altar of sacrifice the erring saints, was fully endorsed by Brigham Young as follows:— "There are sins that men commit for which they cannot receive forgiveness in this world, or in that which is to come; and if they had their eyes open to see their
- 66. condition, they would be perfectly willing to have their blood spilt upon the ground, that the smoke thereof might ascend to Heaven as an offering for their sins, and the smoking incense would atone for their sins; whereas, if such is not the case, they will stick to them, and remain upon them in the spirit-world. "I know, when you hear my brethren telling about cutting people off from the earth, that you consider it is strong doctrine. It is to save them, not to destroy them. I will say further, I have had men come to me, and offer their lives to atone for their sins. It is true that the blood of the Son of God was shed for sins, through the fall, and those committed by man, yet men can commit sins which it can never remit. As it was in ancient days, so it is in our day; and though the principles are taught publicly from this stand, still the people do not understand them; yet the Law is precisely the same. There are sins that can be atoned for by an offering upon the altar, as in ancient days, and there are sins that the blood of a lamb, of a calf, or of turtle-doves cannot remit, but they must be atoned for by the blood of the man. That is the reason why men talk to you as they do from this stand. They understand the doctrine, and throw out a few words about it."[160:A] But the greatest change of all in the Mormon religion, made by Brigham Young, was the introduction and establishment of polygamy. This was no part of the Mormon system of religion as originally established. On the contrary, it was expressly repudiated by all the Mormon writers and speakers, previous to 1852, and in Europe for some years afterward. The Mormon religion was founded by Joseph Smith and his coadjutors, and the principles and doctrines of the religion were, in
- 67. the first instance, such as they established. The Book of Mormon is the historical foundation, corresponding with the Old Testament of the Christian Bible. Afterward, a volume of revelations to Smith and others was collected and published, called the Book of Doctrine and Covenants. This corresponds to the Christian's New Testament. It may be safely asserted, therefore, that previous to the innovations of Young, the Mormon religion was embodied in these two volumes. Their authority in the church is universal and unquestioned. Let us examine these volumes, and see whether they teach or countenance polygamy. The Book of Mormon nowhere contains a word in favor of it. On the contrary all of its principal characters were monogamists. Such was Lehi, the patriarch of Mormon history. Such also were Ishmael and Nephi.[161:A] That the people of Zarahemla were monogamists, is evident from what is said concerning them on page 146. But we are not left to inference as to the testimony of this volume concerning this practice. On page 119 we have the following:— "Behold the Lamanites, your brethren, whom ye hate because of their filthiness and the cursings which hath come upon their skins, are more righteous than you; for they have not forgotten the commandment of the Lord, which was given unto our fathers, that they should have, save it were one wife; and concubines they should have none; and there should not be whoredoms committed among them. And now, this commandment they observe to keep; wherefore, because of this observance, in keeping this commandment, the Lord God will not destroy them, but will be merciful unto them; and one day they shall become a blessed people."[161:B] Again:—
- 68. "And it came to pass that Riplakish did not do that which was right in the sight of the Lord, for he did have many wives and concubines, and did lay that upon men's shoulders which was grievous to be borne; yea, he did tax them with heavy taxes; and with the taxes he did build many spacious buildings."[162:A] And again:— "And he [Noah] did not walk in the ways of his father. [Zeniff.] For behold, he did not keep the commandments of God, but he did walk after the desires of his own heart. And he had many wives and concubines. And he did cause his people to commit sin, and to do that which was abominable in the sight of the Lord. Yea, and they did commit whoredoms and all manner of wickedness. And he laid a tax of one fifth part of all they possessed." . . . "All this did he take to support himself, and his wives and his concubines; and also his priests, and their wives and their concubines; thus he had changed the affairs of the kingdom."[162:B] "And it came to pass that he placed his heart upon his riches, and he spent his time in riotous living, with his wives and his concubines; and so did also his priests spend their time with harlots."[162:C] As if to place this matter beyond any question, we have the following still more explicit testimony, on pages 115 and 118:— "And now it came to pass that the people of Nephi, under the reign of the second king, began to grow hard in their hearts and indulge themselves somewhat in wicked practices, such as like unto David of old, desiring many wives and concubines, and also Solomon his son." . . .
- 69. "The word of God burdens me because of your grosser crimes. For behold, thus saith the Lord, this people begin to wax in iniquity; they understand not the Scriptures; for they seek to excuse themselves in committing whoredoms, because of the things which were written concerning David, and Solomon his son. Behold David and Solomon truly had many wives and concubines, which thing was abominable before me, saith the Lord: wherefore, thus saith the Lord, I have led this people forth out of the land of Jerusalem, by the power of mine arm, that I might raise up unto me a righteous branch from the fruit of the loins of Joseph. Wherefore, I the Lord God, will not suffer that this people shall do like unto them of old. Wherefore, my brethren, hear me, and hearken to the word of the Lord; for there shall not any man among you have, save it be one wife; and concubines he shall have none; for I, the Lord God, delighteth in the chastity of women. And whoredoms are an abomination before me; thus saith the Lord of Hosts."[163:A] Here it is stated as coming from God himself, that the polygamy and concubinage of David and Solomon were abominable before the Lord. And yet we every day hear David and Solomon, as well as Abraham, Jacob, and others, cited by those practising polygamy, as their illustrious prototypes, whose example is worthy of all imitation. Orson Pratt, the ablest writer on Mormon theology, is compelled to admit that the Book of Mormon is opposed to polygamy. He says: — "Do you believe that the Book of Mormon is a divine revelation? We do. Does that book teach the doctrine of plurality of wives? It does not. Does the Lord in that book forbid the plurality doctrine? He forbid the ancient Nephites to have any more than one wife."[163:B]
- 70. Elder Pratt then endeavors to blunt the force of this testimony in the following manner:— "Why were the ancient Nephites restricted to the one- wife system? Because, first, the number of males and females among them, at the time the command was given, was about equal. Secondly, there was no probability that judgments, wars, or any other calamities which were to befall their nation, would produce a disproportionate number of males and females. Thirdly, this small remnant of the tribe of Joseph, were, at that time, about equally righteous; and one was about as capable of raising up a family in righteousness as another. And, lastly, the Lord himself informs them, in the same connection with the quotation which I have just made, that if He would have them practise differently from what He had previously taught them, it must be by His command."[164:A] Thus, in the attempt to weaken the force of the evidence furnished by the Book of Mormon against polygamy, Pratt acknowledges, in the most explicit manner, the validity of the argument against it, founded upon the equality in the numbers of each sex. Two of the four reasons why the Nephites were to retain monogamy, relate to the equality in the numbers of the sexes. But there is a substantial equality in the numbers of the sexes, not only in the United States, but in Utah Territory. (See U. S. Census.) Let us now turn to the Book of Doctrine and Covenants, and see if we can find in that volume any authority for polygamy. The following passages will determine the question:— "Thou shalt love thy wife with all thy heart, and shalt cleave unto her, and none else; and he that looketh upon a woman to lust after her, shall deny the faith, and shall not have the spirit; and if he repents not he shall be cast out."[164:B]
- 71. Again. In 1845, the year after Smith's death, an Appendix was authoritatively added to the Book of Doctrine and Covenants, containing the following, which is extracted from the section entitled "Marriage":— "2. Marriage should be celebrated with prayer and thanksgiving; and at the solemnization, the persons to be married standing together," etc., "he [the person officiating] shall say, calling each by their names, 'you both mutually agree to be each other's companion, husband and wife, observing the legal rights belonging to this condition; that is, keeping yourselves wholly for each other, and from all others, during your lives.' And when they have answered 'yes,' he shall pronounce them 'husband and wife,' in the name of the Lord Jesus Christ and by virtue of the laws of the country, and authority vested in him. . . . "4. . . . Inasmuch as this church of Christ has been reproached with the crime of fornication and polygamy; we declare that we believe that one man should have one wife; and one woman but one husband, except in case of death, when either is at liberty to marry again."[165:A] Can anything be more explicit than this? Polygamy is not only expressly repudiated by the church, but is classed by the side of fornication as a crime. Thus we find that polygamy is contrary to both books of the Mormon Bible. That it is, in fact, strongly condemned in those volumes. It is, therefore, no part of the Mormon religion, as given to the world by Joseph Smith. But polygamy is practised in Utah. Whence did it arise, and upon what foundation does it rest?
- 72. Like slavery, and all other great social evils, it had its origin, doubtless, in an abuse of the passions of man. It was first publicly announced and recommended in Utah Territory on the 29th of August, 1852, by Orson Pratt and Brigham Young, at a politico-religious meeting, held in Great Salt Lake City. On that occasion, President Young said:— "You heard Brother Pratt state, this morning, that a Revelation would be read this afternoon, which was given previous to Joseph's death. It contains a doctrine a small portion of the world is opposed to; but I can deliver a prophecy upon it. Though that doctrine has not been preached by the Elders, this people have believed in it for years. "The original copy of this Revelation was burnt up. William Clayton was the man who wrote it from the mouth of the Prophet. In the mean time it was in Bishop Whitney's possession. He wished the privilege to copy it, which Brother Joseph granted. Sister Emma (wife of Joseph Smith) burnt the original. The reason I mention this is, because that the people who did know of the Revelation, suppose it was not now in existence. "The Revelation will be read to you. The principle spoken upon by Brother Pratt this morning, we believe in. . . . "Many others are of the same mind. They are not ignorant of what we are doing in our social capacity. They have cried out proclaim it; but it would not do a few years ago; everything must come in its time, as there is a time to all things. I am now ready to proclaim it. "This Revelation has been in my possession many years; and who has known it? None but those who should know it. I keep a patent lock on my desk, and there does not anything leak out that should not."[166:A]
- 73. The Revelation, so called, which was read at the close of this sermon, purports to have been given to Joseph Smith, July 12, 1843. It is very lengthy, consisting of twenty-five sections or paragraphs. It is published in full, in Burton's "City of the Saints," and in various other publications. The following synopsis exhibits all that is essential of this extraordinary Revelation. THE REVELATION. Section 1. "Verily, thus saith the Lord unto you, my servant Joseph, that inasmuch as you have inquired of my hand to know and understand wherein I, the Lord, justified my servants Abraham, Isaac, and Jacob, as also Moses, David, and Solomon, my servants, as touching the principle and doctrine of their having many wives and concubines: Behold, and lo, I am the Lord thy God, and will answer thee as touching this matter." [The balance of this section is prefatory, declaring that a new law and everlasting covenant is about to be revealed, and that he who abides not that covenant shall be damned.] Sec. 2. All covenants, contracts, vows, etc., not made and sealed by the Holy Spirit of promise, of him who is anointed (Joseph Smith) both as well for time and for all eternity, are of no efficacy or force after the resurrection. Sec. 3 represents the necessity of having everything sanctioned by the Almighty. Secs. 4 and 5. Persons married for life only, or for time and eternity, but not by the proper authority, not bound to each other after this life. Sec. 6 provides that if a man marry a wife by the law of God, and by the new and everlasting covenant, and if they abide in the covenant, and do not shed innocent blood, then the covenant shall be binding throughout time and eternity, "and they shall pass by the angels, and the gods which are set there, to their exaltation and glory in all things."
- 74. Sec. 7 declares that such shall be gods in the eternal world. Sec. 8 states that none can receive such exaltation except those who receive and abide the law of God. Sec. 9. "Verily, verily I say unto you, if a man marry a wife according to my word, and they are sealed by the Holy Spirit of promise according to mine appointment, and he or she shall commit any sin or transgression of the new and everlasting covenant whatever, and all manner of blasphemies, and if they commit no murder wherein they shed innocent blood, yet they shall come forth in the first resurrection, and enter into their exaltation, but they shall be destroyed in the flesh, and shall be delivered unto the buffetings of Satan unto the day of redemption, saith the Lord God." Sec. 10 explains that shedding innocent blood, and assenting unto the death of Christ, is the blasphemy against the Holy Ghost, which shall not be forgiven in the world nor out of the world. Secs. 11 and 12 refer to Abraham as the father of the faithful, and him to whom the promises were made. "This promise is yours also, because ye are of Abraham, and the promise was made unto Abraham." "Go ye, therefore, and do the works of Abraham; and enter ye into my law, and ye shall be saved." Sec. 13 intimates that Sarah acted in accordance with the command of God in giving Hagar to Abraham. Sec. 14 refers to the concubines which Abraham received, and says, "they bare him children, and it was accounted unto him for righteousness." The latter part of the section is as follows: "David also received many wives and concubines, as also Solomon, and Moses my servant; and also many others of my servants, from the beginning of creation until this time; and in nothing did they sin save in those things which they received not of me." Sec. 15. "David's wives and concubines were given unto him, of me, by the hand of Nathan, my servant, and others of the prophets who had the keys of this power; and in none of these things did he sin against me, save in the case of Uriah and his wife; and therefore
- 75. he hath fallen from his exaltation, and received his portion; and he shall not inherit them out of the world; for I gave them unto another, saith the Lord." Sec. 16 prescribes certain regulations concerning those who commit adultery, and provides that in case the husband commits adultery, and the wife is innocent, and the fact is revealed by God to Joseph, the wife shall be given by Smith to one who has not committed adultery, "but hath been faithful, for he shall be made ruler over many." Sec. 17. "And verily, verily I say unto you, that whatsoever you seal on earth shall be sealed in heaven; and whatsoever you bind on earth in my name and by my word, saith the Lord, it shall be eternally bound in the heavens; and whosesoever sins you remit on earth shall be remitted eternally in the heavens; and whosesoever sins ye retain on earth shall be retained in heaven." Sec. 18. "And again, verily I say, whomsoever you bless I will bless, and whomsoever you curse I will curse, saith the Lord; for I, the Lord, am thy God." Sec. 19. "And again, verily I say unto you, my servant Joseph, that whatsoever you give on earth, and to whomsoever you give any one on earth, by my word, and according to my law, it shall be visited with blessings, and not cursings, and with my power, saith the Lord, and shall be without condemnation, on earth and in heaven." Then follows a declaration to the effect that Smith has found favor with God, and that he will forgive his sins, etc. Sec. 20 commands Emma Smith "that she stay herself, and partake not of that which I commanded you to offer unto her; for I did it, saith the Lord, to prove you all," etc., and continues as follows: "And let mine handmaid, Emma Smith, receive all those that have been given unto my servant Joseph, and who are virtuous and pure before me; and those who are not pure, and have said they are pure, shall be destroyed, saith the Lord God; for I am the Lord thy God," etc.
- 76. Sec. 21 commands Emma Smith, wife of Joseph, to abide and cleave unto Joseph and none else, under penalty of destruction. She is also exhorted to forgive Joseph his trespasses. Sec. 22 forbids Joseph putting his property out of his hands. Sec. 23 touches upon the law of the priesthood, and says of any one who is called of God, as was Aaron, "if he do anything in my name, and according to my law, and by my word, he will not commit sin, and I will justify him." Joseph is to be justified, etc. The last two sections are as follows:— Sec. 24. "And again, as pertaining to the law of the priesthood: if any man espouse a virgin, and desire to espouse another, and the first gives her consent; and if he espouse the second, and they are virgins, and have vowed to no other man, then he is justified; he cannot commit adultery, for they are given unto him; for he cannot commit adultery with that that belongeth unto them, and to none else; and if he have ten virgins given unto him by this law, he cannot commit adultery, for they belong to him, and they are given unto him; therefore is he justified. But if one, or either of the ten virgins, after she is espoused, shall be with another man, she has committed adultery, and shall be destroyed; for they are given unto him to multiply and replenish the earth, according to my commandment, and to fulfil the promise which was given by my Father before the foundation of the world, and for their exaltation in the eternal worlds, that they may bear the souls of men; for herein is the work of my Father continued, that he may be glorified." Sec. 25. "And again, verily, verily I say unto you, if any man have a wife who holds the keys of this power, and he teaches unto her the law of my priesthood as pertaining to these things, then shall she believe, and administer unto him, or she shall be destroyed, saith the Lord your God; for I will destroy her; for I will magnify my name upon all those who receive and abide in my law. Therefore it shall be lawful in me, if she receive not this law, for him to receive all things whatsoever I, the Lord his God, will give unto him, because she did
- 77. not believe and administer unto him, according to my word; and she then becomes the transgressor, and he is exempt from the law of Sarah, who administered unto Abraham according to the law, when I commanded Abraham to take Hagar to wife. And now, as pertaining to this law: Verily, verily I say unto you, I will reveal more unto you hereafter; therefore let this suffice, for the present. Behold, I am Alpha and Omega. Amen." Such is the foundation upon which is built the superstructure of Utah polygamy. And the system itself, what is it in its theory and practical application? The mode of its institution has been shown. Its ceremonials, and many facts illustrative of its tendency and effects, will be given; and it is for our readers to determine how much it is better than promiscuous intercourse, and to discover, if they can, its redeeming features, as distinguished from such a state of society. No man who has a wife already, has any right to make propositions of marriage to a lady, until he has consulted the President of the whole church, and through him obtained a revelation from God upon the subject. If the revelation be favorable, he must next obtain the approbation of the parents, and thirdly, he is to consult the lady herself. It is also necessary that the first wife be consulted. If she refuses her consent, however, the lover husband may take an appeal to the President; and unless the wife can give to the President satisfactory reasons why her consent is withheld, the husband may proceed to introduce another wife into the family, against her will. The plan is, either to divorce the first wife, and damn her eternally, or to torment her daily, until, with a broken heart and a crushed spirit, she goes to the altar, and there gives another to her husband. Thus the semblance of her approbation is obtained. The exquisite cruelty of this abominable practice will appear most vividly from the marriage ceremony.
- 78. "When the day set apart for the solemnization of the marriage ceremony has arrived, the bridegroom and the wife, and also the bride, together with their relations, and such other guests as may be invited, assemble at the place which they have appointed. The scribe then proceeds to take the names, ages, native towns, counties, States, and countries of the parties to be married, which he carefully enters on record. The President, who is the Prophet, Seer, and Revelator over the whole church, throughout the whole world, and who alone holds the keys of authority in this solemn ordinance, calls upon the bridegroom and his wife, and the bride, to arise, which they do, fronting the President. The wife stands on the left hand of her husband, while the bride stands on her left. The President then puts this question to the wife: 'Are you willing to give this woman to your husband, to be his lawful and wedded wife, for time and all eternity? If you are, you will manifest it by placing her right hand within the right hand of your husband.' The right hands of the bridegroom and the bride being thus joined, the wife takes her husband by the left arm, as if in the attitude of walking. The President then proceeds to ask the following questions of the man: 'Do you, brother, (calling him by name) take sister (calling the bride by name) by the right hand, to receive her unto yourself, to be your lawful and wedded wife, and you to be her lawful and wedded husband, for time and for all eternity, with a covenant and promise on your part, that you fulfil all the laws, rites, and ordinances pertaining to this holy matrimony, in the new and everlasting covenant,—doing this in the presence of God, angels, and these witnesses, of your own free will and choice?' The bridegroom answers, 'Yes.' The President then puts the question to the bride: 'Do you, sister, (calling her by name) take brother (calling him by name) by the right hand, and give yourself to him to be his lawful and wedded wife, for time and for all eternity, with a
- 79. covenant and promise, on your part, that you will fulfil all the laws, rites, and ordinances pertaining to this holy matrimony, in the new and everlasting covenant,—doing this in the presence of God, angels, and these witnesses, of your own free will and choice?' The bride answers, 'Yes.' The President then says: 'In the name of the Lord Jesus Christ, and by the authority of the Holy Priesthood, I pronounce you legally and lawfully husband and wife, for time and all eternity; and I seal upon you the blessings of the holy resurrection, with power to come forth in the morning of the first resurrection, clothed with glory, immortality, and eternal lives; and I seal upon you the blessings of thrones, and dominions, and principalities, and powers, and exaltations; together with the blessings of Abraham, Isaac, and Jacob; and say unto you, be fruitful and multiply, and replenish the earth, that you may have joy and rejoicing in your posterity, in the day of the Lord Jesus. All these blessings, together with all other blessings, pertaining to the new and everlasting covenant, I seal upon your heads, and enjoin your faithfulness unto the end, by the authority of the Holy Priesthood, in the name of the Father, and of the Son, and of the Holy Ghost. Amen.'" The scribe then enters the marriage on the records, and the parties retire. The wedding is then celebrated with a feast at the husband's house, and a "Mormon dance." The new wife is assigned a room,—if indeed the happy husband's domicil contains two rooms, —and her experience in "plurality" begins. In well-regulated Mormon families, the first wife stands at the head of domestic concerns. She carries the keys of the storehouse, makes the purchases for the family, and deals them out to the plural wives, in much the same manner as other housekeepers do to their cooks. The husband's will is law, and from it there is no appeal, except in extreme cases, when the Bishop may be consulted.
- 80. If a husband has lost his wife by death, before he had the opportunity of attending to this holy ordinance, and securing her as his lawful wife for eternity, then it is the duty of the second wife, first, to be sealed or married to the husband, for and in the name of the deceased wife, for all eternity; and, secondly, to be married for time and eternity herself, to the same man. Thus, by this holy ordinance, both the dead and the living wife will be his in the eternal worlds. But if, previous to marriage for eternity, a woman lose her husband by death, and marry a second, and if her first husband was a good man, then it is the duty of the second husband to be married to her for eternity, not for himself, but in the name of her deceased husband, while he himself can only be married to her for time; and he is obliged to enter into a covenant to deliver her up, and all her children, to her deceased husband, in the morning of the first resurrection. Thus, by these refinements, a religious veil, captivating to the fancy, is thrown over the institution to hide its deformity. The same distinctions are carried through all the various relations of life; hence in case a widow is married to a widower, three ceremonies are necessary, in order fully to establish the eternal relations of all the parties. Incest is the practical result of some of the branches of this new- fangled system of sealing and marriage. It has already been shown, by the report of the Committee on Territories in the United States Senate, and the Message of Gov. Harding, that a mother and her daughters (by a former husband) all live together, as wives of the same husband.[173:A] A still more revolting relation is sometimes maintained. It is called "heirship," and is plainly enough sanctioned by Young, as follows:— "The text is, the right of heirship. I will, however, make an addition to the scripture, before I proceed further with
- 81. Welcome to our website – the perfect destination for book lovers and knowledge seekers. We believe that every book holds a new world, offering opportunities for learning, discovery, and personal growth. That’s why we are dedicated to bringing you a diverse collection of books, ranging from classic literature and specialized publications to self-development guides and children's books. More than just a book-buying platform, we strive to be a bridge connecting you with timeless cultural and intellectual values. With an elegant, user-friendly interface and a smart search system, you can quickly find the books that best suit your interests. Additionally, our special promotions and home delivery services help you save time and fully enjoy the joy of reading. Join us on a journey of knowledge exploration, passion nurturing, and personal growth every day! ebookbell.com