Register  |  Login
Adoption is easy

ScopeTracker is very forgiving. You can start by using the tool to just create your full requirements list. This is a very important first step as you now have the full list of all capabilities that must be delivered for acceptance, with unique numbers and version managed. It reduces the effort of your testers, as they now don’t need to first try and find the requirements in all sorts of documents. To keep the workload manageable, here’s a tip: “if it is important enough to test, make it a requirement”.


Having this list enables you to prioritise and meet timelines as agreed. Next you can make a start with adding some links between requirements. For example, add the most significant links between business and software requirements, or performance and functional requirements.


As you go, add the first tags in your specification documents. Now you can trace the true source location of the requirements. In parallel, the testers can make a start dragging & dropping the requirement Tags into their test cases and scripts. Never mind if it is not all complete, at least you can now find the most important links between requirements and files or parts within files.


Note that you can trace and manage any track-able item, be it a requirement, CR number, TBR (to be resolved) number, Assumption number ...

Some usage examples by role


Testers typically already do this work manually. They’ll use a highlighter to plough through the documentation to pick up measurable capabilities the system should deliver (requirements). At the end of each highlight, they scribble a number or similar so that they can reference the materials and figure out completeness of testing. (but what-if the docs change?!)


Developers should also add requirement IDs/tags to their source code. This may be the most difficult behavioural change to institute. However, it is necessary, as without tagging the code, you can’t know the impacts of changes on tests and documents when you change those code files. Adding Tags to code is easy as all you have to do is drop them into a comment in the code. And you don’t have to go overboard, just start with the tricky stuff first. ScopeTracker is non-invasive, meaning it has no impact on compiling, accessibility or performance.


As you can now see, you can make a start and expand usage, filling in the gaps as you go. It is also a great way to gradually get back on top of existing systems and documentation.

More work? No, the same or less!

As you can see from the above, there is actually no increase in effort. Some of the work you do by hand already. But now with ScopeTracker - for very little effort indeed - you can finally do traceability (something most of us know we need to do). And when things change it is actually less work because ScopeTracker tracks all the changes for you.


Make a start, get messy…

Get your trial or buy ScopeTracker from the Store.


  mail to colleague



Your Rating: 0.0   Average Rating: 0   Ratings: 0
Site Software v2.2.0, 26 Oct 2016