IV&V Facility - Requirement Management and Traceability Tool
T
h
e
S
i
m
p
l
e
M
a
n
a
g
e
m
e
n
t
a
n
d
A
n
a
l
y
s
i
s
o
f
R
e
q
u
i
r
e
m
e
n
t
s
a
n
d
T
r
a
c
e
a
b
i
l
i
t
y
(
S
M
A
R
T
)
T
o
o
l
Travis Dawson
Michael Facemire
Charles Broadwater
G
e
n
e
s
i
s
2
T
h
e
N
e
e
d
•
Much of what IV&V does involves tracing (or evaluating
developer traces) of one artifact element to another, e.g.
–
Higher-level requirements (parents) to lower-level, dependent
requirements (children)
–
IV&V model elements to FSW requirements
–
Potentially, any life-cycle artifact element to any other
–
etc, etc, etc
•
The traces themselves are their own “objects” with their own
characteristics, fields, etc.
–
Want to capture IV&V analysis notes
–
Want to assert IV&V traces in addition to developer traces, and
distinguish between them
–
A link field in one item with a pointer to another item is not
sufficient
•
Analysis notes can lead to findings or to assurance evidence,
and we need a way to support these
•
We don’t need a database in which we enter our analysis
results, we need a tool to facilitate that analysis
3
C
o
n
c
e
p
t
u
a
l
U
s
e
r
R
e
q
u
i
r
e
m
e
n
t
s
•
Artifacts
–
Ability to represent a wide variety of artifacts
–
Ability to display artifacts with native formatting (graphics, etc.)
•
Facilitating analysis
–
Ability to attach IV&V-interest attributes to both parent and child
elements
–
Ability to capture attributes and analysis notes for reqts & traces
–
Support development of issues and assurance evidence
•
Visualization/Navigation
–
Ability to easily load and link various artifacts
–
Ability to see lists (with filtering) of elements for selection
–
Ability to view parent, child and trace simultaneously
•
Deployment
–
Ability to support multiple analysts in the same data set, often
geographically dispersed
–
Ability to support multiple projects without new development
–
Ability to represent custom fields without development
4
T
i
m
e
l
i
n
e
5
Antiquity
MER
IV&V
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
Analyst
Utopia
MER
RTA
“Tool”
Juno
RTAT
Proposed
as IV&V
Research
Initiative
Ares
IV&V
RTAT Extended
to include
graphics, UML
components
Variety of
customers,
including
MRO
,
SIRTF
,
Dawn
,
OCO
,
Deep
Impact
SMAP
SMART
RTA
Requirements Traceability Analysis
RTAT
A specific RTA tool
ORBIT
IV&V tool based on PTS Integrity (formerly MKS Integrity) to capture
issues (initially), requirements analysis (later), and risks (future)
ORBIT reqts
discovery/
trade study
ORBIT
Roll-Out
Ares
Pre-SMART
ESMDI
MAVEN
SMART
ICESat-2
SMART
M
A
V
E
N
S
M
A
R
T
6
•
Two viable
options
–
Submit a request for SWAT to make the necessary updates to
ORBIT
–
Reuse an existing in-house developed tool
•
Due to several factors, the team decided to re-use an
existing in-house developed tool
•
Several in-house options were considered; however, the
SMART tool developed for SMAP was determined to
offer the best solution for MAVEN
M
A
V
E
N
I
V
&
V
T
o
o
l
S
e
l
e
c
t
i
o
n
7
•
Requirements based - view any project requirement along with
supporting attributes
•
Ability to import requirements with embedded images
•
Ability to import issues from ORBIT and associate the issues with
analysis records
•
Microsoft Access frontend with SQL Server backend – supports
distributed users and real time data synchronization
•
Requirements traceability – for the selected requirement in focus
–
Display all parent requirements
–
Display all child requirements
–
Display all child requirements of the parent requirements
–
Add a recommended parent or child trace to any requirement
–
Add an analysis comment to any trace
–
Indicate whether a trace is valid
•
Requirements validation assessment form
–
Contains quality assessment and analysis note fields used in MKS
•
Built in filters
–
Filter on latest version only
–
Filter on assigned analyst or other custom requirement tag
–
Maintain multiple filters even if analyst manually filters another field
S
M
A
R
T
B
a
s
e
l
i
n
e
T
o
o
l
8
S
M
A
R
T
C
o
n
t
e
x
t
DOORS
MS Access
Front End
Rqmts & Traces
Analysts
Analyze Artifacts &
Record Results
Draft
Findings
Issues, &
Observations
9
TIM X-Refs
perl scripts
Build
Deliveries
(FSW & UT
Code)
SQL Server
Tables
SMART
A
n
a
l
y
s
i
s
F
o
r
m
10
I
n
-
P
r
o
c
e
s
s
E
n
h
a
n
c
e
m
e
n
t
s
•
Generalization of forms among artifact
types
–
Removal of requirement artifact as the only
left-hand artifact
•
Enhanced navigation
–
addition of list navigation
•
Allowing multiple instances of forms
11
C
o
n
f
i
g
u
r
a
b
l
e
A
n
a
l
y
s
i
s
F
o
r
m
12
E
x
a
m
p
l
e
:
R
e
q
u
i
r
e
m
e
n
t
s
t
o
S
c
e
n
a
r
i
o
s
13
M
u
l
t
i
p
l
e
A
n
a
l
y
s
i
s
F
o
r
m
s
14
S
w
a
p
p
i
n
g
L
e
f
t
a
n
d
R
i
g
h
t
S
i
d
e
15
U
s
e
r
R
e
q
u
i
r
e
m
e
n
t
s
R
e
p
o
r
t
C
a
r
d
16
F
u
t
u
r
e
o
f
S
M
A
R
T
17
P
o
t
e
n
t
i
a
l
E
n
h
a
n
c
e
m
e
n
t
s
•
Anything to bring report card grades up
•
Generalization across projects
•
Using common data model
•
Native-formatted requirements
–
OLE
–
html
•
Extend mapping targets
•
Simplify data structures
•
Better support for issue development
•
Better support for assurance evidence
18
O
w
n
e
r
s
h
i
p
•
Enterprise vs Project
•
Analysts vs SWAT
19
C
o
n
c
l
u
s
i
o
n
s
20
C
o
n
c
l
u
s
i
o
n
s
•
SMART is field-proven
–
Multiple projects, many issues generated
–
I assert a unique capability (currently
supported, traceability tool)
•
SMART has a large user and user-
developer base
•
SMART has had initial discussion with
SWAT on enterprise support
•
SMART has planned enhancements that
are progressing
21
B
a
c
k
u
p
C
h
a
r
t
s
22
S
M
A
R
T
Q
u
e
r
i
e
s
C
h
a
n
g
e
I
m
p
a
c
t
A
n
a
l
y
s
i
s
•
Changed Requirement Text (ObjectText)
•
New Requirements
•
Deleted Requirements
•
New Traces
•
Deleted Traces
23
F
a
c
t
o
r
s
B
e
h
i
n
d
T
o
o
l
S
e
l
e
c
t
i
o
n
24
•
Like MAVEN, SMAP was initially using MKS to support requirements
validation
–
Led to a nearly one-to-one mapping between the fields in MKS and the
requirements validation form in SMART
–
Analysts would already be familiar with fields
–
Made migrating analysis records from MKS to SMART straightforward
•
MAVEN and SMAP projects use DOORS for requirements and
traceability
–
Resulted in a database schema and features oriented towards handling artifacts
from DOORS
•
SMART now has a multimission pedigree
–
Instantiations of the tool used on Juno, ESMDI, Ares, ICESat-II, SMAP, and now
MAVEN – helping establish the framework for a common tool to be used on IV&V
projects
–
MAVEN benefits from multiple enhancements made to the tool to support the
various projects
–
Due to MAVEN inheriting analysts from Juno, there was already an experience
base with the tool and its architecture
•
SMART relies on a Microsoft Access frontend
–
Flexible architecture and easy to tailor and modify on the fly - does not require a
formal change request process
–
Considerable experience on the team with Access and database development
S
M
A
R
T
f
o
r
M
A
V
E
N
E
n
h
a
n
c
e
m
e
n
t
s
•
Added MAVEN-specific scoping qualifiers
•
Added fields to support change/impact analysis
•
Added several requirement fields to facilitate filters
•
Code analysis form
–
Allows analyst to trace one or more functions to a requirement
–
Analyst can select the function from dropdown list, which pre-
populates a code snippet field
–
Analyst can add comments on each trace, as well as comment
on the traceability overall if multiple functions are traced to the
requirement
•
Test validation form
–
Modeled after code analysis form
–
Instead of relying on user to trace test requirements, tool will use
developer provided traces
–
Designed to support unit test validation and acceptance test
validation tasks
25
F
u
t
u
r
e
E
n
h
a
n
c
e
m
e
n
t
s
•
Develop a form to support analysis of mini-
scenarios (basic form developed)
•
Develop a form to support the general
code inspection task
•
Provide broader coverage of AVT task
•
Conditional formatting based on various
flags
26
IV&V Facility, also known as the Simple Management and Analysis of Requirements and Traceability (SMART) tool, is designed to streamline the process of tracing and managing requirements in software development projects. The tool allows for tracking dependencies between different levels of requirements and model elements, capturing analysis notes, and distinguishing between developer traces and IV&V traces. It also supports the visualization and navigation of artifacts, deployment for multiple analysts and projects, and represents custom fields without the need for additional development.
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. Download presentation by click this link. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
E N D
Presentation Transcript
IV&V Facility The Simple Management and Analysis of Requirements and Traceability (SMART) Tool Travis Dawson Michael Facemire Charles Broadwater
IV&V Facility Genesis 2
The Need IV&V Facility Much of what IV&V does involves tracing (or evaluating developer traces) of one artifact element to another, e.g. Higher-level requirements (parents) to lower-level, dependent requirements (children) IV&V model elements to FSW requirements Potentially, any life-cycle artifact element to any other etc, etc, etc The traces themselves are their own objects with their own characteristics, fields, etc. Want to capture IV&V analysis notes Want to assert IV&V traces in addition to developer traces, and distinguish between them A link field in one item with a pointer to another item is not sufficient Analysis notes can lead to findings or to assurance evidence, and we need a way to support these We don t need a database in which we enter our analysis results, we need a tool to facilitate that analysis 3
Conceptual User Requirements IV&V Facility Artifacts Ability to represent a wide variety of artifacts Ability to display artifacts with native formatting (graphics, etc.) Facilitating analysis Ability to attach IV&V-interest attributes to both parent and child elements Ability to capture attributes and analysis notes for reqts & traces Support development of issues and assurance evidence Visualization/Navigation Ability to easily load and link various artifacts Ability to see lists (with filtering) of elements for selection Ability to view parent, child and trace simultaneously Deployment Ability to support multiple analysts in the same data set, often geographically dispersed Ability to support multiple projects without new development Ability to represent custom fields without development 4
Timeline IV&V Facility RTAT Proposed as IV&V Research Initiative RTAT Extended to include graphics, UML components ORBIT reqts discovery/ trade study MAVEN SMART MER RTA Tool ORBIT Roll-Out ICESat-2 SMART Variety of customers, including MRO, SIRTF, Dawn, OCO, Deep Impact Pre-SMART Ares IV&V MER IV&V Juno SMAP SMART ESMDI Analyst Utopia Ares Antiquity 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 RTA RTAT ORBIT Requirements Traceability Analysis A specific RTA tool IV&V tool based on PTS Integrity (formerly MKS Integrity) to capture issues (initially), requirements analysis (later), and risks (future) 5
IV&V Facility MAVEN SMART 6
MAVEN IV&V Tool Selection IV&V Facility Two viable options Submit a request for SWAT to make the necessary updates to ORBIT Reuse an existing in-house developed tool Due to several factors, the team decided to re-use an existing in-house developed tool Several in-house options were considered; however, the SMART tool developed for SMAP was determined to offer the best solution for MAVEN 7
SMART Baseline Tool IV&V Facility Requirements based - view any project requirement along with supporting attributes Ability to import requirements with embedded images Ability to import issues from ORBIT and associate the issues with analysis records Microsoft Access frontend with SQL Server backend supports distributed users and real time data synchronization Requirements traceability for the selected requirement in focus Display all parent requirements Display all child requirements Display all child requirements of the parent requirements Add a recommended parent or child trace to any requirement Add an analysis comment to any trace Indicate whether a trace is valid Requirements validation assessment form Contains quality assessment and analysis note fields used in MKS Built in filters Filter on latest version only Filter on assigned analyst or other custom requirement tag Maintain multiple filters even if analyst manually filters another field 8
SMART Context IV&V Facility Build Deliveries (FSW & UT Code) SMART Rqmts & Traces DOORS Excel SMART perl scripts Analyze Artifacts & Record Results MS Access Front End SQL Server Tables Analysts Draft Findings TIM X-Refs ORBIT Excel Issues, & Observations 9
Analysis Form IV&V Facility 10
In-Process Enhancements IV&V Facility Generalization of forms among artifact types Removal of requirement artifact as the only left-hand artifact Enhanced navigation addition of list navigation Allowing multiple instances of forms 11
Configurable Analysis Form IV&V Facility 12
Example: Requirements to Scenarios IV&V Facility 13
Multiple Analysis Forms IV&V Facility 14
Swapping Left and Right Side IV&V Facility 15
User Requirements Report Card IV&V Facility Category Requirement Grade B C Represent a wide variety of artifacts Display artifacts with native formatting (graphics, tables, italics and other font attributes, etc.) Attach IV&V-interest attributes to both parent and child elements Capture attributes and analysis notes to traces Support development of issues and assurance evidence Easily load and link various artifacts See lists (with filtering) of elements for selection View parent, child and trace simultaneously Support multiple analysts in the same data set, often geographically dispersed Support multiple projects without new development Artifacts A Facilitating Analysis B C B B A B- Visualization/ Navigation Deployment C Represent custom fields without development D 16
IV&V Facility Future of SMART 17
Potential Enhancements IV&V Facility Anything to bring report card grades up Generalization across projects Using common data model Native-formatted requirements OLE html Extend mapping targets Simplify data structures Better support for issue development Better support for assurance evidence 18
Ownership IV&V Facility Enterprise vs Project Analysts vs SWAT 19
IV&V Facility Conclusions 20
Conclusions IV&V Facility SMART is field-proven Multiple projects, many issues generated I assert a unique capability (currently supported, traceability tool) SMART has a large user and user- developer base SMART has had initial discussion with SWAT on enterprise support SMART has planned enhancements that are progressing 21
IV&V Facility Backup Charts 22
SMART Queries Change Impact Analysis IV&V Facility Changed Requirement Text (ObjectText) New Requirements Deleted Requirements New Traces Deleted Traces 23
Factors Behind Tool Selection IV&V Facility Like MAVEN, SMAP was initially using MKS to support requirements validation Led to a nearly one-to-one mapping between the fields in MKS and the requirements validation form in SMART Analysts would already be familiar with fields Made migrating analysis records from MKS to SMART straightforward MAVEN and SMAP projects use DOORS for requirements and traceability Resulted in a database schema and features oriented towards handling artifacts from DOORS SMART now has a multimission pedigree Instantiations of the tool used on Juno, ESMDI, Ares, ICESat-II, SMAP, and now MAVEN helping establish the framework for a common tool to be used on IV&V projects MAVEN benefits from multiple enhancements made to the tool to support the various projects Due to MAVEN inheriting analysts from Juno, there was already an experience base with the tool and its architecture SMART relies on a Microsoft Access frontend Flexible architecture and easy to tailor and modify on the fly - does not require a formal change request process Considerable experience on the team with Access and database development 24
SMART for MAVEN Enhancements IV&V Facility Added MAVEN-specific scoping qualifiers Added fields to support change/impact analysis Added several requirement fields to facilitate filters Code analysis form Allows analyst to trace one or more functions to a requirement Analyst can select the function from dropdown list, which pre- populates a code snippet field Analyst can add comments on each trace, as well as comment on the traceability overall if multiple functions are traced to the requirement Test validation form Modeled after code analysis form Instead of relying on user to trace test requirements, tool will use developer provided traces Designed to support unit test validation and acceptance test validation tasks 25
Future Enhancements IV&V Facility Develop a form to support analysis of mini- scenarios (basic form developed) Develop a form to support the general code inspection task Provide broader coverage of AVT task Conditional formatting based on various flags 26
