Use-Case Specification: Add Table



Database Visualizer - dbViz

Use-Case Specification: Add Columns to Query

Version 1.2

Revision History

|Date |Version |Description |Author |

|23/Oct/2002 |1.0 |Document created |Dave Hampshire |

|09/Nov/2002 |1.1 |Document updated |Brian Schoudel |

|12/Dec/2002 |1.2 |Post Review |Brian Schoudel |

| | | | |

Table of Contents

1. Use-Case Name 4

1.1 Brief Description 4

2. Flow of Events 4

2.1 Basic Flow 4

2.2 Alternative Flows 4

2.2.1 Entity-Relationship diagram is corrupt 4

2.2.2 User unselects the column's checkbox 4

2.2.3 User selects column where table is not part of query 4

2.2.4 User selects column where table has no relationship with existing table(s) in query 4

3. Special Requirements 5

3.1 Response Time 5

3.2 Query Requirements 5

4. Preconditions 5

4.1 Existing Entity-Relationship Diagram 5

5. Postconditions 5

5.1 Column is added to the query in the query edit text box 5

5.2 Confirmation Message 5

6. Extension Points 5

6.1 Query edit text box 5

Use-Case Specification: Add Table

Use-Case Name

1 Brief Description

The user wishes to add a column to query based on a table from the Entity-Relationship diagram.

Flow of Events

1 Basic Flow

1. User selects the checkbox beside the appropriate column in the table description on the Entity-Relationship diagram.

2. Application displays "Column X has been added from table Y to the existing query." on the Status Bar.

3. The existing query is updated in the query editing text box. The column is added to the select portion of the query.

4. Mouse cursor is changed to the default cursor.

2 Alternative Flows

1 Entity-Relationship diagram is corrupt

    

*a1. Display "Corrupted E-R diagram Error" message.

     *a2. Prompt user to either rebuild E-R diagram or continue.

2 User unselects the column's checkbox

1a1. User unselects the column's checkbox. Application aborts adding the column to the existing.

1a2. Control of application passed back to user.

3 User selects column where table is not part of query

1b1. User selects column where table is not part of query.

     1b2. Application prompts “Do you wish to add table Y to your query”

1b3. If user selects “Yes”

1b3a. Control resumes with step 2 of the Basic Flow.

Else if user select “No”

1b3b. Column is not added to the query.

1b3c. Control of application passed back to the user.

4 User clicks on table with no relationships to existing table(s) in query.

1d1. User clicks on table with no relationships to existing table(s) in query.

     1d2. Application prompts “There are no joins to make with the existing query. Do you wish to continue

adding the selected column?”

1d3. If user selects “Yes”

1d3a. Control resumes with step 2 of the Basic Flow.

Else user selects “No”

1d3b. Column is not added to query

1d3c. Control of application passed back to user.

Special Requirements

1 Response Time

System response time should be fast (within 2 seconds).

2 Query Requirements

Queries are to utilize standards as set forth with SQL92 standard.

Preconditions

1 Existing Entity-Relationship diagram

An existing Entity-Relationship exists where the user can start checking columns to add to or create an SQL query.

Postconditions

1 Column is added to the query in the query edit text box

Column X is added to the select portion of the query along with table X if not already added. The proper join statement is added to where clause as well where appropriate.

2 Confirmation Message

The application status bar displays "Column X of Table Y successfully added to the query."

Extension Points

There is one extension point: Query Edit Text Box.

1 Query Edit Text Box

This extension point happens after the column has been successfully added to the existing query.

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download