D BXPERT : CASE T OOL 1 Project Advisor: Prof. Ishaq Raza Group Members: SHEIKH HASSAN IMTIAZ L1F06BSCS0024 MUHAMMAD NABEEL ARIF L1S07BSCS0019 MUHAMMAD NOUMAN L1S09BSCS0018

2

P URPOSE 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 3

S COPE Our product will be desktop based. Implement Chen notation for ER schema diagram Forward and Reverse Engineering between ER and RM 4

5

P RODUCT F EATURES 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 6

U SER C LASSES & C HARACTERISTICS 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. 7

‘USERS‘ HIGH L EVEL UCD FOR ‘USERS‘ 8

A SSUMPTIONS AND D EPENDENCIES 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. 9

10

W RITE ER SCHEMA IN TXT (UC1) 11 Actor actionSystem 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 Actors Users Pre-conditions NA Post-conditions After the successful execution of this use-case, the user will have an ER schema in TXT format. Basic Flow

D RAW ER SCHEMA D IAGRAM (UC3) 12 Actor actionSystem 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 ‘Draw ER’ optionSystem 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 Actors Users Pre-conditions NA Post-conditions After the successful execution of this use-case, the user will have a ER diagram. Basic Flow

W RITE R ELATIONAL SCHEMA IN TXT (UC4) 13 Actor actionSystem Response User 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 formatSystem 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 Actors Users Pre-conditions NA Post-conditions After the successful execution of this use-case, the user will have a Relational schema in TXT format. Basic Flow

D RAW R ELATIONAL M ODEL (UC6) 14 Actor actionSystem Response User 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’ optionSystem 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 Actors Users Pre-conditions NA Post-conditions After the successful execution of this use-case, the user will have a Relational diagram Basic Flow

C ONVERT ER SCHEMA IN TXT INTO ER SCHEMA IN XML (UC8) 15 Actor actionSystem Response User 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. Actors Users Pre-conditions UC1 has executed i.e. user has the ER Schema in txt format OR UC7 has executed and user has opened ER Schema TXT file. Post-conditions After the successful execution of this use-case, the user will have ER schema in xml format. Basic Flow

C ONVERT ER SCHEMA IN TXT FORMAT INTO ER S CHEMA D IAGRAM (UC9) 16 Actor actionSystem Response User 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. Actors Users Pre-conditions UC1 has executed i.e. user has the ER Schema in txt format OR UC7 has executed and user has opened ER Schema TXT file. Post-conditions After the successful execution of this use-case, the user will have ER Diagram. Basic Flow

C ONVERT ER SCHEMA IN XML FORMAT INTO ER SCHEMA D IAGRAM (UC11) 17 Actor actionSystem Response User 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. Actors Users Pre-conditions UC2 has executed i.e. user has the ER Schema in xml format OR UC7 has executed and user has opened ER Schema XML file. Post-conditions After the successful execution of this use-case, the user will have ER schema Diagram. Basic Flow

C ONVERT ER SCHEMA D IAGRAM INTO ER SCHEMA IN TXT FORMAT (UC12) 18 Actor actionSystem 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 Actors Users Pre-conditions UC3 has executed i.e. user has the ER Schema in txt format OR UC7 has executed and user has opened ER Schema Diagram file. Post-conditions After the successful execution of this use-case, the user will have ER Schema in txt format. Basic Flow

C ONVERT R ELATIONAL S CHEMA D IAGRAM INTO R ELATIONAL SCHEMA IN TXT (UC18) 19 Actor actionSystem 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. Actors Users Pre-conditions UC6 has executed i.e. user has the Relational Schema Diagram. OR UC7 has executed and user has opened Relational Schema Diagram file. Post-conditions After the successful execution of this use-case, the user will have Relational schema in txt. Basic Flow

F ORWARD E NGINEERING (UC20) 20 Actor actionSystem Response User will select ‘Home’ tab.System will show different options. User will click on ‘Forward Engineering’ button System will generate Relational Schema. Actors Users Pre-conditions UC1 or UC2 or UC3 has executed i.e. user has the ER Schema. OR UC7 has executed and user has opened ER Schema file. Post-conditions After the successful execution of this use-case, the user will have Relational Schema. Basic Flow

R EVERSE E NGINEERING (UC21) 21 Actor actionSystem Response User will select ‘Home’ tab.System will show different options. User will click on ‘Reverse Engineering’ button System will generate ER schema. Actors Users Pre-conditions UC4 or UC5 or UC6 has executed i.e. user has the Relational Schema. OR UC7 has executed and user has opened Relational Schema file. Post-conditions After the successful execution of this use-case, the user will have ER schema. Basic Flow

F IND T EXT (UC28) 22 Actor actionSystem Response User 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. Actors Users Pre-conditions The user must have some file opened in notepad editor. Post-conditions After the successful execution of this use-case, the user will get to the first successful matched text on the file. Basic Flow

23

24

25

26

27

28