Register your product to gain access to bonus material or receive a coupon.
IT Architecture Toolkit
- By Jane Carbone
- Published May 10, 2004 by Pearson.
Book
- Sorry, this book is no longer in print.
Description
- Copyright 2004
- Dimensions: 7" x 9-1/4"
- Pages: 256
- Edition: 1st
- Book
- ISBN-10: 0-13-147379-4
- ISBN-13: 978-0-13-147379-9
Information is the lifeblood of most organizations. In fact, in many cases information is not just critical to the business - it IS the business. Organizations struggling with the fallout from today's economy have a heightened need for enterprise architecture the set of IT plans that describes how all parts of the IT infrastructure need to behave to support the organizations needs. Urgent cost-containment issues, consolidations, productivity pressures and ebusiness integration all demand solutions. This book will help you master the vital skills needed to plan how data is collected, how data should efficiently flow through your organization, and how data is transformed into information can your business can use. Learn from Ms. Carbone's decades of experience and proven approaches to better understand and implement enterprise architecture.
Extras
Related Articles
Putting the "I" Back in IT Planning
Ten Signs of Enterprise Entropy (or How to Tell If Your Enterprise Architecture Needs an Overhaul)
Sample Content
Downloadable Sample Chapter
Table of Contents
Preface.
Frequently Asked Questions.
Acknowledgments.
About The Author.
Introduction.
The Role of IT Planning.
Four Mini Case Studies-Best (and Worst) Practices.
Introducing the Enterprise Architecture Toolkit.
Getting Started. Components of an Enterprise Architecture.
A Comparison of the Toolkit and the Zachman Framework.
Critical Success Factors.
A Word about Integration.
How This Book Is Organized.
Connecting Architecture to the Business.
The Business Framework.
Describing the Business Current State-Collecting Key Facts.
Suggested Exercise.
Another Approach to Describing the Current State.
Analyzing the Business Current State.
Using Assessment Indicators.
Environmental Scan.
Suggested Exercise.
Using Process Flows.
Constructing the Business Target State.
Using Assessment Indicators.
Using Process Flows.
Digging Down.
Suggested Exercise.
Analyzing the Target State-Identifying Gaps and Opportunities.
Analyze the Target State.
First Approach.
Second Approach.
Suggested Exercise.
Integration.
Principles.
The IT (Architecture) Framework.
Defining Principles.
CDCo IT Principles.
Suggested Exercise.
Architecture Models.
Setting the Context for Architecture Models.
Ground Rules For Modeling.
Rule #1 Agree on a set of standard components.
Rule #2 Use a standard representation scheme.
Rule #3 Set a scope.
Rule #4 Determine the level of detail.
Rule #5 Define the state to be modeled.
Rule #6 Define the environment.
Building Architecture Models.
Level 0 Current State Model.
Considerations for Assessing Current State Architecture.
Level 0 Target State Model.
Architecture Strategies.
Level 1 Model.
Level n Models.
Suggested Exercise.
Architecture-Based Logical Models.
Translating Architecture to Conceptual Data Model.
Inventory.
Set a Scope.
Determine the Level of Detail.
Define the State.
Define the Environment.
Agree on a Format.
Suggested Exercise.
Standards.
Ground Rules for Setting Standards.
Establish Ownership.
Define the State.
Define the Environment.
Define the Level of Detail.
Setting Function/Application Standards.
Selecting Technology Standards.
Setting People Standards.
Setting Data Standards.
The Good.
The Bad.
The Ugly.
The Payoff.
Then and Now.
Some Good Examples.
Suggested Exercise.
Integration-Again.
Projects.
The Framework for Implementation.
Translating Architecture to Projects.
Identifying Architecture Projects.
Selecting Architecture Projects.
Data-Driven Approach to Project Selection.
Apply Viability Criteria.
Suggested Exercise.
Six Strategies for Containing Project Scope.
First Things First.
Use It or Lose It.
No Data before Its Time.
Smaller Is Better.
Just in Time.
Something New under the Sun.
The Project Brief.
Suggested Exercise.
Summary.
Establishing Metrics.
Measuring Architecture Effectiveness.
Setting Business Objectives.
Setting Project Objectives.
Setting Architecture Objectives.
Measuring Architecture Value.
Benchmark Data.
Sample Data.
Suggested Exercise.
Presenting the Plan for Buy-in.
Gaining Executive Support.
Creating a Presentation-Level Architecture Model.
Gaining Support from IT.
Suggested Exercise.
Compliance and Other Key Processes.
Architecture Governance Process.
Architecture Development Process.
When Should Architecture Be Developed?
Where Is the Architecture?
SDLC Process.
People.
Human Resources Issues for Architecture.
Evaluating HR Practices for the Architecture Team.
Staffing the Architecture Team.
Key Architecture Roles.
Data Management Roles.
Organization Structure.
Putting It Together.
A Final Word.
Business Framework Interview Outlines.
Group 1 Questions.
Group 2 Questions.
Group 3 Questions.
Business Framework Data Collection Documents.
Architecture Data Collection Documents.
Sample Architecture Principles.
Enterprise IT Principles.
Example Architecture Strategies.
Application Development Strategies.
Data Management Strategies.
Technology Strategies.
Example Target Application Architecture Patterns.
Estimating IT Work Effort for Projects.
Sample Scale for Estimating IT Effort.
Add New Code.
Change Script-Wording-Only.
Create New List.
Modify Existing Script.
Add New Code-Code Contains Intelligence Used by Applications.
Fix Small Bug.
Create New Report.
Create Customer List.
Modify Existing Applications-More Than One Module.
Add New Function and Interfaces.
Reorganize Work across Functions-Existing and New.
New Process, Applications, Data Store, and Cross-Function Data Movement.
Sample Current Architecture Cost Data Collection.
Current Cost of Projects Survey.
Sample Job Descriptions.
Data Steward.
Key Functions.
Expected Outputs.
Key Skills/Knowledge.
Data Architect.
Key Functions.
Expected Outputs.
Key Skills/Knowledge.
Data Acquisition.
Key Functions.
Expected Outputs.
Key Skills/Knowledge.
Common Data Services.
Key Functions.
Expected Outputs.
Key Skills/Knowledge.
Data Architecture Associate.
Key Functions.
Expected Outputs.
Key Skills/Knowledge.
Enterprise Architecture Toolkit: 3-Day Workshop.
Course Description.
Course Overview.
Target Audience.
Course Approach.
Course Outline.
Course Logistics.
Conducting Enterprise Architecture Assessment: 2-Day Workshop.
Course Description.
Course Overview.
Target Audience.
Course Approach.
Course Objectives.
Course Outline.
Course Logistics.
Index.
Preface
There were two factors that motivated me to write this book. One was that, while those of us who were data geeks were always passionate about business information, our opinions were not always popular. Today, meaningful, accurate information is the lifeblood of most organizations. In fact, in many cases, information is not just critical to the business-it is the business. Therefore, the need to plan how data is collected, flows through the organization, and is transformed into information the business can access, is vital. That need is increasingly recognized, not only by CIOs, but also by CEOs and even by the non-IT world at large. I was pleasantly surprised to read the following in an unlikely source:
Halfway through the last century, information became a thing. It became a commodity, a force-a quantity to be measured and analyzed. It's what our world runs on. Information is the gold and the fuel. (James Glieck, "Bit Player," The New York Times Magazine, December 30, 2001)
The second factor that motivated me to write this book was that, just as a converted smoker becomes overly eager about the smoking habits of those around him, I have had my own religious experience. Having been honed (some would say charred) on the altar of architecture, I am eager to share both my suffering and my successes. Having learned many lessons the hard way, I am anxious to help you benefit from those lessons.
This book, therefore, is a very practical guide to enterprise architecture. Many fine minds have addressed architecture theory from the podium and the bookshelf. The purpose of this book is to help architects, IT planners, and analysts find ways to implement those theories, and to spare you as much pain as possible in the process.
Frequently Asked Questions1. Q. Is this just more theory?
A. No. The Toolkit is very practical-it is based on our learnings as chief architects and consultants (and in both cases, compensation was determined by success).
2. Q. How can you ensure that business needs are addressed in the architecture?
A. Having wrestled with this problem, we developed a business framework and methods for translating business needs to architecture outputs. The Toolkit also addresses financial considerations and measurement development to tightly link architecture with the business.
3. Q. How does this approach relate to the Zachman Framework for Enterprise Architecture?
A. The Toolkit architecture framework produced by our company, infomajic, is consistent with, but simpler than, the Zachman Framework. It focuses on the upper left-hand rows and provides methods for filling in the cells. It also addresses strategies for implementing target architecture. The Toolkit is very practical-it's based on experience. We'll do a more complete comparison with the Zachman Framework a little later.
4. Q. How do you create architecture outputs?
A. We discuss what the critical outputs are-principles, models, inventory, and standards-and include specific methods for developing them. Examples and exercises allow you to practice using them.
A. Yes. The Toolkit includes an implementation framework, which addresses strategies and practices for successfully gaining business and IT buy-in, and includes descriptions of key architecture processes and roles.
6. Q. How can you translate conceptual architecture into reality?
A. The Toolkit includes a step-by-step approach to translating architecture into manageable projects-how to identify, select, and downsize architecture projects.
A. The Toolkit includes descriptions of key architecture roles.
8. Q. How can you measure/cost justify architecture?
A. The Toolkit addresses financial considerations and measurement development.