1 / 28

Dbxpert : CASE Tool

Project Advisor: Prof. Ishaq Raza. Dbxpert : CASE Tool. Group Members: SHEIKH HASSAN IMTIAZ L1F06BSCS0024 MUHAMMAD NABEEL ARIF L1S07BSCS0019 MUHAMMAD NOUMAN L1S09BSCS0018. software Requirement Specification. Purpose.

elisha
Download Presentation

Dbxpert : CASE Tool

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Project Advisor: Prof. IshaqRaza Dbxpert: CASE Tool 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) • 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

  12. Draw ER schema Diagram (UC3) Actors • Users Pre-conditions NA Post-conditions After the successful execution of this use-case , the user will have a ER diagram . Basic Flow

  13. Write Relational schema in TXT (UC4) 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

  14. Draw Relational Model (UC6) Actors • Users Pre-conditions NA Post-conditions After 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) 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

  16. Convert ER schema in txt format into ER Schema Diagram (UC9) 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

  17. Convert ER schema in xml format into ER schema Diagram (UC11) 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

  18. Convert ER schema Diagram into ER schema in txt format (UC12) 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

  19. Convert Relational Schema Diagram into Relational schema in txt (UC18) 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

  20. Forward Engineering (UC20) 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

  21. Reverse Engineering (UC21) 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

  22. Find Text (UC28) 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. Screen-Shorts from Current Work

  24. Thank you

More Related