Systems Architecture. Strategy and product development for complex systems Bruce Cameroninstant download
Systems Architecture. Strategy and product development for complex systems Bruce Cameroninstant download
https://ebookmass.com/product/systems-architecture-strategy-and-
product-development-for-complex-systems-bruce-cameron/
https://ebookmass.com/product/designing-and-managing-complex-systems-
david-moriarty/
https://ebookmass.com/product/system-architecture-and-complexity-
vol-2-contribution-of-systems-of-systems-to-systems-thinking-printz/
https://ebookmass.com/product/complexity-and-complex-chemo-electric-
systems-stanislaw-sieniutycz/
https://ebookmass.com/product/complexity-and-complex-thermo-economic-
systems-stanislaw-sieniutycz/
Entropy of Complex Processes and Systems Eugene Barsky
https://ebookmass.com/product/entropy-of-complex-processes-and-
systems-eugene-barsky/
https://ebookmass.com/product/process-systems-engineering-for-
biofuels-development-adrian-bonilla-petriciolet/
https://ebookmass.com/product/introduction-to-the-theory-of-complex-
systems-stefan-thurner-2/
https://ebookmass.com/product/introduction-to-the-theory-of-complex-
systems-stefan-thurner/
https://ebookmass.com/product/securing-systems-applied-security-
architecture-and-threat-models-ebook-pdf-version/
Global Global
edition edition
edition
Global
System
Architecture
System Architecture
preserves the cutting-edge approach and pedagogy of the
original, but also features alterations, customization, and
adaptation from the North American version.
Selva
Cameron
Crawley
This is a special edition of an established
title widely used by colleges and universities Strategy and Product Development
throughout the world. Pearson published this
exclusive edition for the benefit of students
outside the United States and Canada. If you
for Complex Systems
purchased this book within the United States
or Canada, you should be aware that it has Edward Crawley Bruce Cameron Daniel Selva
been imported without the approval of the Foreword by Norman R. Augustine
Publisher or Author.
Global Edition
The rights of Edward Crawley, Bruce Cameron, and Daniel Selva to be identified as the authors of this work have been
asserted by them in accordance with the Copyright, Designs and Patents Act 1988.
Authorized adaptation from the United States edition, entitled System Architecture: Strategy and Product Development
for Complex Systems, 1st edition, ISBN 978-0-13-397534-5, by Edward Crawley, Bruce Cameron, and Daniel Selva
published by Pearson Education © 2016.
All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any
form or by any means, electronic, mechanical, photocopying, recording or otherwise, without either the prior written
permission of the publisher or a license permitting restricted copying in the United Kingdom issued by the Copyright
Licensing Agency Ltd, Saffron House, 6–10 Kirby Street, London EC1N 8TS.
All trademarks used herein are the property of their respective owners. The use of any trademark in this text does not
vest in the author or publisher any trademark ownership rights in such trademarks, nor does the use of such trademarks
imply any affiliation with or endorsement of this book by such owners.
A catalogue record for this book is available from the British Library
10 9 8 7 6 5 4 3 2 1
Foreword 7
Preface 9
Acknowledgments 11
About the Authors 12
4.7 Summary 96
References 96
chapter 5 Function 97
5.1 introduction 97
5.2 Function in Architecture 97
5.3 Analysis of external Function and Value 103
5.4 Analysis of internal Function 108
5.5 Analysis of Functional interactions and Functional Architecture 112
5.6 Secondary Value-related external and internal
Functions 122
5.7 Summary 123
References 123
Appendices 420
Chapter Problems 435
Index 462
Foreword
CoNTeNTS 7
Norman R. Augustine
A particularly promising trend that has been taking place in healthcare is the marriage of biomed-
ical research with engineering practices. A friend of mine, an engineer, recently described to me
a meeting that took place at one of America’s most prestigious universities between the faculties
of the engineering department and the cardiology department exploring just such opportunities.
Having decided to focus on constructing a practicable mechanical human heart, the head of car-
diology began his presentation with a description of the properties of the human heart. Almost
immediately an engineer interrupted, asking “Does it have to be in your chest? Could it be, say, in
your thigh where it would be easier to reach?” No one in the room had ever considered that pos-
sibility. Nonetheless, the presentation continued. Soon another interruption occurred; this time it
was another engineer asking, “Instead of just one heart could you have three or four small hearts
integrated in a distributed system?” No one had thought of that either.
System Architecture, so insightfully presented in this book by three of the field’s most highly
regarded leaders, is about asking—and—answering just such questions. In my own career I have
encountered system architecture questions in fields ranging from engineering to business to gov-
ernment. When established practices of the field of system architecture are applied, far superior
outcomes seem to result.
Applying such practices has not always been the case. Early in my career I recall asking
various of my colleagues who were working “together” on a guided missile program why they
had chosen a particular design approach for their specific element of the product. One replied,
“Because it is the lowest weight.” Another assured me that his part would have the lowest radar
cross-section. Still another answered because her component would be less costly. And yet
another had focused on minimizing volume. And so it went.
What was missing? The answer is a system architect.
This shortcoming is too often encountered, usually in more subtle ways. Consider the case of
the Near-Sonic Transport aircraft that was in the early stages of development a few years ago. A
marketing survey had indicated that airline passengers want to get to their destinations faster. To
an aerodynamicist (my own early field), if one wishes to avoid the penalties of supersonic flight,
that translates into more closely approaching Mach One, creeping up on the drag curve into a
regime wherein fuel consumption abruptly increases. This was, in fact, the underlying concept
of the Near-Sonic Transport.
But when viewed from a system architecture perspective, the appropriate question is not how
to fly faster; rather, it is how to minimize the time to get from one’s home, to the airport, check-in,
pass through security, board the aircraft, fly, collect baggage and travel to one’s final destination.
Placed in this context, an even more fundamental question arises: “How much will a passenger
pay to save five or ten minutes of flying time?” The answer turns out to be, “not much”—and the
Near-Sonic Transport aircraft thus met its early, and deserved, demise. There are clearly better
Norman R. Augustine has served in industry as chairman and CEO of Lockheed Martin Corporation, in government as
Under Secretary of the Army, in academia as a member of the engineering faculty of Princeton University and as a trustee
of MIT, Princeton, and Johns Hopkins and as a regent of the University System of Maryland’s 12 institutions.
8 ForeworD
opportunities in which to invest if one’s objective is to help passengers reach their destinations
more rapidly. The failing in this case was to not recognize that one was dealing with a problem of
system architecture . . . not simply a problem of aerodynamics and aircraft design.
My own definition of a “system” evolved over years of experience. It is “two or more ele-
ments that interact with one another.” The authors of this book wisely add that the resultant
functionality must exceed the sum of functionalities of the individual elements. Thus simple in
concept, the complexity of most real-world systems is enormous. In fact, the equation describ-
ing the number of possible states a system of several elements (that interact in the simplest of all
manners) has been aptly named, “The Monster!” And when a system includes humans, as many
systems do, the challenge of system architecting becomes all the more immense due to the pres-
ence of unpredictability. But these are the kind of systems that one encounters, and are the kind
of systems that the authors show how to deconstruct and address.
One such system that I had the occasion to analyze concerned provisioning the (human
occupied) U.S. station at the Earth’s South Pole. Setting the specific objective of the evaluation
in itself required care . . . as is often the case. Was it to minimize expected cost? Or to minimize
worst-case cost in the face of uncertainty, say, due to weather? Or perhaps to minimize “regret”—
that is, when supplies are not delivered at all? Or . . .?
In the case of this particular system there are a number of elements that must interface
with one-another: cargo ships, ice breakers, aircraft of various types, ice piers for off-loading,
storage facilities, traverse vehicles, communications . . . and, underlying all decisions, was the
ever-present danger of single-point failure modes creeping into the architecture.
In the business world one of the more complex problems faced in my career was whether—
and how—all or major parts of seventeen different companies could be combined to create the
Lockheed Martin Corporation. Each of the “elements” had its strengths and its weaknesses; each
involved large numbers of humans, each with their own goals, capabilities, and limitations; and
critical to the decision, the whole had to have significantly greater functionality than the sum of
the parts. If the latter were not the case, there would be no reason to pay the financial premium
that is implicit in most mergers and acquisitions.
Sadly, in engaging complex questions of this type there is no simple mathematical formula
that will reveal the “right” answer. However, the discipline of systems thinking proves to be an
invaluable tool in assessing exposure, opportunities, parametric sensitivities, and more. In the
above case, most people judge that the answer came out “right”—which, incidentally, contrasts
with nearly 80 percent of similar undertakings.
One of the authors of this book and I, along with a group of colleagues, had the occasion to
propose to the President of the United States a human spaceflight plan for America for the next
few decades. In this instance perhaps the most difficult challenge was to define a useful mission,
as opposed to the (non-trivial) task of defining an appropriate hardware configuration. Fortunately,
such issues are amenable to solution through system thinking.
As the authors point out in the material that follows, the process of establishing the archi-
tecture of systems is both a science and an art. But, as is so elegantly portrayed herein, there is
a Darwinian phenomenon wherein systems embodying the mistakes of the past do not survive;
whereas those that embody sound architectures generally do survive—and even prosper.
That, of course, is what architecting complex systems is all about.
Preface9
CoNTeNTS
We wrote this book to capture a powerful idea. The idea of the “architecture of a system” is
growing in recognition. It appears in diverse fields including the architecture of a power grid or
the architecture of a mobile payment system. It connotes the DNA of the system, and the basis
for competitive advantage. There are over 100,000 professionals with the title system architect
today, and many more practicing the role of the architect under different titles.
Powerful ideas often have nebulous boundaries. We observed that many of our co-workers,
clients, students had a shared recognition of system architecture issues, but used the term in very
different scopes. The term is often used to differentiate between existing systems, as in “the
architecture of these two mountain bikes is different.”
What exactly constitutes the architecture of a system is often a subject of great debate. In
some fields, the term is used for a singular decision that differentiates two types of systems at
a high level, as in “packet-switched architecture” vs. “circuit-switched architecture.” In other
fields, the term is used to describe a whole implementation, save for some smaller details, as in
“our software as a service architecture.”
Our goal was to capture the power of the idea of architecture, and to sharpen the boundaries.
Much of the power of idea originates with the potential to trade among several architectures
early, to look downstream and identify which constraints and opportunities will be central to
value. It isn’t possible to trade among early ideas if the architecture encompasses all details, nor
is it a meaningful exercise if important drivers of value are missing.
We wrote this book to build on the idea that the architect is a specialist, not a generalist, as
proposed by Eberhardt Rechtin. Our intent is to showcase the analysis and methodologies of sys-
tem architecture, and to develop the ‘science’ of system architecture. This text is less prescriptive
in places than the discipline of product design, as the systems tackled are more complex. Where
the product development community has a stronger focus on design, our focus centers more on
emergence—the magic of functions coming together to produce a coherent whole.
We’ve imbued this book with our past experience. We’ve been fortunate to be involved in the
early development of a number of complex systems in communications, transportation, mobile
advertising, finance, robotics, and medical devices, ranging in complexity from farm equipment
to the International Space Station.
Additionally, we have included case studies from the experience of other system architects,
in disciplines ranging from hybrid cars to commercial aircraft. Our intent was that this book can
only advance system architecture if it works from challenges faced by system architects today.
We wrote this book for two core audiences—professional architects and engineering
students. System architecture as an idea grew out of practitioners’ wisdom and attempts to codify
the challenges of developing new architecture. One core audience is senior professionals who
are faced with architectural decisions. The field encompasses a variety of professionals in senior
technical and managerial roles in technical industries—software, electronics, industrial goods,
aerospace, automotive, and consumer goods.
This book is also focused on engineering students as a core audience. This text grew out of
the graduate course we have taught at MIT for the past 15 years, where we’ve been fortunate
to educate many leaders in the private sector and government. The lens of architecture helps us
understand how a system operates today, but moreover, we believe that it is a necessary compe-
tency to learn in the management of technical organizations.
Visit https://ebookmass.com today to explore
a vast collection of ebooks across various
genres, available in popular formats like
PDF, EPUB, and MOBI, fully compatible with
all devices. Enjoy a seamless reading
experience and effortlessly download high-
quality materials in just a few simple steps.
Plus, don’t miss out on exciting offers that
let you access a wealth of knowledge at the
best prices!
This page intentionally left blank
acknowledgments
CoNTeNTS 11
We’d like to thank the many people that made this book possible. First and foremost, our thanks
to Bill Simmons, Vic Tang, Steve Imrich, Carlos Gorbea, and Peter Davison who contributed
sections from their expertise, and who all provided comments on early drafts. We’re indebted to
Norm Augustine, who in addition to contributing the foreword, shaped our thinking on the topic.
Our reviewers Chris Magee, Warren Seering, Eun Suk Suh, Carlos Morales, Michael Yukish,
and Ernst Fricke helped us deliver crisp messages and helped identify where we had missed key
ideas. We also received a number of anonymous reviews, whose feedback improved the book.
Dov Dori has been an invaluable partner as the developer of the OPM.
Pat Hale supported the development of the curriculum at MIT, and provided feedback on an
early draft. The 63 students of the MIT System Design and Management Class of 2011 reviewed
each chapter in detail and provided mountains of suggestions. In particular, our thanks to Erik
Garcia, Marwan Hussein, Allen Donnelly, Greg Wilmer, Matt Strother, David Petrucci, Suzanne
Livingstone, Michael Livingstone, and Kevin Somerville. Ellen Finnie Duranceau at MIT
Libraries helped us choose a publisher wisely.
Our graduate students over the years have helped shape the book’s content – much of their
work appears here in one form or another. In addition to those mentioned above, we’d like to
thank Morgan Dwyer, Marc Sanchez, Jonathan Battat, Ben Koo, Andreas Hein, and Ryan Boas.
We would like to thank Eun Suk Suh for his contributions to the Global Edition as well.
The staff at Pearson made our book a reality—Holly Stark, Rose Kernan, Erin Ault, Scott
Disanno, and Bram van Kempen. Thanks for all your hard work.
Finally, to our wives Ana, Tess, and Karen, thanks for your patience as we labored on week-
ends and during vacations, enduring the risk that this project become a “forever book.”
Edward Crawley Bruce Cameron Daniel Selva
Cambridge, MA
about the authors
Edward F. Crawley
Edward Crawley is the President of the Skolkovo Institute of Science and Technology (Skoltech)
in Moscow, Russia, and a Professor of Aeronautics and Astronautics and Engineering Systems at
MIT. He received an S.B. and an S.M. in Aeronautics and Astronautics and an Sc.D. in aerospace
structures, all from MIT.
From 1996 to 2003, he was head of the Department of Aeronautics and Astronautics at
MIT. He has served as founding co-director of an international collaboration on the reform of
engineering education and was the lead author of Rethinking Engineering Education: The CDIO
Approach. From 2003 to 2006, he was the Executive Director of the Cambridge-MIT Institute,
a joint venture with Cambridge University funded by the British government and industry; the
Institute’s mission was to understand and generalize how universities can act effectively as
engines of innovation and economic growth.
Dr. Crawley has founded a number of companies. ACX, a product development and manu-
facturing firm; BioScale, a company that develops biomolecular detectors; Dataxu, a company
in Internet advertising placement; and Ekotrope, a company that supplies energy portfolio analy-
sis to businesses. From 2003 to 2012, he served on the Board of Directors of Orbital Sciences
Corporation (ORB).
Professor Crawley is a Fellow of the AIAA (American Institute of Aeronautics and
Astronautics) and Royal Aeronautical Society (UK) and a member of the Royal Swedish Acad-
emy of Engineering Science, the Royal Academy of Engineering (UK), the Chinese Academy of
Engineering, and the National Academy of Engineering (US).
Bruce G. Cameron
Bruce Cameron is the founder of Technology Strategy Partners (TSP), a consulting firm, and the
Director of the System Architecture Lab at MIT. Dr. Cameron received his undergraduate degree
from the University of Toronto, and graduate degrees from MIT.
As a Partner at TSP, Dr. Cameron consults on system architecture, product development,
technology strategy, and investment evaluation. He has worked with more than 60 Fortune 500
firms in high tech, aerospace, transportation, and consumer goods, including BP, Dell, Nokia,
Caterpillar, AMGEN, Verizon, and NASA.
Dr. Cameron teaches system architecture and technology strategy at the Sloan School of
Management and in the School of Engineering at MIT. Previously at MIT, Dr. Cameron ran the
MIT Commonality Study, which comprised over 30 firms spanning 8 years.
Previously, Dr. Cameron worked in high tech and banking, where he built advanced ana-
lytics for managing complex development programs. Earlier in his career, he was a system
engineer at MDA Space Systems, and has built hardware currently in orbit. He is a past board
member of the University of Toronto.
ABouT THe AuTHorS 13
Daniel Selva
Daniel Selva is an Assistant Professor in Mechanical and Aerospace Engineering at Cornell. He
has degrees in electrical engineering and aeronautical engineering from Polytechnic University
of Catalonia (UPC), Supaero, and MIT.
Professor Selva’s research focuses on applications of system architecture, knowledge
engineering, and machine learning tools to early design activities. His work has been applied
to the NASA Earth Science Decadal Survey, the Iridium GeoScan Program, and the NASA
Tracking and Data Relay Satellite System (TDRSS), where he developed architectural analysis
in support of system architects and executives. He is the recipient of Best Paper and Hottest
Article awards.
Between 2004 and 2008, he worked for Arianespace in Kourou, French Guiana, as a mem-
ber of the Ariane 5 Launch team, specializing in the On Board Data Handling, and Guidance,
Navigation and Control. He has previously worked for Cambrian Innovation in the development
of novel bioelectromechanical systems for use on orbit, and at Hewlett Packard on the monitoring
of banking networks. He is a member of the Board of Advisors for NuOrion Partners, a wealth
management firm.
This page intentionally left blank
Part 1
System Thinking
Part 1: System Thinking focuses on the opportunities presented in system architecture, namely, the
opportunity to articulate the key decisions that define a system and to choose an architecture to
match complex challenges.
Chapter 1: Introduction to System Architecture presents the idea of architecture with exam-
ples, identifies good architecture, and outlines the book. Chapter 2: System Thinking assembles
the ideas necessary for system analysis. Chapter 3: Thinking about Complex Systems identifies the
constituent modes of thinking we will use to analyze system architecture.
Chapter 1
Introduction to System Architecture
The simplest notion of architecture we will use is that architecture is an abstract descrip-
tion of the entities of a system and the relationship between those entities. In systems built by
humans, this architecture can be represented as a set of decisions.
The premise of this text is that our systems are more likely to be successful if we are careful
about identifying and making the decisions that establish the architecture of a system. This text is
an attempt to encode experience and analysis about early system decisions and to recognize that
these choices share common themes. Over the past 30 years, analysis and computational effort
have opened a broad tradespace of options, and in many areas, that tradespace grew faster than
our ability to understand it. The field of system architecture grew out of practitioners’ attempts
to capture expert wisdom from past designs and to structure a broader understanding of potential
future designs.
The market context in which our products and systems compete does not offer any comfort.
Consider Boeing’s decision to “bet the company” on the development of the 787 aircraft and the
associated composite technology. Boeing is half of a global duopoly for large passenger aircraft,
yet in its core business, rather than spreading risk across many small programs, the firm turns
on a single product’s emergent success or failure. The global market for mobile devices is larger
and more competitive still. Although it can be argued that the product risk is more diversified
(that is, an individual product development investment is a smaller fraction of firm revenues) in
the mobile sector, witness the declines of former giants BlackBerry and Ericsson. To capture
market share, systems must innovate on the product offering, incorporate novel technologies,
and address multiple markets. To compete on tight margins, they must be designed to optimize
manufacturing cost, delivered through multi-tiered supply chains. We will argue that good archi-
tectural decisions made by firms can create competitive advantage in difficult markets, but bad
decisions can hobble large developments from the outset.
18 part1 • SyStemthInkIng
Every system built by humans has an architecture. Products such as mobile phone software,
cars, and semiconductor capital equipment are defined by a few key decisions that are made
early in each program’s lifecycle. For example, early decisions in automotive development, such
as the mounting of the engine, drive a host of downstream decisions. Choosing to mount an
engine transversely in a car has implications for the modularization of the engine, gearbox, and
drivetrain, as well as for the suspension and the passenger compartment. The architecture of a
system conveys a great deal about how the product is organized.
In the design of complex systems, many of these early architectural decisions are made
without full knowledge of the system’s eventual scope. These early decisions have enormous
impact on the eventual design. They constrain the envelope of performance, they restrict poten-
tial manufacturing sites, they make it possible or impossible for suppliers to capture after-market
revenue share, and so forth. As an example of gathering downstream information for upstream
consumption, the width of John Deere’s crop sprayers is constrained to be less than the column
separation at the manufacturing site. In this case the width constraint is obvious to the develop-
ment team and was not uncertain or hidden, but it is one of the main variables in the productivity
equation for a crop sprayer.
The central assertion of this text is that these early decisions can be analyzed and treated.
Despite uncertainty around scope, even without knowing the detailed design of components, the
architecture of the system merits scrutiny. Architecting a system is a soft process, a composite
of science and art; we harbor no fantasies that this can or should be a linear process that results
in an optimal solution. Rather, we wrote this text to bring together what we’ve learned about the
core ideas and practices that compose system architecture. Our central assertion is that structured
creativity is better than unstructured creativity.
This focus on decisions enables system architects to directly trade the choices for each
decision, rather than the underlying designs they represent, thus encouraging broader concept
evaluation. At the same time, this decision language enables system architects to order decisions
according to their leverage on the system performance, in recognition that system architectures
are rarely chosen in one fell swoop; rather, they are iteratively defined by a series of choices.
The failed National Polar-Orbiting Environmental Satellite System (NPOESS) is an exemplar
of architectural decisions handicapping a system. NPOESS1 was created in 1994 from the merger
of two existing operational weather satellite programs, one civilian (weather prediction) and one
military (weather and cloud cover imagery). The rationale for the merger was not ill-founded; these
two systems collecting related data presented a $1.3 billion cost consolidation opportunity. [9]
Early in the merged program, a decision was made to include the superset of instruments capability
from both historical programs. For example, the VIIRS (Visible Infrared Image Radiometer Suite)
instrument was expected to combine the capabilities of three historical instruments.
The assumption underlying the program was that the functional complexity of the merged pro-
gram would scale linearly with the sum of the two historical programs. This might have held, had
the program derived needs and concepts from the heritage instruments. However, a second decision
to list new functions independent of the system concept trapped the architectural performance in an
1
The prevalence of challenges with government programs cited here reflects a bias: We have more information about
government programs than about private programs. Our intent is to learn from the challenges, not to comment on public
vs. private.
Chapter1 • IntroduCtIontoSyStemarChIteCture 19
unreachable corner of its envelope. For example, the VIIRS instrument was to accomplish the tasks
of three instruments with less mass and volume than a single historical instrument.
A series of early architectural decisions placed NPOESS on a long and troubled devel-
opment path, attempting to create detailed designs that ignored fundamental system tensions.
Further, a failure to appoint a system architect responsible for managing these trades during
the early years of the program foreshadowed challenges to come. The program was canceled in
2010, $8.5 billion over the original $6.5 billion estimate. [10]
This text is not a formula or a manual for product development. Success is not assured.
Experience suggests that getting the architecture wrong will sink the ship but that getting it “right”
merely creates a platform on which the execution of the product can either flourish or flounder.
There are many aspects of this text that are applicable to all systems, whether built by humans,
evolved by society, or naturally evolved. The analysis of architecture can be applied to built or evolved
systems. For example, brain researchers are trying to unfold the architecture of the brain, urban plan-
ners deal with the architecture of cities, and political and other social scientists strive to understand the
architecture of government and society. But we will focus predominantly on built systems.
Learning Objectives
This is a text on how to think, not what to think. Our intent is to help the reader develop a way to
think about and create system architecture, not to provide a set of procedures. Experience suggests
that the best architects have a remarkably common understanding of architecture and its methods,
but the content they work with and the context in which they work vary widely.
This text aims to help system architects to structure and lead the early, conceptual phases of
the system development process, and to support the process throughout its development, deploy-
ment, operation, and evolution.
To these ends, this text provides guidance to help architects:
• Use system thinking in a product context and a system context
• Analyze and critique the architecture of existing systems
• Identify architectural decisions, and differentiate between architectural
and non-architectural decisions
• Create the architecture of new or improved systems, and produce the deliverables
of the architect
• Place the architecture in the context of value and competitive advantage for the
product and the firm
• Drive the ambiguity from the upstream process by defining the context and
boundaries of the system, interpreting needs, setting goals, and defining the
externally delivered functions
• Create the concept for the system, consisting of internal function and form, while
thinking holistically and out of the box when necessary
• Manage the evolution of system complexity and provide for future uncertainty so that
goals are met and functions are delivered, while the system remains comprehensible
to all during its design, implementation, operation, and evolution
• Challenge and critically evaluate current modes of architecting
Visit https://ebookmass.com today to explore
a vast collection of ebooks across various
genres, available in popular formats like
PDF, EPUB, and MOBI, fully compatible with
all devices. Enjoy a seamless reading
experience and effortlessly download high-
quality materials in just a few simple steps.
Plus, don’t miss out on exciting offers that
let you access a wealth of knowledge at the
best prices!
Exploring the Variety of Random
Documents with Different Content
aid the law: and in the same thought he stood confounded at his
own baseness. The loyalty might all be on one side, yet—
“Better see Florio yourself,” he answered. “You can judge. He lives
up in the next cove.”
The stranger argued long, and surrendered reluctantly.
“Well,” he sighed, “I s’pose that’s right, if you’re so stubborn to it. I’ll
go see him.”
He slouched away, and plunged among the bushes. Miles, climbing
toward the house, paused halfway on the slope, to look down
thoughtfully at the shore. Seldom had he encountered so many
persons there in one day; never so many problems. Life, like the
fiddle-heads, seemed to unfold into complexities. The river sparkled
through chinks in the grove, and dazzled broadly across a distant
gap, where the path swung bare to the headland. It was the one
pass to Alward’s. But the stranger did not darken it, either going or
coming.
“He’ll wait down there,” thought Miles, “then come lying back, and
say he can’t find Tony. Spying! And I couldn’t tell him!”
He could not, the fact was adamant—not even to save the hostage
in the other camp.
CHAPTER IX
THE RUNNING BROOK
Some weeks later, at dusk on a calm evening, Miles and his sole
companion sat outdoors for the first time that year. A little bench—
Tony’s handiwork—girdled the hackmatack, so that while leaning
against the same trunk, each saw a different quarter of the valley,
and talked over the shoulder lazily, facing two cardinal points, with
thoughts as far asunder. The time was neither spring nor summer,
but that rare Arcadian interval, too brief for a season, too elusive for
even a transition, and yet in the calendar of sense marked off as
plain as a festival. The night fell neither warm nor cool; a tempered
fragrance of blossoms drew down, without stir of air, from the
orchard over the hill; lower field and shore, river and farthest ridge,
lay confounded in blackness under the stars, land and water parted
only by faint zigzag margins, where the last edge of daylight lined
some inlet or hooked about a promontory.
“Them days,” continued Ella in a distant monotone, “the Injuns
camped in back of ar house at Sweet Water. Old Lewie Neptune, he
was chieft. An’ nights he got drunk, he’d pitch ’em outdoor, so’s all
hands would come beg for in. Midnight an’ bitter cold, sometimes,
women-fo’ks an’ youngsters, they rout us out o’ bed. Big Mary,
Æneas Moon an’ his brother Peter, an’ Lolas an’ Francises an’
Socabasins,—whol’ slews of ’em, all wropped an’ huddledt up in
blankets, scairt, an’ sayin’ they’d be killed. I see the kitchen floor
covered with ’em, many the time, sleepin’ curled round the stove—
Who’s that?”
A flurry of footsteps came up out of the dark; some one raced by
them toward the house.
“We’re out here,” called Miles, rising. “What’s wanted?”
“Oh!” The runner stopped, and returned panting. “I’ve come. You
told me to.”
“Anna!” he cried joyfully.
She stood for an instant motionless, breathing hard; gave a little
failure of a laugh; then spoke quickly, in a voice meant to be calm.
“I stood them as long as I could. Now you must tell me where to go.
Those men! While my father stayed himself, I had somebody; but
now he’s—they’re both against me.” She broke off, as though stifled.
“I’ll never go back; I won’t, I won’t!”
Ella suddenly moved between them.
“Come in the house,” she ordered coldly. “Can’t see ye. If the’ ’s
trouble, we’ll take a light to it, first thing.”
They went in together to the front room. Miles lighted the candle
(which, since Tony’s day, replaced the lamp) and over the trembling
leaf-point of flame saw the girl’s head start into radiance like a
vision. She stood before them with a half-shy, half-defiant
composure; but her eyes and her brown cheeks told another story, a
pulse throbbed in her bare throat, and under the thin blue cloth her
breathing fluttered deeply.
“He tried to beat me,” she said, with the same quiet scorn. “Me,
after all the time I was—”
Ella had stood watching with eyes puckered skeptically, and round
face set in lines of no compromise. But now, without warning, she
flung both her stout arms round the refugee.
“Wild Injuns!” she fumed. “What was I tellin’ ye? You’re all alike, you
men-fo’ks. There, there, poor thing!” Awkward and motherly, she
stroked the girl’s bright hair, scolding and consoling in a breath.
“There, there, nubbin, you’re all of a quiver—all on a string. Worse ’n
old Neptune, they are!—Miles, I left my knittin’ somewheres by that
tree. Jest you hyper out an’ find it.”
Needles and all, it lay on the table before them, but Miles obeyed.
He paced back and forth under the stars, watching the lighted
window. He should be sorry for her, ran his thought. But his one
clear emotion was nothing of the kind; buoyantly, against reason
and through suspense, rioted the conviction that all was well. When
the voices ceased within, he entered, and found the two women
sitting like friends agreed. They smiled at him rather uncertainly.
“Well,” exclaimed the elder, whipping a handkerchief out of sight.
“That’s settled, anyhow. She’ll stay here with us till she finds
somewheres better.”
“But I forgot,” the girl objected. “All my things are there.”
“I’ll get them,” offered Miles.
“You’d look well,” the servant retorted grimly. “I’ll go my own self.
Incidental, I’ll see that pair o’ shoats. And they won’t ask me to set
and come again, either!”
“But,” said the girl, “they’ll come after me.”
“Let ’em!” cried Ella, with sudden extravagance. “I’ll set ’em down so
hard they—they can comb their hair with their spinal columes! Let
’em come.”
For that night no one accepted the challenge; and next morning Ella
promptly descended on Alward’s, to return in ferocious triumph,
bearing a little armful of spoils.
“There’s your clothes!” she cried with the voice of Deborah. “A haley
old mess that house is already, without ye! What did I say to ’em?
Never you mind. They know more ’n they did. The fear o’ the Lord’s
the beginnin’ o’ wisdom. I said what was vouched to me that hour. I
bit a piece out o’ the roof!”
At all events she had determined the situation, and from now
forward there were three in the house. It seemed incredible. Miles
passed the first days in a dream, a revolution of thoughts and
habits. To have this shining guest come and go upon the stairs, or sit
at table like a mortal, or read beside the window on rainy
afternoons, or move at night overhead in Tony’s chamber, not only
threw all indoor routine into the bright confusion of drama, but
changed the very air upon the hills, the light on the waters. The
valley was visited, like the plains of Mamre.
And even when this earliest wonder passed, and they began to live
as though always under the same roof, he could not find the old
bearings. The change had scattered, tossed, and revived his
faculties, as haymakers pitch a mouldy windrow abroad in the sun.
By an odd transfer, she who rightfully should radiate all that was
new and strange, had slipped at once into customary life,
established, familiar, like a thing of childhood; and when they walked
the shore, dug in the garden side by side, or tended lamps in the
early evening, it was she who always had belonged there: all other
things—trees he had seen grow, rocks he knew in every line and
fissure, paths he could follow running in the dark—had altered as
after long absence or some new gift of sight.
It was a happy, incomprehensible time; none the less happy,
although he felt somehow that vague elements were weaving into
danger, that an unknown thread guided them in a maze. Perhaps it
was only that their delight would keep no even level, but daily
mounted; perhaps that in their simplest talk, when their friendship
seemed the oldest, there fell a silence, a chance word, a shock of
difference or agreement, a flash of bygone things, to show how
unerringly their lines converged, across what gulfs.
One afternoon, when summer had glowed and ripened, they
revisited Kilmarnock Brook. Alders flanked the bend through a long
meadow, mapping it distantly as a curved wall of darker green, and
losing it, to near approach, in a cool, low wood where grassy
clearings wound so intricately that a stranger (unless he made the
one plunge through tangle) might wander among leaves, see the
oozy light quivering over them from below, and hear the invisible
water sing like a stream of Tantalus. But Anna and Miles knew all
these interlocked recesses, and, threading them in and out, had
reached their own secret place,—an alder closet, where a tiny
crescent of lawn curved round a pool. On a bank which ran smoothly
into brown water, they sat a little apart, in shadow. Above them
sunlight dappled the leaves, and day-flies danced in brief ecstasy;
below, with a delicate breath of steeping earth and roots and
brookmint, the water stole away silently, to take up its tinkling
narrative round the next bend.
For a long time neither had spoken. Suddenly Miles laughed.
“Ophelia!”
She was looking past her open book, considering the pool.
“You needn’t call names,” she replied, without rousing. “Besides, I
don’t know what you mean.”
“‘Read on this book!’” he scoffed. “The old chucklehead knew! No
girl would ever read in one.”
“A lot you know about them!” She laughed at him, with a sidelong
glance, but quickly returned to her contemplation. “I was thinking.”
“What?”
She shook her head. A leaf-pattern of shadows and golden flame
settled once more upon it, trembling.
“The river-drivers,” she answered at last. “I was only thinking about
the river-drivers.”
Following her glance, he tried, as he had so often tried in the last
weeks, to see with her eyes. The peace of the pool beside them, like
all peace in Nature, was an illusion. Minnows steered over the brown
sand, or whipped their magnified shadows, blurred and globular,
through sunny patches under the farther bank; even where the
water lay most dark and thick, weeds tugged slowly at the tether;
and over the surface her “river-drivers,” snapping and kicking
between wind and water, floated erratically down an imperceptible
current.
“About those?” he asked incredulously. “What, those beetles?”
“Yes.” Her eyes danced with that look of hers which he had never
seen in any other person,—a look both grave and whimsical. “Yes,
they’re only beetles. See, though: they scoot here and there, but
always head upstream. They can’t have any reason to, and it’s so
much easier going down. And still they’re stubborn, and fight along.
I wonder—I think they must have an Idea.”
“You’re a funny girl!” he laughed. Yet as he watched, the darting
insects began to appear not wholly insensate.
“Now the fish down there,” she continued, as though to herself,
“they nose about their business. And the day-flies—with them it’s all
dancing,—just eat, drink, and be merry. But the river-drivers—see
that one, floating on the blade of grass, all tired out; and there he
goes again, up and up, and all the time carried below. They’re like—
like people. They’re betwixt and between, like us. And it may be no
use. But they must. Their Idea. And the stream flows down and
down, and sweeps everything—”
Her words were quiet as the brook beyond.
“A parable,” said Miles.
His voice rose no higher; for both were suddenly a little awed, as
though their spirits had caught some rushing echo of that broader
flood, the irrevocable and universal. And now some influence as
wide, something neither gradual nor swift, closed about them
powerfully. They had leaned forward, shoulder to shoulder, over the
brown pool; but at this mystical, blind accession, each felt the other
tremble and draw back.
A kingfisher chattered angrily, away in the upper reaches. It was the
recurring silence, however, that alarmed. Of all their silences, this
seemed as it were the end, the turning, and the explication. But still
it endured, throbbing with a perilous energy.
Slowly, in a kind of sleep-waking effort, the girl got upon her feet.
“Come,” she said. Her face, in the alder shadows, was very pale. A
shiver of light from the brook played golden about her throat, like
the reflected glow of buttercups in the children’s game.
“Come,” she repeated. “We can’t—we must get home.”
Moved by the helplessness of that command, he followed. They
crossed the sunset pastures almost without word or look, like
pilgrims crossing the Debatable Ground. And when they had climbed
the last hill, and come racing steeply down toward the river and the
house, she went straight to the shelter of Ella’s kitchen.
He did not see her alone again till that evening. Meanwhile he had
walked the shore, raging at himself for what had passed, put almost
beside his reason at thought of what might come. After blindness, it
was an aching sight that disclosed how their friendship—so
wholesome, firm, and precious—could change at a breath, and in
the most tranquil moment of security could totter above unknown
deeps. Was he then worse than Tony, and their house no better than
the drunkard’s? This girl had fled to him; she had taken his
promises, was here upon his honor; and now, because he had
willfully drifted down a pleasant way, they had reached such a pass
that—He closed the thought with a groan. By some detestable trick,
he foresaw, their very speech could no longer be free and honest.
She made no offer, that evening, to go down with him to the lamps;
and he was rather glad of the fact than sorry at its cause. To walk
alone from tower to tower, through the cool firs and cedars, proved
a respite. Yet when he faced the hill to return, trepidation seized him
afresh. He climbed toward the house, vexed and wondering; and for
the second time in all his memory, was afraid to enter.
She sat behind the candle-flame, a great book flattened wide on the
table, and her head bent over it as for dear life. All the brightness in
the room had gathered in this corner, and at first he dared not go
near. But it was now or never with his play-acting; and so, choosing
a book at random, he sat down opposite her resolutely, to begin the
pretense that all things remained as before.
Ella had gone to bed with the birds. Except the two readers, all the
world might have been asleep. Their breathing, and the tick of a
death watch in the wall, made the only sounds in house or valley.
For all the window stood open, the little blade of light between them
reared without wavering. This silence at full stretch, this
preposterous calmness at close range, were alike unreal and
unbearable. His book appeared to be “The Polar and Tropical
Worlds,” a treasury of boyhood; but the pictures swam in a blur—
icebergs, gorillas, the open coffin on Spitzbergen, the march of land-
crabs through a palm-grove, all an empty jumble. Sometimes his
eyesight escaped the page; but then perhaps he found her looking
up, by the same chance; caught for an instant, as her eyes dropped,
the last of a pitiful, appealing light; and plunged into his book again,
like a desperate man hunting a text of divination.
He might thus have turned a hundred pages, and she none at all,
when the contest ended. There came a stir, a little broken sound,
abrupt and choking, which tugged at his heart more than words.
“Oh,” she sobbed, “where can I go next?” and dropped head upon
arms, across the open volume.
As though a musket were shot off in the room, his chair had struck
the floor. He circled the table and caught her up, in a gust that sent
the candle-light reeling.
“Oh, what a wretched girl!” she cried, her voice stifled in his jacket.
All the inevitable drift of their summer, the whole multitude of their
hidden motives, shone clear before and about them,—a wide,
manifold peace in the tumult, like a field of daisies seen by lightning.
CHAPTER X
TONY PASSES
ebookmasss.com