软件需求案例

商家名称	信用等级	购买信息	订购本书
		软件需求案例
		软件需求案例

基本信息·出版社：世界图书出版公司
·页码：349 页
·出版日期：2008年10月
·ISBN：7506292920/9787506292924
·条形码：9787506292924
·版本：第1版
·装帧：平装
·开本：16
·正文语种：英语

内容简介 这本实用的手册将指导您如何将通用的范本同有效的软件需求结合起来。 《软件需求案例》将帮助您学习进化的、实用的技巧来应付各种具体的软件需求，书中提供了30个需求的范本板以及大量的实例来帮助您构建具体而又有效的软件需求。书中的每一个范本都向您解释软件需求所需要考量的范畴，揭示潜在性的问题，指出可能存在的缺陷，提出更进一步的建议，以及其他的提示。《软件需求案例》同时还涵盖了如何为软件需求编写其他信息，诸如假设、术语表、文档历史和参考资料等，以及如何构建软件需求的规范。
作者简介 Stephen Winthall has nearly30 years experience developing and specifying software systems for organizations in a variety of industries across the globe His career spans many roles including programmer business analyst architect and chief technical officer.
目录
Foreword
Prefece
Part Ⅰ Setting the Scene
1 Synopsis of"Crash Course in Specifying Requirements"
1.1 What Are Requirements?
1.2 Where Do Requirements Fit in the Grand Scheme?
1.3 A Few General Principles
1.4 A Traditional Requirements Process
1.5 Agile Requirements Processes
An Extreme Requirements Process
An Incremental Requirements Process
2 Synopsis of "The Contents of a Requirements Specification"
2.1 Introduction Section
System Purpose
Document Purpose
Requirement Format
Glossary
References
Document History
2.2 Context Section
Scope
Major Assumptions
Major Exclusions
Key Business Entities
Infrastructures
2.3 Functional Area Sections
2.4 Major Nonfunctional Capabilities Section
3 Requirement Pattern Concepts
3.1 Introduction to Requirement Patterns
3.2 The Anatomy of a Requirement Pattern
Basic Details
Applicability
Discussion
Content
Template(s)
Example(s)
Extra Requirements
Considerations for Development
Considerations for Testing
3.3 Domains
Domains and Infrastructures
3.4 Requirement Pattern Groups
3.5 Relationships Between Requirement Patterns
Requirement Pattern Classifications
Refinement Requirements
Divertive Requirement Patterns
Requirement Patterns and Diversity of Approaches
Use Cases for Requirement Patterns
Business Rules and Requirement Patterns
4 Using and Producing Requirement Patterns
4.1 When and How to Use Requirement Patterns
4.2 Tailoring Requirement Patterns
4.3 Writing New Requirement Patterns
How to Find Candidate Requirement Patterns
How to Write a Requirement Pattern

Part Ⅱ Requirement Pattern Catalog
5 Fundamental Requirement Patterns
5.1 Inter-System Interface Requirement Pattern
5.2 Inter-System Interaction Requirement Pattern
6 Information Requirement Patterns
7 Data Entity Requirement Patterns
8 User Function Requirement Patterns
9 Performance Requirement Patterns
10 Flexibility Requirement Patterns
11 Access Control Requirement Patterns
12 Commercial Requirement Patterns
Glossary
References
Index
……
文摘 In Figure 3 3, "Data entity" is not a pattern. It's a requirement pattern group: a place for describingthe common features of the four patterns that build on it. Any descriptive information that appliesto all patterns in a group should be given for the group, rather than repeated for each pattern.Also, by convention, labels for relationships between requirement patterns are placed nearer thesubject of the relationship, rather than the object. So, it is a Data entity that has an lD （rather thanvice versa）. The hexagonal shape of"Information storage" denotes it as an infrastructureSee the beginning of Part II of this book for a diagram of this sort for aft the requirementpatterns in this book. Each of the eight domain chapters contains a diagram of this sort inits introduction, with annotations giving a brief explanation of each pattern, pattern group,and infrastructure.Requirement Pattern ClassificationsRequirements can be classified in various ways （for example, by dividing them into functional andnonfunctional ones）. Using requirement patterns has the advantage that if we classify the patterns,we automatically classify the requirements that use those patterns Classifications tell us a littleabout the nature of the requirements that result from using each requirement pattern.Other ways of using these classifications include finding requirements according to their dassifica-tion and producing statistics. People like statistics （some people, at least, and they tend to be seniorexecutives it's worth our while keeping happy）. Statistics on the requirements for a system can beuseful in a variety of ways They, can give a rough picture of the scale and complexity of the system.To do this, we need to tag each requirement with whatever values are needed for all the sorts .
插图：

查看更多 下一篇