T. Biggerstaff and C. Richter, "Reusability framework, assessment, and directions.", in Frontier Series: Software reusability: Volume I - Concepts and Models, T.J. Biggerstaff and A.J. Perlis, Eds., chapter 1, pp. 1--17. ACM Press New York, 1989.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....e commerce projects. To make misuse case analysis more appealing to practitioners reuse may be essential as security requirements could then be specified more rapidly. As pointed out already in the 80 s, reuse of requirements could lead to significant savings in development time and cost [20]. Although requirements reuse has attracted some research attention since then, methods suggested from academia have failed to demonstrate practicality or scalability [21] perhaps with the exception of types of development particularly suited for reuse, such as product family development [22, ....

T. Biggerstaff and C. Richter, "Reusability Framework, Assessment and Directions," IEEE Software, vol. 4, pp. 41-49, 1987.

....importance to the efficient development of large software systems. Methods for software reuse promote a way of thinking about system design that merges top down decomposition and bottom up composition. Using these methods, software systems are built by composing prepackaged reusable components [1]. Of the various approaches to software reuse, object oriented programming (OOP) is perhaps the most promising, as it provides both mechanisms for organizing and decomposing systems into encapsulated components (i.e. objects and classes) and mechanisms for incrementally modifying and composing ....

T. Biggerstaff and C. Richter, "Reusability Framework, Assessments, and Directions", IEEE Software, March 1987.

....help to cut down the cost of developing software in many ways. The most significant way in which they do so is in providing the possibility of a large software base of well designed, pre packaged, reusable objects. For a survey on software reusability, see either [Biggersta# and Perliss 1984] or [Biggersta# and Richter 1987]. Object oriented languages not only adopt the old idea of reusable libraries of subroutines, but they extend the ways in which software can be made reusable by supporting mechanisms such as object instantiation, operator overloading (i.e. tailoring of object classes) run time binding (when ....

T.J. Biggersta# and C. Richter, "Reusability Framework, Assessment, and Directions", IEEE Software, vol. 4, no. 2, pp. 41-49, March 1987.

....as Smalltalk, have a class library built in making programmers use that class library when writing code. In order for a programmer to reuse a component from a class library, he she must first locate the reusable component, understand it, and finally modify incorporate it into his her work [5] [2]. Therefore, to make efficient use of that class library, components in the class library should be easy to find, understand, and modify. When the problem of locating reusable components is looked at more closely, some of the problems can be stated as follows: ffl size 1 1 1 The size of the ....

T. Biggerstaff and C. Richter: "Reusability Framework, Assessment, and Directions", in Software Reusability, Vol.1, -- Concepts and Models --, T. Biggerstaff and A. Perlis (eds), pp.1-17, ACM Press (1989).

....3) less interaction with human users, and 4) higher ratios of comments to lines of code. Such modules were 13 generally small; thus, did not compose a significant part of a typical software development effort. Selby s investigation introduces the granularity problem identified by Biggerstaff. [BIGG87] Smaller, simpler components tend to be reused more because the population is large and evaluation and adaptation are easy, though finding smaller components can be hard and the payoff is usually low. Larger components tend to be reused less often because the population is low and evaluation and ....

T. Biggerstaff and C. Richter, "Reusability Framework, Assessment, and Directions," IEEE Software, March 1987, pp. 41-49.

....to support the design, development, distribution, and maintenance of reusable Software ICs . LEDB85] By 1987, advocates such as Biggerstaff saw software reuse as a great promise unfulfilled. Biggerstaff s experience was that well under half of delivered systems could be composed of reused code. [BIGG87] Intermetrics, owners of a reusable software library, reported that 33 of delivered code consisted of reused Ada packages. BURT87] Prieto Diaz found that most reusable components were small in number of lines of code, were simple in structure, had excellent documentation, and were written in the ....

....can be adequately classified, the location and retrieval problem must be addressed. How can potentially appropriate reusable candidates be located and retrieved The search space could be immense. Some means of factoring out specificity is required, so that the search space can be narrowed. [BIGG87] If specificity is factored out, then a means of mapping between a specification and appropriate implementations is needed. BIGG87] Helping a 9 programmer retrieve a group of possible reuse candidates is achievable, but allowing a programmer to find the closest match against his stated ....

[Article contains additional citation context not shown here]

T. Biggerstaff and C. Richter, "Reusability Framework, Assessment, and Directions", IEEE Software, March 1987, pp. 41-49.

.... What classes should be incorporated into these libraries How should these libraries be organized What is a good size for a reusable class What methods and data should it contain For a more detailed explanation on why software reuse hasn t been incorporated into the software community, see [Bigg87, Free86, Meye87, Trac87, Trac88b]. Description of New Research This new research, headed by Mark Lattanzi, attempts to quantify some of the properties of reusable software in hopes that some of the reluctance to reuse software can be clarified and dispelled. Object oriented software (classes) is by nature reusable, but there ....

Biggerstaff, Ted and Charles Richter, "Reusability Framework, Assessment, and Directions," IEEE Software, March 1987.

....approach has been evaluated through a prototype implementation, which addresses the reuse of a general purpose Smalltalk repository. 1 Introduction Software reuse is considered as the best potential approach to bring about the gains of productivity and quality that the software industry needs [3]. However, there are several methodological and technical problems that hinder reuse [5] Object Oriented Programming has been proposed as the best hope for facing these problems and promoting widespread software reuse [19] However, the concepts that provide the great strengths of this paradigm ....

Biggerstaff, T. J. & Richter, C., 1987. "Reusability Framework, Assessment, and Directions". IEEE Software, vol. 4, 2.

....in a software development life cycle. Dart et al. classified software development environments into language based, structured based, toolkit based, and method based ones [23] Biggerstaff et al. categorized software development environments into generation based and component based ones [9]. Fuggetta defined five classes of CASE environments: toolkits, languages centered environments, integrated environments, fourth generation environments, and process centered environments [30] In this section I describe three types of visual software development environments: programming based, ....

....environments for existing languages are Interlisp for Lisp language [83] Cedar for Mesa Cedar [82] Smalltalk V for Smalltalk [36] and the Relational Environment for Ada [7] 2.5. 2 Generation Based Environments A generation based environment reuses patterns integrated into a generator program [9]. Reusable patterns may be code patterns or rule patterns used by transformation systems. An example of a generation based environment is the Draco system, which is an application generator and transformation based system [61] 2.5.3 Component Based Environments Component based environments ....

Ted Biggerstaff and Charles Richter. "Reusability Framework, Assessment and Directions". IEEE Software, pages 41--49, March 1987.

....the classes that implement a fault tolerant internet whiteboard (FTIW) The FTIW serves as a proof of concept for the Cortex framework. Experimental results and discussions are included in Section G. Section H concludes this chapter by summarizing it. B. Object Oriented Frameworks A framework[72] is a reusable design expressed as a set of abstract classes and the way their instances collaborate. By definition, a framework is an object oriented design. It doesn t have to be implemented in an object oriented language, though it usually is. It is the skeleton of an application that can be ....

T. J. Biggerstaff and C. Richter, "Reusability framework, assessment, and directions, " IEEE Software, vol. 4, pp. 41--49, March 1987.

....transferring an acquisition to a recipient, and an instantiation of this could be a library lending a book to a borrower. In the area of software engineering, in particular software reuse, domain abstractions have been utilized in several forms, e.g. clichs [Reubenstein91] reusable patterns [Biggerstaff87], generalised application frames [Constantopoulos92] and analysis patterns [Fowler97] We believe that an important class of domain abstractions is the one consisting of schemas for communicative structures, and that a language with deontic and illocutionary constructs is adequate for describing ....

T. Biggerstaff and C. Richter, "Reusability Framework, Assessment, and Directions", IEEE Software, March, 1987.

....transferring an acquisition to a recipient, and an instantiation of this could be a library lending a book to a borrower. In the area of software engineering, in particular software reuse, domain abstractions have been utilized in several forms, e.g. clichs [Reubenstein91] reusable patterns [Biggerstaff87], and generalised application frames [Constantopoulos92 ] We believe that an important class of domain abstractions is the one consisting of schemas for communicative structures, and that a language with deontic and illocutionary constructs is adequate for describing such domain abstractions. Our ....

T. Biggerstaff and C. Richter, "Reusability Framework, Assessment, and Directions", IEEE Software, March, 1987.

....factors may have been responsible for the failure of such a facility to emerge : no clearly defined standards exist for reusable components. no large repositories of reusable software and components, or tools to access and synthesize systems from them, exist. Biggerstaff and Richter [Biggerstaff87] also state that a critical mass of components is necessary before reuse really begins to pay off. They believe the absence of component repositories is one of the factors that has prevented technologists from spontaneously generating a successful reuse environment. This thesis specifically ....

....and return a value as a result. They are stand alone components, in the sense that they are not dependent upon their environment. Functional reuse is widely practiced in certain domains, especially in mathematics (the NAG library, described earlier, is a prime example) 24 However, it is argued [Biggerstaff87] that functional reuse can only be effectively applied to domains that exhibit several special features : narrowness the domain must be characterised by a small number of data types, to ease problems of description and retrieval. generally acknowledged terminology as in mathematics, the ....

[Article contains additional citation context not shown here]

Biggerstaff, T.J., Richter, C. "Reusability Framework, Assessment, and Directions", IEEE Software, pp.41-49 (March 1987).

....of events, such as statement, control, inc counter, dec counter, bubble sort, etc. An attempt is made to match the lowest level events to code statements. Then the low level events are combined to form high level events. The third approach, called the informal tokens approach [15] 16] 17][18][19] matches keywords taken from comments and identifiers to a knowledge base. Recognized low level concepts in the knowledge base are combined to form higher level concepts. Some of the knowledge based approaches use additional, structural information such as abstract syntax trees or call ....

....with loop analysis. Athough loops typically are one of the most difficult parts of a program to understand, loop analysis alone does not normally provide sufficient information upon which to base overall understanding of a program. 2.3.1.7. The DESIRE System Biggerstaff Biggerstaff [15] 16] 17][18][19] argues that a parsing oriented approach based on structural patterns of programming language features, which is the approach of all tools examined in this survey so far, is necessary but not sufficient for solving the general concept assignment problem. Parsing approaches return ....

[Article contains additional citation context not shown here]

Biggerstaff, T.J., and Richter, C., "Reusability Framework, Assessment, and Directions," IEEE Software, Vol. 4, No. 2, March, 1987, pp. 41-49.

....designers can effectively search the repository. At a minimum, components must be categorized before they are placed in the repository. This value added approach to building software repositories creates a barrier of real and intellectual capital investments that many organizations cannot overcome [Biggerstaff, Richter 1987]. Most development organizations are pressed to deliver specific products, and cannot afford the extra work required to generalize and categorize work products created in individual projects. Methods are needed that can provide adequate retrieval effectiveness with minimal indexing and structuring ....

....investigations of CodeFinder. 2. Supporting Software Reuse With Component Repositories There are two basic technologies that have been applied in software reuse methodologies: compositionbased reuse (AKA parts based or component based) and generative techniques (AKA language based reuse) [Biggerstaff, Richter 1987; Frakes, Pole 1994] In composition technologies, the components are self contained entities such as library routines, data structures, programs, objects, and the like. Re using these components is accomplished by developers finding, understanding, and adapting the components into a new ....

[Article contains additional citation context not shown here]

Biggerstaff, T. J., Richter, C. "Reusability Framework, Assessment, and Directions," IEEE Software, 4(2), pp. 41-49.

.... Design reuse is an area of current research in both CAE (computer aided engineering) environments (see work reported by Mostow [Mos85] Mostow and Barley [MB87] and Huhns and Acosta [HA88] and CASE (computer aided software engineering) environments (see discussions by Biggerstaff and Richter [BR86] and Prieto Diaz and Freeman [PF87] and collections of papers examining reuse in software engineering [IEEE88, IEEE87, IEEE84] In each, the reuse problem can be addressed by providing: 1. Techniques for capturing and representing information by which a design component should be classified for ....

Ted Biggerstaff, Charles Richter, "Reusability Framework, Assessment, and Directions", MCC (Non Proprietary) Technical Report No. STP-345-86, October 1986.

....transferring an acquisition to a recipient, and an instantiation of this could be a library lending a book to a borrower. In the area of software engineering, in particular software reuse, domain abstractions have been utilized in several projects, e.g. clich s [Reubenstein91] reusable patterns [Biggerstaff87] and generalized application frames [Constantopoulos92] The purpose of using domain abstractions in software reuse is to obtain a classification of frequently occurring structures, which facilitates the search for software components that may be reused. Domain abstractions can take many ....

T. Biggerstaff and C. Richter, "Reusability Framework, Assessment, and Directions", IEEE Software, March, 1987.

....and evaluated, and if something is wrong, components are adapted or replanned. To be able to compare different reuse approaches, and to extract all the necessary information, we focus ourselves on some particular points of interest. These points of interest are mainly based on those proposed in [1] and [2] and on our own experiences [3] They are: 1) Component description, i.e. the structure of a component, including the interface. 2) Component taxonomy, i.e. their interrelationship, like a hierarchical classification. 3) The data that a component manipulates, and an abstract ....

....software components, like [6] and [7] 2] also addresses this issue. For reasons of space, we have chosen not to mention other approaches or issues in this section, although they have played a role in our analysis presented in section 3. An overview of the field of software reuse can be found in [2, 1, 8, 9]. 2.1 GenVoca In [10] components are used as building blocks for large scale software system construction. The authors point of view is based on two systems, Genesis and Avoca. Component description Components are identified by their interface. The interface of a component consists of ....

T. Biggerstaff and C. Richter, "Reusability framework, assessment, and directions.", in Frontier Series: Software reusability: Volume I - Concepts and Models, T.J. Biggerstaff and A.J. Perlis, Eds., chapter 1, pp. 1--17. ACM Press New York, 1989.

....evaluation of CodeFinder has demonstrated the effectiveness of the approach. Information Access Tools for Software Reuse Scott Henninger 2 August 1, 1995 1. Finding Examples in Software Repositories The goal of increasing programmer productivity through software reuse has proven to be elusive [1, 2, 3]. Although many approaches have been suggested [4] none of them have yet reached the critical point at which the cost of reuse is equal to or less than the effort to create new code. The problems are numerous, including the fact that an existing piece of code rarely fits exactly, that a ....

T.J. Biggerstaff, C. Richter, "Reusability Framework, Assessment, and Directions", IEEE Software, Vol. 4, No. 2, March 1987, pp. 41-49.

....are fixed for the lifetime of the application. In contrast, dynamic compositions mean that components are composed at application run time. Thus, this enables applications to be dynamically reconfigurable. Refinements can be implemented in two ways: compositionally or transformationally [Big87, Gri94]. A compositional implementation called a compositional component defines the code that is to be executed at application run time. Compositional components are templates (if composed statically) or are object libraries (when composed dynamically) A transformational implementation ....

T. Biggerstaff and C. Richter, "Reusability Framework, Assessment and Directions", IEEE Software, March 1987.

....January 2, Software Reuse Page 68 . T Transformational systems have been criticized by some researchers for their limited range of applicability [123] he programs generated with this approach were mostly toy examples, as was the case with other AI oriented automatic e a programming systems [9]. While, in principle, the transformational approach is not limited to small programs, th mount of knowledge that needs to be encoded to handle large software systems is prohibitively large. Most of the earlier D transformational systems embody basic, domain independent, programming knowledge. ....

Ted J. Biggerstaff and Charles Richter, "Reusability Framework, Assessment, and Directions," IEEE Software, pp. 2 41-49, July 1987.

No context found.

T. Biggerstaff and C. Richter, "Reusability framework, assessment, and directions.", in Frontier Series: Software reusability: Volume I - Concepts and Models, T.J. Biggerstaff and A.J. Perlis, Eds., chapter 1, pp. 1--17. ACM Press New York, 1989.

No context found.

T. Biggerstaff and C. Richter, `Reusability framework, assessment and directions', IEEE Software, 4, (2), (1987).

No context found.

T. Biggerstaff and C. Richter. "Reusability Framework, Assessment, and Directions". IEEE Software, 4(2):41-49, March 1987.

No context found.

Biggerstaff, T. and C. Richter (1987): "Reusability Framework, Assessment and Directions." IEEE Software(July): p. 41-49.

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