Chen's ERD of MMORPG

"In software engineering, an entity–relationship model (ER model) is a data model for describing a database in an abstract way.Chen's notation for entity–relationship modeling uses rectangles to represent entity sets, and diamonds to represent relationships appropriate for first-class objects: they can have attributes and relationships of their own. If an entity set participates in a relationship set, they are connected with a line.
Attributes are drawn as ovals and are connected with a line to exactly one entity or relationship set." [Entity–relationship model. Wikipedia]
This sample Chen's ER-diagram illustrates the structure of a typical MMORP game.
"Massively multiplayer online role-playing game (MMORPG) mixes the genres of role-playing video games and Massively multiplayer online games, possibly in the form of web browser-based games, in which a very large number of players interact with one another within a virtual world.
As in all RPGs, players assume the role of a character (often in a fantasy world or science-fiction world) and take control over many of that character's actions. MMORPGs are distinguished from single-player or small multi-player online RPGs by the number of players, and by the game's persistent world (usually hosted by the game's publisher), which continues to exist and evolve while the player is offline and away from the game." [Massively multiplayer online role-playing game. Wikipedia]
This ERD example was redrawn using the ConceptDraw PRO diagramming and vector drawing software from the Wikipedia file: ER Diagram MMORPG.png. [en.wikipedia.org/ wiki/ File:ER_ Diagram_ MMORPG.png]
This file is licensed under the Creative Commons Attribution-Share Alike 3.0 Unported license. [creativecommons.org/ licenses/ by-sa/ 3.0/ deed.en]
This Chen's ERD example is included in the Entity-Relationship Diagram (ERD) solution from the Software Development area of ConceptDraw Solution Park.

The vector stencils library "Bank UML composite structure diagram" contains 10 shapes for drawing UML composite structure diagrams.
Use it for object-oriented modeling of your bank information system.
"The key composite structure entities identified in the UML 2.0 specification are structured classifiers, parts, ports, connectors, and collaborations.
* Part : A part represents a role played at runtime by one instance of a classifier or by a collection of instances. The part may only name the role, it may name an abstract superclass, or it may name a specific concrete class. The part can include a multiplicity factor, such as the [0..*] shown for Viewer in the diagram.
* Port : A port is an interaction point that can be used to connect structured classifiers with their parts and with the environment. Ports can optionally specify the services they provide and the services they require from other parts of the system. In the diagram, each of the small squares is a port. Each port has a type and is labelled with a name... in the diagram. Ports may contain a multiplicity factor...
* Connector : A connector binds two or more entities together, allowing them to interact at runtime. The connector is shown as a line between some combination of parts, ports and structured classifiers. The diagram shows three connectors between ports, and one connector between a structured classifier and a part.
* Collaboration : A collaboration is generally more abstract than a structured classifier. It is shown as a dotted oval containing roles that instances can play in the collaboration.
* Structured classifier: A StructuredClassifier represents a class, often an abstract class, whose behavior can be completely or partially described through interactions between parts.
An EncapsulatedClassifier is a type of structured classifier that contains ports." [Composite structure diagram. Wikipedia]
This example of UML composite structure diagram symbols for the ConceptDraw PRO diagramming and vector drawing software is included in the ATM UML Diagrams solution from the Software Development area of ConceptDraw Solution Park.

The involvement matrix (responsibility assignment matrix, RAM, RACI matrix, ARCI matrix, linear responsibility chart, LRC) defines the level of involvement and nature of participation . The diagram shows the degree of involvement for all identified parties in the execution of corrective actions.
"Key responsibility roles.
Responsible.
Those who do the work to achieve the task. There is at least one role with a participation type of responsible, although others can be delegated to assist in the work required (see also RASCI below for separately identifying those who participate in a supporting role).
Accountable (also approver or final approving authority).
The one ultimately answerable for the correct and thorough completion of the deliverable or task, and the one who delegates the work to those responsible. In other words, an accountable must sign off (approve) on work that responsible provides. There must be only one accountable specified for each task or deliverable.
Consulted (sometimes counsel).
Those whose opinions are sought, typically subject matter experts; and with whom there is two-way communication.
Informed.
Those who are kept up-to-date on progress, often only on completion of the task or deliverable; and with whom there is just one-way communication." [Responsibility assignment matrix. Wikipedia]
The involvement matrix is one of the Seven Management and Planning Tools (7 MP tools, Seven New Quality Tools).
The person involvement matrix template for the ConceptDraw PRO diagramming and vector drawing software is included in the solution "Seven Management and Planning Tools" from the Management area of ConceptDraw Solution Park.

The vector stencils library "UML class diagrams" contains 38 symbols for the ConceptDraw PRO diagramming and vector drawing software.
"... classes are represented with boxes which contain three parts:
(1) The top part contains the name of the class. It is printed in Bold, centered and the first letter capitalized.
(2) The middle part contains the attributes of the class. They are left aligned and the first letter is lower case.
(3) The bottom part gives the methods or operations the class can take or undertake. They are also left aligned and the first letter is lower case. ...
To indicate a classifier scope for a member, its name must be underlined. ...
An association can be named, and the ends of an association can be adorned with role names, ownership indicators, multiplicity, visibility, and other properties. ...
Aggregation ... is graphically represented as a hollow diamond shape on the containing class end of the tree with a single line that connects the contained class to the containing class.
... graphical representation of a composition relationship is a filled diamond shape on the containing class end of the tree of lines that connect contained class(es) to the containing class.
... graphical representation of a Generalization is a hollow triangle shape on the superclass end of the line (or tree of lines) that connects it to one or more subtypes.
... graphical representation of a Realization is a hollow triangle shape on the interface end of the dashed line (or tree of lines) that connects it to one or more implementers. A plain arrow head is used on the interface end of the dashed line that connects it to its users.
Multiplicity ... representation of an association is a line with an optional arrowhead indicating the role of the object(s) in the relationship, and an optional notation at each end indicating the multiplicity of instances of that entity (the number of objects that participate in the association).
Entity classes ... are drawn as circles with a short line attached to the bottom of the circle. Alternatively, they can be drawn as normal classes with the «entity» stereotype notation above the class name." [Class diagram. Wikipedia]
The example "Design elements - UML class diagrams" is included in the Rapid UML solution from the Software Development area of ConceptDraw Solution Park.

The vector stencils library "LDAP" contains 20 symbols of Lightweight Directory Access Protocol (LDAP) elements for drawing the LDAP Directory Services network structure diagrams.
"The Lightweight Directory Access Protocol (LDAP) is an open, vendor-neutral, industry standard application protocol for accessing and maintaining distributed directory information services over an Internet Protocol (IP) network. Directory services play an important role in developing intranet and Internet applications by allowing the sharing of information about users, systems, networks, services, and applications throughout the network. As examples, directory services may provide any organized set of records, often with a hierarchical structure, such as a corporate email directory. Similarly, a telephone directory is a list of subscribers with an address and a phone number.
LDAP is specified in a series of Internet Engineering Task Force (IETF) Standard Track publications called Request for Comments (RFCs), using the description language ASN.1. The latest specification is Version 3, published as RFC 4511. ...
A common usage of LDAP is to provide a "single sign on" where one password for a user is shared between many services, such as applying a company login code to web pages (so that staff log in only once to company computers, and then are automatically logged into the company intranet).
LDAP is based on a simpler subset of the standards contained within the X.500 standard. Because of this relationship, LDAP is sometimes called X.500-lite." [Lightweight Directory Access Protocol. Wikipedia]
The symbols example "LDAP - Vector stencils library" was created using the ConceptDraw PRO diagramming and vector drawing software extended with the Active Directory Diagrams solution from the Computer and Networks area of ConceptDraw Solution Park.
www.conceptdraw.com/ solution-park/ active-directory-diagrams

The vector stencils library Involvement matrix contains 20 templates and symbols for drawing the involvement matrices using the ConceptDraw PRO diagramming and vector drawing software. The involvement matrix is one of the Seven Management and Planning Tools (7 MP tools, Seven New Quality Tools).
"Matrix Diagram ... shows the relationship between items. At each intersection a relationship is either absent or present. It then gives information about the relationship, such as its strength, the roles played by various individuals or measurements. Six differently shaped matrices are possible: L, T, Y, X, C, R and roof-shaped, depending on how many groups must be compared." [Seven Management and Planning Tools. Wikipedia]
Use it to show what people and groups are involved in actions, and what their role is in every action.
The example "Design elements - Involvement matrix" is included in the solution "Seven Management and Planning Tools" from the Management area of ConceptDraw Solution Park.

This agile software development infographic example illustrates roles in disciplined agile delivery (DAD).
"Disciplined agile delivery (DAD) is a process decision framework that enables simplified process decisions around incremental and iterative solution delivery. DAD builds on the many practices espoused by advocates of agile software development, including Scrum, agile modeling, lean software development, and others." [Disciplined agile delivery. Wikipedia]
The infographic sample "Roles on DAD teams" was created using the ConceptDraw PRO software extended with the Scrum solution from the Project Management area of ConceptDraw Solution Park.

The vector stencils library "UML composite structure diagrams" contains 36 symbols for the ConceptDraw PRO diagramming and vector drawing software.
"The key composite structure entities identified in the UML 2.0 specification are structured classifiers, parts, ports, connectors, and collaborations.
(1) Part : A part represents a role played at runtime by one instance of a classifier or by a collection of instances. The part may only name the role, it may name an abstract superclass, or it may name a specific concrete class. The part can include a multiplicity factor, such as the [0..*] shown for Viewer in the diagram.
(2) Port : A port is an interaction point that can be used to connect structured classifiers with their parts and with the environment. Ports can optionally specify the services they provide and the services they require from other parts of the system. In the diagram, each of the small squares is a port. Each port has a type and is labelled with a name, such as "var", "indVar1", or "view" in the diagram. Ports may contain a multiplicity factor, for example.
Ports can either delegate received requests to internal parts, or they can deliver these directly to the behavior of the structured classifier that the port is contained within. Public ports that are visible in the environment are shown straddling the boundary, while protected ports that are not visible in the environment are shown inside the boundary. All the ports in the diagram are public, except for the view port along the right boundary of FibonacciSystem.
(3) Connector : A connector binds two or more entities together, allowing them to interact at runtime. The connector is shown as a line between some combination of parts, ports and structured classifiers. The diagram shows three connectors between ports, and one connector between a structured classifier and a part.
(4) Collaboration : A collaboration is generally more abstract than a structured classifier. It is shown as a dotted oval containing roles that instances can play in the collaboration.
(5) Structured classifier : A StructuredClassifier represents a class, often an abstract class, whose behavior can be completely or partially described through interactions between parts." [Composite structure diagram. Wikipedia]
The example "Design elements - UML composite structure diagrams" is included in the Rapid UML solution from the Software Development area of ConceptDraw Solution Park.