R.G. Fichman and C.F. Kemerer, Object technology and reuse: Lessons from early adopters, IEEE Computer 30 (1997) 47--59. Home/Search Document Details and Download
Summary Related Articles Check |
This paper is cited in the following contexts:
An Empirical User Study of an Active Reuse Repository System - Yunwen Ye Sra (2002) (1 citation) (Correct)
....studies [7] conclude that most software developers can only anticipate the existence of a limited portion of the components included in a repository, and that they would not actively seek the reuse of the components whose existence they do not know. This conclusion is corroborated by many reports [4, 5, 17] about reuse experience in companies. Even if software developers are willing to reuse a component, they might not be able to do so if they perceive reuse costs more than developing from scratch or if they Proceedings of 7th International Conference on Software Reuse (ICSR 7) Austin, TX, pp. ....
....reuse repository systems in the context of software development. Empirical studies that are based on interview and questionnaire are another approach to understand software developers general perspectives on reuse. Based on interviews with many developers in four companies, Fichman and Kemerer [5] identify many barriers to the success of reuse. Frakes and Fox [10] take a questionnaire based approach to analyze the major problems in software reuse. Research that studies how reuse influences the productivity and quality of software development [1] complements our study. We assume reuse is a ....
Fichman, R.G. and Kemerer, C.E.: Object technology and reuse: Lessons from early adopters. IEEE Software, 14(10):47-59, 1997.
Context-Aware Browsing of Large Component Repositories - Ye, Fischer (2001) (Correct)
....from a software developer. I could be creating a method that does exactly the same thing somebody else s does. even though we have access to each other s code. We might call them different names and we might have a bit different way of doing it, but we re still doing the same thing. [5] 3.2 Context Aware Browsing Information delivery systems that just throw a piece of decontextualized information at users are of little use because they ignore the working context. The working context consists of the task being performed and the user performing it. The challenge for information ....
Fichman, R.G. and C.E. Kemerer, Object Technology and Reuse: Lessons from Early Adopters. 1EEE Software. 14(10):47-59, 1997.
Integrating Active Information Delivery and Reuse Repository .. - Ye, Fischer, Reeves (2000) (Correct)
....this inhibiting factor of reuse. Devanbu et al. 5] report that because developers are unaware of reusable components, they repeatedly re implement the same function in one case, this occurred ten times. This kind of behavior is also observed as typical among the four companies investigated in [9]. From the experience of promoting reuse, Rosenbaum and DuCastel [34] conclude that making components known to developers is a key factor for successful reuse. Developers will reuse those components repeatedly once they have reused them once [24] 2.3 Cognitive Biases against Reuse Human beings ....
....and informal information for readability by peer developers. Informal information includes structural indentation, comments, and identifier names. Comments and identifier names are important beacons for the understanding of programs, because they reveal the important concepts of programs [2, 9, 29]. One important constraint of a program is its type compatibility, which is manifested in its signature. A signature is the type expression of a program, and defines its syntactical interface. For a reusable component to be easily integrated, its signature should be compatible with the ....
Fichman, R.G. and C.E. Kemerer, "Object Technology and Reuse: Lessons from Early Adopters," IEEE Software, 14(10), 47-59 (1997).
An Active and Adaptive Reuse Repository System - Ye (2001) (Correct)
....Many reports about reuse experience in software companies illustrate the phenomenon of information islands. Devanbu et al. have reported that developers, unaware of reusable components, repeatedly re implement the same function in one case, ten times [3] Similar reports can be found in [5, 20]. No attempt to reuse is also caused by the perceived low reuse utility reuse utility is the ratio of reuse value to reuse cost. Due to cognitive biases against reuse, software developers tend to underestimate the reuse value and to overestimate the reuse cost [24] This perceived low reuse ....
Fichman, R. G. and C. E. Kemerer, "Object Technology and Reuse: Lessons from Early Adopters," IEEE Software, 14(10), pp. 47-59, 1997.
Collaborative Use Design of Interactive Simulations - Repenning, Ioannidou, Phillips (Correct)
....activities. Students are users of the finished content. Supporting the Use = Design spectrum allows teachers to interact with technology at their desired level of comfort. Where teacher comfort tapers off, developers may support them. Limitations Making software reuse work is a hard problem [Fichman Kemere 1997]. We believe that if 90 of a component is useful and the remaining 10 need to be changed but cannot be changed by its user, then the component is 100 unusable. In the case of the EOE, users typically need to edit Java source to modify components. Within ESCOT, some modification is possible ....
Fichman, R. G., & Kemere, C. F. (1997). Object Technology and Reuse: Lessons from Early Adopters. IEEE Computer, 30(10, October).
Electronic Commerce as innovation - a framework for.. - Wilkins, Swatman.. (2000) (Correct)
....a shared, long term vision for IT would be better explained with process analysis rather than factor models. We suspect there are several paths to a shared IT vision and that a longitudinal ethnographic study is required to illuminate the antecedents of this construct [27] Fichman and Kemerer [11] looked at prominent innovations in software process technology (CASE) They found that an innovation which enjoys robust sales yet is only sparsely deployed is not genuinely diffused in the sense of having a significant impact on the operational processes of acquiring firms. Deployment, they ....
Fichman, R.G. and Kemerer, C.F., (1997), Object Technology and Reuse: Lessons from Early Adopters, IEEE Computer, 30,10, 47-59.
Accessing a Medical Database using WWW-Based User Interfaces - Sinha, Bowers, Mamrak (1998) (Correct)
....used by applications. Considerably more advantage can be realized if the patterns of interaction among the components are similar or identical across different applications in the project. Many nontechnical factors can mitigate against success. An emerging consensus in the reuse community [1] is that the primary nontechnical reuse barriers stem from the organization and management of the software development team and include: ffl A poor investment in organizational learning. ffl A lack of attention or effort to develop a complete software architecture, including not only tangible ....
Robert G. Fichman and Chris F. Kemerer. Object technology and reuse: Lessons from early adopters. Computer, pages 47--58, October 1997.
Activity Based Costing for Component-Based Software Development - Fichman, Al. (2002) Self-citation (Fichman Kemerer) (Correct)
No context found.
R.G. Fichman and C.F. Kemerer, Object technology and reuse: Lessons from early adopters, IEEE Computer 30 (1997) 47--59.
Investigating Effective Inspection of Object-oriented Code - Dunsmore (2002) (Correct)
No context found.
R. G. Fichman and C. F. Kemerer, Object Technology and Reuse: Lessons from Early Adopters, IEEE Computer, 30(10), pp. 47-59, 1997.
uJuly--September 1998 - Te Mb Er (Correct)
No context found.
R. G. Fichman and C. F. Kemerer, "Object Technology and Reuse: Lessons from Early Adopters," IEEE Computer, Vol. 30, No. 10, Oct. 1997, pp. 47--59.
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