Review - Use-Case: Import from SQL File
Brian Sidharta 07 Dec 2002

This is an informal review report of the Use Case Specification for
importing from a SQL file, authored by Abhay Sathe.  Reviewed
sections are bulleted with a hyphen "-", with the reviewer's comments
following each item.

- Title/Heading
  The Use Case should be "Import from a SQL file" instead of "Load
  Saved Schema"  The term "load" implies reading an
  application-internal, efficient file format.  SQL is a format that
  we are reading, which is optimized for creating/querying databases
  in a user-friendly manner.

- 2.1 Basic Flow
  The use-case initiation steps should be changed.  As importing from
  a SQL file is a refinement of the general Import Schema use case, it
  should be similar but more detailed than the parent use cases.

- 2.2 Alternative Flows
  Please add numbering to the flow steps to denote what step of the
  Basic Flow the Alternative Flow modifies.  For an example, please
  see the Use Case Specification for Adding a Table to an ER Diagram.

- 2.2.1 User is unable...
  Change the result (step 2) to be that the browse window disappears
  and the user is returned to the general import dialog window.