SysFEAT - Systemic Framework for Enterprise Architecture & Transformation

CLASS OF CLASS OF INDIVIDUAL - Software System Environment Scenario

Description

Abstract Concept

A Software System Environment Scenario is a story involving the partners of a Business Software System (Partner System), interacting in order to produce Information Outcome Events in a specific Eco-System (Software System Environment).

This includes:

- A course of events represented by Object Flows depicting the story towards the delivery of expected Information Outcome Events.

- Interacting partners who participate to the story in the considered Eco-System.

Functional Domain: SOF - Business Software Operating Model

The SOF - Business Software Operating Model domain provides concepts and abstractions shared by all Business Software Systems.

External references

OpenGroup - ArchiMate - Application Interaction

Super Types

Business System Environment Sxcenario

Dictionary

Dictionary of SysFEAT concepts

Lexical Scope

Architecture Container

RELATIONSHIPS

Simple Graph Graph & Inheritance Table

Simple Graph

Composition: ➝ Classification: ➝ Specialization: ➝ Instance Of: --> Enumerated definition: ➝ Syntax: ➝

Graph & Hierarchy

Composition: ➝ Classification: ➝ Specialization: ➝ Instance Of: --> Enumerated definition: ➝ Syntax: ➝

Relationship Table

Relationship	Cardinality	Target Entity	Source Entity	Description
Scenarized Software System Environment	[1..1]	Software System Environment	Software System Environment Scenario
Application Flow	[1..1]	Information Outcome Event	Software System Environment Scenario
Participant Software	[*..0]	Business Software System	Software System Environment Scenario
Partner Software System	[*..0]	Business Software System	Software System Environment Scenario
Subject Software System	[1..1]	Business Software System	Software System Environment Scenario
Specialized Functional Asset	[*..0]	Functional Asset	Functional Asset
Realized Functional Asset	[*..0]	Functional Asset	Functional Asset	A kind of specialization between an implementing Functional Asset and its abstract Realized Functional Asset.Realization relationships are the foundation to establish the mapping between Functional Assets that belong to different Conceptualization Levels.
Policy Conformance	[*..0]	Policy	Functional Asset	A Policy Conformance is the conformity requirement that applies a Functional Asset.
Risk	[*..0]	Risk Type	Functional Asset	A Risk refers to the potential for loss resulting from inadequate structure or behavior of a Functional Asset.
Hierarchical Member	[*..0]	Building Block	Aggregate Block	A Hierarchical Member is an Aggregate Member that is also a Block Lexical Scope for the Building Block it aggregates: it relates its aggregated block by nesting (see Nesting Relationship).Hierarchical Members are used to build hierarchical structures of Building Blocks, in constrast to Block Members which are used to build network structures of Building Blocks.
Block Member	[*..0]	Building Block	Aggregate Block	A Block Member is an Aggregate Member that aggregates its releated Building Block by reference (see Referencing Relationship).Block Members are used to build network structures of Building Blocks while Hierarchical Members are used to build hierarchical structures of Building Blocks.
Start Type	[*..0]	Temporal Bounding Type	Class of Bounded Individual
End Type	[*..0]	Temporal Bounding Type	Class of Bounded Individual
Temporal Sequencing Type	[*..0]	Temporal Bounding Type	Class of Bounded Individual
Aggregate Composition Type	[*..0]	Class of Bounded Individual	Class of Bounded Individual	An Aggregate Composition Type is a reified flavor of Composition Type whereby the referenced Class of Individual is aggregated in its parent (whole) Class of Bounded Individual.Example:1) A Process Step is the reification of the composition of a child process in a parent process.2)
Dependency Relationship	[1..1]	Entity	Entity	A Dependency Relationship is a Relationship that specifies the existential dependency of the sourceRelationship on its target Relationship.The cardinality to the target Entity is [1..1].

SERIALIZATION FORMAT

TEXTUAL SYNTAX RDF

File: 25c0a10061e2fc12.rdf

SEMANTIC TAXONOMY

Sub-Types Super-Types

Click node rectangle to collapse/expand one level. Click triangle for full recursive collapse/expand. Double-click on a node to open its URL. Hover for description.

INTERNAL STRUCTURE

../images/25c0a10061e2fc12_25c0a2b161e2feac_i.png

CONNECTORS

Connector	Source	Target	Connector Type	Description
Application Flow	Participant Software	Participant Software	Information Outcome Event

CLASS OF CLASS OF INDIVIDUAL - Software System Environment Scenario

RELATIONSHIPS

Simple Graph

Graph & Hierarchy

Relationship Table

SERIALIZATION FORMAT

SEMANTIC TAXONOMY

INTERNAL STRUCTURE

CONNECTORS

CHARTER

Missing Content

Governance

Provide Feedback