INDEX

B  C  D  E  G  H  I  M  O  R  S  T  U  W 

REFERENCE LIST

NameDescription
B
 Business Dictionary
C
 Christensen Institute
D
 DAU - Glossary The Glossary of Defense Acquisition Acronyms and Terms, contains most acronyms, abbreviations, and terms commonly used in the systems acquisition process within the Department of Defense (DoD) and defense industries. It focuses on terms with generic DoD application but also includes some service-unique terms. 
 DDD- Glossary A web of resources on Domain Driven Design.
E
 EIP Blog chronicles of Gregor Hohpe's journey with asynchronous and distributed system design over two decades, covering integration, messaging, and conversation patterns, and patterns.
G
 Gartner Glossary Glossary from Gartner.
 GRCschema.org GRCSchema.org is a collaborative community initiative dedicated to developing, maintaining, and promoting Common Data Format schemas within the Governance, Risk, and Compliance sectors.
H
 Hardward Business Review Harvard Business Publishing (HBP) was founded in 1994 as a not-for-profit, independent corporation that is an affiliate of Harvard Business School. Our mission is to improve the practice of management in a changing world. This mission influences how we approach what we do here and what we believe is important.
 Harward Business School Harvard Business School was founded in 1908 to educate general managers who would lead the types of large-scale organizations that emerged from the Industrial Revolution. More than a century later, Harvard Business School is a global community of learners that influences business and management practice worldwide, working to positively impact society—and make a difference in our world.
I
 Interaction-design.org Design School to Learn New Design Skills.
 ISO 1087 - Terminologie
 ISO 15926
The scope of ISO 15926 is "Integration of life-cycle data for process plants, including oil and gas production facilities".
Data integration means combining information derived from several independent sources into one coherent set of data that represents what is known. Because the independent sources often have overlapping scopes, combining their data requires the common things to be recognized, duplicate information to be removed, and new information represented. To succeed in the role of integration, the data model must have a context that can include all the possible data that might be wanted or required.
 ISO 42010 Software, systems and enterprise — Architecture description.
 ISO 9000 This International Standard provides the fundamental concepts, principles and vocabulary for quality management systems (QMS) and provides the foundation for other QMS standards. This International Standard is intended to help the user to understand the fundamental concepts, principles and vocabulary of quality management, in order to be able to effectively and efficiently implement a QMS and realize value from other QMS standards.
M
 Martin Fowler Software development is a young profession, and we are still learning the techniques and building the tools to do it effectively. I've been involved in this activity for over three decades and in the last two I've been writing on this website about patterns and practices that make it easier to build useful software. The site began as a place to put my own writing, but I also use it to publish articles by my colleagues.
 Method Resources Resources documentation provided along with the  SysFEAT framework.
 Microsoft - Architecture Design Best practices and patterns for building applications on Microsoft Azure:
O
 OMG - BACM
The Business Architecture Core Metamodel defines concepts suitable for modeling business concepts found to be useful in business direction and strategy and not found in business operating models. These concepts include value and its delivery to stakeholders of a business, capability, abstract org anization, process, product and strategy. The concepts are represented at a high level typical of executive management and staffs who are responsible for overall business management and direction.
Business architecture models derived from this metamodel are not intended to represent all aspects of a business; they are intended to be used in conjunction with other models, with the ensemble of models being a sufficient basis for strategic and business analysis and planning. While the business architecture models are high level, they must be grounded in the reality and details of the business. For this reason, an ability to align or link elements or groups of elements of a business architecture model with elements and groups of elements of other models or even portions of prose documents or business data is a strong requirement.
The OMG has produced or is working on specifications for other business models, but the business architect will need to include models not based on any OMG specification. This specification defines a general mechanism for linking a BACM-derived model to other models and
data sources. These mechanisms respond to the RFP request for a “touchpoint” mechanism.
 OMG - BPMN
The Object Management Group (OMG) has developed a standard Business Process Model and Notation (BPMN). The primary goal of BPMN is to provide a notation that is readily understandable by all business users, from the business
analysts that create the initial drafts of the processes, to the technical developers responsible for implementing the technology that will perform those processes, and finally, to the business people who will manage and monitor those processes. Thus, BPMN creates a standardized bridge for the gap between the business process design and process implementation.
 OMG - Kernel Modeling Language (KerML) The Kernel Modeling Language (KerML) is an application-independent modeling language with a well-grounded formal semantics for modeling existing or planned systems. The language includes general syntactic constructs for structuring models, such as relationships, annotations and namespaces; core semantic constructs that have semantics based on classification; and additional constructs for commonly needed modeling capabilities, such as associations and behaviors.
 OMG - SBVR
This specification defines the vocabulary and rules (see Clauses 7 through 21) for documenting the semantics of business vocabularies and business rules for the exchange of business vocabularies and business rules among rganizations and between software tools.
This specification is interpretable in predicate logic with a small extension using modal operators. It supports linguistic analysis of text for business vocabularies and business rules, with the linguistic analysis itself being outside the scope of this specification.
 OMG - SysML2
The Systems Modeling Language (SysML) is a general-purpose modeling language for modeling systems that is intended to facilitate a model-based systems engineering (MBSE) approach to engineer systems. This document
provides the standard specification for SysML Version 2 (SysML v2). SysML v2 is intended to enhance the precision, expressiveness, interoperability, and the consistency and integration of the language relative to SysML Versions 1.0 to 1.7 [SysML v1]
 OMG - UML
This specification defines the Unified Modeling Language (UML), revision 2. The objective of UML is to provide system architects, software engineers, and software developers with tools for analysis, design, and implementation of
software-based systems as well as for modeling business and similar processes.
 OpenGroup - OAA References to the OpenGroup Open Agile Architecture framework
 OpenGroup - TOGAF - Enterprise agility An Open Group TOGAF® Series Guide on Enterprise Agility.
 OpenGroup - TOGAF - Method
This standard contains two types of content designed to assist the Enterprise Architect:
. TOGAF Fundamental Content
. Extended Guidance
R
 Russell Ackoff - Choice & Communication This document is a reformatted version of the document published by Russell Ackoff in a report to the National Science Foundation under Grant GN-389, Management Science Center, University of Pennsylvania, Philadelphia, 1967. Russell Ackoff published a more recent version of this document with Fred E. Emery in 1972 under the title “On Purposeful Systems”. A new edition of this last book was reedited in 2017 by Routledge.
 Russell Ackoff - Towards a system of concepts This document is a reformatted version of the document published by Russell Ackoff in volume 17 of the magazine "Management Science", in July 1971.
 Russell Ackoff - Transformational leadership ADMINISTRATION, MANAGEMENT, AND LEADERSHIP:  These terms are often used interchangeably. What a waste! There are important differences they can be used to reveal. Therefore, I have defined them in a way that is directed at improving leadership and bringing about more significant organizational transformations.
S
 SEBoK The SEBoK provides a guide to the key knowledge sources and references of systems engineering organized and explained to assist a wide variety of individuals. It is a living product, accepting community input continuously, with regular refreshes and updates. The SEBoK is not a compendium but instead references existing literature.
 Semantic Studios Semantic Studios is led by Peter Morville, a well-known pioneer of the disciplines of information architecture and user experience.
 Stanford Encyclopedia of Philosophy The Stanford Encyclopedia of Philosophy (SEP), which as of Summer 2023, has nearly 1800 entries online. From its inception, the SEP was designed so that each entry is maintained and kept up-to-date by an expert or group of experts in the field. All entries and substantive updates are refereed by the members of a distinguished Editorial Board before they are made public.
 SysFEAT Framework
 System Thinking Alliance Systems Thinking Alliance is a global organization supporting practitioners and organizations who explore and apply systems thinking principles, practices and methods to make the world humane and sustainable sustainable.
T
 The Law Dictionary
U
 UCF Glossary Unified Compliance is the integration of processes and tools to aggregate and harmonize all compliance requirements applicable to an organization. Control mapping and harmonizing done for you.
W
 W3C - OWL The Web Ontology Language OWL is a semantic markup language for publishing and sharing ontologies on the World Wide Web. OWL is developed as a vocabulary extension of RDF (the Resource Description Framework) and is derived from the DAML+OIL Web Ontology Language. This document contains a structured informal description of the full set of OWL language constructs and is meant to serve as a reference for OWL users who want to construct OWL ontologies.