Аннотация
t’s no secret that poorly understood user requirements and uncontrolled
scope creep lead to many software project failures. Many software
development organizations are improving the methods they use to
gather, analyze, document, and manage their requirements. Project
teams traditionally document their requirements in a structured
software requirements specification (SRS) written in natural language.
However, a document-based SRS has some limitations:
* It’s difficult to keep current * It’s hard to communicate changes
to the affected team members * It’s difficult to store supplementary
information about each requirement * It’s hard to define links
between functional requirements and corresponding use cases, designs,
code, tests, and project tasks.
A commercial requirements management tool that stores requirements
and related information in a multi-user database provides a more
robust solution. These tools provide functions to manipulate and
view the database contents, import and export requirements, define
links between requirements, and connect requirements to other software
development tools.
In this article, I’ll describe several benefits a requirements management
tool can provide, identify the basic features to expect from such
tools, and briefly review four commercial tools: TBI’s Caliber-RM,
QSS’s DOORS, Rational’s RequisitePro, and Integrated Chipware’s
RTM Workshop (Table 1). These tools won’t help you gather the
right requirements for your project, and they don’t replace a
defined process for managing your project’s requirements. A tool
is not a process in itself, but it supports and enables an established
process.
Пользователи данного ресурса
Пожалуйста,
войдите в систему, чтобы принять участие в дискуссии (добавить собственные рецензию, или комментарий)