Multiplicity in BADI

[Former Member]

what is the term multiplicity in BADIs, have you ever heard this term explain

[Former Member]

hi,

The multiplicity is the number of participating objects in one class that have a relationship to an object..

UML (Unified Modeling Language) is a standardized modeling language. It is used for the specification,

construction, visualization and documentation of models for software systems and enables uniform

communication between various users.

UML does not describe the steps in the object-oriented development process.

UML is an industry standard and has been standardized by the OMG (Object Management Group) since

September 1997 as UML Version 1.1. The members of the OMG are continuously developing it further.

SAP uses UML as the company-wide standard for object-oriented modeling.

UML describes a number of different diagram types in order to represent different views of a system.

Use-case diagrams show the relationships between agents and actions (use cases), that is, they represent

external system behavior from the user’s point of view.

Class diagrams show the static view of a model.

Interaction diagrams demonstrate the relationships and method calls between objects.

Sequence diagrams emphasize the timing sequence of the method calls, while collaboration diagrams

focus more on the object relationships and their topology.

Status diagrams show a sequence of statuses that an object can adopt during its lifetime, and the stimuli

that cause this status to change.

Activity diagrams are a special type of status diagrams. They mostly or exclusively contain activities.

Component diagrams show the organization and dependencies of components.

Distribution diagrams represent the dependencies of software and hardware.

Class name

lcl_airplane

+ denotes public attributes/methods

denotes private attributes/methods

denotes protected attributes/methods

_ Static attributes/static methods

are marked with an underscore

Methods

name: string

count: i

lcl_airplane

+ set_name(im_name: string)

+ get_count(): i

UML

A class diagram describes the elements contained in the model and their various static relationships. There

are two basic forms of static relationships:

Associations (for example, a flight customer books a flight)

Generalization/specialization (for example a cargo plane and a passenger plane are planes)

Classes can also be shown with their attributes and methods in the class diagrams.

An association describes a semantic relationship between classes. The specific relationship between

objects in these classes is known as an object link. Object links are therefore the instances of an

association.

An association is usually a relationship between different classes. However, an association can also be

recursive; in this case, the class would have a relationship with itself. In most cases, recursive associations

are used to links two different objects in one class.

The points below assume that the associations are binary.

Each association has two roles, one for each direction of the association (flight booking->customer,

customer -> flight booking). Roles can have names (for example, the association flight->flight booking could

be called reservations).

Each role has a cardinality that shows how many instances participate in this relationship. The multiplicity is

the number of participating objects in one class that have a relationship to an object in the other class.

UML notation:

An association is represented by a line between the class symbols.

The cardinality of the relationship can be shown at each end of the line.

Associations can be given a name for ease of identification (a verb or a short text). This name is written in

italics above the line and may have a arrow to show the direction. Both are optional.

Aggregation is a special kind of association. Aggregation describes one object that contains another or

consists of other objects (whole-part). An airplane consists of wings. The relationship can be described by

the words “consists of” or “is a part of”.

UML notation for aggregation:

An aggregation, like an association, is represented by a line between two classes, which then additionally

has a small rhombus at one end. The rhombus is always at the aggregate end, that is, the whole object

end. Otherwise the notation conventions are the same as for associations.

Composition is a special kind of aggregation. Composition describes the fact that the object contained

cannot exist without the aggregate (for example, a flight booking cannot exist without the relevant flight).

Differences between composition and aggregation:

The cardinality on the aggregate side can only be one. Each part is only part of one composite object,

otherwise the existence dependency would be contradictory. The lifetime of the individual parts is linked to

the lifetime of the aggregate: parts are created either with or immediately after the aggregate, and they are

destroyed either with or immediately before the aggregate.

UML notation for composition:

Like aggregation, composition is shown as a line between two classes and marked with a small rhombus

on the aggregate side. However, in contrast to aggregation, the rhombus is filled in.

UML notation:

Generalization and specialization are denoted by triangular arrows that point from the subordinate class to

the superclass.

Several arrows can be summarized into a tree.

Hope this is helpful, Do reward.