The Software Architect's Profession: An Introduction
暫譯: 軟體架構師的職業：入門指南

Marc Sewell, Laura Sewell

The Software Architect's Profession: An Introduction
  • 出版商: Prentice Hall
  • 出版日期: 2001-09-19
  • 售價: $1,770
  • 貴賓價: 9.5 折 $1,682
  • 語言: 英文
  • 頁數: 144
  • 裝訂: Paperback
  • ISBN: 0130607967
  • ISBN-13: 9780130607966

    • 已過版

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

商品描述

A transformational guide to the profession of software architecture.

Whether a structure is built of bricks, steel, or computer code, the process begins with an architect and client. Together they arrive at a shared vision—a plan—that the architect guides through the bidding, construction, and implementation phases. The Parthenon and the Empire State Building were built according to architectural designs, but the software industry has been building information skyscrapers without architects. It is time for the profession to become a reality.

Successful software-based technology is designed, then built. It does not "develop." Who creates the design? An enormous grass-roots demand exists for software architects-but a true profession of software architecture is not yet established. Many software professionals adopt the gravitas of the title "software architect," but fail to fulfill the true, classical role. Drawing on deep metaphors from traditional architecture, Marc T. Sewell, President of the Worldwide Institute of Software Architects, and Laura M. Sewell examine the nature of architecture, what defines a software architect, and how the profession is coming of age.

The Software Architect's Profession is lingo-free. It is a book of philosophy that will enable anyone to understand software construction, and it is the first "line in the sand" defining the parameters of this fledgling, yet ancient, e-profession.

Key areas include:

  • Bridging the chasm that separates clients from technical professionals
  • Differentiating the professions within the software construction industry and defining the roles and accountabilities of software engineers and software "builders"
  • Discussing the vocational temperament and aptitudes that characterize architects
  • Reviewing the phases of architecture
  • Describing the critical role of the client in understanding and validating the design and construction of software

Whether you are a CIO, CEO, IT manager, software professional, or student, you inhabit software structures, and your world is profoundly affected by their design. The Software Architect's Profession offers a simple cognitive map that will change your world view of software architecture, construction, and the information structures we live and work in everyday.

Table of Contents

Foreword.
Preface.
1. Simple Analogy.

The Perfect Analogy. Finally, a Cognitive Map. The Analogy Reveals the Missing Ingredient Architecture. The Analogy Confers Clarity of Role and Purpose. It All Begins with a Client and an Architect. With the Analogy, Words Are Meaningful. With the Analogy, Processes Are Predictable. The Analogy Brings Order to Complexity and Flexibility. Conclusion.


2. World Without Architects.

The Paradox of the Software Industry. The March of the Notorious. The Federal Aviation Administration. Internal Revenue Service Tax System Modernization (TSM). Conclusion.


3. What Is Architecture?

Technology: The Common Thread of Architecture. Many Definitions of the Indefinable. Utilitas, Venustas, Firmitas. The Mystery of Design. The Lesson of St. Peter's: Harmony and Unity. The Quality Without a Name. Conclusion.


4. A Pithy History of Architecture.

The Greek Ideal. Architects: Anonymous Craftsmen and Superstars. Modern Architecture: Rise and Demise. The Architect as Social Philosopher. Architecture and the Third Wave. Conclusion.


5. The Roles of Software Construction.

Architect, Builder, Engineer, Scientist. Guiding Principles. Software Architects Decide How the Structure Will Look and Act. Software Engineers Make the Structure Sound. Developers Build the Structure. Computer Scientists Further Knowledge. The Role of the Client. Defining, Not Limiting. An Indelicate, but Trenchant, Illustration of the Roles of Construction. Conclusion.


6. The Role of the Software Architect.

The Role of the Architect Begins with the Client. The Architect as Client Advocate and Design Champion. The Art of Listening. The Art of Observation. The Art of Strategy. The Pyramid in Paris. Conclusion.


7. The Phases of Architecture-Driven Software Construction.

Two Overall Phases. Architectural Phases, with Caveats. The Design Is Not the Deliverable. Caution: These Design Phases Are Not Linear. The Building Phases. Conclusion: The Party Phase.


8. The Architectural Plan.

The Characteristics of an Architectural Plan. Good Architects, Good Plans. Why Have Plans at All? The Levels of the Plan. Conclusion.


9. Educating Software Architects.

Second Wave Education, Third Wave Needs. Still Another Crisis. We Are What We Do. What Is the Profile of a Computer Scientist? Architecture Education. Establishing Software Architecture Education. Can Design Be Taught? Conclusion.


10. Venturing to Call Ourselves Architects.

What Is a Profession? Client Expectations. A Standard Body of Knowledge. Education. Identity. A Code of Ethics and Standards. Where to Begin.


Index.

商品描述(中文翻譯)

一部關於軟體架構職業的轉型指南。

無論結構是由磚塊、鋼材還是電腦程式碼建成，這個過程都始於建築師和客戶。兩者共同達成一個共享的願景——一個計畫——建築師在投標、建設和實施階段中引導這個計畫。帕台農神廟和帝國大廈都是根據建築設計建造的，但軟體產業卻在沒有建築師的情況下建造資訊摩天大樓。是時候讓這個職業成為現實。

成功的基於軟體的技術是設計出來的，然後再建造。它不會「發展」。誰來創造設計？對軟體架構師的需求非常龐大，但真正的軟體架構職業尚未建立。許多軟體專業人士採用了「軟體架構師」這個頭銜的莊重性，但未能履行真正的、傳統的角色。全球軟體架構師協會的總裁Marc T. Sewell和Laura M. Sewell借用傳統建築的深刻隱喻，探討了架構的本質、什麼定義了軟體架構師，以及這個職業如何逐漸成熟。

《軟體架構師的職業》是一本不使用行話的書。這是一本哲學書，將使任何人都能理解軟體建設，並且是定義這個新興但古老的電子職業參數的第一條「沙線」。

主要領域包括：
- 橋接客戶與技術專業人士之間的鴻溝
- 區分軟體建設產業內的職業，並定義軟體工程師和軟體「建造者」的角色與責任
- 討論塑造建築師的職業氣質和能力
- 回顧架構的階段
- 描述客戶在理解和驗證軟體設計與建設中的關鍵角色

無論您是CIO、CEO、IT經理、軟體專業人士還是學生，您都生活在軟體結構中，您的世界深受其設計的影響。《軟體架構師的職業》提供了一個簡單的認知地圖，將改變您對軟體架構、建設以及我們日常生活和工作的資訊結構的世界觀。

目錄
前言。
序言。
1. 簡單的類比。
完美的類比。終於，一個認知地圖。類比揭示了缺失的成分架構。類比賦予角色和目的的清晰性。一切始於客戶和建築師。透過類比，詞語變得有意義。透過類比，過程變得可預測。類比為複雜性和靈活性帶來秩序。結論。

2. 沒有建築師的世界。
軟體產業的悖論。臭名昭著的進程。聯邦航空管理局。國稅局稅制現代化（TSM）。結論。

3. 什麼是架構？
技術：架構的共同線索。許多無法定義的定義。Utilitas、Venustas、Firmitas。設計的奧秘。聖彼得的教訓：和諧與統一。無名的品質。結論。

4. 建築的簡要歷史。
希臘理想。建築師：匿名工匠和明星。現代建築：興起與衰亡。建築師作為社會哲學家。建築與第三波。結論。

5. 軟體建設的角色。
建築師、建造者、工程師、科學家。指導原則。軟體架構師決定結構的外觀和行為。軟體工程師使結構穩固。開發者建造結構。計算機科學家進一步擴展知識。客戶的角色。定義，而非限制。對建設角色的微妙但尖銳的插圖。結論。

6. 軟體架構師的角色。
建築師的角色始於客戶。建築師作為客戶的倡導者和設計的捍衛者。傾聽的藝術。觀察的藝術。策略的藝術。巴黎的金字塔。結論。

7. 以架構為驅動的軟體建設階段。
兩個整體階段。架構階段，附帶警告。設計不是可交付成果。注意：這些設計階段不是線性的。建設階段。結論：派對階段。

8. 建築計畫。
建築計畫的特徵。好的建築師，好的計畫。為什麼要有計畫？計畫的層次。結論。

9. 培養軟體架構師。
第二波教育，第三波需求。又一場危機。我們就是我們所做的。計算機科學家的特徵是什麼？架構教育。建立軟體架構教育。設計可以被教導嗎？結論。

10. 冒險自稱為建築師。
什麼是職業？客戶期望。一套標準的知識體系。教育。身份。一套倫理和標準。從哪裡開始。

索引。

類似商品

最後瀏覽商品 (10)