Thank you to everyone who participated in the Leveraging Reusability and Traceability in Product Development
webinar. The recording is now available if you weren't able to attend or if you would like to watch it again.
For those that are interested in buying Dave's book, you can buy the book here www.ArtechHouse.com/vogel
with promo code DV25
Q&AQ: I understand the concept of validation, but in the examples you gave you kept mentioning requirements of these various stakeholders. If these requirements are known, why can't they be verified?
A: Generally, in GPSV lingo
, we think of verifying the implementation of a requirement, and validating that it meets the user need. For example a marketing requirement of "user friendly" (which is admittedly vague) is interpreted as a number of software requirements by engineers, but validation is needed to see if the users agree that it is user friendly.
Q: Can failed test cases be exported to an external tool for recording software defects (e.g., Rational ClearQuest)?
A: Yes. TestTrack includes an SDK
that you can use to integrate with ClearQuest.
Q: How long does it take to implement a solution like TestTrack?
A: Assuming you have good processes in place, it can take as little as three days. If you have more complex projects, or multiple product lines, it could take up to five or six days to implement.
Q: What licensing models are available?
A: TestTrack offers the flexibility of named licenses, floating licenses, or a combination of licenses
. By selecting the license types best suited to your organization's needs, you can provide access to the greatest number of TestTrack users at the lowest cost we can use we have what is called a name license which is dedicated to a user and we also have floating licenses which are like a concurrent model which can be shared across a group of people. They can all be mix and matched, there is no perfect answer every organization is different. Licensing is very customizable.
Note: In the presentation, there are two software design specs areas in the flowchart on page 11. This is a mistake. One should be labeled ‘GUI design spec’ and the other ‘Functional design spec’.