E-Business and IS Solutions: An Architectural Approach to Business Problems and
William J. Buffam
- 出版商: Addison Wesley
- 出版日期: 2000-09-22
- 定價: $1,225
- 售價: 5.0 折 $613
- 語言: 英文
- 頁數: 256
- 裝訂: Paperback
- ISBN: 0201708477
- ISBN-13: 9780201708479
-
相關分類:
電子商務 E-commerce
立即出貨(限量) (庫存=1)
買這商品的人也買了...
-
$600The E-business Evolution (Paperback) -
$1,872Robots for Kids: Exploring New Technologies for Learning -
$790Integrating Your e-Business Enterprise -
$700Network Architecture & Design: A Field Guide for IT Consultants -
$525Technology Acquisition: Buying the Future of Your Business -
$700Managing IT as an Investment: Partnering for Success -
$640IT Web Services: A Roadmap for the Enterprise -
資訊架構學網站應用 (Information Architecture for the World Wide Web, 2/e)$680$537 -
Unix Application Migration Guide (Paperback)$2,010$1,910 -
數位邏輯設計 (Digital Design, 3/e)$580$568 -
鳥哥的 Linux 私房菜─基礎學習篇增訂版$560$504 -
2004 PC DIY 硬碟安裝、分割、調整、系統轉移$350$298 -
C 程式設計藝術 (C How to Program, 4/e)$780$702 -
C 語言教學手冊 第三版$620$484 -
$1,058Software Engineering: A Practitioner's Approach, 6/e -
最新 JavaScript 完整語法參考辭典 第三版$490$382 -
$299Technology Paradise Lost: Why Companies Will Spend Less to Get More from Information Technology (Hardcover) -
Linux 程式設計教學手冊$780$616 -
JavaServer Faces 互動式網站介面 (JavaServer Faces)$820$648 -
RFID 技術與應用$480$408 -
The End of Software : Transforming Your Business for the On Demand Future$1,170$1,112 -
$199The Business Guide to Selling Through Internet Auctions: A Proven Seven-Step Plan for Selling to Consumers and Other Businesses -
$1,584Cloudonomics, + Website: The Business Value of Cloud Computing (Hardcover) -
統計學，最強的商業武器－從買樂透到大數據，全都離不開統計學；不懂統計學，你就等著被騙吧！$320$253 -
50大商業思想家論壇：當代最具影響力 18 位大師談管理$360$324
相關主題
商品描述
Description
Developing IT architectures that enable e-Business: the practical, concise guide!
- Key high-level principles and guidelines for e-Business architecture.
- Covers every stage of the solution-building process: the activities involved and how they fit together.
- Why e-Business architectures are fundamentally different from anything that has come before.
William J. Buffam heads up the Unisys Architectural Center of Excellence in Malvern, Pennsylvania. A graduate of the University of Manchester, his perspective of information technology has been shaped by many years of endeavor as solutions architect, software engineer, technology specialist, manager, and educator. During leisure hours, you'll likely find him soaring high in the sky on his hang glider, keeping the world in proper architectural perspective. 
Table Of Contents
Preface.Acknowledgments.
I. SETTING THE SCENE FOR ARCHITECTURAL SOLUTION BUILDING.
1. Characteristics of E-Business. What Do We Mean by “E-Business” ?
What Are the Effects of E-Business on Architectural IS Solution Building?
What Are the Effects of E-Business on Architectural IS Solution Building?
2. The Essence of “Architecture.”
The Evolution of Information Systems.
“Architecture” and the Original Architects.
Why Do We Need Architecture in Information Systems?
“Architecture” in Information Systems — What Is It?
Summary of the “Architectural Way.”
The Legacy of Isolated Systems.
The Emergence of Standards.
The Need for IS Architectures.
The Emergence of Standards.
The Need for IS Architectures.
“Architecture” and the Original Architects.
Why Do We Need Architecture in Information Systems?
Fundamental Requirements.
Enabling Requirements.
Enabling Requirements.
“Architecture” in Information Systems — What Is It?
The Common-Component Sense of “Architecture.”
The Design Sense of “Architecture.”
The Blueprinting Sense of “Architecture.”
The Framework Sense of “Architecture.”
The Design Sense of “Architecture.”
The Blueprinting Sense of “Architecture.”
The Framework Sense of “Architecture.”
Summary of the “Architectural Way.”
3. Object-Oriented Methods and Architectural Solution Building.
What Is Object Orientation All About?
Object Orientation and the “Architectural Way.”
Benefits of an Object-Oriented Approach.
Objects and Components.
Pitfalls of an Object-Oriented Approach.
OO Benefits without OO Tools.
Where to Find More Information.
Object Orientation Compared with Functional Decomposition.
Models for Architectural Solution Building.
Modeling and Requirements Gathering.
Object-Oriented Development Environments.
Models for Architectural Solution Building.
Modeling and Requirements Gathering.
Object-Oriented Development Environments.
Object Orientation and the “Architectural Way.”
Benefits of an Object-Oriented Approach.
Narrowing the Semantic Gap.
Object Orientation and Good Design.
Object Orientation at the Source Code Level.
Object Orientation and Good Design.
Object Orientation at the Source Code Level.
Objects and Components.
Pitfalls of an Object-Oriented Approach.
Large, Complex Enterprises.
Inappropriate Mindset.
Inappropriate Mindset.
OO Benefits without OO Tools.
Where to Find More Information.
4. Project Scope Considerations.
Large-Scale Projects.
Narrow-Scope Projects.
Trade-Offs in Project Scope.
Impact of Varying Scope on Architecture Stages.
Where to Find More Information.
Characteristics of Large-Scale Projects.
Critical Success Factors for Large-Scale Projects.
Critical Success Factors for Large-Scale Projects.
Narrow-Scope Projects.
Characteristics of Narrow-Scope Projects.
Narrowing the Scope to Produce Repeatable Solutions.
Narrowing the Scope to Produce Repeatable Solutions.
Trade-Offs in Project Scope.
A Scope Trade-Off Illustration.
Scope, Commitment, and Risk.
Scope, Commitment, and Risk.
Impact of Varying Scope on Architecture Stages.
The E-Business Paradigm.
The Reengineering Paradigm.
The Incremental Improvement Paradigm.
Summary of Project Paradigms.
The Reengineering Paradigm.
The Incremental Improvement Paradigm.
Summary of Project Paradigms.
Where to Find More Information.
II. THE SEVEN-STAGE SOLUTION-BUILDING PROCESS.
5. Introduction.
Overview of the Architectural Solution-Building Process.
Architectural Solution-Building Team.
Global Architectural Principles.
Architectural Solution-Building Team.
Stages and Participants.
Team Roles.
Team Size and Dynamics.
Team Roles.
Team Size and Dynamics.
Global Architectural Principles.
6. Business Modeling.
Business Modeling in the Context of the Total Process.
Information Sources for the Business Modeling Stage.
Business Strategy.
The Business Model.
Applying the Business Model.
Where Was the “Architecture” ?
Relation to Other Stages.
Relation to the OO Model Set.
Participants.
Relation to the OO Model Set.
Participants.
Information Sources for the Business Modeling Stage.
Existing Written Material.
Team Experience and Expertise.
Interviews.
Brainstorming Workshops.
Team Experience and Expertise.
Interviews.
Brainstorming Workshops.
Business Strategy.
Enterprise Mission and Objectives.
Business Environment.
Business Environment.
The Business Model.
Content of the Business Model.
Tools for Developing the Business Model.
Adjusting the Focus — Setting the Scope.
Where We've Been, and Where We're Going.
Reuse and the Business Model.
Models for Reengineering.
Models for E-Business.
Models for Incremental Improvement.
Tools for Developing the Business Model.
Adjusting the Focus — Setting the Scope.
Where We've Been, and Where We're Going.
Reuse and the Business Model.
Models for Reengineering.
Models for E-Business.
Models for Incremental Improvement.
Applying the Business Model.
Alignment of the IS Solution with Business Objectives.
Organizational Impact of the Business Model.
Models as Monitors of Scope Creep.
Organizational Impact of the Business Model.
Models as Monitors of Scope Creep.
Where Was the “Architecture” ?
7. IS Modeling.
IS Modeling in the Context of the Total Process.
IS Strategy.
Developing the IS Strategy.
The IS Model.
The IS Real-Object Model.
Where Was the “Architecture” ?
Relation to Other Stages.
Relation to the OO Model Set.
Participants.
Relation to the OO Model Set.
Participants.
IS Strategy.
Five-Era View.
Developing the IS Strategy.
Guidelines for Business-Driven IS Strategy.
Guidelines for Technology-Driven IS Strategy.
Content of the IS Strategy.
Guidelines for Technology-Driven IS Strategy.
Content of the IS Strategy.
The IS Model.
The IS Model for Large-Scope Projects.
The Reuse Principle and the IS Model.
Content of the IS Model.
The IS Model for Narrow-Scope Projects.
Forks in the Road: Solution Alternatives.
The Reuse Principle and the IS Model.
Content of the IS Model.
The IS Model for Narrow-Scope Projects.
Forks in the Road: Solution Alternatives.
The IS Real-Object Model.
Where Was the “Architecture” ?
8. Current IS Analysis.
Overview.
Current IS Analysis in the Context of the Total Process.
Introducing the Architectural Framework.
Conducting the Current IS Inventory.
Inventory of IS Components.
Assessment of Current IS Environment.
Where Was the “Architecture” ?
Current IS Analysis in the Context of the Total Process.
Relation to Other Stages.
Participants.
Participants.
Introducing the Architectural Framework.
Conducting the Current IS Inventory.
Inventory of IS Components.
Business Solution Applications.
Solution Enablers.
Data.
Middleware Integration Software.
Operating Systems.
Hardware Platforms.
Network.
Development Environments, Tools, and Methodologies.
Management Enablers.
Security Enablers.
IS Organization.
Solution Enablers.
Data.
Middleware Integration Software.
Operating Systems.
Hardware Platforms.
Network.
Development Environments, Tools, and Methodologies.
Management Enablers.
Security Enablers.
IS Organization.
Assessment of Current IS Environment.
Functionality.
Non-Functional Attributes.
Human-Resource Capabilities.
Outsourced Services.
Non-Functional Attributes.
Human-Resource Capabilities.
Outsourced Services.
Where Was the “Architecture” ?
9. IS Architecture Planning.
IS Architecture Planning in the Context of the Total Process.
Architectural Principles.
Defining Architecture Models.
Defining Supporting IT Infrastructure.
IT Infrastructure for E-Business.
Where to Find More Information.
Relation to Other Stages.
Relation to the OO Model Set.
Participants.
Relation to the OO Model Set.
Participants.
Architectural Principles.
How Are Principles Defined?
Guidelines for Writing Principles.
Guidelines for Writing Principles.
Defining Architecture Models.
Forks in the Road: Solution Alternatives.
Architecture Models for Object-Oriented Development Environments.
Architecture Models for Non-Object-Oriented Development Environments.
Architecture Models for Object-Oriented Development Environments.
Architecture Models for Non-Object-Oriented Development Environments.
Defining Supporting IT Infrastructure.
Technology Evaluation Criteria and Considerations.
Filling Technology Gaps.
Identifying Hardware and Software Products.
Filling Technology Gaps.
Identifying Hardware and Software Products.
IT Infrastructure for E-Business.
Environmental Influences on E-Business Technology.
E-Business Technology: Its Responses to Environmental Demands.
Where Was the “Architecture” ?
E-Business Technology: Its Responses to Environmental Demands.
Where Was the “Architecture” ?
Where to Find More Information.
10. Implementation Planning.
Implementation Planning in the Context of the Total Process.
Identifying Implementation Options.
Preliminary Analysis of Implementation Options.
Analyzing the Implementation Options.
Establishing a Transition Strategy.
Where Was the “Architecture” ?
Where to Find More Information.
Relation to Other Stages.
Participants.
Participants.
Identifying Implementation Options.
Preliminary Analysis of Implementation Options.
Analyzing the Implementation Options.
Cost-Benefit Analysis.
Analyzing Risks.
Analyzing Organizational Impact.
Analyzing Risks.
Analyzing Organizational Impact.
Establishing a Transition Strategy.
Using a Risk-Benefit Matrix.
Selecting Short- and Long-Term Priorities.
Diversifying Risk.
Determining a Transition Sequence.
Building a Business Case and Determining a Transition Strategy.
Selecting Short- and Long-Term Priorities.
Diversifying Risk.
Determining a Transition Sequence.
Building a Business Case and Determining a Transition Strategy.
Where Was the “Architecture” ?
Where to Find More Information.
11. Deployment.
Deployment in the Context of the Total Process.
Deployment Activities.
Project Management.
Where Was the “Architecture” ?
Relation to Other Stages.
Participants.
Participants.
Deployment Activities.
Project Management.
Management Tasks.
Feedback Loops.
Feedback Loops.
Where Was the “Architecture” ?
12. Review.
The Review Stage in the Context of the Total Process.
Reviewing Projects.
Maintaining the IS Architecture.
Participants.
Relation to Other Stages.
Relation to Other Stages.
Reviewing Projects.
Activities in the Review Stage.
Maintaining the IS Architecture.
Ongoing Maintenance.
Ongoing Maintenance: Reacting to Change.
Scheduled Maintenance.
Benefits of Proper Maintenance.
Ongoing Maintenance: Reacting to Change.
Scheduled Maintenance.
Benefits of Proper Maintenance.
III. LET'S GET PRACTICAL.
13. Enlisting Outside Help: The Role of Consultants.
Consultants for Cross-Enterprise Leverage.
Consultants for Technology Expertise.
Consultants as Project Managers.
The Bottom Line on Consultants.
Consultants for Technology Expertise.
Consultants as Project Managers.
The Bottom Line on Consultants.
14. Methodologies: Patterns for Solution Building.
What's in a Methodology?
Developing or Acquiring a Methodology.
Using a Methodology in Practice.
Developing or Acquiring a Methodology.
Using a Methodology in Practice.
Pitfall 1: “This Stuff Is Easy!”
Pitfall 2: You Can't Fly a Boeing 747 Just by Reading the Manual.
Pitfall 3: Methodology Bloat.
Pitfall 2: You Can't Fly a Boeing 747 Just by Reading the Manual.
Pitfall 3: Methodology Bloat.
15. Practical Considerations in Conducting Solution Building.
Feedback Loops and Whirlpools.
Duration of Solution Building.
Architectural Solution Building and Ongoing Projects.
Duration of Solution Building.
Architectural Solution Building and Ongoing Projects.
Allocating Resources.
Integrating Multiple Projects.
Integrating Multiple Projects.
16. Issues Concerning Reuse.
Benefits of Reuse.
Reuse Domains.
Impediments to Reuse.
Essential Enablers of Reuse.
Environmental Drivers of Reuse.
Sources of Reusable Artifacts.
Reuse Domains.
Source Code.
Middleware.
Business Logic.
Middleware.
Business Logic.
Impediments to Reuse.
Essential Enablers of Reuse.
Environmental Drivers of Reuse.
Sources of Reusable Artifacts.
Reusable Artifacts from Ongoing Development.
Reusable Artifacts from Current IS Assets.
Reusable Artifacts from Packaged Software.
Reusable Artifacts from the Specialty Store.
Reusable Artifacts from the Specialty Broker.
Reusable Artifacts from Current IS Assets.
Reusable Artifacts from Packaged Software.
Reusable Artifacts from the Specialty Store.
Reusable Artifacts from the Specialty Broker.
Epilogue: Take-Home Thoughts.
Bibliography and References.
Index. 0201708477T04062001
商品描述(中文翻譯)
描述
開發能夠實現電子商務的IT架構：一個實用、簡明的指南！
- 電子商務架構的關鍵高層原則和指南。
- 涵蓋解決方案構建過程的每個階段：涉及的活動以及它們如何相互配合。
- 為什麼電子商務架構與以往任何事物都有根本的不同。
隨著所有業務都變成電子商務，管理人員和IT專業人員必須實施有效、靈活、具有彈性的IT架構，以應對無情的變化、增長和加速，否則可能在一夜之間失去競爭力。《電子商務和IS解決方案：一種面向業務問題和機遇的架構方法》針對管理人員和技術專業人員，提供了完整的高層指導，用於定義和實施能夠實現電子商務的IT架構，而不是阻礙它。本書展示了基於架構的電子商務方法的好處，並向管理人員展示如何為其組織設計有效的電子商務架構和基礎設施。William J. Buffam回顧了應用電子商務技術獲得競爭優勢的核心原則和實踐，逐步介紹了定義有效電子商務架構所需的每個關鍵活動，並提供了設計電子商務應用的IT基礎設施的獨特挑戰的強大解決方案。適用於所有參與電子商務戰略、實施或IT架構的管理人員和IT專業人員，包括架構師、分析師、策略師、項目經理、開發人員等。
William J. Buffam是賓夕法尼亞州馬爾文市Unisys Architectural Center of Excellence的負責人。他畢業於曼徹斯特大學，多年來作為解決方案架構師、軟件工程師、技術專家、經理和教育工作者的努力，塑造了他對信息技術的觀點。在閒暇時間，你可能會發現他在他的滑翔翼上高飛，保持世界的正確架構觀點。
目錄
前言。
致謝。
第一部分：為架構解決方案構建營造氛圍。
1. 電子商務的特點。
2. “架構”的本質。
3. 面向對象的方法和架構解決方案構建。
