Scribd
Upload
50 views

Use of UML Diagrams

The document discusses how UML diagrams can be useful for database design. Behavioral UML diagrams like use case diagrams, sequence diagrams, and state charts are useful for defining system transactions and processes. For example, a use case diagram for a university website indicates students need a username and password to log in and get admitted. Class diagrams, which are similar to entity-relationship diagrams, are most closely associated with database structure design. Class diagrams define classes, attributes, associations, and relationships between entities. They can provide information needed to design database tables and structure.

Uploaded by

Nityashreeba Gohil
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
50 views

Use of UML Diagrams

The document discusses how UML diagrams can be useful for database design. Behavioral UML diagrams like use case diagrams, sequence diagrams, and state charts are useful for defining system transactions and processes. For example, a use case diagram for a university website indicates students need a username and password to log in and get admitted. Class diagrams, which are similar to entity-relationship diagrams, are most closely associated with database structure design. Class diagrams define classes, attributes, associations, and relationships between entities. They can provide information needed to design database tables and structure.

Uploaded by

Nityashreeba Gohil
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 1

Use of UML Diagrams: During the construction of an application system design we use all the maj or

UML diagrams. But how are these diagrams useful for the database design.
Let us first discuss the behavioural/dynamic diagrams of UML. The use Case Diagrams ar e used to
gather infor mation dur ing the requirement analysis phase. Li kewise the sequence diagram is used to
visualise the execution of the use cases, whi le the collabora tion di agram defines the sequence of
messages. The state Chart Diagram and acti vit y diagram are used to graphically represent some of
the states and acti vities of a system.
Thus, these diagrams are ver y useful for providing the behavioural or functional i nfor mat ion about
databases. Thus, they may be useful for transaction and processing design. For example, a use case
diagram of a student of an on -line Uni versity may be:

This use case diagram is indicating that the student and staff may have to login fi rst, thus, the
implementation of such a system would require a table for user -name and password and f or taking
admission a student may need to have a vali d user name and password. It also indicates t hat the
process of admission will be certified by a staff member, who will allow the student to t ake
admission after due checking. Thus, UML behavioral diagrams may be useful to define
processing/transactions. They also provide some infor mation about entities and attributes. However,
the UML diagram is cl osely a ssociated with database structure design in the class diagram. Let us
discuss these diagrams in more detail in respect of database desi gn and i mplementation.

2.4.1 UML Class Diagrams and Database Design


To begin with, let us f irst recollect what we ha ve learnt about class diagrams. The class diagrams
someti mes may be considered as an alternative notation to E -R diagram. In UML class di agram
contains:
• ‘Class’ – is displayed as a box. It has three sections:

“Top Section” – Class Name


“Middle Section” – Attributes
“Last Section” – Oper ations
• Associations: Relationship Types are called Associations.
• Links: Relationship i nstances are called Li nks.
• Binar y Association: Represented as a line connecting the partici pating classes.
• Linked Attribute: Connected to the Association’s line by dashed line.
• Multiplicities: The (Minimum and Maxi mum) constraints.
• Reflexi ve Association: A Recursi ve Relationship.
• Aggregation: To represent a relationship between a whole obj ect and its component parts.
• Different unidirectional and bi -directional Associations.

You might also like