SysFEAT - Test

CLASS OF INDIVIDUAL - Asset Portfolio

Description

Abstract Concept

An Asset Portfolio is a Management System aimed at developing and maintaining in operational conditions a set of Mezzo Resource Operating Assets, delivering Resource Capabilitys required by Business Operations.

The purpose of Asset Portfolios is efficiency: Managed Resource Assets must provide expected Resource Capabilitys in the best cost / performance ratio.

Categorical partition of Asset Portfolio: an Asset Portfolio is either a Hardware Portolio, an Application Portfolio or a Technology Portfolio

Functional Domain: Asset Portfolio Pattern

Super Types

Asset Management Initiative (from partition: Structural Partition of Asset Management Initiative)

Management System

Operational Transformation

Dictionary

Dictionary of SysFEAT concepts

Lexical Scope

Model Lexical Scope

Model 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
Portfolio Roadmap	[*..0]	Asset Portfolio Stage	Asset Portfolio	Abstract Relationship Set of all Asset Portfolio Stages of an Asset Portfolio that , in conjunction with coordinating initiative milestones, establishes the roadmap for the Business Operating Assets under its supervision.
Portfolio Functional Scope	[*..0]	Resource Capability Map	Asset Portfolio	Abstract Relationship
Managed Resource Asset	[*..0]	Mezzo Resource Operating Asset	Asset Portfolio	Abstract Relationship A Managed Resource Asset represents the status of a Business Operating Asset which creation, maintenance, evolutation and rating is under the control of an Asset Portfolio.
Concerned Organization	[1..1]	Organization	Management System
Dependent Portfolio	[*..0]	Management System	Management System
Sub-Management System	[*..0]	Management System	Management System
Packaged Property Block	[*..0]	Model Property Block	Model Container
Packaged Documentation	[*..0]	Documentation	Model Container
Packaged Tag	[*..0]	Tag	Model Container
Imported Model Container	[*..0]	Model Container	Model Container	Abstract Relationship The Imported Model Container relationship extends the Model Lexical Scope of a Model Container to Model Building Blocks of the imported Model Container.
Qualifying Property	[*..0]	Property	Bounded Individual	Abstract Relationship Qualifying Property is a specialization relationship between a Bounded Individual and its qualifying Property.
Temporal Sequencing	[*..0]	Temporal Bounding	Bounded Individual	Abstract Relationship
Nested Description Note	[*..0]	Description Note	Model Lexical Scope
Existential Dependency	[1..1]	Entity	Entity	Abstract Relationship An Existential Dependency relationship is a Relationship where the source Entitys existence depends on the existence of the target Entity.The cardinality of the set of targetted Entity is [1..1].
Meronymy (Part Of)	[*..0]	Particular Entity	Particular Entity	Abstract Relationship Meronymy (Part Of) is a directional part-to-whole Relationship between Particular Entitys, where the source Particular Entity (the part) is defined has being part of a larger whole Particular Entity.In accordance with principles of Compositionality, Meronymy (Part Of) is not simply the inverse of Holonymy. In some cases, the whole Particular Entity is not inherently defined by some its parts. Location (Located at) and period relationships are such Meronymy (Part Of).Example:- William Shakespeare is born in Stratford-upon-Avon, but the Stratford-upon-Avon geo-location is not inherently defined by William Shakespeare. It is defined by its geophysical containers: Continent-Europe, Landmass-Great Britain.- William Shakespeare is born in 1564, but the year 1564 is not inherently defined by the birth of William Shakespeare. It is defined by its position in the Gregorian calendar and contains countless other global events.
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.

SERIALIZATION FORMAT

TEXTUAL SYNTAX RDF

File: 26b8889c5eea8ab7.rdf

SEMANTIC TAXONOMY

Sub-Types Super-Types

SUB-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.

BORDERS

Name	Super type	Border Type
Coordination Milestone	Bounded Individual::Temporal Border	Initiative Milestone
end	Bounded Individual::End	Initiative Milestone
start	Bounded Individual::Start	Initiative Milestone