No stable release available yet.
Upcoming and alpha/beta/candidate releases
- Alpha releases should only be used for testing and development.
- Beta releases and Release Candidates are normally released for production testing, but should not be used on mission-critical sites.
- Always install on a separate test server first, and make sure you have proper backups before installing.
What is UC Workbench?
UC Workbench is a tool assisting analysts in requirements engineering. It allows
analyst to create use cases easily, manage them, maintain changes, sketch user interface and generate simple prototypes that can be shown to customers and thus enhance their imagination about future system. It is meant to be a tool for complex requirements management, supporting:
- use-case authoring and maintenance
- requirements reviews
- effort estimation based on use cases
- screen sketching and attaching them to use-case steps
- natural language processing based analysis and defect detection
The history of UC Workbench
Development of the first version was started in 2004. It was based on Eclipse 3.2. In the early 2007 we have encountered serious architectural constraints, so we have decided to start once again from scratch - we have rewritten most of UC Workbench 1 code and create UC Workbench 2, which is a tool based on the most recent Eclipse technologies (e.g. EMF, GMF).
Note that UC Workbench I and II are separate incompatible applications (however they share the same idea).
UC Workbench I
UC Workbench I is not maintained anymore. There are some bugs we are aware, but if you know how to overcome those issues you can work with it quite successfully (some of us still do)!
You can read more about UC Workbench I and download latest version here.
UC Workbench II
UC Workbench II hasn't been finished. It is also not maintained anymore, however we are using it as a platform for developing research tools. It can be used but user can encounter some usability issues.
You can read more about UC Workbench II and download latest version here.
[ ] Internationalized
[X] Unit tests
[ ] End-user documentation
[X] Internal documentation (documentation, interfaces, etc.)
[ ] Existed and maintained for at least 6 months
[ ] Installs and uninstalls cleanly
[ ] Code structure follows best practice