Object oriented Analysis Design 2nd Edition Lars

Mathiassen pdf download

https://ebookname.com/product/object-oriented-analysis-
design-2nd-edition-lars-mathiassen/

Get the full ebook with Bonus Features for a Better Reading Experience on ebookname.com
Instant digital products (PDF, ePub, MOBI) available
Download now and explore formats that suit you...

Object Oriented Analysis and Design for Information

Systems 2nd Edition Raul Sidnei Wazlawick

https://ebookname.com/product/object-oriented-analysis-and-
design-for-information-systems-2nd-edition-raul-sidnei-wazlawick/

Object oriented analysis and design with applications

3rd ed Edition Booch

https://ebookname.com/product/object-oriented-analysis-and-
design-with-applications-3rd-ed-edition-booch/

Developing Software with UML Object Oriented Analysis

and Design in Practice 2nd Edition Bernd Oestereich

https://ebookname.com/product/developing-software-with-uml-
object-oriented-analysis-and-design-in-practice-2nd-edition-
bernd-oestereich/

Wrangling Women Humor and Gender in the American West

Kristin M. Mcandrews

https://ebookname.com/product/wrangling-women-humor-and-gender-
in-the-american-west-kristin-m-mcandrews/
The Closed Treatment of Common Fractures 4th Edition
John Charnley

https://ebookname.com/product/the-closed-treatment-of-common-
fractures-4th-edition-john-charnley/

Elements of Information Theory Second Edition Thomas M.

Cover

https://ebookname.com/product/elements-of-information-theory-
second-edition-thomas-m-cover/

Surgical Critical Care 1st Edition Robert U. Ashford

https://ebookname.com/product/surgical-critical-care-1st-edition-
robert-u-ashford/

Romance Languages and Linguistic Theory 2000 Selected

Papers from Going Romance 2000 Utrecht 30 November 2
December 1st Edition Claire Beyssade (Ed.)

https://ebookname.com/product/romance-languages-and-linguistic-
theory-2000-selected-papers-from-going-
romance-2000-utrecht-30-november-2-december-1st-edition-claire-
beyssade-ed/

Anandi s Rainbow First Edition Anup Roy

https://ebookname.com/product/anandi-s-rainbow-first-edition-
anup-roy/
Cyrus the Great Ancient World Leaders 1st Edition
Samuel Willard Crompton

https://ebookname.com/product/cyrus-the-great-ancient-world-
leaders-1st-edition-samuel-willard-crompton/
’’Mathiassen, Munk-Madsen, Nielsen, and Stage have written this excellent
hook on object-oriented analysis and design. It is written in a refreshingly
mild style, open-minded and gentle and easy to read. The case studies are
varied and their approach to development methods is sensibly eclectic... I am
sure you will enjoy reading this book ”
— Michael Jackson

This book presents the OOA&D method for object-oriented analysis and de­
sign. OOA&D includes tested, mainstream techniques such as problem-do­
main modeling using class diagrams, application-domain modeling based
on use cases and functions, and design based on layered architectures and
encapsulation. However, the authors’ underlying approach to analysis and
design is new and inventive. Their OOA&D method offers two simple fra­
meworks: the first gives readers insight into the computerized system, and
the second focuses on the system’s context. These two frameworks are used
throughout the book, resulting in a simple, coherent presentation.

Nonetheless, this is not a book of recipes to be slavishly followed. The

authors’ approach is pedagogical. The book’s structure, concepts, guideli­
nes, and examples are designed to help the reader understand analysis and
design practices, and to reflect critically upon them. The book is suitable for
a university course in system development. It can also offer practitioners a
framework for implementing new working practices in analysis and design.

The book offers a complete guide to object-oriented analysis and design. It

includes guidelines for designing high-quality user interfaces and a reper­
toire of patterns that can inspire designs for specific solutions. The book
also offers exercises and problems, and references to literature on system
development.
 OBJECT-ORIENTED
ANALYSIS & DESIGN

LARS MATHIASSEN
ANDREAS MUNK-MADSEN
PETER AXEL NIELSEN
JAN STAGE

Foreword by Michael Jackson

Object-oriented analysis & design
2. edition
© 2018 Metodica ApS, Hadsund, Denmark
Text and layout: Lars Mathiassen, Andreas Munk-Madsen, Peter Axel Nielsen, Jan Stage
Cover: Zink Graphics
Print: rosendahls

All rights reserved. No part o f this book may be reproduced, stored in a retrieval system, or transmitted,
in any form or by any means, electronic, mechanical, photocopying, recording or otherwise, without the
prior written permission of the publisher.

Publisher: Metodica ApS

Lyngbakken 20 •9560 Hadsund •Denmark
Phone +45 3331 6432
Website www.metodica.dk •E-mail metodica@post4.tele.dk
ISBN 978-87-970693-0-1
 Foreword
Scandinavia has a long and notable tradition in computer science and soft­
ware engineering. Peter Naur was a major contributor to the development
of Algol-60 and co-inventor of the Backus-Naur notation in which its syntax
and that o f many subsequent languages was described. The original ideas
of object oriented programming came out o f the work o f Ole-Johan Dahl and
Kristen Nygaard on Simula 67. Per Brinch Hansen did fundamental work
in concurrency and operating systems and in languages for parallel pro­
gramming. Bjarne Stroustrup brought object orientation to the huge com­
munity o f C programmers in the C++ language.
Now Lars Mathiassen, Andreas Munk-Madsen, Peter Axel Nielsen, and
Jan Stage have written this excellent book on object-oriented analysis and
design. It is written in a refreshingly mild style, open-minded and gentle
and easy to read. The case studies are varied: two well-known example
problems, automobile cruise control and IFIP’s conference management,
and two less familiar, the management of a hairdressing salon and a moni­
toring system for a rescue station that operates fire engines, ambulances
and breakdown trucks. Little illustrations of particular points abound in
the text.
Their approach to development method is sensibly eclectic. They draw
on ideas from Checkland’s Soft Systems Methodology and from Structured
Analysis and Design; they take use cases from Jacobson, and the model-
function separation from JSD; they bring in design evaluation criteria from
Tom Gilb and Bertrand Meyer.
In the best Scandinavian tradition they are civilized, undogmatic and
humane. They emphasize the importance o f user involvement, and put in­
terface design in its proper place in their approach. They don’t allow them­
selves to be drawn into an excessively technical treatment o f each problem,
forgetting its real-world context in the excitement of playing with the UML
notations that, after all, are designed to represent programs. And, citing
Peter Naur’s delightful book Computing: A Human Activity, they remember
to remind us that the most useful and important documentation is often
what is written in natural language. I am sure you will enjoy reading this
book.

April 2000

Michael Jackson
 Preface to First Edition
Object orientation has become the dominate approach to the analysis and
design o f computerized systems. This book provides a pedagogical presenta­
tion of the object-oriented approach. Our method, OOA&D, is both original
and well tested. It presents a new, comprehensive view of analysis and de­
sign, making it easy for the reader to gain an overall understanding of
these important activities. However, many parts of OOA&D are derived
from other methods, because they have proven to work best in practice.
In the following chapters, we provide a comprehensive presentation of
central principles. Traditionally, analysis and design are described sepa­
rately. The design of the system’s logical kernel is traditionally governed by
functional considerations, and influenced by the literature on programming
and modeling. The design of the user interface and the system’s interaction
with its context are typically governed by considerations about usage, and
are primarily treated in the literature about hum an-com puter interaction
and usability. Finally, architectural design is often governed solely by tech­
nical considerations. In this book, we look at all essential aspects o f analy­
sis and design through a systematic presentation of the system’s problem
domain, application domain, architecture, and components.
Our presentation style is methodological. Our main emphasis is on
principles, concepts, and ways of thinking. Analysis and design books are
often tied to a certain notation with its associated diagramming techniques
and CASE tools. This gives rise to unproductive religious wars, and creates
dependencies on specialized commercial products. In this book, we use the
Unified Modeling Language for notation. UML is fast becoming the stan­
dard object-oriented notation, and thus gives readers access to a large port­
folio of developmental tools.
Finally, this book is not about object-oriented programming. OOA&D
gives practitioners clarity about system requirements and establishes a
qualified basis for implementation. Our method assumes that the program­
mers using it are competent and capable of exploiting the facilities in mod­
ern programming environments to attain high productivity and quality. We
therefore recommend that the analysis document contain a brief, but com­
plete description of system requirements, and that the design document al­
so be brief and provide an overview o f the system’s parts and their interac­
tions, as well as answers to the central design questions.
OOA&D is useful both in the classroom and in system development en­
vironments. Our target audiences are students in computer or information
sciences, as well as practicing developers who are seeking support for intro-
during object-oriented technology or inspiration for their own professional
development.
We wrote this book using an iterative process. Through practical exper­
iments and teaching at universities and in industry, we have collaborated
closely with colleagues, students, and system developers. This has provided
valuable insights and has led to many improvements. An earlier version of
this book has been used in Scandinavia for many years, and a draft of the
English version has been used by colleagues around the world. These activ­
ities have given us valuable insights that have improved the manuscript.
We would, therefore, like to thank everyone who participated in these activ­
ities. Their inspiration and critique has had a decisive influence on the final
product.
The research that led to OOA&D has enjoyed generous support from
The Danish Science Research Council (Program 9400911). Also thanks to
Jakob and Kimberly Iversen for their help in translating the Danish manu­
script and to Keri Schreiner for her detailed and creative copy-editing o f the
final manuscript.
We wish the best o f luck to system developers who will apply the meth­
od, educators who will use the book for teaching, and students who will
work with the method in their attempts to become competent system devel­
opers. We are interested in both questions and critiques that may inspire
our continued work with object-oriented ideas in system development.

May 2000

Lars Mathiassen
Andreas Munk-Madsen
Peter Axel Nielsen
Jan Stage
 Preface to Second Edition
Over the past two decades, object orientation has grown to be a superior ap­
proach to software development, both in modeling and programming. When
we introduced the OOA&D method, it represented a new approach to mod­
eling that was inherently based on a distinction between problem domain
and application domain, and as opposed to other contemporary methods we
suggested to model both of these domains, but in different ways. Since then,
we have experienced that this approach is very useful both in education and
software development practice. This is also reflected in the extensive posi­
tive and constructive feedback that we have received over the years.
Based on these experiences, we have decided to reprint the book. We
have maintained the original form and content but edited obvious errors
and typos. This means that some o f the examples and technologies may ap­
pear somewhat dated; but we encourage the reader to benefit from the
strength of the approach by focusing on the principles and guidelines of the
method.
We hope that our readers will appreciate the method in their teaching
and development practice, and we will be pleased to receive further feed­
back on this new edition.

July 2018

Lars Mathiassen, lars.mathiassen@ecigsu.edu

Andreas Munk-Madsen, metodica@post4.tele.dk
Peter Axel Nielsen, pan@cs.aau.dk
Jan Stage, jans@cs.aau.dk
 Table of Contents
I. B ack groun d .................................................................................... 1
1. M ethod.............................................................................................. 3
1.1. Objects and C la s s e s ...................................................................................4
1.2. Model the Context....................................................................................... 6
1.3. Emphasize the Architecture..................................................................... 9
1.4. Reuse P a tte r n s ..........................................................................................11
1.5. Tailor the M e th o d ..................................................................................... 12
1.6. R esu lts......................................................................................................... 16
1.7. Unified Process and Notation................................................................. 16
1.8. Principles.....................................................................................................18
1.9. E x ercises.....................................................................................................19
1.10. L ite r a tu r e .................................................................................................. 19

2. System Choice................................................................................23
2.1. System D efin ition .....................................................................................23
2.2. Choosing the System ................................................................................ 25
2.3. Describe the S itu a tio n ............................................................................ 26
2.4. Create I d e a s ..............................................................................................32
2.5. Experiments with Prototypes................................................................. 34
2 .6. Define S y stem s......................................................................................... 37
2.7. The FACTOR Criterion............................................................................40
2.8. Evaluation and C h o ic e ............................................................................ 42
2.9. Principles.................................................................................................... 42
2.10. E x ercises.................................................................................................... 43
2.11. L ite r a tu r e .................................................................................................. 44

II. Problem-Domain A n a ly s is ..................................................... 47

3. Classes..............................................................................................51
3.1. Classification of Objects and E v e n ts ....................................................52
3.2. Find C la s s e s ..............................................................................................57
3.3. Find Events ..............................................................................................59
3.4. Evaluate System atically..........................................................................62
3.5. Principles.................................................................................................... 66
3.6. E x ercises.................................................................................................... 67
3.7. L ite r a tu r e .................................................................................................. 69
4. S t r u c t u r e .................................................................................................. 71
4.1. Object-Oriented S tru ctu res.................................................................... 72
4.2. Structures between C lasses.................................................................... 74
4.3. Structures between O bjects.................................................................... 77
4.4. Find Candidates for Structure................................................................79
4.5. Explore Patterns........................................................................................ 82
4.6. Evaluate S ystem a tica lly.........................................................................86
4.7. P r in c ip le s ................................................................................................... 88
4.8. E xercises......................................................................................................89
4.9. L iteratu re................................................................................................... 90

5. B e h a v io r .....................................................................................................91
5.1. Behavioral Pattern and A ttrib u te s.......................................................92
5.2. Notation for Behavioral P a tte r n s ......................................................... 95
5.3. Describe Behavioral P a tte r n s ................................................................98
5.4. Explore Patterns...................................................................................... 104
5.5. Consider S tructu res................................................................................108
5.6. Consider Classes...................................................................................... 110
5.7. Describe Attributes..................................................................................112
5.8. P r in c ip le s ................................................................................................. 113
5.9. E xercises....................................................................................................114
5.10. L iteratu re................................................................................................. 115

II I. A p p l i c a t i o n - D o m a i n A n a l y s i s ..................................................117

6. U s a g e ....................................................................................................... 121
6.1. Use C a s e s ................................................................................................. 121
6.2. Example: An Automated Payment S ystem ........................................123
6.3. Find Actors and Use C a s e s .................................................................. 126
6.4. Explore Patterns...................................................................................... 132
6.5. Evaluate S ystem a tica lly.......................................................................134
6 .6. P r in c ip le s ................................................................................................. 135
6.7. E xercises....................................................................................................136
6 .8. L iteratu re................................................................................................. 137

7. F u n c t io n s ................................................................................................ 139
7.1. System Functions.................................................................................... 139
7.2. Find F u n ction s.........................................................................................143
7.3. Specify Complex F u n ction s.................................................................. 146
7.4. Evaluate S ystem a tica lly.......................................................................148
7.5. P r in c ip le s ................................................................................................. 149
7.6. E xercises....................................................................................................149
7.7. L iteratu re................................................................................................. 150
8. Interfaces...................................................................................... 153
8.1. User and System In terfaces................................................................. 153
8 .2. Explore User-Interface P a tte r n s ........................................................ 156
8.3. Determine User-Interface E le m e n ts..................................................158
8.4. Describe User-Interface E lem ents...................................................... 162
8.5. Explore System Interface P a tte rn s .................................................... 165
8 .6. Describe System Interface F a cilities..................................................169
8.7. Evaluate the In te r fa c e .......................................................................... 171
8 .8. Principles...................................................................................................172
8.9. E x ercises...................................................................................................173
8.10. L ite r a tu r e ................................................................................................ 174

IV. Architectural D e sig n .............................................................. 175

9. Criteria.......................................................................................... 179
9.1. Good Design.............................................................................................. 179
9.2. Consider General C r ite r ia ................................................................... 181
9.3. Analyze Specific C on ditions................................................................. 184
9.4. P rio ritize ...................................................................................................187
9.5. Principles...................................................................................................188
9.6. E x ercises.................................................................................................. 188
9.7. L ite r a tu r e ................................................................................................ 189

10. Components..................................................................................191
10.1. System C om ponents.............................................................................. 192
10.2. Explore Architectural P a tte r n s ...........................................................194
10.3. Define S u bsystem s.................................................................................200
10.4. Identify Com ponents.............................................................................. 203
10.5. Specify Relevant C om p on en ts.............................................................208
10.6. Principles.................................................................................................. 208
10.7. E x ercises.................................................................................................. 209
10.8. L ite r a tu r e ................................................................................................ 210

11. Processes......................................................................................211
1 1 .1. System P r o c e s s e s ...................................................................................212
11.2. Distribute Program C om ponents........................................................ 215
11.3. Explore Distribution P a tte rn s............................................................ 217
11.4. Identify Shared R esou rces................................................................... 221
11.5. Select Coordination M echanism s........................................................ 226
11.6. Explore Coordination Patterns.............................................................227
11.7. Principles.................................................................................................. 229
11.8. E x ercises.................................................................................................. 229
11.9. L ite r a tu r e ................................................................................................ 230
V. Component D esign ..................................................................233
12. Model Component...................................................................... 237
12.1. Designing the Model Com ponent......................................................... 238
12.2. Represent Private E v e n t s .................................................................... 241
12.3. Represent Common E v e n ts .................................................................. 243
12.4. Restructure C la sse s............................................................................... 245
12.5. P r in c ip le s ................................................................................................. 248
12.6. E xercises................................................................................................... 250
12.7. L iteratu re................................................................................................. 250

13. Function Component................................................................ 253

13.1. Designing the Function C om p on en t.................................................. 253
13.2. Design Functions as O p eration s......................................................... 256
13.3. Explore Patterns...................................................................................... 262
13.4. Specify Complex O p era tion s................................................................266
13.5. P r in c ip le s ................................................................................................. 270
13.6. E xercises................................................................................................... 271
13.7. L iteratu re................................................................................................. 272

14. Connecting Components.......................................................... 273

14.1. Coupling and C o h e s io n .........................................................................273
14.2. Connect C la s s e s ...................................................................................... 277
14.3. Explore Patterns...................................................................................... 280
14.4. Evaluate Connections............................................................................. 282
14.5. P r in c ip le s ................................................................................................. 283
14.6. E xercises................................................................................................... 283
14.7. L iteratu re................................................................................................. 284

VI. Practice........................................................................................ 285

15. Strategy.........................................................................................287
15.1. A Tailored S t r a t e g y ............................................................................... 289
15.2. Urgency o f S tra teg y ............................................................................... 291
15.3. Characterize the T a s k ...........................................................................292
15.4. Evaluate Difficulties............................................................................... 293
15.5. Design the S tra teg y ............................................................................... 294
15.6. Practical A p p lica tio n ............................................................................. 296
15.7. P r in c ip le s ................................................................................................. 299
15.8. E xercises................................................................................................... 299
15.9. L itera tu re................................................................................................. 300
16. D o c u m e n t a t io n ....................................................................................301
16.1. Importance of D ocu m en tation.............................................................302
16.2. Documentation S tan d ard ..................................................................... 303
16.3. Good Documentation.............................................................................. 305
16.4. Control and D ocum entation................................................................. 308
16.5. User-Oriented D ocum entation.............................................................311
16.6. Principles.................................................................................................. 312
16.7. E x ercises.................................................................................................. 312
16.8. L ite r a tu r e ................................................................................................ 313

17. I m p le m e n t a t io n ..................................................................................315
17.1. Object-Oriented P latform ..................................................................... 316
17.2. Relational Database S y s t e m ...............................................................322
17.3. Principles.................................................................................................. 326
17.4. E x ercises.................................................................................................. 327
17.5. L ite r a tu r e ................................................................................................ 327

18. N o t a t i o n ................................................................................................. 329

18.1. P u r p o s e .................................................................................................... 329
18.2. Unified Modeling Language................................................................. 332
18.3. OOA&D’s N ota tion ................................................................................ 336
18.4. Rich Picture..............................................................................................337
18.5. Class D iagram ......................................................................................... 338
18.6. Deployment D ia g ra m ............................................................................ 342
18.7. Sequence D ia g r a m ................................................................................ 342
18.8. Statechart D ia g r a m .............................................................................. 343
18.9. Use-Case D ia g r a m ................................................................................ 345
18.10. Navigation d ia g r a m .............................................................................. 346
18.11. Window D ia g r a m ...................................................................................346
18.12. Principles.................................................................................................. 346
18.13. L ite r a tu r e ................................................................................................ 347

VII. E x a m p le s ....................................................................................349
19. C o n fe r e n c e P la n n in g ........................................................................ 351
19.1. Analysis D ocu m en t................................................................................ 352
19.2. Design D o cu m e n t...................................................................................376

20. H a ir S a l o n .............................................................................................385
20.1. The Situation............................................................................................385
20.2. The Development T a s k ..........................................................................385
20.3. Prototype Experim ents..........................................................................386
20.4. System D efin ition ...................................................................................388
20.5. Problem-Domain A n a ly s is ................................................................... 388
20.6. Application-Domain Analysis...............................................................396
21. Rescue Station............................................................................ 401
21.1. Situation and T a sk ................................................................................. 401
21.2. System Choice.......................................................................................... 403
21.3. First M o d e l...............................................................................................405
21.4. Behavioral P a ttern s............................................................................... 406
21.5. Revised M odel.......................................................................................... 410
21.6. F u n c tio n s ................................................................................................. 410
21.7. Conclusion................................................................................................. 411

22. Cruise Control............................................................................ 413

2 2 .1. Analysis Docum ent................................................................................. 414
22.1. Cruise Control for a C ar.........................................................................414
2 2 .2. Strategy......................................................................................................421
22.3. A rch itectu re.............................................................................................424
22.4. System Interface...................................................................................... 425
22.5. K e rn e l........................................................................................................425
22.6. User Interface.......................................................................................... 428
22.7. Process Architecture............................................................................... 428
22.8. Component A rch itectu re...................................................................... 430
22.9. Conclusion................................................................................................. 432

Bibliography............................................................................................433
Index ........................................................................................................ 439
 Part I

Background

Methods must be tailored for practical use, rather than followed step-by-
step like a recipe. Therefore, we must understand the method’s underlying
principles, as well as the task at hand, to ensure that our planned activities
effectively address the challenges ahead.
In keeping with this idea, Chapter 1 offers an overview o f our object-ori­
ented method, OOA&D. We present its basic principles and concepts, and
outline its main activities, which we explore in more detail throughout the
book. Although some of the ideas in Chapter 1 might seem initially ab­
stract, the following chapters offer more concrete and detailed descriptions
of the principles and ideas. Later, after you’ve examined the method’s activ­
ities in detail, you can refer back to the first chapter for a review and sum­
mary of OOA&D’s basic parts.
Our discussion of methodology is the general starting point for
OOA&D; the practical starting point is the problem to be solved. However,
before you begin analysis and design, you must first produce an initial sys­
tem definition. The system definition explicates and delimits the task and
serves as a first agreement between system developers and users. Whether
or not you participate in this pre-analysis activity, you should know the
principles and methods for choosing a computerized solution as you might
need to reconsider the choice later in the project. In any case, you must en­
sure that the prerequisites for starting an object-oriented project are in
place.
In Chapter 2, “System Choice,” we discuss how to choose and define a
computerized solution so that it establishes a reasonable framework for
analysis and design. We discuss how you can do this using short and precise
definitions of alternative systems. We present the information in a practical
way, helping you choose a qualified system by answering two basic ques­
tions: What subactivities are involved? What are the most important tech­
niques to support these activities?
 Chapter 1

Method

Purpose • To determine system requirements.

• To produce a system design without significant uncer­
tainties.
• To understand a system, its context, and the conditions
for its implementation.

Concepts • Object: An entity with identity, state, and behavior.

• Class: A description of a collection of objects sharing
structure, behavioral pattern, and attributes.
• Problem domain: That part of a context that is admin­
istrated, monitored, or controlled by a system.
• Application domain: The organization that adminis­
trates, monitors, or controls a problem domain.
• System: A collection of components that implements
modeling requirements, functions, and interfaces.

Principles • Model the context.

• Emphasize the architecture.
• Reuse patterns.
• Tailor the method to suit specific projects.

Results • An analysis document and a design document.

Good system developers are recognized more for the skills they obtain
through practical experience than for the methodical knowledge they obtain
through theoretical study. Methods are, however, becoming increasingly
important because they provide a way to learn new technologies and to ex­
change experiences and inspiration. Even though the importance of meth­
ods should not be overrated, it is a good idea to work with them to improve
practices within specific disciplines.
This book presents our OOA&D method. In this chapter, we introduce
the most important ideas behind OOA&D. Our method uses objects and
classes as its key concepts and builds on four general principles for analysis
and design: model the system’s context, emphasize architectural consider­
ations, reuse patterns that express well-established design ideas, and tailor
the method to each development situation. These principles are the founda­
tion for OOA&D and contribute to its coherence.

1.1 Objects and Classes

In OOA&D, the basic building block is an object. During analysis, we use
objects to organize our understanding of the system’s context. During de­
sign, we use objects to understand and describe the system itself. In each
case, the definition is the same:

Object: An entity with identity, state, and behavior.

In analysis, an object is an abstraction o f a phenomenon in the system’s
context, such as a customer. The object expresses the users’ view of reality:
Certain people are customers, and they are treated as single entities with a
specific identity, state, and behavior. In design, an object is part o f the sys­
tem. A customer can also be a design object. In design, the customer object
would represent parts of a specific person’s history and state within the sys­
tem and make operations available for other system objects. Using such ob­
jects, the system can manage and store customer-specific data.
Typically, we describe objects in terms o f classes, rather than individu­
ally. For example, a system’s customer class might contain specific custom­
er objects, such as the user’s mother or neighbor, but the same class will al­
so contain many other customers, each with their unique identity, state,
and behavior. Classes are useful for understanding objects and vitally im­
portant for describing them. Instead o f describing each particular object, we
develop a shared object description for all objects in the same class. A class
can be defined as:

Class: A description o f a collection o f objects sharing structure,

behavioral pattern, and attributes.

Analysis and Design Objects

Analysis and design often share objects and classes, although the object’s
meaning changes. An analysis object’s identity expresses how the user dif­
ferentiates it from the other objects in the context. A design object’s identity
expresses how other objects in the system can recognize it, and thereby gain
access to it. Design also gives rise to new classes. Such classes do not reflect
the system’s context, but they are important for implementing the system
on the technical platform. These classes might include “Window,” “List,”
“Printer,” and so on.
 Object behavior is the decisive difference between analysis and design
objects. In analysis, we express an object’s behavior by the events it per­
forms or experiences. Customer objects are, for example, involved in order­
ing and shipping goods. Such events (order and ship) occur at definite
points in time, and involve one or more classes of objects (customers and
goods). The events help us understand how and when to change a system’s
representation of an object.
In design, we express an object’s behavior by the operations it can carry
out and make available to other objects in the system. Customer objects, for
example, can represent information about real-world customers. Such ob­
jects have operations, such as “add order” and “remove order,” which let the
system update the customer object’s state as the real world changes. A de­
sign object encapsulates the internal representation of its state. The repre­
sentation is hidden so other objects can only access the object’s state (which
goods are ordered) through its operations (add order and remove order). An
operation is defined as a process capability in a class and activated through
the class’ objects.
Analysis and design objects describe two clearly different matters.
Analysis objects describe phenomena outside the system, such as people
and things, which are typically independent. Although we cannot always
command them, we must register the events they perform or experience.
Design objects describe phenomena within the system that we can control.
We describe their behavior as operations for the computer to carry out.

Advantages of Object-Orientation
In many traditional analysis and design methods, functions, data, and data
flows are the key concepts. These concepts are suitable for describing phe­
nomena in offices and computerized systems. Objects, state, and behavior,
on the other hand, are more general concepts and are suitable for describ­
ing most phenomena that can be expressed in natural language. Objects are
similar to nouns, designating things such as people or inventory. Object at­
tributes or states, like adjectives, characterize object traits. Object behav­
ior, like verbs, describe actions or influences. As an example look at the sen­
tence “The house looked nice after Bob painted it.” This closely parallels the
object-oriented way of thinking. There are two objects (the house and Bob),
a common event (painting the house), and one of the objects has changed
state (the house has become nice).
Here we touch upon a primary strength o f object-orientation: It pro­
vides clear information about the system’s context. Traditional methods
were very effective at modeling early systems, whose purpose was to auto­
mate labor-intensive information processing tasks. Most such systems have
now been developed; new systems build upon them to support individual
problem solving, communication, and coordination. The function o f these
new systems is not only to handle large amounts of uniform data, but also
to distribute specialized data throughout the organization. Therefore, it is
now necessary to use methods that focus, with equal clarity, on both the
system and its context.
Another strength o f object-oriented methods is the close connection be­
tween object-oriented analysis, object-oriented design, object-oriented user
interfaces, and object-oriented programming. Objects can model social, eco­
nomic, and organizational conditions, as well as the system’s interfaces,
functions, processes, and components. In analysis, developers use objects to
determine system requirements. In design, they use objects to describe the
system itself. Developers also use objects as a central concept in program­
ming.
Objects provide material coherence to the system’s structure. They also
provide mental coherence: Objects offer developers a natural way of think­
ing about problems that support abstraction without forcing a one-sided,
technical point of view.

1.2 Model the Context

Success in system development greatly depends on the developer’s under­
standing o f the system’s practical application. As Figure 1.1 shows, the sys­
tem’s context can be viewed from two complementary perspectives: the sys­
tem models something (the problem domain) and it is operated by users
(the application domain). We define these two different, but strongly relat­
ed context perspectives as follows:

Problem domain: That part o f a context that is administrated,

monitored or controlled by a system.

Application domain: The organization that administrates, moni­

tors, or controls a problem domain.

The problem domain describes the system’s purpose, as well as the parts of
reality that the system should help administrate, monitor, or control. The
application domain is a part of the user organization. A system’s success (or
failure) depends on how well it links the application and problem domains
together into a functioning whole.
For a payroll system, the application domain includes the personnel of­
fice, while the problem domain includes the employees, their contracts, and
their work schedules. For an air traffic control system, the application do­
main is a part of the air traffic controllers’ job, while the problem domain
includes planes, flight departures, flight corridors, runways, flight posi­
tions, and movements. For a device for measuring telephone signals, the
 Figure 1.1: The system’s context

application domain is part of the technicians’ job, and the problem domain
includes signals, protocols, lines, transmitters, and receivers.
A key task in analysis and design is to model what the system will ad­
ministrate, monitor, or control. In an air traffic control system, this in­
cludes airplanes, flight departures, flight corridors, and positions. The air
traffic controllers’ job consists of monitoring and controlling the air traffic
using the system’s information about these objects. Controllers use this in­
formation, rather than direct observation of aircraft movement, as a basis
for decision making. Their understanding of air traffic consists of both the
actual situation in the air, and the way they think and talk about the traffic
in technical terms.
Because the controllers’ understanding of the problem domain is both
created and maintained through the system, the problem domain and the
system’s model of the problem domain must agree completely. This is a cru­
cial quality requirement. It is also crucial that the system’s model is orga­
nized in agreement with the air traffic controller’s structural understand­
ing. Thus, in this and all cases, system developers should analyze the prob­
lem domain, both to understand the system’s context and to learn how to
usefully representing it to the system’s users.
A second key task in analysis and design is to model how the system
will interact with users in the application domain. This includes identifying
all user groups and understanding both what they will use the system for
and how each group will interact with the system in different situations. In
 oriented analysis is not very differ­
Traditional methods
ent from modern structured analy­
The first analysis methods, which
sis in what it describes. The differ­
came out around 1970, were not ob­
ence lies mainly in the elegance of
ject oriented, but function oriented.
description. In object-oriented
Structured Analysis is a good ex­
analysis, the objects, their states,
ample o f such a method. To develop
and their behavioral patterns are
a payroll system using a function-
described coherently. In modern
oriented method, we immediately
structured analysis, related items
focus on the requirements, analyz­
are described in several different
ing tasks in the personnel office
models.
and how the system should move
In traditional design methods,
and process data. We are not inter­
the key principle is functional de­
ested in the employees as such, but
composition, in which an overview
rather focus on the data they pro­
is created by decomposing func­
duce and processes they use.
tions into smaller functions. In
Around 1980, function-oriented
functional decomposition, data has
analysis methods were supple­
low priority; it appears as function-
mented with data-oriented meth­
call parameters and intermediate-
ods inspired by database design.
result files. The existing data struc­
Entity relationship modeling is a
tures can therefore rarely be re­
good example o f a data-oriented
used when new functions are add­
analysis method. To develop a pay­
ed. The basic idea in a data-orient­
roll system based on such a meth­
ed design is to make all data avail­
od, we focus on objects (entities)
able to all functions. It is then easy
such as employees, departments,
to express very powerful functions.
and contracts, and examine their
However, in large organizations
state, such as seniority and depart­
with many functions and program­
mental relation (attributes and re­
mers, dependencies are built into
lations). We could also use a func­
the systems, making it possible for
tion-oriented method to describe
new functions to misinterpret or
how to best use these data struc­
contaminate existing data.
tures.
In object-orientation, the key de­
The newest version of structured
sign principle is encapsulation. The
analysis is called modern struc­
idea is to tie data to its related op­
tured analysis. It combines func­
erations; these operations then
tion and data orientations to en­
serve as the system’s data-access
compass an analysis o f the entities’
point. The goal is to break the sys­
state changes resulting from events
tem down into components with
in the application domain. Object-
minimal interfaces.
an air traffic control system, for example, we would study how traffic con­
trollers, pilots, and ground personnel would interact with the system to en­
sure a smooth and effective operation once the system is deployed.
In practice, there are always several ways to interpret a given piece of
information. Users and system developers interpret things in different
ways, and users often disagree even among themselves. During system de­
velopment, you must move between the present and the future, between the
existing and the new. The task is to understand the users’ current job, with
the goal of developing a system that will help them do it better. Analysis
and design efforts should respect the users’ current understanding of the
problem and application domains, but, more importantly, they should mod­
el ways of working with the new system. Thus, system development re­
quires a common understanding between developer and user. Object-orient­
ed analysis focuses on this challenge.
The object-oriented approach is useful in all types of system develop­
ment. Our OOA&D method is particularly useful in developing systems
with a dynamic problem-domain model as a key element. You can also use
OOA&D for designing tool systems, such as word processors, or systems
based on static models, such as those for processing questionnaire data. In
these situations, there is less emphasis on developing a problem-domain
model and more focus on the application domain.

1.3 Emphasize the Architecture

Understanding the context is important, but it is equally important to un­
derstand the system itself. We view the system as an entity adapted to
solve identified needs for a specific technical platform:

System: A collection o f components that implement modeling require­

ments, functions, and interfaces.

During analysis and design, it is essential to develop an overall under­

standing of the system. OOA&D therefore emphasizes the system architec­
ture as a key challenge, focusing on ease of understanding, flexibility, and
usefulness as important design qualities. The system architecture should
be easy to understand because it serves as the basis for decisions and as a
communication and work tool in the development work ahead. It should be
flexible because system development takes place in a turbulent environ­
ment. Finally, the architecture should be useful because the system’s suc­
cess depends on the role it will play in the user organization.
However, these general criteria do not specify when a design job is fin­
ished. The main purpose of OOA&D is to design a system without signifi­
cant uncertainties. We should not deal with details for their own sake, but
 Figure 1.2: A general system architecture

rather concentrate our efforts on points o f uncertainty in the system’s im ­

plementation and leave the rest to the programming activities.
A reasonable architecture gives us an overview of the system. Even
small systems contain so many classes and objects that the system easily
becomes unwieldy. As a tool for handling system complexity, OOA&D uses
components, which are groups of classes and objects.
Identifying the relevant components in a concrete system is a crucial is­
sue in object-oriented design. The choice o f architecture will always reflect
the concrete situation, and selecting one is a highly iterative process. In
OOA&D, we start with a very basic architecture with three components: a
model component, a function component, and an interface component.
Figure 1.2 shows this basic architecture, which reflects the system’s
context. The model component contains a dynamic model of the system’s
problem domain. We structure the model component to agree with the us­
ers’ view of the problem domain, and update it when important changes oc­
cur. In an air traffic control system, the model component contains a repre­
sentation of planes, flight departures, flight corridors, positions, and the re­
lations among them.
The function component contains the facilities through which users up­
date and use the model component. When planes change position in the air­
port’s air space, radar detects the movement and sends a signal to a system
update function which changes the model component’s state. If the model
component’s state shows that two planes are about to collide, a warning
function sends a signal to air traffic controllers that the planes’ flight cours­
es should be changed immediately.
 The interface component couples the system to its context in two ways.
First, the interface includes monitors with text and graphics, printouts, and
other facilities that let the user activate system functions. Second, the in­
terface directly connects with other technical systems, such as radar and
sensors.
This basic system architecture plays a central role in OOA&D. During
analysis, where we concentrate on understanding the system’s context and
identify requirements, the architecture’s simplicity helps us focus our at­
tention and create a simple and transparent structure in the analysis docu­
ment. During design, where we concentrate on structuring the system, we
use the architecture as a pillar to design a system that is usable, flexible,
and easy to understand. Although we start with three basic components, we
can add others as needed; for example, we might add a component for con­
currency and communication in distributed systems.

1.4 Reuse Patterns

A fundamental way of ensuring quality and efficiency in analysis and de­
sign is to reuse ideas that have been tested and used in other situations.
OOA&D inspires reuse in two ways: by using objects and components, and,
more generally, by using analysis and design patterns. A pattern is a gener­
alized description of a problem and a related solution. It is expressed as a
configuration of objects or components that can be used as inspiration for
analysis and design efforts. A pattern is simplified and abstract, and must
be adapted to the particulars of a given situation. In essence, it is a tem­
plate that points at possible, often partial, solutions that must be further
developed and supplemented to fit particular needs.
For example, we can use the role pattern during analysis to model dif­
ferent roles that people play over time. Given a system containing informa­
tion about both employees and customers, we can choose a straightforward
model in which people are modeled as employees or customers. However, if
a customer is later hired, we would have to model this by having both a cus­
tomer object and an employee object with similar attributes. This is a truly
unnatural model. The alternative is to design a dynamic role model, as
shown in Figure 1.3. This is a little more complicated, but better reflects re­
ality. In this model, a person at any point in time has zero or one employee
and zero or one customer roles, and maybe several over time. Thus, when a
customer is hired, we would simply add an employee role to the existing
customer role. The role pattern captures a general way to model objects
with dynamically changing roles using a shared repertoire of possible roles.
Another example o f a design pattern is the basic architecture we dis­
cussed above. This pattern expresses a particular way to structure the sys­
tem’s components into a functioning whole. In OOA&D, we use this pattern
 Figure 1.3: A simple role pattern

as a starting point for designing the system architecture. We then modify

and expand the architectural pattern to suit the particular needs of differ­
ent design situations.
It is important to stress that software-component reuse is not brought
about by using a particular method. Reuse comes from a disciplined work
process that is firmly anchored in the local tradition o f system development.
However, OOA&D supports reuse through elaborate use of patterns and
through its object and component concepts. To take full advantage o f the
opportunities these reuse tools offer typically requires a radical change in
the norms, traditions, and management styles within system development
organizations.

1.5 Tailor the Method

OOA&D is a collection of general guidelines for carrying out analysis and
design. It must therefore be tailored to your organization and project. To
make our method more usable, we designed it so that adaptations, improve­
ments, and part substitutions would be easy to implement.
OOA&D reflects four central perspectives on a system and its context:
the system’s information contents, how the system will be used, the system
as a whole, and the system’s components. The perspectives are connected to
OOA&D’s main activities: problem-domain analysis, application-domain
analysis, architectural design, and component design, respectively. Each
activity leads to specific results, which are subsequently included in the
analysis and design documentation. How you organize and document these
activities will depend on how you tailor OOA&D to the needs o f your proj­
ect.

Four Perspectives
The system is first understood from an information perspective: The system
must offer a useful model o f the problem domain. It should contain a model
 in real life, requirements change
Analysis and Design
because the design work provides
System development involves
new insights and because the sys­
adapting a system to people’s
tem’s context changes. Therefore,
needs. During system develop­
regardless o f whether or not we
ment’s thirty-year history, a tradi­
choose to separate the project into
tion has arisen in which system de­
an analysis phase and a design
velopment is divided into specific
phase, analysis and design are wo­
activities. The fundamental activi­
ven together. There is, however, a
ty is programming, which involves
natural succession of the results.
writing instructions that a machine
The final requirements should ex­
can execute on the available techni­
ist prior to the general solution,
cal platform. Prior to program­
which in turn should exist prior to
ming, however, the system must be
the detailed solution. However,
understood and described.
from this you cannot deduce a sim­
The goal with the analysis and
ple order of the activities.
design elements o f system develop­
In typical usage, “Analysis”
ment is to create an overview of the
means an activity in which some
system requirements and establish
item is taken apart and described,
a basis for system implementation.
while “design” is a constructive ac­
Both analysis and design deal with
tivity in which known parts are put
the system, but there is a differ­
together in a new way. In this
ence in perspective: analysis looks
sense, system development’s “anal­
at the system from the outside,
ysis” includes both design and
while design looks at it from the in­
analysis activities, and the same
side. Analysis starts with the sys­
holds true for system development
tem’s context, which serves as the
“design.” To limit confusion, we will
basis for requirements. Design, on
use the traditional designations,
the other hand, uses the available
and stress that the analysis and de­
technical constructs as its starting
sign activities are defined by their
point, and determines how the re­
purpose, principles, and results.
quirements can be implemented.
If requirements never changed,
it would be possible to completely
separate analysis and design. But

of the relevant problem-domain elements that let users administrate, moni­

tor, or control the problem domain. This information perspective is predom­
inant during analysis. But the perspective is also important during design
since the system should make the model available in an efficient and useful
manner.
 The system is next understood from the user’s viewpoint: The system
must he integrated in the application domain. We must understand the peo­
ple, devices, and other systems that the target system will interact with,
and which functions to offer these actors. Relations such as how, how quick­
ly, how often, and in what pattern different actors should interact with the
system are crucial for system usability. A well-functioning system is inte­
grated with other systems and adapted to the organization and the tradi­
tions in the application domain.
The third perspective is the architectural perspective: The system must
run on a specific technical platform. How should the system be divided into
components? Important considerations include the physical processes,
units, and connections that make up the technical platform. How should
the system use this platform? An architecture emphasis helps you deter­
mine how best to take advantage o f a platform’s possibilities and overcome
its limitations.
Finally, the system should be understood as a whole: The system should
he a well-functioning unit o f cooperating parts. The individual components
and their mutual interfaces and interactions should be designed to serve as
a basis for system implementation.

Four Main Activities

OOA&D covers the four perspectives through four main activities, shown in
Figure 1.4. We deal with each activity in detail in the four parts that follow
here. Ideally, we would discuss these activities in the order that you should
carry them out. Unfortunately, the situation is not so simple.
Analysis and design are always strongly iterative, wherein consider­
ations based on one perspective give rise to new considerations based upon
another perspective. The four activities’ relative importance and sequence
changes from project to project. In some projects, the application-domain
analysis is characterized by great uncertainty. The project might, for exam­
ple, be based on a new interface technology that is unfamiliar to both users
and developers. In other projects, the architecture is characterized by great
uncertainty, perhaps because the system is to be implemented on a recently
distributed platform. Thus, the priority and organization o f OOA&D’s main
activities depends on the situation.
As we noted above, the system should be in balance with its context.
But how can you achieve this? The obvious place to start is with the most
important perspective. Thus, you must assess the actual situation and de­
cide which perspectives you should emphasize. In practice, an activity’s or­
der and importance are controlled by a strategy that reflects the concrete
goals and circumstances for analysis and design. We discuss how to develop
such a strategy for particular projects in Chapter 15.
Exploring the Variety of Random
Documents with Different Content
wo yield him. " O Water '. thou didst contribute to the life of our
brother ; thou wert one of his sustaining elements. His remains are
now dispersed ; receive thy share of him, who has now taken an
everlasting flight ! " — Forbcs's Oriental Memoirs, iii, 12. Jlnd she, in
many ail emulous essay, At length into a descant uf her own Had
blended all tlieir notes. — Canto III. st. 39, &c. An extract from a
journal written in Switzerland will be the best comment upon the
description in these stanzas, which indeed were probably suggested
by my recollections of the Staubach. "While we were at the waterfall,
some half score iieasants, chiefly women and girls, assembled just
out of reach of the spray, and set up — surely the wildest chorus
that ever was heard by human ears — a song, not of articulate
sounds, but in which the voice was used as a mere instrument of
music, more flexible than any which art could produce, — sweet,
powerful, and thrilling beyond descrijition." It will be seen by the
subjoined sonnet of Mr. Wordsworth's,'who visited this spot three
years after me, that he was not less impressed than I had been by
this wild concert of voices. On approaching the Staub-bach,
Luuterbrunnen. Tracks let me follow far from human kind Which
these illusive greetings may not reach ; Where only Nuture tunes her
voice to teach Careless iiursuits, and raptures unconfined. No
Mermaid warbles (to allay the wind That drives some vessel towards
a dangerous beach) More thrilling melodies ! no cavern'd Witch,
Chanting a love-spell, ever intertwined Notes shrill and wild with art
more musical ! Alas ! that from the lips of abject Want And Idleness
in tatters mendicant They should proceed — enjoyment to inthrall,
And with regret and useless pity haunt This bold, this pure, this sky-
born Waterfall! " The vocal powers of these musical beggars (says
Mr. Wordsworth) may seem to be exaggerated ; but this wild and
savage air was utterly unlike any sounds I hud ever heard ; the
notes reached me from a dislince, and on what occasion they were
sung I could not guess, only they seemed to belong in some w.ay or
other to the waterfall ; and reminded me of religious services
chanted to streams and fountains in Pagan times." Some dim
presage. — Canto III. st. 41. Upon this subject an old Spanish
romancer speaks thus : .^iinque hombre no sabe lo de adelante
como ha dc venir, el espiritu lo siente, y antes que venga se duele
dello .- y de aqiii se levantaron los grandes sospiros i/ue hombres
dan a sohrevicntji no pcnsando en ninguna cosa, como a muchos
acaesce ; que aquel que el sospiro echa de si, el c^iritu es que
sieixte el mal que ha de ser. — Chronica del Rey D. Rodrigo, p. ii. c.
)71. Across her shoulders was a hammock flung . — Canto III. St.
45. Pinkerton, in his Geography, (vol. ii. p. 535, n. 3d edit.)
The text on this page is estimated to be only 29.91%
accurate

NOTES TO A TALE OF PARAGUAY, 531 Bays, that nets are

sometimes worn among tlie Guiiranis instead of clothes, and rt'firs to
this very story in proof of liis assertion. 1 believe he had no otiier
ground for it. lie adds, that "perhaps they were worn only to keep
oH' the flies;" as if those blood-suckers were to be keiit off hy open
network ! Wo owe something, however, to the person who
introduces ua to a good and valuable book, and I am inilebted
ori^'inally to Mr. Pinkerton for my knowledge ofDobrizhoffer. He says
of him, when referring to the HUturia de Miponibus, " the lively
singularity of tlio old man's Latin is itself an amusement ; and
though sometimes garrulous, he is redundiuit in authentic and
curious iiifurmation. His work, though bearing a restricted title, is the
best account yet published of the whole viceroyalty of La Plata." Her
feel upon the crescent moon were set. — Canto III. st. 51. This is a
common representation of the Virgin, from the Revelation. Virgem
de Sol veMida, e dos sens raios Claros envolta loda, e das Estrcllas
Coroadji, e debaixo os pes a Lua. Frakcisco ue Sa de Miranda, These
lines are highly esteemed by the Portuguese critics. Severe lie was,
and in his avger dread, Yet alioay at his Mother's will, grew mdd. So
well did he obey tluit Maiden undefilcd. — Canto III. St. 51. " How
hath the conceit of Christ's humiliation here on earth, of his
dependence on his mother during the time of his formation and
birth, and of his subjection to her in his infancy, brought forth
preposterous and more than heathenish transformations of bis glory
in the superstitious daughters of tlie idolatrous churcli ! They cannot
conceive Christ as King, unless they acknowledge her as Queen
Dowager of heaven : her title of Lady is a3y people whom they
found living where tliey liked, tc fettle in such places as were most
convenient for the work in whiib they were now to be compulsorily
em|)Ioyed. All tlicir work was task-work, imposed with little
moderation, and exacted without mercy. This tyranny extended to
the women and children ; and as all the Spaniards, the officers of
justice as well as the Encomenderos, were implicated in it, the
Indians had none to whom they could look for protection. Even the
institutions of Christianity, by which the Spanish government hoped
to better the temporal condition of its now subjects, were made the
occasion of new grievances and more intolerable oppression. For, as
the Indians were legally free, — free, therefore, to marry where they
pleased, and the wife was to follow the husband, — every means
was taken to prevent a marriage between two Indians who belonged
to different Rcpartimientns, and the interest of the master
counteracted all the efforts of the priest. The Spanish women are
said to have exceeded their husbands in cruelty on such occasions,
and to have instigated them to the most violent and iniquitous
measures, that they might not lose their female attendants. The
consetpienco was, that profligacy of manners among the Indians
was rather encouraged than restrained, as it is now in tlie English
sugar islands, where the planter is not a religious man. — Lozano,
1.1, §3,0,7. St. Joachin. — Canto IV. st. 17. The legend of his visit to
Limbo is given here in a translated extract from that very curious
work, the Life of the Virgin Mary, as related by herself to Sister Maria
de Jesus, Abbess of the Franciscan Convent de la Inmaculada
Concepcion at Agreda, and published with the sanction of all the
ecclesiastical authorities in Spain. After some conversation between
the Almighty and the Virgin, at that time three years and a half old,
the Franciscan confessor, who was the accomplice of the abbess in
this blasphemous imposture, proceeds thus : — " The Most High
received this morning sacrifice from his tender spouse, .Mary the
most holy, and with a pleased countenance said to her, ' Thou art
beautiful in thy thoughts, O Prince's daughter, my dove, and my
beloved ! I admit thy desires, which are agreeable to my eyes : and
it is my will, in fulfilment of them, that thou sliouldest understand
the time draws nigh, when by my divine appointment thy father
Joachin must pass from this mortal life to the life immortal and
eternal. His death shall be short, and he will soon rest in peace, and
be placed with the Saints in Limbo, awaiting the redem|)tion of the
whole human race.' 'J'his information from the Lord neither
disturbed nor troubled the regal breast of Mary, the Princess of
Heaven ; yet as the love of children to their parents is a debt due hy
nature, and that love in all its perfection existed in this most holy
child, a natural grief at losing her most holy father Joachin, whom as
a daughter she devoutly loved, could not fail to be resented. The
tender and sweet child Mary felt a movement of grief compatible
with the serenity of her magnanimous heart : and acting with
greatness in every thing, following both grace and nature, she made
a fervent prayer for her father Joachin : she besought the Lord, that,
as the mighty and true God, he would look upon him in the hour of
his liajipy death, and defend him from the Devil, especially in th;it
hour, and preserve him, and appoint him in the number of his elect,
as one who in bis life had confessed and magnified his holy and
adorable name. And the more to oblige his Majesty, the most faithful
daughter offired to endure for her father, the most holy Joachin, all
that the Lord might ordain. " His Majesty accepted this petition, and
consoled the divine child, assuring her that he would be with her
fither as a merciful and compassionate remunerator of those who
love and serve him, and that he would place him with the Patriarchs,
Abraham, Isaac, and Jacob ; and be prepared her again to receive
and suffer other troubles. Eight days before the death of the holy
Patriarch Joachin, Mary the most holy had other advices from the
Lord, declaring the day and hour in which he was to die, as in fact it
occurred, only six months after our Queen wont to reside in the
temple. When her Highness had received this information from the
Lord, she besought the twelve angels, (who, 1 have before said,
were those whom
 532 NOTES TO A TALE OF PARAGUAY. St. John names in
tlio Revelation,) that they would be with her father Joachin in his
sickness, and comfort him, and console him in it ; and thus they did.
And for the last hour of his transit she sent all those of her guard,
and besought the Lord that he would make them manifest to her
father for his greater consolation. The Most High granted this, and in
every thing fulfilled the desire of his elect, unique, and perfect one :
and the great Patriarch and happy Joachin saw the thousand holy
angels who guaided his daughter Maria, at whose petition and desire
the grace of the Almighty superabounded, and by his command the
angel said to Joachin these things : — " ' Man of God, the Most High
and Mighty is thy eternal salvation, and he sends thee from bis holy
place the necessary and timely assistance lor thy soul I Mary, thy
daughter, sends us to be with thee at Ibis hour, in which thou hast to
pay to thy Creator the debt of natural death. She is thy most faithful
and powerful intercessor with the Most High, in whose name and
peace depart thou from this world with consolation and joy, that he
bath made thee parent of so blessed a daughter. And aUliougb bis
incomprebensible Majesty, in his serene wisdom, hath not till now
manifested to thee the sacrament and dignity in whicii he will
constitute thy daughter, it is bis pleasure that thou sbouldest know it
now, to the intent that thou mayest magnify him and praise him,
and that at such news the jubilee of thy s]jirit may be joined with
the grief and natural sadness of death. Mary, thy daughter, and our
Ciueen, is the one chosen by the arm of the Omnipotent, that the
Divine Word may in her clothe himself with flesh, and with the
human form. She is to be the happy Mother of the Messiah, blessed
among women, superior to all creatures, and inferior only to God
himself. Thy most happy daughter is to be the repairer of what the
human race lost by the first fall, and the high mountain whereon the
new law of grace is to be formed and established. Thereibre, as tbou
leavest now in the world its restauratrix and daughter, by whom God
prepares for it the fitting remedy, depart thou in joy ; and the Lord
will bless thee from Zion, and will give thee a place among the !?
aints, that thou mayest attain to the sight and possession of the
happy Jerusalem.' " While the holy Angels spake these words to
Joachin, St. Anna, his wife, was present, standing by the pillow of
his bed ; and she heard, and, by divine permission, understood
them. At the same time, the holy Patriarch Joachin lost his speech,
and entering upon the common way of all flesh, began to die, with a
marvellous struggle between the delight of such joyful tidings and
the pain of death. During this conflict with his interior powers, many
and fervent acts of divine love, of faith, and adoration, and praise,
and thanksgiving, and humiliation, and other virtues, did he
heroically perform : and thus absorbed in the new knowledge of so
divine a mystery he came to the end of his natural life, dying the
precious death of the .Saints. His most holy spirit was carried by the
Angels to the Limbo of the Holy Fathers and of the Just: and for a
new consolation and light in the long night wherein they dwelt, the
Most High ordered that the soul of the holy Patriarch Joachin sliould
be the new Paranymph and Ambassador of his Great Majesty, for
announcing to all that congregation of the Just, how the day of
eternal light had now dawned, and the day-break was born, Mary,
the most holy daughter of Joachin and of Anna, from whom should
be born the Sun of Divinity, Christ, Restorer of the whole human
race. The Holy Fathers and the Just in Limbo heard these tidings,
and in their jubilee composed new hymns of thanksgiving to the
Most High. " This happy death of the Patriarch St. Joachin occurred
(as I have before said) half a year after his daughter, Mary the most
holy, entered the Temple ; and when she was at the tender age of
three and a half, she was thus left in the world without a natural
father. The age of the Patriarch was sixty and nine years, distributed
and divided thus : at the age of forty six years, he took St. An..a to
wife ; twenty years after this marriage, Mary the most holy was born
; and the three years and a half of her Highness's age make sixty-
nine and a half, a few days more or less. " The holy Patriarch and
father of our Queen being dead, the holy Angels of her guard
returned incontinently to her presence, and gave her notice of all
that bad occurred in her father's transit. Forthwith the most prudent
child solicited with prayers for the consolation of her mother St.
Anna, entreating that the Lord would, as a father, direct and govern
her in the solitude wherein, by the loss of her husband, Joachin, she
was left. St. Anna .herself sent also news of bis death, whicli was
first comnmnitlted fo the Mistress of our divine Piincess, that, in
imparting it, she might console her. The Mistress did this, and the
most wise child heard her, with all composure and dissimulation, but
with the patience and the modesty of a Queen ; but she was not
ignorant of the event which her Mistress related to her as news." —
Mistica Ciudud de Dios, par. 1, 1.2, c. l(i, ^664 — 669. Madrid, 1714.
It was in the middle of the seventeenth century that the work, from
which this extract is translated, was palmed upon the Spaniards as a
new revelation. Gross and blasphemous as the imposture is, the
work was still current when I procured my copy, about twenty years
ago ; and it is not included in the Spanish Index Expurgatorius of
1790, the last (I believe) which was published, and which is now
before me. He could not tarry here. — Canto IV. st. 67. A case
precisely of the same kind is mentioned by Mr. Mariner. " A young
Chief at Tonga, a very handsome man, was inspired by the ghost of
a woman in Bolotoo, who had fallen in love with him. On a sudden,
he felt himself lowspirited, and, shortly afterwards, fainted away.
When he came to himself, he was very ill, and was taken accordingly
to the house of a priest. As yet, he did not know who it was that
inspired him, but the priest informed liim that it was a woman of
Bolotoo, mentioning her name, who bad died some years before,
and who wished him nosv to die, that he might be near her. He
accordingly died in two dnys. The Chief said he suspected this, from
the dreams he had had at different times, when the figure of a
woman came to him in the night. Mr. Mariner was with the sick Chief
three or four times during his illness, and beard the priest foretell his
death, and relate the occasion of it." — Mariner. The following
similar case appeared in a newspaper: — " Died, on Sunday evening,
the 14th instant, John Sackeouse, aged 22, a native of the west
coast of Greenland. This Eskimaux has occupied a considerable
share of the pulilic attention, and bis loss will be very generally felt.
He bad already rendered important service to the country in the late
expedition of discovery, and great expectations were naturally
formed of the utility which be would prove on the expedition about
to sail for Daffin's Bay. The Admiralty, with great liberality and
judgment, had directed the greatest pains to be taken in his further
education ; and he had been several months in Edinburgh with this
view, when be was seized with a violent inflammation in the chest,
which carried him ofi" in a few days. He was extremely docile, and,
though rather slow in the attainment of knowledge, he was
industrious, zealous, and cheerful, and was always grateful for the
kindness aiul attention shown to him. His amiable disposition and
simple manners bad interested those who had opportunities of
knowing him personally, in a way that will not soon be forgotten. 'J'o
the public, his loss, we fear, is irreparable — to his friends, it is
doubly severe. Just before his death, the poor Eskimaux said he
knew he was going to die ; that his father and mother had died in
the same way ; and that his sister, who was the last of all his
relations, had just appeared to him, and called him away." —
Edinburgh Courant, Feb. 19.
 ALL FOR LOVE, OR A SINNER WELL SAVED. 533 ALL FOR
LOVE, OR A SINNER W^ELL SAVED. TO CAROLINE BOWLES. Could I
look forward to a distant day With hope of buildinsr some elaborate
lay, Then would I wait till worthier strains of mine Might bear
inscribed thy name, O Caroline ! For I would, while my voice is heard
on earth, Bear witness to thy genius and thy worth. But we have
both been taught to feel with fear How frail the tenure of existence
here. What unforeseen calamities prevent, Alas, how oft ! the best-
resolved intent ; And therefore this poor volume I address To thee,
dear friend, and sister Poetess. ROBERT SOUTHEY. Keswick, 21 Feb.
1829. Tho story of tlie following Poem is taken from a Lift; of St.
Basil, ascribed to his contemporary St. Amphilochius, Bishop of
Iconium ; a Latin version of which, made by Cardinal Ursus in the
ninth century, is inserted by Ro3weyde, among the Lives of tlie
Fathers, in his compilation Historic Ereiniticie. The original ha
 534 ALL FOR LOVE, OR A SINNER WELL SAVED. "Time
presses. Cyra is content " The passage will be swift and safe ; To bid
the world farewell, No danger awaits thee beyond ; And pass her
days, a virgin vow'd. Thou wilt only have now to sign and seal,
Among Emmelia's sisterhood, And hereafter to pay the Bond." Tlie
tenant of a cell. » Thus hath her father will'd, that so ♦ A life of rigor
here below May fit her for the skies. 11. And Heaven acceptably
receive His costliest sacrifice. Shunning human sight, like a thief in
the night, Eleijmon made no delay, " The admiring people say of this
But went unto a Pagan's tomb That Angels, or that Saints in bliss.
Beside the public way. The holy thought inspire ; And she is call'd a
blessed Maid, Enclosed with barren elms it stood, And he a happy
Sire. There planted when the dead Within the last abode of man "
Through Cappadocia far and wide Had been deposited. The news
hath found its way, And crowds to Coesarea flock And thrice ten
years those barren trees, To attend the solemn day. Enjoying light
and air, Had grown and flourish'd, while the dead " The robes are
ready, rich with gold. In daj-kness moulder'd there. Even like a bridal
dress. Which at the altar she will wear Long had they overtopp'd the
tomb ; When self-devoted she stands there And closed was now that
upper room In all her loveliness. Where friends were wont to pour.
Upon the honor'd dust below. " And that coarse habit too, which she
Libations through the floor. Must then put on, is made. Therein to be
for life and death There on that unblest monument Unchangeably
array'd. The young man took his stand, And northward he the
tablets held " This night, this precious night is ours ; In his uplifted
hand. Late, late, I come to you ; But all that must be dared, or done.
A courage not his own he felt. Prepared to dare and do." A wicked
fortitude. Wherewith bad influences unseen »• Thou hast hesitated
long ! " said Abibas, That hour his heart endued. " And thou hast
done amiss, In praying to Him whom I name not, The rising Moon
grew pale in heaven That it never might come to this ! At that
unhappy sight ; And all the blessed Stars seem'd then ' But thou
hast chosen thy part, and here thou art ; To close their twinkling
light ; And thou shalt have tliy desire ; And a shuddering in the elms
was heard. And though at the eleventh hour ■ Though winds were
still that night. Thou hast come to serve our Prince of Power, He will
give thee in full thine hire. He call'd the Spirits of the Air, He call'd
them in the name " These Tablets take ; " (he wrote as he spake ;)
Of Abibas; and at the call " My letters, which thou art to bear. The
attendant Spirits came. Wherein I shall commend thee To the Prince
of the Powers of the Air. A strong hand, which he could not see,
Took his uplifted hand ; " Go from the North Gate out, and take He
felt a strong arm circle him, On a Pagan's tomb thy stand ; And lift
him from his stand ; — And, looking to the North, hold up The
Tablets in thy hand ; — A whirr of unseen wings he heard About him
every where. " And call the Spirits of the Air, Which onward, with a
mighty force, That they iny messenger may bear Impell'd him
through the air. To the place whither he would pass. And there
present him to their Prince Fast through the middle sky and far In
the name of Abibas. It hurried him along ;
 ALL FOR LOVE, OR A SINNER WELL SAVED. 535 The
Hurricane is not so swift, The Torrent not so strong; — The Lightning
travels not so fast. The Sunbeams not so far ; And now behind him
he hath left The Moon and every Star. And still, erect as on the tomb
In impious act he stood. Is he rapt onward — onward — still In that
fix'd attitude. But as he from the living world Approach'd where
Spirits dwell, His bearers tliere in thinner air Were dimly visible ; —
Shapeless, and scarce to be descried In darkness where they flew ;
But still, as they advanced, the more And more distinct they grew.
And when their way fast-speeding they Through their own region
went. Then were they in their substance seen. The angelic form, the
fiendish mien. Face, look, and lineament. Behold where dawns
before them now. Far off, tlie boreal ray. Sole daylight of that frozen
zone. The limit of their way. In that drear realm of outer night. Like
the shadow, or the ghost of light. It moved in the restless skies, And
went and came, like a feeble flame That flickers before it dies. There
the fallen Seraph reign'd supreme Amid the utter waste ; There, on
the everlasting ice. His dolorous tlirone was placed. Son of the
Morning ! is it then For this that thou hast given Thy seat,
preeminent among The hierarchies of Heaven .' — As if dominion
here could joy To blasted pride impart ; Or this cold region slake the
fire Of Hell within the heart ! Thither the Evil Angels bear The youth,
and, rendering homage there Their service they evince, And in the
name of Abibas Present him to their Prince : Just as they seized him
when he made The Sorcerer's mandate known. In that same act and
attitude They set him before the throne. The fallen Seraph cast on
him A dark, disdainful look ; And from his raised hand scornfully The
proffer'd tablets took. " Ay, — love ! " he cried. " It serves me well.
There was the Trojan boy, — His love brought forth a ten years' war.
And fired the towers of Troy. " And when my own Mark Antony
Against young Caesar strove. And Rome's whole world was set in
arms, The cause was, — all for love ! " Some for ambition sell
themselves ; By avarice some are driven ; Pride, envy, hatred, best
will move Some souls ; and some for only love Renounce their hopes
of Heaven. " Yes, of all human follies, love, Methinks, hath served
me best ; The Apple had done but little for me. If Eve had not done
the rest. " Well then, young Amorist, whom love Hath brought unto
this pass, I am willing to perform the word Of my servant Abibas. "
Thy Master's daughter shall be thine. And with her sire's consent;
And not more to thy heart's desire Than to her own content. " Yea,
more ; — I give thee with the girl, Thine after-days to bless. Health,
wealth, long life, and whatsoe'er The world calls happiness. " But,
mark me ! — on conditions, youth I No paltering here we know !
Dost thou here, solemnly, this hour. Thy hope of Heaven forego ? "
Dost thou renounce thy baptism, And bind thyself to me, My woful
portion to partake Through all eternity ? " No lurking purpose shall
avail, When youth may fail and courage quail, To cheat me by
contrition ! I will have thee written down among The children of
Perdition. "Remember, I deceive thee not, Nor have I tempted thee !
Thou comcst of thine own accord, And actest knowingly. " Dost thou,
who now to choose art free, Forever pledge thyself to me .' As I
shall help thee, say ! " —
 53G ALL FOR LOVE, OR A SINNER WELL SAVED. I do ; so
lielp me, Satan ! The wilful castaway. said "A resolute answer," quoth
the Fiend; " And now then, Child of Dust, In further proof of that
firm heart. Thou wilt sign a Bond before we part,* For I take thee
not on trust I " Swift as thought, a scroll and a reed were brought.
And to Eleiimon's breast. Just where the heart-stroke plays, the point
Of the reed was gently press'd. It pierced not in, nor touch'd the skin
; But the sense that it caused was such, As when an electric pellet of
light Comes forcibly out at a touch ; — A sense no sooner felt than
gone, But, with that short feeling, then A drop of his heart's blood
came forth And fill'd the fatal pen. And with that pen accurs'd he
sign'd The execrable scroll. Whereby he to perdition bound His
miserable soul. "Eleemon, Eleemon ! " then said the Demon, " The
girl shall be thine, By the tie she holds divine. Till time that tie shall
sever ; And by this writing thou art mine, Forever, and ever, and ever
! " III. Look at yon silent dwelling now ! A heavenly sight is there,
Where Cyra in her Chamber kneels Before the Cross in prayer. She is
not loath to leave the world ; For she hath been taught with joy To
think that prayer and praise thenceforth Will be her life's employ.
And thus her mind hath she inclined. Her pleasure being still (An
only child, and motherless) To do her Father's will. The moonlight
falls upon lier face. Upraised in fervor meek. While peaceful tears of
piety Are stealing down her cheek. That duty done, the harmless
maid Disposed herself to rest ; No sin, no sorrow in her soul. No
trouble in her breast. But when upon the pillow then, Composed,
she laid her head. She little thought what unseen Powers Kept watch
beside her bed. A double ward had she that night, When evil near
her drew ; Her own Good Angel guarding her. And Eleiimon's too.
Their charge it was to keep her safe From all unholy things ; And
o'er her, while she slept, they spread The shadow of their wings. So
when an Evil Dream drew nigh. They barr'd him from access. Nor
sufTer'd him to reach her with A breath of sinfulness. But with his
instigations they A hallowing influence blent. And made his fiendish
ministry Subserve to their intent. Thus, while in troubled sleep she
lay, Strange impulses were given, Emotions earthly and of earth.
With heavenly ones of Heaven. And now the nightingale hath ceased
Her strain, who all night long Hath in the garden rosier trill'd A rich
and rapturous song. The storks on roof, and dome, and tower.
Forbear their clattering din, As now the motions and the sounds Of
daily life begin. Then, as from dreams that seem'd no dreams, The
wondering Maid awoke, A low, sweet voice was in her ear, Such as
we might expect to hear If some Good Angel spoke. According with
her dreams, it said, " So, Cyra, must it be ; The duties of a wedded
life Hath Heaven ordain'd for thee." This was no dream full well she
knew ; For open-eyed she lay, Conscious of thought and
wakefulness. And in the light of day ; And twice it spake, if doubt
had been, To do all doubt away. Alas ! but how shall she make
known This late and sudden change .'' Or how obtain belief for what
Even to herself is strange .' How will her Father brook a turn That
must to all seem shame .'
 ALL FOR LOVE, OR A SINNER WELL SAVED. 5.37 How bear
to tliink that vulgar tongues " Yea, I was fruitful as a vine ; Are busy
with her name ? — Our Heavenly Parent me and mine In all things
seem'd to bless ; That she should for a voice — a dream — Our
ways were ways of peace, our patlis Expose herself to be the theme
Were paths of pleasantness. Of wonder and of scorn ; — Public as
lier intent had been, " When I taught lisping lips to pray, And this the
appointed morn ! The joy it was to me. O Father, thus to train these
plants The Nuns even now are all alert; For immortality ! The altar
hath been dress'd. The scissors that should clip her hair " I saw their
little winning ways Provided, and the black hood there, Their
grandsire's love engage ; And there the sable vest. Methought they
were the pride, the joy, The crown of his old age. And there the
Priests are robing now ; The Singers in their station ; " When from
the Vision I awoke. Hark ! in the city she can hear A voice was in my
ear, — The stir of expectation ! A waking voice, — I heard it twice;
No human tongue was near ; — Througli every gate the people pour.
And guests on roof, and porch, and tower, "No human utterance so
could reach Expectant take their place ; The secret soul, no human
speech The streets are swarming, and the church So make the soul
rejoice ; Already fills apace. In hearing it I felt and knew It was an
Angel's voice ! Speak, then, she must : her heart she felt This night
had changed its choice ; " And thus, in words distinct, it said : — Nor
dared the Maiden disobey, — ' So, Cyra, must it be ! Nor did she
wish to (sooth to say,) — The duties of a wedded life That sweet and
welcome voice. Hath Heaven ordain'd for thee.' " Her Father comes :
she studies not Her cheek was like the new-blown rose, For gloss, or
for pretence ; While thus she told her tale ; The plain, straight
course will Cyra take Protcrius listened earnestly. (Which none
without remorse forsake) And as he heard grew pale ; — Of truth
and innocence. For he, too, in the dreams of night. " O Father, hear
me patiently ! " At the altar had seem'd to stand. The blushing
Maiden said; And to Eleemon, his freedman, " I tremble. Father,
while 1 speak. Had given his daughter's hand. But surely not for
dread ; — Their offspring, courting his caress. " If all my wishes liave
till now About his knees had throng'd ; Found favor in thy sight. A
lovely progeny, in whom. And ever to perform thy will When he was
in the silent tomb. Hath been my best delight. His line should be
prolong'd. Why should I fear to tell thee now The visions of this
night .'' And he had heard a waking voice, Which said it so must be,
" I stood in a dream at the altar, — Pronouncing upon Cyra's name
But it was as an earthly Bride ; A holiest eulogy : — And Eleemon,
thy freedman, Was the Bridegroom at my side. " Her shall her
husband praise, and her Her children bless'd shall call ; " Thou,
Father, gavest me to him, Many daughters have done virtuously,
With thy free and full consent ; But thine excelleth them all ! " And
— why should I dissemble it.'' — Methought I was content. No
marvel if his heart were moved ; The dream he saw was one ; '
Months then and years were crowded He kiss'd his trembling child,
and said, In the course of that busy night; " The will of Heaven be
done ! " I clasp'd a baby to my breast, And, oh ! with what delight !
Little did child or sire in this 68 The work of sorcery fear ;
 538 ALL FOR LOVE, OR A SINNER WELL SAVED. As little did
Elefimon think And what though EleC-mon were That the hand of
Heaven waa here. A man of lowly birth.' Enough it waa if Nature had
Ennobled him with worth. "This was no doubtful thing," they said,
IV. " For he had in the house been bred. From house to house, from
street to street. The rapid rumor flies ; Nor e'er from thence
removed ; But there from childhood had been known. Incredulous
ears it found, and hands Are lifted in surprise ; And trusted, and
approved. And tongues through all the astonish'd town Are busier
now than eyes. " Sucii as he was, his qualities Might to the world
excuse " So sudden and so strange a change ! The Maid and Father
for their choice, A Freedman, too, the choice ! Without the vision
and the voice, The shame, — the scandal, — and for what.' Had
they been free to choose. A vision and a voice 1 " But Heaven by
miracle had made " Had she not chosen the strait gate, — Its
pleasure manifest; The narrow way, — the holy state, — That
manifested will must set The Sanctuary's abode.' All doubtful
thoughts to rest. Would Heaven call back its votary Mysterious
though they be, the ways To the broad and beaten road .' Of
Providence are best." "To carnal wishes would it turn The wondering
City thus discoursed; The mortified intent.' To Abibas alone For this
are miracles vouchsafed .' The secret truth, and even to him For this
are Angels sent .' But half the truth, was known. " A plain collusion !
a device Meantime the Church hath been prepared Between the girl
and youth ! For spousal celebration ; Good easy man nmst the
Father be, The Sisters to their cells retire. To take such tale for truth
! " Amazed at such mutation. So judged the acrid and the austere,
The habit and hood of camel's hair. And they whose evil heart Which
with the sacred scissors there Inclines them, in whate'er betides. On
the altar were display'd. To take the evil part. Are taken thence, and
in their stead The marriage rings are laid. But others, whom a
kindlier frame To better thoughts inclined, Behold, in garments gay
with gold. Preserved, amid their wonderment. For other spousals
wrought, An equitable mind. The Maiden from her Father's house
With bridal pomp is brought. They would not of Proterius thus
Injuriously misdeem, — And now before the Holy Door A grave,
good man, and with the wise In the Ante-nave they stand ; For
wisdom in esteem. The Bride and Bridegroom side by side, The
Paranymphs, in festal pride. No easy ear, or vain belief. Arranged on
either hand. Would he to falsehood lend ; Nor ever might light
motive him Then from the Sanctuary the Priests, From well-weigh'd
purpose bend. With incense burning sweet, Advance, and at the
Holy Door And surely on his pious child, The Bride and Bridegroom
meet. The gentle Cyra, meek and mild, Could no suspicion rest;
There to the Bride and Bridegroom they For in this daughter he had
been The marriage tapers gave ; Above all fathers blest. And to the
altar as they go, With cross-way movement to and fro, As dutiful as
beautiful, The thuribule they wave. Her praise was widely known.
Being one who, as she grew in years, For fruitfulness, and perfect
love, Had stiJl in goodness grown. And constant peace, they pray'd.
 ALL FOR LOVE, OR A SINNER WELL SAVED. 539 On
EleCmoii, the Lord's Servant, And Cyra, tlie Lord's Handmaid. They
call'd upon the Lord to bless Their spousal celebration, And sanctify
the marriage rite To both their souls' salvation. A pause at every
prayer they made ; Whereat, with one accord, The Choristers took
up their part, And sung, in tones that thrill'd the heart, Have mercy
on us. Lord ! Then with the marriage rings the priest Betroth'd them
each to each. And, as the sacred pledge was given. Resumed his
awful speech ; — Pronouncing them, before high Heaven This hour
espoused to be. Now and forevermore, for time, And for eternity.
This did he in the presence Of Angels and of men; And at every
pause the Choristers Intoned their deep Amen ! Then to that
gracious Lord, the Priest His supplication made. Who, as our sacred
Scriptures tell, Did bring Rebecca to the well When Abraham's
servant pray'd. He call'd upon that gracious Lord To stablish with his
power The espousals made between them, In truth and love, this
hour ; — And with his mercy and his word Their lot, now link'd, to
bless, And let his Angel guide them In the way of righteousness.
With a Christian benediction. The Priest dismiss'd them then. And
the Choristers, with louder voice. Intoned the last Amen ! The days
of Espousals are over; And on the Crowning-day, To the sacred fane
the bridal train, A gay procession, take again Through thronging
streets their way. Before them, by the Paranymphs, The coronals are
borne. Composed of all sweet flowers of spring By virgin hands that
morn. With lighted tapers in array They enter the Holy Door, And the
Priest with the waving thuribule Perfumes the way before. He raised
his voice, and call'd aloud On Him who from the side Of our first
Father, while he slept, Form'd Eve to be his bride ; — Creating
Woman thus for Man A helpmate meet to be. For youth and age, for
good and ill, For weal and woe, united still In strict society, — Flesh
of his flesh; appointing them One flesh to be, one heart. Whom God
hath joined together. Them let not man dispart ! And on our Lord he
call'd, by whom The marriage feast was blest, When first by miracle
he made His glory manifest. Then, in the ever-blessed Name,
Almighty over all. From the man's Paranymph he took The marriage
coronal ; — And crowning him therewith, in that Thrice holy Name,
he said, " Ele{jmon, the Servant of God, is crown'd For Cyra, the
Lord's Handmaid ! " Next, with like action and like words. Upon her
brow he set Her coronal, intwined wherein The rose and lily met;
How beautifully they beseem'd Her locks of glossy jet ! Her he for
Eleemon crown'd. The Servant of the Lord ; — Alas, how little did
that name With his true state accord ! " Crown them with honor.
Lord ! " he said, " With blessings crown the righteous head ! To
them let peace be given, A holy life, a hopeful end, A heavenly
crown in Heaven ! " Still as he made each separate prayer For
blessings that they in life might share, And for their eternal bliss,
The echoing Choristers replied, " O Lord, so grant thou this ! " How
differently, meantime, before The altar as they knelt, While they the
sacred rites partake Which endless matrimony make. The Bride and
Bridegroom felt ! She, who possess'd her soul in peace And
thoughtful happiness, With her whole heart had inly join'd In each
devout address.
 540 ALL FOR LOVE, OR A SINNER WELL SAVED. His lips the
while had only moved In hollow repetition ; For he had steel'd
himself, like one Bound over to perdition In- present joy he wrapp'd
his heart. And resolutely cast All other thoughts beside him, Of the
future, or the past. Tw ELVE years have held their quiet course Since
Cyra's nuptial day ; How happily, how rapidly, Those years have past
away ! Bless'd in her husband she hath been ; He loved her as
sincerely, (Most siaful and unhappy man !) As he had bought her
dearly. She hath been fruitful as a vine, And in her children bless'd ;
Sorrow hath not come near her yet, Nor fears to shake, nor cares to
fret. Nor grief to wound the breast. And bless'd alike would her
husband be. Were all things as they seem ; Eleemon hath every
earthly good, And with every man's esteem. But where the accursed
reed had drawn The heart-blood from his breast, A small red spot
remain'd Indelibly impress'd. Nor could he from his heart throw off
The consciousness of his state ; It was there with a dull, uneasy
sense, A coldness and a weight ; — It was there when he lay down
at night. It was there when at morn he rose ; He feels it whatever
he does. It is with him wherever he goes. No occupation from his
mind That constant sense can keep ; It is present in his waking
hours, It is present in his sleep ; — But still he felt it most. And with
painfulest weight it press'd, O miserable man ! When he was
happiest. O miserable man. Who hath all the world to friend. Yet
dares not in prosperity Remember his latter end ! But happy man,
whate'er His earthly lot may be, Who looks on Death as the Angel
That shall set his spirit free. And bear it to its heritage Of immortality
! In such faith hath Proterius lived ; And strong is that faith, and
fresh. As if obtaining then new power, When he hath reach'd the
awful hour Appointed for all flesh. Elefimon and his daughter With
his latest breath he bless'd. And saying to them, " We shall meet
Again before the Mercy-seat! " Went peacefully to rest. This is the
balm which God Hath given for every grief; And Cyra, in her
anguish, Look'd heavenward for relief. But her miserable husband
Heard a voice within him say, " Eleemon, Eleemon, Thou art sold to
the Demon ! " And his heart seem'd dying away. Whole CiEsarea is
pour'd forth To see the funeral state. When Proterius is borne to his
resting-place Without the Northern Gate. Not like a Pagan's is his
bier At doleful midnight borne By ghastly torchlight, and with wail Of
women hired to mourn. With tapers in the face of day. These rites
their faithful hope display ; In long procession slow. With hymns that
fortify the heart. And prayers that soften woe. In honor of the dead
man's rank. But of his virtues more. The holy Bishop Basil Was one
the bier who bore. And with the Bishop side by side. As nearest to
the dead allied, Was Eletimon seen : All mark'd, but none could read
aright. The trouble in his mien. " His master's benefits on him Were
well bestow'd," they said, " Whose sorrow now full plainly show'd
How well he loved the dead." They little ween'd what thoughts in
him The solemn psalm awoke.
 ALL FOR LOVE, OR A SINNER WELL SAVED. 541 Which to
all other hearts that hour Till he hath wash'd away with tears Its
surest comfort spoke : — The red spot from his breast ! " Gather my
Saints together ; " Hold fast thy hope, and Heaven will not In peace
let them be laid, Forsake thee in thine hour : They who with me,"
thus saith the Lord, Good Angels will be near thee. " Their covenant
have made 1 " And evil ones shall fear thee. And Faith will give thee
power." What pangs to Eleemon then. O wretchedest of wretched
men. Perturb'd, yet comforted, she woke ; That psalmody convey'd!
For in her waking ear For conscience told liim that he, too. The
words were heard which promised her A covenant had made. A
strength above all fear. And when he would have closed his ears An
odor, that refresh'd no less Against the unwelcome word. Her spirit
with its blessedness Then from some elms beside the way Than her
corporeal frame. A Raven's croak was heard. Was breathed around,
and she surely found That from Paradise it came. To him it seem'd a
hollow voice That warn'd him of his doom ; And, though the form
revered was gone. For the tree whereon the Raven sat A clear,
unearthly light Grew over the Pagan's tomb. Remain'd,
encompassing the bed. When all around was night. It narrow'd as
she gazed ; VI. And soon she saw it rest. Concentred, like an eye of
light. When weariness would let her Upon her husband's breast. No
longer pray and weep. And midnight long was past. Not doubting
now the presence Then Cyra fell asleep. Of some good presiding
Power, Collectedness as well as strength Into that wretched sleep
she sunk Was given her in this hour. Which only sorrow knows,
Wherein the exhausted body rests. And rising half, the while in deep
But the heart hath no repose. But troubled sleep he lay. She drew
the covering from his breast Of her Father she was dreaming, With
cautious hand away. Still aware that he was dead. When, in the
visions of the night. The small, round, blood-red mark she saw; He
stood beside her bed. Eleemon felt her not ; But in his sleep he
groan'd, and cried, Crown'd and in robes of light he came ; " Out !
out — accursed spot ! ' ' She saw he had found grace ; And yet
there seem'd to be The darkness of surrounding night A trouble in
Welcome to our website – the ideal destination for book lovers and
knowledge seekers. With a mission to inspire endlessly, we offer a
vast collection of books, ranging from classic literary works to
specialized publications, self-development books, and children's
literature. Each book is a new journey of discovery, expanding
knowledge and enriching the soul of the reade

Our website is not just a platform for buying books, but a bridge
connecting readers to the timeless values of culture and wisdom. With
an elegant, user-friendly interface and an intelligent search system,
we are committed to providing a quick and convenient shopping
experience. Additionally, our special promotions and home delivery
services ensure that you save time and fully enjoy the joy of reading.

Let us accompany you on the journey of exploring knowledge and

personal growth!

ebookname.com