This book is a bridge to confident academic writing for advanced non-native English users. It emphasizes depth over breadth through mastery of core writing competencies and strategies which apply to most academic disciplines and genres. Tailored to students in EMI programs, the content was piloted and revised during a longitudinal writing study. The innovative approach prepares students to write for the academic community through the dual lenses of Art (developing a writer’s voice through choices in language, style, and topics) and Architecture (mastering norms of academic language, genre, and organization.) The user-friendly text maximizes time for writing practice and production by avoiding lengthy readings. Part 1 builds skills and confidence in writing by focusing on assignments that do not require research. Part 2 applies newly mastered principles, skills, and strategies to research-based writing. Students learn to incorporate thesis, research, and evidence into a process for academic writing by following the AWARE framework (Arranging to write, Writing, Assessing, Revising, and Editing.)
Writing Architecture considers the process, methods, and value of architecture writing based on Wiseman’s 30 years of experience in writing, editing, and teaching young architects how to write. This book creatively tackles a problematic issue that Wiseman considers crucial to successful architecture writing: clarity of thinking and expression. He argues that because we live our lives within the built environment, architecture is the most comprehensive and complex of all art forms. Written as a primer for both college-level students and practitioners, Writing Architecture acknowledges and explores the boundaries between different techniques of architecture writing from myriad perspectives and purposes. Using excerpts from writers in different genres and from different historical periods, Wiseman offers a unique and authoritative perspective on the comprehensible writing skills needed for success.
Writing Program Architecture offers an unprecedented abundance of information concerning the significant material, logistical, and rhetorical features of writing programs. Presenting the realities of thirty diverse and award-winning programs, contributors to the volume describe reporting lines, funding sources, jurisdictions, curricula, and other critical programmatic matters and provide insight into their program histories, politics, and philosophies. Each chapter opens with a program snapshot that includes summary demographic and historical information and then addresses the profile of the WPA, program conception, population served, funding, assessment, technology, curriculum, and more. The architecture of the book itself makes comparison across programs and contexts easy, not only among the programs described in each chapter but also between the program in any given chapter and the reader’s own program. An online web companion to the book includes access to the primary documents that have been of major importance to the development or sustainability of the program, described in a “Primary Document” section of each chapter. The metaphor of architecture allows us to imagine the constituent parts of a writing program as its foundation, beams, posts, scaffolding—the institutional structures that, alongside its people, anchor a program to the ground and keep it standing. The most extensive resource on program structure available to the field, Writing Program Architecture illuminates structural choices made by leaders of exemplary programs around the United States and provides an authoritative source of standard practice that a WPA might use to articulate programmatic choices to higher administration. Contributors: Susan Naomi Bernstein, Remica Bingham-Risher, Brent Chappelow, Malkiel Choseed, Angela Clark-Oates, Patrick Clauss, Emily W. Cosgrove, Thomas Deans, Bridget Draxler, Leigh Ann Dunning, Greg A. Giberson, Maggie Griffin Taylor, Paula Harrington, Sandra Jamieson, Marshall Kitchens, Michael Knievel, Amy Lannin, Christopher LeCluyse, Sarah Liggett, Deborah Marrott, Mark McBeth, Tim McCormack, John McCormick, Heather McGrew, Heather McKay, Heidi A. McKee, Julianne Newmark, Lori Ostergaard, Joannah Portman-Daley, Jacqueline Preston, James P. Purdy, Ben Rafoth, Dara Regaignon, Nedra Reynolds, Shirley Rose, Bonnie Selting, Stacey Sheriff, Steve Simpson, Patricia Sullivan, Kathleen Tonry, Sanford Tweedie, Meg Van Baalen-Wood, Shevaun Watson, Christy I. Wenger, Lisa Wilkinson, Candace Zepeda
Drawings, doodles, and ideograms argue with ferocity and wit for traditional urbanism and architecture. Architect Léon Krier's doodles, drawings, and ideograms make arguments in images, without the circumlocutions of prose. Drawn with wit and grace, these clever sketches do not try to please or flatter the architectural establishment. Rather, they make an impassioned argument against what Krier sees as the unquestioned doctrines and unacknowledged absurdities of contemporary architecture. Thus he shows us a building bearing a suspicious resemblance to Norman Foster's famous London “gherkin” as an example of “priapus hubris” (threatened by detumescence and “priapus nemesis”); he charts “Random Uniformity” (“fake simplicity”) and “Uniform Randomness” (“fake complexity”); he draws bloated “bulimic” and disproportionately scrawny “anorexic” columns flanking a graceful “classical” one; and he compares “private virtue” (modernist architects' homes and offices) to “public vice” (modernist architects' “creations”). Krier wants these witty images to be tools for re-founding traditional urbanism and architecture. He argues for mixed-use cities, of “architectural speech” rather than “architectural stutter,” and pointedly plots the man-vehicle-landneed ratio of “sub-urban man” versus that of a city dweller. In an age of energy crisis, he writes (and his drawings show), we “build in the wrong places, in the wrong patterns, materials, densities, and heights, and for the wrong number of dwellers”; a return to traditional architectures and building and settlement techniques can be the means of ecological reconstruction. Each of Krier's provocative and entertaining images is worth more than a thousand words of theoretical abstraction.
This is a practical guide for software developers, and different than other software architecture books. Here's why: It teaches risk-driven architecting. There is no need for meticulous designs when risks are small, nor any excuse for sloppy designs when risks threaten your success. This book describes a way to do just enough architecture. It avoids the one-size-fits-all process tar pit with advice on how to tune your design effort based on the risks you face. It democratizes architecture. This book seeks to make architecture relevant to all software developers. Developers need to understand how to use constraints as guiderails that ensure desired outcomes, and how seemingly small changes can affect a system's properties. It cultivates declarative knowledge. There is a difference between being able to hit a ball and knowing why you are able to hit it, what psychologists refer to as procedural knowledge versus declarative knowledge. This book will make you more aware of what you have been doing and provide names for the concepts. It emphasizes the engineering. This book focuses on the technical parts of software development and what developers do to ensure the system works not job titles or processes. It shows you how to build models and analyze architectures so that you can make principled design tradeoffs. It describes the techniques software designers use to reason about medium to large sized problems and points out where you can learn specialized techniques in more detail. It provides practical advice. Software design decisions influence the architecture and vice versa. The approach in this book embraces drill-down/pop-up behavior by describing models that have various levels of abstraction, from architecture to data structure design.
Anyone writing real-time operating systems, multi-task operating systems, or device drivers for these systems needs to be able to do assembly language protected-mode programming. Protected Mode Software Architecture helps readers understand the problems that single-task and multitasking operating systems must deal with, and then examines each component of both the real and protected mode software architectures of the post-286 Intel processors.
API Design for C++ provides a comprehensive discussion of Application Programming Interface (API) development, from initial design through implementation, testing, documentation, release, versioning, maintenance, and deprecation. It is the only book that teaches the strategies of C++ API development, including interface design, versioning, scripting, and plug-in extensibility. Drawing from the author's experience on large scale, collaborative software projects, the text offers practical techniques of API design that produce robust code for the long term. It presents patterns and practices that provide real value to individual developers as well as organizations. API Design for C++ explores often overlooked issues, both technical and non-technical, contributing to successful design decisions that product high quality, robust, and long-lived APIs. It focuses on various API styles and patterns that will allow you to produce elegant and durable libraries. A discussion on testing strategies concentrates on automated API testing techniques rather than attempting to include end-user application testing techniques such as GUI testing, system testing, or manual testing. Each concept is illustrated with extensive C++ code examples, and fully functional examples and working source code for experimentation are available online. This book will be helpful to new programmers who understand the fundamentals of C++ and who want to advance their design skills, as well as to senior engineers and software architects seeking to gain new expertise to complement their existing talents. Three specific groups of readers are targeted: practicing software engineers and architects, technical managers, and students and educators. - The only book that teaches the strategies of C++ API development, including design, versioning, documentation, testing, scripting, and extensibility - Extensive code examples illustrate each concept, with fully functional examples and working source code for experimentation available online - Covers various API styles and patterns with a focus on practical and efficient designs for large-scale long-term projects
"This book addresses the topic of software design: how to decompose complex software systems into modules (such as classes and methods) that can be implemented relatively independently. The book first introduces the fundamental problem in software design, which is managing complexity. It then discusses philosophical issues about how to approach the software design process and it presents a collection of design principles to apply during software design. The book also introduces a set of red flags that identify design problems. You can apply the ideas in this book to minimize the complexity of large software systems, so that you can write software more quickly and cheaply."--Amazon.
A historical study of Vitruvius's De architectura, showing that his purpose in writing "the whole body of architecture" was shaped by the imperial Roman project of world domination. Vitruvius's De architectura is the only major work on architecture to survive from classical antiquity, and until the eighteenth century it was the text to which all other architectural treatises referred. While European classicists have focused on the factual truth of the text itself, English-speaking architects and architectural theorists have viewed it as a timeless source of valuable metaphors. Departing from both perspectives, Indra Kagis McEwen examines the work's meaning and significance in its own time. Vitruvius dedicated De architectura to his patron Augustus Caesar, the first Roman emperor, whose rise to power inspired its composition near the end of the first century B.C. McEwen argues that the imperial project of world dominion shaped Vitruvius's purpose in writing what he calls "the whole body of architecture." Specifically, Vitruvius's aim was to present his discipline as the means for making the emperor's body congruent with the imagined body of the world he would rule. Each of the book's four chapters treats a different Vitruvian "body." Chapter 1, "The Angelic Body," deals with the book as a book, in terms of contemporary events and thought, particularly Stoicism and Stoic theories of language. Chapter 2, "The Herculean Body," addresses the book's and its author's relation to Augustus, whose double Vitruvius means the architect to be. Chapter 3, "The Body Beautiful," discusses the relation of proportion and geometry to architectural beauty and the role of beauty in forging the new world order. Finally, Chapter 4, "The Body of the King," explores the nature and unprecedented extent of Augustan building programs. Included is an examination of the famous statue of Augustus from Prima Porta, sculpted soon after the appearance of De architectura.
Practical Software Architecture Solutions from the Legendary Robert C. Martin (“Uncle Bob”) By applying universal rules of software architecture, you can dramatically improve developer productivity throughout the life of any software system. Now, building upon the success of his best-selling books Clean Code and The Clean Coder, legendary software craftsman Robert C. Martin (“Uncle Bob”) reveals those rules and helps you apply them. Martin’s Clean Architecture doesn’t merely present options. Drawing on over a half-century of experience in software environments of every imaginable type, Martin tells you what choices to make and why they are critical to your success. As you’ve come to expect from Uncle Bob, this book is packed with direct, no-nonsense solutions for the real challenges you’ll face–the ones that will make or break your projects. Learn what software architects need to achieve–and core disciplines and practices for achieving it Master essential software design principles for addressing function, component separation, and data management See how programming paradigms impose discipline by restricting what developers can do Understand what’s critically important and what’s merely a “detail” Implement optimal, high-level structures for web, database, thick-client, console, and embedded applications Define appropriate boundaries and layers, and organize components and services See why designs and architectures go wrong, and how to prevent (or fix) these failures Clean Architecture is essential reading for every current or aspiring software architect, systems analyst, system designer, and software manager–and for every programmer who must execute someone else’s designs. Register your product for convenient access to downloads, updates, and/or corrections as they become available.
