abstract component technology
a vocabulary and notation for specifying components, assemblies, and their runtime environments in a component-technology-independent way, and for specifying the constraints, imposed by reasoning frameworks, that must be satisfied for predictions to be valid
constraints imposed by one or more reasoning frameworks on an abstract component technology
a property P associated with a referent R, meaning that “R has property P,” denoted as R.P
a set of components and their enabled interactions
behavioral and topological rules of well-formedness imposed on components and assemblies by one or more (real) component technologies, and one or more reasoning frameworks
automated reasoning procedure
a decision procedure and interpretation, each susceptible to full automation. See also property theory
a linking mechanism embedded in components to enable their interaction with other components. See also pin.
an implementation in final form, modulo bound labels, that provides an interface for third-party composition and is a unit of independent deployment
a component technology imposes fabrication standards for assembling software from large-scale building blocks. A component technology consists of a component model and a runtime environment. The component model specifies fabrication standards governing such issues as a component's life cycle and allowable forms of interaction. A runtime environment is an execution environment that enforces aspects of the component model and provides standard interaction mechanisms and services.
to enable component interaction through connectors
a set of interactions among components enabled through connectors. See also assembly.
a mechanism provided by the runtime environment that enforces an interaction protocol, or discipline, on the components that are participants in an interaction
an abstract component technology, tools to enforce assembly constraints, and other tools used to automate the specification, development, and deployment of components and their assemblies
a language for specifying abstract component technologies (ACTs) and their well-formed components and assemblies
a counterexample is an execution trace that results in the violation of a behavioral assertion Counterexamples provide diagnostic feedback that help engineers understand and reproduce failures
to restrict the visibility of interactions on pins
a process for developing reasoning frameworks, and in particular, for finding an acceptable tradeoff among various qualities of a reasoning framework, such as generality, complexity, and stability
a function that evaluates claims made on assemblies, described in the property theory, to the values “true” or “false”
defines where (in which instance of a runtime environment, and, ultimately, on which physical computing device) component behavior is executed
evidence acquired through direct observation, preferably under controlled circumstances, with results reported in well-defined units of measure. Empirical evidence is therefore provisional, as any other observation might have been different. See also formal evidence.
a software specification that is ready for execution on a physical or virtual machine. See also component.
evidence acquired through mathematical proof. Formal evidence is therefore irrefutable, as all such proofs are tautological. See also empirical evidence.
a composition of two or more reactions, from distinct components, using a runtime-environment-provided connector
an n-tuple <name, value, ... >, where name and value refer to the name of some property and the value it takes, respectively. See also annotation.
a calculus and logic that provides an objective, rigorous, and verifiable or falsifiable basis for predicting the properties of assemblies
specification of the behavior of a unit of concurrency within a component (e.g., a thread) and the behavioral dependencies between sink pins and source pins of a component
environment that provides runtime services that may be used by components in an assembly, provides an implementation for one or more connectors, and enforces assembly constraints
a pin that accepts interactions with the environment of a component (i.e., from other components or the runtime environment). See also pin, source pin.
a pin that initiates interactions with the environment of a component (i.e., to other components or the runtime environment). See also pin, sink pin.
unit of independent deployment
a component is independently deployable if all its dependencies on external resources are clearly specified (e.g., as pins), and if it can be substituted for, or substituted by, some other component. See also deployment.
provides an objective basis for trusting the validity and soundness of a reasoning framework, and defines its required component properties with sufficient rigor to provide an objective basis for trust in assertions of component behavior