Part I: The Law of Nations
Chapter 1: The Nature of International Law
Chapter 2: Development of Law Among Nations
Chapter 3: Sources of the Law
Part II: Subject of International Law
Chapter 4: The Relationship Between International and Municipal Law
Chapter 5: Subjects of International Law
Chapter 6: Recognition of States and Governments
Chapter 7: Rights and Duties of International Legal Persons
Chapter 8: State Succession
Part III: The Law and the Individual
Chapter 9: Nationality
Chapter 10: Jurisdiction: Allocation of Competence
Chapter 11: International Agreements
Chapter 12: State Responsibility: Responsibility for Injuries to Aliens
Part IV: Territorial Questions
Chapter 13: The Law of the Sea
Chapter 14: Jurisdiction Over Air Space and Outer Space
Part V: International Transactions
Chapter 15: Agents of International Intercourse: Immunities
Chapter 16: The Individual and International Law: Human Rights
Chapter 17: International Criminal Law
Chapter 18: Adjudication
Chapter 19: International Law and Protection of the Environment
Chapter 20: The Use of Force
Chapter 21: International Humanitarian Law: War Crimes
Chapter 22: War Crimes Tribunals
]]>
Susan J. Wolfson is professor of English at Princeton University. In addition to this present volume, her editorial work includes Felicia Hemans (Princeton UP, 2000) and the Longman Cultural Edition of John Keats. With Claudia Johnson, she is coeditor of the Longman Cultural Edition of Jane Austen's Pride and Prejudice. With Peter Manning, she is coeditor of the Romantics volume in The Longman Anthology of British Literature, and Selected Poems of Lord Byron (Penguin, 2005). Her critical books include the prize-winning Formal Charges: The Shaping of Poetry in British Romanticism (Stanford UP, 1997) and Borderlines: The Shiftings of Gender in British Romanticism (Stanford UP, 2007).
About Longman Cultural Editions.
About this Edition.
Introduction.
Table of Dates.
The text explores four specific themes throughout its chapters:
Practical Exercises present real world scenarios that motivate students to get involved in their local the political systems.
Questions for Review and Chapter Discussion Questions help students review the main ideas of each chapter.
New to this Edition:
Chapter 1: Introduction: The Struggle for Power and Influence
Importance of State and Local Politics
Learning About Local Politics and Government
Scope of the Book
The Struggle
Politics
PART II: INSTITUTIONS AND ELECTIONS
Chapter 2: Constitutions and Charters: The Foundations of State
The Beginnings of State and Local Governments in the United States
Constitutions and Charters–the Ballpark of Politics
State Constitutions
City (Municipal) Charters
Forms of Local Government
Chapter 3: Struggles in State Legislatures and City Councils
Serving in the City Council or the State Legislature
Struggling for Power and Influence in Legislative Bodies
Legislative Life
Who are the lawmakers
Lawmaking Roles
Organizing and Operating a Legislative Body
The Capacity to Legislate Effectively
Committees as the Fountain and Deathtrap of Legislation
Redistricting
Making your Bill a Law
Limits on Lawmakers
Making Decisions is Not Simple
Ethics in Legislative Decision Making — The “Queasiness” Test
“How’re We Doin’?” in our Legislative Bodies
Chapter 4: Executive Power in State and Local Government
State and Local Chief Executives Struggle for Power
Powers of Governors and Mayors as Chief Executives
The Various Roles of Chief Executives
History of State and Local Executive Power
The State Executive Branch
Executive Officials in City and County Government
Running a Bureaucracy
Conclusion
Chapter 5: Election Battles
Getting Elected
Nowlan and Simpson Campaigns
Deciding to Run
Launching a Candidacy
Developing a Campaign Strategy
A Candidate’s Image
A Campaign’s Message
Winning Elections
Chapter 6: Justice and Corrections
Structure
People in the Criminal Justice System
Processes of the Criminal Justice System
Outcomes of the Justice System
Civil Cases
Chapter 7: Federalism: Playing Tug of War
Historical Background of Federalism
State and Local Governmental Connections with the Federal Judicial Branch
State and Local Governmental Connections with the Federal Legislative Branch
State and Local Governmental Connections with the Federal Executive Branch
Interplay between Congress, State and Local Government, and Federal Agencies
The Tug of War among States — Horizontal Federalism
Interplay between States and Local Governments
States and Cities Today: Stronger in the Tug of War?
Intergovernmental Relations: A Summary
PART III: POLITICAL PARTICIPATION
Chapter 8: Participation in State and Local Government
Paid Lobbyists
Lobbying in the Legislative Process
Journalists’ and the Media’s Role as Community Watchdogs
Blogs
Citizen Activists
Community Organizations
Roles Citizens Can Play
PART IV: POLICIES AND PROBLEMS
Ch. 9: Follow the Money — The Politics of State and Local Budgeting
Budgets as Allocations of Our Values and Demands or Needs
Enormous Pressure to Spend
Finding the Revenue Always a Struggle
The Big Three Taxes: Sales, Income, Property
Should We Tax Sales on the Internet?
Evaluating Revenue Sources: The Old Regressive-Progressive Debate
Budgeting Process Is Simple, But Decisions Are Difficult
The Office of Management and Budget
Capital Borrowing and Spending
The Politics of “Shift and Shaft"
Political Dynamics of Budgeting
Budget Trends
Chapter 10. Metropolitanization and Globalization
Governing the Metropolitan Region
Urban Sprawl
Gated Communities
Globalization
Problems of Metropolitanization and Globalization
Our Neighbors: Canada and Mexico
Getting Along with Our Neighbors
Conclusion
Chapter 11: The Struggle for the Schoolhouse and Campus
The Historical Development of American Public Education
Public School Education — From Kindergarten through High School
The Federal Role in Education
Who Pays for Public Education?
Non-public School Education
The Campuses Struggle to Maintain Independence
PART V: DEMOCRACY AND ETHICS
Chapter 12: Democracy and Ethics at the Grassroots
Representative Democracy
Metropolitanization and Globalization
Ethics in Politics
Practical Exercises
Chapter Notes
]]>Writing for the Health Professions looks at a wide range of health professionals¿ writing needs, including visual and electronic forms of communication, necessary in today¿s high-tech medical and health writing situations. The text addresses writing situations found in hospitals, clinics, HMOs, health insurance companies, and other health specialties. Covers a variety of genres including charting, patient histories, progress notes, procedural reports, handbooks, newsletters, brochures, websites, proposals, grant writing, and more.
Those interested in learning the basics of medical and health communication.
]]>II. GENRES IN THE HEALTH PROFESSIONS.
III. MEDIA AND CULTURES.
IV. APPENDICES.
Uses analytical and critical reading techniques to show readers the types of writing required in different fields of study and professions (see writing activities in Part 1; classical rhetorical techniques in Part 2). Readings focus on a broad range of issues that readers care about like: finding meaningful work; affirmative action; family-friendly workplaces (see table of contents). Reading and Writing activities help readers find, evaluate, and synthesize research materials. Provides time-tested rhetorical techniques to help readers organize their ideas into coherent arrangement patterns and then builds on them with the writing styles of specific disciplines and professions (Ch 4).
Anyone interested in exploring their future career or changing careers.
]]>I. WRITING TO INQUIRE.
II. READING AND WRITING IN ACADEMIC AND PROFESSIONAL COMMUNITIES.
III. THE PROCESS OF RESEARCH.
IV. CASEBOOKS FOR FURTHER READING AND RESEARCH.
A unique chapter (Ch.4) on the media shows how Web sites, web logs, and blogging can be used in developing an autobiography, in understanding autobiography as a genre, and in demonstrating the connection of the autobiography to history and culture. Journaling is a central feature of the book, both as an end in itself and as a means of invention in life narratives. Unique Timeline assignments help readers understand how the personal and social are connected.
]]>
Helps readers to identify the knowledge they already possess and use that metacognition as a basis for encountering new texts and new interpretive challenges. Makes extensive use of student writing, in each chapter, engaging readers in the careful consideration of other students¿ writing. Offers practical tools to help readers interpret difficult texts—the “difficulty” paper; the triple-entry notebook; and reflective questioning. Covers a wide range of genres and types of texts ¿ poetry, narrative, drama, essay, and hybrid genres.
Anyone interested in learning to understand more difficult texts.
]]>
PART II.
PART III.
Handsomely produced and affordably priced, the Longman Cultural Editions series presents classic works in provocative and illuminating contexts—cultural, critical, and literary. Each Cultural Edition consists of the complete text of an important literary work, reliably edited, headed by an inviting introduction, and supplemented by helpful annotations; a table of dates to track its composition, publication, and public reception in relation to biographical, cultural, and historical events; and a guide for further inquiry and study.
]]>
Jeff Nunokawa specializes in English literature from about 1830 till about 1900 at Princeton University. His first book, The Afterlife of Property, studies how the novels of Dickens and Eliot labor to preserve the idea of secure possession by overseeing its transfer from the sphere of a cold and uncertain economy to a happier realm of romance. Tame Passions of Wilde: Styles of Manageable Desire excavates the aspiration to imagine a form of desire as intense as those that compel us, but as light as the daydream or thought experiment safely under our control. His current project is a book whose working title is "Eros and Isolation: Getting Away from Others in Nineteenth Century Literature." This book brings a range of social theory to bear on writers like Austen, C. Brontë, Thackeray, Dickens and Eliot to figure out why it’s so hard to break free, even for a little while, from the groups that surround and define us. Most generally, he is interested in the ways that various ideas of society clash and collaborate with one another. Before his day is done, he hopes to write a book about Henry James.
]]>
Handsomely produced and affordably priced, the Longman Cultural Editions series presents classic works in provocative and illuminating contexts—cultural, critical, and literary. Each Cultural Edition consists of the complete text of an important literary work, reliably edited, headed by an inviting introduction, and supplemented by helpful annotations; a table of dates to track its composition, publication, and public reception in relation to biographical, cultural, and historical events; and a guide for further inquiry and study.
]]>CONTEXTS
Handsomely produced and affordably priced, the Longman Cultural Editions series presents classic works in provocative and illuminating contexts–cultural, critical, and literary. Each Cultural Edition consists of the complete text of an important literary work, reliably edited, headed by an inviting introduction, and supplemented by helpful annotations; a table of dates to track its composition, publication, and public reception in relation to biographical, cultural, and historical events; and a guide for further inquiry and study.
]]>
About Longman Cultural Editions ix
About This Edition xi
Introduction xiv
Table of Dates xxii
King Lear 1
The Texts of King Lear 134
Contexts 139
Shakespeare’s Narrative and Dramatic Sources 141
RAPHAEL HOLINSHED, from “The Second Booke of the Historie of England” in The First and Second Volumes of Chronicles (1587) 144
From The True Chronicle History of King Leir and his three daughters . . . As it hath beene divers and sundry times lately acted (1605) 147
SIR PHILIP SIDNEY, from The Countesse of Pembrokes Arcadia (1590) 154
The State 158
From An Exhortation Concerning Good Order and Obedience to Rulers and Magistrates (1570) 160
CHARLES MERBURY, from A Brief Discourse of Royal Monarchie, as of the Best Common Weale (1581) 162
SIR THOMAS SMITH, from De Republica Anglorum (1583) 163
JAMES VI OF SCOTLAND, from The Trew Law of Free Monarchies (1599) 164
JAMES I OF ENGLAND, from A Speech [. . .] delivered in the Upper House of Parliament on Monday the 19 March 1604, being the first day of the First Parliament 167
THOMAS SACKVILLE AND THOMAS NORTON, from Gorbuduc (1562) 169
SAMUEL HARSNETT, from A Declaration of Egregious Popish Impostures (1603) 173
The Household 176
MICHEL DE MONTAIGNE, from “Of the Affection of Fathers for Their Children” from The Essays (London, 1603) 179
WILLIAM GOUGE, from Of Domesticall Duties (1622) 184
JOSEPH SWETNAM, from The Arraignment of Lewde, Idle, Forward, and Unconstant Women (1615) 191
JANE ANGER, from Her Protection for Women (1589) 193
Fools and Folly 194
ERASMUS, from A Letter to Martin Dorp (1515) 195
ROBERT ARMIN, from Foole upon Foole (1600) 196
“Good” and “Evil” 200
WILLIAM HARRISON, from “Of the Ancient Religion Used in Albion” (1587) 201 JEAN CALVIN, from Institutes of the Christian Religion (1536) 205 RICHARD HOOKER, from Of the Laws of Ecclesiastical Polity (1593) 209 THOMAS HOBBES, from Leviathan (1651) 215 ST. AUGUSTINE, from The City of God, Book XIX (c. 413—427) 218
Early Readings and Rewritings 220
NAHUM TATE, from The History of King Lear (1681) 222
LEWIS THEOBALD, from The Censor (1715) 230
SAMUEL JOHNSON, from “Notes on King Lear” in The Plays of William Shakespeare (London, 1765) 233
GEORGE COLMAN, from the Preface to The History of King Lear (1768) 236
CHARLES LAMB, from “On the Tragedies of Shakespeare, considered with reference to their fitness for stage representation” (1810) 238
CHARLES LAMB, from “King Lear” in Tales from Shakespeare (1807) 241
WILLIAM HAZLITT, from The Characters of Shakespear’sPlays (1818) 247
SAMUEL TAYLOR COLERIDGE, from Lectures on Shakespeare (1818) 251
JOHN KEATS, “On Sitting Down to Read King Lear Once Again” (1818) 254
A. C. BRADLEY, from Shakespearean Tragedy: Lectures on Hamlet, Othello, King Lear and Macbeth (1904) 255
Adaptations of King Lear 259
Further Reading 261
]]>
I. GETTING STARTED: FROM RESPONSE TO ARGUMENT.
II. UP CLOSE: THINKING CRITICALLY ABOUT LITERARY WORKS AND LITERARY FORMS.
III. STANDING BACK: ARGUING INTERPRETATIONS AND EVALUATIONS, AND UNDERSTANDING CRITICAL STRATEGIES.
Written by historians with years of experience teaching world history, Connections presents both a global and regional perspective, so students can appreciate both the diversity and connectedness of human societies. Concise chapters and a clear engaging narrative make the text accessible to a wide range of students. Because students struggle with geography, the book includes significantly more maps than other texts–in most cases twice as many–and great care was taken to make them consistent and exceptionally clear. In each caption, the authors have provided guidance for reading the map and for connecting it to the surrounding text. To further help students succeed, marginal notes highlight major connections for easy review, and pronunciation guides appear after difficult names. Compelling vignettes introduce the themes of each chapter, concise excerpts from relevant primary sources allow students to hear the voices of the past, and an extensive chapter review section is designed to help students test themselves and succeed in this difficult course.
]]>Chapter 2 Early Societies of West Asia and North Africa, to 500 B.C.E.
Chapter 3 Societies and Beliefs of Early India, to 300 C.E.
Chapter 4 The Origins of the Chinese Empire, to 220 C.E.
Chapter 5 Early American Societies: Connection and Isolation, 20,000 B.C.E.-1500 C.E.
Chapter 6 The Persian Connection: Its Impact and Influences, 2000 B-C.E-637 C.E.
Chapter 7 Classical Greece and Its Conflict with Asia, 2000-30 B.C.E.
Chapter 8 The Romans Connect the Mediterranean World, 753 B.C.E-284 C.E.
Chapter 9 Germanic Societies and the Emergence of the Christian West, 100-1100 C.E.
Chapter 10 The Byzantine World, 284-1240
Chapter 11 Origins and Expansion of Islam, 100-750
Chapter 12 Religion and Diversity in the Transformation of Southern Asia, 711-1400
Chapter 13 African Societies and the Impact of Islam, 1500 B.C.E — 1500 C.E.
Chapter 14 The Evolution and Expansion of East Asian Societies, 220-1240 C.E.
Chapter 15 Nomadic Conquests and Eurasian Connections, 100-1400
Chapter 16 The Resurgence of the Christian West 1050-1530
Chapter 17 Culture and Conflict in the Great Islamic Empires, 1071-1707
Chapter 18 The Aztec and Inca Empires, 1300-1550
Chapter 19 Global Exploration and Global Empires, 1400-1700
Chapter 20 The West in an Age of Religious Conflict and Global Expansion, 1500-1650
Chapter 21 The Search for Stability in East Asia, 1300-1800
Chapter 22 Southern Asia and the Global Shift in Wealth and Power, 1500-1800
Chapter 23 Africa and the Atlantic Slave Trade, 1400-1800
Chapter 24 Absolutism and Enlightenment in Europe, 1600-1763
Chapter 25 Russia’s Eurasian Empire: Convergence of East and West, 1300-1800
Chapter 26 The Atlantic Revolutions, 1750-1830
Chapter 27 Industry, Ideology, and their Global Impact, 1700-1914
Chapter 28 Nation-Building in North and South America, 1789-1914
Chapter 29 Confrontation and Adaptation in Eastern and Southern Asia, 1770-1914
Chapter 30 The Transformation of West Asia and Africa, 1800-1914
Chapter 31 The Great War and the Russian Revolutions, 1890-1918
Chapter 32 Anxieties and Ideologies of the Interwar Years, 1918-1939
Chapter 33 World War II and the Holocaust, 1933-1945
Chapter 34 East Versus West: Cold War and It’s Global Impact, 1945-Present
Chapter 35 The Upheavals of Asia, 1945-Present
Chapter 36 Reform and Revolution in Latin America, 1914-2008
Chapter 37 Post-Colonial Challenges in Africa and the Middle East, 1939-Present
Glossary
]]>
--Connie Brand, Meridian Community College
“This text very carefully demonstrates the complex interactions between civilizations while emphasizing the strengths, weaknesses, and challenges of individual civilizations. I’ve never encountered a text that blends these two themes more effectively.”
~ Robert McCormick, University of South Carolina, Spartanburg
“One great strength of showing connections is that it helps make history come alive for students.”
~ David John Marley, Vanguard University
“I thought the connections were very well done. It was easy to read and contain all of the relevant information without being dull. The maps were very helpful as were the important facts off to the side.”
~ Tracey Provost, Middle Georgia College
“The text covers well the interaction of civilizations and gives the students the sense that events and civilizations do not exist in a vacuum. This is precisely the approach that I use in my classes.”
~ Gregort Havrilcsak, University of Michigan, Flint
“I found the broader connections presented here to be accurate, easily accessible, and meaningful for students. This is one of the strong points of the text.”
~ Anthony Gulig, University of Wisconsin, Whitewater"
The progression of maps within each chapter is incredibly well thought out and integrated. The maps are beautiful and carefully done, and the number of maps included in each chapter is far more than in a typical world history textbook."
---Linda Bregstein Scherr, Mercer County Community College
“The maps are vivid. The show connections, trace routes in a direct contextual line with the text. They serve as an ancillary for the text, not as a distraction.”
~ John H. Frederick, South Louisiana Community College
“I think this book would be effective with a range of my students, because of its clear writing and nice narrative flow.”
~ Jonathan Ablard, Ithaca College
“The best part of the book is how well it flows. Sometimes I feel like I am reading a story book rather than a textbook, but I am still learning history…I think the end-of-chapter material puts everything into perspective. It basically sums some lose ends up that completes your knowledge of history.”
~ Katrina Slaski, student at Le Moyne College
“I like that the history textbook has many maps and very specific information on all topics. This textbook is easier to follow [than other textbooks]. I like that maps are easy to read and contain details on the side.”
~ Lejor Custic, student at Le Moyne College
]]>
Written by historians with years of experience teaching world history, Connections presents both a global and regional perspective, so students can appreciate both the diversity and connectedness of human societies. Concise chapters and a clear engaging narrative make the text accessible to a wide range of students. Because students struggle with geography, the book includes significantly more maps than other texts—in most cases twice as many—and great care was taken to make them consistent and exceptionally clear. In each caption, the authors have provided guidance for reading the map and for connecting it to the surrounding text. To further help students succeed, marginal notes highlight major connections for easy review, and pronunciation guides appear after difficult names. Compelling vignettes introduce the themes of each chapter, concise excerpts from relevant primary sources allow students to hear the voices of the past, and an extensive chapter review section is designed to help students test themselves and succeed in this difficult course.
]]>Chapter 2 Early Societies of West Asia and North Africa, to 500 B.C.E.
Chapter 3 Societies and Beliefs of Early India, to 300 C.E.
Chapter 4 The Origins of the Chinese Empire, to 220 C.E.
Chapter 5 Early American Societies: Connection and Isolation, 20,000 B.C.E.-1500 C.E.
Chapter 6 The Persian Connection: Its Impact and Influences, 2000 B-C.E-637 C.E.
Chapter 7 Classical Greece and Its Conflict with Asia, 2000-30 B.C.E.
Chapter 8 The Romans Connect the Mediterranean World, 753 B.C.E-284 C.E.
Chapter 9 Germanic Societies and the Emergence of the Christian West, 100-1100 C.E.
Chapter 10 The Byzantine World, 284-1240
Chapter 11 Origins and Expansion of Islam, 100-750
Chapter 12 Religion and Diversity in the Transformation of Southern Asia, 711-1400
Chapter 13 African Societies and the Impact of Islam, 1500 B.C.E — 1500 C.E.
Chapter 14 The Evolution and Expansion of East Asian Societies, 220-1240 C.E.
Chapter 15 Nomadic Conquests and Eurasian Connections, 100-1400
Chapter 16 The Resurgence of the Christian West 1050-1530
Chapter 17 Culture and Conflict in the Great Islamic Empires, 1071-1707
Chapter 18 The Aztec and Inca Empires, 1300-1550
Chapter 19 Global Exploration and Global Empires, 1400-1700
Chapter 20 The West in an Age of Religious Conflict and Global Expansion, 1500-1650
Glossary
]]>
~ Connie Brand, Meridian Community College
“This text very carefully demonstrates the complex interactions between civilizations while emphasizing the strengths, weaknesses, and challenges of individual civilizations. I’ve never encountered a text that blends these two themes more effectively.”
~ Robert McCormick, University of South Carolina, Spartanburg
“One great strength of showing connections is that it helps make history come alive for students.”
~ David John Marley, Vanguard University
“I thought the connections were very well done. It was easy to read and contain all of the relevant information without being dull. The maps were very helpful as were the important facts off to the side.”
~ Tracey Provost, Middle Georgia College
“The text covers well the interaction of civilizations and gives the students the sense that events and civilizations do not exist in a vacuum. This is precisely the approach that I use in my classes.”
~ Gregort Havrilcsak, University of Michigan, Flint
“I found the broader connections presented here to be accurate, easily accessible, and meaningful for students. This is one of the strong points of the text.”
~ Anthony Gulig, University of Wisconsin, Whitewater"
The progression of maps within each chapter is incredibly well thought out and integrated. The maps are beautiful and carefully done, and the number of maps included in each chapter is far more than in a typical world history textbook."
---Linda Bregstein Scherr, Mercer County Community College
“The maps are vivid. The show connections, trace routes in a direct contextual line with the text. They serve as an ancillary for the text, not as a distraction.”
~ John H. Frederick, South Louisiana Community College
“I think this book would be effective with a range of my students, because of its clear writing and nice narrative flow.”
~ Jonathan Ablard, Ithaca College
“The best part of the book is how well it flows. Sometimes I feel like I am reading a story book rather than a textbook, but I am still learning history…I think the end-of-chapter material puts everything into perspective. It basically sums some lose ends up that completes your knowledge of history.”
~ Katrina Slaski, student at Le Moyne College
“I like that the history textbook has many maps and very specific information on all topics. This textbook is easier to follow [than other textbooks]. I like that maps are easy to read and contain details on the side.”
~ Lejor Custic, student at Le Moyne College
]]>
Written by historians with years of experience teaching world history, Connections presents both a global and regional perspective, so students can appreciate both the diversity and connectedness of human societies. Concise chapters and a clear engaging narrative make the text accessible to a wide range of students. Because students struggle with geography, the book includes significantly more maps than other texts—in most cases twice as many—and great care was taken to make them consistent and exceptionally clear. In each caption, the authors have provided guidance for reading the map and for connecting it to the surrounding text. To further help students succeed, marginal notes highlight major connections for easy review, and pronunciation guides appear after difficult names. Compelling vignettes introduce the themes of each chapter, concise excerpts from relevant primary sources allow students to hear the voices of the past, and an extensive chapter review section is designed to help students test themselves and succeed in this difficult course.
]]>Chapter 20 The West in an Age of Religious Conflict and Global Expansion, 1500-1650
Chapter 21 The Search for Stability in East Asia, 1300-1800
Chapter 22 Southern Asia and the Global Shift in Wealth and Power, 1500-1800
Chapter 23 Africa and the Atlantic Slave Trade, 1400-1800
Chapter 24 Absolutism and Enlightenment in Europe, 1600-1763
Chapter 25 Russia’s Eurasian Empire: Convergence of East and West, 1300-1800
Chapter 26 The Atlantic Revolutions, 1750-1830
Chapter 27 Industry, Ideology, and their Global Impact, 1700-1914
Chapter 28 Nation-Building in North and South America, 1789-1914
Chapter 29 Confrontation and Adaptation in Eastern and Southern Asia, 1770-1914
Chapter 30 The Transformation of West Asia and Africa, 1800-1914
Chapter 31 The Great War and the Russian Revolutions, 1890-1918
Chapter 32 Anxieties and Ideologies of the Interwar Years, 1918-1939
Chapter 33 World War II and the Holocaust, 1933-1945
Chapter 34 East Versus West: Cold War and It’s Global Impact, 1945-Present
Chapter 35 The Upheavals of Asia, 1945-Present
Chapter 36 Reform and Revolution in Latin America, 1914-2008
Chapter 37 Post-Colonial Challenges in Africa and the Middle East, 1939-Present
Glossary
]]>
--Connie Brand, Meridian Community College
“This text very carefully demonstrates the complex interactions between civilizations while emphasizing the strengths, weaknesses, and challenges of individual civilizations. I’ve never encountered a text that blends these two themes more effectively.”
~ Robert McCormick, University of South Carolina, Spartanburg
“One great strength of showing connections is that it helps make history come alive for students.”
~ David John Marley, Vanguard University
“I thought the connections were very well done. It was easy to read and contain all of the relevant information without being dull. The maps were very helpful as were the important facts off to the side.”
~ Tracey Provost, Middle Georgia College
“The text covers well the interaction of civilizations and gives the students the sense that events and civilizations do not exist in a vacuum. This is precisely the approach that I use in my classes.”
~ Gregort Havrilcsak, University of Michigan, Flint
“I found the broader connections presented here to be accurate, easily accessible, and meaningful for students. This is one of the strong points of the text.”
~ Anthony Gulig, University of Wisconsin, Whitewater"
The progression of maps within each chapter is incredibly well thought out and integrated. The maps are beautiful and carefully done, and the number of maps included in each chapter is far more than in a typical world history textbook."
---Linda Bregstein Scherr, Mercer County Community College
“The maps are vivid. The show connections, trace routes in a direct contextual line with the text. They serve as an ancillary for the text, not as a distraction.”
~ John H. Frederick, South Louisiana Community College
“I think this book would be effective with a range of my students, because of its clear writing and nice narrative flow.”
~ Jonathan Ablard, Ithaca College
“The best part of the book is how well it flows. Sometimes I feel like I am reading a story book rather than a textbook, but I am still learning history…I think the end-of-chapter material puts everything into perspective. It basically sums some lose ends up that completes your knowledge of history.”
~ Katrina Slaski, student at Le Moyne College
“I like that the history textbook has many maps and very specific information on all topics. This textbook is easier to follow [than other textbooks]. I like that maps are easy to read and contain details on the side.”
~ Lejor Custic, student at Le Moyne College
]]>
Philip Romanik is an independent consultant who has been designing and implementing real-world software applications for the past twenty years. He is an expert in the development of real-time, embedded software for performance-intensive applications. He has created patentable technology for his clients and has provided services to such leading companies as Eastman Kodak and Microsoft.
Amy Muntz is an independent consultant who holds advanced technical and business degrees, and writes from broad experience in both fields. She specializes in the development and management of aggressive software projects, successfully helping her clients over the past fifteen years build and market products that meet their business objectives.
"I really like the software engineering advice given here. As the chief engineer/architect for a large development group, I can say with certainty that the advice given in this book about how real-world projects must work is right on the mark."
--Steve Vinoski, coauthor of Advanced CORBA Programming with C++, columnist for C/C++ Users Journal and IEEE Internet Computing, and Chief Architect, IONA Technologies
Applied C++ is a practical, straightforward guide to developing high-quality, maintainable software. It reflects the power of C++, templates, and the Standard Template Library for industrial-strength programming. Whether you are a single developer or work in a large team, the tips and techniques presented in this book will help you improve your language and design skills and show you how to solve substantial problems more effectively.
The authors, drawing on their extensive professional experience, teach largely by example. To illustrate software techniques useful for any application, they develop a toolkit to solve the complex problem of digital image manipulation. By using a concrete, real-world problem and describing exact feature, performance, and extensibility requirements, the authors show you how to leverage existing software components and the tools inherent in C++ to speed development, promote reuse, and deliver successful software products.
Inside Applied C++, you will find:
Commercial software is delivered to customers (internal or external) who will rely on the interface you provide. It may be in an embedded system, or it may be a software library or application for standard platforms. No matter where it ultimately runs, the software must be released at a particular time with all of the features it needs to be successful in the market. It is software that is built by one group of engineers and potentially extended and maintained by other engineers. The engineers who take over maintaining the software may not have been part of the original team, and they might have to add features or try to fix problems while visiting customer sites.
Getting a group of engineers to build a complex piece of software and deliver it on time with full functionality is one of software engineering's biggest challenges. An even bigger challenge is building that same software in such a way that it can be handed off to others to extend and maintain. The C++ techniques and practical tips we have compiled into this book have been used repeatedly to accomplish just this. In many cases, we draw a distinction between the ideal solution and the practical one. We try to provide discussions of the trade-offs so that you can make informed decisions, and we tell you what our criteria are when selecting one method over another. We leave it to you to determine what works best in your application. Our goal is to share practical techniques that we have found made our commercial software efforts much more successful than they otherwise would have been. We hope you will find them useful.
For those of you who prefer to learn by looking at the code, you will find plenty of examples. We illustrate all of the techniques by using a concrete example that runs throughout the book. Because it was our experiences with imaging software that prompted us to write this book, our example comes from the image processing domain, but the C++ techniques are applicable to any domain. We start with a simple, although inadequate, application that generates thumbnail images. We use this application in our prototyping phases to experiment with different C++ design and implementation techniques. The application is simple to understand and the results of applying various C++ techniques are immediately obvious, making it a nice candidate for prototyping. This simple thumbnail image generator has many of the same inherent problems that our final image framework will have to address. The application is:
The complete source code for the thumbnail generator application, the prototypes, and the final image framework can be found on the included CD-ROM. Any updates to the software can be found at the web site: http://www.appliedcpp.com.
We expect you to be familiar with C++ so that when we apply various constructs from the language, you have seen or used them before. We also assume that you have built applications either for personal or commercial use and are familiar with what the Standard Template Library (STL) can provide. We hope to engage you in detailed discussions of the advantages and disadvantages of certain C++ constructs. Finally, we hope you really like to look at actual code examples, because the book is filled with them.
We do not attempt to provide a reference for the C++ language, but we do provide primers and reviews of those topics that have exacting syntax or are not used as frequently. For the basics of the C++ language, we refer you to The C++ Programming Language, Special Edition Stroustrup00. For in-depth discussions on certain C++ constructs, such as reference counting, we refer you to Effective C++, Second Edition Meyers98. For information on the Standard Template Library, we refer you to Effective STL Meyers01. For information on using C++ templates, we refer you to C++ Templates Vandevoorde03.
As for our chosen domain of digital imaging, we don't expect you to have any experience with writing software that manipulates images. We provide some basic information about imaging that you can review; if you are familiar with imaging, you can skip that section. Whenever we talk about a particular operation that we apply to an image, we take the time to give a simple explanation, as well as some before and after pictures, before proceeding to the code example. If you want an in-depth, mathematical discussion of image processing operations, we refer you to Digital Image Processing Pratt01.
The book is intended to be read sequentially, since there is a concrete example introduced in Chapter 2 and used to evolve the final design of the image framework that is presented in Chapter 5. Throughout the book, we highlight the C++ techniques we are exploring in heading titles and in summary boxes that appear on the first page of each chapter.
The book is organized as follows:
Chapter 1, Introduction, provides an overview of what we set out to accomplish by writing this book, and reveals our background and biases as they apply to the C++ techniques we recommend. We also provide an optional background section on digital imaging. If you have experience working with imaging applications, you may want to skip the final section of this chapter.
Chapter 2, A Test Application, introduces our simple, inadequate application, used as a test bed for prototyping C++ techniques. We deliberately create this strikingly simple application because it effectively demonstrates the trade-offs of various design and implementation decisions.
Chapter 3, Design Techniques, begins our discussion of C++ design. We use lots of code examples to demonstrate design strategies, and we provide a primer on templates since they are used so heavily within the book. Finally, we prototype various aspects of the design and build general utilities needed to support the design.
Chapter 4, Design Considerations, explores guidelines and additional strategies you may want to use in your designs. We offer a practical set of coding guidelines, reusability strategies, and a simple but effective debugging strategy.
Chapter 5, System Considerations, explores system-level design issues, like multi-threaded and multi-process designs, exception handling (including a framework we provide for handling exceptions), compile time and run-time issues, template specialization, and internationalization concerns.
Chapter 6, Implementation Considerations, applies the C++ techniques we have explored to the final design and implementation of all pieces in the image framework. In addition, this chapter introduces global image processing functions, like edge sharpening and noise reduction, and provides both a visual overview of these techniques and the C++ implementations. We also provide a high-level interface to libraries and other third-party software. Specifically, we introduce you to the Intel Integrated Performance Primitives (IPP) library and show you how to use IPP for high-speed imaging applications.
Chapter 7, Testing and Performance, provides a reasonable strategy for integrating unit tests into your software development cycle, including a full unit test framework and a discussion of how you can extend it to meet your particular needs. We also focus on performance, giving specific techniques that you can use to immediately improve the run-time performance of your application.
Chapter 8, Advanced Topics, explores those issues that we felt warranted more detailed discussion, such as copy on write, caching, explicit keyword usage, const, and pass by reference. We also include a section on extending the image framework, to serve as a guide for taking the existing framework and adding your own processing functions. We've highlighted some routines that work particularly well for enhancing your digital photographs.
Appendix A, Useful Online Resources, provides links to those software tools and resources that we thought might be helpful.
Appendix B, CD-ROM Information, outlines the contents of the CD-ROM included with this book. There is a great deal of code presented in this book. All of the source code for our test application, prototypes, and image framework is included on the disc. In addition, we provide all of the unit tests, unit test framework, and makefiles necessary to run the software on a variety of platforms. We also include some useful third-party software: the freeware DebugView utility by SysInternals for Microsoft Windows, the evaluation version of the Intel Integrated Performance Primitives (IPP) library for Microsoft Windows and Linux, the evaluation version of the Intel C++ Compiler for Microsoft Windows, the source code to build the JPEG file delegate, and the source code to build the TIFF file delegate.
Philip Romanik, 2003
Amy Muntz, 2003
"One of the great byproducts of Lance's work with honeypots and honeynets is that he's helped give us a much clearer picture of the hacker in action."
--From the Foreword by Marcus J. Ranum
"From the basics of shrink-wrapped honeypots that catch script kiddies to the detailed architectures of next-generation honeynets for trapping more sophisticated bad guys, this book covers it all....This book really delivers new information and insight about one of the most compelling information security technologies today."
--Ed Skoudis, author of Counter Hack, SANS instructor, and Vice President of Security Strategy for Predictive Systems
Honeypots are unique technological systems specifically designed to be probed, attacked, or compromised by an online attacker. Implementing a honeypot provides you with an unprecedented ability to take the offensive against hackers. Whether used as simple "burglar alarms," incident response systems, or tools for gathering information about hacker motives and tactics, honeypots can add serious firepower to your security arsenal.
Honeypots: Tracking Hackers is the ultimate guide to this rapidly growing, cutting-edge technology. The book starts with a basic examination of honeypots and the different roles they can play, and then moves on to in-depth explorations of six specific kinds of real-world honeypots: BackOfficer Friendly, Specter™, Honeyd, Homemade honeypots, ManTrap®, and Honeynets.
Honeypots also includes a chapter dedicated to legal issues surrounding honeypot use. Written with the guidance of three legal experts, this section explores issues of privacy, entrapment, and liability. The book also provides an overview of the Fourth Amendment, the Electronic Communications Privacy Act, the Wiretap Act, and the Pen/Trap Statute, with an emphasis on how each applies to honeypots.
With this book you will gain an understanding of honeypot concepts and architecture, as well as the skills to deploy the best honeypot solutions for your environment. You will arm yourself with the expertise needed to track attackers and learn about them on your own. Security professionals, researchers, law enforcement agents, and members of the intelligence and military communities will find this book indispensable.
Welcome to the exciting world of honeypots, where we turn the tables on the bad guys. Most of the security books you read today cover a variety of concepts and technologies, but almost all of them are about keeping blackhats out. This book is different: It is about keeping the bad guys in--about building computers you want to be hacked. Traditionally, security has been purely defensive. There has been little an organization could do to take the initiative and challenge the bad guys. Honeypots change the rules. They are a technology that allows organizations to take the offensive.
Honeypots come in a variety of shapes and sizes--everything from a simple Windows system emulating a few services to an entire network of productions systems waiting to be hacked. Honeypots also have a variety of values--everything from a burglar alarm that detects an intruder to a research tool that can be used to study the motives of the blackhat community. Honeypots are unique in that they are not a single tool that solves a specific problem. Instead, they are a highly flexible technology that can fulfill a variety of different roles. It is up to you how you want to use and deploy these technologies.
In this book, we explain what a honeypot is, how it works, and the different values this unique technology can have. We then go into detail on six different honeypot technologies. We explain one step at a time how these honeypot solutions work, discuss their advantages and disadvantages, and show you what a real attack looks like to each honeypot. Finally, we cover deployment and maintenance issues of honeypots. The goal of this book is not to just give you an understanding of honeypot concepts and architecture but to provide you with the skills and experience to deploy the best honeypot solutions for your environment. The examples in the book are based on real-world experiences, and almost all of the attacks discussed actually happened. You will see the blackhat community at their best, and some of them at their worst. Best of all, you will arm yourself with the skills and knowledge to track these attackers and learn about them on your own.
I have been using honeypots for many years, and I find them absolutely fascinating. They are an exciting technology that not only teaches you a great deal about blackhats but also teaches you about yourself and security in general. I hope you enjoy this book as much as I have enjoyed writing and learning about honeypot technologies.
This book is intended for the security professional. Anyone involved in protecting or securing computer resources will find this resource valuable. It is the first publication dedicated to honeypot technologies, a tool that more and more computer security professionals will want to take advantage of once they understand its power and flexibility.
Due to honeypots' unique capabilities, other individuals and organizations will be extremely interested in this book. Military organizations can apply these technologies to Cyberwarfare. Universities and security research organizations will find tremendous value in the material concerning research honeypots. Intelligence organizations can apply this book to intelligence and counterintelligence activities. Members of law enforcement can use this material for the capturing of criminal activities. Legal professionals will find Chapter 15 to be one of the first definitive resources concerning the legal issues of honeypots.
A CD-ROM accompanies this book and contains additional information related to the topics in the book. It includes everything from whitepapers and source code to actual evaluation copies of software and data captures of real attacks. This will give you the hands-on opportunity to develop your skills with honeypot technologies.
This book has a Web site dedicated to it. The purpose of the Web site is to keep this material updated. If any discrepancies or mistakes are found in the book, the Web site will have updates and corrections. For example, if any of the URLs in the book have been changed or removed, the Web site will provide the updated links. Also, new technologies are always being developed and deployed. You should periodically visit the Web site to stay current with the latest in honeypot technologies.
http://www.tracking-hackers.com/book/
Each chapter ends with a references section. The purpose is to provide you with resources to gain additional information about topics discussed in the book. Examples of references include Web sites that focus on securing operating systems and books that specialize in forensic analysis.
Lance Spitzner is a geek who constantly plays with computers, especially network security. He loves security because it is a constantly changing environment. His love for tactics first began in the U.S. Army, where he served both as an enlisted infantryman in the National Guard and as an armor officer in the Rapid Deployment Force. Following the Army he received his graduate degree and became involved in the world of information security. Now he fights the enemy with IPv4 packets instead of 120mm SABOT rounds.
His passion is researching honeypot technologies and using them to learn more about the bad guys. He is also actively involved with the security community. He is founder of the Honeynet Project, moderator of the honeypot mail list, coauthor of Know Your Enemy, and author of several whitepapers. He has also spoken at various conferences and organizations, including Blackhat, SANS, CanSecWest, the Pentagon, the FBI Academy, West Point, National Security Agency, and Navy War College. He is a senior security architect for Sun Microsystems Inc.
For many, the obstacle to learning refactoring is in identifying the "smells"—the potential problem areas-found in code. Instead of having you read about the smells, Refactoring Workbook makes sure you understand them. You'll solve a carefully assembled series of problems, and you'll find yourself learning at a deeper level and arriving at a few insights of your own. Wake uses the workbook method—a learning-focused approach that forces you to apply the techniques presented in the book-in the rest of the book. This approach helps you learn and apply the most important refactoring techniques to your code and, as a side benefit, helps you to think more about creating great code even when you're not refactoring.
Refactoring Workbook provides user-friendly references such as:
This book is intended for programmers with a knowledge of Java, though a C# or C++ programmer with a basic understanding of Java would also be able to follow and learn from the examples. It can be used as a companion to Martin Fowler's Refactoring (also from Addison-Wesley Professional), which provides step-by-step instructions for many refactorings.
]]>Refactoring is the art of improving the design of existing code. Refactoring provides us with ways to recognize problematic code and gives us recipes for improving it.
This book is a workbook designed to help you
To a smaller extent, this book is a reference book with
Refactoring being a technique for code, this book then is especially intended for practicing programmers who write and maintain code.
Students can also benefit from refactoring, although I'd expect they'd see the value only after they've had a chance to develop medium-sized or larger programs or had to work in teams (this probably applies to juniors, seniors, and graduate students).
It would be helpful to have the book, Refactoring: Improving the Design of Existing Code, by Martin Fowler et al. for its catalog of refactorings. (You can read my book and Refactoring at the same time.) Martin and his colleagues have worked out step-by-step instructions for many refactorings, and I will not repeat those in this book. Furthermore, they've provided a fully worked-out example, along with a lot of good discussion and background material. Someone determined to get through this book without that one could probably do it, but I wouldn't recommend it.
The examples in this book are written in Java. This is not because it's the easiest language to refactor, but because it's popular, and the best Java development environments provide automated refactoring support. A C# or C++ programmer has enough reading knowledge of Java to make sense of most of the questions. However, in later parts of the book, you will modify, test, and run larger programs, and this could be problematic for programmers using languages other than Java.
The book Design Patterns, by Gamma et al., describes patterns as "targets for refactoring." It would be helpful to have some familiarity with the ideas in that book because I freely refer to the patterns it mentions. If you're not yet familiar with Design Patterns, let me recommend Steve Metsker's book, Design Patterns Java Workbook, as well.
Solving a problem is more challenging than recognizing a solution. There are answers to some problems in the back of the book, but you'll learn more if you try the problems before peeking at the answers. If you work through the problems, you'll probably even find that you disagree with me on some answers. That will be more fun for all of us than if you just look at my answers and nod.
I think it's more fun to work with others (either a partner or in a small group), but I recognize that isn't always possible.
The later (longer) examples need to be done at a computer. Looking for problems, and figuring out how to solve them, is different when you're looking at a program in your environment.
]]>
I. SMELLS WITHIN CLASSES.
II. SMELLS BETWEEN CLASSES.
III. PROGRAMS TO REFACTOR.
IV. APPENDIXES.
I. SCIENTIFIC CONVENTIONS.
II. SAMPLE RESEARCH CASES.
Eoin Woods is a principal consultant at Züehlke Engineering in London, where he works as a consultant software architect focusing on trading and investment management companies in the financial markets. He has worked in the software engineering field for fifteen years with a number of companies, including Ford Motor Company, Groupe Bull, InterTrust Technologies, and Sybase.
With this book you will learn how to
The architectural viewpoints and perspectives presented in the book also provide a valuable long-term reference source for new and experienced architects alike.
Whether you are an aspiring or practicing software architect, you will find yourself referring repeatedly to the practical advice in this book throughout the lifecycle of your projects.
A supporting Web site containing further information can be found at www.viewpoints-and-perspectives.info
While there may be an emerging consensus that the software architect's role is an important one, there seems to be little agreement on what the job actually involves. Who are our clients? To whom are we accountable? What are we expected to deliver? What is our involvement once the architectural design has been completed? And, perhaps most fundamentally, where are the boundaries between requirements, architecture, and design?
The absence of a clear definition of the role is all the more problematic because of the seriousness of the problems that today's software projects (and specifically, their architects) have to resolve.
When we first started to take on the role of software architects, we looked for some sort of software architecture handbook that would walk us through the process of developing an architectural design. After all, other architectural disciplines have behind them centuries of theory and established best practice.
For example, in the first century A.D., the Roman Marcus Vitruvius Pollio wrote the first ever architectural handbook, De architectura libri decem ("Ten Books on Architecture"), describing the building architect's role and required skills and providing a wealth of material on standard architectural structures. In 1670, Anthony Deane, a friend of diarist Samuel Pepys, a former mayor of the English town of Harwich and later a member of Parliament, published a ground-breaking textbook, A Doctrine of Naval Architecture, which described in detail some of the leading methods of the time for large ship design. Deane's ideas and principles helped systematize the practice of naval architecture for many years. And in 1901, George E. Davis, a consulting engineer in the British chemical industry, created a new field of engineering when he published his text A Handbook of Chemical Engineering. This text was the first book to define the practical principles underpinning industrial chemical processes and guided the field for many years afterward.
The existence of such best practices has a very important consequence in terms of uniformity of approach. If you were to give several architects and engineers a commission to design a building, a cruise liner, or a chemical plant, the designs they produced would probably differ. However, the processes they used, the ways they represented their designs on paper (or a computer screen), and the techniques they used to ensure the soundness of their designs would be very similar.
Sadly, our profession has yet to build any significant legacy of mainstream industrial best practices. When we looked, we found a dearth of introductory books to guide practicing information systems architects in the details of doing their jobs.
Admittedly, we have an abundance of books on specific technologies, whether it's J2EE, CORBA, or .NET, and some on broader topics such as Web services or object orientation (although, because of the speed at which software technology changes, many of these become out-of-date within a few years). There are also a number of good general software architecture books, several of which we refer to in later chapters. But many of these books aim to lay down principles that apply across all sorts of systems and so are written in quite general terms, while most of the more specific texts are aimed at our colleagues in the real-time and embedded-systems communities.
We feel that if you are a new software architect for an information system, the books that actually tell you how to do your job, learn the important things you need to know, and make your architectural designs successful are few and far between. While we don't presume to replace the existing texts on software architecture or place ourselves alongside the likes of Vitruvius, Deane, and Davis, addressing these needs was the driving force behind our decision to write this book.
Specifically, the book shows you
Throughout the book we primarily focus on the development of large-scale information systems (by which we mean the computer systems used to automate the business operations of large organizations). However, we have tried to present our material in a way that is independent of the type of information system you are designing, the technologies the developers will be using, and the software development lifecycle your project is following. We have standardized on a few things, such as the use of Unified Modeling Language (UML) in most of our diagrams, but we've done that only because UML is the most widely understood modeling language around. You don't have to be a UML expert to understand this book.
We didn't set out to be the definitive guide to developing the architecture of your information system--such a book would probably never be finished and would require the collaboration of a huge number of experts across a wide range of technical specializations. Also, we did not write a book of prescriptive methods. Although we present some activity diagrams that explain how to produce your deliverables, these are designed to be compatible with the wide range of software development approaches in use today.
What we hope we have achieved is the creation of a practical, practitioner-oriented guide that explains how to design successful architectures for information systems and how to see these through to their successful implementation. This is the sort of book that we wish had been available when we started out as software architects, and one that we expect to refer to even now.
You can find further useful software architecture resources, and contact us to provide feedback on the book's content, via our Web page: www.viewpoints-and-perspectives.info. We look forward to hearing from you.
]]>Acknowledgments.
About the Authors.
1. Introduction.
Stakeholders, Viewpoints, and Perspectives.
The Structure of This Book.
Who Should Read This Book.
Conventions Used.
I. ARCHITECTURE FUNDAMENTALS.
2. Software Architecture Concepts.
Software Architecture.
Architectural Elements.
Stakeholders.
Architectural Descriptions.
Interrelationships between the Core Concepts.
Summary.
Further Reading.
3. Viewpoints and Views.
Architectural Views.
Viewpoints.
Interrelationships between the Core Concepts.
The Benefits of Using Viewpoints and Views.
Viewpoint Pitfalls.
Our Viewpoint Catalog.
Summary.
Further Reading.
4. Architectural Perspectives.
Quality Properties.
Architectural Perspectives.
Applying Perspectives to Views.
Consequences of Applying a Perspective.
Interrelationships between the Core Concepts.
The Benefits of Using Perspectives.
Perspective Pitfalls.
Our Perspective Catalog.
Summary.
Further Reading.
5. The Role of the Software Architect.
The Architecture Definition Process.
The Role of the Architect.
Interrelationships between the Core Concepts.
Architectural Specializations.
The Organizational Context.
The Architect's Skills.
The Architect's Responsibilities.
Summary.
Further Reading.
II. THE PROCESS OF SOFTWARE ARCHITECTURE.
6. Introduction to the Software Architecture Process.
7. The Architecture Definition Process.
Guiding Principles.
Process Outcomes.
The Process Context.
Supporting Activities.
Architecture Definition Activities.
Process Exit Criteria.
Architecture Definition in the Software Development Lifecycle.
Summary.
Further Reading.
8. Scope, Concerns, Principles, and Constraints.
Business Goals and Drivers.
Architectural Scope.
Architectural Concerns.
Architectural Principles.
Other Architectural Constraints.
Checklist.
Summary.
Further Reading.
9. Identifying and Engaging Stakeholders.
Selection of Stakeholders.
Classes of Stakeholders.
Examples.
Proxy Stakeholders.
Stakeholder Groups.
Stakeholders' Responsibilities.
Checklist.
Summary.
Further Reading.
10. Identifying and Using Scenarios.
Types of Scenarios.
Uses for Scenarios.
Identifying and Prioritizing Scenarios.
Capturing Scenarios.
Applying Scenarios.
Effective Use of Scenarios.
Checklist.
Summary.
Further Reading.
11. Using Styles and Patterns.
Software Patterns.
Styles, Patterns, and Idioms.
An Example of an Architectural Style.
The Benefits of Using Architectural Styles.
Styles and the Architectural Description.
Common Architectural Styles.
Design Patterns and Language Idioms in Architecture.
Checklist.
Summary.
Further Reading.
12. Producing Architectural Models.
Why Models Are Important.
Types of Models.
Modeling Languages.
Guidelines for Creating Effective Models.
Agile Modeling Techniques.
Checklist.
Summary.
Further Reading.
13. Creating the Architectural Description.
Properties of an Effective Architectural Description.
Glossaries.
The IEEE Standard.
Contents of the Architectural Description.
Checklist.
Summary.
Further Reading.
14. Validating the Architecture.
Why Validate the Architecture?
Validation Techniques.
Scenario-Based Evaluation Methods.
Validation during the Software Lifecycle.
Recording the Results of Validation.
Checklist.
Summary.
Further Reading.
III. THE VIEWPOINT CATALOG.
15. Introduction to the Viewpoint Catalog.
16. The Functional Viewpoint.
Concerns.
Models.
Problems and Pitfalls.
Checklist.
Further Reading.
17. The Information Viewpoint.
Concerns.
Models.
Problems and Pitfalls.
Checklist.
Further Reading.
18. The Concurrency Viewpoint.
Concerns.
Models.
Problems and Pitfalls.
Checklist.
Further Reading.
19. The Development Viewpoint.
Concerns.
Models.
Problems and Pitfalls.
Checklist.
Further Reading.
20. The Deployment Viewpoint.
Concerns.
Models.
Problems and Pitfalls.
Checklist.
Further Reading.
21. The Operational Viewpoint.
Concerns.
Models.
Problems and Pitfalls.
Checklist.
Further Reading.
22. Achieving Consistency across Views.
Relationships between Views.
Functional and Information View Consistency.
Functional and Concurrency View Consistency.
Functional and Development View Consistency.
Functional and Deployment View Consistency.
Functional and Operational View Consistency.
Information and Concurrency View Consistency.
Information and Development View Consistency.
Information and Deployment View Consistency.
Information and Operational View Consistency.
Concurrency and Development View Consistency.
Concurrency and Deployment View Consistency.
Deployment and Operational View Consistency.
IV. THE PERSPECTIVE CATALOG.
23. Introduction to the Perspective Catalog.
24. The Security Perspective.
Applicability to Views.
Concerns.
Activities: Applying the Security Perspective.
Architectural Tactics.
Problems and Pitfalls.
Checklists.
Further Reading.
25. The Performance and Scalability Perspective.
Applicability to Views.
Concerns.
Activities: Applying the Performance and Scalability Perspective.
Architectural Tactics.
Problems and Pitfalls.
Checklists.
Further Reading.
26. The Availability and Resilience Perspective.
Applicability to Views.
Concerns.
Activities: Applying the Availability and Resilience Perspective.
Architectural Tactics.
Problems and Pitfalls.
Checklists.
Further Reading.
27. The Evolution Perspective.
Applicability to Views.
Concerns.
Activities: Applying the Evolution Perspective.
Architectural Tactics.
Problems and Pitfalls.
Checklists.
Further Reading.
28. Other Perspectives.
The Accessibility Perspective.
The Development Resource Perspective.
The Internationalization Perspective.
The Location Perspective.
The Regulation Perspective.
The Usability Perspective.
V. PUTTING IT ALL TOGETHER.
29. Working as a Software Architect.
The Architect in the Project Lifecycle.
The Architect in Different Types of Projects.
Appendix: Other Viewpoint Sets.
Kruchten "4+1".
RM-ODP.
Siemens (Hofmeister, Nord, and Soni).
SEI Viewtypes.
Garland and Anthony.
Bibliography.
Index.
]]>Ila Neustadt has worked in IT for British Airways for more than twenty years and has experience of all parts within the IT development life cycle. She worked in the strategy department modeling the architecture process and developing architecture training, and acted as program head for the graduate business analyst program. Ila now coordinates skills development for BA™s IT staff.
“I’ve never seen a system of business patterns as detailed as this one. The completeness that Arlow and Neustadt provide in these patterns is impressive. The explanations for why the patterns are formed the way they are and how they’re interconnected are incredibly thorough. The patterns presented here have the potential to impact business applications in the same way the ‘Gang of Four’ patterns have impacted general software development.”
—Steve Vinoski“Enterprise Patterns and MDA is a detailed, yet very readable, guide to designing business applications using reusable model components and Model Driven Architecture. It deserves a place on every application designer’s desk.”
—Andrew Watson“Design patterns are generally acknowledged as an effective approach to developing robust and highly reusable software. Now that Model Driven Architecture is raising software design to ever-higher levels of abstraction, it is only natural that pattern concepts should find application in advanced modeling techniques. With this book, Arlow and Neustadt have greatly advanced the state of the art of MDA by defining both a theory and a methodology for applying the concept of Archetype Patterns to business software modeling.”
—John Poole“The burgeoning field of Model Driven Architecture tools and worldwide support for the Unified Modeling Language are finally being met with high-quality books that explain standard modeling techniques in a way any developer can follow. This book meets an urgent need squarely and clearly, and explains with copious examples a powerful approach to building usable (and reusable!) assets and applications. Every enterprise developer needs this book.”
—Richard Mark Soley, Ph.D.This book is a practical guide to applying Model Driven Architecture (MDA) and patterns in order to create business applications more easily. It provides you with a proven catalog of archetype patterns: high-value model components that can be easily incorporated into Unified Modeling Language (UML) models. Each archetype pattern allows you to understand and model a specific part of an enterprise system.
Enterprise Patterns and MDA teaches you how to customize any archetype pattern—such as Customer, Product, and Order—to reflect the idiosyncrasies of your own business environment. Because all the patterns work harmoniously together and have clearly documented relationships to each other, you’ll come away with a host of reusable solutions to common problems in business-software design.
This book shows you how using a pattern or a fragment of a pattern can save you months of work and help you avoid costly errors. You’ll also discover how—when used in literate modeling—patterns can solve the difficult challenge of communicating UML models to broad audiences.
The configurable patterns can be used manually to create executable code. However, the authors draw on their extensive experience to show you how to tap the significant power of MDA and UML for maximum automation. Not surprisingly, the patterns included in this book are highly valuable; a blue-chip company recently valued a similar, but less mature, set of patterns at hundreds of thousands of dollars.
Use this practical guide to increase the efficiency of your designs and to create robust business applications that can be applied immediately in a business setting.
This is a practical book that we hope will save you a great deal of time and effort in your software development projects. It gives you a set of archetype patterns and the theory you need to use them effectively. We’re planning to publish some more volumes of archetype patterns over the next few years, and because this book is the first volume, it sets the theoretical groundwork for future work on archetypes.
Archetype patterns are high-value model components that you can easily use in your own UML models. Each archetype pattern provides a solution for understanding and modeling a specific part of a business system. These patterns are valuable—a similar, but much less mature, set of patterns was recently independently valued at about $300,000 by a blue chip company. Using any one of these patterns, or even a pattern fragment, may save you many days or months of work. Even more important than this saving is the fact that each archetype pattern may prevent you from making expensive mistakes! All of the patterns presented in this volume work together harmoniously and so provide a unified pattern language for talking about selling systems. This harmony greatly adds to their value.
We think that in the year 2003, we are at the start of a revolution in software development. Much as the 1990s saw an increase in the level of abstraction from procedural to object-oriented code, we believe that this decade will see a further, and more significant, increase in the level of abstraction. This will be a change from code-centric software development to model-centric software development through the OMG’s Model Driven Architecture (MDA) initiative. We hope that the concepts, techniques, tools and patterns that we describe in this book will help us all to make this revolution in software development a reality.
Our Vision
One of the reasons this book came about was through boredom! After modeling for many years, we decided that we were often just doing the same old thing over and over again. At their most abstract levels, most businesses seem to be made up of the same semantic elements—Customer, Product, Order, Party, etc. In fact, so pervasive are some of these elements, that it led us to the notion of business archetype patterns. We speculated that most business systems could be assembled, like Lego bricks, from a sufficiently complete set of archetype patterns.
The essence of our vision is that archetype patterns should be treated as a type of “model component” that can be taken off the shelf, customized and instantiated in your own models. This process can be done manually, but ideally should be automated to as high a degree as possible, by using an MDA (Model Driven Architecture) tool.
Today, you can use a GUI builder to create graphical user interfaces rapidly from GUI components. The work we describe in Chapter 2 enables you to construct semantically correct and verifiable UML models rapidly from platform independent, generic, model components with a high degree of automation. We believe that this may be the future of software development. We call this “component based modeling.”
This is reuse writ large—software systems are not considered to be composed of reusable classes, reusable code components, or even reusable subsystems, but rather from the reusable semantic elements that we call archetype patterns. In fact, to a great extent the essence of the business system lies in its archetypes and their patterns, rather than in any code or design artifacts. Coding practices, design practices and even architectures come and go with technology changes, but the archetypes survive, largely unchanged, sometimes over millennia.
Why We Haven’t Done It Sooner
We have wanted to write this book for several years but there have been obstacles that we have only recently overcome. These obstacles were:
The Structure of This Book
There are four main threads to this book:
Chapters 1, 2 and 3 provide you with the theoretical basis for the rest of the book, and you will find that they cover a lot of new material. In Chapter 1 we describe a new approach to dealing with the problem of pattern variation—how to adapt patterns for different usage contexts. In Chapter 2 we show you how you can automate the process of using archetype patterns using an MDA-enabled UML modeling tool. The first two Chapters are intimately related. The pattern automation described in Chapter 2 depends on the theory of archetypes and archetype patterns presented in Chapter 1. Chapter 3 describes the technique of literate modeling that you can use to document your patterns. This chapter is pretty much self-contained. Literate modeling is a powerful way of communicating UML models to a wide audience.
Each of the first three chapters contains a summary that reiterates the key information in the chapter in a very concise outline form. This is great for revision and it is also a useful source of bullet points for presentations.
The pattern catalog can stand alone. If you choose to use the book primarily as a pattern catalog (Chapter 4 through Chapter 12), then you can skip much of the theoretical background in the first three chapters. Use the pattern catalog as a valuable resource for your own models. Each of the pattern chapters ends with a very brief summary that lists the key concepts and archetypes introduced in that chapter. Again, we do this in outline form.
Having said that the pattern catalog can stand alone, we believe that you will be able to apply the patterns much more effectively if you have at least a basic understanding of archetype theory first. You can find all you need to know in Chapter 1. All the patterns in the in the pattern catalog are a direct result of the application of the theories and techniques described in the first three chapters. The notions of archetypes, archetype patterns, pattern configuration and literate modeling have allowed us to create much more complete and robust patterns than would otherwise have been possible. Finally, we provide a glossary of archetypes, a bibliography and a complete index.
Text Processing in Python begins with an introduction to text processing and contains a quick Python tutorial to get you up to speed. It then delves into essential text processing subject areas, including string operations, regular expressions, parsers and state machines, and Internet tools and techniques. Appendixes cover such important topics as data compression and Unicode. A comprehensive index and plentiful cross-referencing offer easy access to available information. In addition, exercises throughout the book provide readers with further opportunity to hone their skills either on their own or in the classroom. A companion Web site (http://gnosis.cx/TPiP) contains source code and examples from the book.
Here is some of what you will find in thie book:
At the broadest level text processing is simply taking textual information and doing something with it. This doing might be restructuring or reformatting it, extracting smaller bits of information from it, algorithmically modifying the content of the information, or performing calculations that depend on the textual information. The lines between "text" and the even more general term "data" are extremely fuzzy; at an approximation, "text" is just data that lives in forms that people can themselves read—at least in principle, and maybe with a bit of effort. Most typically computer "text" is composed of sequences of bits which have a "natural" representation as letters, numerals and symbols; and most often such text is delimited (if delimited at all) by symbols and formatting that can be easily pronounced as "next datum."
The lines are fuzzy, but the data that seems least like text—and that, therefore this particular book is least concerned with—is the data that makes up "multimedia" (pictures, sounds, video, animation, etc.) and data that makes up UI "events" (draw a window, move the mouse, open an application, etc.). Like I said, the lines are fuzzy, and some representations of the most non-textual data are themselves pretty textual. But in general, the subject of this book is all the stuff on the near side of that fuzzy line.
Text processing is arguably what most programmers spend most of their time doing. The information that lives in business software systems mostly comes down to collections of words about the application domain—maybe with a few special symbols mixed in. Internet communications protocols consist mostly of a few special words used as headers, a little bit of constrained formatting, and message bodies consisting of additional wordish texts. Configuration files, log files, CSV and fixed-length data files, error files, documentation, and source code itself, are all just sequences of words with bits of constraint and formatting applied.
Programmers and developers spend so much time with text processing, that it is easy to forget that that is what we are doing. The most common text processing application is probably your favorite text editor. Beyond simple entry of new characters, text editors perform such text processing tasks as search/replace and copy/paste, which—given guided interaction with the user—accomplishes sophisticated manipulation of textual sources. Many text editors go farther than these simple capabilities, and include their own complete programming systems (usually called "macro processing"); in those cases where editors include "Turing-complete" macro languages, text editors suffice, in principle, to accomplish anything that the examples in this book can.
After text editors, a variety of text processing tools are widely used by developers. Tools like "File Find" under Windows, or "grep" on Unix (and other platforms) perform the basic chore of locating text patterns. "Little languages" like sed and awk perform basic text manipulation (or even non-basic). A large number of utilities—especially in Unix-like environments—perform small custom text processing tasks: wc, sort, tr, md5sum, uniq, split, strings and many others.
At the top of the text processing food chain are general purpose programming languages, such as Python. I wrote this book on Python in large part because Python is such a clear, expressive, and general purpose language. But for all Python's virtues, text editors and "little" utilities will always have an important place for developers "getting the job done." As simple as Python is, it is still more complicated than you need to achieve many basic tasks. But once you get past the very simple, Python is a perfect language for making the difficult things possible (and it is also good at making the easy things simple).
Hang around any Python discussion groups for a little while, and you will certainly be dazzled by the contributions of the Python developer, Tim Peters (and by a number of other Pythonistas). His "Zen of Python" captures much of the reason that I choose Python as the language in which to solve most programming tasks that are presented to me. But to understand what is most special about text processing as a programming task, it is worth turning to Perl creator Larry Wall's cardinal virtues of programming: Laziness, impatience, hubris.
What sets text processing most clearly apart from other tasks computer programmers accomplish is the frequency with which we perform text processing on an ad hoc or "one-shot" basis. One rarely bothers to create a one-shot GUI interface for a program. You even less frequently performs a one-shot normalization of a relational database. But every programmer with a little experience has had numerous occasions where she has received a trickle of textual information (or maybe a deluge of it) from another department, from a client, from a developer working on a different project, or from data dumped out of a DBMS; the problem in such cases is always to "process" the text so that it is usable for our own project, program, database, or work unit. Text processing to the rescue. This is where the virtue of impatience first appears—we just want the stuff processed, right now!
But text-processing tasks that were obviously one-shot tasks that we knew we would never need again have a habit of coming back like restless ghosts. It turns out that that client needs to update the one-time data they sent last month. Or the boss decides that she would really like a feature of that text summarized in a slightly different way. The virtue of laziness is our friend here—with our foresight not to actually delete those one-shot scripts, we have them available for easy reuse and/or modification when the need arises.
Enough is not enough, however. That script you reluctantly used a second time turns out to be quite similar to a more general task you will need to perform frequently, perhaps even automatically. You imagine that with only a slight amount of extra work you can generalize and expand the script, maybe add a little error checking and some runtime options while you are at it; and do it all in time and under budget (or even as a side project, off the budget). Obviously, this is the voice of that greatest of programmers' virtues: hubris.
The goal of this book is to make its readers a little lazier, a smidgeon more impatient, and a whole bunch more hubristic. Python just happens to be the language best suited to the study of virtue.
This book is ideally suited for programmers who are a little bit familiar with Python, and whose daily tasks involve a fair amount of text processing chores. Programmers who have some background in other programming languages—especially with other "scripting" languages—should be able to pick up enough Python to get going by reading Appendix A.
While Python is a rather simple language at heart, this book is not intended as a tutorial on Python for non-programmers. Instead, this book is about two other things: getting the job done, pragmatically and efficiently; and understanding why what works works and what doesn't work doesn't work, theoretically and conceptually. As such, we hope this book can be useful both to working programmers and to students of programming at a level just past the introductory.
Many sections of this book are accompanied by problems and exercises, and these in turn often pose questions for users. In most cases, the answers to the listed questions are somewhat open-ended—there are no simple right answers. I believe that working through the provided questions will help both self-directed and instructor-guided learners; the questions can typically be answered at several levels, and often have an underlying subtlety. Instructors who wish to use this text are encouraged to contact the author for assistance in structuring a curriculum involving it. All readers are encouraged to consult the book's web site to see possible answers provided by both the author and other readers; additional related questions will be added to the web site over time, along with other resources.
The Python language itself is conservative. Almost every Python script written ten years ago for Python 1.0 will run fine in Python 2.3+. However, as versions improve, a certain number of new features have been added. The most significant changes have matched the version number changes—Python 2.0 introduced list comprehension's, augmented assignments, Unicode support, and a standard XML package. Many scripts written in the most natural and efficient manner using Python 2.0+ will not run without changes in earlier versions of Python.
The general target of this book will be users of Python 2.1+, but some 2.2+ specific features will be utilized in examples. Maybe half the examples in this book will run fine on Python 1.5.1+ (and slightly fewer with older versions), but examples will not necessarily indicate their requirement for Python 2.0+ (where it exists). On the other hand, new features introduced with Python 2.1 and above will only be utilized where they make a task significantly easier, or where the feature itself is being illustrated. In any case, examples requiring versions past Python 2.0 will usually indicate this explicitly.
In the case of modules and packages—whether in the standard library or third-party—we will explicitly indicate what Python version is required; and where relevant, which version added the module or package to the standard library. In some cases, it will be possible to use later standard library modules with earlier Python versions. In important cases, this possibility will be noted.
All constants, functions, and classes in discussions and cross-references will be explicitly prepended with their namespace (module). Methods will additionally, be prepended with their class. In some cases, code examples will use the local namespace, but a preference for explicit namespace identification will be present in sample code also. For example, a reference might read:
See Also: email.Generator.DecodedGenerator.flatten() 346; raw input() 442; tempfile.mktemp() 70;
The first is a class method in the email.Generator module; the second, a built-in function; the last, a function in the tempfile module
In the special case of built-in methods on types, the expression for an empty type object will be used in the style of a namespace modifier. For example:
Methods of built-in types include .sort(), "".islower(), {}.keys(), and (lambda:1).func code.
The file object type will be indicated by the name FILE in capitals; A reference to a file object method will appear as, e.g.:
See Also: FILE.flush() 16;
Brief inline illustrations of Python concepts and usage will be taken from the Python interactive shell. This approach allows readers to see the immediate evaluation of constructs, much as they might explore Python themselves. Moreover, examples presented in this manner will be self-sufficient (not requiring external data), and may be entered—with variations—by readers trying to get a grasp on a concept. For example:
>>> 13/7 # integer division
1
>>> 13/7. # float division
1.8571428571428572
In documentation of module functions, where named arguments are available, they are listed with their default value. Optional arguments are listed in square brackets. These conventions are also used in the Python Library Reference. For example:
foobar.spam(s, val=23 ,taste="spicy")If a named argument does not have a specifiable default value, the argument is listed followed by an equal sign and ellipsis. For example:
foobar.baz(string=. . . , maxlen=. . . )With the introduction of Unicode support to Python, an equivalence between a character and a byte no longer holds in all cases. Where an operation takes a numeric argument affecting a string-like object, the documentation will specify whether characters or bytes are being counted. For example:
Operation A reads num bytes from the buffer. Operation B reads num charactersfrom the buffer.
The first line indicates a number of actual 8-bit bytes affected. The second line indicates an indefinite number of bytes are affected, but that they compose a number of (maybe multi-byte) characters.
First things first. All the source code in this book is hereby released to the public domain. You can use it however you like, without restriction. You can include it in free software, or in commercial/proprietary projects. Change it to your heart's content, and in any manner you want. If you feel like giving credit to the author (or sending him large checks) for code you find useful, that is fine—but no obligation to do so exists.
All the source code in this book, and various other public domain examples, can be found at the book's web site. If such an electronic form is more convenient for you, we hope this helps you. In fact, if you are able, you might benefit from visiting this location, where you might find updated versions of examples or other useful utilities not mentioned in the book.
First things out of the way, let us turn to second things. Little of the source code in this book is intended as a final say on how to perform a given task. Many of the examples are easy enough to copy directly into your own program, or to use as stand-alone utilities. But the real goal in presenting the examples is educational. We really hope you will think about what the examples do, and why they do it the way they do. In fact, we hope readers will think of better, faster, and more general ways of performing the same tasks. If the examples work their best, they should be better as inspirations than as instructions.A good clearing house for resources and links related to this book is the book's web site. Over time, I will add errata and additional examples, questions, answers, utilities, etc. to the site, so check it from time to time:
http://gnosis.cx/TPiP/
The first place you should probably turn for any question on Python programming(after this book), is:
http://www.python.org/
The Python newsgroup comp.lang.python is an amazingly useful resource, with discussion that is generally both friendly and erudite. You may also post to and follow the newsgroup via a mirrored mailing list:
http://mail.python.org/mailman/listinfo/python-list
This book generally aims at an intermediate reader. Other Python books are better introductory texts (especially for those fairly new to programming generally). Some good introductory texts are:
As introductions, I would generally recommend these books in the order listed, but learning styles vary between readers.
Two texts that overlap this book somewhat, but focus more narrowly on referencing the standard library are:
For coverage of XML, at a far more detailed level than this book has room for, is the excellent text:
Currently, the best Python-specific directory for software is the Vaults of Parnassus:
http://www.vex.net/parnassus/
SourceForge is a general open source software resource. Many projects—Python and otherwise—are hosted at that site, and the site provides search capabilities, keywords, category browsing, and the like:
http://sourceforge.net/
Freshmeat is another widely used directory of software projects (mostly open source). Like the Vaults of Parnassus, Freshmeat does not directly host project files, but simply acts as an information clearing house for finding relevant projects:
http://freshmeat.net/
A number of Python projects are discussed in this book. Most of those are listed in one or more of the software directories mentioned above. A general search engine like Google, http://google.com, is also useful in locating project homepages. Below are a number of project URLs that are current at the time of this writing. If any of these fall out of date by the time you read this book, try searching in a search engine or software directory for an updated URL.
The author's Gnosis Utilities contains a number of Python packages mentioned in this book, including gnosis.indexer, gnosis.xml.indexer, gnosis.xml.pickle, and others. You can download the most current version from:
http://gnosis.cx/download/Gnosis Utils-current.tar.gz
eGenix.com provides a number of useful Python extensions, some of which are documented in this book. These include mx.TextTools, mx.DateTime, severeral new datatypes, and others facilities:
http://egenix.com/files/python/eGenix-mx-Extensions.html
SimpleParse is hosted by SourceForge, at:
http://simpleparse.sourceforge.net/
The PLY parsers has a home page at:
http://systems.cs.uchicago.edu/ply/ply.html
Thomas J. Shelford is a partner in Project Calibrate™, a consulting group specializing in Web project management training (http://www.projectcalibrate.com). He began his Web-related career in 1996 as the founder of SeaState Internet Solutions, a freelance Web development shop.
Gregory A. Remillard has been a project manager on large-scale Web development projects for five years. He has managed projects for diverse companies such as Gruner & Jahr USA (Parents.com) and UrbanExpress.com (formerly UrbanFetch.com). Greg is a founding partner of Project Calibrate™ (http://www.projectcalibrate.com).
The process of designing and building today's dynamic Web applications comes with a host of challenges not typically solved by traditional project management methodologies. A wealth of practical resources, Real Web Project Management: Case Studies and Best Practices from the Trenches is a book of solutions for designing, managing, and delivering virtually any type of Web-based project under even the most challenging of conditions.
Based on solutions implemented from actual, real-world scenarios, this practical book offers a complete road map for navigating every facet of a contemporary Web project. Filled with tips and techniques, it provides practices to implement and pitfalls to avoid to ensure success. Beginning by outlining the responsibilities of the project manager, this complete and comprehensive guide then covers team assembly and communication, project definition, change management, planning strategies, and workflow before moving on to the design, build, and delivery stages. The book's accessible format also provides immediate hands-on solutions for project managers seeking a quick answer to a particular problem.
Issues covered include:
This book is packaged with a value-added CD-ROM, which includes complete project plan templates, model Web sites, project checklists, consulting contracts, software vendor reviews, and more. Additional resources and templates are available on the book's accompanying Web site at http://www.realwebprojects.com.
All of this makes Real Web Project Management an essential reference for the working project manager, or for those new to the field. It is the most comprehensive resource available for planning, managing, and executing successful Web-based applications.
The search for knowledge began with Yahoo! At the time, our search turned up only a small handful of Web sites devoted to project management but nothing Web-specific. We did discover the Project Management Body of Knowledge® (PMBOK®) from the Project Management Institute (PMI). PMBOK, and other project management books, taught us basic, traditional project management processes and methods that had been used in other industries for years. We felt reassured with this newfound knowledge but at the same time a little uneasy because we still could find nothing specific on Web project management. "That's all right," we thought. "A project's a project--right?"
As we set out to mimic our colleagues in the more mature branches of software project management, a dark, uneasy feeling entered the pits of our stomachs at the kickoff meeting of every new project. Somehow, in spite of everything we had recently read about process and methodology, we knew we were going to end up doing the one thing we felt sure would betray the very premise of project management: wing it.
The disconnect between the correct process and what happens in real life has been a source of growing unease among Web project managers. For a time, many people explained away the problem by pointing to the inexperience of the industry. It was assumed that, once traditional software development processes and best practices were understood by immature Web professionals, the chaos would subside. Well, not quite. As we gained more experience, project by project, we discovered that the harder we tried to adhere to the use of traditional project management methods, the more frustrated we became, and the more chaotic the atmosphere seemed.
How do you hit a hard-and-fast completion date when the specifications for the project are changed and expanded daily by the very person who is mandating the completion date? In your project plan, how do you account for the time your star developer spends getting in the mood to work by shooting minibasketball free throws for a couple of hours, followed by a donut run, and then a few quick games of UNO with the graphic designer? This was our reality. Knowing when or how to implement overengineered or seemingly inapplicable project management techniques like "force field analysis" or "interrelationship digraphs"caused us to second guess our approach to the "science" of project management. We needed techniques and processes we could implement NOW that would garner us the greatest results in the shortest amount of time.
Because of the continued rapid growth of the Web, the constant changes to the technologies that support it, and the frenzied, media-driven expectations and mythologies that surround it, developing Web sites using only traditional project management methodologies adopted from other industries just was not enough to get the job done. Many traditional methodologies rely on the existence of a fixed scope and clear, measurable objectives. Web site design and development, however, is not like building a rocket or releasing an off-the-shelf software product. Web teams must collaborate in a continually unfolding creative process, which is often more of an art than a science.
Traditional methods will get you part way there. Basic process building blocks can be used with great success and should be. In this book, we demonstrate some of the basic methods as they relate to Web development. But we also demonstrate where traditional methods fail and discuss how the ability to improvise and think on your feet will serve you far better than a painstakingly constructed work breakdown structure or GANTT chart.
It all boils down to this: There is no accepted, proven, documented, or foolproof process for developing Web sites or Web applications. You use what works, and what works you glean from experience. We certainly don't think we have a patentable method, but we do have a lot of experience; and we know what has worked for us and our peers in the industry.
In writing this book, the goal was to spare the new project manager the pain of learning project management theories, processes, and terminology that would cause only confusion and frustration when they were applied to the Web development arena. We wanted to chronicle our experience and describe the methods and processes that have worked by showing them at work in real-world situations.
From the moment we embarked on this project, we decided that the best approach to recounting experiences was to be as lighthearted as possible without undermining the point of the lessons. We are the first to admit that project management for the Web, or any industry for that matter, is a pretty dry topic. We hope that a little humor mixed into the content will keep the material engaging. One thing we've learned from our experiences as project managers is that you must maintain a sense of humor--without it you will lose the ability to lead effectively, and your life at work will be tedious. By the same token, why should reading a book about your profession be tedious? Simple answer: It shouldn't.
What's the use of a lot of theoretical mumbo jumbo without some illustrative material to prove or disprove the theory? In our early search for project management knowledge, we read many books that were long on theory but short on examples of real-life application. We wanted to see an example of a "force field analysis" in action. More to the point, we wanted to see an example of a "force field analysis" in action on a Web project in full meltdown mode with only two days to go before launch. While working our way through project after project, we discovered traditional methodologies that worked and many that did not. We found other methodologies and techniques that could be tweaked to fit into the Web environment. After a couple of years, it dawned on us that the hundreds of e-mail threads, scope documents, and project plans we had drafted contained our own project management body of knowledge. The basis for this body of knowledge was experience: the real-life projects we had managed.
As we interviewed colleagues and peers in the Web development industry for this book, we were provided with more case studies and stories that could be used to illustrate project management methods. We found that the experiences that resonated the most with colleagues were not the huge successes but the dismal failures. To be truly helpful and instructive, we have chosen to publish case studies and interviews that illustrate things that can and often do go wrong during a Web development project. In order to avoid any legal difficulties from sensitive corporations and their attorneys, we have fictionalized the stories recounted here and changed the names to protect the not-so-innocent. But be assured: The stories herein are all based on real-life events; we couldn't have made up some of this stuff if we tried.
This book was written for people who are new to the project manager role in the Web development industry. Real Web Project Management will provide those of you who come to the role from more specialized expertise, such as programming or design, with an introduction to the world of Web development from a manager's or generalist's perspective. We also hope the book will provide a resource for fresh ideas and inspiration to veteran Web project managers who may recognize themselves in some of the case studies and situations described in the book.
Through frontline experience and during the many interviews conducted for this book, it became crystal clear that the role of the project manager in the Web development industry has come to be considered indispensable. This is true for both interactive agencies and internal Web development or IT departments. Web project management has become a crucial success factor for a huge variety of organizations. Having worked with many unfortunate companies that lack solid project management practices, we believe that reading this book will be worth your time. Please enjoy it, and send any feedback to feedback@realwebprojects.com.
Abigail Rudner is a Web design consultant and trainer. The principle creative of her design company, BIG FUN Designs, Abigail and her team produce illustrative content for a wide range of multimedia and print projects. She has worked with top clients including Levi's, Wells Fargo, Dow Jones, America Online, Apple Computers, and Microsoft Press. This is her first book for Peachpit Press.]]>
Macromedia Flash MX H.O.T. covers all of the most important new features of Macromedia Flash MX, beginning with projects that focus on the MX interface, drawing and color tools, animation basics, tweening, symbols and instances, bitmaps, and more. As the projects progress, you'll tackle more complex techniques, such as working with movie clips, text, sound, and video. The latter part of the book addresses publishing and managing Macromedia Flash MX content, as well as how to create content by integrating other software into Macromedia Flash MX. If you're looking for an intelligent, approachable guide for learning Macromedia's latest version of Flash, you'll find lynda.com's Hands-On Training your e-ticket to Macromedia Flash MX expertise!
]]>The update to this best-selling book focuses specifically on using Photoshop 7 and ImageReady 7 for the Web with guided, tutorial-based lessons and exercises that have been developed and tested in Lynda Weinman's lynda.com digital arts training center. Each lesson contains extensive background information designed to help you understand the process as well as the particular exercise. You'll also learn how to create Photoshop rollovers, animations, image maps, transparency, layer styles, automation techniques, and more. If you're a beginning to intermediate Web designer, or a Photoshop user who is looking for a great tool to create graphics for the Web, this book has exactly what you've been looking for!
]]>
Writing Assignments provide a flexible structure and help students practice writing strategies and make connections between familiar and new writing strategies. Readings provide a variety of approaches to literacy and encourage students to think creatively and innovatively about how they and others define “education” and “literacy.” Included are narratives, analytical pieces, and essays.
College students wanting to improve their writing skills.
]]>
About This Book: Approaches and Assignments
“Reading: Words and Images”
“Getting” reading
Reading questions
Strategic reading
Reading images
Assignments
“Learning from Self” Assignments
Expectations and Experiences
Influencing Your Literacy Development
The Purposes of Schooling
Why Are You Here?
“Your” Campus
Your Literacy History and Its Significance
Your Literacy Development
“Learning from Others” AssignmentsWhat’s the Purpose of Education and Literacy
Literacy Practices and Schooling
Testing Definitions: Dominant and Vernacular Literacies
What Counts as “Learning” and for Whom?
How Is Literacy/Education Defined by You and by Others?
Community Literacies
“Learning Through Research” AssignmentsDebating the Purpose of School
Representing the College Experience
Designing Assessments
What Counts, for What, and Who Says?
Analyzing Literacy Experiences
Positive Learning Experiences
What’s Taught and Why
What Counts, for What, and Who Says?
Observing Literacy Practices
“Speaking Out, Joining In, Talk Back” Assignment
Readings About Uses of Learning:
David Barton and Mary Hamilton. “Literacy Practices”
bell hooks. “Engaged Pedagogy”
Paolo Freire. “The Banking Concept of Education”
Theodore Sizer. “What High School Is”
Readings About Learners:
David Barton and Mary Hamilton. “How They’ve Fared in Education: Harry’s Literacy Practices”
Lorene Cary. From Black Ice.
Mark Edmundson. “On the Uses of a Liberal Education I: As lite entertainment for bored college students.”
Andrea Fishman. “Becoming Literate: A Lesson from the Amish”
June Jordan. “Don’t Nobody Mean More to Me Than You