BTABoK glossary is a table containing a set of definitions for terms which are commonly used in the BTABoK. The glossary contains terms which are defined by IASA and terms which IASA use but may be defined by other organisations or persons. The source column in the table identifies the organisation or person the definition originates from.
|Agility||The ability to adapt quickly to change, and thus take advantage of the opportunities that change brings.|
|Architecturally Significant Requirement|
|Architecture Pattern||A re-usable design often used in the context of a particular architecture style.|
|Architecture Review Board|
|Architecture Style||The fundamental principles for designing a particular architecture. For example, multi-layered, service-oriented, domain-driven.|
|ATAM||Architecture Trade-off Analysis Method|
|Balanced Scorecard (BSC)||A a strategic planning and management system. https://balancedscorecard.org/|
|Business Capability||A particular ability or capacity that a business may possess or exchange to achieve a specific purpose or outcome.
Ulrich Homann, “A Business-Oriented Foundation for Service Orientation”, Feb. 2006
|Business Requirement||A statement which describes what a business needs in order to succeed in a given business context.|
|CBAM||Cost Benefit Analysis Method|
|Component||A part of a system, or a larger component.|
|Continuous Deployment (CD)|
|Continuous Integration (CI)|
|Iron Triangle||A well-known project management concept which shows the relationship between cost, time and scope.|
|Minimum Viable Product (MVP)|
|Practice||A practice is a group of professionals, most of whom are reasonably junior, who grow through learning a particular set of skills and apply those skills to create something of value.|
|Project Management Office (PMO)|
|SAAM||Software Architecture Analysis Method|
|SEI||Software Engineering Institute at Carnegie Mellon University|
|SOA||Service Oriented Architecture|
|View||A representation of one or more aspects of an architecture that illustrates how the architecture addresses the concerns held by one or more of its stakeholders.|
|Viewpoint||A collection of patterns, templates, and conventions for constructing one type of view. It defines the stakeholders whose concerns are reflected in the viewpoint and the guidelines, principles, and template models for constructing its views.|
|Return of Investment (ROI)|
|Total Cost of Ownership (TCO)|
|Robot Process Automation (RPA)||A technique used to automate manual processes performed on a software user interface.|
|DevOps||A set of practices intended to reduce the time between committing a change to a system and the change being placed into normal production, while ensuring high quality.|
|Enterprise Resource Management (ERP)|
|Capital Expenditure (CAPEX)||Capital expenditures (CapEx) are funds used by a company to acquire, upgrade, and maintain physical assets such as property, plants, buildings, technology, or equipment.
|Operational Expenditure (OPEX)||Operating expenses are the costs that a company incurs for running its day-to-day operations. As such, they don’t apply to any costs related to the production of goods and services.
|Rapid Value Management||An iterative approach to continual value realization to ensure programs and projects are on-track to meet the objective they target.|
|Non-Governmental Organization (NGO)||A group that functions independently of any government. It is usually non-profit. NGOs, sometimes called civil society organizations, are established on community, national, and international levels to serve a social or political goal such as a humanitarian cause or the protection of the environment.
|Business As Usual (BAU)|
|Heat Map||A visual representation of data which uses colors to indicate different values.|
|CRUD||Short hand for Create, Read, Update and Delete. Often used in reference to data.|
|Unit of Competitive Advantage (UCA)|
|Unit Cost||A unit cost is a total expenditure incurred by a company to produce, store, and sell one unit of a particular product or service.
|Customer Segment||A categorization of customers into specific groups based on shared characteristics, behaviors, or preferences.|
|Organizational Network Analysis (ONA)||A structured way to visualize how communications, information, and decisions flow through an organization.
|Center of Excellence|
|European e-CF||An IT skills framework which lists architecture as a set of skills aligned with a plan, build, run, manage philosophy.|
|Innovation||The desire and understanding of trying new things with the shared understanding that many, if not most, will fail.|
|Motivation||How staff is rewarded, punished, and influenced. The primary driver for positive culture is that self-motivation of employees is respected and acted upon.|
|Risk-Tolerance||The level of risk that is acceptable in any aspect of work in the organization.|
|SATIR Change Model|
|Westrum Culture Diagnostic (WCD)||A tool used to understand culture from a information sharing, learning, responsibility, collaboration, failure and ideas perspective.|
|Culture Map||A tool to help understand the dynamics and implementation of culture.|
|Architecturally Significant Decision (ASD)|
|Module||A sub-component of a system.|
|Cognitive Bias||The ways in which human biases impact decisions.|
|Technical Product Owner|
|Business Case||Objectives, Investment Planning|
|Request for Information (RFI)||A formal process for gathering information from potential suppliers of a good or service.
|Request for Proposal (RFP)||A business document that announces a project, describes it, and solicits bids from qualified contractors to complete it.
|Request for Quote (RFQ)||A process in which a company solicits select suppliers and contractors to submit price quotes and bids for the chance to fulfill certain tasks or projects.
|Request for Tender (RFT)||An invitation to bid for a project. Tendering usually refers to the process whereby governments and financial institutions invite bids for large projects that must be submitted within a finite deadline.
|SAFe||Scaled Agile Framework.|
|YAGNI||Short for You Aren’t Going to Need It|
|SOLID||Design principles based on Single responsibility, Open/closed, Liskov substitution, Interface segregation and Dependency inversion|
BTABoK 3.0 by IASA is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License. Based on a work at https://btabok.iasaglobal.org/