|
Books > Arts & Architecture > Architecture > General
How to Read Modern Buildings is an indispensable pocket-sized guide
to understanding the architecture of the modern era. It takes the
reader on a guided tour of modern architecture through its most
iconic and significant buildings, showing how to read the hallmarks
of each architectural style and how to recognise them in the
buildings all around. From Art Deco and Arts and Crafts, through
the International Style and Modernism to today's environmental
architecture and the rise and fall of the icon, all the major
architectural movements from the 1900s to the present day are
traced through their classic buildings. Examining the key
architectural elements and hidden details of each style, we learn
what to look out for and where to look for it. Packed with detailed
drawings, plans, and photographs, this is both a fascinating
architectural history and an effective I-spy guide, it is a
must-read for anyone with an interest in modern design and
architecture.
This volume wades into the fertile waters of Augustan Rome and the
interrelationship of its literature, monuments, and urban
landscape. It focused on a pair of questions: how can we
productively probe the myriad points of contact between textual and
material evidence to write viable cultural histories of the ancient
Greek and Roman worlds, and what are the limits of these kinds of
analysis? The studies gathered here range from monumental absences
to monumental texts, from canonical Roman authors such as Cicero,
Livy, and Ovid to iconic Roman monuments such as the Rostra,
Pantheon, and Solar Meridian of Augustus. Each chapter examines
what the texts in, on, and about the city tell us about how the
ancients thought about, interacted with, and responded to their
urban-monumental landscape. The result is a volume whose
methodological and heuristic techniques will be compelling and
useful for all scholars of the ancient Mediterranean world.
To provide structure and transparency to the complex world of
IT, Enterprise Architecture was created. However, we created
complexities within Enterprise Architecture with Frameworks that
are not easily understandable and purposefully implementable. In
this book, Nagesh and Gerry help to turnaround Enterprise
Architecture organizations. They introduce a simple IDEA Framework
that is based on common practices and investments within IT
organizations. The Ten deliverables presented in this book bring
structure and clarity to IT organizations that are 10-people IT
shops and 1000+ IT staff enterprises alike.
This book is not an ivory tower work, it is actionable, applied
Enterprise Architecture. It is also a healthy dose of EA tough
love. If you want to know why EA fails, read the second chapter. It
is introspective, it does not blame external forces: the
not-my-fault syndrome. It also does not blame, in fact it hardly
mentions, technology. To be fair, the Nagesh and Gerry do recognize
external influences; however they are viewed as risks that must be
managed.
Most corporations focus on this year s budget, investments, and
rewards. The same focus rolls downhill to the Information
Technology department. If the IT department has not successfully
communicated the budget and managed to spend it within the limits (
10% variance), everything else may seem irrelevant. Eventually,
Nagesh and Gerry started looking through current IT systems and IT
assets to understand: (a) where the current funds were being
invested, (b) how these investments jelled or were mandated because
of the previous investments that had been made by IT, and (c) how
the company s business priorities aligned with future technology
needs, including the need to meet compliance requirements.
Considering and discovering the answers to these three questions
led Nagesh and Gerry to develop a definition of Enterprise
Architecture that was based on technology investments Investment
Driven Enterprise Architecture (IDEA) Framework.
The purpose of the IDEA Framework is to provide guidance on how
the corporation s future technology will be drafted and
communicated. Its method is to utilize actual systems, hardware,
people, and business functions in order to establish boundaries
within which the IDEA Framework will work. The structure of the
IDEA Framework differs from that of many others because it consists
of key deliverables that fit into day-to-day activities and it
accommodates an enterprise-wide strategic plan. It also provides
for the much-needed interaction between these key deliverables and
facilitates contributions from key stakeholders across Business
Units and the various IT departments. In essence, the IDEA
Framework takes the key deliverables, stakeholders, and
organizations and demonstrates how they dynamically function
together.
|
|