Markets for software applications have been established for some time. Conventionally, revenue collection is done at the time the component is distributed.
Revenue Collection is the mechanism by which payment for a component is made to reach the producing vendor, regardless of the context in which the component is actually used. Several distribution techniques are conventionally used throughout the industry: embedding (static linking), runtime linking, and runtime loading. The latter includes font collections, clip-art sheets, economic indicators, and so on.Ĭomponents, subassemblies, and applications go through an economic cycle which includes two mechanisms relevant to our discussion: the distribution mechanism and the revenue collection mechanism.ĭistribution is the mechanism by which a component is made available to another component or final consumer (end-user). The former includes such examples as operating system subsystems, runtime libraries, specialized classes, etc. We will use the term subassembly only if there is need to distinguish them from small-grain components.īoth program components and data components exist. In electronic hardware the analogous entities are electronic components (such as integrated circuits and passive components), boards (usually ready to be plugged into bus connectors), and systems (such as personal computers).įor simplicity, we will use the term component to mean both components and subassemblies. The basic distinction between components, subassemblies and applications is that of granularity. Successive composition finally yields what we all think of as applications - a conventional packaging of functionality. These are grouped in subassemblies, such as a library or a subsystem.
Software structure starts with small-grain components such as functions, classes, and data values. It is natural to think of software as being an assemblage of components. It also introduces several terms used throughout the paper.Ĭomponents, Subassemblies and Applications This section motivates the work on economic grounds. A few examples model concrete business needs, bridging the gap between technologically motivated mechanism and business motivated policies.
#Kala software code
Kala allows the licensing and/or metering of access to any software facilities, both data (passive resources) and executable code and associated services (active resources). Kala offers a suite of low-level primitives for constructing both simple and sophisticated licensing (pay-per-user) and metering (pay-per-use) models. This paper describes the licensing and metering capabilities of Kala, a persistent data server.
0 kommentar(er)
