Templates | QualiWare Center of Excellence

Object Generalization

Object generalization in a business diagram refers to the process of creating a more general class or category of objects or components that share similar characteristics or behaviors. Object generalization is used to simplify the representation of complex systems by grouping similar objects or components together.

For example, a line might connect a specific product to a product category to represent how the product belongs to a more general category of products. Similarly, a line might connect a specific customer to a customer type to represent how the customer belongs to a more general category of customers.

The ObjectGeneralization tab

Property	Metamodel name	Description
Short Description	ShortDescription	Short verbal description of the generalization

Operation

The specification of a service that may be requested from objects.

Operation properties

The Operation tab

Property	Metamodel name	Description
Short Description	ShortDescription
Type	MethodType	Choices are: Normal Constructor Destructor Message
Modifier	Modifier	Choices are: Normal Virtual Static
Property	Property	Choices are: Root Leaf Abstract
Group
Sequential	Sequential	Initial value is on.
Guarded	Guarded	Initial value is off.
Concurrent	Concurrent	Initial value is off.
isQuery	isQuery	Initial value is off.
Parameters	HasParameters	Links to: Parameter.

The Precondition tab

Property	Metamodel name	Description
Precondition	PreCondition

The Signals tab

Property	Metamodel name	Description
Outbound	RaisedSignals	Links to: Signal.
Reception	ReceivedSignals	Links to: Signal.

The Postcondition tab

Property	Metamodel name	Description
Postcondition	PostCondition

The Extensions tab

Property	Metamodel name	Description
Stereotype	Stereotype	Links to: Stereotype.
Constraints	HasConstraints	Links to: Constraint.
Tagged values	HasTaggedValues	Links to: TagDefinition.

Opportunity

An opportunity refers to a positive external factor that can be leveraged to improve a process, workflow, or journey. It is a chance or possibility that can be seized to create benefits and enhance outcomes. For example, in a customer journey map, an opportunity might refer to a new market or a gap in the market that can be filled.

Outcome : Archimate

Outcomes are high-level, business-oriented results produced by capabilities of an organization, and by inference by the core elements of its architecture that realize these capabilities. Outcomes are tangible, possibly quantitative, and time-related, and can be associated with assessments. An outcome may have a different value for different stakeholders.

The notion of outcome is important in business outcome-driven approaches to Enterprise Architecture and in capability-based planning. Outcomes are closely related to requirements, goals, and other intentions. Outcomes are the end results, and goals or requirements are often formulated in terms of outcomes that should be realized. Capabilities are designed to achieve such outcomes.
Outcome names should unambiguously identify end results that have been achieved in order to avoid confusion with actions or goals. At a minimum, outcome names should consist of a noun identifying the end result followed by a past-tense verb or adjective indicating that the result has been achieved. Examples include “First-place ranking achieved” and “Key supplier partnerships in place”. Outcome names can also be more specific; e.g., “2015 quarterly profits rose 10% year over year beginning in Q3”.

Package

A package is a general purpose grouping mechanism.

Package properties

The Package tab

Property	Metamodel name	Description
Short Description	ShortDescription
Display contents	Display	Initial value is off.
Visibility	Visibility	Choices are: Protected Public Private Package
Owns	Owns	Links to: All templates.

The References tab

Property	Metamodel name	Description
References	References	Links to: All templates.

The Extensions tab

Property	Metamodel name	Description
Stereotype	Stereotype	Links to: Stereotype.
Constraints	HasConstraints	Links to: Constraint.
Tagged values	HasTaggedValues	Links to: TagDefinition.

Parameter

Description of a parameter to or from an operation.

Parameter properties

The Parameter tab

Property	Metamodel name	Description
Default value	DefaultValue
Kind	Kind	Choices are: in out inout return
Type	HasType	Links to: DataType, Interface, Class.
Transfer method	TransferMethod	Choices are: value reference pointer

The Extensions tab

Property	Metamodel name	Description
Stereotype	Stereotype	Links to: Stereotype.
Constraints	HasConstraints	Links to: Constraint.
Tagged values	HasTaggedValues	Links to: TagDefinition.

Partner Link

A PartnerLink is a physical place where a process is running

Path : ArchiMate

A path is used to model the logical communication (or distribution) relations between nodes. It is realized by one or more communication networks (or distribution networks when modeling physical elements; see Chapter 11), which represent the physical communication (or distribution) links. The properties (e.g., bandwidth, latency) of a path are usually aggregated from these underlying networks.
A path connects two or more nodes. A path is realized by one or more networks. A path can aggregate nodes.

Path properties

The Path tab

Property	Metamodel name	Description
Short description	ShortDescription
Implements	Implements	Links to: All templates.
BreaksDownTo	BreaksDownTo	Links to: All templates.

Peripheral

A peripheral can be any type of item which exists in the infra structure which you want to add to a InfraStructureDiagram. Typically it is a hardware device which is physically defined by a HardwareComponent.

Peripheral properties

The Peripheral tab

Property	Metamodel name	Description
Short Description	ShortDescription	A short description of the item
Type	PeripheralType	The type of the peripheral.
Show	ShowType	Display the type next to the symbol on diagrams. Initial value is off.
Hardware	Hardware	The hardware or computer that implements the peripheral. Links to: Computer, HardwareComponent.
IP Address	IPAddress	The IP address of the device if the address is fixed
Logical name/address	LogicalAddress	The logical name or address of the item.
Show	ShowNetworkName	Display the network name next to the symbol on diagrams. Initial value is off.
Vendor	Vendor	The vendor of the item. The vendor might for instance be an internal organisation unit or an external supplier. Links to: BusinessConnection, ExternalEntity, OrganizationUnit.
Support	Support	The support provider. Links to: BusinessConnection, Person, ExternalEntity, OrganizationUnit.

The Economy tab

Property	Metamodel name	Description
Date of purchase	DateOfPurchase	When the item was purchased
Warranty expires	WarrantyExpires	When the warranty of the item expires
Contracts	HasContract	All the different contracts connected to the item. Links to: Contract.

Plateau : ArchiMate

An important premise in the TOGAF framework is that the various architectures are described for different stages in time. In each of the Phases B, C, and D of the ADM, a Baseline Architecture and Target Architecture are created, describing the current situation and the desired future situation. In Phase E (Opportunities and Solutions), so-called Transition Architectures are defined, showing the enterprise at incremental states reflecting periods of transition between the Baseline and Target Architectures. Transition Architectures are used to allow for individual work packages and projects to be grouped into managed portfolios and programs, illustrating the business value at each stage.
In order to support this, the plateau element is defined.Plateau propertiesThe Plateau tab

Property	Metamodel name	Description
Short description	ShortDescription
Implements	Implements	Links to: All templates.
BreaksDownTo	BreaksDownTo	Links to: All templates.