Tool support
Objectives
To explain the tool categories used in requirements engineering and their basic characteristics.
To explain the advantages and disadvantages of the use of tools in requirements engineering.
To describe typical representatives of the different tool categories.
To apply the basic procedure for choosing and implementing of the tool.
Motivation for use of tools
Support for managing and evaluating requirements
Structuring of requirements
Implementation of traceability
Automated checks
Centralized information accessible to all stakeholder
Data security
Definition of views and reports
Input and defined processing of requirements
Categories of tools
There is no such thing as “the best tool”
Office tools – but one best fitting
Requirements management tools ▪ the organization
▪ the actual project
Modelling tools
Issue management tools
Configuration management tools
Integrated tool suites
Knowledge management tools (e.g. Wiki)
Basic features of RM-tools
Manage various information
Manage logical relationships between information
Identify artifacts uniquely
Make information accessible flexibility and securely, e.g. through access control
Support views over the data
Organize the information, e.g. through assignment of attributes and formation of hierarchies
Generate report over the information
Generate documents out of the information
Use of tools in process
XYZ Office Drawing
Tools Tools Tools
Proj. Mgmt Config Mgmt
RM Tools
System
Change
Project and Document Mgmt
Q Mgmt Quality Mgmt System
System Revision-and-Change-Ma
Management nagement
Development
Test Mgmt Modelling Test Design Development
Tools Tools Tools Tools
Office tools
Examples
Text processing
Spreadsheet calculation
Drawing and presentation tools
Local data base application
Requirements management tools
Examples
IBM Rational RequisitePro
IBM Rational DOORS
Serena Dimension RM
Sparx Systems RaQuest
Visure IRqA
Outdated – but still in use
Have a look at a state-of-the-art tool: rational
collaborative lifecycle manager
Rational Collaborative Lifecycle Manager
IBM Rational Team Concert,
IBM Rational Quality Manager,
IBM Rational Requirements Composer
Based on Jazz (which is derived from the Eclipse community)
https://youtube.com/watch?feature+player_embedded&v=l_W5nkG6iAE
Modelling tools
Examples
SA/SD, e.g.
microtool CASE/4/0
UML tools, e.g.
Star UML
SparxSystems Enterprise Architect
NoMagic MagicDraw UML
IBM Rational Rhapsody
IBM Rational Software Architect
Process modeling tools, e.g.
Scheer ARIS Toolset
Good free tools
Visual Paradigm
Astha Communicty
Modelling tools
Examples
Atlassian JIRA
Mozilla Bugzilla
MantisBT
Seapine Testtrack Pro
Source for information about these tools, e.g.
http://www.testingfaqs.org/t-track.html
Configuration management tools
Examples
CollabNet Subversion
Serena ChangeMan
Serena Dimension
Seapine Surround SCM
IBM Rational ClearCase
MKS Integrity
Integrated tool suites
Examples
Polarion
microtool inStep
HP Quality Centre
Microsoft Team Foundation Server
(TFS)
Aspects to be considered when introducing
RM-tools
▪ Consider necessary resources.
▪ Avoid risks by means of pilot projects.
▪ Evaluation according to defined criteria.
▪ Take into account costs beyond license costs.
▪ Instruct employees.
Generic process for introducing the tools
6
7 Pilot
1
Roll-Out
Stake-hol
Problem
der
5 Review
2 3
Practice
Concept Formulate
Selection 4
process Study
State-of-A
rt Proto-typi
ng
Introducing tools, step 2: process definition
and study of the state-of-art tools
Goal:
▪ Define the work processes to be supported.
▪ Understand the tools landscape.
Procedure
▪ Process development together with coworkers and experts.
▪ Differentiate the tool categories.
▪ Study the tool categories.
▪ Catalogues like: https://www.capterra.com/requirements-management-software/
▪ Asking the experts.
Introducing tools, step 3: selection
Goal:
▪ Create a prioritized list with few candidates for advanced evaluation.
Procedure
▪ Catalogue of criteria grouped by 7 views
▪ Project view: preparation, planning, execution
▪ User view: handling, roles, collaboration
▪ Product view:functionality, views, reports, traceability
▪ Process view: methodical support, activity protocol
▪ Technical view: integration, scalability, data security
▪ Economic view: procurement, implementation, maintenance
▪ Asking the tool vendor.
Introducing tools, step 4-6: prototyping,
stakeholder review, pilot
Goal:
▪ Secure the process support.
▪ Evaluate the benefit and acceptance of the tool in praxis
▪ Identify defects during operation.
▪ Understand reluctance of coworkers.
Procedure
▪ Adapt tool to the process.
▪ Run through the process with tool.
▪ Execute process with tool in the representative project.
▪ Evaluate findings and results and compare to earlier proceedings.
Introducing tools, step 7: roll out
Goal:
▪ Establish a broad usage of the chosen tool.
Procedure
▪ Plan and establish support.
▪ Train coworkers.
▪ Adapt tool individually.
▪ Check usage and results.
▪ Calculate costs with license costs, individual adaptations of the tool, training, support.
End of chapter
