Got a minute?
Great, 'cause it takes less time than that to enter a requirement into TOMOS.
Requirements Made Simple.
Name your Requirement, add a few notes if you want, link it up to a transaction and application area, pick a priority and you’re done. BAM, that’s it. Go back and make some changes if you want, we’ll keep track of the history.
Lots of people can make a simple interface for Requirements entry. The hard part is actually creating the Requirements. We’ve got you covered there too. TOMOS’ built-in methodology and role-based workflow equips you with best practices for defining, gathering, and managing Requirements.
TOMOS provides buckets to define application areas and transactions /use cases or user stories. Then you can put the Requirements in these buckets. Instead of re-typing things multiple times, you can copy-and-paste or drag-and-drop to make changes. It’s dead simple to use and makes perfect sense at first glance, leaving you with time to, you know, actually get work done.
Key features:
- A dedicated Requirements dashboard with key metrics and real-time graphs
- The ability to view Requirements in a tree, grid or a combo tree+grid
- Traceability from Requirements to Test Cases to defects
- Track the complete audit history of changes to each Requirement
- Attach any kind of file or picture to each Requirement
- Track a thread of comments and messages for each Requirement
- Save, Print and Export to PDF the Requirements graphs
- Built-in Methodology guide to get you started
- Role Based workflow diagrams and definitions which includes Business Analyst, Developers, and Testers
- Automated email notifications are sent when the main aspects of a Requirement are adjusted or created
- A Microsoft Outlook-like look-and-feel with buttons for workspace, methodology, role-based workflow, glossary, legend and key metrics
- Many more features!
