It 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 . StumbleUponrequirements
In TestTrack RM, the default requirements workflow includes a Review Note event that reviewers use to provide feedback on individual requirements.
Before requirements are approved, it’s crucial to make sure all review notes are addressed. You can make this easier by adding a check box to the Review Note event, which users select after addressing a note. You can also create a filter to display requirements that still contain review notes to address. Users can apply this filter to quickly find requirements that need attention.
Continue reading…
We recently released version 2010.1 of TestTrack, which contains many new exciting new features. One new feature that I would like to give some love to is Item Mapping Rules. This feature will benefit users who have more than one TestTrack applications, as it allows you to configure how field values are mapped from one application to another.
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUponAfter you add a review note to a requirement, you may realize you need to add information to it or correct mistakes. Depending on your security permissions, you can edit review notes to make changes.
Review notes are workflow events that can be edited like other events. The quickest way to edit a review note from Review Mode View in the Specification Document window is to click the Review Note link to edit the note.
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUponSince the introduction of TestTrack RM earlier this year, I’ve had a chance to demonstrate the product many times to prospects. While the initial feature set of the product is impressive, every once in a while I do hear about features that are not currently available. These become feature requests, which are prioritized and scoped out by our product management team.
One feature request I have heard a few times is for a very specific need. This scenario is for a user whose only action related to requirements is to approve or reject them. This user is not in development, QA, or any other group directly involved with software development and does not use TestTrack. This individual is likely to only deal with business requirements and not functional requirements. The user does not want to install the TestTrack client and learn how to use it when only a simple view is needed to review and approve or reject requirements.
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUponWe recently released a new requirements management product, TestTrack RM.
The early feedback on the product has been great. TestTrack RM is proving to be a valuable addition to the TestTrack family, which also includes TestTrack Pro (defect management) and TestTrack TCM (test case management).
While TestTrack RM provides many benefits on its own, the real power comes when it is used as an integrated solution with the other TestTrack applications. For example, you can easily determine if you have proper test coverage by ensuring that a test case has been created for every requirement. You can easily flag a test case if a requirement has changed, avoiding testing stale data and wasting time and money. For this post, I want to focus on one of the biggest benefits: complete traceability.
Continue reading…
If you use Surround SCM or any other robust software configuration management tool (gasp!), chances are you are using branches to manage your software development process. Depending on your branch strategy, you may find yourself with a defect that exists across multiple branches. There are many ways to manage this situation, the best one for you will depend on your environment and needs.
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUpon
Last week, Seapine Software presented a webinar called “Transparent Traceability in Life Sciences: A practical approach to compliance in your development lifecycle”. The program was presented by Paula Rome, Sr. Product Manager, and myself and was moderated by Jay Luis, VP of Marketing. Preparing for these webinars is harder than I thought but we’re all very happy with the result.
Continue reading…
Requirements traceability is a best practice for developing quality software. The complexity and cost of today’s requirements management tools prohibits many companies from realizing their benefits or even purchasing a tool. Well, we’ve developed a great requirements management solution that reduces complexity and costs less. We call it TestTrack RM. Since the release of TestTrack 2009 in February, it’s been full steam ahead for the entire TestTrack team to deliver TestTrack RM.
Continue reading…
