Software Reuse Guidelines,

Hooper, James; Chester, R.O.

doi:10.21236/ada325305

Cited by 11 publications

(9 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…A case study research design also enables discovery of other facilitating factors from a process view. Though researchers have reported a number of difficulties associated with reuse adoption, empirical investigation of these factors has been lacking (Biggerstaff and Perlis, 1989;Hooper and Chester, 1991;Frakes et al, 1991;Card and Comer, 1994;Jones, 1994;Kim and Stohr, 1998;Fichman and Kemerer, 2001). This study fills that gap.…”

Section: Introductionmentioning

confidence: 90%

Managing Technology and Administration Innovations: Four Case Studies on Software Reuse

Sherif¹,

Menon²

2004

JAIS

View full text Add to dashboard Cite

A software process innovation, such as software reuse, involves both technology and administration innovation. Following literature on organizational change, absorptive capacity, innovation assimilation stages, and software reuse, we develop a process model of the assimilation trajectory of an organization's innovation. The model postulates that actors at different organizational levels implement strategy, process, and culture changes in order for an organization to advance through the stages of innovation assimilation. The actions at these levels instill routines that establish the absorptive capacity for implementing future innovations. Case-study data collected from four software development sites -two reporting failure in the reuse program, and two reporting success -revealed that programs that implemented change at the strategy, process and culture levels scored higher on all paths in the model than nonsuccessful programs. The right incentives help in the latter stages of innovation assimilation during which culture change by operational staff is important. No reuse metrics were collected Team-based structures Frequent formal and informal communication Infrequent formal communication Infrequent formal communication Frequent formal and informal communication

show abstract

Section: Introductionmentioning

confidence: 90%

Managing Technology and Administration Innovations: Four Case Studies on Software Reuse

Sherif¹,

Menon²

2004

JAIS

View full text Add to dashboard Cite

show abstract

“…The main cause of this failure was a combination of poor quality and the lack of reusability of software components. Both factors led to chronic maintenance problems (Hooper and Chester 1991). A proposal to solve this "software crisis" was based on the reuse of interchangeable components (McIlroy, 1976).…”

Section: Hardware or Software?mentioning

confidence: 99%

The Software Crisis of Synthetic Biology

Valverde

Porcar

Peretó

et al. 2016

Preprint

View full text Add to dashboard Cite

In fifteen years, Synthetic Biology (SB) has moved from proof-of-concept designs to several flagship achievements. Standardisation efforts are still under way, basic engineering concepts such as modularity and orthogonality are still controversial in biology, and making predictions from computer models is still unreliable. A deep characterization in the pattern of re-use of biological blocks in SB has not been attempted to date. We have compared the topological organisation of two different technological networks, one associated to a standard, large-scale software repository and the second provided by the Registry of Standard Biological Parts (RSBP). Our results strongly suggest that software engineering, and not industrial engineering, is the closest complex system to SB. In both cases, combining standard or quasi-standard components assembly with tinkering may not be at odds with success.

show abstract

“…In software engineering, the trend is changing from the traditional software development approach to the extension and integration with existing systems [1][2][3][4]. An ideal software component reuse technology would enable software developers to quickly use and adapt components in software development.…”

Section: Introductionmentioning

confidence: 99%

Development metrics measurement level for component reusability evaluation approach (CREA)

Ismail¹,

Mohd²,

Jalil³

et al. 2019

IJECE

View full text Add to dashboard Cite

The study of software component reuse is rising in software development field and one of the methods used to reduce the production cost and time. Among the problems faced by software developers in component reuse, is the difficulty to determine which set of components are suitable to use in new software development. Thus, this study was conducted with the purpose; to define the characteristics of software component reusability evaluation approach (CREA) based on experienced software developer’s feedback, and to estimate the measurement level for each of the predefined metric. Three characteristics and sub characteristics, namely understandability (documentation level and observality), adaptability (customizability), and portability (external dependency) were identified that have been used to develop the metrics for CREA. The result for all metrics will be used as an input to the fuzzy inference system (FIS) for measuring the reusability level of the component.

show abstract

Software Reuse Guidelines,

Cited by 11 publications

References 0 publications

Managing Technology and Administration Innovations: Four Case Studies on Software Reuse

Managing Technology and Administration Innovations: Four Case Studies on Software Reuse

The Software Crisis of Synthetic Biology

Development metrics measurement level for component reusability evaluation approach (CREA)

Contact Info

Product

Resources

About