TestTrack’s sample project includes a sample workflow for managing requirements and requirement documents. In most cases, customers base their workflow on the sample, but want to tweak it to meet their needs. This article explains how to make three quick tweaks to the sample workflow: configuring when requirements and requirement documents are locked, enabling test cases to be generated from requirements, and configuring the workflow states and events.
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUponRequirements Management
Do requirements still matter in an Agile environment? What is the business case for Agile, and why is the market moving toward Agile solutions? Agile experts from Seapine Software will answer these questions and more at the TechNet-Aero Conference in Dayton, Ohio, October 17-20.
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUpon
Thanks to everyone who joined us for the FDA Design Traceability Requirements for Device Development webinar with John Avellanet, Managing Director & Principal at Cerulean Associates, LLC and Larry Nicholson, Business Development Manager for Life Sciences at Seapine Software. If you missed the event, or want to watch it again, the recording can be found below or viewed on SlideShare. Additionally, you can download the FDA Expectations for Traceability in Device Design slide deck.
Q&A
Where can I find the FDA draft document for medical applications?
All of the recent medical device guidance documents can be found on the FDA site: www.fda.gov/MedicalDevices/DeviceRegulationandGuidance/GuidanceDocuments/ucm162707.htm. (Avellanet)
Is an application that sets up datasets for infusion pumps considered a medical application?
Take a look at the guidance, specifically at the criteria listed on pages 13-15, and then the examples provided by the agency in Appendix A of the guidance. (Avellanet)
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUpon
While Agile has been gaining more and more ground, it appears that many organizations are also adopting their own flavor of Agile. They take the parts that they like or work for them and integrate them into their own process. Sometimes this is driven by outside factors, like compliance needs and customers.
In these instances, you may have a need to manage both requirements and user stories in the same project. In this post, I’ll talk about one way to do this in TestTrack.
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUponSeapine Solutions Evangelist, Peter Varhol, was recently interviewed about requirements traceability by Mike Lippis for the Outlook Series. The “Strengthened Traceability Drives Greater Quality & Communication” podcast is now available.
Peter and Mike discuss several aspects of requirements management, and why traceability is so important to the software development process these days. Following are a few interesting nuggets, if you don’t have time to listen to the 46-minute interview:
01:30 - Definition of requirements traceability
09:50 - How to make traceability automatic
21:55 - How to know if your traceability strategy measures up
30:00 - Information about managing requirements traceability with TestTrack
Have an opinion on traceability, or a story about how your team uses traceability to improve quality? We’d love to hear it—leave us a comment!
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUpon
Thanks to everyone who joined us for our When Requirements Change: Continuing to Meet User Expectations with Requirements Traceability webinar. The recording is now available on YouTube if you missed the webinar or want to watch it again. Following is the SlideShare version of the webinar.
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUpon
Unlike a wildebeest, your products are unlikely to thrive in the middle of the herd right now. In challenging economic times, your customers start focusing on value and you need to separate yourself from the herd. I was reminded of this earlier in the week while listening to Activision Publishing’s CEO discuss the gaming market. In responding to a question about current challenges in the gaming industry, Eric Hirshberg had this to say (paraphrasing):
It’s really the best of times and the worst of times for the gaming industry. The top 10 titles are bigger than ever and growing, the part of the industry that is struggling is the “middle class of title.” The middle-budget and middle-rating games aren’t seeing as much interest as they did just a few years ago … There’s no way to market yourself out of a mediocre game.
His point was that quality is the key imperative to a title’s success, and that’s something we’re seeing in every industry right now. The products that best meet users’ needs—and do so reliably—are the products that win in this market.
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUponIt used to be that users, or product management, submitted a set of features and requirements to the development team and waited patiently while development constructed exactly what they asked for. Six months later, when users saw this new application for the first time, they realized that what they asked for wasn’t really what they needed. Something had been lost in the translation from what they needed to what they told development to create, to what development ultimately created. “No problem,” development would say when told the existing software didn’t meet a specific need, “we can change that in the next release.” And six months later, it would indeed be changed!
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUpon
Prospective customers often ask me if there is a way to approve all the requirements in a requirement document at once.
I usually ask a few questions before responding:
- Are there multiple document approvers?
- Does each document approver have an area of expertise?
- Does the approver verify the content of each and every requirement in the document?
- Is there a need to have accountability in specific areas of the requirements process, such as design, technical, or software?
Make plans to join us when the Seapine ALM Tour 2010 stops in Huntsville, Alabama on September 23. Meet some of our product management team, see the upcoming Seapine ALM 2011 release, and learn ways to boost agility, collaboration, and traceability! It’s all free!
