gtdigital®

QMS TOOLS FOR REQUIREMENTS MANAGEMENT AND SOFTWARE DEVELOPMENT QA

J. Bellott, MSEE

Rev 3.0

 

Contents:

Introduction

HP Quality Center

Tracking and Reporting Capabilities

HP Quality Center components

Enterprise Management Software Development Support

TELEOGIC DOORS Requirements Management System

Software Modification and Change Control Tracking Tools (Example: Siebel)

BORLAND TOOLS - CaliberRM

CaliberRM

Useful Links

 

Introduction

 

In product development and test methodologies, documentation is hierarchical:

·        Requirements

·        Specifications

·        Test Plans

 

Automated tools permit businesses to manage release contents for multiple products, assigning software component versions and also re-usable tests to cover the requirements for multiple products, and to assess the risks and issues (defects) in product releases.

 

Using enterprise level tools, business planners can schedule development and testing of multiple projects more effectively by taking into account the status, defects, and tests needed for each product to plan and accomplish order (sales delivery) goals effectively.

HP Quality Center

 

HP Quality Center features include means to:

·        manage project requirements and their changes

·        track software development progress

·        Assess risk

·        Plan software release contents

 

HP Quality Center capabilities are analogous to Borland Project Lifecycle Management tools.

 

HP Quality center can be used across distributed organizations. HP Quality Center supports:

·        Centralized release management and version numbering of large software products across the organization.

·        Ability to assign versions of software components created in different groups to the builds for specific products.

·        Ability to assign versions of tests for software components to specific product releases, re-using existing tests and test scripts.

·        Ability to re-use tests and test scripts for different products.

·        Ability to keep track of bugs and defects for each product in a centralized database, based upon its specific software component versions and test script test status/results.

·        Risk assessment is possible for a given product release using this information.

 

All software components have their own version numbers. Tests and Test scripts are assigned their own release and version numbers also.

 

Tracking and Reporting Capabilities

Using linked information and database analysis, HP Quality Center provides the ability to assess:

·        Requirements coverage by units and modules the product comprises. Defects affecting requirements are visible.

·        Reporting capabilities provide ways to share info

·        Large QA efforts can make use of these tools across a network for collaboration to succeed.

·        Workflows through the lifecycle provide standardized repeatable methods.

 

By including tools supporting each portion of the product lifecycle, consistent, repeatable QA can be performed on software successfully. 

 

As with all development methodology tools, the ability to find defects more easily before production is a strong advantage.

 

HP Quality Center components

 

·        The Quality Center Foundation – basic platform for workflow rules. Can be configured for your business environment.

 

·        HP TestDirector (was in v9; now part of V10 without using this name)– Used to manage requirements, plan and schedule tests (assigning test assets to requirements), reporting results, and reporting on defects and issues to facilitate planning and risk assessment.

 

·        Functional Test components – permit advanced automated functional testing and regression testing. A special module supports enterprise IT applications.

 

·        HP Business Process Testing software – allows business analysts and other planners to analyze business use cases of software products and the process flows involved with creating multiple products (with insight into scheduling based upon status of all tests and components). This permits scheduling of test development to proceed in a manner which facilitates success across the product line and software release roll-out for multiple products (thanks to a single large QC repository of info available).

·        Using HP Quality Center, one can identify and schedule tests needed to address the impact of changes, so application quality is increased and risk is minimized.

 

Enterprise Management Software Development Support

§  HP Quality Center can make use of SAP and SOA extensions to support SAP, SOA, and Oracle® quality management.

§  As with all software developed using HP Quality Center, one can identify and schedule tests needed to address the impact of changes, so application quality is increased and risk is minimized.

 

§  HP Service Test components – An advanced quality management package, covering SOA test management, requirements, defects tracking, functional testing, regression testing and business process design validation.

 

TELEOGIC DOORS Requirements Management System

 

Teleogic Doors uses a database with linked, numbered sections for each product development milestone document; e.g. Market requirements, Engineering system requirements, hardware and software unit specifications, and test plan test cases. Each are numbered and linked together.

 

With doors, one can verify that a test case covers or “traces” back to each requirement or specification above.

 

One can also verify which section of specifications documents cover product system level requirements.

 

(the name “Doors” refers to the ability to jump or link between project hierarchical documents). This tool was introduced in the late 1990’s. It is best for product development and checking traceability of hierarchical documents.

 

Software Modification and Change Control Tracking Tools (Example: Siebel)

 

Tools in this category assist system developers by keeping track of software change requests and their status. Siebel is an example of a basic MR tracking tools. Siebel allows users to conveniently enter MR’s, assign priorities, and owners.

 

A project team member is assigned as MR change control administrator/tracker.

MR’s pass through a series of steps that are user definable, and may include:

 

Open (by originator)

·        UI (owner)

·        Fixed (new owner is tester)

·        Verified (owner

·        Closed (MR admin)

 

Other MR assignments might include:

·        Defer

 

In the case of defer, the project team leadership decides which release to phase changes into.

 

Useful information catalogued with entries in software change control databases include:

·        Description of problem

·        How to reproduce problem

·        Area impacted (as specific as possible; a software module)

·        Severity (critical, high, medium, low; or 1-4) – Critical changes require prompt investigation.

·        Impact of problem: who is affected where

·        Customer who reported problem and notes about their needs.

 

Siebel and other MR tracking tools allow users to print reports sorted by severity, status (open, UI, etc), and other fields.

 

As change control tracking on PBX and large ATM switch projects at Bell Labs and ViaGate Technologies, I used tools to track MR status and priorities. As senior systems engineer in the software development group at ViaGate, I was responsible for planning software release contents for a period of time early in the initial product shipment timeframe. This involved working with engineers, marketing and engineering management closely to evaluate status and make decisions about release contents for our ATM switch.

The ViaGate switch used 12 unix multiprocessing boards, and provided internet, video (CATV lineup), and VLAN access to up to 240 subscribers using set top boxes and VDSL modems. The switch was designed for use in basements, and connected to the telco by Sonet fibers.

 

ViaGate Product Description (Telecommunication Switch for Internet, VLAN, and Video Access to 240 Subscribers)

http://www.jbmsee.net/reslib/ViaGateNode.htm

 

BORLAND TOOLS - CaliberRM

 

Borland makes leading Windows software compiler IDE tools in competition with Microsoft.

Borland has entered the market with software lifecycle management tools.

 

Tools include these aspects of development:

·        Requirements definition and management

·        Testing, software release planning, and risk assesment

 

Borland’s testing and ASQ tools help automate planning/tracking in these areas:

·        Requirements based testing

·        Software Test Management (planning, documentation of test processes)

·        Software Development Metrics – to assist managers

·        Test Automation – tools to help automate developer (unit), functional (system and integration testing), and performance testing (product quality/verification). This is accomplished by tools that support each step in the workflow.

 

 

(from Borland site)

 

CaliberRM

 

During the fall of 2003, I attended a training and info seminar on Borland compilers and software development project tools. These tools assist requirements traceability, change tracking, release planning, and risk assessment. Borland has attempted to provide tools for each essential workflow step, allowing project managers to track status of large projects in an organization.

 

The CaliberRM tools is used for requirements management, and provides network based means to collaborate between users on large projects. CaliberRM allows users to enter detailed info about unit modules and their development status.

 

Borland also HP Quality Center components (The “Quality Center Foundation, “ HP TestDirector for HP Quality Center, and Extensions for SAP and SOA)

 

 

Useful Links

Doors

http://www.wbbinc.com/doors_requirements_management.html

 

HP Quality Center

http://h50281.www5.hp.com/software/index.html

 

Borland Project Management Tools

http://www.borland.com/us/solutions/requirements-definition-management/index.html