rent-now

Rent More, Save More! Use code: ECRENTAL

5% off 1 book, 7% off 2 books, 10% off 3+ books

9780201708479

E-Business and Is Solutions: An Architectural Approach to Business Problems and Opportunities

by
  • ISBN13:

    9780201708479

  • ISBN10:

    0201708477

  • Format: Paperback
  • Copyright: 2000-09-01
  • Publisher: Addison-Wesley Professional
  • Purchase Benefits
List Price: $34.95

Summary

As all business becomes e-Business, managers and IT professionals must implement IT architectures that are effective, flexible, resilient enough to handle relentless change, growth, and acceleration -- or risk becoming uncompetitive virtually overnight. Written for both managers and technical professionals, E-Business and IS Solutions: An Architectural Approach to Business Problems and Opportunities offers complete, high-level guidance for defining and implementing IT architectures that enable e-Business instead of standing in its way. The book demonstrates the benefits of an architecture-based approach to e-business, and shows managers how to design effective e-Business architectures and infrastructure for their organizations. William J. Buffam reviews the core principles and practices associated with applying e-Business technology for competitive advantage, walks through each key activity needed to define an effective e-Business architecture, and presents powerful solutions for unique challenges of designing IT infrastructure for e-Business applications. For all managers and IT professionals involved with e-Business strategy, implementation, or IT architecture, including architects, analysts, strategists, project managers, developers, and many others.

Table of Contents

Preface xv
Acknowledgments xxi
PART I SETTING THE SCENE FOR ARCHITECTURAL SOLUTION BUILDING 1(62)
Characteristics of E-Business
3(4)
What do we mean by ``e-business''?
3(3)
What are the effects of e-business on architectural IS solution building?
6(1)
The Essence of ``Architecture''
7(24)
The evolution of information systems
7(5)
The legacy of isolated systems
7(1)
The emergence of standards
8(4)
The need for IS architectures
12(1)
``Architecture'' and the original architects
12(2)
Why do we need architecture in information systems?
14(5)
Fundamental requirements
14(2)
Enabling requirements
16(3)
``Architecture'' in information systems---what is it?
19(9)
The common-component sense of ``architecture''
20(2)
The design sense of ``architecture''
22(4)
The blueprinting sense of ``architecture''
26(1)
The framework sense of ``architecture''
27(1)
Summary of the ``architectural way''
28(3)
Object-Oriented Methods and Architectural Solution Building
31(18)
What is object orientation all about?
31(7)
Object orientation compared with functional decomposition
32(2)
Models for architectural solution building
34(2)
Modeling and requirements gathering
36(2)
Object-oriented development environments
38(1)
Object orientation and the ``architectural way''
38(3)
Benefits of an object-oriented approach
41(3)
Narrowing the semantic gap
41(1)
Object orientation and good design
42(1)
Object orientation at the source code level
43(1)
Objects and components
44(1)
Pitfalls of an object-oriented approach
44(2)
Large, complex enterprises
44(1)
Inappropriate mindset
45(1)
OO benefits without OO tools
46(1)
Where to find more information
47(2)
Project Scope Considerations
49(14)
Large-scale projects
50(3)
Characteristics of large-scale projects
51(1)
Critical success factors for large-scale projects
51(2)
Narrow-scope projects
53(1)
Characteristics of narrow-scope projects
53(1)
Narrowing the scope to produce repeatable solutions
54(1)
Trade-offs in project scope
54(4)
A scope trade-off illustration
56(1)
Scope, commitment, and risk
57(1)
Impact of varying scope on architecture stages
58(3)
The e-business paradigm
58(1)
The Reengineering paradigm
59(1)
The incremental improvement paradigm
60(1)
Summary of project paradigms
60(1)
Where to find more information
61(2)
PART II THE SEVEN-STAGE SOLUTION-BUILDING PROCESS 63(144)
Introduction
65(10)
Overview of the architectural solution-building process
65(2)
Architectural solution-building team
67(3)
Stages and participants
68(1)
Team roles
68(2)
Team size and dynamics
70(1)
Global architectural principles
70(5)
Business Modeling
75(26)
Business modeling in the context of the total process
78(3)
Relation to other stages
78(2)
Relation to the OO model set
80(1)
Participants
80(1)
Information sources for the business modeling stage
81(2)
Existing written material
82(1)
Team experience and expertise
82(1)
Interviews
82(1)
Brainstorming workshops
83(1)
Business strategy
83(3)
Enterprise mission and objectives
83(2)
Business environment
85(1)
The business model
86(11)
Content of the business model
86(2)
Tools for developing the business model
88(1)
Adjusting the focus---setting the scope
89(1)
Where we've been, and where we're going
90(1)
Reuse and the business model
91(1)
Models for reengineering
92(2)
Models for e-business
94(1)
Models for incremental improvement
95(2)
Applying the business model
97(2)
Alignment of the IS solution with business objectives
97(1)
Organizational impact of the business model
98(1)
Models as monitors of scope creep
98(1)
Where was the ``architecture''?
99(2)
IS Modeling
101(26)
IS modeling in the context of the total process
102(4)
Relation to other stages
102(2)
Relation to the OO model set
104(1)
Participants
104(2)
IS Strategy
106(2)
Five-Era View
106(2)
Developing the IS Strategy
108(5)
Guidelines for business-driven IS strategy
108(1)
Guidelines for technology-driven IS strategy
109(1)
Content of the IS strategy
109(4)
The IS Model
113(11)
The IS model for large-scope projects
114(2)
The reuse principle and the IS Model
116(2)
Content of the IS model
118(3)
The IS model for narrow-scope projects
121(3)
Forks in the road: solution alternatives
124(1)
The IS real-object model
124(1)
Where was the ``architecture''?
125(2)
Current IS Analysis
127(20)
Overview
127(1)
Current IS analysis in the context of the total process
128(2)
Relation to other stages
128(2)
Participants
130(1)
Introducing the architectural framework
130(3)
Conducting the current IS inventory
133(2)
Inventory of IS components
135(6)
Business solution applications
135(1)
Solution enablers
136(1)
Data
137(1)
Middleware integration software
137(1)
Operating platforms
138(1)
Hardware platforms
138(1)
Network
139(1)
Development environments, tools, and methodologies
139(1)
Management enablers
140(1)
Security enablers
141(1)
IS Organization
141(1)
Assessment of current IS environment
141(3)
Functionality
142(1)
Non-functional attributes
143(1)
Human-resource capabilities
144(1)
Outsourced services
144(1)
Where was the ``architecture''?
144(3)
IS Architecture Planning
147(30)
IS architecture planning in the context of the total process
147(3)
Relation to other stages
147(2)
Relation to the OO model set
149(1)
Participants
149(1)
Architectural principles
150(7)
How are principles defined?
151(3)
Guidelines for writing principles
154(3)
Defining architecture models
157(4)
Forks in the road: solution alternatives
158(1)
Architecture models for object-oriented development environments
158(2)
Architecture models for non--object-oriented development environments
160(1)
Defining supporting IT infrastructure
161(3)
Technology evaluation criteria and considerations
163(1)
Filling technology gaps
164(1)
Identifying hardware and software products
164(1)
IT infrastructure for e-business
164(11)
Environmental influences on e-business technology
165(2)
E-business technology: its responses to environmental demands
167(8)
Where was the ``architecture''?
175(1)
Where to find more information
176(1)
Implementation Planning
177(16)
Implementation planning in the context of the total process
177(2)
Relation to other stages
177(1)
Participants
178(1)
Identifying implementation options
179(1)
Preliminary analysis of implementation options
180(1)
Analyzing the implementation options
180(4)
Cost-benefit analysis
181(1)
Analyzing risks
182(2)
Analyzing organization impact
184(1)
Establishing a transition strategy
184(9)
Using a risk--benefit matrix
185(1)
Selecting short- and long-term priorities
185(1)
Diversifying risk
185(1)
Determining a transition sequence
186(2)
Building a business case and determining a transition strategy
188(2)
Where was the ``architecture''?
190(1)
Where to find more information
191(2)
Deployment
193(8)
Deployment in the context of the total process
193(2)
Relation to other stages
193(1)
Participants
194(1)
Deployment activities
195(2)
Project management
197(1)
Management tasks
197(1)
Feedback loops
198(1)
Where was the ``architecture''?
198(3)
Review
201(6)
The review stage in the context of the total process
201(3)
Participants
202(1)
Relation to other stages
203(1)
Reviewing projects
204(1)
Activities in the review stage
204(1)
Maintaining the IS architecture
205(2)
Ongoing maintenance
205(1)
Ongoing maintenance: reacting to change
205(1)
Scheduled maintenance
206(1)
Benefits of proper maintenance
206(1)
PART III LET'S GET PRACTICAL 207(26)
Enlisting Outside Help: the Role of Consultants
209(4)
Consultants for cross-enterprise leverage
209(2)
Consultants for technology expertise
211(1)
Consultants as project managers
211(1)
The bottom line on consultants
211(2)
Methodologies: Patterns for Solution Building
213(6)
What's in a methodology?
214(1)
Developing or acquiring a methodology
214(1)
Using a methodology in practice
215(4)
Pitfall 1: ``This stuff is easy!''
215(1)
Pitfall 2: You can't fly a Boeing 747 just by reading the manual
216(1)
Pitfall 3: Methodology bloat
217(2)
Practical Considerations in Conducting Solution Building
219(4)
Feedback loops and whirlpools
219(1)
Duration of solution building
220(1)
Architectural solution building and ongoing projects
220(3)
Allocating resources
221(1)
Integrating multiple projects
221(2)
Issues Concerning Reuse
223(10)
Benefits of reuse
223(1)
Reuse domains
224(1)
Source code
224(1)
Middleware
225(1)
Business logic
225(1)
Impediments to reuse
225(2)
Essential enablers of reuse
227(1)
Environmental drivers of reuse
228(1)
Sources of reusable artifacts
229(4)
Reusable artifacts from ongoing development
229(1)
Reusable artifacts from current IS assets
229(1)
Reusable artifacts from packaged software
229(1)
Reusable artifacts from the specialty
230(2)
Reusable artifacts from the specialty broker
232(1)
Epilogue: Take-Home Thoughts 233(4)
Bibliography and References 237(6)
Index 243

Supplemental Materials

What is included with this book?

The New copy of this book will include any supplemental materials advertised. Please check the title of the book to determine if it should include any access cards, study guides, lab manuals, CDs, etc.

The Used, Rental and eBook copies of this book are not guaranteed to include any supplemental materials. Typically, only the book itself is included. This is true even if the title states it includes any access cards, study guides, lab manuals, CDs, etc.

Rewards Program