Fuggetta, A. 2000. Software Process: A Roadmap. ACM Press. chapter The Future of Software Engineering.  Home/Search   Document Details and Download   Summary   Related Articles   Check

.... field of Process centered Software Engineering Environments (PSEE) ACF98, GPS99] A key advantage of using a WfMS, instead of a PSEE, is a wider domain of applicability, which allows for different aspects of a software organization, and not only software processes, to be modelled in a uniform way [Fug00]. Additional advantages are a reduced complexity and intrusiveness. In this respect, workflow management systems seem to be more flexible, as they may provide software project managers and the other actors involved in the process with a certain level of freedom to both decide the detail about the ....

A. Fuggetta, "Software Process: A Roadmap", The Future of Software Engineering, A. Finkelstein, Editor, ACM Press, 2000, pp. 25-34.

....roles and responsibilities at global level as well as for organizing the activities that will be executed at a local site for a specific subprocess. r Inter site coordination based on Events and Software Agents. These guidelines perfectly match with the research directions suggested in [17], concerning the main characteristics of future process modelling languages. 2.1. The Industrial Partners The GENESIS project includes two industrial partners, namely LogicDIS from Greece and SchlumblegerSema from Spain. Both industrial partners will execute two different test beds in order to ....

A. Fuggetta. Software process: a roadmap. In Proceedings of the conference on The future of Software engineering, pages 25--34. ACM Press, 2000.

....a convenient way. This is only possible for textual files, e.g. source code. PSDEs can facilitate the handling of complex methods since tasks and conditions in the method definition are directly available in developers environments. Unfortunately, PSDEs are virtually in significant in practice [23]: The idea of regarding a software development process as an algorithm which takes a requirements specification and a set of developers as input and produces a runnable software system as its output has not prevailed. Reasons for this are the limited flexibility of systems, technical problems, and ....

A. Fuggetta. Software Process: A Roadmap. In Finkelstein [19], pages 25-34.

.... these tools will cooperate, to build a fully fledged, evolutive and efficient SE environment, is an active research topic (mega programming, COTS federations etc) This last issue, interoperability control, can become another area where SCM research and tools can contribute; further, as quoted in [28] several researchers believe that Configuration Management environments are the real process centered environments . Nevertheless, in the near future, provided the number of core topic issues yet to be solved and the efficiency, scalability and usability issues, no one of these evolutions will ....

A. Fuggetta. Software Process : A Roadmap. In this issue.

....Culture Centered Process, Multilevel Model, Engineering Level, Cultural Procedure, Behavioral Competencies. 1. INTRODUCTION A software process model should come out of the fecund interrelation between the socio cultural, scientific technological and paradigmatological environments [2, 8]. In this paper a culture centered multilevel software process cycle model (MPCM) is presented. This model considers cultural, social, organizational and personnel related issues, normally absent in the traditional software process models. The general aim of the software process research is ....

....not happen whit the organizational dimension of incipient development in the software process modeling. Although there has been a historical lack of relationships between the technological and organizational dimensions for the software process modeling, the situation is changing for a few years [1, 2, 3, 5, 8, 10]. This transition happened when there was an awareness of the importance the socio cultural environment has in the origin, development, application and evaluation of the high quality software products. In this article, we address the following subjects: a) how to model the organization and b) how ....

A. Fuggetta, "Software process: A roadmap". In The Future of Software Engineering, Ed. A. Finkelstein, (ACM Press, 2000) 27-34.

....be divided into several sub models expressing different viewpoints or perspectives. Additionally, there is a variety of notations for defining the process models as described in section 3.2. The results achieved so far in software process research are comprehensively reviewed in [4] and [21] and [30] presents an overall critical evaluation and possible directions for future research. 3. ELEMENTS AND APPROACHES OF SOFTWARE PROCESS MODELLING Firstly, we are going to deal with the basic process related elements, as well as their possible interrelationships. The different approaches to ....

....to identify the elements that represent the software process and, therefore, model the process in question. The prescriptive models considered are shown in Figure 2. Just two process definition standards were considered for manual models. The most important automated models were chosen [5] 45] 47][30]. These prescriptive models are characterised according to the above mentioned criteria in Table 1. If they meet a table characteristic, the respective table cell is marked with X, otherwise the space is left blank. In relation to the manual prescriptive models, the software life cycle process ....

A. Fuggetta, "Software process: A roadmap". In The Future of Software Engineering, Ed. A. Finkelstein, (ACM Press, 2000) 27-34.

.... area in reverse engineering and program understanding is software process [30] A software process can be defined as the coherent set of policies, organizational structures, technologies, procedures and artifacts that are needed to conceive, develop, deploy, and maintain a software product [20]. Software process involves technical, methodological, organizational and economic issues [20] 2.2. An XP Primer Extreme Programming (XP) is a light weight methodology for teams of approximately 10 people developing software in the face of vague or rapidly changing requirements [2] XP builds ....

.... process can be defined as the coherent set of policies, organizational structures, technologies, procedures and artifacts that are needed to conceive, develop, deploy, and maintain a software product [20] Software process involves technical, methodological, organizational and economic issues [20]. 2.2. An XP Primer Extreme Programming (XP) is a light weight methodology for teams of approximately 10 people developing software in the face of vague or rapidly changing requirements [2] XP builds upon various existing and common sense practices and principles, but applies these to extreme ....

A. Fuggetta. Software process: A roadmap. In A. Finkelstein, editor, The Future of Software Engineering. ACM Press, 2000.

No context found.

Fuggetta, A. 2000. Software Process: A Roadmap. ACM Press. chapter The Future of Software Engineering.

No context found.

Alfonso Fuggetta. Software process: a roadmap. In Proceedings of the conference on The future of Software engineering, pages 25--34. ACM Press, 2000.

No context found.

A. Fuggetta, "Software process: A roadmap". In The Future of Software Engineering, Ed. A. Finkelstein, (ACM Press, 2000) 27-34.

No context found.

A. Fuggetta, "Software Process: A Roadmap", In Anthony Finkelstein, ed. The future of Software Engineering. ACM Press, pp27-34, 2000.

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