E-Business and IS Solutions: An Architectural Approach to Business Problems and
暫譯: 電子商務與資訊系統解決方案：針對商業問題的架構方法

William J. Buffam

E-Business and IS Solutions: An Architectural Approach to Business Problems and
  • 出版商: Addison Wesley
  • 出版日期: 2000-09-22
  • 定價: $1,225
  • 售價: 5.0 折 $613
  • 語言: 英文
  • 頁數: 256
  • 裝訂: Paperback
  • ISBN: 0201708477
  • ISBN-13: 9780201708479
  • 相關分類: 電子商務 E-commerce

    • 立即出貨(限量) (庫存=1)

買這商品的人也買了...

商品描述


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.
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.

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.

Back to Top


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?

2. The Essence of “Architecture.”
The Evolution of Information Systems.
The Legacy of Isolated Systems.
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.

“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.”

Summary of the “Architectural Way.”

3. Object-Oriented Methods and Architectural Solution Building.
What Is Object Orientation All About?
Object Orientation Compared with Functional Decomposition.
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.

Objects and Components.
Pitfalls of an Object-Oriented Approach.
Large, Complex Enterprises.
Inappropriate Mindset.

OO Benefits without OO Tools.
Where to Find More Information.

4. Project Scope Considerations.
Large-Scale Projects.
Characteristics of 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.

Trade-Offs in Project Scope.
A Scope Trade-Off Illustration.
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.

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.
Stages and Participants.
Team Roles.
Team Size and Dynamics.

Global Architectural Principles.

6. Business Modeling.
Business Modeling in the Context of the Total Process.
Relation to Other Stages.
Relation to the OO Model Set.
Participants.

Information Sources for the Business Modeling Stage.
Existing Written Material.
Team Experience and Expertise.
Interviews.
Brainstorming Workshops.

Business Strategy.
Enterprise Mission and Objectives.
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.

Applying the Business Model.
Alignment of the IS Solution with Business Objectives.
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.
Relation to Other Stages.
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.

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 IS Real-Object Model.
Where Was the “Architecture” ?

8. Current IS Analysis.
Overview.
Current IS Analysis in the Context of the Total Process.
Relation to Other Stages.
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.

Assessment of Current IS Environment.
Functionality.
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.
Relation to Other Stages.
Relation to the OO Model Set.
Participants.

Architectural Principles.
How Are Principles Defined?
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.

Defining Supporting IT Infrastructure.
Technology Evaluation Criteria and Considerations.
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” ?

Where to Find More Information.

10. Implementation Planning.
Implementation Planning in the Context of the Total Process.
Relation to Other Stages.
Participants.

Identifying Implementation Options.
Preliminary Analysis of Implementation Options.
Analyzing the Implementation Options.
Cost-Benefit Analysis.
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.

Where Was the “Architecture” ?
Where to Find More Information.

11. Deployment.
Deployment in the Context of the Total Process.
Relation to Other Stages.
Participants.

Deployment Activities.
Project Management.
Management Tasks.
Feedback Loops.

Where Was the “Architecture” ?

12. Review.
The Review Stage in the Context of the Total Process.
Participants.
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.

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.

14. Methodologies: Patterns for Solution Building.
What's in a Methodology?
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.


15. Practical Considerations in Conducting Solution Building.
Feedback Loops and Whirlpools.
Duration of Solution Building.
Architectural Solution Building and Ongoing Projects.
Allocating Resources.
Integrating Multiple Projects.


16. Issues Concerning Reuse.
Benefits of Reuse.
Reuse Domains.
Source Code.
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.


Epilogue: Take-Home Thoughts.
Bibliography and References.
Index. 0201708477T04062001


Back to Top

商品描述(中文翻譯)

描述

開發能夠支持電子商務的 IT 架構：實用且簡明的指南！
- 電子商務架構的關鍵高層原則和指導方針。
- 涵蓋解決方案構建過程的每個階段：涉及的活動及其如何相互配合。
- 為什麼電子商務架構與以往的任何事物根本不同。

隨著所有業務轉向電子商務，管理者和 IT 專業人員必須實施有效、靈活且具有韌性的 IT 架構，以應對不斷的變化、增長和加速，否則將面臨幾乎一夜之間失去競爭力的風險。電子商務與資訊系統解決方案：一種針對商業問題和機會的架構方法 為管理者和技術專業人員提供了完整的高層指導，幫助他們定義和實施能夠支持電子商務的 IT 架構，而不是阻礙其發展。本書展示了基於架構的方法對電子商務的好處，並向管理者展示如何為其組織設計有效的電子商務架構和基礎設施。William J. Buffam 回顧了與應用電子商務技術以獲取競爭優勢相關的核心原則和實踐，逐步介紹了定義有效電子商務架構所需的每個關鍵活動，並提出了針對電子商務應用設計 IT 基礎設施的獨特挑戰的強大解決方案。適合所有參與電子商務策略、實施或 IT 架構的管理者和 IT 專業人員，包括架構師、分析師、策略師、專案經理、開發人員等。

William J. Buffam 擔任位於賓夕法尼亞州馬爾文的 Unisys 架構卓越中心負責人。他是曼徹斯特大學的畢業生，作為解決方案架構師、軟體工程師、技術專家、經理和教育者，他對資訊技術的看法受到多年努力的影響。在閒暇時間，您可能會發現他在滑翔翼上高高飛翔，保持世界的正確架構視角。

目錄

- 前言
- 致謝

I. 為架構解決方案構建設定場景
1. 電子商務的特徵
- 我們所說的「電子商務」是什麼？
- 電子商務對架構資訊系統解決方案構建的影響？

2. 「架構」的本質
- 資訊系統的演變
- 隔離系統的遺產
- 標準的出現
- 對資訊系統架構的需求
- 「架構」及其原始架構師
- 為什麼我們需要資訊系統中的架構？
- 基本要求
- 啟用要求
- 資訊系統中的「架構」——它是什麼？
- 「架構」的共同組件意義
- 「架構」的設計意義
- 「架構」的藍圖意義
- 「架構」的框架意義
- 「架構方式」的總結

3. 物件導向方法與架構解決方案構建
- 物件導向是什麼？
- 物件導向與功能分解的比較
- 架構解決方案構建的模型
- 建模與需求收集
- 物件導向開發環境
- 物件導向與「架構方式」
- 物件導向方法的好處
- 縮小語義差距
- 物件導向與良好設計
- 物件導向在源代碼層級
- 物件與組件
- 物件導向方法的陷阱
- 大型、複雜的企業
- 不當的心態
- 沒有物件導向工具的物件導向好處
- 更多資訊的來源

4. 專案範圍考量
- 大型專案
- 大型專案的特徵
- 大型專案的關鍵成功因素
- 窄範圍專案
- 窄範圍專案的特徵
- 縮小範圍以產生可重複的解決方案
- 專案範圍的權衡
- 範圍權衡示例
- 範圍、承諾與風險
- 變化範圍對架構階段的影響
- 電子商務範式
- 再造範式
- 漸進改進範式
- 專案範式的總結
- 更多資訊的來源

II. 七階段解決方案構建過程
5. 介紹
- 架構解決方案構建過程概述
- 架構解決方案構建團隊
- 階段與參與者
- 團隊角色
- 團隊規模與動態
- 全球架構原則

6. 商業建模
- 總過程中的商業建模
- 與其他階段的關係
- 與物件導向模型集的關係
- 參與者
- 商業建模階段的信息來源
- 現有書面材料
- 團隊經驗與專業知識
- 訪談
- 腦力激盪工作坊
- 商業策略
- 企業使命與目標
- 商業環境
- 商業模型
- 商業模型的內容
- 開發商業模型的工具
- 調整焦點——設定範圍
- 我們的過去與未來
- 重用與商業模型
- 再造模型
- 電子商務模型
- 漸進改進模型
- 應用商業模型
- 資訊系統解決方案與商業目標的對齊
- 商業模型對組織的影響
- 模型作為範圍蔓延的監控工具
- 「架構」在哪裡？

7. 資訊系統建模
- 總過程中的資訊系統建模
- 與其他階段的關係
- 與物件導向模型集的關係
- 參與者
- 資訊系統策略
- 五時代觀
- 發展資訊系統策略
- 商業驅動的資訊系統策略指導方針
- 技術驅動的資訊系統策略指導方針
- 資訊系統策略的內容
- 資訊系統模型
- 大範圍專案的資訊系統模型
- 重用原則與資訊系統模型
- 資訊系統模型的內容
- 窄範圍專案的資訊系統模型
- 分岔路口：解決方案選擇
- 資訊系統實體模型
- 「架構」在哪裡？

8. 當前資訊系統分析
- 概述
- 總過程中的當前資訊系統分析
- 與其他階段的關係
- 參與者
- 介紹架構框架
- 進行當前資訊系統清單
- 資訊系統組件清單
- 商業解決方案應用
- 解決方案啟用者
- 數據
- 中介軟體整合
- 作業系統
- 硬體平台
- 網路
- 開發環境、工具與方法論
- 管理啟用者
- 安全啟用者
- 資訊系統組織
- 當前資訊系統環境的評估
- 功能性
- 非功能性屬性
- 人力資源能力
- 外包服務
- 「架構」在哪裡？

9. 資訊系統架構規劃
- 總過程中的資訊系統架構規劃
- 與其他階段的關係
- 與物件導向模型集的關係
- 參與者
- 架構原則
- 原則如何定義？
- 撰寫原則的指導方針
- 定義架構模型
- 分岔路口：解決方案選擇
- 物件導向開發環境的架構模型
- 非物件導向開發環境的架構模型
- 定義支持的 IT 基礎設施
- 技術評估標準與考量
- 填補技術空白
- 確定硬體和軟體產品
- 電子商務的 IT 基礎設施
- 環境對電子商務技術的影響
- 電子商務技術：對環境需求的回應
- 「架構」在哪裡？
- 更多資訊的來源

10. 實施規劃
- 總過程中的實施規劃
- 與其他階段的關係
- 參與者
- 確定實施選項
- 實施選項的初步分析
- 分析實施選項
- 成本效益分析
- 風險分析
- 組織影響分析
- 建立過渡策略
- 使用風險效益矩陣
- 選擇短期和長期優先事項
- 分散風險
- 確定過渡順序
- 建立商業案例並確定過渡策略
- 「架構」在哪裡？
- 更多資訊的來源

11. 部署
- 總過程中的部署
- 與其他階段的關係
- 參與者
- 部署活動
- 專案管理
- 管理任務
- 反饋循環
- 「架構」在哪裡？

12. 審查
- 總過程中的審查階段

類似商品