Documentation: An Architecture State groups a set of related architectures in a particular context or configuration. Such contexts could be temporal, e.g. reflecting architectures that are valid today or in the future. Equally, this context could represent the set of architectures required to achieve a particular goal. Naming of Architecture States is important. Architecture States should be named for the configuration of architectures that they group. What does this state do for the organisation? Avoid names such as 'Current State' or 'Future State' as these Architecture States can be used in different contexts.

Superclasses

• Strategy_Management

Subclasses

• None

Types

• :STANDARD-CLASS

Template Slots
	Slot Name	Documentation	Type	Cardinality	Min/Max	Default	Template Value
	arch_state_application_conceptual	Slot to group the set of architectures from the Application Conceptual layer in an Architecture State	Application_Conceptual	0:*
	arch_state_application_logical	Slot to group the set of architectures from the Application Logical Layer in an Architecture State	Application_Logical, :Application_Relationship	0:*
	arch_state_application_physical	Slot to group the set of architectures from the Application Physical layer in an Architecture State	Application_Physical	0:*
	arch_state_application_relations	Slot to capture the Application Relationship instances (e.g. Application to Process relationships) that are in an Architecture State	Application_Relationship	0:*
	arch_state_business_conceptual	Slot to group the set of architectures from the Business Conceptual Layer in an Architecture State	Business_Conceptual	0:*
	arch_state_business_logical	Slot to group the set of architectures from the Business Logical Layer in an Architecture State	Business_Logical	0:*
	arch_state_business_physical	Slot to group the set of architectures from the Business Physical layer in an Architecture State	Business_Physical	0:*
	arch_state_business_relations	Slot to capture the Business Relationship instances (e.g. Actor to Role relationships) that are in an Architecture State	Business_Relationship	0:*
	arch_state_information_conceptual	Slot to group the set of architectures from the Information Conceptual layer in an Architecture State	Information_Conceptual	0:*
	arch_state_information_logical	Slot to group the set of architectures from the Information Logical layer in an Architecture State	Information_Logical	0:*
	arch_state_information_relations	Slot to capture the Information Relationship instances (e.g. Information used by Application relationships) that are in an Architecture State	Information_Relationship	0:*
	arch_state_physical_information	Slot to group the set of architectures from the Information Physical layer in an Architecture State	Information_Physical	0:*
	arch_state_security_management	Slot to capture the elements related to security management in an Architecture State. Choose a relevant concrete instance, e.g. Security Principle, Security Policy etc.	Security_Management	0:*
	arch_state_technology_conceptual	Slot to group the set of architectures from the Technology Conceptual layer in an Architecture State	Technology_Conceptual	0:*
	arch_state_technology_logical	Slot to group the set of architectures from the Technology Logical Layer in an Architecture State	Technology_Logical, :Technology_Relationship	0:*
	arch_state_technology_physical	Slot to group the set of architectures from the Technology Physical layer in an Architecture State	Technology_Physical	0:*
	description	A meaningful description of the element and its purpose in the model.	String	0:1
	element_classified_by	Slot to capture the classification(s) that apply to an element in the ontology. Add this slot to any class that is to be managed by a Taxonomy.	Taxonomy_Term	0:*
	end_date	The date until which this architecture is relevant to the enterprise	Time	0:1
	external_reference_links	Slot to manage the set of external reference links to an EA_Class instance. Normally, create a new instance.	External_Reference_Link	0:*
	external_repository_instance_reference	Holds a set of references to this instance that are used in external repositories	External_Instance_Reference	0:*
	name	A descriptive name of the element in the model. (NOTE: A unique, internal reference is managed separately by the system.)	String	1:1
	stakeholders	Define the stakeholders for the element. Specific stakeholders are defined in terms of an ACTOR_TO_ROLE_RELATION. Alternatively, the type of relevant stakeholders can be defined in terms of a Business_Role.	ACTOR_TO_ROLE_RELATION, Business_Role	0:*
	start_date	the date from which this architecture is relevant to the enterprise	Time	0:1
	supersedes_version	Slot to capture the instance of which this instance is a new version. i.e. Use this slot to define the instance that represents the previous version of the element being considered. Allowed classes must always be a single class of the same type as the domain. e.g. a Technology_Product can only supersede another Technology_Product.	Architecture_State	0:1
	synonyms	Alternative names by which this element is known	Synonym	0:*

Own Slots
	Slot Name	Value
	:DIRECT-INSTANCES	Default EA Architecture State
	:DIRECT-SUBCLASSES
	:DIRECT-SUPERCLASSES	Strategy_Management
	:DIRECT-TEMPLATE-SLOTS	arch_state_information_logical, arch_state_information_conceptual, arch_state_application_conceptual, arch_state_information_relations, arch_state_security_management, arch_state_business_logical, start_date, arch_state_application_logical, arch_state_technology_logical, arch_state_technology_conceptual, arch_state_application_relations, arch_state_application_physical, arch_state_business_conceptual, arch_state_physical_information, arch_state_technology_physical, arch_state_business_relations, arch_state_business_physical, end_date
	:DIRECT-TYPE	:STANDARD-CLASS
	:DOCUMENTATION	An Architecture State groups a set of related architectures in a particular context or configuration. Such contexts could be temporal, e.g. reflecting architectures that are valid today or in the future. Equally, this context could represent the set of architectures required to achieve a particular goal. Naming of Architecture States is important. Architecture States should be named for the configuration of architectures that they group. What does this state do for the organisation? Avoid names such as 'Current State' or 'Future State' as these Architecture States can be used in different contexts.
	:NAME	Architecture_State
	:ROLE	Concrete
	:SLOT-CONSTRAINTS

  ^ back to top