A Requirements Pattern: Succeeding in the Internet Economy (需求模式:在網路經濟中成功)
Patricia L. Ferdinandi
- 出版商: Addison Wesley
- 出版日期: 2001-11-29
- 定價: $1,580
- 售價: 2.5 折 $399
- 語言: 英文
- 頁數: 528
- 裝訂: Paperback
- ISBN: 0201738260
- ISBN-13: 9780201738261
-
相關分類:
企業資源規劃 Erp、行銷/網路行銷 Marketing
立即出貨(限量)
買這商品的人也買了...
-
$931Artificial Intelligence: A Modern Approach
-
$480$408 -
$2,500$2,375 -
$1,980$1,881 -
$680$578 -
$1,560$1,482 -
$1,850$1,758 -
$1,029Operating System Concepts, 6/e
-
$590$502 -
$600$510 -
$1,720$1,634 -
$1,560$1,482 -
$1,090$1,068 -
$780$624 -
$420$328 -
$420$332 -
$600$474 -
$620$527 -
$420$357 -
$580$493 -
$1,615CCNA Cisco Certified Network Associate Study Guide, 5/e (640-801)
-
$1,519A Practical Guide to Linux Commands, Editors, and Shell Programming
-
$480$408 -
$480$408 -
$650$553
相關主題
商品描述
Table of Contents
1. What Is…
What Is Requirements Engineering.
What Is Internet.
How Does One Work with and Impact the Other.
Terminology — A Common Understanding.
Conclusion.
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 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.
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.
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.
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 Requirement Process.
The Requirement Subprocess.
Conclusion.
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 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.
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.
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 Organization.
Organization Impact.
Conclusion.
Requirement Community.
Requirement Perspective.
Requirement Focus.
Relationships between Categories.
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.
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.
The Pattern Specifics.
Gap Analysis.
Changing Business Model.
Understanding the Problem or Need.
Preparing for Allocation.
Understanding the Problem or Need.
Preparing for Allocation.
The Pattern Specifics.
Important Communities.
Perspective Specifics.
Focus Details.
Cell Association Checklist.
Perspective Specifics.
Focus Details.
Cell Association Checklist.
Gap Analysis.
Conclusion.
5. Internet Requirements Antipatterns.
Gap in Knowledge.
Gap in Participation.
Gap in Process.
Identifying Additional Antipatterns.
Conclusion.
Hacker Intervention <38> Other Security
Issues.
Quality of Service Impact.
Create Read Update Delete List (Crudl).
Quality of Service Impact.
Create Read Update Delete List (Crudl).
Gap in Participation.
The Business Model Tolerance Indicators.
Network Engineers Involvement.
Network Engineers Involvement.
Gap in Process.
Scope Creep.
When Designers Take Over (Technology for the Sake of Technology).
The Imposed Deadline.
When Designers Take Over (Technology for the Sake of Technology).
The Imposed Deadline.
Identifying Additional Antipatterns.
Conclusion.
6. Requirement Quality.
Individual Requirement Quality.
Requirement Specification Quality.
Requirement Set Quality.
Conclusion.
Parts of a Requirement.
Quality Characteristics.
Quality Characteristics.
Requirement Specification Quality.
Requirement Set Quality.
Quality Checkpoints.
Unit Test Versus System Test.
Walkthroughs.
Requirement Measurement.
Prototyping the Requirements.
Unit Test Versus System Test.
Walkthroughs.
Requirement Measurement.
Prototyping the Requirements.
Conclusion.
7. Managing the Internet Requirement Set.
Requirements Management <47> Configuration
Management.
Configuration Management for Requirements.
Conclusion.
Software Engineering Institute — Capability
Maturity Model.
Level 2: Repeatable.
Interpreting the Capability Maturity Model.
What Is Configuration Management.
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.
How to Implement RCM for Internet Type Applications.
What to Manage Under Requirements.
Preparing for Implementation.
The Implementation Process.
Conclusion.
Reference Material.
Additional Information.
Additional Information.
8.
Requirement Supplier.
Requirement User.
Requirement Supporter.
Requirement Producers.
The Internet Organization.
Conclusion.
Product Direction.
Detail Suppliers.
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.
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.
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 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.
Recap of What the Book Discussed.
Conclusion.
How to Get Started.
Applying the Requirement Pattern to Other Applications Types.
Key Points to Remember.
Sources for Additional Information.
Books.
Periodicals.
Web Sites.
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. 網際網路需求反模式。
知識差距。
參與差距。
黑客介入<38>其他安全問題。
服務品質影響。
建立讀取更新刪除列表(CRUDL)。
服務品質影響。
建立讀取更新刪除列表(CRUDL)。
參與差距。
商業模式容忍指標。
網路引擎```
網路引擎```