Business Architecture
In the business sector, business architecture is a discipline that "represents holistic, multidimensional business views of: capabilities, end‐to‐end value delivery, information, and organizational structure; and the relationships among these business views and strategies, products, policies, initiatives, and stakeholders." In application, business architecture provides a bridge between an enterprise business model and enterprise strategy on one side, and the business functionality of the enterprise on the other side. It often enables the Strategy to Execution methodology. People who develop and maintain business architecture are known as business architects. Overview The term "business architecture" is often used to mean an architectural description of an enterprise or a business unit, an architectural model, or the profession itself. The Business Architecture Working Group of the Object Management Group (OMG) (2010) describes it as "a blueprint of the enterprise tha ... [...More Info...]       [...Related Items...]     OR:     [Wikipedia]   [Google]   [Baidu]   |
|
OMG Business Architecture Working Group
The Business Architecture Special Interest Group (BASIG) is a working group on business architecture of the Object Management Group (OMG), known for their contribution to the history of business architecture. This working group was founded in 2007 as the Business Architecture Working Group (BAWG). History Foundation The 2007 announcement for the OMG Technical Meeting on Dec. 12, 2007 in Burlingame, California gave the following rationale for the foundation of a specialized working group on business architecture: In looking at the link between IT and the business, it has become apparent that there needs to be more formally defined sets of relationships between IT architecture and business architecture. In addition, the concept of business architecture is probably 10-15 years behind the maturity of the IT architecture world. For example, the relationship between business rules and processes is not apparent and the role of organizational governance is similarly disconnected. Th ... [...More Info...]       [...Related Items...]     OR:     [Wikipedia]   [Google]   [Baidu]   |
|
OMG Business Architecture Special Interest Group
The Business Architecture Special Interest Group (BASIG) is a working group on business architecture of the Object Management Group (OMG), known for their contribution to the history of business architecture. This working group was founded in 2007 as the Business Architecture Working Group (BAWG). History Foundation The 2007 announcement for the OMG Technical Meeting on Dec. 12, 2007 in Burlingame, California gave the following rationale for the foundation of a specialized working group on business architecture: In looking at the link between IT and the business, it has become apparent that there needs to be more formally defined sets of relationships between IT architecture and business architecture. In addition, the concept of business architecture is probably 10-15 years behind the maturity of the IT architecture world. For example, the relationship between business rules and processes is not apparent and the role of organizational governance is similarly disconnected. T ... [...More Info...]       [...Related Items...]     OR:     [Wikipedia]   [Google]   [Baidu]   |
|
Value Stream
A value stream is the set of actions that take place to add value to a customer from the initial request through realization of value by the customer. The value stream begins with the initial concept, moves through various stages of development and on through delivery and support. A value stream always begins and ends with a customer. Value streams are artifacts within business architecture that allow a business to specify the value proposition derived by an external (e.g., customer) or internal stakeholder from an organization. A value stream depicts the stakeholders initiating and involved in the value stream, the stages that create specific value items, and the value proposition derived from the value stream. The value stream is depicted as an end-to-end collection of value-adding activities that create an overall result for a customer, stakeholder, or end-user. In modeling terms, those value-adding activities are represented by value stream stages, each of which creates and ad ... [...More Info...]       [...Related Items...]     OR:     [Wikipedia]   [Google]   [Baidu]   |
|
Architectural Domain
An architecture domain in enterprise architecture is a broad view of an enterprise or system. It is a partial representation of a whole system that addresses several concerns of several stakeholders. It is a description that hides other views or facets of the system described. Business, data, application and technology architectures are recognized as the core domains in the most of proposed concepts concerned with the definition of enterprise architecture. Overview Since Stephen Spewak's book called enterprise architecture planning (EAP) in 1993, and perhaps before then, it has been normal to recognise four types of architecture domain. The British Computer Society's "Reference Model for Enterprise and Solution Architecture" also follows this subdivision but additionally mentions the (single) application architecture level just below the application''s'' architecture as well as the domains of information architecture, information systems architecture, or security architectur ... [...More Info...]       [...Related Items...]     OR:     [Wikipedia]   [Google]   [Baidu]   |
|
Business Process Modeling Notation
Business Process Model and Notation (BPMN) is a graphical representation for specifying business processes in a business process model. Originally developed by the Business Process Management Initiative (BPMI), BPMN has been maintained by the Object Management Group (OMG) since the two organizations merged in 2005. Version 2.0 of BPMN was released in January 2011, at which point the name was amended to Business Process Model ''and'' Notation to reflect the introduction of execution semantics, which were introduced alongside the existing notational and diagramming elements. Though it is an OMG specification, BPMN is also ratified as ISO 19510. The latest version is BPMN 2.0.2, published in January 2014. Overview Business Process Model and Notation (BPMN) is a standard for business process modeling that provides a graphical notation for specifying business processes in a ''Business Process Diagram'' (BPD), based on a flowcharting technique very similar to activity diagrams from ... [...More Info...]       [...Related Items...]     OR:     [Wikipedia]   [Google]   [Baidu]   |
|
Semantics Of Business Vocabulary And Rules
The Semantics of Business Vocabulary and Business Rules (SBVR) is an adopted standard of the Object Management Group (OMG) intended to be the basis for formal and detailed natural language declarative description of a complex entity, such as a business. SBVR is intended to formalize complex compliance rules, such as operational rules for an enterprise, security policy, standard compliance, or regulatory compliance rules. Such formal vocabularies and rules can be interpreted and used by computer systems. SBVR is an integral part of the OMG's model-driven architecture (MDA). Overview The SBVR standard defines the vocabulary and rules for documenting the semantics of business vocabularies, business facts, and business rules; as well as an XMI schema for the interchange of business vocabularies and business rules among organizations and between software tools. SBVR allows the production of business vocabularies and rules; vocabulary plus rules constitute a shared domain model w ... [...More Info...]       [...Related Items...]     OR:     [Wikipedia]   [Google]   [Baidu]   |
|
Business Motivation Model
The Business Motivation Model (BMM) in enterprise architecture provides a scheme and structure for developing, communicating, and managing business plans in an organized manner. Specifically, the Business Motivation Model does all of the following: * identifies factors that motivate the establishing of business plans; * identifies and defines the elements of business plans; and * indicates how all these factors and elements inter-relate. History Initially developed by the Business Rules Group (BRG), in September 2005, the Object Management Group (OMG) voted to accept the Business Motivation Model as the subject of a Request for Comment (RFC). This meant that the OMG was willing to consider the Business Motivation Model as a specification to be adopted by the OMG, subject to comment from any interested parties. Adoption as an OMG specification carries the intention that the Business Motivation Model would, in time, be submitted to the International Organization for Standard ... [...More Info...]       [...Related Items...]     OR:     [Wikipedia]   [Google]   [Baidu]   |
|
Model Driven Architecture
Model Driven Architecture (MDA) is a software design approach for the development of software systems. It provides a set of guidelines for the structuring of specifications, which are expressed as models. Model Driven Architecture is a kind of domain engineering, and supports model-driven engineering of software systems. It was launched by the Object Management Group (OMG) in 2001."OMG pursues new strategic direction to build on success of past efforts" Overview Model Driven Architecture® (MDA®) "provides an approach for deriving value from models and architecture in support of the full life cycle of physical, organizational and I.T. systems". A model is a (representation of) an abstraction of a system. MDA® provides value by producing models ...[...More Info...]       [...Related Items...]     OR:     [Wikipedia]   [Google]   [Baidu]   |
|
Unified Modeling Language
The Unified Modeling Language (UML) is a general-purpose, developmental modeling language in the field of software engineering that is intended to provide a standard way to visualize the design of a system. The creation of UML was originally motivated by the desire to standardize the disparate notational systems and approaches to software design. It was developed at Rational Software in 1994–1995, with further development led by them through 1996. In 1997, UML was adopted as a standard by the Object Management Group (OMG), and has been managed by this organization ever since. In 2005, UML was also published by the International Organization for Standardization (ISO) as an approved ISO standard. Since then the standard has been periodically revised to cover the latest revision of UML. In software engineering, most practitioners do not use UML, but instead produce informal hand drawn diagrams; these diagrams, however, often include elements from UML. History Before UM ... [...More Info...]       [...Related Items...]     OR:     [Wikipedia]   [Google]   [Baidu]   |
|
Object Management Group
The Object Management Group (OMG) is a computer industry standards consortium. OMG Task Forces develop enterprise integration standards for a range of technologies. Business activities The goal of the OMG was a common portable and interoperable object model with methods and data that work using all types of development environments on all types of platforms. The group provides only specifications, not implementations. But before a specification can be accepted as a standard by the group, the members of the submitter team must guarantee that they will bring a conforming product to market within a year. This is an attempt to prevent unimplemented (and unimplementable) standards. Other private companies or open source groups are encouraged to produce conforming products and OMG is attempting to develop mechanisms to enforce true interoperability. OMG hosts four technical meetings per year for its members and interested nonmembers. The Technical Meetings provide a neutral forum t ... [...More Info...]       [...Related Items...]     OR:     [Wikipedia]   [Google]   [Baidu]   |
|
Enterprise Architecture Framework
An enterprise architecture framework (EA framework) defines how to create and use an enterprise architecture. An architecture framework provides principles and practices for creating and using the architecture description of a system. It structures architects' thinking by dividing the architecture description into domains, layers, or views, and offers models - typically matrices and diagrams - for documenting each view. This allows for making systemic design decisions on all the components of the system and making long-term decisions around new design requirements, sustainability, and support. Overview Enterprise architecture regards the enterprise as a large and complex system or system of systems. To manage the scale and complexity of this system, an architectural framework provides tools and approaches that help architects abstract from the level of detail at which builders work, to bring enterprise design tasks into focus and produce valuable architecture description doc ... [...More Info...]       [...Related Items...]     OR:     [Wikipedia]   [Google]   [Baidu]   |
|
Zachman Framework
The Zachman Framework is an enterprise ontology and is a fundamental structure for enterprise architecture which provides a formal and structured way of viewing and defining an enterprise. The ontology is a two dimensional classification schema that reflects the intersection between two historical classifications. The first are primitive interrogatives: What, How, When, Who, Where, and Why. The second is derived from the philosophical concept of reification, the transformation of an abstract idea into an instantiation. The Zachman Framework reification transformations are: identification, definition, representation, specification, configuration and instantiation. The Zachman Framework is not a methodology in that it does not imply any specific method or process for collecting, managing, or using the information that it describes; rather, it is an ontology whereby a schema for organizing architectural artifacts (in other words, design documents, specifications, and models) is u ... [...More Info...]       [...Related Items...]     OR:     [Wikipedia]   [Google]   [Baidu]   |