Tool Selection: A Practitioners View

1
Tool Selection A Practitioners View

• Stephen Boyd

2
Topic

• What are the essential (versus non-essential)
  ingredients in successfully managing the business
  requirements of any project?
• Is requirements management scaleable and if so,
  what are the tradeoffs?

3
Stephen Boyd

• Director of Softability (Sys Def/BRA)
• Systems Engineering Manager at EDI-Rail on
  Rolling Stock PPP
• Engineering Manager at Thales Australia on the
  FFG Upgrade Project
• RE/BRA at Raytheon on Air Warfare Destroyer
• RE/BRA at BAE Systems on IASSF
• Engineering Officer in the RAAF
• Conducting PhD at UTS (IT Faculty)

4
Overview

• Requirements Traceability
• Scaleable Requirements Management
• Actual Tool Selections
• RM Tool Survey Top 15
• Vitechs CORE HTML Demo
• Summary Questions

5
Requirements Traceability

• Requirements traceability is defined as the
  ability to describe and follow the life of a
  requirement, in both a forward and backward
  direction (i.e. from its origins, through its
  development and specification, to its subsequent
  deployment and use, and through periods of
  ongoing refinement and iteration in any of these
  phases) (Gotel 95)

6
Requirement - Example
7
Requirement Traceability
The Climate Control Subsystem shall monitor the
Temperature within each Car of the Train and
alert the driver when the Temperature of any Car
exceeds 28C
8
Data Model Example
9
Is the CMMI relevant here?

• CMMI (Capability Maturity Model Integration) is
  a process improvement maturity model for the
  development of products and services. It consists
  of best practices that address development and
  maintenance activities that cover the product
  lifecycle from conception through delivery and
  maintenance.

10
CMMI Process Areas
11
Scaleability CMMI
12
Scaleability My Experience
13
Requirements Management Tool Selection
14
RM Tools
15
INCOSE RM Tools Survey

• 15 MOST IMPORTANT (IMO)
• 3.1 Requirements derivation (req. to req., req.
  to analysis/text)
• 3.3 Bi-directional requirement linking to system
  elements
• 5.1 History of requirement changes, who, what,
  when, where, why, how
• 5.2 Baseline/Version control
• 5.3 Access control (modification, viewing, etc.)
• 6.1 Standard specification output (if so, what
  kind)
• 6.6.3 Other ad hoc queries searches
• 7.1 Support of concurrent review, markup,
  comment
• 8.1.1 Interfaces to other tools?
• 8.1.4 Import of existing data from various
  standard file formats
• 8.2.2. Consistency/comparison checking between
  same-tool datasets
• 10.5 Executable via scripts (recordable) or
  macros
• 10.6 Web browser interface?
• 12.4 On-line help
• 13.1 Tool-specific training classes
• http//www.paper-review.com/tools/rms/read.php

16
CORE HTML Demo
17
Summary

• Requirements Management is scaleable
• Organisational Maturity (e.g. CMMI)
• Practical Experience (whats important)
• Contractual Requirements (e.g. Safety)
• Prioritise Survey Questions before using RM Tool
  Surveys
• Dont just buy tools Design a Data Model

18
Questions?

• Contact Details
• Stephen Boyd
• E sboyd_at_softability.com.au
• M 0404 066 478
• W www.softability.com.au