Bearing in mind the above comments, it's important to remember that this isn't a list of words you should immediately stop using; simply be aware of who you're talking to, and be sure that if you do use any of these words they are necessary and appropriate in the context you use them. This list is by no means exhaustive; with over comments across our original article and three Facebook posts , we had to cap it somewhere! Included here are the words that were mentioned most often and which we had encountered ourselves.
So without further ado, and in no particular order, here is our readers' list of weird words that only architects use:. Main image via Shutterstock. You'll now receive updates based on what you follow! Personalize your stream and start following your favorite authors, offices and users.
Learn more about the story behind our new brand identity. Read more. About Contact Submit Advertise. The concept of a hybrid cloud is not new to the industry but the trend of fierce adoption of hybrid cloud is creating a buzz in the industry. The term implies that applications are live in public cloud as opposed to an on-premises datacenter. The pen-source refers to any program whose source code is made available for use or modification as users or other developers see fit.
Open-source software is usually developed as a public collaboration and made freely available. Omni-cloud refers to the cloud infrastructure composed of different services from different cloud providers. The term can be perceived as a successor of multi-cloud. Serverless is a cloud-computing execution model in which the cloud provider runs the server, and dynamically manages the allocation of machine resources.
A serverless application runs in stateless compute containers that are event-triggered and fully managed by the cloud providers. Quantum computing is the use of quantum-mechanical phenomena such as superposition and entanglement to perform computation. A data lake is a centralized repository that allows you to store all your structured and unstructured data at any scale. The relationship of a requirement to its proof of implementation. The trace bidirectionally connects the requirement to its test cases.
An advanced form of traceability in which the rationale or satisfaction argument for a set of links is captured, either as a single attribute of the linked requirement or as an additional layer of structured information between layers of requirements. Vertical Tracing. Connects project artifacts bidirectionally to their successors. For example, design to code. Business Case. Which features are to be included:.
Business Case Analysis. Business Case Analysis considers:. Business Types. Product Business Definition: Marketing of individual products, modules and components. No need for integrating services or customer specific adjustments. System Business Definition: Combination of different products. A certain degree of engineering effort for systems technology. Systems can be used generally; some customer-specific costs. Substantial customer specific engineering, project planning, assembly, and startup effort.
Extensive know-how is required in the technology of the industry. Solution Business Definition: Customer-specific, integrated solutions including services as consulting, design, engineering, systems integration, assembly, startup, finding an operator, etc. Product Development. One solution for all customers.
Solution Development. Individual solutions for each customer. Economies of Scale. The condition in which fewer inputs, such as effort and time, are needed to produce greater quantities of a single output.
Economies of Scope. The condition where fewer inputs such as effort and time are needed to produce a greater variety of outputs. Greater business value is achieved by jointly producing different outputs. Producing each output independently fails to leverage commonalities that affect costs.
Economies of scope occur when it is less costly to combine two or more products in one production system than to produce them separately. Motivation for product lines. Investment Analysis. A process of estimating the value of an investment proposal to an organization.
Investment analysis involves quantifying the costs and benefits of the investment, analyzing the uncertainties, and constructing a spending strategy. This analysis links the strategic and technical merits of an investment to its financial results. Instantiation Costs. Costs for the use of a core asset in a product during product development.
Mass Customization. The large-scale production of goods tailored to individual customers' needs. SMART targets. S: Specific. M: Measurable. R: Realistic.
T: Time-bounded. Product Line. A single product is called a "family member. Product Family. Software Platform. A platform is a core asset of a product family and incorporates those features that are common to all products. An area of process or knowledge driven by business requirements and characterized by a set of concepts and terminology understood by stakeholders in that area.
The problem domain and the solution domain are two kinds of domains. Problem Domain. The world of the customer with their view of a system, their requirements, use cases and scenarios. Solution Domain. The world of the software developer, with their artifacts, such as source code, tools, frameworks and domain-specific languages. Problem Domain-Solution Domain Mapping. In both domains we try to raise the level of abstraction, for example from individual operations to framework operations in the solution domain.
This makes the mapping of problem domain to solution domain easier to understand. The usage of self-explanatory identifiers in source code aligns both, but feature models and their mapping into the solution domain allow for easy and explicit reasoning about the dependencies.
The hard part — which will always require human reasoning — is the traversal "hop" from the problem domain to the solution domain.
A common way to traverse from problem to solution domain is to express responsibilities that are grouped and set in relation using CRC cards. This transformation step allows us to acquire an initial structure —the architecture — of the system.
Domain Model. The domain model of a product line defines the glossary, the entities, their relationships, and key use cases that show how the entities interact with each other. The domain model essentially captures the domain knowledge, which is often considered the core competence of companies or business units operating in a domain. Further, a domain model is the basis for a feature model of a domain.
Assets can be almost anything: for example documentation, process, tools, test plans, and components. Product Asset. An artifact that is part of a product in a product line - not only the deliverables, but every artifact used for producing the product.
Core Asset. Any reusable artifact used as the basis for the software product line. It is built to be used in the production of more than one product. A core asset may be architecture, a software component, a process model, a plan, a document, or any other useful artifact used in building a system. Core assets may be conditional assets, as only a subset of core assets will be implemented in a specific product.
Software Engineering. Software engineering is the application of a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software. Product Line Engineering. A paradigm for developing software applications using software platforms and mass customization. Domain Engineering.
The process of software product line engineering in which the commonality and the variability of the product line are defined and realized. Includes the collection of past experience in building products in a particular domain. Application Engineering. The process of producing concrete members of a product family using the reusable assets developed during domain engineering. This term subsumes components from different sources with different degrees of modification possibilities.
Sources may vary from in-house, through nuances of non-develop-mental, to commercial. Reference Architecture. A description of the architectural artifacts, mechanisms, and rules on how to derive concrete product architectures. The artifacts can be frameworks, components, or conceptual guidelines, such as patterns. The mechanisms describe how to integrate existing artifacts and create additional ones.
The rules describe the constraints and consistency checks to ensure that derived architectures follow the mindset of the reference architecture Kircher. Target Architecture. This is the architecture of the product built with the help of the reference architecture. Showing the context of the system context diagram. Scoping is the process of identifying and bounding the focus of development for reuse in product line development. Domain Scoping.
In domain engineering: finding commonalities and variabilities of the products in order to define the scope of the platform. Setting the boundaries of the domain you are addressing with your development. Application Scoping. In product engineering: finding the context and boundaries of the product that is member of the product line. Core Asset Scoping.
The process of identifying the various elements that should be made reusable, that is, the specific assets that should be part of the reuse infrastructure, as opposed to being developed specifically for the product.
In this domain engineering step the set of desired family members products is analyzed to identify features that are present in every family member, and features that are optional or have to be adapted for a specific member. The result of this analysis also shapes the solution domain. It determines the core assets and the necessary level of configuration of the variable assets.
The result of the commonality-variability analysis is most commonly documented using feature modeling. The "how" and "when" of binding the variabilities is crucial to the architecture.
Specific infrastructure such as containers or interceptors needs to be provisioned, especially for runtime binding. Features that are present in most members of a product line. Assets that are optional or that have to be adapted for a specific member of a product line. Variability appears in the problem domain and in the solution domain and there must be a mapping between both. Variation is the way in which variants can differ from each other Kircher. Variation is usually described in general terms, such as the capabilities or properties that the variants have.
It is not the mechanism used to implement the variation. Variation Point. A variation point is a location in the product line, where a customization for a specific product can occur Kircher. A variant is one value or instance for this customization Kircher. The realization of a variable part of a core asset achieved through exercising its variation mechanism. Variation Mechanism. Feature Analysis. Feature analysis is a domain analysis method based on identifying the prominent or distinctive features of a class of products.
Product and Feature Matrix. A matrix that shows the relation between features and products that need that feature. Used to decide which features will be part of a platform.
Typical columns titles might be "product1," "product2,"… "product n", "platform release 1. Feature Model. Feature modeling is a method with a notation to elicit and represent common and variable features of a product family. A feature model can in most cases only be created when the domain is understood well enough, for example when multiple similar products have been built in a domain.
Feature Graph. A feature graph is a graphical representation of a feature model showing relations between features. It may use relations of different types like "depends on" "mutually exclusive" "conflicting" and others. It provides relations among features and not relations of feature to product. The latter is provided by the product feature matrix. A domain analysis method based on identifying the prominent or distinctive features of a class of systems.
The FODA methodology was founded on two modeling concepts: abstraction and refinement. Abstraction is used to create domain products from the specific applications in the domain. These generic domain products abstract the functionality and designs of the applications in a domain. The generic nature of the domain products is created by abstracting away "factors" that make one application different than other related applications.
The FODA method advocates that applications in the domain should be abstracted to the level where no differences exist between the applications. Specific applications in the domain are developed as refinements of the domain products.
Abstract Class. A class that does not implement all the methods defined in its interface. An abstract class defines a common abstraction for its subclasses. Abstract Component. A component that specifies one or more interfaces for other components. Abstract components form the basis for exploiting polymorphism and implementing flexible systems.
This term is used in the same way as abstract class, to avoid restricting patterns to object-oriented languages. Active Connection Establishment. The connection role played by a peer application that initiates a connection to a remote peer. Compare with Passive Connection Establishment. Active Object. An object that executes its methods in a different thread than the clients that invoke its methods. Compare with passive object. Application programming interface.
The external interfaces of a reusable software platform , such as an operating system , that is used by systems or applications built on top of it. A program or collection of programs that fulfills a customer or user's requirements. Application Framework. An integrated set of components that collaborate to provide a reusable software architecture for a family of related applications.
In an object-oriented environment, an application framework consists of abstract and concrete classes , and inversion of control. Instantiation of such a framework consists of composing and sub classing from existing classes. Architectural Drift. Find out why and how to fully align your strategy and execution with this free white paper:. Buzzwords have their uses, but can also be an absolute pain. Which buzzwords do you love, hate or love to hate? Join the discussion on this LinkedIn post.
Ardoq is passionate about engaging and connecting stakeholders across the organization. We constantly do our best to minimize data duplication, limit access to data, and educate all employees on data protection and privacy. We use Ardoq, and are happy to share with you how. Related posts. Find out why and how to fully align your strategy and execution with this free white paper: Buzzwords have their uses, but can also be an absolute pain.
A monthly digest of the latest news, articles, and resources. We value your business and respect your privacy We constantly do our best to minimize data duplication, limit access to data, and educate all employees on data protection and privacy. All Rights Reserved.
0コメント