S. Henninger, "Case-Based Knowledge Management Tools for Software Development," Journal of Automated Software Engineering, vol. 4, pp. 319-340, 1997. Home/Search Document Details and Download
Summary Related Articles Check |
This paper is cited in the following contexts:
Program Comprehension in Multi-Language Systems - Kullbach, Winter, Dahm, Ebert (1998) (10 citations) (Correct)
....the phases after software development. Already in the late seventies it has been reported that about 47 of maintenance efforts are spent on program understanding whereas only about 25 are spent on modification [18] Following other studies, the program understanding effort is said to cover 40 [21], 60 [38] or even up to 90 [40] As such, program understanding is the key activity during software maintenance providing a large potential to improving the efficiency of software development and maintenance processes. There are various approaches to program understanding, which follow a common ....
S. Henninger. Case-Based Knowledge Management Tools for Software Development. Journal of Automated Software Engineering, 4(3), July 1997.
Program Comprehension in Multi-Language Systems - Kullbach, Winter, Dahm, Ebert (1998) (10 citations) (Correct)
....the phases after software development. Already in the late seventies it has been reported that about 47 of maintenance efforts are spent on program understanding whereas only about 25 are spent on modification [16] Following other studies, the program understanding effort is said to cover 40 [19], 60 [35] or even up to 90 [37] As such, program understanding is the key activity during software maintenance providing a large potential to improving the efficiency of software development and maintenance processes. There are various approaches to program understanding, which follow a common ....
S. Henninger. Case-Based Knowledge Management Tools for Software Development. Journal of Automated Software Engineering, 4(3), July 1997.
A Case-Based Approach to Tailoring Software Processes - Henninger, Baumgarten (2001) Self-citation (Henninger) (Correct)
No context found.
S. Henninger, "Case-Based Knowledge Management Tools for Software Development," Journal of Automated Software Engineering, vol. 4, pp. 319-340, 1997.
Using Organizational Learning Techniques to Develop.. - Henninger, Lu, Faith (1997) Self-citation (Henninger) (Correct)
No context found.
Henninger, S. "Case-Based Knowledge Management Tools for Software Development," Journal of Automated Software Engineering, (in press).
Software Process as a Means to Support Learning Software.. - Henninger (2000) Self-citation (Henninger) (Correct)
No context found.
Henninger, S., "Case-Based Knowledge Management Tools for Software Development." Journal of Automated Software Engineering, 4 (1). 319-340.
A Tool for Managing Software Development Knowledge - Henninger, Schlabach (2001) Self-citation (Henninger) (Correct)
No context found.
S. Henninger, "Case-Based Knowledge Management Tools for Software Development," Journal of Automated Software Engineering, vol. 4, pp. 319-340, 1997.
Supporting Adaptable Methodologies to Meet Evolving.. - Henninger, Ivaturi, .. (2002) (2 citations) Self-citation (Henninger) (Correct)
No context found.
Henninger, S., "Case-Based Knowledge Management Tools for Software Development," Journal of Automated Software Engineering, 4(3), pp. 319-340, 1997.
Supporting Adaptable Methodologies to Meet Evolving.. - Henninger, Ivaturi, .. (2002) (2 citations) Self-citation (Henninger) (Correct)
No context found.
Henninger, S., "Case-Based Knowledge Management Tools for Software Development," Journal of Automated Software Engineering, 4(3), pp. 319-340, 1997.
Software Process as a Means to Support Learning Software.. - Henninger (2000) Self-citation (Henninger) (Correct)
No context found.
Henninger, S., "Case-Based Knowledge Management Tools for Software Development." Journal of Automated Software Engineering, 4 (1). 319-340.
Using Organizational Learning Techniques to Develop.. - Henninger, Lu, Faith (1997) Self-citation (Henninger) (Correct)
No context found.
Henninger, S. "Case-Based Knowledge Management Tools for Software Development," Journal of Automated Software Engineering, (in press).
Tool Support for Experience-Based Methodologies - Henninger (2003) Self-citation (Henninger) (Correct)
No context found.
S. Henninger, "Case-Based Knowledge Management Tools for Software Development," Journal of Automated Software Engineering, 4(3), pp. 319-340, 1997.
Turning Development Standards Into Repositories of Experiences - Henninger (2001) (1 citation) Self-citation (Henninger) (Correct)
No context found.
S. Henninger, "Case-Based Knowledge Management Tools for Software Development," Journal of Automated Software Engineering, vol. 4, pp. 319-340, 1997.
A Tool for Managing Software Development Knowledge - Henninger, Schlabach (2001) Self-citation (Henninger) (Correct)
No context found.
S. Henninger, "Case-Based Knowledge Management Tools for Software Development," Journal of Automated Software Engineering, vol. 4, pp. 319-340, 1997.
A Case-Based Approach to Tailoring Software Processes - Henninger, Baumgarten (2001) Self-citation (Henninger) (Correct)
No context found.
S. Henninger, "Case-Based Knowledge Management Tools for Software Development," Journal of Automated Software Engineering, vol. 4, pp. 319-340, 1997.
A Tool for Managing Software Development Knowledge - Henninger, Schlabach Self-citation (Henninger) (Correct)
....is then disseminated to subsequent projects to provide experience based knowledge of development issues encountered at a software development organization. These principles have been demonstrated through an exploratory prototype, named BORE (Building an Organizational Repository of Experiences) [19]. Early BORE research focused on developing tools to support the creation of case based repositories [19] BORE prototypes were evaluated in two separate contexts. In the first, a pilot project at Union Pacific Railroad [18] evaluated BORE by documenting some cases and providing comments of how ....
....encountered at a software development organization. These principles have been demonstrated through an exploratory prototype, named BORE (Building an Organizational Repository of Experiences) 19] Early BORE research focused on developing tools to support the creation of case based repositories [19]. BORE prototypes were evaluated in two separate contexts. In the first, a pilot project at Union Pacific Railroad [18] evaluated BORE by documenting some cases and providing comments of how BORE can be improved to better meet their specific needs. The second evaluation context was a Software ....
[Article contains additional citation context not shown here]
Henninger, S., "Case-Based Knowledge Management Tools for Software Development," Journal of Automated Software Engineering, vol. 4, pp. 319-340, 1997.
An Organizational Learning Method for Applying Usability.. - Henninger (2001) Self-citation (Henninger) (Correct)
....of this work is not the creation or discovery of good guidelines or patterns, but the creation of tools that capture and disseminate knowledge of user interface design principles and experiences at the right time during the development process. In addition, our organizational learning approach [7] allows the incremental capture of the characteristics of the context of use so the applicability rules and guidelines can evolve as new requirements are encountered, new techniques are used, and new designs are created. 2 Usability Guidelines and Patterns Usability guidelines have become a ....
....to learn and improve on past performance. Emphasis must be placed on establishing a continuous improvement process that enhances product quality and developer productivity, while recognizing past experiences as a catalyst for the learning process. We call this an organizational learning approach [7] to emphasize that the knowledge is used as the basis for improvement, not just memorizing past experiences [43 45] 3.1 The GUIDE Process for Applying Usability Resources Our approach to supporting organizational learning to usability resources is a combination of tool and process to capture ....
[Article contains additional citation context not shown here]
S. Henninger, "Case-Based Knowledge Management Tools for Software Development," Journal of Automated Software Engineering, vol. 4, 1997, pp. 319-340.
An Environment for Reusing Software Processes - Henninger (1998) (4 citations) Self-citation (Henninger) (Correct)
....for the continuous improvement of process and quality. Rule Based Process Support Earlier work in our laboratory has focused on an organizational learning approach to software development demonstrated in an exploratory prototype, named BORE (Building an Organizational Repository of Experiences) [16]. The general approach is to capture project experiences in a case based repository that contains information about how project issues are resolved and the resources used to resolve the issues [15] This repository is used as a basis for reuse of software artifacts, documentation, and general ....
S. Henninger, "Case-Based Knowledge Management Tools for Software Development," Journal of Automated Software Engineering, 1997, (in press).
Tools Supporting the Creation and Evolution of Software.. - Henninger (1997) (1 citation) Self-citation (Henninger) (Correct)
....many initiatives within the organization had emerged to address the need to capture and disseminate information, a strategy was needed to tie these efforts together. This approach has been demonstrated in an exploratory prototype, named BORE (Building an Organizational Repository of Experiences) [11]. In BORE, cases represent project issues and contain information about how issues were resolved and the resources used to resolve the issues [9] Cases are stored in a repository that can be searched and browsed to find issues with similar characteristics [10 12] Although refinement and ....
S. Henninger, "Case-Based Knowledge Management Tools for Software Development," Journal of Automated Software Engineering, 1997, (in press).
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