Lecture 5

Data Modeling Using the

Entity-Relationship (ER) Model

Copyright © 2016 Ramez Elmasri and Shamkant B. Navathe Slide 6- 1

Chapter Outline
 Overview of Database Design Process
 Example Database Application (COMPANY)
 ER Model Concepts
 Entities and Attributes
 Entity Types, Value Sets, and Key Attributes
 Relationships and Relationship Types
 Weak Entity Types
 Roles and Attributes in Relationship Types
 ER Diagrams - Notation
 ER Diagram for COMPANY Schema
 Relationships of Higher Degree

Copyright © 2016 Ramez Elmasr and Shamkant B. Navathei Slide 3- 2

Overview of Database Design Process
 Two main activities:
 Database design
 Applications design
 Focus in this chapter on conceptual database
design
 To design the conceptual schema for a database
application
 Applications design focuses on the programs and
interfaces that access the database
 Generally considered part of software engineering

Copyright © 2016 Ramez Elmasr and Shamkant B. Navathei Slide 3- 3

Entity Relationship Model (ERM)
 Basis of an entity relationship diagram (ERD)
 ERD depicts the:
 Conceptual database as viewed by end user
 Database’s main components
 Entities
 Attributes
 Relationships
 Entity - Refers to the entity set and not to a
single entity occurrence

Copyright © 2016 Ramez Elmasr and Shamkant B. Navathei 4

An ER Schema Daigram for
COMPANY

Copyright © 2016 Ramez Elmasr and Shamkant B. Navathei Slide 3- 5

Example COMPANY Database
 We need to create a database schema design
based on the following (simplified) requirements
of the COMPANY Database:
 The company is organized into DEPARTMENTs.
Each department has a name, number and an
employee who manages the department. We keep
track of the start date of the department manager.
A department may have several locations.
 A department may control a number of projects,
each of which has a unique name, a unique
number, and a single location.

Copyright © 2016 Ramez Elmasr and Shamkant B. Navathei Slide 3- 6

Example COMPANY Database
(Continued)
 The database will store each EMPLOYEE’s social
security number, address, salary, sex, and birthdate.
 Each employee works for one department but may
work on several projects.
 The DB will keep track of the number of hours per
week that an employee currently works on each
project.
 It is required to keep track of the direct supervisor of
each employee.
 Each employee may have a number of
DEPENDENTs.
 For each dependent, the DB keeps a record of name,
sex, birthdate, and relationship to the employee.
Copyright © 2016 Ramez Elmasr and Shamkant B. Navathei Slide 3- 7
ER Model Concepts
 Entities and Attributes
 Entity is a basic concept for the ER model. Entities are
specific things or objects in the mini-world that are
represented in the database.
 For example the EMPLOYEE John Smith, the Research
DEPARTMENT, the ProductX PROJECT
 Attributes are properties used to describe an entity.
 For example an EMPLOYEE entity may have the attributes
Name, SSN, Address, Sex, BirthDate
 A specific entity will have a value for each of its attributes.
 For example a specific employee entity may have
Name='John Smith', SSN='123456789', Address ='731,
Fondren, Houston, TX', Sex='M', BirthDate='09-JAN-55‘
 Each attribute has a value set (or data type) associated with
it – e.g. integer, string, date, enumerated type, …

Copyright © 2016 Ramez Elmasr and Shamkant B. Navathei Slide 3- 8

Types of Attributes (1)
 Simple
 Each entity has a single atomic value for the attribute. For
example, SSN or Sex.
 Composite
 The attribute may be composed of several components. For
example:
 Address(Apt#, House#, Street, City, State, ZipCode, Country), or
 Name(FirstName, MiddleName, LastName).
 Composition may form a hierarchy where some components
are themselves composite.
 Multi-valued
 An entity may have multiple values for that attribute. For
example, Color of a CAR or PreviousDegrees of a STUDENT.
 Denoted as {Color} or {PreviousDegrees}.

Copyright © 2016 Ramez Elmasr and Shamkant B. Navathei Slide 3- 9

Types of Attributes (2)
 In general, composite and multi-valued attributes
may be nested arbitrarily to any number of levels,
although this is rare.
 For example, PreviousDegrees of a STUDENT is
a composite multi-valued attribute denoted by
{PreviousDegrees (College, Year, Degree, Field)}
 Multiple PreviousDegrees values can exist
 Each has four subcomponent attributes:
 College, Year, Degree, Field

Copyright © 2016 Ramez Elmasr and Shamkant B. Navathei Slide 3- 10

Example of a composite attribute

Copyright © 2016 Ramez Elmasr and Shamkant B. Navathei Slide 3- 11

Entity Types and Key Attributes (1)
 Entities with the same basic attributes are
grouped or typed into an entity type.
 For example, the entity type EMPLOYEE
and PROJECT.
 An attribute of an entity type for which each
entity must have a unique value is called a
key attribute of the entity type.
 For example, SSN of EMPLOYEE.

Copyright © 2016 Ramez Elmasr and Shamkant B. Navathei Slide 3- 12

Entity Types and Key Attributes (2)
 A key attribute may be composite.
 VehicleTagNumber is a key of the CAR entity

type with components (Number, State).

 An entity type may have more than one key.
 The CAR entity type may have two keys:

 VehicleIdentificationNumber (popularly called VIN)

 VehicleTagNumber (Number, State), aka license
plate number.
 Each key is underlined (Note: this is different from
the relational schema where only one “primary
key is underlined).
Copyright © 2016 Ramez Elmasr and Shamkant B. Navathei Slide 3- 13
 Entity Set
 Each entity type will have a collection of entities
stored in the database
 Called the entity set or sometimes entity collection
 Previous slide shows three CAR entity instances in
the entity set for CAR
 Same name (CAR) used to refer to both the entity
type and the entity set
 However, entity type and entity set may be given
different names
 Entity set is the current state of the entities of that
type that are stored in the database
Copyright © 2016 Ramez Elmasr and Shamkant B. Navathei Slide 3- 14
Value Sets (Domains) of Attributes
 Each simple attribute is associated with a value
set
 E.g., Lastname has a value which is a character
string of upto 15 characters, say
 Date has a value consisting of MM-DD-YYYY
where each letter is an integer
 A value set specifies the set of values associated
with an attribute

Copyright © 2016 Ramez Elmasr and Shamkant B. Navathei Slide 3- 15

Displaying an Entity type
 In ER diagrams, an entity type is displayed in a
rectangular box
 Attributes are displayed in ovals
 Each attribute is connected to its entity type
 Components of a composite attribute are
connected to the oval representing the composite
attribute
 Each key attribute is underlined
 Multivalued attributes displayed in double ovals
 See the full ER notation in advance on the next
slide

Copyright © 2016 Ramez Elmasr and Shamkant B. Navathei Slide 3- 16

NOTATION for ER diagrams

Copyright © 2016 Ramez Elmasr and Shamkant B. Navathei Slide 3- 17

Entity Type CAR with two keys and a
corresponding Entity Set

Copyright © 2016 Ramez Elmasr and Shamkant B. Navathei Slide 3- 18

Initial Conceptual Design of Entity Types
for the COMPANY Database Schema
 Based on the requirements, we can identify four
initial entity types in the COMPANY database:
 DEPARTMENT
 PROJECT
 EMPLOYEE
 DEPENDENT
 Their initial conceptual design is shown on the
following slide
 The initial attributes shown are derived from the
requirements description
Copyright © 2016 Ramez Elmasr and Shamkant B. Navathei Slide 3- 19
Initial Design of Entity Types:
EMPLOYEE, DEPARTMENT, PROJECT, DEPENDENT

Copyright © 2016 Ramez Elmasr and Shamkant B. Navathei Slide 3- 20

Refining the initial design by introducing
relationships
 The initial design is typically not complete
 Some aspects in the requirements will be
represented as relationships
 ER model has three main concepts:
 Entities (and their entity types and entity sets)
 Attributes (simple, composite, multivalued)
 Relationships (and their relationship types and
relationship sets)
 We introduce relationship concepts next

Copyright © 2016 Ramez Elmasr and Shamkant B. Navathei Slide 3- 21

Relationships and Relationship Types (1)
 A relationship relates two or more distinct entities with a
specific meaning.
 For example, EMPLOYEE John Smith works on the ProductX
PROJECT, or EMPLOYEE Franklin Wong manages the
Research DEPARTMENT.
 Relationships of the same type are grouped or typed into
a relationship type.
 For example, the WORKS_ON relationship type in which
EMPLOYEEs and PROJECTs participate, or the MANAGES
relationship type in which EMPLOYEEs and DEPARTMENTs
participate.
 The degree of a relationship type is the number of
participating entity types.
 Both MANAGES and WORKS_ON are binary relationships.

Copyright © 2016 Ramez Elmasr and Shamkant B. Navathei Slide 3- 22

Relationship instances of the WORKS_FOR N:1
relationship between EMPLOYEE and DEPARTMENT

Copyright © 2016 Ramez Elmasr and Shamkant B. Navathei Slide 3- 23

Relationship instances of the M:N WORKS_ON
relationship between EMPLOYEE and PROJECT

Copyright © 2016 Ramez Elmasr and Shamkant B. Navathei Slide 3- 24

Relationship type vs. relationship set (1)
 Relationship Type:
 Is the schema description of a relationship
 Identifies the relationship name and the
participating entity types
 Also identifies certain relationship constraints
 Relationship Set:
 The current set of relationship instances
represented in the database
 The current state of a relationship type

Copyright © 2016 Ramez Elmasr and Shamkant B. Navathei Slide 3- 25

Relationship type vs. relationship set (2)
 Previous figures displayed the relationship sets
 Each instance in the set relates individual participating
entities – one from each participating entity type
 In ER diagrams, we represent the relationship type as
follows:
 Diamond-shaped box is used to display a relationship

type
 Connected to the participating entity types via straight

lines
 Note that the relationship type is not shown with an

arrow. The name should be typically be readable from

left to right and top to bottom.
Copyright © 2016 Ramez Elmasr and Shamkant B. Navathei Slide 3- 26
Refining the COMPANY database
schema by introducing relationships
 By examining the requirements, six relationship types are
identified
 All are binary relationships( degree 2)
 Listed below with their participating entity types:
 WORKS_FOR (between EMPLOYEE, DEPARTMENT)
 MANAGES (also between EMPLOYEE, DEPARTMENT)
 CONTROLS (between DEPARTMENT, PROJECT)
 WORKS_ON (between EMPLOYEE, PROJECT)
 SUPERVISION (between EMPLOYEE (as subordinate),
EMPLOYEE (as supervisor))
 DEPENDENTS_OF (between EMPLOYEE, DEPENDENT)

Copyright © 2016 Ramez Elmasr and Shamkant B. Navathei Slide 3- 27

ER DIAGRAM – Relationship Types are:
WORKS_FOR, MANAGES, WORKS_ON, CONTROLS, SUPERVISION, DEPENDENTS_OF

Copyright © 2016 Ramez Elmasr and Shamkant B. Navathei Slide 3- 28

Discussion on Relationship Types
 In the refined design, some attributes from the initial entity
types are refined into relationships:
 Manager of DEPARTMENT -> MANAGES
 Works_on of EMPLOYEE -> WORKS_ON
 Department of EMPLOYEE -> WORKS_FOR
 etc
 In general, more than one relationship type can exist
between the same participating entity types
 MANAGES and WORKS_FOR are distinct relationship
types between EMPLOYEE and DEPARTMENT
 Different meanings and different relationship instances.

Copyright © 2016 Ramez Elmasr and Shamkant B. Navathei Slide 3- 29

Constraints on Relationships
 Constraints on Relationship Types
 (Also known as ratio constraints)
 Cardinality Ratio (specifies maximum participation)
 One-to-one (1:1)
 One-to-many (1:N) or Many-to-one (N:1)
 Many-to-many (M:N)
 Existence Dependency Constraint (specifies minimum
participation) (also called participation constraint)
 zero (optional participation, not existence-dependent)
 one or more (mandatory participation, existence-dependent)

Copyright © 2016 Ramez Elmasr and Shamkant B. Navathei Slide 3- 30

Cardinality Ratios for Binary
Relationships
 The cardinality ratio for a binary relationship specifies the maximum number
of relationship instances that an entity can participate in.

 For example, in the WORKS_FOR binary relationship type,

DEPARTMENT:EMPLOYEE is of cardinality ratio 1:N, meaning that each
department can be related to (that is, employs) any number of employees (N),
but an employee can be related to (work for) at most one department (1).

 This means that for this particular relationship type WORKS_FOR, a

particular department entity can be related to any number of employees (N
indicates there is no maximum number). On the other hand, an employee can
be related to a maximum of one department.

 The possible cardinality ratios for binary relationship types are 1:1, 1:N, N:1,
and M:N

Copyright © 2016 Ramez Elmasr and Shamkant B. Navathei Slide 6- 31

Many-to-one (N:1) Relationship

Copyright © 2016 Ramez Elmasr and Shamkant B. Navathei Slide 3- 32

One-to-one (1:1) Relationship

Copyright © 2016 Ramez Elmasr and Shamkant B. Navathei Slide 6- 33

Many-to-many (M:N) Relationship

Copyright © 2016 Ramez Elmasr and Shamkant B. Navathei Slide 3- 34

Existence Dependency Constraint
or participation constraint
 Participation Constraints and Existence Dependencies- The
participation constraint specifies whether the existence of an entity
depends on its being related to another entity via the relationship type.

 This constraint specifies the minimum number of relationship instances that

each entity can participate in and is sometimes called the minimum
cardinality constraint.

 There are two types of participation constraints—total and partial—that we

illustrate by example.

 We will refer to the cardinality ratio and participation constraints,

taken together, as the structural constraints of a relationship type.

Copyright © 2016 Ramez Elmasr and Shamkant B. Navathei Slide 6- 35

Total and Partial Participation
 Total Participation - If a company policy states that every employee must work for a
department, then an employee entity can exist only if it participates in at least one
WORKS_FOR relationship instance (Figure 3.9). Thus, the participation of EMPLOYEE in
WORKS_FOR is called total participation, meaning that every entity in the total set of
employee entities must be related to a department entity via WORKS_FOR. Total
participation is also called existence dependency .

 Partial Participation - In Figure 3.12 we do not expect every employee to manage a

department, so the participation of EMPLOYEE in the MANAGES relationship type is
partial, meaning that some or part of the set of employee entities are related to some
department entity via MANAGES, but not necessarily all.

 In ER diagrams, total participation (or existence dependency) is displayed as a double

line connecting the participating entity type to the relationship, whereas partial
participation is represented by a single line (see Figure 3.2).

Copyright © 2016 Ramez Elmasr and Shamkant B. Navathei Slide 3- 36

Recursive Relationship Type
 A relationship type between the same participating entity
type in distinct roles
 Also called a self-referencing relationship type.
 Example: the SUPERVISION relationship
 EMPLOYEE participates twice in two distinct roles:
 supervisor (or boss) role
 supervisee (or subordinate) role
 Each relationship instance relates two distinct
EMPLOYEE entities:
 One employee in supervisor role
 One employee in supervisee role

Copyright © 2016 Ramez Elmasr and Shamkant B. Navathei Slide 3- 37

Displaying a recursive
relationship
 In a recursive relationship type.
 Both participations are same entity type in

different roles.
 For example, SUPERVISION relationships

between EMPLOYEE (in role of supervisor or

boss) and (another) EMPLOYEE (in role of
subordinate or worker).
 In following figure, first role participation labeled
with 1 and second role participation labeled with
2.
 In ER diagram, need to display role names to
distinguish participations.

Copyright © 2016 Ramez Elmasr and Shamkant B. Navathei Slide 3- 38

A Recursive Relationship Supervision`

Copyright © 2016 Ramez Elmasr and Shamkant B. Navathei Slide 3- 39

Recursive Relationship Type is: SUPERVISION
(participation role names are shown)

Copyright © 2016 Ramez Elmasr and Shamkant B. Navathei Slide 3- 40

Weak Entity Types
 An entity that does not have a key attribute and that is identification-
dependent on another entity type.
 A weak entity must participate in an identifying relationship type with
an owner or identifying entity type
 Entities are identified by the combination of:
 A partial key of the weak entity type

 The particular entity they are related to in the identifying

relationship type
 Example:
 A DEPENDENT entity is identified by the dependent’s first name,

and the specific EMPLOYEE with whom the dependent is related

 Name of DEPENDENT is the partial key

 DEPENDENT is a weak entity type

 EMPLOYEE is its identifying entity type via the identifying

relationship type DEPENDENT_OF

Copyright © 2016 Ramez Elmasr and Shamkant B. Navathei Slide 3- 41

Partial Key
 A weak entity type normally has a partial key, which is
the attribute that can uniquely identify weak entities that
are related to the same owner entity.

 In our example, if we assume that no two dependents of

the same employee ever have the same first name, the
attribute Name of DEPENDENT is the partial key. In the
worst case, a composite attribute of all the weak entity’s
attributes will be the partial key.

Copyright © 2016 Ramez Elmasr and Shamkant B. Navathei Slide 6- 42

Weak Entity Type Example
 Here we see a (strong) entity type “DogOwner” and a dependent
weak entity type “Dog” that is connected via the identifying
relationship “owns”.
 The entity type “Dog” has attribute “name” which is not globally
unique (i.e., there might be more than one dog with the same name),
but is unique for a certain dog owner (i.e., an owner never owns two
dogs with the same name).
 In this case “name” cannot be a (primary) key of the entity type “Dog”,
since it is not globally unique, but it is a partial key, because if we
combine it with the key of its owner we can uniquely identify a dog.

Copyright © 2016 Ramez Elmasr and Shamkant B. Navathei

Attributes of Relationship types
 A relationship type can have attributes:
 For example, HoursPerWeek of WORKS_ON
 Its value for each relationship instance describes
the number of hours per week that an EMPLOYEE
works on a PROJECT.
 A value of HoursPerWeek depends on a particular
(employee, project) combination
 Most relationship attributes are used with M:N
relationships
 In 1:N relationships, they can be transferred to the
entity type on the N-side of the relationship

Copyright © 2016 Ramez Elmasr and Shamkant B. Navathei Slide 3- 44

 Attributes of Relationship types
(Continued)
 Attributes of 1:1 or 1:N relationship types
 can be migrated to one of the participating entity types.

 For example, the Start_date attribute for the MANAGES

relationship can be an attribute of either EMPLOYEE (manager) or
DEPARTMENT.

 Although conceptually it belongs to MANAGES. This is because

MANAGES is a 1:1 relationship, so every department or employee
entity participates in at most one relationship instance. Hence, the
value of the Start_date attribute can be determined separately, either
by the participating department entity or by the participating employee
(manager) entity.

Copyright © 2016 Ramez Elmasr and Shamkant B. Navathei Slide 3- 45

Attributes of Relationship types
(Continued)
 For a 1:N relationship type, a relationship attribute can be migrated
only to the entity type on the N-side of the relationship.
 For example, in Figure 3.9, if the WORKS_FOR relationship also has an
attribute Start_date that indicates when an employee started working for a
department, this attribute can be included as an attribute of EMPLOYEE.

 This is because each employee works for at most one department, and
hence participates in at most one relationship instance in WORKS_FOR,
but a department can have many employees, each with a different start
date.

 In both 1:1 and 1:N relationship types, the decision where to place a
relationship attribute—as a relationship type attribute or as an
attribute of a participating entity type—is determined subjectively by
the schema designer.

Copyright © 2016 Ramez Elmasr and Shamkant B. Navathei

Attributes of Relationship types
(Continued)
 For M:N (many-to-many) relationship types, some
attributes may be determined by the combination of
participating entities in a relationship instance, not by any
single entity. Such attributes must be specified as
relationship attributes.
 An example is the Hours attribute of the M:N relationship
WORKS_ON (Figure 3.13); the number of hours per week
an employee currently works on a project is determined
by an employee-project combination and not separately
by either entity

Copyright © 2016 Ramez Elmasr and Shamkant B. Navathei Slide 3- 47

Example Attribute of a Relationship Type:
Hours of WORKS_ON

Copyright © 2016 Ramez Elmasr and Shamkant B. Navathei Slide 3- 48

Notation for Constraints on
Relationships
 Cardinality ratio (of a binary relationship): 1:1,
1:N, N:1, or M:N
 Shown by placing appropriate numbers on the
relationship edges.
 Participation constraint (on each participating
entity type): total (called existence dependency)
or partial.
 Total shown by double line, partial by single line.
 NOTE: These are easy to specify for Binary
Relationship Types.

Copyright © 2016 Ramez Elmasr and Shamkant B. Navathei Slide 3- 49

Alternative (min, max) notation for
relationship structural constraints:
 Specified on each participation of an entity type E in a relationship
type R
 Specifies that each entity e in E participates in at least min and at
most max relationship instances in R
 Default(no constraint): min=0, max=n (signifying no limit)
 Must have minmax, min0, max 1
 Derived from the knowledge of mini-world constraints
 Examples:
 A department has exactly one manager and an employee can

manage at most one department.

 Specify (0,1) for participation of EMPLOYEE in MANAGES
 Specify (1,1) for participation of DEPARTMENT in MANAGES
 An employee can work for exactly one department but a
department can have any number of employees.
 Specify (1,1) for participation of EMPLOYEE in WORKS_FOR
 Specify (1,n) for participation of DEPARTMENT in WORKS_FOR

Copyright © 2016 Ramez Elmasr and Shamkant B. Navathei Slide 3- 50

The (min,max) notation for
relationship constraints

Read the min,max numbers next to the entity

type and looking away from the entity type

Copyright © 2016 Ramez Elmasr and Shamkant B. Navathei Slide 3- 51

COMPANY ER Schema Diagram using (min,
max) notation

Copyright © 2016 Ramez Elmasr and Shamkant B. Navathei Slide 3- 52

Alternative diagrammatic notation
 ER diagrams is one popular example for
displaying database schemas
 Many other notations exist in the literature and in
various database design and modeling tools
 Appendix A illustrates some of the alternative
notations that have been used
 UML class diagrams is representative of another
way of displaying ER concepts that is used in
several commercial design tools

Copyright © 2016 Ramez Elmasr and Shamkant B. Navathei Slide 3- 53

Summary of notation for ER diagrams

Copyright © 2016 Ramez Elmasr and Shamkant B. Navathei Slide 3- 54

Relationships of Higher Degree
 Relationship types of degree 2 are called binary
 Relationship types of degree 3 are called ternary
and of degree n are called n-ary
 In general, an n-ary relationship is not equivalent
to n binary relationships
 Constraints are harder to specify for higher-
degree relationships (n > 2) than for binary
relationships

Copyright © 2016 Ramez Elmasr and Shamkant B. Navathei Slide 3- 55

Discussion of n-ary relationships (n > 2)
 In general, 3 binary relationships can represent different
information than a single ternary relationship (see Figure
3.17a and b on next slide)
 If needed, the binary and n-ary relationships can all be
included in the schema design (see Figure 3.17a and b,
where all relationships convey different meanings)
 In some cases, a ternary relationship can be represented
as a weak entity if the data model allows a weak entity
type to have multiple identifying relationships (and hence
multiple owner entity types) (see Figure 3.17c)

Copyright © 2016 Ramez Elmasr and Shamkant B. Navathei Slide 3- 56

Example of a ternary relationship

Copyright © 2016 Ramez Elmasr and Shamkant B. Navathei Slide 3- 57

Chapter Summary
 ER Model Concepts: Entities, attributes,
relationships
 Constraints in the ER model
 Using ER in step-by-step mode conceptual
schema design for the COMPANY database
 ER Diagrams - Notation
 Alternative Notations – UML class diagrams,
others
 Binary Relationship types and those of higher
degree.
Copyright © 2016 Ramez Elmasr and Shamkant B. Navathei Slide 3- 58
Data Modeling Tools (Additional
Material )
 A number of popular tools that cover conceptual modeling
and mapping into relational schema design.
 Examples: ERWin, S- Designer (Enterprise Application
Suite), ER- Studio, etc.
 POSITIVES:
 Serves as documentation of application requirements, easy
user interface - mostly graphics editor support
 NEGATIVES:
 Most tools lack a proper distinct notation for relationships
with relationship attributes
 Mostly represent a relational design in a diagrammatic form
rather than a conceptual ER-based design

Copyright © 2016 Ramez Elmasr and Shamkant B. Navathei Slide 3- 59

 Some of the Automated Database
Design Tools (Note: Not all may be on the market now)
COMPANY TOOL FUNCTIONALITY
Embarcadero ER Studio Database Modeling in ER
Technologies
DB Artisan Database administration, space and security management

Oracle Developer 2000/Designer 2000 Database modeling, application development

Popkin Software System Architect 2001 Data modeling, object modeling, process modeling,
structured analysis/design
Platinum Enterprise Modeling Suite: Erwin, Data, process, and business component modeling
(Computer BPWin, Paradigm Plus
Associates)
Persistence Inc. Pwertier Mapping from O-O to relational model

Rational (IBM) Rational Rose UML Modeling & application generation in C++/JAVA
Resolution Ltd. Xcase Conceptual modeling up to code maintenance
Sybase Enterprise Application Suite Data modeling, business logic modeling
Visio Visio Enterprise Data modeling, design/reengineering Visual Basic/C++

Copyright © 2016 Ramez Elmasr and Shamkant B. Navathei Slide 3- 60