Glossary of Terms and Acronyms

This page will contain all of my definitions of the terms and acronyms that are used in this blog.  You may disagree with some of many of them.  This seems to be a right for all in the various sub-disciplines of Systems Engineering.

I will be updating the page with all definitions of previous posts, as well as, those definition from posts, as they appear.  I will link the definitions to the posts from which they came.  More soon.

  • Assembly of Composite Applications
  • Choreography is a technique used to characterize and to compose service-oriented business collaborations based on ordered message exchanges between peer entities in order to achieve a common business goal(From OASIS Reference Architecture for Service Oriented Architecture Version 1.0 ,Public Review Draft 1, 23 April 2008, p. 71). \
  • A Composite Application is
  • Enterprise Architect the role of the enterprise architect is to support the organization’s investment process to ensure that the funded projects and programs optimize the systems and tooling for the organization to meet its mission using its strategies.  Additionally, the enterprise architect supports the Governance and Policy Management process to ensure that the policies and standards minimize the intra-/inter-organizational process friction.
  • Event Driven Architecture is
  • Event Rule is
  • IDEF0 Pattern is
  • An Issue is a problem.
  • Knowlege Management
  • Knowledge Rule is
  • Mission Alignment is the process of aligning the organization's enterprise architecture with the organization's mission to ensure the organization's investments in processes and infrastructure most optimally enable and support the organization's mission and vision.
  • Mission Execution
  • Mission Implementation
  • Model Driven Architecture
  • The OODA Loop was created by Col. John Boyd (ret.) to explain the process steps in acting on a stimulus.  OODA stands for (O)bserve, (O)rient, (D)ecide, and (A)ct.  While initially, Col. Boyd intended it for military use, "he wins who can think inside the other guy's OODA loop", the concept embodied in the OODA Loop are widely applicable.
  • Orchestration is A technique used to compose hierarchical and self-contained service-oriented business processes that are executed and coordinated by a single agent acting in a "conductor" role.  (From OASIS Reference Architecture for Service Oriented Architecture Version 1.0 ,Public Review Draft 1, 23 April 2008, p. 69). 
  • A Requirement is
  • A Risk is an unknown.  In mission implementation, a risk is always associated with the design, not the requirements.
  • Satisficing Behavior - "...a continuing interaction between analyzing what is achevable and what is desirable...[where the decision maker]...must constantly weigh...what he would like to get and what he thinks he might be able to get." (see the post for additional information).
  • Service Component
  • Service Oriented Architecture
  • System Architect The role of the Enterprise Architect is to decompose and derive the functions, to structure the functions, to allocate functions to components, to determine the acquisition method for components through tradeoff studies (make/buy/rent), and to validation that the product meets the customer's system requirements.
  • Systems Engineer The role of the systems engineer is to work with the customer to identify the customer’s “system” and “programmatic” requirements and to ensure that the customer’s system requirements are met (the system has been validated.)

  • BAMM is Business Activity Monitoring and Management
  • CEP is Complex Event Processing
  • IaaS is Infrastructure as a Service
  • KM is Knowledge Management
  • OODA is Observe, Orient, Decide, and Act
  • PaaS is Platform as a Service
  • RAD is Rapid Application Development
  • SaaS is Software as a Service
  • SOA is Service Oriented Architecture

No comments:

Post a Comment