|
The tool was already in the works using HTML, JSP, and Apache (with Struts), no JMX yet. There were no design documents, design requirements,
prototypes, roadmap or competitive benchmarks or goals. The engineering team had a grip on the engineering requirements, but not the
priority of those requirements or a method to determine the most effective method to present the features.
Issues identified from an "Expert" evaluation:
- Over 70 usability issues
- Starting to peal away the onion skins (revealing new issues only once we get rid of other issues covering underlying issues)
- Needed better navigation model (inconsistent paths, dead-ends, no symatery in functionality, no bread crumbs, no ability to show where you are in the system)
- Functions did not validate input or provide consistent feedback or error messages
- Setup of system parameters not obvious
- Installer's and documentation were poorly written, improperly organized and incomplete
- Mismatch in data that was needed, not needed, required and optional
- Web interface not tested for browser compatibility, UI standards were needed.
|
