A Requirements Pattern: Succeeding in the Internet Economy
暫譯: 需求模式:在網際網路經濟中成功

Patricia L. Ferdinandi

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

相關主題

商品描述

Table of Contents

1. What Is…

What Is Requirements Engineering.
Internet Requirements.
What Is the State of Requirements Today.
What Is Technologies Involvement.
What Is the Path to Satisfying the Current Needs of the Business.

What Is Internet.
The Internet Explosion.
Collapsed Hierarchy.
Business Partnerships.
New Lines of Business.
Customer Centric.
Profit versus Potential Revenue.

How Does One Work with and Impact the Other.
Understanding Requirements Engineering.
The Common Perspective.

Terminology — A Common Understanding.
What Is Internet.
What Is a Requirement.
What Is an Internet Requirement.
Requirement Set.
What Is a Pattern.
What Is a Requirements Pattern.
What Is an Internet Requirements Pattern.
What Is an Anti-Pattern.
What Is an Internet Requirements Anti-Pattern.
Requirement Specification.
Requirement Engineer.
Requirement Engineering.
Requirements Management.
What Is a Requirement Process.
Requirement Versus Requirement Specification Versus Requirement Set.

Conclusion.


2. Requirement Evolution.

The Requirement Evolution.
The Manufacturing Process.
The Internet Development Process.
Requirement Development Process.
The Birth of an Idea.
Product Concept.
The Business Case … Do You Belong on the Net.

The Requirement Process.
Requirement Allocation.
Avoiding Politics.
What a Process.
Internet Evolution.
Current Requirement Process Scenario.
The Correlation between Allocation Level and Perspective.
Requirements Evolving through Perspectives.

The Requirement Subprocess.
Elicitation.
Analysis.
Specification.
Validation.
Approval as a Separate Activity.
Quality Gate Checkpoints.
Managing the Requirements and the Requirement Set.
The Subprocess Is a Generic Process.
Requirement Reuse.

Conclusion.


3. The Requirement Set.

Requirement Category.
Requirement Community.
Requirement Perspective.
Requirement Focus.
Relationships between Categories.

Requirement Organization.
A Quality Home.
Different Views of the Same House.
Different Focuses of the Same Software Solution.
Extensions to the Information Systems Architecture.

Organization Impact.
Conclusion.


4. Internet Requirements Pattern.

The Kick off.
Changing Business Model.
Understanding the Problem or Need.
Preparing for Allocation.

The Pattern Specifics.
Important Communities.
Perspective Specifics.
Focus Details.
Cell Association Checklist.

Gap Analysis.
Conclusion.


5. Internet Requirements Antipatterns.

Gap in Knowledge.
Hacker Intervention <38> Other Security Issues.
Quality of Service Impact.
Create Read Update Delete List (Crudl).

Gap in Participation.
The Business Model Tolerance Indicators.
Network Engineers Involvement.

Gap in Process.
Scope Creep.
When Designers Take Over (Technology for the Sake of Technology).
The Imposed Deadline.

Identifying Additional Antipatterns.
Conclusion.


6. Requirement Quality.

Individual Requirement Quality.
Parts of a Requirement.
Quality Characteristics.

Requirement Specification Quality.
Requirement Set Quality.
Quality Checkpoints.
Unit Test Versus System Test.
Walkthroughs.
Requirement Measurement.
Prototyping the Requirements.

Conclusion.


7. Managing the Internet Requirement Set.

Requirements Management <47> Configuration Management.
Software Engineering Institute — Capability Maturity Model.
Level 2: Repeatable.
Interpreting the Capability Maturity Model.
What Is Configuration Management.

Configuration Management for Requirements.
Supporting the Configuration Management of Requirements.
How to Implement RCM for Internet Type Applications.
What to Manage Under Requirements.
Preparing for Implementation.
The Implementation Process.

Conclusion.
Reference Material.
Additional Information.


8.

Requirement Supplier.
Product Direction.
Detail Suppliers.

Requirement User.
Project Manager.
Data Warehouse Specialist.
Database Administrator.
Developers.
Usability Engineer.
Network Planner.
Operations Analyst.
Technical Architect.
Test Analyst <47> Quality Control Analyst.
Trainer.
Writer, Editors <38> User Education.

Requirement Supporter.
Facilitator.
Process Manager.
Quality Assurance.
Group Manager.
Anthropology.

Requirement Producers.
The Power of Meeting Minutes.
The Requirement Engineering Roles.
The Necessary Skills the Requirement Engineering Organization.

The Internet Organization.
Conclusion.


9.

How Long Will This Take.
How to Get Started.
Applying the Requirement Pattern to Other Applications Types.
Key Points to Remember.
Sources for Additional Information.
Books.
Periodicals.
Web Sites.

Recap of What the Book Discussed.
Conclusion.


Appendix A. Internet Requirements Pattern Specification Format.
Appendix B. Internet Requirements Pattern (Information Technology Community).
Appendix C. Requirements Pattern Work Breakdown Structure.
Appendix D. Requirement Pattern Language.
Appendix E. Requirement Pattern & Anti-Pattern Usage.
Glossary.
Bibliography.

商品描述(中文翻譯)

目錄

1. 什麼是…
什麼是需求工程。
網際網路需求。當前需求的狀態是什麼。技術的參與是什麼。滿足當前商業需求的途徑是什麼。

什麼是網際網路。
網際網路的爆炸。層級崩潰。商業夥伴關係。新的商業線。以客戶為中心。利潤與潛在收入。

如何相互影響。
理解需求工程。共同的觀點。

術語 — 共同的理解。
什麼是網際網路。什麼是需求。什麼是網際網路需求。需求集。什麼是模式。什麼是需求模式。什麼是網際網路需求模式。什麼是反模式。什麼是網際網路需求反模式。需求規範。需求工程師。需求工程。需求管理。什麼是需求過程。需求與需求規範與需求集的區別。

結論。

2. 需求演變。
需求演變。
製造過程。網際網路開發過程。需求開發過程。一個想法的誕生。產品概念。商業案例…你是否適合上網。

需求過程。
需求分配。避免政治。什麼是過程。網際網路演變。當前需求過程情境。分配層級與觀點之間的關聯。需求透過觀點的演變。

需求子過程。
引出。分析。規範。驗證。批准作為一個獨立的活動。質量門檻檢查點。管理需求與需求集。子過程是一個通用過程。需求重用。

結論。

3. 需求集。
需求類別。
需求社群。需求觀點。需求焦點。類別之間的關係。

需求組織。
一個質量之家。同一房子的不同視角。同一軟體解決方案的不同焦點。對資訊系統架構的擴展。

組織影響。結論。

4. 網際網路需求模式。
啟動。
變更商業模式。理解問題或需求。準備分配。

模式細節。
重要社群。觀點細節。焦點細節。單元關聯檢查表。

差距分析。
結論。

5. 網際網路需求反模式。
知識的差距。
駭客介入及其他安全問題。服務質量影響。創建讀取更新刪除清單(Crudl)。

參與的差距。
商業模式容忍指標。網路工程師的參與。

過程的差距。
範圍蔓延。當設計師接管(為了技術而技術)。強加的截止日期。

識別其他反模式。結論。

6. 需求質量。
個別需求質量。
需求的部分。質量特徵。

需求規範質量。需求集質量。
質量檢查點。單元測試與系統測試。走查。需求測量。需求的原型設計。

結論。

7. 管理網際網路需求集。
需求管理與配置管理。
軟體工程研究所 — 能力成熟度模型。第二級:可重複。解釋能力成熟度模型。什麼是配置管理。

需求的配置管理。
支持需求的配置管理。如何為網際網路類型應用實施RCM。需求下要管理的內容。準備實施。實施過程。

結論。
參考資料。附加資訊。

8. 需求供應商。
產品方向。詳細供應商。

需求使用者。
專案經理。資料倉儲專家。資料庫管理員。開發人員。可用性工程師。網路規劃師。運營分析師。技術架構師。測試分析師與質量控制分析師。培訓師。作家、編輯與用戶教育。

需求支持者。
促進者。過程管理者。質量保證。小組經理。人類學。

需求生產者。
會議紀錄的力量。需求工程角色。需求工程組織所需的技能。

網際網路組織。結論。

9. 這需要多長時間。如何開始。將需求模式應用於其他應用類型。要記住的要點。附加資訊來源。
書籍。期刊。網站。

本書討論的內容回顧。結論。

附錄A. 網際網路需求模式規範格式。
附錄B. 網際網路需求模式(資訊技術社群)。
附錄C. 需求模式工作分解結構。
附錄D. 需求模式語言。
附錄E. 需求模式與反模式的使用。
詞彙表。
參考書目。