1

DBXPERT: CASE TOOL

Project Advisor:Prof. Ishaq Raza

Group Members:SHEIKH HASSAN IMTIAZ

L1F06BSCS0024 MUHAMMAD NABEEL ARIF

L1S07BSCS0019 MUHAMMAD NOUMAN

L1S09BSCS0018

2

SOFTWARE REQUIREMENT SPECIFICATION

3

PURPOSE

Our product will enable the users to draw database schema

Our product will enable the users to write database schema

Uses a database tool to perform forward engineering and reverse engineering

4

SCOPE

Our product will be desktop based.

Implement Chen notation for ER schema diagram

Forward and Reverse Engineering between ER and RM

5

OVERALL DESCRIPTION

6

PRODUCT FEATURES ER Diagram through drag and drop interface

ER Schema and Relational Schema format in txt or xml

Convert ER schema into Relational schema

Convert Relational schema into ER schema

To make our CASE Tool available on the internet

7

USER CLASSES & CHARACTERISTICS

The solution is intended to be used primarily by Teachers/Students/Developers/DB designers.

All of these users are categorized as a single

user “Users”.

‘Users’ will have the same privileges and perform similar tasks.

8

HIGH LEVEL UCD FOR ‘USERS‘

9

ASSUMPTIONS AND DEPENDENCIES

This tool will be built using C#.Net.

.Net is not an open source language therefore design and implementation constraints specific to implementing language and platforms selected may appear during the product development

Our product will be using ER and RM schema formats developed by us. Users will have to follow these conventions as our product will be dependent on these conventions.

10

Use Cases

11

WRITE ER SCHEMA IN TXT (UC1)

Actor action System Response

User will open the application and click on ER model.

System will show a new window where there will be four options.

User will select ‘TXT’ format option. System will open the notepad editor .User will write the ER schema in notepad editor.

System will display the text

User will click on ‘SAVE’ option and give a file name

System will generate a file bearing the desired name

ActorsUsers

Pre-conditionsNA

Post-conditionsAfter the successful execution of this use-case , the user will have an ER schema in TXT format .

Basic Flow

12

DRAW ER SCHEMA DIAGRAM (UC3)

Actor action System ResponseUser will open the application and click on ER model.

System will show a new window where there will be four options.

User will select ‘Draw ER’ option System will open the drawing editor User will click on ‘Insert’ tab. System will display different options in

PageGroup.User will draw the ER diagram using drag and drop options from insert toolbars.

System will display the drawing

User will click on the ‘Save’ option and give a file name.

System will generate a file bearing the desired name

ActorsUsers

Pre-conditionsNA

Post-conditionsAfter the successful execution of this use-case , the user will have a ER diagram .

Basic Flow

13

WRITE RELATIONAL SCHEMA IN TXT (UC4)

Actor action System ResponseUser will open the application and click on Relational model.

System will show a new window where there will be four options.

User will select TXT format System will open the notepad editor User will write the Relational schema in notepad editor.

System will display the text

User will click on the ‘Save’ option and give a file name

System will generate a file bearing the desired name

ActorsUsers

Pre-conditionsNA

Post-conditionsAfter the successful execution of this use-case , the user will have a Relational schema in TXT format .

Basic Flow

14

DRAW RELATIONAL MODEL (UC6)

Actor action System ResponseUser will open the application and click on Relational model.

System will show a new window where there will be four options.

User will select ‘Draw RM’ option System will open the drawing editor User will click on ‘Insert’ tab. System will display different options in

PageGroup.User will draw the RM diagram using drag and drop options from insert toolbars.

System will display the drawing

User will click on the ‘Save’ option and give a file name.

System will generate a file bearing the desired name

ActorsUsers

Pre-conditionsNA

Post-conditionsAfter the successful execution of this use-case , the user will have a Relational diagram

Basic Flow

15

CONVERT ER SCHEMA IN TXT INTO ER SCHEMA IN XML (UC8)

Actor action System ResponseUser will click on ‘Convert ’tab System will display different option in

Combo Box.

User will select ‘ER txt schema into ER xml schema’.

System will generate ER schema in XML format.

ActorsUsers

Pre-conditionsUC1 has executed i.e. user has the ER Schema in txt format ORUC7 has executed and user has opened ER Schema TXT file.

Post-conditionsAfter the successful execution of this use-case , the user will have ER schema in xml format.

Basic Flow

16

CONVERT ER SCHEMA IN TXT FORMAT INTO ER SCHEMA

DIAGRAM (UC9)

Actor action System ResponseUser will click on ‘Convert ’tab System will display different option in

Combo Box.

User will select ‘ER txt schema into ER schema Diagram’.

System will generate ER schema Diagram.

ActorsUsers

Pre-conditionsUC1 has executed i.e. user has the ER Schema in txt format ORUC7 has executed and user has opened ER Schema TXT file.

Post-conditionsAfter the successful execution of this use-case , the user will have ER Diagram.

Basic Flow

17

CONVERT ER SCHEMA IN XML FORMAT INTO ER SCHEMA DIAGRAM (UC11)

Actor action System ResponseUser will click on ‘Convert ’tab System will display different option in

Combo Box.

User will select ‘ER xml schema into ER schema Diagram’.

System will generate ER schema Diagram.

ActorsUsers

Pre-conditionsUC2 has executed i.e. user has the ER Schema in xml format ORUC7 has executed and user has opened ER Schema XML file.

Post-conditionsAfter the successful execution of this use-case , the user will have ER schema Diagram.

Basic Flow

18

CONVERT ER SCHEMA DIAGRAM INTO ER SCHEMA IN TXT FORMAT (UC12)

Actor action System Response

User will click on ‘Convert ’tab System will display different option in Combo Box.

User will select ‘ER schema Diagram into ER txt Schema’.

System will generate ER txt Schema

ActorsUsers

Pre-conditionsUC3 has executed i.e. user has the ER Schema in txt format ORUC7 has executed and user has opened ER Schema Diagram file.

Post-conditionsAfter the successful execution of this use-case , the user will have ER Schema in txt format.

Basic Flow

19

CONVERT RELATIONAL SCHEMA DIAGRAM INTO RELATIONAL

SCHEMA IN TXT (UC18)

Actor action System Response

User will click on ‘Convert ’tab System will display different option in Combo Box.

User will select ‘Relational Model into Relational txt Schema ’.

System will generate Relational schema in txt format.

ActorsUsers

Pre-conditionsUC6 has executed i.e. user has the Relational Schema Diagram. ORUC7 has executed and user has opened Relational Schema Diagram file.

Post-conditionsAfter the successful execution of this use-case , the user will have Relational schema in txt.

Basic Flow

20

FORWARD ENGINEERING (UC20)

Actor action System Response

User will select ‘Home’ tab. System will show different options.

User will click on ‘Forward Engineering’ button

System will generate Relational Schema.

ActorsUsers

Pre-conditionsUC1 or UC2 or UC3 has executed i.e. user has the ER Schema. ORUC7 has executed and user has opened ER Schema file.

Post-conditionsAfter the successful execution of this use-case , the user will have Relational Schema.

Basic Flow

21

REVERSE ENGINEERING (UC21)

Actor action System Response

User will select ‘Home’ tab. System will show different options.

User will click on ‘Reverse Engineering’ button

System will generate ER schema.

ActorsUsers

Pre-conditionsUC4 or UC5 or UC6 has executed i.e. user has the Relational Schema. ORUC7 has executed and user has opened Relational Schema file.

Post-conditionsAfter the successful execution of this use-case , the user will have ER schema.

Basic Flow

22

FIND TEXT (UC28)

Actor action System ResponseUser will press the Find text button. System will show a dialogue box

where text to be searched can be entered.

User will type the text to be searched in the text box and press Find.

System will show the first successful matched text on the file.

User will press the Find Next button. System will show the next successful matched text on the file.

ActorsUsers

Pre-conditionsThe user must have some file opened in notepad editor.

Post-conditionsAfter the successful execution of this use-case, the user will get to the first successful matched text on the file.

Basic Flow

23

Screen-Shorts from Current Work

24

25

26

27

28

THANK YOU