Review - Use-Case: Create an ER Diagram
Brian Sidharta 07 Dec 2002

This is an informal review report of the Use Case Specification for
Creating an ER diagram, authored by Brian Schoudel.

Page 4 and page headers reads "Add Table". It should be  "Create ER
Diagram".  Actually, most of the use case looks like it's for Add
Table and not Create ER Diagram.

The basic flow should be something like:
1) Use selects the "Create new diagram" option.
2) A new diagram appears in the GUI window.

This depends on the diagram/schema model we're using in the
application.  Where do we save the schema data on disk?  And the
diagram(s)?

The correct abstraction model would have the schema be a separate
entity, and the user can import one schema and create multiple
diagrams (views) of that schema. However, this requires a more
complicated implementation and user-interface.

A simpler abstraction model is to have only one diagram per imported
schema.  If the user wishes to make multiple views, they are forced to
import the schema multiple times.  This is a much simpler abstraction
model, and it would negate the need for this use case. However,
forcing the user to import a diagram every time may be harsh.