mit5314: database applicationsslide # 1 visible analyst dr. peeter kirsfall 2003 an introduction to...

MIT5314: Database Applications Slide # 1

Visible Analyst

Dr. Peeter Kirs Fall 2003

An Introduction To Using Visual Analyst to Create an

ERD


Visible Analyst


Visible Analyst is a Computer Aided Software Engineering (CASE) Tool

Among the models included are: Functional Decomposition (Business Model)

• Shows the business functions and processes they support in a hierarchical structure

Entity Relationship Diagram (Data Model) • Shows the data entities of an application and the relationship

between the entities

Object Model (Object Class Model) • Shows classes of Objects, Subclasses, Aggregations, and

Inheritance

• A quick Note: In January 2003, The Visible Developer Professional Edition was selling for $1,995 (Cheap!)


Visible Analyst


Visible Analyst Models (Continued) State Transition Model (Real Time Model)

• Shows object transition to and from various states and conditions and the events or triggers cause them to change between different states

Process Model (Data Flow Diagrams) • Shows how things occur in the organization via a sequence of

processes, actions, stores, inputs and outputs.

• Processes are decomposed into more detail, producing a layered hierarchical structure

Product Model (Structure Chart) • Shows a hierarchical, top-down design map of how the application

will be programmed, built, integrated, and tested


Visible Analyst


Visible Analyst Models (Continued) Use-Case Model

• Shows the relationship between a user and the information system

Activity Model• A special form of the state diagram representing the performance of

actions or subactivities

Sequence Model• Shows how objects collaborate in some behavior

Collaboration Model• Shows an interaction organized around the objects in the interaction

and their links to each other

Repository Model (Database Project_• The Bible of Systems Analysis and Design


Visible Analyst


Open the Visible Analyst Program The First Thing You will see is the start-up menu


Visible Analyst


The Next thing you will see is the main menu:

To start a new project, select New Project from the File Menu


Visible Analyst


When you do, another pop-up menu will appear:

You have now created a Project called Medical which will be stored (in this case) at C:\VISABLE Analyst\Data

Click the OK Button


Visible Analyst


Once you have created a project, Visible Analyst, by default, assumes you will creating a new diagram:

It just happens to be an ERD

(Which is what we want)

Click the OK Button


Visible Analyst


You will now see the ERD Drawing Screen:

Let’s First add the Entity PHYSICIAN

Click on the Entity Button

When you do, your cursor will change:


Visible Analyst


• Move the cursor to some position on the screen (Or keep it where it is)

• Then Right Click

• Another Pop-up menu will then appear asking you to name the entity (Object)

• Label it PHYSICIAN

PHYSICIAN

• Then Press OK


Visible Analyst


You Have now created the Entity Physician

• Next, we need to change to the select mode

• Next we right-click on our entity PHYSICIAN(A Pop-up Menu Will appear)

Define …Change Item …

Stylize …Text Settings …Colors …

CutCopy

Delete

• Choose Define(We are going to add attributes)


Visible Analyst


• Before we can go any further, we need to save our diagram

• Let’s label our diagram as MEDICAL DATABASE

MEDICAL DATABASE

• And then Press OK


Visible Analyst


• A New Pop-up Menu Will appear

• This menu will first ask us for a description of the entity

• Describe what the database is for

(This will become part of the Repository)

• Put in an appropriate description

Contains Information about the Physician employed by the hospital


Visible Analyst


• Alias ??


(We will talk about that later --- Maybe ---)

• To add an attribute, Simply move your cursor to the add field, and start typing in the field name

PHYSID

• As soon as you do, some default values come up

Char No

• These values refer to the data type, the length, and whether or not a Null value can be entered


Visible Analyst


• Notes ??


PHYSID Char No• A GREAT idea – Put in

thoughts about what this means – if it turns out to be wrong, you can change it later

This will be the primary key for the PHYSICIAN table. It will also be the foreign key in table PATIENT

• We will first have to change the null (or missing) values, as necessary • In our case, we know that

PHYSID should be of length 9

9

• Now ADD the attribute to the entity


Visible Analyst


• And the attribute has been added

• For the time being, let’s assume that this is the only attribute

• Click on the EXIT button

A Dialogue Box will remind to save our entry

• Click ‘YES’


Visible Analyst


• It may not look like we did anything, but we did

• There are three ways of viewing the screen:

• The ENTITY LEVEL (which we are in)

• The PRIMARY KEY LEVEL

• The ATTRIBUTE LEVEL

• To see the attribute added, Click on the ATTRIBUTE Level View


Visible Analyst


• Notice that the Entity (PHYSICIAN) and the one attribute we entered (PhysID) are displayed

• Click on the PRIMARY KEY LEVEL Button

• While we are at it, let’s look at the PRIMARY KEY LEVEL screen


Visible Analyst


Where is all the information?Where is all the information?• The PRIMARY KEY LEVEL Screen

Shows ONLY the Entity Name and the Primary Key

• Let’s make PhysID the primary key

• Once again, RIGHT-CLICK on the entity



CutCopy

Delete • And again, Choose DEFINE

• We didn’t designate a Primary Key


Visible Analyst


• Adding a Primary Key is extremely simple

• Click on the primary key button

• A new dialogue Box will appear

• Click on the attribute you wish to make a Primary Key

• And it will appear in the “Columns in Key” Box

PhysID

• Now just press the OK Button


Visible Analyst


• Notice that PhysID is now the Primary Key

• Now let’s go back and see our Diagram Screen

• Click on the EXIT button(This time there will be no reminder to save the object)


Visible Analyst


• Remember, we are still in the PRIMARY KEY LEVEL screen

• Let’s Add another Attribute (You know the drill)

• RIGHT-CLICK on the entity



CutCopy

Delete

• And again, Choose DEFINE


Visible Analyst


• Let’s Add the attribute ‘PhysName’

PhysName

• Once again, the default values will appear in the ‘Type’ and ‘Null’ Fields

Char No

What if we don’t Want the data type ‘Char’ or

we wished to allow ‘Null’ Values?

What if we don’t Want the data type ‘Char’ or

we wished to allow ‘Null’ Values?

• Change them


Visible Analyst


• Let’s change the attribute ‘PhysName’ to an integer

PhysName Char No

(Yes -- I know that’s dumb, but bear with me)

• Click on the Scroll Bar button


Visible Analyst


• The list of all available data types will appear

• Choose the one you want

• Integer ???• Small Integer ???


Visible Analyst


• Clicking on the ‘Null’ Scroll Bar will cause the possibilities to be displayed

• At any rate, we want the attribute ‘PhysName’ to be of data type ‘Char’ and of length 30

(Which we would signify by entering ’30’ in the length field)30


Visible Analyst


• Once again, after we have added our attribute, we need to add it to the list


Visible Analyst


• As soon as we hit the add button, it will be added to the list

• Let’s go back to the Diagram Screen

• Click Exit(Again, there will be no reminder to save)


Visible Analyst


(I have added a few more Attributes)

• Notice that we are in ATTRIBUTE LEVEL Mode

What if we want to add a constraint to an attribute ??

What if we want to add a constraint to an attribute ??

• Not a problem all we need to do is go back to the ‘Define’ menu



CutCopy

Delete


Visible Analyst


• Click on the ‘Check Constraints’ Tab


Visible Analyst


• Click on the ‘Column Check Constraints’ Scroll Bar

(The complete list of attributes will appear)

• Highlight the attribute you wish to put conditions on and click


Visible Analyst


• Click the ‘Add/Remove’ Button

• Add the condition


Visible Analyst


• Now let’s add the entity ‘PATIENT’• Click on the ‘Entity’ Button

• Put the entity wherever you want

• Once again, the label entity dialogue box will ask you to label the object

PATIENT

• After that, Click on the ‘OK’ Button


Visible Analyst


• Add ‘PATIENT’ Attributes as we did before(Make sure you first choose the

‘Select Mode’)

• Notice also that I have expanded the ENTITY folder


Visible Analyst


• We’re now ready to link the tables together• Choose the appropriate relationship from the menu bar

(In our case, this is a one (mandatory) to many (optional) relationship)


Visible Analyst


• After you click on the relationship button, simply connect the tables with your cursor


Visible Analyst


• Another Dialogue box will appear asking you questions about the relationship

• May a Physician have Zero patients?• Enter the name of the relationship

from PHYSICIAN to PATIENT

Treats

• Enter the name of the relationship from PATIENT to PHYSICIAN

Treated By

• Click the ‘OK’ Button


Visible Analyst


• And we have set up a relationship between the tables

Have We ?? Have We ?? • One nice feature about Visible Analyst is that it will

Analyze our diagram for us


Visible Analyst


• Click on the ‘DIAGRAM’ Tool bar option

SymbolsLines

TextConstruct

Change Item

Split Dataflow

Modify View

Delete

Stylize

ConnectSnap Symbols

Snap Lines

Analyze

• Now click on the ‘Analyze’ Option

• Another Menu will pop-up with available options

• Click the ‘OK’ Button

• And, we Appear to be OK


Visible Analyst


• Keep in mind that Visible Analyst is MORE that just a diagramming tool

• It also maintains our REPOSITORY


Visible Analyst


Before going on, let’s review what a Repository does:• A repository is a database for a project that contains information

both captured from your diagrams and entered directly by you.

• It contains metadata that describes the organization’s data and data processing resources

• Provides information about:• What users must know what

• What automated CASE tools that are used to specify and develop information systems

• All Applications that access and manipulate data

• The DBMS that maintain the repository and update system privileges, passwords, and other information


Visible Analyst


• Now, getting back to our Example:

• To check our repository, click on the ‘REPOSITORY’ Tool bar option


Visible Analyst


• Let’s do a Key Analysis

• We forgot to add our foreign key


Visible Analyst


• The procedure for adding a foreign key is straight-forward

• RIGHT-CLICK on the entity

• And again, Choose DEFINE



CutCopy

Delete


Visible Analyst


• One of the options on the ‘Define Item’ Menu is ‘Foreign Keys’


Visible Analyst


• First, Click on the attribute you wish as a foreign key

• Then click on the field you want to relate the foreign key with

(The attribute will be added)

Physician

• Save it• And Exit


Visible Analyst


• Notice that our ATTRIBUTE LEVEL Screen reflects the addition of the foreign key

• Let’s check our repository to make sure everything is OK

DefineDivisions

Key AnalysisKey Synchronization

Model Balancing

Report Query

Syntax Check

Generate Database SchemaGenerate DDS

Generate Code

Reports

• Pick Key AnalysisWhat is going on ?? What is going on ??


Visible Analyst


There are actually a few problems:• Remember how we defined our PHYSICIAN Table• And our PATIENT Table

• We have a mismatch between PHYSICIAN.PhysID and PATIENT.Physician


Visible Analyst


• Another benefit of Visible Analyst is that it will correct these types of problems automatically

• Once again, Click on ‘Repository’

DefineDivisions


Model Balancing

Report Query

Syntax Check


Generate Code

Reports

• Now Click on ‘Key Synchronization’

• The Pop-up Menu will give you some options

• Click ‘OK’


Visible Analyst


• You will be asked to save your synchronization

• So, Save it

NameItWhatYouWish

• Save this file too


Visible Analyst


Are we OK now ?? Are we OK now ?? • Let’s Check ---

DefineDivisions


Model Balancing

Report Query

Syntax Check


Generate Code

Reports

• Click on ‘Key Analysis’

• We appear to be OK


Visible Analyst


Let’s once again take a look at our tables:• First, our PHYSICIAN Table• Next, our PATIENT Table

• The Issue has been resolved


Visible Analyst


• I have added two more entities(You know how to do this)

• Let’s add the Associative entity TREATMENT

• Aside from clicking on the ‘Associative Entity’ Button (instead of the ‘Entity’ Button, the procedure is the same


Visible Analyst


• First, let’s relate PATIENT and TREATMENT(This is a (mandatory) 1 to (optional) Many relationship)

• Next use the mouse to connect the entities

• Then fill in the necessary information


Visible Analyst


• Let’s Check

Are we OK now ?? Are we OK now ??

SymbolsLines

TextConstruct

Change Item

Split Dataflow

Modify View

Delete

Stylize

ConnectSnap Symbols

Snap Lines

Analyze

• Note that this is a WARNING not an ERROR


Visible Analyst


• Let’s Check that

But what about the Repository ?? But what about the Repository ?? DefineDivisions


Model Balancing

Report Query

Syntax Check


Generate Code

Reports

• Once again, we forgot our Foreign Keys


Visible Analyst


• Open the ‘DEFINE’ Menu(Right-Click on TREATMENT)

• Go to the ‘Foreign Keys’ Option

• First link PATIENT and TREATMENT

• Choose the relationship• Then add the attribute

• Move it to the Link

Patient

• This time, Click on ‘Migrate’


Visible Analyst


Migrate ?? Migrate ?? Key Synchronization ‘migrates’ primary keys across normalized relationships to make Foreign Keys in other Entities

It also adds descriptive information about the relationship and the related entities to the Repository

When you created the entity, the Repository created an ‘Associator’ Element Name for it

Visible Analyst uses this information for Key Analysis and Synchronization


Visible Analyst


• Do the same thing for the other relationships

• Select the relationship between TREATMENT and PRESCRIPTION

• Add the attribute

• Move it to the Link

Prescription

• Migrate

• Do it again for the relationship between TREATMENT and ILLNESS


Visible Analyst


• Notice that a strange thing has happened:• The attribute names have been changed to correspond with

their labels in the tables they refer to:

(Due to Synchronization)

• We could change them, or just leave them as is


Visible Analyst


Are we OK now ?? Are we OK now ?? • Let’s Check

DefineDivisions


Model Balancing

Report Query

Syntax Check


Generate Code

Reports


Visible Analyst


• The Only thing we haven’t done is set-up our Unary Relationship (But we know how to)

• Right-Click on PHYSICIAN

• Choose ‘Define’

• Add the field ‘Supervisor’

• Draw the relationship

• Set ‘Supervisor’ as a Foreign Key

-- And We’re Done ---


Visible Analyst


• First, Go to the ‘File’ Option

How do we Open a Different Project ?? How do we Open a Different Project ??


Visible Analyst


• Now Select the project• Let’s Choose Project TEST

• Then Click ‘OK’


Visible Analyst


• Choose (highlight) Entity

• Now open up the ‘Diagram’


Visible Analyst


• Let’s Open the Driver’s License ERD


Visible Analyst


• Let’s Review the ERD:

The Department of Motor Vehicles (DMV)

Has Many Evaluators

Each Evaluator Gives many Road Tests

Many Individuals Apply for Licenses

An Applicant May take may Road Tests

The DMV May (Must?) Issue Many Drivers Licenses


Visible Analyst


Let’s Look at some of Visible Analyst’s other (ERD) options:

• We can Establish Database Security

• We can Modify The Balancing Rules

• We can Modify The SQL Dialect


Visible Analyst


• We can Even:• Generate the DDS

(Data Descriptor Specification)

• Generate the SQL Code Needed

• Create Reports

• Create Report Queries

-- BUT NOT WITH THE STUDENT VERSION ---


Visible Analyst


?? Any Questions ????? Any Questions ???


Visible Analyst


mit5314: database applicationsslide # 1 visible analyst dr. peeter kirsfall 2003 an introduction to...

Documents