Software Architecture FundamentalsA Study Guide

for the Certified Professional for Software

Architecture Foundation Level iSAQB compliant
1st Edition Mahbouba Gharbi download
https://textbookfull.com/product/software-architecture-
fundamentalsa-study-guide-for-the-certified-professional-for-
software-architecture-foundation-level-isaqb-compliant-1st-
edition-mahbouba-gharbi/

Download more ebook from https://textbookfull.com

We believe these products will be a great fit for you. Click
the link to download now, or visit textbookfull.com
to discover even more!

Software Architecture for Business Lina Khalid

https://textbookfull.com/product/software-architecture-for-
business-lina-khalid/

Software Architecture for Big Data and the Cloud 1st

Edition Ivan Mistrik

https://textbookfull.com/product/software-architecture-for-big-
data-and-the-cloud-1st-edition-ivan-mistrik/

Assembly Programming and Computer Architecture for

Software Engineers Brian Hall

https://textbookfull.com/product/assembly-programming-and-
computer-architecture-for-software-engineers-brian-hall/

Software Product Management The ISPMA Compliant Study

Guide and Handbook 1st Edition Hans-Bernd Kittlaus

https://textbookfull.com/product/software-product-management-the-
ispma-compliant-study-guide-and-handbook-1st-edition-hans-bernd-
kittlaus/
Incremental Software Architecture A Method for Saving
Failing IT Implementations 1st Edition Michael Bell

https://textbookfull.com/product/incremental-software-
architecture-a-method-for-saving-failing-it-implementations-1st-
edition-michael-bell/

Software Adaptation in an Open Environment: a software

architecture perspective 1st Edition Yu Zhou

https://textbookfull.com/product/software-adaptation-in-an-open-
environment-a-software-architecture-perspective-1st-edition-yu-
zhou/

Software Architecture 12th European Conference on

Software Architecture ECSA 2018 Madrid Spain September
24 28 2018 Proceedings Carlos E. Cuesta

https://textbookfull.com/product/software-architecture-12th-
european-conference-on-software-architecture-ecsa-2018-madrid-
spain-september-24-28-2018-proceedings-carlos-e-cuesta/

PSPP Users Guide 1st Edition Free Software Foundation

https://textbookfull.com/product/pspp-users-guide-1st-edition-
free-software-foundation/

CWSP Certified Wireless Security Professional Official

Study Guide Coll.

https://textbookfull.com/product/cwsp-certified-wireless-
security-professional-official-study-guide-coll/
Mahbouba Gharbi is managing director and Chief Architect at ITech
Progress GmbH, and chairman of the board at the International
Software Architecture Qualification Board (iSAQB). She is a self-
confessed software architecture enthusiast and the author of many
expert articles. She is a welcome guest speaker at numerous
international conferences.

Prof. Dr. Arne Koschel is a lecturer at the University of Applied

Sciences and Arts, Hannover, Germany specializing in distributed
(information) systems. He has many years of industry experience
planning and developing distributed information systems. His
lectures include a broad range of IT topics, including cloud
computing, integration, middleware, microservices, and SOA. He is
an active member of the iSAQB board.

Prof. Dr. Andreas Rausch is head of the software systems department

at the Technical University of Clausthal. He is a consultant and lead
software architect for a number of large-scale distributed software
systems.
Mahbouba Gharbi · Arne Koschel · Andreas Rausch

Software Architecture Fundamentals

A Study Guide for the Certified Professional for Software
Architecture®
– Foundation Level
– iSAQB compliant

Content proofreading by Andrew Le Gear

Mahbouba Gharbi · [email protected]
Arne Koschel · [email protected]
Andreas Rausch · [email protected]

Editor: Michael Barabas / Christa Preisendanz

Content proofreading: Andrew Le Gear
Copyeditor: Jeremy Cloot
Layout and type: Josef Hegele
Cover design: Helmut Kraus, www.exclam.de

Library of Congress Control Number: 2019931449

Bibliografische Information der Deutschen Nationalbibliothek

Die Deutsche Nationalbibliothek verzeichnet diese Publikation in der Deutschen
Nationalbibliografie; detaillierte bibliografische Daten sind im Internet über
http://dnb.d-nb.de abrufbar.
978-3-86490-625-1

Copyright © 2019 dpunkt.verlag GmbH

Wieblinger Weg 17
69123 Heidelberg

Title of the German original: Basiswissen für Softwarearchitekten.

Aus- und Weiterbildung nach iSAQB-Standard zum Certified Professional for
Software Architecture – Foundation Level.
3., überarb. u. akt. Auflage 2018
ISBN 978-3-86490-499-8

Many of the designations in this book used by manufacturers and sellers to

distinguish their products are claimed as trademarks of their respective companies.
Where those designations appear in this book, and dpunkt.verlag was aware of a
trademark claim, the designations have been printed in caps or initial caps. They
are used in editorial fashion only and for the benefit of such companies, they are
not intended to convey endorsement or other affiliation with this book. No part of
the material protected by this copyright notice may be reproduced or utilized in any
form, electronic or mechanical, including photocopying, recording, or by any
information storage and retrieval system, without written permission of the
copyright owner. While reasonable care has been exercised in the preparation of
this book, the publisher and author assume no responsibility for errors or omissions,
or for damages resulting from the use of the information contained herein.
This book is printed on acid-free paper.
Printed in the U.S.A
Preface

In addition to motivated teams and great management, software

architecture is an important factor for the success of any software
project. In the context of systematic design and construction, solid
software architecture ensures the fulfilment of quality requirements
such as extensibility, flexibility, performance, and time-to-market.
Software architects reconcile customer requirements with the
available technical options and the prevailing conditions and
constraints. They ensure the creation of appropriate structures and
smooth interaction of all system components. As team players, they
work closely with software developers and other parties involved in the
project.
The International Software Architecture Qualification Board
(iSAQB) is an independent international body that defines standards for
training, examination, and certification of software architects. Software
Architecture Fundamentals is based on the curriculum for the
iSAQB’s Certified Professional for Software Architecture – Foundation Level
(CPSA-F) course.
The text is based on the revised version 4.1.1 of the curriculum,
which has been expanded to cover new aspects of domain-driven design
(DDD). DDD enables software architects to design large-scale
functional structures and gain a better understanding of the overall
interaction of functional components. The current curriculum also
covers numerous new architectural patterns such as microservices.
CPSA-F certification ensures that software architects have sound
levels of knowledge and expertise for the design of small and medium-
sized systems. Based on a detailed requirements specification, they can
then design and document appropriate software architectures. CPSA-F
graduates have the requisite skills for making problem-specific design
decisions that build on their previous practical experience.
This self-study book enables you to prepare for the certification
examination. It assumes that you have practical experience designing
and developing software systems, command of a high-level
programming language, and an understanding of the basics of UML.
Because lectures alone cannot replace interaction with other software
architects, we also recommend participation at iSAQB attendance-based
events.
Benefit from our many years of experience in software and systems
engineering, and in the design and construction of medium- and large-
scale IT systems.
We hope you enjoy reading our book and wish you every success
with your CPSA-F training and certification!

Mahbouba Gharbi, Arne Koschel, Andreas Rausch

December 2018
Content

1 Introduction
1.1 Software architecture as an aspect of software engineering
1.2 iSAQB: The International Software Architecture Qualification
Board
1.3 Certified Professional for Software Architecture – Foundation and
Advanced Level
1.4 The aim of this book
1.5 Prerequisites
1.6 Reader’s guide
1.7 Target audience
1.8 Acknowledgements

2 Software Architecture Fundamentals

2.1 Integration with the iSAQB curriculum
2.2 Software-intensive systems and software architectures
2.3 Fundamental software architecture concepts
2.4 A bird’s-eye view of software architecture design
2.5 Test your knowledge

3 Designing Software Architectures

3.1 Integration with the iSAQB curriculum
3.2 Overview of the architecture design process
3.3 Design principles and heuristics
3.4 Architecture-centric development approaches
3.5 Techniques for a good design
3.6 Architectural patterns
3.7 Design patterns
3.8 Test your knowledge

4 Description and Communication of Software Architectures

4.1 Integration with the iSAQB curriculum
4.2 The CoCoME example
4.3 Views and templates
4.4 Technical/cross-cutting concepts in software architectures
4.5 Architecture and implementation
4.6 Common document types for software architectures
4.7 Best-practice rules for documentation
4.8 Examples of alternative architecture frameworks
4.9 Test your knowledge

5 Software Architectures and Quality

5.1 Integration with the iSAQB curriculum
5.2 Evaluating software architectures
5.3 Prototypes and technical proof of concept
5.4 Architecture analysis
5.5 Test your knowledge

6 Tools for Software Architects

6.1 Integration with the iSAQB curriculum
6.2 General information
6.3 Requirements management tools
6.4 Modeling tools
6.5 Generation tools
6.6 Static code analysis tools
6.7 Dynamic analysis tools
6.8 Build management tools
6.9 Configuration and version management tools
6.10 Code management tools
6.11 Testing tools
6.12 Documentation tools
6.13 Test your knowledge

Appendix

A Sample Questions
A.1 Excerpts from the examination regulations
A.2 Sample Questions

B List of Abbreviations

C Glossary

D References
Table of Contents

1 Introduction
1.1 Software architecture as an aspect of software engineering
1.2 iSAQB: The International Software Architecture Qualification
Board
1.3 Certified Professional for Software Architecture – Foundation and
Advanced Level
1.4 The aim of this book
1.5 Prerequisites
1.6 Reader’s guide
1.7 Target audience
1.8 Acknowledgements

2 Software Architecture Fundamentals

2.1 Integration with the iSAQB curriculum
2.1.1 Learning goals
2.2 Software-intensive systems and software architectures
2.2.1 What is a software-intensive system?
2.2.2 Types of software-intensive systems
2.2.3 The importance of software architecture for a software-
intensive system
2.3 Fundamental software architecture concepts
2.3.1 What is a software architecture?
2.3.2 Building blocks, interfaces, and configurations
 2.3.3 Concepts for describing software architectures
2.3.4 Architectural description and architectural levels
2.3.5 Interactions between software architecture and
environment
2.3.6 Quality and value of a software architecture
2.4 A bird’s-eye view of software architecture design
2.4.1 Objectives and functions of software architecture design
2.4.2 Overview of software architecture design
2.4.3 Interplay between activities and abstraction levels within the
design
2.4.4 A software architect’s tasks and relationships with other
roles
2.5 Test your knowledge

3 Designing Software Architectures

3.1 Integration with the iSAQB curriculum
3.1.1 Learning goals
3.2 Overview of the architecture design process
3.3 Design principles and heuristics
3.3.1 Top-down and bottom-up
3.3.2 Hierarchical (de)composition
3.3.2.1 Divide and conquer
3.3.2.2 Decomposition principles
3.3.2.3 The “as-simple-as-possible” principle
3.3.2.4 Separation of concerns
3.3.3 Lean interfaces and information hiding
3.3.3.1 Information hiding
3.3.3.2 Use of interfaces
3.3.4 Regular refactoring and redesign
3.4 Architecture-centric development approaches
3.4.1 Domain-driven design
3.4.1.1 Functional models as the basis for a design
 3.4.1.2 Systematic management of domain objects
3.4.1.3 Structuring of the functional domain
3.4.1.4 Types of domains
3.4.1.5 Integration of domains
3.4.2 MDA
3.4.3 Reference architectures
3.4.3.1 Generative creation of system building blocks
3.4.3.2 Aspect orientation
3.4.3.3 Object orientation
3.4.3.4 Procedural approaches
3.5 Techniques for a good design
3.5.1 Degenerated design
3.5.2 Loose coupling
3.5.3 High cohesion
3.5.4 The open/closed principle
3.5.5 Dependency inversion
3.5.6 Separation of interfaces
3.5.7 Resolving cyclic dependencies
3.5.8 Liskov’s substitution principle
3.6 Architectural patterns
3.6.1 Adaptable systems
3.6.1.1 Dependency Injection
3.6.2 Interactive systems
3.6.2.1 Model-view-controller pattern
3.6.2.2 Model-view-presenter pattern
3.6.2.3 Presentation-abstraction-control
3.6.3 From chaos to structure
3.6.3.1 Layered architecture
3.6.3.2 Pipes and filters
3.6.3.3 Blackboard
3.6.4 Distributed systems
 3.6.4.1 Broker
3.6.4.2 Service orientation
3.6.4.3 Modularization
3.6.4.4 Microservices
3.7 Design patterns
3.7.1 Adapter
3.7.2 Observer
3.7.3 Decorator
3.7.4 Proxy
3.7.5 Facade
3.7.6 Bridge
3.7.7 State
3.7.8 Mediator
3.8 Test your knowledge

4 Description and Communication of Software Architectures

4.1 Integration with the iSAQB curriculum
4.1.1 Learning goals
4.2 The CoCoME example
4.2.1 Use cases in the CoCoME system
4.2.2 Overview of the structure of the CoCoME system
4.3 Views and templates
4.3.1 Well-established views as defined by the iSAQB
4.3.2 UML diagrams as a notation tool in view descriptions
4.3.3 View description: high-level structure and an example
4.3.3.1 High-level structure: template-type view
description
4.3.3.2 Example: Excerpt from a view description for a
building block view
4.3.4 Context view (or context diagram)
4.3.5 Building block view
4.3.6 Runtime view
 4.3.7 Deployment/infrastructure view
4.3.8 Interdependencies of architecture views
4.3.9 Hierarchical refinement of architecture views
4.4 Technical/cross-cutting concepts in software architectures
4.4.1 Technical/cross-cutting concepts - sample dimensions
4.4.2 Error handling
4.4.3 Security
4.5 Architecture and implementation
4.5.1 Sample implementation
4.6 Common document types for software architectures
4.6.1 Central architecture description
4.6.2 Architecture overview
4.6.3 Document overview
4.6.4 Overview presentation
4.6.5 Architecture wallpaper
4.6.6 Documentation handbook
4.6.7 Technical Information
4.6.8 Documentation of external interfaces
4.6.9 Template
4.7 Best-practice rules for documentation
4.7.1 Rule 1: Write from the readers’ perspective
4.7.2 Rule 2: Avoid unnecessary repetition
4.7.3 Rule 3: Avoid ambiguity
4.7.4 Rule 4: Standardized organizational structure or templates
4.7.5 Rule 5: Justify important decisions in writing
4.7.6 Rule 6: Check the documentation’s suitability for use
4.7.7 Rule 7: Uncluttered diagrams
4.7.8 Rule 8: Regular updates
4.8 Examples of alternative architecture frameworks
4.8.1 The 4+1 framework
4.8.2 RM-ODP
 4.8.3 SAGA
4.9 Test your knowledge

5 Software Architectures and Quality

5.1 Integration with the iSAQB curriculum
5.1.1 Learning goals
5.2 Evaluating software architectures
5.2.1 Qualitative evaluation
5.2.1.1 DIN ISO/IEC 25010
5.2.1.2 Quality characteristics
5.2.1.3 Additional quality characteristics
5.2.1.4 Effects of specific quality characteristics
5.2.1.5 Tactics and practices for fulfilling quality
requirements
5.2.2 Quantitative evaluation
5.2.2.1 Checking architecture compliance
5.2.2.2 Metrics
5.2.2.3 Cyclomatic complexity
5.3 Prototypes and technical proof of concept
5.3.1 Technical proof of concept
5.3.2 Prototype
5.3.2.1 Benefits and disadvantages of software prototypes
5.3.2.2 Types of software prototypes
5.4 Architecture analysis
5.4.1 The ATAM method
5.5 Test your knowledge

6 Tools for Software Architects

6.1 Integration with the iSAQB curriculum
6.1.1 Learning goals
6.2 General information
6.2.1 Costs
 6.2.2 Licenses and licensing conditions
6.3 Requirements management tools
6.3.1 Requirements and decision criteria
6.3.2 Challenges faced by requirements management tools
6.3.3 Examples
6.4 Modeling tools
6.4.1 Requirements and decision criteria
6.4.2 Challenges faced by modeling tools
6.4.3 Examples
6.5 Generation tools
6.5.1 Requirements and decision criteria
6.5.2 Challenges faced by code generators
6.5.3 Examples
6.6 Static code analysis tools
6.6.1 Requirements and decision criteria
6.6.2 Challenges faced by static code analysis tools
6.6.3 Examples
6.7 Dynamic analysis tools
6.7.1 Requirements and decision criteria
6.7.2 Challenges faced by dynamic analysis tools
6.7.3 Examples
6.8 Build management tools
6.8.1 Requirements and decision criteria
6.8.2 Challenges faced by build management tools
6.8.3 Examples
6.9 Configuration and version management tools
6.9.1 Requirements and decision criteria
6.9.2 Challenges faced by configuration and version management
tools
6.9.3 Examples
6.10 Code management tools
 6.10.1 Challenges faced by code management tools
6.10.2 Examples
6.11 Testing tools
6.11.1 Requirements and decision criteria
6.11.2 Challenges faced by test tools
6.11.3 Examples
6.12 Documentation tools
6.12.1 Requirements and decision criteria
6.12.2 Challenges faced by documentation tools
6.12.3 Examples
6.13 Test your knowledge

Appendix

A Sample Questions
A.1 Excerpts from the examination regulations
A.2 Sample Questions

B List of Abbreviations

C Glossary

D References
1 Introduction

Nowadays, software is everywhere, from commercial enterprises to

virtually all areas of our day-to-day professional, public, and private
lives. Air travel, phone calls, bank transfers, or driving would all be next
to impossible without software. Software-controlled components can be
found in every home and in many everyday devices, from washing
machines to cars [BJ+06]. Software is not usually autonomous, but is
instead embedded along with hardware and electronics, or as part of the
business processes that companies use to generate value [TT+00].
The value and commercial success of companies and products is
increasingly determined by software and software quality (see [BM00],
[SV99], [TT+00]). Software engineers are thus faced with the challenge
of implementing increasingly complex requirements at ever-increasing
speed using ever-decreasing budgets while maintaining a high level of
software quality.
Continual increase in the size and complexity of software systems
has made them some of the most complex human-made systems ever
created. The best example is the Internet, which is a truly global
software-based system. Internet is now available beyond the bounds of
our home planet on the International Space Station (ISS).
A structured and systematic approach to design is essential for the
success of software-based systems. Despite the use of established
software development methods, the number of unsuccessful software
projects remains alarmingly large. To counter this, we need to avoid as
many errors as possible, or identify and eliminate them during the early
phases of software engineering. Requirements engineering and software
architecture are two of these phases. In the words of Ernst Denert, one
of the fathers of methodical software development, software
architecture is the “Ultimate software engineering discipline” (taken
from Denert’s foreword in [Sie04]).

1.1 Software architecture as an aspect of software

engineering
Problems with software projects were identified as early as the 1960s,
and were referred to then as “the software crisis”. From 7–11 October
1968, the NATO Science Committee invited 62 internationally
renowned researchers and experts to a conference in Garmisch,
Germany, to address the future of software development. This
conference is now regarded as the birth of modern software engineering
[Dij72].

Figure 1-1 Publications on the subject of software architecture since 1973

[Reu12]

Compared to traditional engineering disciplines (such as construction)

that can fall back on several thousand years of experience, software
engineering is still an extremely young discipline. It is therefore no
surprise that the sub-discipline of software architecture is even younger.
Figure 1-1 shows an increasing number of publications on the subject of
software architecture from the 1990s onward [Reu12]. These figures are
taken from The Web of Knowledge—one of the largest and most
renowned publication databases.
With a view to the long history of construction architecture, Marcus
Vitruvius Pollio (a Roman architect from the first century BC) was an
architectural pioneer. In De architecture—nowadays known as Ten Books
on Architecture [Vit60]—he argued that good architecture can be
achieved using a clever combination of the following elements:
Utilitas (usefulness):
The building performs its function.
Firmitas (solidity):
The building is stable and long-lasting.
Venustas (elegance):
The building is aesthetically pleasing.

Figure 1-2 Architecture in ancient Rome

This hypothesis can be directly applied to the discipline of software
architecture. The objective of software architecture (and thus a software
architect’s primary task) is to construct a system that balances the
following three attributes:
Utilitas (usefulness):
The software fulfills the functional and non-functional
requirements of the customer and its users.
Firmitas (solidity):
The software is stable in terms of the specified quality
requirements (for example, the number of simultaneously
supported users). It also has to allow future enhancements without
having to completely rebuild the system.
Venustas (elegance):
The software’s structure makes it intuitive to use, but also easy to
maintain and develop.

1.2 iSAQB: The International Software Architecture

Qualification Board
Software architecture is an extremely young discipline and, despite
many publications on the subject, various opinions still exist regarding
its precise scope and design in the context of computer science and
information technology. The tasks and responsibilities of software
architects are defined in very different ways and are subject to continual
renegotiation during a project.
In contrast, software engineering disciplines such as project
management, requirements engineering, and testing have a more
mature knowledge base. Various independent organizations offer
training curricula that clearly define the knowledge and skills required
by these disciplines (for testing, visit www.istqb.org; for requirements
engineering, visit www.ireb.org; for project management, visit
www.pmi.org).
 In 2008, a group of software architecture experts from business,
industry, and scientific communities formed the International Software
Architecture Qualification Board as a registered association under German
law (iSAQB e.V., www.isaqb.org). The goal of the iSAQB is to define
product- and manufacturer-independent standards for the training and
certification of software architects. Certifications at Foundation,
Advanced, and Expert levels allow software architects to certify their
knowledge, experience, and skills using a recognized procedure (see
figure 1-3).
Because it eliminates the terminological uncertainty referred to
earlier, standardized training benefits established and aspiring software
architects, companies, and training organizations. Precise training
curricula are essential for the examination and certification of aspiring
software, and ensure that high-quality training is available on the basis
of an accepted canon of knowledge.
Certification as a Certified Professional for Software Architecture
(CPSA) is carried out by independent bodies. CPSA Foundation Level
certification is based on a subset of a non-public catalogue of
demanding questions developed by the iSAQB and matched to the
curriculum. Advanced Level certification also requires practical
certification and participation in licensed training courses (or
acknowledgement of equivalent non-iSAQB qualifications). Expert Level
certification is currently in development.
Figure 1-3 iSAQB certification levels (www.isaqb.org)

Various licensed training institutions offer multi-day courses designed

to refresh and deepen candidates’ existing knowledge in these subject
areas. Participation in a course is recommended, but is not a
prerequisite for registration for the certification examination.

1.3 Certified Professional for Software Architecture –

Foundation and Advanced Level
The iSAQB has now defined clear certification guidelines for CPSA
Foundation Level and Advanced Level certification.
Advanced Level certification is modular and consists of individual
courses dedicated to specific core competences for IT professionals:
Methodical competence
Technology-independent skills for systematic approaches to IT
 projects
Technical competence
Skills in the use of technology for solving design tasks
Communicative competence
Communication, presentation, rhetorical, and meeting skills that
increase efficiency during the software development process

Prerequisites for Advanced Level certification are:

CPSA-F (Foundation Level) training and certification
At least 3 years’ professional experience in the IT sector
Active participation in the design and development of at least two
different IT systems
At least 70 credit points from all three competence areas (with a
minimum of 10 credit points for each)

The examination consists of solving a prescribed task and discussion of

the solution with two independent examiners.
For Foundation Level certification is based on knowledge and skills
defined in the iSAQB curriculum [isaqb-curriculum]. These are as
follows:
The definition and importance of software architecture
The tasks and responsibilities of software architects
The role of the software architect within a project
State-of-the-art methods and techniques for the development of
software architectures

The focus is on the acquisition of the following skills:

Coordinating critical software architecture decisions with other
parties involved in requirements management, project
management, testing, and development
Documenting and communicating software architectures on the
basis of views, architectural patterns, and technical concepts
 Understanding the main steps involved in the design of software
architectures and performing them independently for small and
medium-sized systems

Foundation Level training provides the knowledge necessary for

designing and documenting a solution-based software architecture for
small and medium-sized systems, based on a sufficiently detailed
requirements specification. This architecture can then serve as a
template for implementation. Participants are trained to make problem-
oriented design decisions on the basis of previous practical experience.
Figure 1-4 shows the content and weighting of the individual areas
of the curriculum for iSAQB Certified Professional for Software
Architecture (CPSA) Foundation Level training.

Figure 1-4 Structure of the iSAQB curriculum for the CPSA Foundation Level
training

Various independent bodies offer certification based on the iSAQB

curriculum. Examiners use standardized questions prepared by the
iSAQB.
Questions are multiple-choice, so the results are objectively
measurable.
 The examination validates your software architecture capabilities on
paper. It is up to you to prove yourself in real-world situations.

1.4 The aim of this book

Members of the iSAQB developed this book during the creation of the
Certified Professional for Software Architecture, Foundation Level
curriculum. The main aim of the book is to provide a concise summary
of the knowledge required to pass the CPSA Foundation Level
examination, and thus the basic knowledge required for the creation of
successful software architectures. This makes the book an ideal
reference manual when preparing for the examination. In addition to
reading the book, we also strongly recommend participation in the
corresponding training courses, which offer practical examples of
software architectures and the personal experience of our training staff,
both of which go beyond the scope of this book.
The book focuses primarily on methodical skills and knowledge, so
specific implementation technologies and tools are not part of the
standardized training content. Specific notations and acronyms (such as
UML) are to be understood only as examples. The book does not
describe individual, specific procedure models or specific development
processes, and instead provides various examples.
It explains important terms and concepts involved in software
architecture and their relationships with other disciplines. Building on
this, it provides an introduction to the fundamental methods and
techniques required for design and development, description and
communication, and quality assurance in software architectures. It also
addresses the roles, tasks, interactions, and work environment of
software architects, and describes how they integrate with company and
project structures.

1.5 Prerequisites
In line with the aims described above, the book and the iSAQB
curriculum assume you have previous experience in software
development. The following content is neither part of the book nor the
curriculum, although it forms an essential part of every software
architect’s skill set:
Several years of practical experience in software development,
gained by programming differing projects or systems
Advanced knowledge of and practical experience with at least one
high-level programming language
Fundamentals of modeling, abstraction, and UML; in particular
class, package, component, and sequence diagrams and how they
relate to source code
Practical experience in technical documentation; in particular the
documentation of source code, system designs, and technical
concepts

Knowledge and experience of object orientation is also advantageous for

an understanding of some of the concepts involved. Experience in the
design and implementation of distributed applications (such as client-
server systems or web applications) is also desirable.

1.6 Reader’s guide

The structure of this book is primarily oriented to the structure and
content of the iSAQB Foundation Level curriculum. For more details, see
figure 1-4 and [isaqb-curriculum]:
In Chapter 2 we describe terms and software architecture basics,
which are then addressed in more detail in subsequent chapters.
For example, the concept of a software system “view” is introduced
within the context of software architecture.
Practical software architecture design is addressed in Chapter 3.
Topics covered include variants of the architecture development
procedure; important architectural patterns such as views, pipes
Discovering Diverse Content Through
Random Scribd Documents
 “The ball game will be for sport,” he said, “and, as you do not
know just how Indians play ball, I have decided that you shall be
divided. Four of you will play on one side, and five on the other. The
rest of the players will be Indians, and there will be twenty on a
side. They are preparing now. Get ready, for the game will begin
right after the race.”
So, with much joking among themselves, the boys pulled off
their sweaters and prepared for the race.
Swiftwing gave their superfluous clothes into the care of an old
man, who was told to watch carefully that no Mexicans or Apaches
stole anything from him.
Then Swiftwing showed the boys the balls and the bats, which
were like old-fashioned “shinny” sticks, and explained to them how
the game was to be played.
This done, the Indian youth left Frank to divide his party, and
hurried away.
Within three minutes a great shouting announced that the
religious race was over, and one of the buildings had won over the
other.
Barely had this shouting ceased when, with yells like wild
animals, thirty-one young bucks, stripped to the breechcloth, came
from somewhere and rushed upon the white boys.
Hans gave a gurgle of fear and rolled over in a sudden attempt
to take flight.
“Here vas where you lose mein scalp!” he gurgled.
Toots was scared, and his teeth chattered.
“Oh, Lordy!” he gasped. “Mah wool am gone dis time fo’ suah! I
done knowed I’d nebber keep dis wool on mah haid till I got back
home!”
Barney Mulloy squared off, his hands clinched and his eyes
flashing.
“Come on, ye spalpanes!” he grated. “It’s a roight tough bit av a
shcrap we’ll be afther havin’, me laddy-bucks!”
“Gug-gug-good gosh!” stammered Ephraim Gallup, his face
turning pale and his knees knocking together. “We’re ketched in a
trap, by gum! I wish I was to hum on the farm!”
“What’s the meaning of this, Merriwell?” cried Jack Diamond,
clutching Frank’s arm with a strong grip. “Are we in for scalping—or
what?”
“It’s all right,” assured Merriwell. “That’s their way of attracting
the attention of the crowd and informing them that the ball game is
about to begin.”
“Is that all?” gurgled Ephraim, in great relief, seeing the young
Indians gather about but observing they did not offer hostilities.
“Wal, darned if I ain’t afraid I’ll never be able to comb my hair ag’in!
It feels as if it was stickin’ up stiffer than quills on the back of a
hedgehoag.”
The shout from the young bucks had attracted the attention of
the spectators and they were rushing toward the spot.
A hand touched Frank’s arm.
“Come,” said the voice of John Swiftwing. “A place for us to play
will be prepared.”
John was one of the young bucks. He had cast aside the clothes
of civilization, and, like the others, he was stripped to the
breechcloth.
 His physique was magnificent, and Frank regarded him with
admiration. Such broad shoulders, such a deep chest, such hard and
muscular limbs were not common among the Pueblos.
In Swiftwing’s hair eagle feathers had been fastened, and it
seemed that, with his clothes, he had cast aside all the refining
changes of civilization.
He was a savage again!
His eyes were flashing, and his head was poised proudly on his
strong neck. The players looked to him as a leader, and they
followed him to the cleared space where the ball game was to take
place.
Frank had divided his party. Rattleton, Diamond, Mulloy and
Gallup were on one side, while Merriwell, Browning, Hodge,
Dunnerwust and Toots were on the other.
It took but a few moments for all arrangements to be
completed.
The sides of twenty men each were drawn up facing each other,
with an open space between them. The forty players were scattered
over considerable territory. Each man stood in an expectant attitude,
one of the rude bats in his hands, ready for the ball to be put into
play.
The ball was small and hard, and the players could not touch it
with their hands after play began, but they must keep it constantly
in the air. The moment it touched the ground the game was won
and the side upon whose territory it had fallen were defeated.
This was the usual rule, but, on this occasion it was modified
somewhat, as there were white players in the game, and it was not
expected they could do as well as the Indians who were familiar with
the sport. It was decided that the ball must be driven to the ground
twice on one side or the other in order to insure a defeat. It was to
be the “best two out of three.”
Suddenly there was a shrill yell, a sharp crack, and the ball had
been batted into play.
 CHAPTER XXII—THE BALL GAME

Up, up into the air sailed the little ball.

With a shout the players rushed to get beneath it.
Frank found himself on the side opposite Swiftwing.
John was the first to strike the ball after it had been batted into
play.
Down came the little black sphere, and, poising himself on one
foot, the Carlisle “buck” swung his bat and sent the ball straight
toward Frank.
The trick was done with marvelous skill, and it seemed to be a
challenge.
Frank squared himself in a fraction of a second, and then——
Crack!
Back sped the ball.
A whoop of delight went up from Frank’s side.
“Shimminy Gristmas!” cried Hans. “Don’d dot peen a pird! Gif id
to him, Vrankie!”
Crack!
Swiftwing hit the ball, and, with equal skill, he shot it back at
Merriwell.
Frank was expecting this, and he returned it with all the skill of
a professional tennis player.
The spectators roared their applause.
 For some moments this “volleying” was kept up, and then the
ball glanced from Swiftwing’s bat and went high in the air.
Frank had come out best in this first struggle, much to his
surprise, as, not being familiar with the game, he had not
anticipated such success.
The white men in the crowd gave a yell of delight.
Frank caught a glimpse of Inza’s face, and he fancied there was
an expression of disappointment on it.
“I believe she would have been pleased if he had vanquished
me!” thought Frank, a trifle bitterly. “I do not understand her at all of
late.”
He could discern the look of admiration on the girl’s face as she
regarded the magnificent Indian who commanded the players on the
side that opposed Merriwell.
Frank was somewhat dismayed when he discovered that
Whirling Bear was the commander of his side.
The young Indian who had been drunk at Embudo the day
before was straight enough now, and he seemed to be somewhat of
a favorite among the Pueblo athletes.
Not a few of the Indians showed a strong dislike for John
Swiftwing, and Frank understood this was because he had been
away to the white man’s school. They wished to see him beaten at
everything that he might know how weak he had become while he
was learning the white man’s knowledge.
When the ball glanced from Swiftwing’s bat it was not allowed
to fall to the ground. A lithe savage ran under it and sent it spinning
into the air.
Far over Whirling Bear’s side sped the little black sphere.
 Whirling Bear shouted a command.
Like a flash three of the rearmost bucks darted after the ball,
and one of them, who had the speed of the wind, ran under it as it
was falling to the ground. Without stopping or pausing, he swung his
bat and hit the ball.
Oh, what a shout of delight pealed from white men and Indians
alike! Surely the ball had been kept from the ground in a most
amazing manner, for the batter was not able to stop and turn till he
had passed at least forty feet beyond the point where he hit the ball.
There was a rush on Swiftwing’s side, and the ball was
returned.
The one who struck it sent it straight at Hodge.
Bart met it with a good crack and sent it back.
Barney Mulloy poised his bat.
“Begobs! Oi’ll knock the paling off it wid me shtick!” he cried.
With all his might he struck.
And missed it!
But one of the young Indians was on hand, and he seemed
prepared for such an emergency, as he struck the ball before it could
reach the ground, lifting it into the air again, and saving the first
defeat for Swiftwing’s side.
Hans Dunnerwust saw the ball coming in his direction, and he
resolved to get some glory out of the game.
He ran to meet it, tripped himself, fell down, rolled over, sat up,
and swung his bat. In some manner he succeeded in hitting the ball
as he sat on the ground, and he sent it into the air again.
“You don’d done dot mit me!” he cried, and the spectators
roared and cheered, the white men laughing loudly, and not a few of
the Indians betraying mirth.
“Gol darn my punkins!” exclaimed Ephraim Gallup, joyously.
“This is more fun than a darg-fight! Never see nothing like it before!
Let me git a rap at that ball!”
But when he made a run for it, his long legs got tangled with his
bat, and he was tripped with such suddenness that he flipped into
the air as if sent with a spring, turned over and dropped on the back
of his neck.
An Indian struck the ball, however, and it did not touch the
ground.
“Say!” snorted the Vermonter, as he sat up and glared around,
“p’int me aout the critter what done that!”
No one paid any attention to him, so he got up, secured his bat,
and waited for a chance to get at the ball without running after it.
Crack! crack! crack!—the bats were rapping the little ball in
quick succession, and the players and spectators were feverish with
excitement.
The Indians were betting madly on the outcome of the game,
and the white witnesses were taking “chances” on it.
Dan Carver, cool and serene, was covering everything that came
his way, backing Swiftwing’s side.
Frank was watching an opportunity to get in a good “drive.” He
observed that the most of the Indian players knocked the ball into
the air, and he fancied that a drive that would place it might be
successful.
His opportunity came at last.
He gave the ball a fierce crack, sending it shooting over the
heads of the other side, just out of the reach of their bats.
 It dropped in a clear space, before a player could reach it, and a
great shout of victory went up.
Whirling Bear, although the commander of the side that Frank
was on, had said nothing to Merriwell, and he seemed to show signs
of disgust, as if he were not pleased that it should have been a
white lad who had knocked the ball.
Dan Carver did not seem at all disturbed by what had
happened, but continued to take bets, offering to place any sum on
Swiftwing at one or two.
In a moment the game was resumed, and it went forward with
more intensity than before. The players seemed warmed up to the
work, and their skill in keeping the ball in the air was astonishing, to
say the least.
Several of the white players won some glory.
Both Diamond and Rattleton got in good strokes, and Bruce
Browning struck once with all the power in his muscular arms,
sending the ball so high into the air that it was a mere speck and
almost went out of sight.
“Begorra! it’s not such fun as this Oi’ve had since Oi attinded me
larst Oirish fair!” cried Barney, who was in his element. “This b’ates a
wake!”
“It’s a darn sight more fun than shuckin’ corn at a huskin’-bee!”
grinned Ephraim Gallup. “Take that, gol darn ye!”
He managed to hit the ball at last, after missing it three times,
and nearly turning himself wrong side out with the violence of his
efforts.
“Whee!” he squealed, as the little sphere carromed off his bat
and whizzed into the air. “I bet a squash that started the bark on
her!”
Toots got a crack on the shins that upset him and made him
howl with pain.
“Land ob wartermillions!” he wailed. “Nebber see no such mess
as dis am! Dutchmans an’ Irish all mixed up in a stew! An’ ebry one
ob um seems tryin’ teh git a crack at de nigger’s shins wif dem
sticks! I’s gwan teh retellyate on some pussen bimer-by—yes, sar!”
Once Harry Rattleton was able to save Swiftwing’s side from a
second and final defeat. An Indian struck and missed the ball, but
Harry caught it with his bat, having struck almost at the same
instant.
“Gear she hoes—I mean here she goes!” he yelled. “Can’t do it
again over there! We’re going to do you up, after all!”
Finally three players on Whirling Bear’s side ran for a ball.
Dunnerwust and Toots were two of them, and they both fell down,
while an Indian fell on top of them.
Over the three sailed Bart Hodge, his bat poised and his teeth
set. He reached the ball and kept it from striking the ground, but it
glanced from his bat and went off sideways.
It went in a bad direction.
Whirling Bear tried to reach it, but failed, and it fell to the
ground.
And now the sides were tied with the chances even for the final
struggle.
 CHAPTER XXIII—THE WRESTLING
MATCH

Less than half a minute elapsed before the game was resumed.
The players went at it with unabated energy and enthusiasm,
and the excitement was more intense than ever.
This round would settle it.
Whirling Bear was in a bad humor. Although one of the white
lads had won the first set with a drive, it seemed to Whirling Bear
that the second one had been lost because Hodge had not hit the
ball as skillfully as he might.
In fact, Hodge had done well to reach it at all.
Frank and Whirling Bear both rushed at the ball and came face
to face. As Frank struck, he saw the Indian swing his bat.
Whirling Bear did not strike at the ball, although he pretended
to do so.
He struck straight at Frank Merriwell’s head.
Merry saw this and dodged.
He succeeded in hitting the ball, and he escaped Whirling Bear’s
bat at the same time. The bat whizzed through the air.
In another moment Frank was ready to meet the Indian’s
assault, but, seeing he had failed in the first attempt, the Pueblo
darted away.
 “That fellow is treacherous,” Merriwell decided. “He has a
grudge against me for some reason, and I’ll have to keep my eye on
him. If he had hit me, my skull would have been cracked.”
Inza witnessed Merriwell’s peril, and she caught her breath,
uttering a little cry of terror. When Frank dodged, she breathed
again, and she panted:
“Go for him, Frank—don’t let him get away!”
Whirling Bear, however, got away like a leaping cat, and
continued giving orders to his men as if nothing unusual had
happened.
Faster and more furious waxed the game. Spurred on by the
shouts and yells of the spectators, each side was exerting itself to
the very utmost.
It was really very exciting, and the skill of the players aroused
the admiration of all. The Indians handled themselves in a
remarkable manner, and, with one or two exceptions, the white boys
were doing almost as well.
On Whirling Bear’s side Merriwell and Hodge were the most
conspicuous among the white players, while Mulloy and Diamond
showed great skill and judgment on the other side.
“Hurro!” the Irish lad was heard to shout. “It’s hot shtuff we
are, an’ don’t yez fergit thot! Erin go braugh! Th’ United States an’
Ould Oireland feriver!”
For some moments there was a furious volleying, so fierce at
moments that the eye followed the movements of the players and
the flying ball with no little difficulty.
Inza Burrage was greatly excited. She clapped her hands and
waved her handkerchief.
 “Oh, aunt!” she cried; “it’s almost as good as a football game!
Isn’t it just perfectly splendid!”
“It is confusing—very confusing,” said Miss Abigail, severely. “It
seems to be a genuine savage game.”
At last Hodge saw his opportunity, and he drove the ball toward
an opening in the ranks of the opposing players. It was skillfully
done, and, almost before any one could realize it the game was over,
Whirling Bear’s side having conquered.
Then the Indians danced and sang songs of victory.
Swiftwing seemed to take his defeat gracefully, and he insisted
that the white boys, Merriwell and Hodge, and not members of his
own race had brought it about.
Frank told Swiftwing that he was astonished to find the Indians
played the game with so much skill.
“It is great sport,” he said. “I feel well satisfied for my trouble in
visiting Taos.”
“You feel satisfied now,” said Swiftwing, in a peculiar manner.
“You may not be so well satisfied when you depart.”
Frank was puzzled by this remark.
“I wonder what he means by that,” he muttered, as the Indian
walked away.
“Begobs! Oi think he m’anes we’ll be beaten at iverything ilse
we thry,” nodded Barney.
But Frank fancied that was not just what the Indian had meant.
The boys found the Indian who had charge of their clothes, and
soon they were in sweaters.
Whirling Bear sought the party, and, standing with his hands on
his hips, eying them insolently, he said:
 “What white boy think he want to wrastle?”
“Gol darn his eyes!” muttered Ephraim, who did not like the
appearance of the Indian. “I’d like ter thump him betwixt ther eyes!”
“What white boy dare to wrastle with Whirling Bear?” asked the
Indian.
With a spring the impulsive Irish lad landed before the insolent
redskin.
“It’s mesilf that’ll thry yez a whirrul!” he cried.
“You?” said Whirling Bear, contemptuously. “You no wrastle! Go
’way!”
That, as he afterward confessed, made the Irish boy “hot.” He
told Whirling Bear he could stand him on his head in a minute.
“All right,” said the Indian, with a wicked gleam in his black
eyes. “You strip off and try. Come.”
Immediately Barney began to “peel.”
“Look out for him,” warned Frank, assisting the Irish lad to get
out of his sweater. “He is treacherous, and he dislikes all whites. I
can see that. He may try to injure you seriously.”
“Oi’ll kape me oie on th’ spalpane, Frankie. Av he gits th’ bist av
me it’s a smart chap he is.”
In a short time the Irish lad was ready.
The challenge had been heard, and there was a rush of the
spectators to witness the wrestling match.
A ring was formed, and the crowd was kept back by some of
the spectators who appointed themselves for that purpose.
Soon all were ready, and, at opposite sides of the ring, the
white boy and the Indian crouched, their hands on their knees,
watching each other like hawks.
 Suddenly, as if moved by the same impulse, they rushed at each
other and grappled.
Both obtained good holds, and a terrific struggle began.
Barney knew considerable about the science of wrestling, and
he immediately discovered that the Indian was not a novice.
As soon as holds were secured Whirling Bear leaned heavily to
the left and pinned Barney’s right arm close to the elbow, at once
causing the Irish lad trouble.
Barney tried to straighten the Indian, but saw that Whirling Bear
fancied he had an advantage and was determined to hold it.
Now the Irish lad knew that, for all that the redskin was
bothering him by this trick, Whirling Bear could not be firm in such a
position, and it would not be difficult to throw him if the trick came
right.
Barney knew that a wrestler who leans to the left always lays
himself open to the cross-buttock, and he immediately began to
work to use that trip on his opponent.
In order to work the cross-buttock successfully it is necessary to
have a hold that is loose at first and yet firm and then to move with
the utmost rapidity. The least hitch or false move may prove fatal to
the aggressor.
As the Indian and the Irish lad strained and squirmed and
sought to trip each other, Barney worked his hold looser and looser,
all the while watching for the opportunity he sought, although
pretending to be working for something else.
The crowd watched the movements of the contestants with the
greatest interest.
 Dan Carver was on hand, and, after a moment, he offered to
bet even money that the Irish boy would take the first fall. He was
able to get up a small amount, and then, hands in pockets, he
calmly regarded the contest.
Barney was tempted once or twice to try the trip, but was not
quite satisfied with his opportunity. If he tried and failed, the Indian
might throw him heavily by sharply jerking him backward.
Twice Whirling Bear jerked Barney forward to get him off his
guard and then tried the inside click, but failed to throw the sturdy
Irish youth.
This seemed to anger the redskin, for it was plain he had looked
on the white boys with no small contempt, and had anticipated
securing an easy victory.
Furiously he went at Barney, and this gave the white boy the
very opportunity he sought.
Quick as thought Barney turned his left side toward his
opponent, got his hip partly beneath him, and then, with a rapid
movement, crossed both his legs and lifted him from the ground.
Down went Whirling Bear, with Barney uppermost!
It was a pretty fall, and it awoke the admiration of the
spectators so that they cheered the Irish lad heartily.
Barney sprang up, but the Indian arose almost as swiftly, and,
before any one realized it, the struggle was on again.
This time Whirling Bear was fiercer than before. The muscles
stood out on his bare limbs and back, while the cords of his neck
were drawn taut and there were knots in his forehead. The look on
his face was not pleasant to see. He looked as if he longed to
murder the Irish lad.
 Frank was watching every movement closely. He was well
pleased with Barney’s success, but it seemed that the Indian had
been taken by surprise, and it was doubtful if the Irish boy could
repeat the trick.
Barney tried the backheel trip, and his failure to throw Whirling
Bear nearly resulted in his own downfall.
Next Barney attempted the hip stroke, but that was another
failure, and Whirling Bear now seemed like a cat on his feet.
All the while Barney was forced to look out for various trips and
heaves which the Indian attempted in rapid succession.
Some one offered to bet Carver even that the Indian took the
second fall, and the sport shook his head.
“I knew the Irishman was going to surprise him at the start,” he
said. “Now he is out for blood. I’ll go something he takes this fall.”
All at once, in some astonishing manner, the Indian got under
Barney and raised him into the air directly across his back.
Then Whirling Bear lifted Barney above his head to hurl him to
the ground!
 CHAPTER XXIV—THE FOOT RACE

Frank saw a gleaming spirit of evil in the eyes of the savage.

Whirling Bear meant to injure, perhaps to kill, Barney.
He intended to cast the Irish youth down upon his head, and
the prospect was that Barney’s neck would be broken instantly.
Immediately Frank leaped forward.
As the Indian dashed Barney to the ground, Frank caught him
and kept him from falling on his head.
The Irish lad went down heavily, but he was not severely
injured.
Whirling Bear gave a cry of anger when he saw what Merriwell
had done, and then rushed at Frank.
Frank dodged and tripped the Indian with the greatest skill, so
that the redskin was pitched forward on his face and stunned for the
moment.
“If you will try the copper-skin a whirl, I’ll back you for any
amount,” said Dan Carver, quietly.
Whirling Bear sat up, savagely glaring at the white boys.
“No can wrastle with two!” he growled. “One at time is ’nough.
Why other white boy do something?”
“I simply kept you from murdering my friend,” said Frank. “You
were trying to break his neck, and I saw it.”
Whirling Bear got up, looking disgusted.
 “Sometime may get ’nother chance,” he said, and then walked
away, paying no heed to the spectators who were calling for him to
remain and settle the match by seeing who could get the third fall.
“Begorra! it’s a roight nate thrick he did whin he lifted me inther
th’ air,” confessed Barney. “Sorry a bit do Oi know how he did it at
all, at all!”
“I do not think I ever saw a throw made in that manner,”
confessed Frank. “He went under you like an eel, and brought you
up across his back and over his shoulder.”
“He is the champion wrestler of the Pueblos,” declared a
spectator. “I did not fancy you would be able to throw him at all.”
“You should be proud to say you broke even with him,” declared
another.
Frank felt a hand on his arm, and a voice said in his ear:
“The sun priests are resting. While they rest there will be a
footrace, the same as white men run. Will you enter. Swiftwing says
you are a great runner.”
The speaker was a young Indian of evident intelligence.
Frank was willing and ready to take part in the footrace, and he
immediately accepted the invitation.
“I know I shall be pitted against Swiftwing,” he thought, “and it
is liable to be the race of my life, for he can run like the wind. I will
beat him—or die!”
A straight course of nearly a quarter of a mile was prepared,
and the spectators ranged up on either side near the finish.
There were five starters, four of whom were Indians. Merriwell
was the only white persons who had been invited to take part.
 The Indians were stripped for the race, as they had been in
taking part in other sports.
Frank brought out a pair of running shoes, and these he put on.
He removed his sweater and stripped down to a light, sleeveless
undershirt.
As they stood side by side, Swiftwing spoke to Frank.
“Much depends on this race,” he said—“much more than you
can know. Beat me, Merriwell, if you can. You will be sorry if you
fail.”
All this was very mysterious, but Frank returned:
“You may be sure I shall do my best to beat you.”
A moment later a great shout went up from the spectators.
The runners had started, darting off from the scratch like so
many deer.
Swiftwing started in a most astonishing manner, seeming to leap
off at full speed in a second.
Frank was not slow in starting, but he found the Indian had
gained a slight advantage at the outset.
It was a beautiful sight to see the five runners come speeding
along the track, heads up, breasts thrown forward, nostrils dilated
and eyes flashing.
Of them all, two persons seemed to fly over the ground with
very little exertion.
They were John Swiftwing and Frank Merriwell.
At Frank’s side ran a tall Indian who was making great speed,
but did not seem as graceful as the white boy or the Indian in
advance.
 Although Swiftwing had gained an advantage at the start, he
was not able to widen the distance between himself and the white
boy. Close behind him he could hear the feet of Frank Merriwell.
And Frank? He was preparing for one mighty spurt at the last of
the race, feeling that he would surprise Swiftwind then.
The spectators cheered wildly, and some enthusiastic cowboys
fired shots into the air, yelling for the white boy to run faster and not
let a “copper-skin” beat him.
Far ahead at the end of the course Frank saw Inza Burrage
watching their approach. Near her stood an Indian who had just
dismounted from the back of a magnificent horse, which he was
holding.
Inza waved her handkerchief.
Was it a signal to Frank? or was it meant for John Swiftwing?
“In either case,” thought the white boy, “it is enough. I will win!”
He set his teeth and gave a great spurt that must have carried
him into the lead; but, at that moment something happened.
The tall Indian who had been racing at Frank’s side thrust out a
foot and neatly tripped Merriwell up. This happened at the very
moment when the white boy started to spurt, and Frank was flung
into the air and hurled forward upon his head. His hands were thrust
out to break his fall, and he saved himself in a measure, but he was
stunned and lay motionless for some seconds.
With a gasp he sat up.
“Beaten!” he hoarsely grated—“beaten by a foul trick! I did not
think John Swiftwing would have anything to do with a plot of this
sort!”
 Then he saw something that caused his heart to give one mad
leap and stand still.
Swiftwing reached the end of the course. As he rushed over the
line, without pausing, he caught Inza Burrage about the waist,
swung her into the air, tossed her over his shoulder, and——
How was it done? An instant later the Indian was astride the
horse which the other Indian had been holding ready for him. He
still held fast to Inza. Frank heard her scream with sudden terror,
and the cry was drowned by a hoarse sound from Swiftwing. Like an
arrow leaving the bow, the horse, bearing its double burden, shot
away.
 CHAPTER XXV—JOHN
SWIFTWING’S FAREWELL

“White Dove, we are alone in the mountains, where neither friend

nor foe can reach us. Here we will stay. Soon the sun will seek his
bed to rest, and the night will smile down upon us from its starry
eyes, while it breathes a soft breath to smooth the ruffled feathers
of the White Dove. You must have no fear of day or night, for I am
with you, and I will guard you as the she-bear guards its cubs.”
Inza Burrage, her face tear-wet, her hair tumbled and tangled,
her clothing torn in two or three places, turned her gaze
reproachingly upon John Swiftwing.
“It is not the day or the night that I fear,” she said, slowly, with
a dignity that was womanly. “I do not fear the dangers of the
mountains. Wild beasts have no terrors for me now. And still my
heart is frozen within me, and all my body is like ice.”
They were standing on a small plateau, where they could look
away across a plain that lay below them. The sun was in the western
sky. Behind them the sweat-stained horse that had brought them
thither was feeding.
“Why should your heart be frozen and your body like ice?”
asked the Indian, gently, his voice soft and musical, and a light of
tenderness gleaming in his eyes.
 “Because, John Swiftwing—because I fear you!”
“The White Dove should not fear me, for I will guard and
protect her with my life. I will face any peril in defense of her.”
He took a step toward her, but she drew back, flinging out her
hand.
“Stop!” she gasped. “Please—please don’t touch me! I want to
talk to you—I wish to beg you to be merciful and take me back to
those from whom you carried me away!”
He folded his arms and looked at her in silence. It was an
unconscious pose, and never had he looked handsomer than at that
moment. After a little silence he spoke:
“Why should I take you back?” he asked. “I love you, and I
want you for my mate. You shall be my mate. You shall be my wife,
White Dove. We will live together in some beautiful valley, far away
from all the world—live in a little nest that I will find for you. The
sunny days will glide by like a soft-floating stream, and every starry
night shall be a dream of happiness.”
“No! no! no!” she cried, with her hands outflung. “That could
not be!”
“Why not?”
“Because—oh, because!”
“White Dove, don’t you love me?”
“No! no! no!”
“Then your eyes have deceived me, for I fancied I saw love
deep down in them. It must have been the reflection of the love that
was in my heart. But still I know there was encouragement in them.
They spoke like words.”
 “And this is my punishment!” sobbed the poor girl. “Oh, Mr.
Swiftwing, it was not love—it was admiration! I thought you so brave
and so noble! I did not dream you could do such a wicked thing as
you have done! No one could have made me believe it was in your
heart. I would have defended you against the tongues of all
accusers. But now—how my idol is shattered!”
He shrank beneath her words, as if they were blows from a
whip. For a moment he cowered, and then he lifted his head with an
angry, defiant toss.
“They told you,” he said—“they told you the red streak was in
me! They were right! I heard them say it! They told you that my
heart was the heart of an Indian, even though I wore white man’s
clothes and read white man’s books. They were right! They told you
all the education I might receive would not change my nature. They
were right! God made the white man, and He made the Indian. He
did not make them alike, and what God has made man cannot
change. The white man took me to give me an education. Bah!
What is an education to me? What would it mean if I had the finest
education that the white man could give me? I would still remain an
Indian, and, with all my education, I would turn back to my people,
live as they live and die as they die—no better. I have thought it all
out. I have thought it is no use to try to be anything but an Indian.
The fight is ended! I am an Indian again!”
Inza’s heart was full of despair.
“I will not believe you are as bad as you think!” she cried. “I
saw something noble in your face, and I think it came from your
heart. See, Swiftwing—on my knees I beg you to take me back to
my friends! I know you will not refuse me! Take me back to them,
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!

textbookfull.com