Professional Documents
Culture Documents
System Design
System Design
UML DIAGRAMS
GOALS:
The Primary goals in the design of the UML are as follows:
1. Provide users a ready-to-use, expressive visual modeling Language so that
they can develop and exchange meaningful models.
2. Provide extendibility and specialization mechanisms to extend the core
concepts.
3. Be independent of particular programming languages and development
process.
4. Provide a formal basis for understanding the modeling language.
5. Encourage the growth of OO tools market.
6. Support higher level development concepts such as collaborations,
frameworks, patterns and components.
7. Integrate best practices.
USE CASE DIAGRAM:
Login
Post
USER
View
Message
viewMessage
logout
login
viewUser
Admin viewReports
blockUsers
logout
CLASS DIAGRAM:
In software engineering, a class diagram in the Unified Modeling Language
(UML) is a type of static structure diagram that describes the structure of a system
by showing the system's classes, their attributes, operations (or methods), and the
relationships among the classes. It explains which class contains information.
user
Admin
dataset
username
password
register()
login()
login()
post()
viewAllUsers()
viewPost()
viewReports()
message()
blockUsers()
viewMessage()
logout()
logout()
SEQUENCE DIAGRAM:
Register
login
login
viewAllUsers
Post
ViewPost&report
viewReports
Message
blockUsers
ViewMessages
logout
logout
Collaboration
A collaboration diagram, also known as a communication diagram, is an
illustration of the relationships and interactions among software objects in the
Unified Modeling Language (UML). These diagrams can be used to portray the
dynamic behavior of a particular usecase and define the role of each object.
11: logout
1: Register
3: login
5: Post
User 6: ViewPost&report
8: Message
10: ViewMessages
Applicati
on
2: login
4: viewAllUsers
7: viewReports
9: blockUsers
12: logout
Admin