The$Quest$for$Ubiquity$ " e l o t " G l l y O g - - PowerPoint PPT Presentation

▶
the quest for ubiquity
SMART_READER_LITE
LIVE PREVIEW

The$Quest$for$Ubiquity$ " e l o t " G l l y O g - - PowerPoint PPT Presentation

May 02, 2023 128 likes •558 views

PowerPoint)Template:)crea1vecommons.org/licenses/by9nd /3.0" & " e " r a w , o S " r o f " p a m y " d t a i i l o b R a " e A c a r T s " m e s t y S "

slide-1
SLIDE 1

The$Quest$for$Ubiquity$

A " R

  • a

d m a p " f

  • r

" S

  • ,

w a r e " & " S y s t e m s " T r a c e a b i l i t y " R e s e a r c h "

O l l y " G

  • t

e l " J a n e " C l e l a n d > H u a n g " J a n e " H u ff m a n " H a y e s " A n d r e a " Z i s m a n " A l e x a n d e r " E g y e d " " P a u l " G r ü n b a c h e r " G i u l i a n

  • "

A n t

  • n

i

  • l

"

PowerPoint)Template:)crea1vecommons.org/licenses/by9nd/3.0"

slide-2
SLIDE 2

Outline$

  • MoMvaMon"
  • Where"are"we?"
  • Where"do"we"want"to"go?"
  • How"can"we"get"there?"
  • Are"we"there"yet?"

RE"2012" The"Quest"for"Ubiquity"

2$ Outline$

slide-3
SLIDE 3

“We're$on$a$road$to$nowhere$…”$

RE"2012" The"Quest"for"Ubiquity"

3$

>>Talking"Heads"

Outline$

slide-4
SLIDE 4

Outline$

  • MoMvaMon"
  • Where"are"we?"
  • Where"do"we"want"to"go?"
  • How"can"we"get"there?"
  • Are"we"there"yet?"

RE"2012" The"Quest"for"Ubiquity"

4$ Outline$

slide-5
SLIDE 5

Traceability$@$the$center$of$all$things$

RE"2012" The"Quest"for"Ubiquity"

5$

garyfcox.blogspot.com/2012/07/where9are9we9in9universe9let9me9show.html)

Outline$

slide-6
SLIDE 6

Outline$

  • MoMvaMon"
  • Where"are"we?"
  • Where"do"we"want"to"go?"
  • How"can"we"get"there?"
  • Are"we"there"yet?"

"

RE"2012" The"Quest"for"Ubiquity"

6$ Outline$

slide-7
SLIDE 7

A$community$vision$quest$

RE"2012" The"Quest"for"Ubiquity"

7$

crystalinks.com)

Outline$

slide-8
SLIDE 8

Outline$

  • MoMvaMon"
  • Where"are"we?"
  • Where"do"we"want"to"go?"
  • How$can$we$get$there?$
  • Are"we"there"yet?"

RE"2012" The"Quest"for"Ubiquity"

8$ Outline$

slide-9
SLIDE 9

Many$ways$to$climb$some$mountains$

RE"2012" The"Quest"for"Ubiquity"

9$ Outline$

sundayriver.com/TheMountain)

slide-10
SLIDE 10

Outline$

  • MoMvaMon"
  • Where"are"we?"
  • Where"do"we"want"to"go?"
  • How"can"we"get"there?"
  • Are"we"there"yet?"

"

RE"2012" The"Quest"for"Ubiquity"

10$of$#$ Outline$

slide-11
SLIDE 11

Progress?$

RE"2012" The"Quest"for"Ubiquity"

11$ Outline$

slide-12
SLIDE 12

Grand$challenges$

RE"2012" The"Quest"for"Ubiquity"

12$ MoRvaRon$

slide-13
SLIDE 13

Status$

RE"2012" The"Quest"for"Ubiquity"

13$ Where$R$ we?$

Trace""!""a""!""bil""! i""! ty:" www.coest.org/index.php/traceability/glossary)

slide-14
SLIDE 14

RE"2012" The"Quest"for"Ubiquity"

14$ Where$2$ go?$

2035$

Artwork)by)Melissa)Huang))

slide-15
SLIDE 15

Challenges$&$research$themes$(i)$

Σ$"Valued:"Strategic"priority"" (buy>in"&"commitment"to"implementaMon)"" P$"Purposed:"Requirements>driven"&"fit"for"purpose"" (prototypical"profiles"&"pa[erns)" ↔"Portable:"Exchanged,"merged"&"reused"" (unified"policies,"standards"&"language)" #$$Scalable:"Through>life"&"cross>boundary"" (levels"of"abstracMon"&"granularity)"

RE"2012" The"Quest"for"Ubiquity"

15$ Where$2$ go?$

slide-16
SLIDE 16

Challenges$&$research$themes$(ii)$

$"Cost\effecRve:"Return"is"adequate"in"relaMon"to"outlay"" (cost>benefit"models"for"analysis)" ∀$Configurable:"Compliant"with"changing"needs"" (semanMcally>rich"dynamic"specificaMons)" T$Trusted:$Of"dependable"quality"" (systemaMc"quality"assessment"&"assurance)" ∞!Ubiquitous:"Always"there"when"needed"" (integral"to"broader"processes"&"tool"support)""

RE"2012" The"Quest"for"Ubiquity"

16$ Where$2$ go?$

slide-17
SLIDE 17

Goals$($)$

  • Total"cost"of"traceability"throughout"a"project’s"life"is"computed,"

along"with"projected"ROI,"&"is"available"to"assess"potenMal" effecMveness"of"compeMng"traceability"soluMons"(G1)"

  • Just"enough"traceability"is"provided,"balancing"stakeholder"

requirements"for"traceability"with"resource"constraints"(G2)"

  • Perfect"middle"ground"between"creaMng"&"maintaining""

traceability"early"or"on"demand"is"a[ained"(G3)"

  • Lessons"learned"are"capitalized"upon,"so"cost>""

effecMveness"of"various"traceability"techniques,"methods"" &"tools"are"known"and"improved"upon"(G4)"

  • IntuiMve"user"interfaces"&"interacMon"mechanisms"enable""

process>related"cost"decisions"to"be"explored"&"altered"" at"all"stages"of"traceability"process"(G5)"

RE"2012" The"Quest"for"Ubiquity"

17$ How$2$get$ there?$

slide-18
SLIDE 18

Research$topics$($)$

  • Agree"upon"metrics"for"measuring"traceability"cost>effecMveness"(RT1)"
  • Understand"typical"cost"profile"of"traceability"outlay""
  • n"a"project"(RT2)"
  • Develop"means"to"associate"a"cost"&"a"benefit""

profile"for"individual"traces"(RT3)"

  • Create"decision"support"tools"&"impact"analysis""

tools"for"making"traceability"ROI"decisions"(RT4)"

  • Develop"benchmark"studies"for"evaluaMng""

cost>effecMveness"of"traceability"techniques"(RT5)"

  • Decrease"costs"&"improve"effecMveness""
  • f"traceability"techniques"(RT6)"

RE"2012" The"Quest"for"Ubiquity"

18$ How$2$get$ there?$

slide-19
SLIDE 19

Industry$pracRces$($)$

  • Consult"Traceability"Body"Of"Knowledge"(TBOK)"for"cost>

effecMveness"of"techniques"&"tools"(IP1)"

  • Use"decision"support"tools"to"explore"cost>benefit"of"mixed"

soluMons"(IP2)"

  • Track"Return"On"Investment"(ROI)"of"traceability"(IP3)"

RE"2012" The"Quest"for"Ubiquity"

19$ How$2$get$ there?$

slide-20
SLIDE 20

Terrain$

  • 8"challenges"&"research"themes"(one"ever"so"grand)"
  • 35"associated"goals"
  • 84"derived"requirements"
  • 52"research"topics"
  • 29"industry"adopMon"pracMces"

RE"2012" The"Quest"for"Ubiquity"

20$ How$2$get$ there?$

slide-21
SLIDE 21

Roadmapping$process$

RE"2012" The"Quest"for"Ubiquity"

21$of$#$ How$2$get$ there?$

slide-22
SLIDE 22

Roadmapping$process$

RE"2012" The"Quest"for"Ubiquity"

22$of$#$ How$2$get$ there?$

Specification Technique Process

What to trace & why

How to establish

& use traces Who, when & where of tracing

Thanks)) for)the)road) Mike!)

slide-23
SLIDE 23

Roadmapping$process$

RE"2012" The"Quest"for"Ubiquity"

23$of$#$ How$2$get$ there?$

Specification Technique Process

What to trace & why

How to establish

& use traces Who, when & where of tracing

slide-24
SLIDE 24

Roadmapping$process$

RE"2012" The"Quest"for"Ubiquity"

24$of$#$ How$2$get$ there?$

Specification Technique Process

What to trace & why

How to establish

& use traces Who, when & where of tracing

$6" $3" $1" $5" $2" $4" Cost-benefit of every trace Intelligent adaptive link creation & maintenance ROI-driven strategic planning Cost profiles for traceability solutions Benchmark experiments & data (eg cost-effectiveness of techniques, etc) Traceability metrics (eg cost-effectiveness, ROI, etc.)

slide-25
SLIDE 25

Roadmapping$process$

RE"2012" The"Quest"for"Ubiquity"

25$of$#$ How$2$get$ there?$

Specification Technique Process

What to trace & why

How to establish

& use traces Who, when & where of tracing

$6" $3" $1" $5" $2" $4" Cost-benefit of every trace Intelligent adaptive link creation & maintenance ROI-driven strategic planning Cost profiles for traceability solutions Benchmark experiments & data (eg cost-effectiveness of techniques, etc) Traceability metrics (eg cost-effectiveness, ROI, etc.) $1" $2,3" Consult"TBOK"for"cost> effecMveness"of" techniques"&"tools"" Use"decision"support"tools"to"explore"$"of"mixed"soluMons" Track"ROI"of"traceability"

"

slide-26
SLIDE 26

Specification Technique Process

What to trace & why

How to establish

& use traces Who, when & where of tracing #8

Artifact

  • ntology

Σ2

Trace representation & description language

↔2

Link semantics

P7

Terms & concepts Motivate & systematize gathering of empirical data

↔1

Traceability metrics (eg quality of trace, (cost) effectiveness, ROI, etc.)

P5, T2, $1 Σ1

Generic roles & responsibilities

#1

Traceability value propositions Measurement techniques (eg fit for purpose, performance, tracking ROI, etc)

T6

Cost profiles for traceability solutions

$2 P6

Trace quality required for use scenarios P1,2

↔4

Stakeholders, tasks & contexts Benchmark experiments & data (eg performance & cost- effectiveness of techniques, etc) Evidence & awareness of traceability (added) value

$5 #6,7 Σ4,5

Specification of intent (traceability information models)

∀1, ↔1 Σ3

Knowledge & skills to establish & use traceability

#3

Training materials Models of traceability process

T1 Understanding

  • f process

vulnerabilities Prototypical requirements profiles

P1,2

Patterns of implementation

∀1

Parameters of required traceability

#6, $6 #6,7 T7,$6

Evidence of quality, performance & cost- effectiveness

#2, 8,9

Quantity & diversity

  • f artifacts &

link types

P1

Support for end use & interaction Portfolio of approaches (improved link quality) T3 Contracts

↔3,7

Policies & standards

#3

Process frameworks

P3 Σ2

Data gathered & measured Trace across boundaries & systems of systems

#10 P6 ∞3 ∞1 ∞2

Embedded in process & tools One click tracing Executable specs Assess trace potential

∀3

Proposing traceability information models

$4

ROI-driven strategic planning

#4

Cost & quality-based granularity decisions Assess, reuse & integrate traces

↔ 5,6

Plug & play

#3 #5

Cost-benefit of every trace $3 Infer trust from quality & process data

T4

Balance continuous & on-demand approaches

$4

Traceability as a service

↔8

Visualization (quality, etc)

T5

Changing reqs & evolve profiles

∀ 2,4

Reconfigure models & realign traces

P4 T9

Self- healing smart traces Intelligent adaptive link creation & maintenance

∀2

Compliance checked models

↔2 T8

Monitor/improve trace quality@runtime

P1, #4 Σ1,2, 4,5 ∞1,2, 3,4 Σ3, ↔1

∀1,$1,# 1,T1,P2

#2,3, $2,3 ↔3, T2 ∀2,3, T3 P3, ↔4

Industry Practices

IP

Σ1 Aware of traceability value, trained & compensated Σ2 Traceability training & certification sought Σ3 Traceability demanded of software & systems Σ4 Traceability integral to college curricula Σ5 TBOK to determine traceability value propositions P1 Use & contribute to Traceability Body of Knowledge (TBOK) P2 Use profiles, contexts & patterns to design traceability solutions P3 Measure effectiveness of process

↔1 Define & use traceability

policies & standards

↔2 Use a unified representation or

language to describe traceability

↔3 Reuse & integrate traceability

from other projects

↔4 Professional agreement on policy,

standards, representation, terms, etc. #1 Traceability established from project

  • nset & through-life

#2 Traceability accounts for any type of media & project artifact #3 Visualizations to support traceability at different granularity levels #4 Datasets contributed to explore scale $1 Consult TBOK for cost-effectiveness of techniques & tools $2 Use decision support tools to explore $ of mixed solutions $3 Track ROI of traceability ∀1 Use traceability information models to specify intent ∀2 Traceability consistent on global & distributed projects ∀3 Individual practices heterogeneous yet compatible T1 Specify levels of traceability quality for user tasks T2 Data provided to determine trust

  • f traceability & its analyses

T3 Supply feedback on traceability quality unobtrusively ∞1 Traceability-enabled integrated development environments chosen ∞2 Traceability parameters configured, then established & evolved ∞3 Traceability is a by-product of engineering tasks ∞4 The “traceability problem” is no longer spoken of

slide-27
SLIDE 27

Specification Technique Process

Σ

P ↔

# $

∀ T

∞

What to trace & why

How to establish

& use traces Who, when & where of tracing #8

Artifact

  • ntology

Σ2

Trace representation & description language

↔2

Link semantics

P7

Terms & concepts Motivate & systematize gathering of empirical data

↔1

Traceability metrics (eg quality of trace, (cost) effectiveness, ROI, etc.)

P5, T2, $1 Σ1

Generic roles & responsibilities

#1

Traceability value propositions Measurement techniques (eg fit for purpose, performance, tracking ROI, etc)

T6

Cost profiles for traceability solutions

$2 P6

Trace quality required for use scenarios P1,2

↔4

Stakeholders, tasks & contexts Benchmark experiments & data (eg performance & cost- effectiveness of techniques, etc) Evidence & awareness of traceability (added) value

$5 #6,7 Σ4,5

Specification of intent (traceability information models)

∀1, ↔1 Σ3

Knowledge & skills to establish & use traceability

#3

Training materials Models of traceability process

T1 Understanding

  • f process

vulnerabilities Prototypical requirements profiles

P1,2

Patterns of implementation

∀1

Parameters of required traceability

#6, $6 #6,7 T7,$6

Evidence of quality, performance & cost- effectiveness

#2, 8,9

Quantity & diversity

  • f artifacts &

link types

P1

Support for end use & interaction Portfolio of approaches (improved link quality) T3 Contracts

↔3,7

Policies & standards

#3

Process frameworks

P3 Σ2

Data gathered & measured Trace across boundaries & systems of systems

#10 P6 ∞3 ∞1 ∞2

Embedded in process & tools One click tracing Executable specs Assess trace potential

∀3

Proposing traceability information models

$4

ROI-driven strategic planning

#4

Cost & quality-based granularity decisions Assess, reuse & integrate traces

↔ 5,6

Plug & play

#3 #5

Cost-benefit of every trace $3 Infer trust from quality & process data

T4

Balance continuous & on-demand approaches

$4

Traceability as a service

↔8

Visualization (quality, etc)

T5

Changing reqs & evolve profiles

∀ 2,4

Reconfigure models & realign traces

P4 T9

Self- healing smart traces Intelligent adaptive link creation & maintenance

∀2

Compliance checked models

↔2 T8

Monitor/improve trace quality@runtime

P1, #4 Σ1,2, 4,5 ∞1,2, 3,4 Σ3, ↔1

∀1,$1,# 1,T1,P2

#2,3, $2,3 ↔3, T2 ∀2,3, T3 P3, ↔4

Σ Valued: Strategic priority (buy-in & commitment to implementation) P Purposed: Requirements-driven & fit for purpose (prototypical profiles & patterns) ↔ Portable: Exchanged, merged & reused (unified policies, standards & language) # Scalable: Through-life & cross-boundary (levels of abstraction & granularity) $ Cost-effective: Return is adequate in relation to outlay (cost-benefit models for analysis) ∀ Configurable: Compliant with changing needs (semantically-rich dynamic specifications) T Trusted: Of dependable quality (systematic quality assessment & assurance) ∞ Ubiquitous: Always there when needed (integral to broader processes & tool support)

“Well,"we"know"where"we're"goin’”" " ">>Talking"Heads" "

Industry Practices

IP

Σ1 Aware of traceability value, trained & compensated Σ2 Traceability training & certification sought Σ3 Traceability demanded of software & systems Σ4 Traceability integral to college curricula Σ5 TBOK to determine traceability value propositions P1 Use & contribute to Traceability Body of Knowledge (TBOK) P2 Use profiles, contexts & patterns to design traceability solutions P3 Measure effectiveness of process

↔1 Define & use traceability

policies & standards

↔2 Use a unified representation or

language to describe traceability

↔3 Reuse & integrate traceability

from other projects

↔4 Professional agreement on policy,

standards, representation, terms, etc. #1 Traceability established from project

  • nset & through-life

#2 Traceability accounts for any type of media & project artifact #3 Visualizations to support traceability at different granularity levels #4 Datasets contributed to explore scale $1 Consult TBOK for cost-effectiveness of techniques & tools $2 Use decision support tools to explore $ of mixed solutions $3 Track ROI of traceability ∀1 Use traceability information models to specify intent ∀2 Traceability consistent on global & distributed projects ∀3 Individual practices heterogeneous yet compatible T1 Specify levels of traceability quality for user tasks T2 Data provided to determine trust

  • f traceability & its analyses

T3 Supply feedback on traceability quality unobtrusively ∞1 Traceability-enabled integrated development environments chosen ∞2 Traceability parameters configured, then established & evolved ∞3 Traceability is a by-product of engineering tasks ∞4 The “traceability problem” is no longer spoken of

slide-28
SLIDE 28

Specification Technique Process

Σ

P ↔

# $

∀ T

∞

What to trace & why

How to establish

& use traces Who, when & where of tracing

TBOK

Disciplined multi-pronged capability Just enough

Autonomic Inside #8

Artifact

  • ntology

Σ2

Trace representation & description language

↔2

Link semantics

P7

Terms & concepts Motivate & systematize gathering of empirical data

↔1

Traceability metrics (eg quality of trace, (cost) effectiveness, ROI, etc.)

P5, T2, $1 Σ1

Generic roles & responsibilities

#1

Traceability value propositions Measurement techniques (eg fit for purpose, performance, tracking ROI, etc)

T6

Cost profiles for traceability solutions

$2 P6

Trace quality required for use scenarios P1,2

↔4

Stakeholders, tasks & contexts Benchmark experiments & data (eg performance & cost- effectiveness of techniques, etc) Evidence & awareness of traceability (added) value

$5 #6,7 Σ4,5

Specification of intent (traceability information models)

∀1, ↔1 Σ3

Knowledge & skills to establish & use traceability

#3

Training materials Models of traceability process

T1 Understanding

  • f process

vulnerabilities Prototypical requirements profiles

P1,2

Patterns of implementation

∀1

Parameters of required traceability

#6, $6 #6,7 T7,$6

Evidence of quality, performance & cost- effectiveness

#2, 8,9

Quantity & diversity

  • f artifacts &

link types

P1

Support for end use & interaction Portfolio of approaches (improved link quality) T3 Contracts

↔3,7

Policies & standards

#3

Process frameworks

P3 Σ2

Data gathered & measured Trace across boundaries & systems of systems

#10 P6 ∞3 ∞1 ∞2

Embedded in process & tools One click tracing Executable specs Assess trace potential

∀3

Proposing traceability information models

$4

ROI-driven strategic planning

#4

Cost & quality-based granularity decisions Assess, reuse & integrate traces

↔ 5,6

Plug & play

#3 #5

Cost-benefit of every trace $3 Infer trust from quality & process data

T4

Balance continuous & on-demand approaches

$4

Traceability as a service

↔8

Visualization (quality, etc)

T5

Changing reqs & evolve profiles

∀ 2,4

Reconfigure models & realign traces

P4 T9

Self- healing smart traces Intelligent adaptive link creation & maintenance

∀2

Compliance checked models

↔2 T8

Monitor/improve trace quality@runtime

P1, #4 Σ1,2, 4,5 ∞1,2, 3,4 Σ3, ↔1

∀1,$1,# 1,T1,P2

#2,3, $2,3 ↔3, T2 ∀2,3, T3 P3, ↔4

Σ Valued: Strategic priority (buy-in & commitment to implementation) P Purposed: Requirements-driven & fit for purpose (prototypical profiles & patterns) ↔ Portable: Exchanged, merged & reused (unified policies, standards & language) # Scalable: Through-life & cross-boundary (levels of abstraction & granularity) $ Cost-effective: Return is adequate in relation to outlay (cost-benefit models for analysis) ∀ Configurable: Compliant with changing needs (semantically-rich dynamic specifications) T Trusted: Of dependable quality (systematic quality assessment & assurance) ∞ Ubiquitous: Always there when needed (integral to broader processes & tool support) Industry Practices

IP

Σ1 Aware of traceability value, trained & compensated Σ2 Traceability training & certification sought Σ3 Traceability demanded of software & systems Σ4 Traceability integral to college curricula Σ5 TBOK to determine traceability value propositions P1 Use & contribute to Traceability Body of Knowledge (TBOK) P2 Use profiles, contexts & patterns to design traceability solutions P3 Measure effectiveness of process

↔1 Define & use traceability

policies & standards

↔2 Use a unified representation or

language to describe traceability

↔3 Reuse & integrate traceability

from other projects

↔4 Professional agreement on policy,

standards, representation, terms, etc. #1 Traceability established from project

  • nset & through-life

#2 Traceability accounts for any type of media & project artifact #3 Visualizations to support traceability at different granularity levels #4 Datasets contributed to explore scale $1 Consult TBOK for cost-effectiveness of techniques & tools $2 Use decision support tools to explore $ of mixed solutions $3 Track ROI of traceability ∀1 Use traceability information models to specify intent ∀2 Traceability consistent on global & distributed projects ∀3 Individual practices heterogeneous yet compatible T1 Specify levels of traceability quality for user tasks T2 Data provided to determine trust

  • f traceability & its analyses

T3 Supply feedback on traceability quality unobtrusively ∞1 Traceability-enabled integrated development environments chosen ∞2 Traceability parameters configured, then established & evolved ∞3 Traceability is a by-product of engineering tasks ∞4 The “traceability problem” is no longer spoken of

slide-29
SLIDE 29

Specification Technique Process

Σ

P ↔

# $

∀ T

∞

What to trace & why

How to establish

& use traces Who, when & where of tracing

TBOK

Disciplined multi-pronged capability Just enough

Autonomic Inside #8

Artifact

  • ntology

Σ2

Trace representation & description language

↔2

Link semantics

P7

Terms & concepts Motivate & systematize gathering of empirical data

↔1

Traceability metrics (eg quality of trace, (cost) effectiveness, ROI, etc.)

P5, T2, $1 Σ1

Generic roles & responsibilities

#1

Traceability value propositions Measurement techniques (eg fit for purpose, performance, tracking ROI, etc)

T6

Cost profiles for traceability solutions

$2 P6

Trace quality required for use scenarios P1,2

↔4

Stakeholders, tasks & contexts Benchmark experiments & data (eg performance & cost- effectiveness of techniques, etc) Evidence & awareness of traceability (added) value

$5 #6,7 Σ4,5

Specification of intent (traceability information models)

∀1, ↔1 Σ3

Knowledge & skills to establish & use traceability

#3

Training materials Models of traceability process

T1 Understanding

  • f process

vulnerabilities Prototypical requirements profiles

P1,2

Patterns of implementation

∀1

Parameters of required traceability

#6, $6 #6,7 T7,$6

Evidence of quality, performance & cost- effectiveness

#2, 8,9

Quantity & diversity

  • f artifacts &

link types

P1

Support for end use & interaction Portfolio of approaches (improved link quality) T3 Contracts

↔3,7

Policies & standards

#3

Process frameworks

P3 Σ2

Data gathered & measured Trace across boundaries & systems of systems

#10 P6 ∞3 ∞1 ∞2

Embedded in process & tools One click tracing Executable specs Assess trace potential

∀3

Proposing traceability information models

$4

ROI-driven strategic planning

#4

Cost & quality-based granularity decisions Assess, reuse & integrate traces

↔ 5,6

Plug & play

#3 #5

Cost-benefit of every trace $3 Infer trust from quality & process data

T4

Balance continuous & on-demand approaches

$4

Traceability as a service

↔8

Visualization (quality, etc)

T5

Changing reqs & evolve profiles

∀ 2,4

Reconfigure models & realign traces

P4 T9

Self- healing smart traces Intelligent adaptive link creation & maintenance

∀2

Compliance checked models

↔2 T8

Monitor/improve trace quality@runtime

P1, #4 Σ1,2, 4,5 ∞1,2, 3,4 Σ3, ↔1

∀1,$1,# 1,T1,P2

#2,3, $2,3 ↔3, T2 ∀2,3, T3 2012 2015 2020 2030 2035+ P3, ↔4

Σ Valued: Strategic priority (buy-in & commitment to implementation) P Purposed: Requirements-driven & fit for purpose (prototypical profiles & patterns) ↔ Portable: Exchanged, merged & reused (unified policies, standards & language) # Scalable: Through-life & cross-boundary (levels of abstraction & granularity) $ Cost-effective: Return is adequate in relation to outlay (cost-benefit models for analysis) ∀ Configurable: Compliant with changing needs (semantically-rich dynamic specifications) T Trusted: Of dependable quality (systematic quality assessment & assurance) ∞ Ubiquitous: Always there when needed (integral to broader processes & tool support) Industry Practices

IP

Σ1 Aware of traceability value, trained & compensated Σ2 Traceability training & certification sought Σ3 Traceability demanded of software & systems Σ4 Traceability integral to college curricula Σ5 TBOK to determine traceability value propositions P1 Use & contribute to Traceability Body of Knowledge (TBOK) P2 Use profiles, contexts & patterns to design traceability solutions P3 Measure effectiveness of process

↔1 Define & use traceability

policies & standards

↔2 Use a unified representation or

language to describe traceability

↔3 Reuse & integrate traceability

from other projects

↔4 Professional agreement on policy,

standards, representation, terms, etc. #1 Traceability established from project

  • nset & through-life

#2 Traceability accounts for any type of media & project artifact #3 Visualizations to support traceability at different granularity levels #4 Datasets contributed to explore scale $1 Consult TBOK for cost-effectiveness of techniques & tools $2 Use decision support tools to explore $ of mixed solutions $3 Track ROI of traceability ∀1 Use traceability information models to specify intent ∀2 Traceability consistent on global & distributed projects ∀3 Individual practices heterogeneous yet compatible T1 Specify levels of traceability quality for user tasks T2 Data provided to determine trust

  • f traceability & its analyses

T3 Supply feedback on traceability quality unobtrusively ∞1 Traceability-enabled integrated development environments chosen ∞2 Traceability parameters configured, then established & evolved ∞3 Traceability is a by-product of engineering tasks ∞4 The “traceability problem” is no longer spoken of

slide-30
SLIDE 30

Framework$

RE"2012" The"Quest"for"Ubiquity"

30$ How$2$get$ there?$

Technique$ Process$

Pervasion" Assurance" Accelerators" Building"Blocks" Groundwork" FoundaMons"

SpecificaRon$

slide-31
SLIDE 31

Specification Technique Process Σ Valued: Strategic priority (buy-in & commitment to implementation) P Purposed: Requirements-driven & fit for purpose (prototypical profiles & patterns) ↔ Portable: Exchanged, merged & reused (unified policies, standards & language) # Scalable: Through-life & cross-boundary (levels of abstraction & granularity) $ Cost-effective: Return is adequate in relation to outlay (cost-benefit models for analysis) ∀ Configurable: Compliant with changing needs (semantically-rich dynamic specifications) T Trusted: Of dependable quality (systematic quality assessment & assurance) ∞ Ubiquitous: Always there when needed (integral to broader processes & tool support)

Σ

P ↔

# $

∀ T

∞

Roadmap Framework

The Quest for Ubiquity: A Roadmap for Software & Systems Traceability Research

What to trace & why

How to establish

& use traces Who, when & where of tracing

TBOK

Disciplined multi-pronged capability Just enough

Autonomic Inside

Industry Practices Research Topics

See Table I in roadmap paper for description of research topic (RT) number of associated challenge #8

Artifact

  • ntology

Σ2

Trace representation & description language

↔2

Link semantics

#4 RT Σ2 Valued challenge Research Topic 2 (RT2)

Key to Road Signs

IP Scalable challenge Industry Practice 4 (See IP side tables ")

6 layers 8 traceability challenges lead to goals, requirements & topics for research

P7

Terms & concepts Motivate & systematize gathering of empirical data

↔1

Traceability metrics (eg quality of trace, (cost) effectiveness, ROI, etc.)

P5, T2, $1 Σ1

Generic roles & responsibilities

#1

Traceability value propositions Measurement techniques (eg fit for purpose, performance, tracking ROI, etc)

T6

Cost profiles for traceability solutions

$2 P6

Trace quality required for use scenarios P1,2

↔4

Stakeholders, tasks & contexts Benchmark experiments & data (eg performance & cost- effectiveness of techniques, etc) Evidence & awareness of traceability (added) value

$5 #6,7 Σ4,5

Specification of intent (traceability information models)

∀1, ↔1 Σ3

Knowledge & skills to establish & use traceability

#3

Training materials Models of traceability process

T1 Understanding

  • f process

vulnerabilities Prototypical requirements profiles

P1,2

Patterns of implementation

∀1

Parameters of required traceability

#6, $6 #6,7 T7,$6

Evidence of quality, performance & cost- effectiveness

#2, 8,9

Quantity & diversity

  • f artifacts &

link types

P1

Support for end use & interaction Portfolio of approaches (improved link quality) T3 Contracts

↔3,7

Policies & standards

#3

Process frameworks

P3 Σ2

Data gathered & measured Trace across boundaries & systems of systems

#10 P6 ∞3 ∞1 ∞2

Embedded in process & tools One click tracing Executable specs Assess trace potential

∀3

Proposing traceability information models

$4

ROI-driven strategic planning

#4

Cost & quality-based granularity decisions Assess, reuse & integrate traces

↔ 5,6

Plug & play

#3 #5

Cost-benefit of every trace $3 Infer trust from quality & process data

T4

Balance continuous & on-demand approaches

$4

Traceability as a service

↔8

Visualization (quality, etc)

T5

Changing reqs & evolve profiles

∀ 2,4

Reconfigure models & realign traces

P4 T9

Self- healing smart traces Intelligent adaptive link creation & maintenance

∀2

Compliance checked models

↔2 T8

Monitor/improve trace quality@runtime

P1, #4 Σ1,2, 4,5 ∞1,2, 3,4 Σ3, ↔1

∀1,$1,# 1,T1,P2

#2,3, $2,3 ↔3, T2 ∀2,3, T3 Challenges Research Themes Focal challenge for research Key outcome for industrial practice

Full automation or traceability built into wider practice Adapt dynamically to real-time feedback & learning Value-added practices, tools, analytical models & aids Advances with practices & tooling Explanatory models & baselines Agree on fundamentals & systematic data gathering Download from www.coest.org

2012 2015 2020 2030 2035+ P3, ↔4

∞1 Traceability-enabled integrated development environments chosen ∞2 Traceability parameters configured, then established & evolved ∞3 Traceability is a by-product of engineering tasks ∞4 The “traceability problem” is no longer spoken of Σ1 Aware of traceability value, trained & compensated Σ2 Traceability training & certification sought Σ3 Traceability demanded of software & systems Σ4 Traceability integral to college curricula Σ5 TBOK to determine traceability value propositions P1 Use & contribute to Traceability Body of Knowledge (TBOK) P2 Use profiles, contexts & patterns to design traceability solutions P3 Measure effectiveness of process

↔1 Define & use traceability

policies & standards

↔2 Use a unified representation or

language to describe traceability

↔3 Reuse & integrate traceability

from other projects

↔4 Professional agreement on policy,

standards, representation, terms, etc. #1 Traceability established from project

  • nset & through-life

#2 Traceability accounts for any type of media & project artifact #3 Visualizations to support traceability at different granularity levels #4 Datasets contributed to explore scale $1 Consult TBOK for cost-effectiveness of techniques & tools $2 Use decision support tools to explore $ of mixed solutions $3 Track ROI of traceability ∀1 Use traceability information models to specify intent ∀2 Traceability consistent on global & distributed projects ∀3 Individual practices heterogeneous yet compatible T1 Specify levels of traceability quality for user tasks T2 Data provided to determine trust

  • f traceability & its analyses

T3 Supply feedback on traceability quality unobtrusively

Technique Process

3 tracks

Pervasion Assurance Accelerators Building Blocks Groundwork Foundations Specification

slide-32
SLIDE 32

NavigaRng$the$roadmap$

  • Near>term:"FoundaMons"&"Groundwork"(<3"Years)"
  • Short>term:"Building"Blocks"(<5"Years)""
  • Mid>term:"Accelerators"(<15"Years)"
  • Long>term:"Assurance"(15+"Years)"
  • Final"DesMnaMon:"Pervasion"(2035?)"

RE"2012" The"Quest"for"Ubiquity"

32$ How$2$get$ there?$

slide-33
SLIDE 33

Specification Technique Process Σ Valued: Strategic priority (buy-in & commitment to implementation) P Purposed: Requirements-driven & fit for purpose (prototypical profiles & patterns) ↔ Portable: Exchanged, merged & reused (unified policies, standards & language) # Scalable: Through-life & cross-boundary (levels of abstraction & granularity) $ Cost-effective: Return is adequate in relation to outlay (cost-benefit models for analysis) ∀ Configurable: Compliant with changing needs (semantically-rich dynamic specifications) T Trusted: Of dependable quality (systematic quality assessment & assurance) ∞ Ubiquitous: Always there when needed (integral to broader processes & tool support)

Σ

P ↔

# $

∀ T

∞

Roadmap Framework

The Quest for Ubiquity: A Roadmap for Software & Systems Traceability Research

What to trace & why

How to establish

& use traces Who, when & where of tracing

TBOK

Disciplined multi-pronged capability Just enough

Autonomic Inside

Industry Practices Research Topics

See Table I in roadmap paper for description of research topic (RT) number of associated challenge #8

Artifact

  • ntology

Σ2

Trace representation & description language

↔2

Link semantics

#4 RT Σ2 Valued challenge Research Topic 2 (RT2)

Key to Road Signs

IP Scalable challenge Industry Practice 4 (See IP side tables ")

6 layers 8 traceability challenges lead to goals, requirements & topics for research

P7

Terms & concepts Motivate & systematize gathering of empirical data

↔1

Traceability metrics (eg quality of trace, (cost) effectiveness, ROI, etc.)

P5, T2, $1 Σ1

Generic roles & responsibilities

#1

Traceability value propositions Measurement techniques (eg fit for purpose, performance, tracking ROI, etc)

T6

Cost profiles for traceability solutions

$2 P6

Trace quality required for use scenarios P1,2

↔4

Stakeholders, tasks & contexts Benchmark experiments & data (eg performance & cost- effectiveness of techniques, etc) Evidence & awareness of traceability (added) value

$5 #6,7 Σ4,5

Specification of intent (traceability information models)

∀1, ↔1 Σ3

Knowledge & skills to establish & use traceability

#3

Training materials Models of traceability process

T1 Understanding

  • f process

vulnerabilities Prototypical requirements profiles

P1,2

Patterns of implementation

∀1

Parameters of required traceability

#6, $6 #6,7 T7,$6

Evidence of quality, performance & cost- effectiveness

#2, 8,9

Quantity & diversity

  • f artifacts &

link types

P1

Support for end use & interaction Portfolio of approaches (improved link quality) T3 Contracts

↔3,7

Policies & standards

#3

Process frameworks

P3 Σ2

Data gathered & measured Trace across boundaries & systems of systems

#10 P6 ∞3 ∞1 ∞2

Embedded in process & tools One click tracing Executable specs Assess trace potential

∀3

Proposing traceability information models

$4

ROI-driven strategic planning

#4

Cost & quality-based granularity decisions Assess, reuse & integrate traces

↔ 5,6

Plug & play

#3 #5

Cost-benefit of every trace $3 Infer trust from quality & process data

T4

Balance continuous & on-demand approaches

$4

Traceability as a service

↔8

Visualization (quality, etc)

T5

Changing reqs & evolve profiles

∀ 2,4

Reconfigure models & realign traces

P4 T9

Self- healing smart traces Intelligent adaptive link creation & maintenance

∀2

Compliance checked models

↔2 T8

Monitor/improve trace quality@runtime

P1, #4 Σ1,2, 4,5 ∞1,2, 3,4 Σ3, ↔1

∀1,$1,# 1,T1,P2

#2,3, $2,3 ↔3, T2 ∀2,3, T3 Challenges Research Themes Focal challenge for research Key outcome for industrial practice

Full automation or traceability built into wider practice Adapt dynamically to real-time feedback & learning Value-added practices, tools, analytical models & aids Advances with practices & tooling Explanatory models & baselines Agree on fundamentals & systematic data gathering Download from www.coest.org

2012 2015 2020 2030 2035+ P3, ↔4

∞1 Traceability-enabled integrated development environments chosen ∞2 Traceability parameters configured, then established & evolved ∞3 Traceability is a by-product of engineering tasks ∞4 The “traceability problem” is no longer spoken of Σ1 Aware of traceability value, trained & compensated Σ2 Traceability training & certification sought Σ3 Traceability demanded of software & systems Σ4 Traceability integral to college curricula Σ5 TBOK to determine traceability value propositions P1 Use & contribute to Traceability Body of Knowledge (TBOK) P2 Use profiles, contexts & patterns to design traceability solutions P3 Measure effectiveness of process

↔1 Define & use traceability

policies & standards

↔2 Use a unified representation or

language to describe traceability

↔3 Reuse & integrate traceability

from other projects

↔4 Professional agreement on policy,

standards, representation, terms, etc. #1 Traceability established from project

  • nset & through-life

#2 Traceability accounts for any type of media & project artifact #3 Visualizations to support traceability at different granularity levels #4 Datasets contributed to explore scale $1 Consult TBOK for cost-effectiveness of techniques & tools $2 Use decision support tools to explore $ of mixed solutions $3 Track ROI of traceability ∀1 Use traceability information models to specify intent ∀2 Traceability consistent on global & distributed projects ∀3 Individual practices heterogeneous yet compatible T1 Specify levels of traceability quality for user tasks T2 Data provided to determine trust

  • f traceability & its analyses

T3 Supply feedback on traceability quality unobtrusively

Technique Process

3 tracks

Pervasion Assurance Accelerators Building Blocks Groundwork Foundations Specification

Aim"to"achieve" traceability"that"is" valued" On"the"road"to" traceability"that"is" purposed"&"portable" Valued"in"pracMce"&" strategic"priority;" commitment"&"training" Emergence"

  • f"a"TBOK"

FoundaMons" Terms"&" concepts" Agree"on" arMfacts"we" want"to"trace" …and"on"the"nature"

  • f"these"traces"

Shared" schemes"for" OUR"domain" To"build"upon"foundaMons…" Understanding"of"traceability" stakeholders"&"their"(future)"needs" …"is"essenMal"groundwork" Understand"what" stakeholders"value" …"and"what"it"costs" to"achieve"this"

slide-34
SLIDE 34

NavigaRng$the$roadmap$

  • Near>term:"FoundaMons"&"Groundwork"(<3"Years)"
  • Short>term:"Building"Blocks"(<5"Years)""
  • Mid>term:"Accelerators"(<15"Years)"
  • Long>term:"Assurance"(15+"Years)"
  • Final"DesMnaMon:"Pervasion"(2035?)"

RE"2012" The"Quest"for"Ubiquity"

34$ How$2$get$ there?$

slide-35
SLIDE 35

NavigaRng$the$roadmap$

  • Near>term:"FoundaMons"&"Groundwork"(<3"Years)"
  • Short>term:"Building"Blocks"(<5"Years)""
  • Mid>term:"Accelerators"(<15"Years)"
  • Long>term:"Assurance"(15+"Years)"
  • Final"DesMnaMon:"Pervasion"(2035?)"

RE"2012" The"Quest"for"Ubiquity"

35$ How$2$get$ there?$

slide-36
SLIDE 36

Specification Technique Process Σ Valued: Strategic priority (buy-in & commitment to implementation) P Purposed: Requirements-driven & fit for purpose (prototypical profiles & patterns) ↔ Portable: Exchanged, merged & reused (unified policies, standards & language) # Scalable: Through-life & cross-boundary (levels of abstraction & granularity) $ Cost-effective: Return is adequate in relation to outlay (cost-benefit models for analysis) ∀ Configurable: Compliant with changing needs (semantically-rich dynamic specifications) T Trusted: Of dependable quality (systematic quality assessment & assurance) ∞ Ubiquitous: Always there when needed (integral to broader processes & tool support)

Σ

P ↔

# $

∀ T

∞

Roadmap Framework

The Quest for Ubiquity: A Roadmap for Software & Systems Traceability Research

What to trace & why

How to establish

& use traces Who, when & where of tracing

TBOK

Disciplined multi-pronged capability Just enough

Autonomic Inside

Industry Practices Research Topics

See Table I in roadmap paper for description of research topic (RT) number of associated challenge #8

Artifact

  • ntology

Σ2

Trace representation & description language

↔2

Link semantics

#4 RT Σ2 Valued challenge Research Topic 2 (RT2)

Key to Road Signs

IP Scalable challenge Industry Practice 4 (See IP side tables ")

6 layers 8 traceability challenges lead to goals, requirements & topics for research

P7

Terms & concepts Motivate & systematize gathering of empirical data

↔1

Traceability metrics (eg quality of trace, (cost) effectiveness, ROI, etc.)

P5, T2, $1 Σ1

Generic roles & responsibilities

#1

Traceability value propositions Measurement techniques (eg fit for purpose, performance, tracking ROI, etc)

T6

Cost profiles for traceability solutions

$2 P6

Trace quality required for use scenarios P1,2

↔4

Stakeholders, tasks & contexts Benchmark experiments & data (eg performance & cost- effectiveness of techniques, etc) Evidence & awareness of traceability (added) value

$5 #6,7 Σ4,5

Specification of intent (traceability information models)

∀1, ↔1 Σ3

Knowledge & skills to establish & use traceability

#3

Training materials Models of traceability process

T1 Understanding

  • f process

vulnerabilities Prototypical requirements profiles

P1,2

Patterns of implementation

∀1

Parameters of required traceability

#6, $6 #6,7 T7,$6

Evidence of quality, performance & cost- effectiveness

#2, 8,9

Quantity & diversity

  • f artifacts &

link types

P1

Support for end use & interaction Portfolio of approaches (improved link quality) T3 Contracts

↔3,7

Policies & standards

#3

Process frameworks

P3 Σ2

Data gathered & measured Trace across boundaries & systems of systems

#10 P6 ∞3 ∞1 ∞2

Embedded in process & tools One click tracing Executable specs Assess trace potential

∀3

Proposing traceability information models

$4

ROI-driven strategic planning

#4

Cost & quality-based granularity decisions Assess, reuse & integrate traces

↔ 5,6

Plug & play

#3 #5

Cost-benefit of every trace $3 Infer trust from quality & process data

T4

Balance continuous & on-demand approaches

$4

Traceability as a service

↔8

Visualization (quality, etc)

T5

Changing reqs & evolve profiles

∀ 2,4

Reconfigure models & realign traces

P4 T9

Self- healing smart traces Intelligent adaptive link creation & maintenance

∀2

Compliance checked models

↔2 T8

Monitor/improve trace quality@runtime

P1, #4 Σ1,2, 4,5 ∞1,2, 3,4 Σ3, ↔1

∀1,$1,# 1,T1,P2

#2,3, $2,3 ↔3, T2 ∀2,3, T3 Challenges Research Themes Focal challenge for research Key outcome for industrial practice

Full automation or traceability built into wider practice Adapt dynamically to real-time feedback & learning Value-added practices, tools, analytical models & aids Advances with practices & tooling Explanatory models & baselines Agree on fundamentals & systematic data gathering Download from www.coest.org

2012 2015 2020 2030 2035+ P3, ↔4

∞1 Traceability-enabled integrated development environments chosen ∞2 Traceability parameters configured, then established & evolved ∞3 Traceability is a by-product of engineering tasks ∞4 The “traceability problem” is no longer spoken of Σ1 Aware of traceability value, trained & compensated Σ2 Traceability training & certification sought Σ3 Traceability demanded of software & systems Σ4 Traceability integral to college curricula Σ5 TBOK to determine traceability value propositions P1 Use & contribute to Traceability Body of Knowledge (TBOK) P2 Use profiles, contexts & patterns to design traceability solutions P3 Measure effectiveness of process

↔1 Define & use traceability

policies & standards

↔2 Use a unified representation or

language to describe traceability

↔3 Reuse & integrate traceability

from other projects

↔4 Professional agreement on policy,

standards, representation, terms, etc. #1 Traceability established from project

  • nset & through-life

#2 Traceability accounts for any type of media & project artifact #3 Visualizations to support traceability at different granularity levels #4 Datasets contributed to explore scale $1 Consult TBOK for cost-effectiveness of techniques & tools $2 Use decision support tools to explore $ of mixed solutions $3 Track ROI of traceability ∀1 Use traceability information models to specify intent ∀2 Traceability consistent on global & distributed projects ∀3 Individual practices heterogeneous yet compatible T1 Specify levels of traceability quality for user tasks T2 Data provided to determine trust

  • f traceability & its analyses

T3 Supply feedback on traceability quality unobtrusively

Technique Process

3 tracks

Pervasion Assurance Accelerators Building Blocks Groundwork Foundations Specification

…"on"the"road"to"ubiquity" When"traceability"is"configured"as" wanted"&"fully"trusted,"we"are"…" PracMMoners"expect"traceability"“inside”"all"projects" Researchers"focus"on"fully"executable"traceability"specificaMons," making"traceability"pervasive"to"all"SSE"processes,"&"ensuring"its" techniques"are"integral"to"tool"support"

slide-37
SLIDE 37

Interim$paths$

  • Specific"research"agendas"

RE"2012" The"Quest"for"Ubiquity"

37$ How$2$get$ there?$

sundayriver.com/TheMountain)

slide-38
SLIDE 38

Specification Technique Process Σ Valued: Strategic priority (buy-in & commitment to implementation) P Purposed: Requirements-driven & fit for purpose (prototypical profiles & patterns) ↔ Portable: Exchanged, merged & reused (unified policies, standards & language) # Scalable: Through-life & cross-boundary (levels of abstraction & granularity) $ Cost-effective: Return is adequate in relation to outlay (cost-benefit models for analysis) ∀ Configurable: Compliant with changing needs (semantically-rich dynamic specifications) T Trusted: Of dependable quality (systematic quality assessment & assurance) ∞ Ubiquitous: Always there when needed (integral to broader processes & tool support)

Σ

P ↔

# $

∀ T

∞

Roadmap Framework

The Quest for Ubiquity: A Roadmap for Software & Systems Traceability Research

What to trace & why

How to establish

& use traces Who, when & where of tracing

TBOK

Disciplined multi-pronged capability Just enough

Autonomic Inside

Industry Practices Research Topics

See Table I in roadmap paper for description of research topic (RT) number of associated challenge #8

Artifact

  • ntology

Σ2

Trace representation & description language

↔2

Link semantics

#4 RT Σ2 Valued challenge Research Topic 2 (RT2)

Key to Road Signs

IP Scalable challenge Industry Practice 4 (See IP side tables ")

6 layers 8 traceability challenges lead to goals, requirements & topics for research

P7

Terms & concepts Motivate & systematize gathering of empirical data

↔1

Traceability metrics (eg quality of trace, (cost) effectiveness, ROI, etc.)

P5, T2, $1 Σ1

Generic roles & responsibilities

#1

Traceability value propositions Measurement techniques (eg fit for purpose, performance, tracking ROI, etc)

T6

Cost profiles for traceability solutions

$2 P6

Trace quality required for use scenarios P1,2

↔4

Stakeholders, tasks & contexts Benchmark experiments & data (eg performance & cost- effectiveness of techniques, etc) Evidence & awareness of traceability (added) value

$5 #6,7 Σ4,5

Specification of intent (traceability information models)

∀1, ↔1 Σ3

Knowledge & skills to establish & use traceability

#3

Training materials Models of traceability process

T1 Understanding

  • f process

vulnerabilities Prototypical requirements profiles

P1,2

Patterns of implementation

∀1

Parameters of required traceability

#6, $6 #6,7 T7,$6

Evidence of quality, performance & cost- effectiveness

#2, 8,9

Quantity & diversity

  • f artifacts &

link types

P1

Support for end use & interaction Portfolio of approaches (improved link quality) T3 Contracts

↔3,7

Policies & standards

#3

Process frameworks

P3 Σ2

Data gathered & measured Trace across boundaries & systems of systems

#10 P6 ∞3 ∞1 ∞2

Embedded in process & tools One click tracing Executable specs Assess trace potential

∀3

Proposing traceability information models

$4

ROI-driven strategic planning

#4

Cost & quality-based granularity decisions Assess, reuse & integrate traces

↔ 5,6

Plug & play

#3 #5

Cost-benefit of every trace $3 Infer trust from quality & process data

T4

Balance continuous & on-demand approaches

$4

Traceability as a service

↔8

Visualization (quality, etc)

T5

Changing reqs & evolve profiles

∀ 2,4

Reconfigure models & realign traces

P4 T9

Self- healing smart traces Intelligent adaptive link creation & maintenance

∀2

Compliance checked models

↔2 T8

Monitor/improve trace quality@runtime

P1, #4 Σ1,2, 4,5 ∞1,2, 3,4 Σ3, ↔1

∀1,$1,# 1,T1,P2

#2,3, $2,3 ↔3, T2 ∀2,3, T3 Challenges Research Themes Focal challenge for research Key outcome for industrial practice

Full automation or traceability built into wider practice Adapt dynamically to real-time feedback & learning Value-added practices, tools, analytical models & aids Advances with practices & tooling Explanatory models & baselines Agree on fundamentals & systematic data gathering Download from www.coest.org

2012 2015 2020 2030 2035+ P3, ↔4

∞1 Traceability-enabled integrated development environments chosen ∞2 Traceability parameters configured, then established & evolved ∞3 Traceability is a by-product of engineering tasks ∞4 The “traceability problem” is no longer spoken of Σ1 Aware of traceability value, trained & compensated Σ2 Traceability training & certification sought Σ3 Traceability demanded of software & systems Σ4 Traceability integral to college curricula Σ5 TBOK to determine traceability value propositions P1 Use & contribute to Traceability Body of Knowledge (TBOK) P2 Use profiles, contexts & patterns to design traceability solutions P3 Measure effectiveness of process

↔1 Define & use traceability

policies & standards

↔2 Use a unified representation or

language to describe traceability

↔3 Reuse & integrate traceability

from other projects

↔4 Professional agreement on policy,

standards, representation, terms, etc. #1 Traceability established from project

  • nset & through-life

#2 Traceability accounts for any type of media & project artifact #3 Visualizations to support traceability at different granularity levels #4 Datasets contributed to explore scale $1 Consult TBOK for cost-effectiveness of techniques & tools $2 Use decision support tools to explore $ of mixed solutions $3 Track ROI of traceability ∀1 Use traceability information models to specify intent ∀2 Traceability consistent on global & distributed projects ∀3 Individual practices heterogeneous yet compatible T1 Specify levels of traceability quality for user tasks T2 Data provided to determine trust

  • f traceability & its analyses

T3 Supply feedback on traceability quality unobtrusively

Technique Process

3 tracks

Pervasion Assurance Accelerators Building Blocks Groundwork Foundations Specification

Near"to"short>term"process>specific" Roles"&"responsibiliMes,"required" knowledge"&"skills,"training"materials" Short"to"mid>term"specificaMon>specific" Reuse"traces"in"new"contexts,"intelligent" adaptaMon,"self>aware"traces" Mid"to"long>term"technique>specific" TIMs,"specificaMon," proposals,""adaptaMon"

slide-39
SLIDE 39

You$have$arrived$@$your$desRnaRon$

RE"2012" The"Quest"for"Ubiquity"

39$ Arrived?$

  • 1st"a[empt"to"map"terrain"for"traceability"research""

(&"to"carve"a"road"through"it)"

  • Priority"(value"&"difficulty)"of"research"topics"–"triage"
  • Measuring"progress"–"classify"research"contribuMons"
  • Other"ways"to"organize"terrain"
  • Different"terrain"enMrely"
slide-40
SLIDE 40

On$the$road$to$traceability$ubiquity$…$

A"community"needs"to" pursue"research"that"fits" together"to"take"us"toward"a" shared"vision"of"the"future" " Research"communiMes"need" to"think"more"about"the"use"

  • f"roadmaps"&"the"role"they"

could"play"

RE"2012" The"Quest"for"Ubiquity"

40$ THE$ message$

Artwork)by)Melissa)Huang)) Roadmap)by)Olly,)Jane,)Jane,) Andrea,)Alexander,)Paul)&) Giuliano)

slide-41
SLIDE 41

Acknowledgments$

  • Thanks"to"all"parMcipants"of"2"traceability"workshops""

(NASA’s"IV&V"facility"2006,"&"Lexington,"Kentucky"2007)"

  • NASA"grant"#NNX06AD02G"&"NSF"grant"#0647443"
  • ParMcular"thanks"to"Alex"Dekhtyar"&"Jonathan"MaleMc"""

for"involvement"in"shaping"the"challenges"

RE"2012" The"Quest"for"Ubiquity"

41$ Thanks$

slide-42
SLIDE 42

Resources$

Gotel,"O.,"Cleland>Huang,"J.,"Huffman"Hayes,"J.,"Zisman,"A.," Egyed,"A.,"Grünbacher,"P.,"Dekhtyar,"A.,"Antoniol,"G."&"MaleMc,"J." The$Grand$Challenge$of$Traceability$(v1.0)"" Center"of"Excellence"for"So,ware"Traceability"Technical"Report" #CoEST>2011>001" June"14,"2011"" " Available"from:"ollygotel.com!

RE"2012" The"Quest"for"Ubiquity"

42$ What’s$the$ quesRon?$

  • lly@gotel.net)