Pub Date : 1996-06-17DOI: 10.1109/ISPW.1996.654386
M. Verlage
The goal of software process model reuse should be to provide a comprehensive process model that guides and coordinates all roles within a project. This means that roles do not use their own process model, but all roles use a single, integrated one that represents all needed information. Views are derived to present information necessary for performing a role's tasks. Because every project is unique, reuse of software process models requires tailoring. Reusing generic, large software process models seems to be impractical, because of many interdependencies between generic parts of the model. Process engineering will only be successful when techniques are developed to formulate units of software process modules (staying relatively stable from project to project), to tailor them according to new contexts, and to integrate them into a comprehensive software process model. The hypothesis of this paper is that views are the process modules to be reused. Views are less complex and easier to maintain than a comprehensive process model.
{"title":"Towards software process modules","authors":"M. Verlage","doi":"10.1109/ISPW.1996.654386","DOIUrl":"https://doi.org/10.1109/ISPW.1996.654386","url":null,"abstract":"The goal of software process model reuse should be to provide a comprehensive process model that guides and coordinates all roles within a project. This means that roles do not use their own process model, but all roles use a single, integrated one that represents all needed information. Views are derived to present information necessary for performing a role's tasks. Because every project is unique, reuse of software process models requires tailoring. Reusing generic, large software process models seems to be impractical, because of many interdependencies between generic parts of the model. Process engineering will only be successful when techniques are developed to formulate units of software process modules (staying relatively stable from project to project), to tailor them according to new contexts, and to integrate them into a comprehensive software process model. The hypothesis of this paper is that views are the process modules to be reused. Views are less complex and easier to maintain than a comprehensive process model.","PeriodicalId":126787,"journal":{"name":"Proceedings 10th International Software Process Workshop","volume":"95 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1996-06-17","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125542242","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1996-06-17DOI: 10.1109/ISPW.1996.654356
M. Kellner
The paper focuses on one particular topic within the realm of software process reuse: namely, the issue of connections among reusable software process elements and components. Such connections can be problematic even in cases where human ingenuity and understanding is counted on entirely to smooth out the connection details while performing the process. However, the difficulties become more severe in cases involving process technology, such as formal representation of processes in a process modeling language, automated analysis and simulation of processes, and automated execution support for processes (aka process-centered environments). The paper addresses the connection issues that arise across all of these cases, particularly including the challenges that process reuse pose to process technology.
{"title":"Connecting reusable software process elements and components","authors":"M. Kellner","doi":"10.1109/ISPW.1996.654356","DOIUrl":"https://doi.org/10.1109/ISPW.1996.654356","url":null,"abstract":"The paper focuses on one particular topic within the realm of software process reuse: namely, the issue of connections among reusable software process elements and components. Such connections can be problematic even in cases where human ingenuity and understanding is counted on entirely to smooth out the connection details while performing the process. However, the difficulties become more severe in cases involving process technology, such as formal representation of processes in a process modeling language, automated analysis and simulation of processes, and automated execution support for processes (aka process-centered environments). The paper addresses the connection issues that arise across all of these cases, particularly including the challenges that process reuse pose to process technology.","PeriodicalId":126787,"journal":{"name":"Proceedings 10th International Software Process Workshop","volume":"29 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1996-06-17","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"130224303","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1996-06-17DOI: 10.1109/ISPW.1996.654383
M. Lehman
1970s studies of the evolution of OS/360 and other software systems suggested that E-type software development processes display feedback system like behaviour, develop a controlling dynamics and are subject to a number of laws termed laws of program evolution. Following the 1994 formulation of a FEAST hypothesis that, inter alia, encapsulates these observations, further studies are now underway. These are re-examining the feedback phenomenon and seeking ways to exploit it so as to improve the process of software process improvement. This paper outlines these themes, summarises some preliminary results and introduces a two year funded project FEAST/1 that, in collaboration with industry, will pursue the matter further. FEAST/1 is seen as laying the foundations for a longer term interdisciplinary study which, if the FEAST hypothesis is valid, should have a significant impact on the industrial process of software development while also providing foundations for a theory of software process and software product evolution.
{"title":"Feedback, evolution and software technology","authors":"M. Lehman","doi":"10.1109/ISPW.1996.654383","DOIUrl":"https://doi.org/10.1109/ISPW.1996.654383","url":null,"abstract":"1970s studies of the evolution of OS/360 and other software systems suggested that E-type software development processes display feedback system like behaviour, develop a controlling dynamics and are subject to a number of laws termed laws of program evolution. Following the 1994 formulation of a FEAST hypothesis that, inter alia, encapsulates these observations, further studies are now underway. These are re-examining the feedback phenomenon and seeking ways to exploit it so as to improve the process of software process improvement. This paper outlines these themes, summarises some preliminary results and introduces a two year funded project FEAST/1 that, in collaboration with industry, will pursue the matter further. FEAST/1 is seen as laying the foundations for a longer term interdisciplinary study which, if the FEAST hypothesis is valid, should have a significant impact on the industrial process of software development while also providing foundations for a theory of software process and software product evolution.","PeriodicalId":126787,"journal":{"name":"Proceedings 10th International Software Process Workshop","volume":"31 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1996-06-17","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129193058","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1996-06-17DOI: 10.1109/ISPW.1996.654369
S. Doublait, Cristina Lissoni
This paper presents a best practice of software reuse, achieved through adoption of specifically-designed engineering and management processes at Sodalia. Our company is a software development joint venture between Bell Atlantic and Telecom Italia which has embraced systematic reuse as a key strategic imperative to reach its objectives of high-quality, rapidly deployed telecommunications software applications. We describe the various processes that have been defined and applied in the context of our corporate reuse program, and summarize results from their adoption. Our experience has shown that the existence of carefully designed processes combined with a sound organizational structure are major enablers for making reuse a systematic practice in an organization.
{"title":"Processes for systematic software reuse","authors":"S. Doublait, Cristina Lissoni","doi":"10.1109/ISPW.1996.654369","DOIUrl":"https://doi.org/10.1109/ISPW.1996.654369","url":null,"abstract":"This paper presents a best practice of software reuse, achieved through adoption of specifically-designed engineering and management processes at Sodalia. Our company is a software development joint venture between Bell Atlantic and Telecom Italia which has embraced systematic reuse as a key strategic imperative to reach its objectives of high-quality, rapidly deployed telecommunications software applications. We describe the various processes that have been defined and applied in the context of our corporate reuse program, and summarize results from their adoption. Our experience has shown that the existence of carefully designed processes combined with a sound organizational structure are major enablers for making reuse a systematic practice in an organization.","PeriodicalId":126787,"journal":{"name":"Proceedings 10th International Software Process Workshop","volume":"261 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1996-06-17","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122087124","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1996-06-17DOI: 10.1109/ISPW.1996.654387
L. Votta, M. Zajac
Fundamental to any attempt of process reuse, the enacting organization needs to have the ability to adapt and modify itself to effectively use the recycled process elements. We examine the underlying feedback mechanism that is needed to drive and tune the organizational adaptation. We illustrate this adaptation using a process improvement case study of the 5ESS design process and the FEAST model for feedback in software development organizations. We found that it is crucial to understand the lag time between the time when the control signal is sampled and reapplied back to the design process. We discuss the 5ESS organizational setting, the FEAST feedback model, and the major observations from applying the model to the design improvement case study. We finish with a set of discussion points that illustrate important issues for any model of organizational feedback, and hence, important issues for process reuse.
{"title":"Using process waiver data to improve a design process: a case study of feedback and control using the FEAST model","authors":"L. Votta, M. Zajac","doi":"10.1109/ISPW.1996.654387","DOIUrl":"https://doi.org/10.1109/ISPW.1996.654387","url":null,"abstract":"Fundamental to any attempt of process reuse, the enacting organization needs to have the ability to adapt and modify itself to effectively use the recycled process elements. We examine the underlying feedback mechanism that is needed to drive and tune the organizational adaptation. We illustrate this adaptation using a process improvement case study of the 5ESS design process and the FEAST model for feedback in software development organizations. We found that it is crucial to understand the lag time between the time when the control signal is sampled and reapplied back to the design process. We discuss the 5ESS organizational setting, the FEAST feedback model, and the major observations from applying the model to the design improvement case study. We finish with a set of discussion points that illustrate important issues for any model of organizational feedback, and hence, important issues for process reuse.","PeriodicalId":126787,"journal":{"name":"Proceedings 10th International Software Process Workshop","volume":"78 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1996-06-17","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"128395914","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1996-06-17DOI: 10.1109/ISPW.1996.654362
R. Balzer
The author considers how the maturation of the software development field has been inextricably tied to its adoption of a product line orientation. Only by specializing in a particular application domain can software development organizations develop the expertise required for that domain, develop cost effective products, and establish a market niche. He argues that software development processes are fundamentally flawed because maintenance, including enhancement and evolution, is performed on source code. This source code has been hand optimized by programmers and that optimization has spread information and built up implicit dependencies among the parts.
{"title":"Supporting product line development","authors":"R. Balzer","doi":"10.1109/ISPW.1996.654362","DOIUrl":"https://doi.org/10.1109/ISPW.1996.654362","url":null,"abstract":"The author considers how the maturation of the software development field has been inextricably tied to its adoption of a product line orientation. Only by specializing in a particular application domain can software development organizations develop the expertise required for that domain, develop cost effective products, and establish a market niche. He argues that software development processes are fundamentally flawed because maintenance, including enhancement and evolution, is performed on source code. This source code has been hand optimized by programmers and that optimization has spread information and built up implicit dependencies among the parts.","PeriodicalId":126787,"journal":{"name":"Proceedings 10th International Software Process Workshop","volume":"32 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1996-06-17","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127214838","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1996-06-17DOI: 10.1109/ISPW.1996.654381
G. Kaiser, P. D. Skopp, J. Yang, G. Heineman
We present our experience using process-centered environments to build, maintain, reengineer and develop sets of related products. A process-centered environment is itself a collection of applications, such as clients and servers, that work together to provide a set of services. We discuss the OzMarvel and EmeraldCity environments that we designed to develop the Oz process-centered environment. Oz's support for process interoperability played a key role in constructing a component-based product line process.
{"title":"On the yellow brick road to component-based product lines","authors":"G. Kaiser, P. D. Skopp, J. Yang, G. Heineman","doi":"10.1109/ISPW.1996.654381","DOIUrl":"https://doi.org/10.1109/ISPW.1996.654381","url":null,"abstract":"We present our experience using process-centered environments to build, maintain, reengineer and develop sets of related products. A process-centered environment is itself a collection of applications, such as clients and servers, that work together to provide a set of services. We discuss the OzMarvel and EmeraldCity environments that we designed to develop the Oz process-centered environment. Oz's support for process interoperability played a key role in constructing a component-based product line process.","PeriodicalId":126787,"journal":{"name":"Proceedings 10th International Software Process Workshop","volume":"84 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1996-06-17","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129128153","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1996-06-17DOI: 10.1109/ISPW.1996.654384
Nancy A. Staudenmayer
Software firms, like producers in any industry, face a spectrum of product and process choices. Historically, however, this continuum has been anchored by two contrasting approaches to software development, and these paradigms continue to dominate literature and practice today: the hacker versus a more discipline-based approach. As application type software products have become larger and more complex, former practitioners of the hacker approach have had to impose more discipline and structure on their development process. Likewise, discipline-based firms are having to learn to work more flexibly in the face of increasingly volatile competition and reduced cycle times. This paper addresses the managerial challenges presented by these converging models. Can firms overcome their legacy as either a hacker or disciplinarian without sacrificing the advantages associated with their old approach?.
{"title":"Moving away from a hacker vs. disciplined-based organizational legacy-an organization theory perspective on software processes","authors":"Nancy A. Staudenmayer","doi":"10.1109/ISPW.1996.654384","DOIUrl":"https://doi.org/10.1109/ISPW.1996.654384","url":null,"abstract":"Software firms, like producers in any industry, face a spectrum of product and process choices. Historically, however, this continuum has been anchored by two contrasting approaches to software development, and these paradigms continue to dominate literature and practice today: the hacker versus a more discipline-based approach. As application type software products have become larger and more complex, former practitioners of the hacker approach have had to impose more discipline and structure on their development process. Likewise, discipline-based firms are having to learn to work more flexibly in the face of increasingly volatile competition and reduced cycle times. This paper addresses the managerial challenges presented by these converging models. Can firms overcome their legacy as either a hacker or disciplinarian without sacrificing the advantages associated with their old approach?.","PeriodicalId":126787,"journal":{"name":"Proceedings 10th International Software Process Workshop","volume":"40 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1996-06-17","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"130398689","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1996-06-17DOI: 10.1109/ISPW.1996.654354
B. Boehm, Steven Wolf
The development and reuse of software engineering processes within an organization can be impeded by the lack of a solid process framework. An open process architecture provides a framework through the identification of architectural elements and the specification of element interfaces. This paper introduces one open process architecture and examines some architectural element interfaces.
{"title":"An open architecture for software process asset reuse","authors":"B. Boehm, Steven Wolf","doi":"10.1109/ISPW.1996.654354","DOIUrl":"https://doi.org/10.1109/ISPW.1996.654354","url":null,"abstract":"The development and reuse of software engineering processes within an organization can be impeded by the lack of a solid process framework. An open process architecture provides a framework through the identification of architectural elements and the specification of element interfaces. This paper introduces one open process architecture and examines some architectural element interfaces.","PeriodicalId":126787,"journal":{"name":"Proceedings 10th International Software Process Workshop","volume":"38 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1996-06-17","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"121985178","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1996-06-17DOI: 10.1109/ISPW.1996.654372
Robert Mark Greenwood, P. Kawalek, I. Robertson, B. Warboys
There are issues of concern to software engineers that cannot be addressed in the context of a single development project. This paper indicates some typical issues, and proposes an asset view of the software development process to enable them to be considered. The asset view places less emphasis on the temporal ordering of activities and more on the concepts of goals, interactions, learning and evolution. It is complementary to the more conventional production view. The asset view may be a better starting point for considerations of reuse and product lines.
{"title":"An asset view on the software process","authors":"Robert Mark Greenwood, P. Kawalek, I. Robertson, B. Warboys","doi":"10.1109/ISPW.1996.654372","DOIUrl":"https://doi.org/10.1109/ISPW.1996.654372","url":null,"abstract":"There are issues of concern to software engineers that cannot be addressed in the context of a single development project. This paper indicates some typical issues, and proposes an asset view of the software development process to enable them to be considered. The asset view places less emphasis on the temporal ordering of activities and more on the concepts of goals, interactions, learning and evolution. It is complementary to the more conventional production view. The asset view may be a better starting point for considerations of reuse and product lines.","PeriodicalId":126787,"journal":{"name":"Proceedings 10th International Software Process Workshop","volume":"99 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1996-06-17","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122028688","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
京公网安备 11010802042870号
京ICP备2023020795号-1
扫码关注我们
求助内容：
应助结果提醒方式：