Sametinger, J.: Software Engineering with Reusable Components. Springer Verlag, 1997  Home/Search   Document Not in Database   Summary   Related Articles   Check

....[Arb96] Glue. Although we claimed that components must be designed to be composed, the simple fact is that we are often constrained to use (legacy) components that are not plug compatible with the components we want to work with. These situations are referred to as compositional mismatches [Sam97] and glue code overcomes these mismatches by adapting components to the new environment they are used in. Glue adapts not only interfaces, but may also adapt client server contracts or bridge platform dependencies. Glue code may be ad hoc, written to adapt a single component, or it may consist ....

Johannes Sametinger. Software Engineering with Reusable Components. Springer, 1997.

....analysis and analyzes the application domain. Sample applications for that domain are investigated and their architecture is described. 2.1 Domain Analysis Domain Analysis is the process of extracting common parts of applications in a domain to provide a foundation for reuse. According to [Sam97], Ara94a] and others Domain Analysis involves the following activities: Domain definition and preparation . Data collection . Data analysis and classification . Evaluation Before a domain can be analyzed it has to be clearly defined. This is done by specifying its width (where the ....

....building blocks that implement larger functional parts which can be reused in an application, such as forms, frames or design patterns. 4.2 Application development When creating software there are several steps involved. While there are many different process models for that (refer to [Sam97] for an overview and [Oes98] for a businessoriented example) they include (of course simplified) the following steps: Analysis . Design . Implementation . Test 25 . Maintenance The first step when creating an application is to analyze the requirements. Based on the requirements a ....

[Article contains additional citation context not shown here]

Johannes Sametinger, Software Engineering With Reusable Components, Springer, 1997

....than building them from scratch. The goal is the use of reusable components as building blocks in new systems with modifications occurring in a controlled way. Reuse benefits have been reported from industry as improvements in quality, productivity, performance, reliability and interoperability [1][3]. However, difficulties involved in teaching software reuse in a software engineering course include: lack of tool support, inadequate component behavior models, language selection issues, platform selection issues, difficulty of finding reusable software, and difficulty of developing course ....

Sametinger, J, "Software Engineering with Reusable Components", Springer, 1997.

....of dynamic, heterogeneous environments. 2. SOFTWARE COMPONENTS The range of component based software engineering practice can be constrained by the definition of a software component. The definition of a software component is hotly debated; a sampling of common definitions can be found in [21, 22, 34, 38]. For the purposes of this paper, the definition presented in [21] will be used. This definition was selected for several reasons: it has undergone extensive review and revision; the definition is architecturally neutral in that it does not favor any specific implementation language or component ....

Sametinger, J. Software Engineering with Reusable Components. Springer-Verlag, New York, 1997.

....days of structured programming, the recurrent theme in software engineering has concerned the appropriate abstraction and encapsulation of procedures and data. To that end, developers now turn to the use and reuse of software components as a potential way out of our perpetual software crisis [7]. The belief is that libraries of software components can offer modular and composable building blocks for use within large application programs. These building blocks can allow developers to view their software more abstractly. These building blocks ostensibly are already tested and debugged. The ....

J. Sametinger, Software Engineering with Reusable Components. Springer-Verlag, Berlin, 1997.

....prescribed by the generalized specification. Documenting. The user oriented questions in the interface and comments in the specification body allow expressing the explanations in the natural language. 5. Case study: VHDL code modification via widening, narrowing isolation Sametinger [11] has described four general methods for generalizing components. We have adopted some of them for the modification of VHDL code with Open PROMOL. The first example (Fig. 2, a) implements modifications by narrowing functionality with respect to the second example (Fig. 2, b) The latter one ....

J. Sametinger, Software Engineering with Reusable Components, Springer, 1997.

....(aka program specialization) is a process of simplifying a program (usually a function) with respect to partially known inputs, thus hoping to increase runtime performance of the program. The following definitions of the functionalityoriented transformations are given according to Sametinger [22]. Widening is extending of the requirements (functionality) of the component, so that a component is more likely to be reused in future applications. Narrowing is the limiting of the functionality of the component at the cost of larger number of components. Isolating is the separating of ....

J. Sametinger. Software Engineering with Reusable Components. Springer , 1997.

....(aka program specialization) is a process of simplifying a program (usually a function) with respect to partially known inputs, thus hoping to increase runtime performance of the program. The following definitions of the functionalityoriented transformations are given according to Sametinger [22]. Widening is extending of the requirements (functionality) of the component, so that a component is more likely to be reused in future applications. Narrowing is the limiting of the functionality of the component at the cost of larger number of components. Isolating is the separating of ....

J. Sametinger. Software Engineering with Reusable Components. Springer, 1997.

....component model. The following paragraphs give an overview of possible choices. Components are self contained, clearly identifiable artifacts that describe and or perform specific functions. The component is a black box, where all interactions occur through the published interface (see also [21]) They can be deployed independently of each other and are subject to composition by third parties. Popular component models like JavaBeans or ActiveX have a historical origin in the assembly of user interfaces, where they are used to route user interface events such as mouse clicks and keyboard ....

Sametinger, J.: Software Engineering with Reusable Components, Springer , New York 1997.

....for defining components because components are intended to be used wider than software developed for a specific purpose. Software documentation is classified into parts according to a purpose: user documentation, system documentation, process documentation, and reuse documentation [11]. The reuse documentation includes a coarse grained functional specification and information that guides reuse, management, and assessment of a component. In a genre system [5] a reusable software component has two parts: the reusable part and a part that supports reuse. The reusable part ....

Sametinger, J. 1997. Software engineering with reusable components. New York: Springer Verlag. 272 p.

....1998 [15] The component concept is fundamental in both the compositional and generative reuse. In general, it is not an easy task to define precisely what a component is, because definitions vary in a wide range: from those giving a very broad understanding to the narrow ones (Sametinger, 1997 [25]; Jacobson, 1997 [18] Broy et al. 1998 [9] However, in any case the characteristics of a component are its interface and functionality. Other features are important, too: a component, e.g. can be composed from other components. In this paper we assume the following definition of the ....

....i.e. approach that uses a TL only for developing GCs, is attractive for black box reuse only, because it can lead to the so called overgeneralization problem. Excessive generality leads to complex components and unnecessary overhead in both execution time and resource consumption (Sametinger, 1997 [25]) The parameterization capabilities of the approach for composing a system are not enough, especially in the case of automatic composition. The reasons why we need to use the twolanguage approach for developing GCs are as follows. First, we can either avoid or reduce the affect of the ....

J. Sametinger. Software Engineering with Reusable Components. Springer, 1997.

.... A formalism or abstraction used to represent the invariant part varies in a wide range: from the simplest templates, such as language structures with holes , i.e. omitted non terminals (Teitelbaum et al. 1981) to more sophisticated templates, such as used in skeleton or kitchen sink approaches (Sametinger, 1997); from the generics and packages in domainspecific languages, such as VHDL (Ashenden, 1996; VHDL Tutorial, 1996) to domainspecific language itself; from the language patterns, such as assembly language to objectoriented abstraction in such language as C (Sametinger, 1997) from the programming ....

.... kitchen sink approaches (Sametinger, 1997) from the generics and packages in domainspecific languages, such as VHDL (Ashenden, 1996; VHDL Tutorial, 1996) to domainspecific language itself; from the language patterns, such as assembly language to objectoriented abstraction in such language as C (Sametinger, 1997); from the programming language extensions (e.g. P is the C extension in GenVoca model (Batory et al. 1995) to scripting languages, such as TCL (Ousterhout, 1993) Perhaps, there is no universal abstraction that suits best for most practical purposes, i.e. for building reusable components ....

[Article contains additional citation context not shown here]

Sametinger, J. (1997). Software Engineering with Reusable Components. Springer.

....design is required. The apparent lack of design information in today s components is considered to be one of the most significant problems of software development based on components [8] In addi tion, reuse of architectural design issues has not been an option on a compositional basis so far [23]. We consider compositional design reuse as a major step in overcoming at least some of the shortcomings mentioned above. We state that design expertise in composable form with explicit design constraints and documentation leads to an increase in systematic design reuse, a decrease of ....

Johannes Sametinger. Software Engineering with Reusable Components. Springer-Verlag. 1997.

No context found.

Sametinger, J.: Software Engineering with Reusable Components. Springer Verlag, 1997

No context found.

Sametinger J. Software engineering with reusable components. Berlin: Springer, 1997.

No context found.

J. Sametinger. Software Engineering with Reusable Components. Springer-Verlag, 1997.

No context found.

Sametinger, J.: Software Engineering with Reusable Components. Springer, Berlin (1997)

No context found.

Johannes Sametinger. Software Engineering with Reusable Components. Springer-Verlag, 1997.

No context found.

J. Sametinger. Software Engineering with Reusable Components. Springer, 1997.

No context found.

Sametinger, J.: Software Engineering with Reusable Components. SpringerVerlag, 1997.

No context found.

Sametinger, J. Software Engineering with Reusable Components. SpringerVerlag, New York, 1997.

No context found.

Sametinger, Johannes. Software Engineering with Reusable Components . New York: Springer, 1997.

No context found.

Sametinger, J.: Software Engineering with Reusable Components. Berlin et al. 1997.

No context found.

J. Sametinger. Software Engineering with Reusable Components. Springer, 1997.

No context found.

Sametinger, J. (1997). Software Engineering with Reusable Components. Springer-Verlag, Berlin/Heidelberg/New York. ISBN 3-540-62695

First 50 documents

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