Ensure Quality Software with Requirements Traceability and Management Tools by kovair

VIEWS: 6 PAGES: 1

More Info
									Ensure Quality Software with Requirements Traceability and Management Tools


The software development lifecycle comprises of six phases namely requirements management, design,
implementation or coding, testing, deployment and maintenance. Of these phases, one of the important
phases of software development life cycle is the requirements management as it is requirements that
form the foundation of quality software products. The development and the testing teams would be at a
loss without appropriate requirements. Thus, requirements management, which is “the process of
documenting, analyzing, tracing, prioritizing and agreeing on requirements and then controlling change
and communicating to relevant stakeholders”, is a continuous process throughout a project. The
purpose of requirements management is to make sure that the documents of an enterprise verify and
meet the needs and expectations of its clients, customers and internal or external stakeholders.

One of the important sub-disciplines of requirements management is requirements traceability, which is
concerned with documenting the life of a requirement. Requirements traceability is defined as “the
ability to describe and trace the life of a requirement, in both a forward and backward direction (e.g.
from its source, through its development and specification, to its actual deployment, and then into the
product cycle of ongoing refinement and iteration in any of these phases).” Requirements traceability
matrix helps the software development team to find the origin of each requirement and track the
changes made to each one.

With requirements management being an arduous process, the software development team needs a
good requirements management tool to capture a set of requirements, collaborate on their
development and trace implementation back to specifications. A traceability matrix is created by
associating requirements with the work products that satisfy them. Tests are associated with the
requirements on which they are based and the product is tested to meet the requirement. In
traceability, the relationship of driver to satisfier can be one-to-one, one-to-many, many-to-one, or
many-to-many. And with a good tool, it can all be done easily.

The requirements management tool helps to select a relation first and based on the relation selected,
the user can select customized filters for each of the entity associated with the relation that imposes a
level of filtration of the linked records. The records of one entity are displayed row-wise while those of
others are displayed column-wise. Furthermore, over the filtration imposed, the user can also select the
records that he/she would like to display. The available options are All, All with the orphans (having no
linked records using this selected relation) highlighted, Only orphans, and Records that have linked
records                                                                                              only.

Thus, with a good requirements management tool, the software development team can ensure that all
developers are working from the same playbook, no matter where they are located, and that there are
no costly last minute surprises. Moreover, the requirements traceability matrix gives a complete visual
representation of the entity items that are linked to one another by means of the relationships. Thus, a
best of the breed requirements management tool eases the workload of the software development
team.

Related Links - Application Lifecycle Management & JIRA Integration

								
To top