There's some overlap between this question and the question on how CaseComplete supports use case modeling. With regard to ease of use, we designed the UI to anticipate what the user needs to do next and guide them towards that next step. So even if the user is not a requirements expert, they will be guided towards writing a solid set of use cases. Here are more specific examples:
- Even novice users can launch the tool and create their first project in a few seconds. (No central administration required, it takes a few keystrokes and the click of a button.)
- The first thing the user sees when starting a new project is a road map detailing a complete process for gathering requirements with use cases. This road map is based on best practices (popular use case books) and our own experience. It's easy to follow and provides a consistent approach. Our customers seem to like this since every team has varying levels of expertise, new team members joining midstream and others leaving.
- The UI is designed around each specific requirements construct (an actor, a use case, a requirement, etc.). The help system tells the user what each attribute of each element means. They're not left staring at a textbox wondering what information goes there.
- Some common tasks can be done automatically, like diagram generation and report generation.
- Since most customers have long lists of requirements, a user can filter quickly with the results shown in real time along with a natural language explanation ("Use Cases where Complexity is low, Priority is 1").
- Much thought and design is put into every aspect of the UI so that the user can accomplish their task with the fewest number of keystrokes and/or mouse gestures.
Comment actions