R. van Ommering, F. van der Linden, J. Kramer, and J. Magee. The koala component model for consumer electronics software. IEEE Computer, 33(3):78--85, march 2000.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....in the makefile. Another drawback is that hardcoding preferences among alternative solutions is not always easy in tools like make. Our work is obviously related to Architecture Description Languages as well as to Software Architectures (e.g. see [15] and other component models (e.g. see [18]) Our approach is independent of methodological and language specific aspects. We have focused in defining a basic formal problem (with obvious practical applications) and obtaining fundamental complexity results. We have also been interested in a lightweight approach. Our framework is ....

R. van Ommering, F. van der Linden, J. Kramer, and J. Magee. The Koala component model for consumer electronics software. IEEE Computer, March 2000. 12

....the product line. The issues involved in creating a development process and business environment tailored to the use of a product line architecture are relatively well understood [4] Additionally, representations for specifying and storing product line architectures have already been developed [3,10,14,34]. Effective use of a particular product line architecture, however, also requires a support environment to manage its evolving structure an area of research that has largely been ignored to date. This paper introduces Mnage, an environment that is specifically designed to fill this void. Mnage ....

....instantiating and implementing individual product architectures. While it is technically possible to reuse architectural styles for this purpose [28] experience with product line architectures has shown a need for higher level support in terms of explicit facilities for modeling variation points [10,34]. Figure 1. Example Product Line Architecture. Architecture description languages support architecture based development [21] by providing formal notations to describe the architecture of a software system. An architecture description language is usually accompanied by various tools for ....

[Article contains additional citation context not shown here]

R. van Ommering, et al., The Koala Component Model for Consumer Electronics Software. Computer, 2000. 33(3): p. 78-85.

.... defines the structure of a single product, a product line architecture (PLA) defines the common architecture for a set of related products [5] A PLA explicitly specifies: 1) elements that are present in all products, 2) elements that are optional, and (3) variation points among products [31, 32, 33]. Particular product instances are selected by choosing the desired optional components and selecting one element per variation point. Perry [27] outlined the space of possibilities for modeling PLAs and observed that a PLA modeling technique must be both generic enough to encompass all members of ....

....to provide developers with adequate support for instantiating and implementing individual products. While it is technically possible to reuse styles for this purpose [29] experience has shown a need for higher level support in terms of explicit facilities for modeling optionality and variability [33]. To date, many architecture description languages (ADLs) have been proposed to aid architecture based development [24] ADLs provide formal notations to describe software systems and are usually accompanied by various tools for parsing, analysis, simulation, and code generation of the modeled ....

[Article contains additional citation context not shown here]

van Ommering, R., et al., The Koala Component Model for Consumer Electronics Software. Computer, 2000. 33(3): p. 78-85.

....abstractions [92] because the abstraction specification of one layer forms the implementation of the next higher layer. A challenge is to make layered abstractions compositional such that new layers can easily be constructed [111] Although various approaches exist (e.g. GenVoca [11] Koala [112]) there is a need for more general, languageindependent solutions. Moreover, configuration validation, for instance by modeling configuration constraints, is needed to automatically detect and prevent invalid component configurations [51, 8, 9] Abstractions for component compositions can be ....

....out to be rather complicated. process be automated Different people and institutes use varying techniques and infrastructure for software development. Potential reusable software components are therefore often entangled in project or institute specific configuration management (CM) systems [40, 112], or depend on local software. Since standardization in CM systems is lacking [112, 151] and because build processes are often not portable [7] reuse of these components over project and institute boundaries is difficult [83] This hampers collaborative software development. be removed in ....

[Article contains additional citation context not shown here]

R. van Ommering, F. van der Linden, J. Kramer, and J. Magee. The Koala component model for consumer electronics software. IEEE Computer, 33(3):78--85, March 2000.

....be useful in regression testing to reduce the number of test cases that actually need to be considered. While the use and adoption of SAs in industry has been moderately successful, the true benefit of using SAs (i.e. reuse) comes when they are applied in the form of product line architectures [6,19,20]. Rather than specifying a single architecture for a single software system, a product line architecture precisely captures, in a single specification, the overall architecture of a suite of closely related products [6] The techniques for doing so are rooted in the disciplines of SA and ....

....support for instantiating and implementing specific product architectures. While it is technically possible to reuse architectural styles for this purpose [25] experience with PLAs has shown a need for higher level support in terms of explicit facilities for modeling optionality and variability [20]. To date, many architecture description languages (ADLs) have been developed to aid architecture based development [17] ADLs provide formal notations to describe software systems and are usually accompanied by various tools for parsing, analysis, simulation, and code generation of the modeled ....

[Article contains additional citation context not shown here]

van Ommering, R., van der Linden, F., Kramer, J., and J. Magee. The Koala Component Model for Consumer Electronics Software. Computer, 33(3) (2000), pp. 78-85.

....survey is given in [6] Architecture systems introduce the notion of components, ports, and connectors as first class representations. However, most of the approaches proposed in the literature do not take into account the specific properties of software systems for embedded devices. In [8] van Ommering et.al. introduce a component model that is used for embedded software in consumer electronic devices. Koala components may have several provides and requires interfaces. Each of this interfaces defines ports in the sense of methods. In order to generate efficient code from ....

Rob van Ommering, Frank van der Linden, Jeff Kramer, and Jeff Magee. The koala component model for consumer electronics software. IEEE Computer, 2000.

....characterizing architectures [29] These notations are typically supported by tools that facilitate understanding, visualizing, analyzing, instantiating, and simulating architecture descriptions. Representative ADLs include Darwin [26] Wright [1] Rapide [25] MetaH [6] C2SADEL [28] and Koala [32]. As Medvidovic and Taylor [29] point out, the minimum requirement for a language to be an ADL is the ability to represent components, connectors, architectural configurations, and interfaces. Each language listed here has this ability. Additionally, each language listed here contains ....

....are applied to the same base type. We minimized the effect of this in the xADL 2.0 schemas [12] We have also made the schemas modular and incremental at the level of individual constructs within the schemas. Where possible, we have made individual elements optional. For instance, some ADLs [26][32] do not use explicit connectors. While xADL 2.0 supports them, they are not required in a xADL 2.0 based architecture specification. The xADL 2.0 schemas do not constrain what kinds of elements may be connected, so links can connect components directly if needed. This finer grained modularity ....

[Article contains additional citation context not shown here]

R. van Ommering, F. van der Linden, J. Kramer, and J. Magee. The Koala Component Model for Consumer Electronics Software. IEEE Computer 33(3): 78-85 (2000).

....method. In Section 3, we introduce scenario based resource prediction. In Section 4 we show how to apply our method in practice. Section 5 addresses related work and draws some conclusions. 2. The Robocop component model The Robocop component model is a variant of the Koala component model [9]. A Robocop component is a set of models, each of which provides a particular type of information about the component. Models may be in humanreadable form (e.g. as documentation) or in binary form. One of the models is the executable model , which contains the executable component. Other ....

R. van Ommering, F. van der Linden, J. Kramer, and J. Magee. The Koala component model for consumer electronics software. IEEE Computer, 33(3):78--85, Mar. 2000.

....and independently release new versions of them as they make these improvements [11,20,34] Much research and development effort is currently being expended on creating technologies to support component based software development. Among them are component platforms (e.g. NET [26] EJB [22] Koala [43]) techniques for the predictable assem1 In this paper, we adopt the common view of a component as a relatively large grained, mostly selfcontained, and independently identified part of one or more software systems that is deployed as a single, coherent unit [34] 2 bly of components [11] and ....

R. van Ommering, et al., The Koala Component Model for Consumer Electronics Software. Computer, 2000. 33(3): p. 78-85.

....KPN as our model of computation. It has been reasoned in the literature that template based design is necessary for designing embedded systems to handle the complexity of applications [27] to achieve the required performance with ecient implementations [31, 5] to generate product families [43], to enable reuse [11, 8] and to reduce time to market [20, 38] A template provides a standard way of communication among the vast variety of computational elements (e.g. processors, DSPs, ASIPs, dedicated hardware) 45, 31, 5] A template with a method for connecting processing elements through ....

van Ommering, R., F. van der Linden, J. Kramer, and J. Magee: 2000, `The Koala Component Model for Consumer Electronics Software'. In: IEEE Computer, Vol. 33. pp. 78-85.

....the remaining problems. Furthermore, they introduce version problems when different versions of a component are used [23, 29] They also provide restricted control over a component s configuration. All these complicating factors hamper software reuse and negatively influence granularity of reuse [28]. We argue that source code components (as alternative to binary components) can improve software reuse in component based software development. Source code components are source files divided in directory structures. They form the implementation of subsystems. Source code component composition ....

....added [23] For example, it requires adaption of a top level Makefile to execute make recursively for the new component. Potentially reusable code does not come available for reuse outside the system because entangled build instructions and build configuration of components are not reusable [28]. For example, as a result of using autoconf, a component s configuration is contained in a top level configuration script and therefore not directly available for reuse. Direct references into source trees of components yield unnecessary file system dependencies between components in addition ....

[Article contains additional citation context not shown here]

R. van Ommering, F. van der Linden, J. Kramer, and J. Magee. The Koala component model for consumer electronics software. IEEE Computer, 33(3):78--85, March 2000.

....same product) and propagating these architectural changes to yet another, third (version of a) product. The first problem has already been addressed through the advent of architectural description languages that incorporate facilities for capturing different versions of a product line architecture [10,17]. The second problem, however, has not been addressed as of yet. Consider a situation in which a number of architects maintain a product line architecture. The product line architecture is defined as a set of core components and connectors that are shared among all of the products, and a set of ....

van Ommering, R., van der Linden, F., Kramer, J., and Magee, J. The Koala Component Model for Consumer Electronics Software. Computer. 33(3), p. 78-85, 2000.

....a single implementation or design, that when manufactured leads to a device or product. A design is therefore the blueprint for the tangible device. A product family contains designs that have common characteristics, and are perhaps derived from each other, through a re use strategy or otherwise [28]. In Section 2 we classify how speci c interaction languages provide services that t the intended application domain (e.g. multimedia as opposed to controldominated) If there is a good t we expect the cost of designing a system to go down, because an application can be described naturally ....

....for data storage and or communication. Tokens are gathered in collections such as channels or pools. Components and channels can be connected in a topology using ports, and tokens are associated to channels or perhaps more generally to token pools. Systems can be generically described in many ways [2, 26, 28, 3]; we do not intend to do so here. Con guration services enable the construction and modi cation of a con guration of the system. Entities must be created, destroyed, or modi ed (e.g. started, suspended, stopped, moved, ushed) and their interaction speci ed or modi ed (e.g. event triggers, ....

[Article contains additional citation context not shown here]

Rob van Ommering, Frank van der Linden, Je Kramer, and Je Magee. The Koala component model for consumer electronics software. In IEEE Computer, volume 33, pages 78-85, 2000.

....partial semantic equivalence over a namespace of predicates used to specify interfaces. Inscape relies on Habermann and Perry s concept of well formed compositions [8] They list several desirable properties of componentbased configurations, most of which are implicitly assured by WREN. Koala [23] is a component model for embedded software in consumer electronics. It uses an explicit, visual description of architectures based on the architecture description language Darwin [15] Like Darwin, it has provides and requires interfaces and treats interfaces as first class entities. While Darwin ....

van Ommering, R., van der Linden, F., Kramer, J., and Magee, J. The Koala Component Model for Consumer Electronics So ftware. Computer 33, 3 (2000), 33-85.

....still a subject of current research to determine whether this is possible on an Internet scale. However, integration of WREN with ArchStudio is planned. While tool integration in WREN is currently implemented on an ad hoc basis, the principled approach of ArchStudio is clearly preferable. Koala [24] is a component model for embedded software in consumer electronics. It uses an explicit, visual description of architectures based on the architecture description language Darwin [11] Like Darwin, it has provides and requires interfaces and treats interfaces as first class entities. While Darwin ....

van Ommering, R., van der Linden, F., Kramer, J., and Magee, J. The Koala Component Model for Consumer Electronics Software. Computer 33, 3 (2000), 33-85.

....to work together efficiently. We call this a lightweight architecture, but leave it to another paper to elaborate on how to create such an architecture. Szyperski [29] defines components as having explicit context dependencies only , and being subject to composition by third parties . In Koala [20], the former are called (explicit) requires interfaces, while the latter is called third party binding. Tony Williams recognized the same two elements in an early paper leading to OLE [33] though an interface is called a base class there, and the third party a creator . In the following ....

....instantiate and bind other components. Darwin has Be it without implementation inheritance, a mishap cured in .NET been applied to the control and monitoring of coal mining, and as Koala to control software for televisions (see below) C m s Fig. 10. The Koala component model Koala [20] is an industrial architectural description language with a resource friendly component model used for the creation of embedded control software for consumer products. Koala supports both composition and variation. Koala components can be instantiated and their (typed) interfaces can be bound by ....

Rob van Ommering, Frank van der Linden, Jeff Kramer, Jeff Magee, The Koala Component Model for Consumer Electronics Software, IEEE Computer, March 2000, p78-85.

No context found.

R. van Ommering, F. van der Linden, J. Kramer, and J. Magee. The koala component model for consumer electronics software. IEEE Computer, 33(3):78--85, march 2000.

No context found.

van Ommering, R., van der Linden, F., Kramer, J., Magee, J.: The Koala component model for consumer electronics software. IEEE Computer, Vol. 33, Nr. 3, March 2000, 78--85.

No context found.

Rob van Ommering, Frank van der Linden, Je# Kramer, and Je# Magee. The koala component model for consumer electronics software. IEEE Computer, 33(3), 2000.

No context found.

R. van Ommering, F. van der Linden, J. Kramer, and J. Magee, "The koala component model for consumer electronics software," Computer, vol. 33, no. 3, pp. 78-- 85, Mar. 2000.

No context found.

F. v. d. L. Rob van Ommering, J. Kramer, and J. Magee. The Koala Component Model for Consumer Electronics Software. IEEE Computer, 3(33):78--85, Mar. 2000.

No context found.

R. van Ommering et al., The Koala component model for consumer electronics software. IEEE Computer, 33 (3): 78-85, Mar. 2002.

No context found.

van Ommering, R., van der Linden, F., Kramer, J.: The koala component model for consumer electronics software. In: IEEE Computer, IEEE (2000) 78--85

No context found.

R. van Ommering et al. The Koala Component Model for Consumer Electronics Software. IEEE Computer, 33(3):78--85, March 2000.

No context found.

R. van Ommering et al. The Koala Component Model for Consumer Electronics Software. IEEE Computer, 33(3):78-- 85, March 2000.

No context found.

van Ommering, R., F. van der Linden, K. Kramer and J. Magee, The Koala component model for consumer electronics software, Computer 33 (2000), pp. 78-85.

No context found.

R. van Ommering, et al., The Koala Component Model for Consumer Electronics Software. Computer, 2000. 33(3): p. 78-85.

No context found.

R. van Ommering, F. van der Linden, and J. Kramer. The Koala component model for consumer electronics software. IEEE Computer, 33(3):78--85, March 2000.

No context found.

R. van Ommering, F. van der Linden, and J. Kramer. The Koala component model for consumer electronics software. IEEE Computer, 33(3):78--85, March 2000.

No context found.

R. van Ommering, F. van der Linden, and J. Kramer. The Koala component model for consumer electronics software. IEEE Computer, 33(3):78--85, March 2000.

No context found.

Rob van Ommering, Frank van der Linden, Jeff Kramer and Jeff Magee. The Koala Component Model for Consumer Electronics Software. Computer, 33 (3), 2000. 78-85.

No context found.

R. van Ommering, et al., The Koala Component Model for Consumer Electronics Software. Computer, 2000. 33(3): p. 78-85.

No context found.

R. van Ommering, et al., The Koala Component Model for Consumer Electronics Software. Computer, 2000. 33(3): p. 78-85.

No context found.

Rob van Ommering, Frank van der Linden, Je# Kramer, and Je# Magee. The Koala component model for consumer electronics software. In IEEE Computer, volume 33, pages 78--85, 2000.

No context found.

R. van Ommering, et al., The Koala Component Model for Consumer Electronics Software. Computer, 2000. 33(3): p. 78-85.

No context found.

van Ommering, R., van der Linden, F., Kramer, J. and Magee, J. The Koala Component Model for Consumer Electronics Software. Computer, 33 (3), 2000. 78-85.

No context found.

R. van Ommering, F. van der Linden, J. Kramer, and J. Magee. The Koala component model for consumer electronics software. IEEE Computer, 33(3):78--85, Mar. 2000.

No context found.

R. van Ommering, J. Kramer, J. Magee, "The Koala Component Model for Consumer Electronics Software", IEEE Computer, March 2000, Vol. 33, No. 3.

No context found.

van Ommering, R., van der Linden, F., Kramer, J.: The koala component model for con-sumer electronics software. In: IEEE Computer, IEEE (2000) 78--85

No context found.

R. van Ommering, F. van der Linden, and J. Kramer; The Koala component model for consumer electronics software. IEEE Computer, 33(3):78--85, March 2000.

No context found.

R. van Ommering, F. van der Linden, and J. Kramer. The Koala component model for consumer electronics software. IEEE Computer, 33(3):78--85, March 2000.

No context found.

R. van Ommering, F. van der Linden, J. Kramer, and J. Magee, "The Koala Component Model for Consumer Electronics Software," IEEE Computer, vol. 33, pp. 78-85, 2000.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC