entity relationship (ER) diagram show types of flowchart that demonstrates
entities such as objects, users and concepts relation to each other within
importance of ER diagram being use to design or debug relationship database in
system development. There are symbols such as rectangles, diamonds, ovals and
connection line are interconnected entities, relationship and their attribute
depending on grammatical structure with entities as nouns and relationship as
verbs. Below ER diagram show relationship of users, admin, login, register, set
of suspicious words concepts relates to each other within system and how users
are communicating through web application and admin interaction with system to
view users shared information and to block the suspicious message not to view
USE CASE DIAGRAM
use case diagram is a diagram that shows the relationships among users and use
cases within a system. Use case diagrams are frequently used to:
Provide an overview of all or part of
the usage requirements for a system
Message scope of a development system
Model your analysis of your usage
requirements in the form of a system use case model
use case model comprised of one or more use case diagrams and any supporting
documentation such as use case specifications and user definitions. Within most
use case models the use case specifications tend to be the primary artifact with
use case diagrams filling a supporting role as the “attach” that
keeps your requirements model together. Use case models are developed from the
point of viewing or detecting suspicious messages that are sent by sender and
receiver through client application and admin department check all activities
made by users. The diagrams included:
Use Case refers to sequence of actions
that provide a measurable value to users and admin depend on function.
Users/Admin is persons, organization, or
external system that plays a role in one or more interactions with your system.
Relationships is a rule in Use Case that
shown as lines connecting two modeling elements with an optional open-headed
arrowhead on one end of the line indicating the direction of the initial invocation
of the relationship.
System Boundary Boxes: The rectangle
around the Use Case is called the system boundary box and as the name suggests
it specifies the scope of system.
Use Case works
Case diagram describe how users and admin integrate with system to perform goal
of system development. Example: there is user1 and users2, and both are
communicating through web application, first User1 register in a username,
password, names and phone number. Then after register, user1 login into website
and also user2 follows the same process done by user1. Users started sending
request and after accepting each other, it allowed to send messages among
has to login and check all sharing details of both users and their informations
when the system streams it to be suspicious word. A system carry out scanning of
all messages and post images to identify suspicious word, short form or code
word, if system found suspicious words from attach messages such as images,
text, and video and so on. A system is not
allowed to share data to users if it contains suspicious words of any kind.
perform task of encoding and decoding plain text hidden in images and detect
suspicious word. Admin can see all details of users and type of suspicious
words that are sent by users.
sequence diagram model shows the flow of logic within our system in a graphic
manner, enabling you both to document and validate logic, and are commonly used
for both analysis and designing better system for detection. Sequence diagram
are the most popular UML object for dynamic modeling, which focuses on
identifying the suspicious words from messages and images of attachments sent.
section start at a simple UML class diagram for the conceptual model for suspicious
word detection. Classes are depicted as boxes with three sections, the tops
indicates the name of the class and middle list the attributes of the class and
the third one list the methods. Administrators have two sections, one for names
and another for listing responsibilities all the classes of the system, their
inter-relationships, and the operations and attributes of the classes.