- All
- ISO 15704
- ISO 42010
- ISO 42020
conceiving, defining, expressing, documenting, communicating, certifying proper implementation of, maintaining and improving an architecture throughout the life cycle for an architecture entity
fundamental concepts or properties of an architecture entity in its environment embodied in its elements, relationships, and in the principles of its design and evolution
group of architectures held by an organization that is subject to governance and management by the organization as a whole
thing considered, described, discussed, studied, or otherwise addressed during the architecting effort
conventions, principles and practices for use by architecture-related activities that have been established within a specific domain of application or community of stakeholders
information item expressing the architecture from the perspective of specific concerns about the architecture entity
conventions for the construction, interpretation and use of architecture views to frame specific concerns about the architecture entity
partially ordered set of enterprise activities that can be executed to achieve some desired end-result in pursuit of a given objective of an enterprise or a part of an enterprise
discipline applied in carting out any efforts to establish, modify, or reorganize any enterprise
abstraction that represents entities within the enterprise, their relationships, composition and detailing, to the extent necessary for conveying enterprise intentions and operations
operational enterprise that functions as a system, which is realized through a life cycle with a life history
context that determines the setting and circumstances of technological, business, operational, organizational, political, regulatory, social, and other critical influences and constraints upon an enterprise that affect its development and behaviour but are not controllable by the enterprise itself
set of distinguishable phases or stages that an entity goes through from its conceptualization until it ceases to exist
actual sequence of phases and steps an entity has gone through during its lifetime
modelled using a formalism, which has a formal syntax and semantics, usually with a theoretical basis, and expressible in a symbolic language
(enterprise) conceptual collection of enterprise-entity aspects related by kind of architectural concern and exhibiting reasonably distinct focal coordinates along a continuum.
group of people and facilities with an arrangement of responsibilities, authorities and relationships
source of information comprising descriptions of generalized enterprise architecture concepts, requirements and recommendations
place where work products and the associated information items are or can be stored for preservation and retrieval
individual or organization having a right, share, claim, or interest in an architecture or in its possession of characteristics that meet their needs and expectations
Related Posts
API Architecture Metamodel
An Application Programming Interface (API) is a construct that enables communication between systems. Integration between systems in complex environments continues to be a business priority to support automation activities. An API can be purpose-built for a bespoke integration (typical of legacy systems), or alternatively a standard connector can be developed between industry standard systems such as ERP’s and Service Management platforms. Managing these integrations becomes a complex operational task as updates and new releases to the integrated systems (and enabling technologies), can lead to intensive release management and testing activities. Security is also of utmost concern when managing integrations as the API provides a potential entry-point from either system integration direction – the API has become a preferred target for malicious attacks on systems and networks.
Clustering
Clustering provides users with a new way of interacting with content in their repository. It provides an enhanced analysis capability directly from the 3D Visualizer by logically grouping objects based on their relationships, concepts, and definitions. Filters can be applied to the clusters through the table-based view using existing functionality to focus analysis efforts (for example only clustering objects that are related to a risk with a high impact). The number of clusters can also be defined by the user to provide a broader or more concise result.
Ontologies in QualiWare
This page is intended to help users model knowledge using the QualiWare GOWL implementation delivered in release 10.8 of QualiWare.