Usability Report
Contents |
[edit] Usability Report
[edit] Overview
Usability reports are feedback from the community about usage of (new) features in the real world.
An usability report is a short account of the user's first impact on a newly tried feature, recording his/her expectations and the level of satisfaction achieved.
[edit] Structure
An usability report should have the following components.
- Product identification
- product name
- version used
- date of experience
- any other relevant information to identify what is being tested.
- Expectations
- Clarity of documentation
- Ease of use
- Real world usage
- Bugs
- Missing pieces
- Level of satisfaction
- (optional) Test units
[edit] Format
The preferred format is wiki markup, because ultimately these reports will go into MySQL Forge.
[edit] Reports archive
[edit] MySQL Server 5.1
- Usability report for table logs Giuseppe Maxia, August 2006.
- Event scheduler
- Partitioning
- XML functions
- Row-based replication
[edit] MySQL Server 6.0
- Falcon storage engine
- Correlated subqueries are very fast
- Large correlated subquery optimization allows for large enterprise table query correlation
- To do
[edit] MySQL Migration Toolkit
- To do
[edit] MySQL Workbench
- To do
[edit] MySQL ODBC connector
- To do
[edit] MySQL JDBC connector
- Easy and versatile to connect to MySQL databases
- To do
Any takers?
Each feature product can have more reports. Each user's first impression is important. Feel free to add new features/products to review.