H. D. Rombach and M. Verlage, `Directions in software process research ', in Advances in Computers, volume 41, (1995).  Home/Search   Document Not in Database   Summary   Related Articles   Check

.... Location: Subject Meeting Objective: Project Meeting Record Team 0 7803 6424 4 00 10.00 2000 IEEE October 18 21, 2000 Kansas City, MO group method [3] 4] and a quality improvement process model similar to Deming s Plan Do Check Act approach [5]. Although the cooperative group method is typically applied to learning environments, the concepts promoted by this approach transfer to project teams. In project team settings, the common goal that builds positive interdependence is creation of a quality product whereas the common goal in ....

....helps identify groups with problems allowing for early intervention. At the end of the semester, each student documents lessons learned during a particular phase of the project. The approaches discussed in this section are similar to standard improvement process models such as Plan Do Check Act [5] that provide a feedback cycle which enables learning from past results. FACILITATION To facilitate the course, the Guidance Team [6] consisting of the professor and TA, oversees and supports the activities of the project teams. Before the project is assigned, the Guidance Team: prepares a ....

Rombach, H.D. and Verlage, M., Directions in Software Process Research, in Advances in Computers, M. Zelkowitz (ed.). San Diego: Academic Press, 1995.

....there is a high risk of failure. Process Modeling Software processes are series of human actions to create software products. Process models are explicit representations of such processes that support communication, package experience, ease analysis, and provide guidance for process performance [8]. Process modeling is a software engineering discipline that focuses on how to create useful models of real world processes. 110 is a process modeling tool that has been developed by Fraunhofer IESE over the last five years [6] Its intention is to make complex software processes easily ....

Rombach, H.D., Verlage, M., Directions in Software Process Research, Advances in Computers, pp 1-63, Vol. 41, Academic Press, 1995

....between the code to be tested and other software documents. Thus, we have been exploring the application of the MultiView architecture to the provision of multiple views of the software process. In providing multiple views of the software process, our environment has similar goals to MVP S[22], among others. As shown in Figure 3, the database process in this case contains a representation of a particular software development process (i.e. the one being followed by this project) for details of this software process representation, the interested reader is referred to [7, 8] For this ....

H. D. Rombach and M. Verlage, "Directions in software process research", i._.an Advances in Computers, Volume 41, (Ed.), pp.l-63 (Academic Press, Inc., , 1995).

....sta# must be trained. The approach presented here addresses this problem in the line of the experience based construction of software. It combines two recent approaches from software engineering: the experience factory ##Basili et al. 1994#; see also section . 3# and softwareprocess modeling ##Rombach and Verlage, 1995## approach. The approach to a CBR development methodology is itself very CBR like . In a nutshell, it captures previous experience from CBR development and stores it in a so called experience base #a term from the experience factory approach#. The entities being stored in the experience base are ....

Rombach, H. D. and Verlage, M. #1995#. Directions in software process research. In Zelkowitz, M. V., editor, Advances in Computers, Vol. 41, pages 1#61. Academic Press.

.... modelling and project management approaches fail to incorporate and then capitalise upon human resources and their experiences [1, 5] Representation and incorporation of human aspects in modelling frameworks is commonly problematic for software (development and engineering) process research [3, 4, 8]. In response to these limitations the demand exists for the development of methods for description and registering knowledge about project resources, which provide support for effective solutions to the software engineering problems relevant to project resources. That is, there is a need to apply ....

H. D. Rombach, and M. Verlage, "Directions in Software Process Research", in Advantages in Computers , Vol. 41, Academic Press, Inc., 1995. 10

.... modelling processes (be they for developing software, hypermedia, or general systems) developers will be better able to understand and manage the way that they undertake development, and organisations will be better able to meet market requirements for productivity, quality, and predictability [19]. Once we have a general model, application to specific domains will allow us to develop specialised models of the hypermedia development process which have practical relevance. In this activity use can be made of the considerable body of work on process modelling which already exists in the field ....

....to specific domains will allow us to develop specialised models of the hypermedia development process which have practical relevance. In this activity use can be made of the considerable body of work on process modelling which already exists in the field of software engineering (for a review see [19]) Process Modelling Frameworks The first step in developing hypermedia development process models is to develop a framework within which such modelling can occur. Most disciplines have a framework which gives an indication of those elements of the process (overall inputs, outputs, resourcing, ....

[Article contains additional citation context not shown here]

Rombach, H.D. & Verlage, M. "Directions in Software Process Research", Advances in Computers, Vol. 41. pp1-63.

....engineering activities. Understanding commonalties and differences between process types is a key factor for better process support. Process support includes improved communication, guiding people when performing processes, improving both processes and their results, and automating process steps (Rombach, and Verlage, 1995). Software process modeling and enactment is one of the main areas in software engineering research. Several frameworks have been developed (e.g. procedural (Sutton, Osterweil, and Heimbigner, 1995] rule based (Kaiser, Feiler, and Popovich, 1988; Peuschel, Schfer, and Wolf, 1992] Petri net ....

Rombach, H.-D., and Verlage, M. (1995). Directions in software process research. In M. V. Zelkowitz (Eds.), Advances in Computers, vol.41. Academic Press.

....engineering (KE) in the light of methodology development. 2. Software process modelling Software engineering is concerned with aspects of software development and maintenance; planning of software developments projects; performing development and project management, including quality assurance (Rombach Verlage, 1995). Particularly, SE is concerned with principles, methods, techniques, and tools that can support these activities. Since CBR application development is a special kind of software development, building a CBR methodology can certainly be viewed as a SE research and development activity. 1 INRECA: ....

....the development of the application and allows the team to have a coherent and consistent view of the path to a successful application (Breen Johnston 1996) 2. 1 Software Process Models One area of SE that can provide such a philosophy also for a CBR methodology is software processes modelling (Rombach Verlage, 1995). In this area, one distinguishes between product engineering process models and process engineering process models. Product engineering process models model the engineering of the product, i.e. the software that has to be produced. Unlike early approaches in SE, the software development is ....

[Article contains additional citation context not shown here]

. Directions in Software Process Research. In: M. V. Zelkowitz

....activities [FH 93] Understanding commonalties and differences between process types is a key factor for better process support. Process support includes improved communication, guiding people when performing processes, improving both processes and their results, and automating process steps [RV 95] Software process modeling and enactment is one of the main areas in software engineering research. Several frameworks have been developed (e.g. procedural [SOH 95] rule based [KFP88, TKP 94, PSW 92] Petri net based [BFG 93a] object oriented [CHL 94] Process sensitive software engineering ....

H.-D. Rombach, M. Verlage. Directions in software process research. In M. V. Zelkowitz, editor, Advances in Computers, vol.41, pages 1--63. Academic Press, 1995.

....staff must be trained. The approach presented here addresses this problem in the line of the experience based construction of software. It combines two recent approaches from software engineering: the experience factory ( Basili et al. 1994) see also section . 3) and software process modeling ((Rombach and Verlage, 1995)) approach. The approach to a CBR development methodology is itself very CBR like . In a nutshell, it captures previous experience from CBR development and stores it in a so called experience base (a term from the experience factory approach) The entities being stored in the experience base are ....

Rombach, H. D. and Verlage, M. (1995). Directions in software process research.

....tasks. 3. 2 Process centered software development 3 In Software Engineering, the need for process engineering has become obvious [21, 17] In order to improve the software process and the software, process modeling, project planning and management, change control, quality measurement and reuse [22, 36] have to be introduced. For this, several process centered software development systems to guide, reason about, control, and coordinate software processes [12, 15, 39, 36] have been developed. Two characteristics of software processes that influence research in this area are their long duration ....

....the software process and the software, process modeling, project planning and management, change control, quality measurement and reuse [22, 36] have to be introduced. For this, several process centered software development systems to guide, reason about, control, and coordinate software processes [12, 15, 39, 36] have been developed. Two characteristics of software processes that influence research in this area are their long duration where necessary changes occur, and the large 2. The project is supported by the Volkswagen Stiftung. Involved are in Computer Science: Prof. Dr. Michael M. Richter s group ....

H. D. Rombach, M. Verlage, Directions in Software Process Research, in: M. V. Zelkowitz, ed., Advances in Computers, Volume 41 (Academic Press, Boston, 1995) 1-63.

....context. More precisely, it should enable managers to cope with: control flow, sequencing and constraints on sequences, defining sequential processing and parallel processing, temporal aspects such as scheduling, resource constraints and allocation. These problems are analysed in [1] 2] 3] [4]. The changes in execution context can be caused by variations in resources and needs. We mention here three significant categories of changes: the gradual collection and analysis of information about the current process quality or constraints may cause the project leader to decide to change ....

....application, depending on the characteristics of the software system to be developed or on software engineer s judgement. 4 All these considerations reveal the need to integrate project management and process management [8] 9] This integration seems to be ignored in most current research [10][4]. This work provides the techniques for planning, coordinating and scheduling the activities to attain and maintain a feasible schedule that meets the deadline requirements, in an uncertain environment where the sets of their properties are always changing. The techniques are based on controlling ....

H.D. Rombach and M. Verlage, "Directions in Software Process Research", Advances in Computers, Vol. 41, Academic Press, 1995.

.... approach is that each developer understand the processes gradually and in a personal fashion, and the processes can be badly executed if their understanding is not complete 2 [9, 10] Many authors maintain that the formalization of the processes can be a useful support to their understanding [3, 4, 6]. In this paper, the authors want to investigate if it can be more effective to leave the developers free to define their own development processes rather than to use a predefined process. The developers have to take into account some constraints when defining their processes so that these can ....

H. D. Rombach and M. Verlage, Directions in Software Process Research, Advances in Computers, Vol. 41, 1995, Academic Press

....2a: McCall s Quality Factors 2b: Adrion s Quality Factors 5 in an explicit, reusable form. This requires an organisational setup for both building explicit models of software engineering with respect to their business demands, and using such models effectively in future, similar projects [Rombach95]. 1.3 Measurement and Modelling Measurement is fundamental to any engineering discipline. The process of assigning abstract numerical representations to both process quantities and product qualities, and their interaction, gives three benefits: Control: our desire to measure the process is ....

....It is therefore generally accepted that no single modelling technique can capture the intricacy of the complex software process. Hence, some recent research effort has been focused on evaluation and integration of process modelling techniques, like that by McChesney [McChesney95] Rombach [Rombach95] has performed a comprehensive review of current research and future research directions in process modelling, finding that despite the large number of different representations few have empirical evidence of successful application representing the relative immaturity of the discipline. As Rombach ....

[Article contains additional citation context not shown here]

H. D. Rombach and M. Verlage, "Directions in Software Process Research," Advances in Computers, no. 41, Academic Press,1995. 44

.... it will provide a solid base for management decision making (e.g. planning, resource allocation, and monitoring) This paper describes the INRECA 1 methodology approach which is based on two relatively new areas in software engineering (SE) experience factory [2] and software process modeling [6]. We developed a methodology based on recent SE techniques which is enriched by up to date experience on building and maintaining CBR applications. This CBR experience was identified by analyzing several successful industrial applications developed by the industrial partners of the INRECA II 1 ....

....Characterize, Set Goals, Choose Process Execute Process Project Support Analyse Experience Base execution plans Lessons Learned Experience in Models Project Organisation Experience Factory Fig. 1. The Experience Factory Approach [2] 2. 2 Software Process Models Software process modeling [6] is an approach that is highly important in the context of the experience factory approach. Software process models describe the engineering of a product, e.g. the software that has to be produced. Unlike early approaches in SE, the software development is not considered to follow a single fixed ....

Rombach & Verlage (1995). Directions in Software Process Research. Advances in Computers, Vol. 41, Academic Press.

....factor for better process support. Process support includes improved communication, detailed reasoning about process features, guiding people when performing processes, improving both processes itself and their results, and automating process steps in order to gain deterministic process behavior [9, 26]. These purposes require explicit process representations (i.e. models) The variety of existing process support systems, for example process sensitive software engineering environments or workflow management systems, corresponds to the variety of process types. In this paper we focus on ....

....the project lifetime. AM7: Planning provides parameters which adapt process models to different contexts. AM8: Plan deviations are not considered. No support for modifying the project s state is provided. Several other approaches for supporting software development processes have been developed [1, 9, 26]. In general, we can distinguish between languages for modeling fine grain processes (i.e. used to integrate tools, hence being similar to programming languages) and coarse grain processes (i.e. used to guide software developers and to coordinate their tasks, hence being similar to specification ....

[Article contains additional citation context not shown here]

H. Dieter Rombach and Martin Verlage. Directions in software process research. In Marvin V. Zelkowitz, editor, Advances in Computers, vol. 41, pages 1--63. Academic Press, 1995.

....accesses 9 products and 10 resources. The purpose of the overall context of modeling (e.g. a measurement activity) has a strong impact on what aspects are highlighted in the model. Analysis of dynamic aspects, for example, stresses the constructs used to describe the behavior of the processes [RV95]. In projects A and C that focused on improvement nearly all concepts of MVP L were used, whereas in project B only processes, products, aggregation hierarchies, and product flow was modeled because the models were used for communication purposes. Dynamic aspects were not considered in project B, ....

H. Dieter Rombach and Martin Verlage. Directions in software process research. In Marvin V. Zelkowitz, editor, Advances in Computers, vol. 41, pages 1--63. Academic Press, 1995.

.... we needed a new language with more emphasis on our requirements regarding natural modeling (R 1) explicit formal interface representation (R 3) process instrumentation (R 4) and flexible modularization (R 7) A more detailed discussion of several approaches for process modeling can be found in [30]. A schema for evaluating a language from a personal point of view is presented in [29] 8 4 Introduction to the Process Modeling Language MVP L We introduce the process modeling language MVP L in terms of its underlying philosophy, language definition, and language implementation. This ....

H. Dieter Rombach and Martin Verlage, "Directions in Software Process Research", in Marvin V. Zelkowitz (Ed.), Advances in Computers, Vol. 41, Academic Press, Boston, MA, 1995.

No context found.

H. D. Rombach and M. Verlage, `Directions in software process research ', in Advances in Computers, volume 41, (1995).

No context found.

Rombach, H. D. and Verlage, M. Directions in Software Process Research, Advances in Computers, vol. 41, 1995. 286

No context found.

H.D. Rombach and M. Verlage, Directions in Software Process Research. Advances in Computers 41, 1995, pp. 1--63.

No context found.

Martin Verlage and H. Dieter Rombach. Directions in Software Process Research. Advances in Computers, 41:1--61, 1995.

No context found.

H. D. Rombach and M. Verlage. Directions in Software Process Research. In Advances in Computers, volume 41, 1995.

No context found.

H.D. Rombach and M. Verlage. Directions in software process research. Advances in Computers, 41:2--63, 1995.

No context found.

H.D. Rombach, M. Verlage, Directions in Software Process Research, Advances in Computers , Vol 41, Academic Press, Boston.

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