Managing software requirements : a use case approach = 软件需求管理 : 用例方法 / 2nd ed.
副标题：无
作 者：Dean Leffingwell, Don Widrig著.
分类号：
ISBN：9787111137870
微信扫一扫,移动浏览光盘
简介
许多软件项目失败的根本原因在于开发人员没有正确理解客户的真正需求。各类应用程序的开发人员都应该读一读这本书。 ——grady booch
为每个开发团队面临的需求难题提供全方位的解决方案。通过阅读本书，所有开发人员都可以开阔视野，获得真知灼见。 ——lvar jacobson
当今，尽管开发的知识和经验不断丰富，可利用的工具也不断增多，但仍然有相当多的软件项目失败了，原因常常是在开始时没有正确地确定和定义需求，或者随着项目的展开没有正确地管理需求。本书聚焦于这一导致项目失败的关键原因，提出了一个经过证明的实用方法，帮助我们在预算内按时提交一个符合客户需要的系统。
作者采用一种易于接受的风格，讲述他们自己的实战经历，列举大量的案例研究，向我们展示了分析人员和开发人员如何把用例技术和传统的需求表达形式结合起来高效地确定需求。书中还说明了一些经过证明的用以确定、实现、验证和确认需求的技术，并给出了在项目的整个生命周期中，管理需求的六大团队技能：分析问题、理解用户需要、定义系统、管理范围、细化系统定义、构建正确系统。
本书还强调不断地管理变更，描述了确保成功定义项目范围并使所有风险承担人达成共识的过程。
目录
foreword
preface to the second edition
preface to the first edition
introduction
chapter i the requirements problem
the goal of software development
a look at the data
the root causes of project success and failure
the frequency of requirements errors
the high cost of requirements errors
summary
chapter 2 introduction to requirements management definitions
what is a software requirement?
what is requirements management?
application of requirements management techniques
types of software applications
systems applications
the road map
the problem domain
stakeholder needs
.moving toward the solution domain
features of the system
software requirements
summary
chapter 3 requirements and the software lifecycle
traditional software process models
the waterfall model
the spiral model
the iterative approach
lifecycle phases
iterations
disciplines
requirements in the iterative model
summary
chapter 4 the software team
software development as a team activity
requisite team skills for effective requirements management
team members have different skills
the organization of software teams
the case study
background for the case study
the holis software development team
summary
team skill 1 analyzing the problem
chapter 5 the five steps in problem analysis
step 1: gain agreement on the problem definition
the problem statement
step 2: understand the root causes--the problem behind
the problem
addressing the root cause
step 3: identify the stakeholders and the users
step 4: define the solution system boundary
step 5: identify the constraints to be imposed on the solution
summary
looking ahead
chapter 6 business modeling
the purpose of business modeling
using software engineering techniques for business modeling
choosing the right technique
the unified modeling language
business modeling using uml concepts
from the business model to the systems model
when to use business modeling
summary
looking ahead
chapter 7 systems engineering of software-intensive systems
what is systems engineering?
pragmatic principles of systems engineering
the composition and decomposition of complex systems
requirements allocation in systems engineering
on derived requirements
a quiet revolution
when generations collide: graying baby boomer
meets generation x-er
avoiding the stovepipe system problem
when subsystems are subcontracts
addressing the conundrum
the case study: systems engineering for holis
preliminary user needs
problem analysis
holis: the system, actors, and stakeholders
holis systems engineering
the subsystems of holis
summary
team skill 1 summary
rout
team skill 2 understanding user and stakeholder needs
chapter 8 the challenge of requirements elicitation
barriers to elicitation
the "yes, but" syndrome
the "undiscovered ruins" syndrome
the "user and the developer" syndrome
summary
chapter 9 the features of a product or system
stakeholder and user needs
features
managing complexity by picking the level of abstraction
attributes of product features
summary
chapter 10 interviewing
context-free questions
solutions-context questions
the moment of truth: the interview
compiling the needs data
the analyst's summary: 10 + 10 + 10 ;e 30
the case study
a note on questionnaires
summary
chapter 11 requirements workshops
accelerating the decision process
preparing for the workshop
selling the concept
ensuring the participation of the right stakeholders
attending to logistics
providing warm-up materials
choosing the facilitator
setting the agenda
running the workshop
problems and tricks of the trade
brainstorming and idea reduction
production and follow-up
summary
chapter 12 brainstorming and idea reduction
live brainstorming
idea reduction
pruning ideas
grouping ideas
defining features
prioritizing ideas
web-based brainstorming
the case study: the holis requirements workshop
the attendees
the workshop
the session
the analysis of results
summary
chapter 13 storyboarding
types of storyboards
what storyboards do
tools for storyboarding
tips for storyboarding
summary
team skill 2 summary
team skill 3 defining the system
chapter 14 a use case primer
the benefits of use cases
use case basics
on actors
use case anatomy
a step-by-step guide to building the use-case model
step 1: identify and describe the actors
step 2: identify the use cases and write a brief description
step 3: identify the actor and use-case relationships
step 4: outline the individual use cases
step 5: refine the use cases
on use cases, storyboarding, and user interface design
use cases and user interfaces
use cases and storyboarding
a use case storyboard example
the case study: the holis use cases
find the holis actors
find the holis use cases
associate the actors and use cases
outline the use cases
summary
chapter 15 organizing requirements information
organizing requirements of complex hardware
and software systems
organizing requirements for product families
on "future" requirements
the case study: organizing the holis requirements
summary
looking ahead
chapter 16 the vision document
components of the vision document
the delta vision document
the vision document for version 1.0
the vision document for version 2.0
the delta vision document in a legacy system environment
summary
chapter 17 product management
the role of the product champion
the product manager in a software product company
primary activities for a product manager
driving the vision
maintaining the product road map
defining the whole product plan
sponsoring the use-case model and supplementary
requirements
testing the product concept
completing the user experience
defining commercial terms
positioning and messaging
supporting activities
branding and product labeling
end user training materials
product demo
sales and marketing collateral
the product champion in an is/it shop
summary
team skill 3 summary
team skill 4 managing scope
chapter 18 establishing project scope
the problem of project scope
the hard question
the requirements baseline
setting priorities
assessing effort
adding the risk element
reducing scope
a reasonable first estimate
summary
chapter 19 managing your customer
engaging customers to manage their project scope
communicating the result
negotiating with the customer
managing the baseline
official changes
unofficial changes
summary
team skill 4 summary
team skill 5 refining the system definition
chapter 20 software gequirements---a more rigorous look
looking deeper into software requirements
the relationship between software requirements and use cases
the relationship between features and software requirements
the requirements dilemma: whatversus how
excluding project information
excluding design information
more on requirements versus design
iterating requirements and design
a further characterization of requirements
functional software requirements
nonfunctional software requirements
design constraints
summary
looking ahead
chapter 21 refining the use cases
how use cases evolve
the scope of a use case
the case study: anatomy of a simple use case
reviewing the actors
reviewing the name
refining the description
defining and refining the flow of events
identifying the pre-and post-conditions
identifying special requirements
summary of our refined use case
extending use cases
including use cases in other use cases
summary
looking ahead
chapter 22 developing the supplementary specification
the role of the supplementary specification
expressing functional requirements in the supplementary
specification
exploring nonfunctional requirements
usability
reliability
performance
supportability
understanding design constraints
sources of design constraints
handling design constraints
are design constraints true requirements?
identifying other requirements
linking the supplementary specification to the use cases
template for the supplementary specification
summary
looking ahead
chapter 23 on ambiguity and specificity
finding the "sweet spot"
mary had a litfie lamb
techniques for disambiguation
summary
chapter 24 technical methods for specifying requirements
pseudocode
finite state machines
decision tables and decision trees
activity diagrams
entity-relationship models
summary
team skill 5 summary
team skill 6 building the right system
chapter 25 from use cases to implementation
mapping requirements directly to design and code
the orthogonality problem
object orientation
the use case as a requirement
managing the transition
modeling software systems
the architecture of software systems
the role of the use-case model in architecture
realizing use cases in the design model
structural and behavioral aspects of collaborations
using collaborations to realize sets of individual requirements
from design to implementation
summary
looking ahead
chapter 26 from use cases to test cases
a tester's perspective: musings on the big black box
is a use case a test case?
common testing terms
relationships of test artifacts
the role of the test cases
use-case scenarios
deriving test cases from use cases: a four-step process
step l: identify the use-case scenarios
step 2: identify the test cases
step 3: identify the test conditions
step 4: add data values to complete the test case
managing test coverage
black-box versus white-box testing with use cases
summary
chapter 27 tracing requirements
the role of traceability in systems development
the traceability relationship
a generalized traceability model
tracing requirements in the system definition domain
tracing requirements to implementation
tracing from requirements to testing
using traceability tools
proceeding without traceability tools
summary
chapter 28 managing change
why do requirements change?
external factors
internal factors
"we have met the enemy, and they is us"
a process for managing change
step 1: recognize that change is inevitable, and plan for it
step 2: baseline the requirements
step 3: establish a single channel to control change
step 4: use a change control system to capture changes
step 5: manage change hierarchically
requirements configuration management
tool-based support for change management
elements impacted by change
audit trail of change history
configuration management and change management
summary
looking ahead
chapter 29 assessing requirements quality in iterative
development
software project quality
assessing quality in iterative development
requirements artifacts sets
performing the assessment
quality assessment checklists for requirements
summary
team skill 6 summary
looking ahead
getting started
dedication
what you've learned so far
introduction
team skill 1: analyzing the problem
team skill 2: understanding user and stakeholder needs
team skill 3: defining the system
team skill 4: managing scope
team skill 5: refining the system definition
team skill 6: building the right system
chapter 30 agile requirements methods
mitigating requirements risk with effective requirements practices
methodology design goals
documentation is a means to an end
an extreme requirements method
an agile requirements method
a robust requirements method
summary
chapter 31 your prescription for requirements management
selecting your requirements approach
the simplifying assumptions
the prescription
on to the next release!
appendixes
appendix a holis artifacts
appendix b vision document template
appendix c use-case specification template
appendix d supplementary specification template
appendix e requirements management in the rational
unified process
appendix f requirements management in the sei-cmm
and within iso 9000:2000
bibliography
index
preface to the second edition
preface to the first edition
introduction
chapter i the requirements problem
the goal of software development
a look at the data
the root causes of project success and failure
the frequency of requirements errors
the high cost of requirements errors
summary
chapter 2 introduction to requirements management definitions
what is a software requirement?
what is requirements management?
application of requirements management techniques
types of software applications
systems applications
the road map
the problem domain
stakeholder needs
.moving toward the solution domain
features of the system
software requirements
summary
chapter 3 requirements and the software lifecycle
traditional software process models
the waterfall model
the spiral model
the iterative approach
lifecycle phases
iterations
disciplines
requirements in the iterative model
summary
chapter 4 the software team
software development as a team activity
requisite team skills for effective requirements management
team members have different skills
the organization of software teams
the case study
background for the case study
the holis software development team
summary
team skill 1 analyzing the problem
chapter 5 the five steps in problem analysis
step 1: gain agreement on the problem definition
the problem statement
step 2: understand the root causes--the problem behind
the problem
addressing the root cause
step 3: identify the stakeholders and the users
step 4: define the solution system boundary
step 5: identify the constraints to be imposed on the solution
summary
looking ahead
chapter 6 business modeling
the purpose of business modeling
using software engineering techniques for business modeling
choosing the right technique
the unified modeling language
business modeling using uml concepts
from the business model to the systems model
when to use business modeling
summary
looking ahead
chapter 7 systems engineering of software-intensive systems
what is systems engineering?
pragmatic principles of systems engineering
the composition and decomposition of complex systems
requirements allocation in systems engineering
on derived requirements
a quiet revolution
when generations collide: graying baby boomer
meets generation x-er
avoiding the stovepipe system problem
when subsystems are subcontracts
addressing the conundrum
the case study: systems engineering for holis
preliminary user needs
problem analysis
holis: the system, actors, and stakeholders
holis systems engineering
the subsystems of holis
summary
team skill 1 summary
rout
team skill 2 understanding user and stakeholder needs
chapter 8 the challenge of requirements elicitation
barriers to elicitation
the "yes, but" syndrome
the "undiscovered ruins" syndrome
the "user and the developer" syndrome
summary
chapter 9 the features of a product or system
stakeholder and user needs
features
managing complexity by picking the level of abstraction
attributes of product features
summary
chapter 10 interviewing
context-free questions
solutions-context questions
the moment of truth: the interview
compiling the needs data
the analyst's summary: 10 + 10 + 10 ;e 30
the case study
a note on questionnaires
summary
chapter 11 requirements workshops
accelerating the decision process
preparing for the workshop
selling the concept
ensuring the participation of the right stakeholders
attending to logistics
providing warm-up materials
choosing the facilitator
setting the agenda
running the workshop
problems and tricks of the trade
brainstorming and idea reduction
production and follow-up
summary
chapter 12 brainstorming and idea reduction
live brainstorming
idea reduction
pruning ideas
grouping ideas
defining features
prioritizing ideas
web-based brainstorming
the case study: the holis requirements workshop
the attendees
the workshop
the session
the analysis of results
summary
chapter 13 storyboarding
types of storyboards
what storyboards do
tools for storyboarding
tips for storyboarding
summary
team skill 2 summary
team skill 3 defining the system
chapter 14 a use case primer
the benefits of use cases
use case basics
on actors
use case anatomy
a step-by-step guide to building the use-case model
step 1: identify and describe the actors
step 2: identify the use cases and write a brief description
step 3: identify the actor and use-case relationships
step 4: outline the individual use cases
step 5: refine the use cases
on use cases, storyboarding, and user interface design
use cases and user interfaces
use cases and storyboarding
a use case storyboard example
the case study: the holis use cases
find the holis actors
find the holis use cases
associate the actors and use cases
outline the use cases
summary
chapter 15 organizing requirements information
organizing requirements of complex hardware
and software systems
organizing requirements for product families
on "future" requirements
the case study: organizing the holis requirements
summary
looking ahead
chapter 16 the vision document
components of the vision document
the delta vision document
the vision document for version 1.0
the vision document for version 2.0
the delta vision document in a legacy system environment
summary
chapter 17 product management
the role of the product champion
the product manager in a software product company
primary activities for a product manager
driving the vision
maintaining the product road map
defining the whole product plan
sponsoring the use-case model and supplementary
requirements
testing the product concept
completing the user experience
defining commercial terms
positioning and messaging
supporting activities
branding and product labeling
end user training materials
product demo
sales and marketing collateral
the product champion in an is/it shop
summary
team skill 3 summary
team skill 4 managing scope
chapter 18 establishing project scope
the problem of project scope
the hard question
the requirements baseline
setting priorities
assessing effort
adding the risk element
reducing scope
a reasonable first estimate
summary
chapter 19 managing your customer
engaging customers to manage their project scope
communicating the result
negotiating with the customer
managing the baseline
official changes
unofficial changes
summary
team skill 4 summary
team skill 5 refining the system definition
chapter 20 software gequirements---a more rigorous look
looking deeper into software requirements
the relationship between software requirements and use cases
the relationship between features and software requirements
the requirements dilemma: whatversus how
excluding project information
excluding design information
more on requirements versus design
iterating requirements and design
a further characterization of requirements
functional software requirements
nonfunctional software requirements
design constraints
summary
looking ahead
chapter 21 refining the use cases
how use cases evolve
the scope of a use case
the case study: anatomy of a simple use case
reviewing the actors
reviewing the name
refining the description
defining and refining the flow of events
identifying the pre-and post-conditions
identifying special requirements
summary of our refined use case
extending use cases
including use cases in other use cases
summary
looking ahead
chapter 22 developing the supplementary specification
the role of the supplementary specification
expressing functional requirements in the supplementary
specification
exploring nonfunctional requirements
usability
reliability
performance
supportability
understanding design constraints
sources of design constraints
handling design constraints
are design constraints true requirements?
identifying other requirements
linking the supplementary specification to the use cases
template for the supplementary specification
summary
looking ahead
chapter 23 on ambiguity and specificity
finding the "sweet spot"
mary had a litfie lamb
techniques for disambiguation
summary
chapter 24 technical methods for specifying requirements
pseudocode
finite state machines
decision tables and decision trees
activity diagrams
entity-relationship models
summary
team skill 5 summary
team skill 6 building the right system
chapter 25 from use cases to implementation
mapping requirements directly to design and code
the orthogonality problem
object orientation
the use case as a requirement
managing the transition
modeling software systems
the architecture of software systems
the role of the use-case model in architecture
realizing use cases in the design model
structural and behavioral aspects of collaborations
using collaborations to realize sets of individual requirements
from design to implementation
summary
looking ahead
chapter 26 from use cases to test cases
a tester's perspective: musings on the big black box
is a use case a test case?
common testing terms
relationships of test artifacts
the role of the test cases
use-case scenarios
deriving test cases from use cases: a four-step process
step l: identify the use-case scenarios
step 2: identify the test cases
step 3: identify the test conditions
step 4: add data values to complete the test case
managing test coverage
black-box versus white-box testing with use cases
summary
chapter 27 tracing requirements
the role of traceability in systems development
the traceability relationship
a generalized traceability model
tracing requirements in the system definition domain
tracing requirements to implementation
tracing from requirements to testing
using traceability tools
proceeding without traceability tools
summary
chapter 28 managing change
why do requirements change?
external factors
internal factors
"we have met the enemy, and they is us"
a process for managing change
step 1: recognize that change is inevitable, and plan for it
step 2: baseline the requirements
step 3: establish a single channel to control change
step 4: use a change control system to capture changes
step 5: manage change hierarchically
requirements configuration management
tool-based support for change management
elements impacted by change
audit trail of change history
configuration management and change management
summary
looking ahead
chapter 29 assessing requirements quality in iterative
development
software project quality
assessing quality in iterative development
requirements artifacts sets
performing the assessment
quality assessment checklists for requirements
summary
team skill 6 summary
looking ahead
getting started
dedication
what you've learned so far
introduction
team skill 1: analyzing the problem
team skill 2: understanding user and stakeholder needs
team skill 3: defining the system
team skill 4: managing scope
team skill 5: refining the system definition
team skill 6: building the right system
chapter 30 agile requirements methods
mitigating requirements risk with effective requirements practices
methodology design goals
documentation is a means to an end
an extreme requirements method
an agile requirements method
a robust requirements method
summary
chapter 31 your prescription for requirements management
selecting your requirements approach
the simplifying assumptions
the prescription
on to the next release!
appendixes
appendix a holis artifacts
appendix b vision document template
appendix c use-case specification template
appendix d supplementary specification template
appendix e requirements management in the rational
unified process
appendix f requirements management in the sei-cmm
and within iso 9000:2000
bibliography
index
Managing software requirements : a use case approach = 软件需求管理 : 用例方法 / 2nd ed.
- 名称
- 类型
- 大小
光盘服务联系方式: 020-38250260 客服QQ：4006604884
云图客服：
用户发送的提问，这种方式就需要有位在线客服来回答用户的问题，这种 就属于对话式的,问题是这种提问是否需要用户登录才能提问
Video Player
×
Audio Player
×
pdf Player
×
