V. R. Basili and H. D. Rombach, "Support for Comprehensive Reuse," Software Engineering Journal, 1991, pp. 303-316  Home/Search   Document Not in Database   Summary   Related Articles   Check

....from one type of experience into another (e.g. a number of related lessons learned into a business process model) 2. 1 Best Practice and Lessons Learned Life Cycle Model We have composed a comprehensive life cycle model for best practices and lessons learned from aspects presented in [2, 6]. This lifecycle model is applicable to software engineering knowledge and is the basis for many of our experience management projects (e.g. COIN, SKe, InDiGo, ESERNET) In addition, the life cycle model is sound with the ideas of the philosopher Immanuel Kant regarding theory ....

V. R. Basili and H. D. Rombach. Support for comprehensive reuse. IEEE Software Engineering Journal, 6(5):303--316, Sept. 1991.

....GQM and QIP in a real software development organization. The last step in the QIP requires experiences to be applied to refine models. This means that there is an organizational learning process where the experiences are made explicitly available as models. In order to facilitate efficient reuse (Basili, 1991), the experiences and models should be stored in an experience base (Basili, 1993) The responsibility of the Experience Factory is to manage the experiences, both in terms of analyzing and packaging the data collected from a project, and in terms of supporting an experience base where the models ....

Victor Basili and Dieter Rombach. Support for comprehensive reuse. Software Engineering Journal, September 1991.

....of an individual project. To facilitate these cross project measurement activities, the organisational structure within which the individual projects run is examined. To illustrate this, the authors discuss the use of measurement within the organisational model provided by the TAME project [1 3]. 1. Introduction Software measurement is often considered in isolation from the software development process within which the measurements are taken. Metrologists discuss the details of measurement definition and validation. Process modellers discuss the ordering and organisation of ....

....of measurement within an improvement oriented organisational structure is also considered. This consideration is based around work done as part of the TAME project outlining an organisational structure for process improvement combining support for model building, project guidance and measurement [1 3]. 2. The relationship between measurement and process The famous quote from DeMarco that you can t control what you can t measure [4] shows the dependency of development process control on software measurement. What may perhaps be less apparent, though equally true, is the dependency of ....

[Article contains additional citation context not shown here]

Basili, V.R. and Rombach, H.D., "Support for comprehensive reuse", report No. CS-TR-2606, 1991, University of Maryland.

....of reusable artifacts. This separation of the product specific development environment from the reusable artifact development environment is a primary feature of the reuse oriented framework called the Experience Factory developed by researchers at the University of Maryland at College Park [4]. The wide applicability of a reusable artifact requires that the process used to build the artifact emphasize quality control because the impact of low quality (in particular, severe errors) is as wide as the number of applications that reuse the artifact. On the other hand, timely development of ....

Basili, V., Rombach, D. Support for comprehensive reuse. Department of Computer Science, University of Maryland at College Park, UMIACS-TR-91-23, CS-TR-2606, 1991.

....Integration problems model [Yakimovich et al. 99b] gives a high level classification of integration issues and possible integration strategies to overcome them. 4. Effort estimation model for COTS integration giving means to estimate COTS integration effort. Comprehensive reuse model [Basili, Rombach 91] allows for identifying appropriate information about reuse candidates, the requirements for the system, and of reuse activities. We give an introduction to these models below. We start with the architectural model. The architectural model Yakimovich s architectural model is based on the ....

....expressed in lines of code (LOC) Yakimovich s algorithm for applying this model is attached in Appendix G. Effort estimation model algorithm. The comprehensive reuse model The comprehensive reuse model is intended for reusing different artifacts, such as products, processes, and knowledge [Basili, Rombach 91] The model describes the transformation of reuse candidates (e.g. COTS products) into required objects through a reuse process. Yaldmovich tailor the reuse model for COTS software products. The model defines characterization schemes or reuse templates for describing reuse candidates and ....

[Article contains additional citation context not shown here]

Basili, V.R, Rombach, H.D., "Support for comprehensive reuse", Software Engineering Journal, September 1991.

....however, there are strong differences about what to reuse and how to reuse. Typically, software reuse needs some kind of modification or adaptation to the new environment. The degree of modification depends on how many, and to what degree, existing object characteristics differ from those required [6]. There are a variety of artefacts that are candidates for reuse: Requirement models and specifications, components, architectures and designs, checklists, scenarios, source code, user and technical documentation, human interfaces, data, test cases, project plans or cost and effort estimates. ....

V.R. Basili, H.D. Rombach. Support for comprehensive reuse. Software Engineering Journal, September 1991, pp 301-318

....while adding necessary degrees of formal procedures to ensure high quality products. This involves not only defining a process, but also using feedback from projects to refine and improve its procedures. These concepts have their predecessors, particularly in the form of software factories [2 4] and process programming [10, 27] but little in the way has been done to create interfaces and CASE tools to support these concepts. This work attempts to fill this gap with the organizational learning perspective, case based decision support, and the BORE prototype. Thus far, most research on ....

....a form of knowledge editing [29] than process programming [10, 27] which is more concerned with integrating tools and documents to automate development activities, although elements of both issues are present. These concepts have their predecessors, particularly in the form of software factories [2 4] and process programming [10, 27] but little in the way has been done to create interfaces and CASE tools to support these concepts. The QIP approach in TAME [3] is another maturity based framework that is designed to develop and package experiences to facilitate reuse within the organization. ....

Basili, V.R. and Rombach, H.D., "Support for Comprehensive Reuse," Software Engineering Journal, pp. 303-316, 1991.

.... engineering experience besides code include requirements, design, and other software documentation as well as design method tools [39] software best practices [31] technologies [23] lessons learned [19, 46] various models (e.g. resource, product, process, quality [13] and cost models [15]) measurement plans [26, 60] and data [59] All this experience has to be stored and retrieved. On the retrieval side, many techniques have been employed. These include classification techniques from library science such as enumerated classification, faceted classification, and information ....

....Measurement Tool Other SE Tool General Purpose Browser Sync Module Other SE Tool Other EB Tool artifact specific access EB specific access reference 4.1 Decomposition of the Task Reuse The task reuse is decomposed as shown in Fig. 3 (a refinement of the decomposition presented in [15, 2]) In the following, the objectives of the subtasks are described. The objective of reusing experience is to save effort while delivering better quality in less time. This is done in several ways: First, instead of developing new artifacts from scratch, appropriate reuse candidates are retrieved ....

[Article contains additional citation context not shown here]

Victor R. Basili and H. Dieter Rombach. Support for comprehensive reuse. IEEE Software Engineering Journal, 6(5):303--316, September 1991.

....[2,5] The OTSO method, provides a repeatable process that evaluates, selects and implements reusable software components in an organization. OTSO supports systematic reuse and allows accumulation of OTS software selection experience, supporting continuous improvement of a component factory [4,8]. Figure 4 presents the OTSO method in the context of the Experience Factory. The OTSO components are highlighted in darker color. A customized, enactable model of the OTSO method is captured in a form of a process definition in the Experience Base. This process definition is reused, and modified ....

V. R. Basili and H. D. Rombach, Support for comprehensive reuse, Software Engineering Journal, vol. September. pp. 303-316, 1991.

....model itself (e.g. the language the model is represented in) the interface of the experience model (i.e. dependencies for reusing the model) and context of the experience model (i.e. the application domain for which the model was developed, the projects in which the model was applied, etc. [BR91]. Often several objects are reused within a project which are interrelated. For instance, the employed development process has an impact on the quality rating of the product. Therefore the quality of the system should not be stored independently from the employed process. This has to be ....

Victor R. Basili and H. Dieter Rombach. Support for comprehensive reuse. IEE Software Engineering Journal, 6(5):303-316, September 1991.

....[SPM94] Traditionally, the emphasis has been on reusing code. However, reuse does not have to stop there. All kinds of software knowledge can be reused, including products (documents created by a software development project) processes (activities or actions aimed at creating some product) [BR91], and models such as effort prediction and productivity models, models of the application being implemented, or any kind of necessary domain knowledge. The reuse of all kinds of software knowledge is one of the main pillars of the approach used for transferring software technologies by our ....

....the project is analyzed (QIP 5) and finally the newly gained experience is packaged (i.e. integrated into the experience base; QIP 6) This cycle is depicted in Figure 1. On the project performance level, a reuse model such as the one proposed by Basili and Rombach can be used (see Figure 2) [BR91]. Given a system S where a new object x is to be integrated, a specification x of the object x is defined. The next step is to identify a set of reuse candidates x 1 , x n . These candidates are evaluated. Eventually the best suited candidate x k is selected. Depending on how close x ....

[Article contains additional citation context not shown here]

Victor R. Basili and H. Dieter Rombach. Support for comprehensive reuse. IEEE Software Engineering Journal, 6(5):303--316, September 1991.

....[16] Traditionally, the emphasis has been on reusing code. However, reuse does not have to stop there. All kinds of software related knowledge can be reused, including products (documents created by a software development project) processes (activities or actions aimed at creating some product) [9], and anything else useful for software development, e.g. effort prediction and productivity models or models of the application being implemented. Reuse can be applied both to the planning of a software development project and to the performance of the project. 2.1 Reuse for Planning a Software ....

.... detected, the experience base may be consulted for possible actions like reducing the number of reviews (which will, however, increase project risks) Reuse for the performance of a software development project is typically described by a reuse model such as the one proposed by Basili and Rombach [9]. Given a system S where a new object is to be integrated, a specification x of an object x is defined. The next step is to identify a set of reuse candidates x 1 , x n . These candidates are evaluated. Eventually the best suited candidate x k is selected. Depending on how close x k is to x, ....

Victor R. Basili and H. Dieter Rombach. Support for comprehensive reuse. IEEE Software Engineering Journal, 6(5):303--316, September 1991.

....the aim of finding an explanation for the diversity of domain modelling techniques, and the type of information they represent. The results of this survey are presented, along with the conclusions obtained. 1. INTRODUCTION Software reuse has been identified as a goal by several organisations [Leach97,Basili91]. Reuse of products, processes and, generally, all kinds of knowledge is an effective way to achieve the main goal in Software Engineering (SE) the development of reliable and high quality software systems on schedule and within budget [Basili91,Basili92] One of the difficulties involved in ....

.... as a goal by several organisations [Leach97,Basili91] Reuse of products, processes and, generally, all kinds of knowledge is an effective way to achieve the main goal in Software Engineering (SE) the development of reliable and high quality software systems on schedule and within budget [Basili91,Basili92]. One of the difficulties involved in reuse is the duality of issues: on the one hand, there are operational issues (reusing existing information to develop software systems) on the other hand, there are infrastructure issues (defining, populating and evolving the repositories of reusable ....

[Article contains additional citation context not shown here]

V.R. Basili and H.D. Rombach. Support for comprehensive reuse. Software Engineering Journal, pages 303-316, September 1991.

No context found.

Victor R. Basili and H. Dieter Rombach. Support for comprehensive reuse. IEE Software Engineering Journal, 6(5):303--316, September 1991.

....from ongoing projects as well as to support guidance of projects based on sound, objective criteria. 2. 1 The TAME Model The Quality Improvement Paradigm (QIP) developed in the TAME project combines support for model building with support for project guidance, and also integrates measurement [10, 14]. Process improvement is achieved by repeating the following sequence of steps for each project: Characterize: The project at hand is characterized based on available models for similar projects. Set goals: Project and quality improvement goals are identified and stated in a operational ....

.... as well as the performance stage of a project (where actual data are compared to historical baseline models in order to achieve guidance) Re packaging refers to all activities aimed at improving the reuse potential of existing experience (includes generalizing, tailoring, formalizing) [14]. In the remainder of the paper we will use the following terminology: Descriptive (or as is ) modeling: the activities aimed at explicitly capturing some aspect(s) of an existing software project. Prescriptive (or to be ) modeling: the activities aimed at creating an explicit model of some ....

[Article contains additional citation context not shown here]

Victor R. Basili and H. Dieter Rombach. Support for comprehensive reuse. IEE Software Engineering Journal, 6(5):303--316, September 1991.

....set of questions pertinent to the defined experimental goal and a set of metrics allowing us to devise answers to these questions. We do not present the complete GQM here, only the metrics we derived. However, the metrics described in the next section were derived by following the GQM methodology [6]. Independent and Dependent Variables Here we define the study s independent variables (e.g. size, amount of reuse) and dependent variables (e.g. productivity, defect density) We intend to make the underlying assumptions and models clear, so a precise terminology is used in the rest of the ....

Basili, V., and Rombach, H.D. Support for comprehensive reuse. IEEE Software Engineering Journal (Sept. 1991), 303--316.

No context found.

V. R. Basili and H. D. Rombach, "Support for Comprehensive Reuse," Software Engineering Journal, 1991, pp. 303-316

No context found.

Basili, V.R., Rombach, H.D., "Support for Comprehensive Reuse." Software Engineering Journal. 303-316.

No context found.

V. R. Basili and H. D. Rombach, "Support for Comprehensive Reuse," Software Engineering Journal, pp. 303-316, 1991.

No context found.

V. R. Basili and H. D. Rombach, "Support for Comprehensive Reuse," Software Engineering Journal, pp. 303-316, 1991.

No context found.

Basili, V.R., Rombach, H.D., "Support for Comprehensive Reuse." Software Engineering Journal. 303-316.

No context found.

V. R. Basili and H. D. Rombach. Support for comprehensive reuse. Software Engineering Journal, 6(5):303--316, September 1991.

No context found.

V. R. Basili and H. D. Rombach, "Support for Comprehensive Reuse," Software Engineering Journal, pp. 303-316, 1991.

No context found.

V. R. Basili and H. D. Rombach, "Support for Comprehensive Reuse," Software Engineering Journal, pp. 303-316, 1991.

No context found.

V. R. Basili and H. D. Rombach, "Support for Comprehensive Reuse," Software Engineering Journal, pp. 303-316, 1991.

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