Pub Date : 1996-06-17DOI: 10.1109/ISPW.1996.654358
W. Schafer
Software process technology as well as software configuration management (SCM) has focussed very much on supporting the development and evolution of a single software product rather than software product-lines. In the case of SCM this is particular harmful, because current SCM technology only provides very limited support to adjust a tool supporting SCM to the particular needs and requirements of a company producing product-line software. Usually such a tool has a built-in process and to the most provides a shell-script like language to define certain responsibilities or development status attributes for the artifacts produced during development and maintenance. There is virtually no support to adjust a tool to e.g. the definition of special workflows for change management and notification.
{"title":"Product-line development requires sophisticated software configuration management","authors":"W. Schafer","doi":"10.1109/ISPW.1996.654358","DOIUrl":"https://doi.org/10.1109/ISPW.1996.654358","url":null,"abstract":"Software process technology as well as software configuration management (SCM) has focussed very much on supporting the development and evolution of a single software product rather than software product-lines. In the case of SCM this is particular harmful, because current SCM technology only provides very limited support to adjust a tool supporting SCM to the particular needs and requirements of a company producing product-line software. Usually such a tool has a built-in process and to the most provides a shell-script like language to define certain responsibilities or development status attributes for the artifacts produced during development and maintenance. There is virtually no support to adjust a tool to e.g. the definition of special workflows for change management and notification.","PeriodicalId":126787,"journal":{"name":"Proceedings 10th International Software Process Workshop","volume":"53 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":"122189342","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.654382
C. Klingler, R. Creps
We have formulated an integrated set of concepts, processes, methods and tools, called ReuseWorks, which supports the product line approach to software development. ReuseWorks is generic and tailorable and has been validated through usage on the Army STARS Demonstration Project.
{"title":"Integrating and applying processes and methods for product line management","authors":"C. Klingler, R. Creps","doi":"10.1109/ISPW.1996.654382","DOIUrl":"https://doi.org/10.1109/ISPW.1996.654382","url":null,"abstract":"We have formulated an integrated set of concepts, processes, methods and tools, called ReuseWorks, which supports the product line approach to software development. ReuseWorks is generic and tailorable and has been validated through usage on the Army STARS Demonstration Project.","PeriodicalId":126787,"journal":{"name":"Proceedings 10th International Software Process Workshop","volume":"19 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":"121848078","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.654370
E. Ellmer, D. Merkl
We believe that the efficiency and productivity of software development processes can be dramatically increased by making the knowledge gained during past projects persistent and thus reusable for future projects. We plead for the establishment of a computer supported organizational memory for software development organizations. Furthermore, we feel that the accelerated growth of software process modeling techniques provides a convenient equipment for the realization of what we propose. A process model is an explicit representation of process knowledge and may thus serve as a means for storing and retrieving organizational knowledge about software process execution. Thus, we argue for reusing software process models. An organizational memory for software development organizations may be implemented by populating and structuring a process model library and providing mechanisms for retrieving and tailoring process models in order to apply them during the execution (management) of projects.
{"title":"Considerations for an organizational memory in software development","authors":"E. Ellmer, D. Merkl","doi":"10.1109/ISPW.1996.654370","DOIUrl":"https://doi.org/10.1109/ISPW.1996.654370","url":null,"abstract":"We believe that the efficiency and productivity of software development processes can be dramatically increased by making the knowledge gained during past projects persistent and thus reusable for future projects. We plead for the establishment of a computer supported organizational memory for software development organizations. Furthermore, we feel that the accelerated growth of software process modeling techniques provides a convenient equipment for the realization of what we propose. A process model is an explicit representation of process knowledge and may thus serve as a means for storing and retrieving organizational knowledge about software process execution. Thus, we argue for reusing software process models. An organizational memory for software development organizations may be implemented by populating and structuring a process model library and providing mechanisms for retrieving and tailoring process models in order to apply them during the execution (management) of projects.","PeriodicalId":126787,"journal":{"name":"Proceedings 10th International Software Process Workshop","volume":"17 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":"121341170","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.654371
J. Estublier, S. Dami
Process model reuse has become a hot topic in the process community. As far as we are concerned, reuse has found its origin within the practical framework of software quality improvement we are involved in as participants of the PERFECT project. The objective of this project is to define a conceptual approach (PERFECT Improvement Approach), in which process improvement is justified as a means towards product improvement, and is implemented through the concepts of goal-oriented measurement, learning, packaging of explicit experience and reuse. Reuse is therefore a main concern that must be made explicit and well formalized for all of the process aspects, i.e., product, activity, role and measurement aspects. While reuse of product, role and measurement models did not cause us much trouble (owing to the object-orientation of their representation), reusing activities has been rather problematic. The work reported in this paper emphasizes the main issues we encountered in our experience facing the problem of process reuse. Our experience has been acquired through the design, implementation and evaluation of two major versions of the APEL tool; a textual and graphical language for describing and enacting process models.
{"title":"About reuse in multi-paradigm process modelling approach","authors":"J. Estublier, S. Dami","doi":"10.1109/ISPW.1996.654371","DOIUrl":"https://doi.org/10.1109/ISPW.1996.654371","url":null,"abstract":"Process model reuse has become a hot topic in the process community. As far as we are concerned, reuse has found its origin within the practical framework of software quality improvement we are involved in as participants of the PERFECT project. The objective of this project is to define a conceptual approach (PERFECT Improvement Approach), in which process improvement is justified as a means towards product improvement, and is implemented through the concepts of goal-oriented measurement, learning, packaging of explicit experience and reuse. Reuse is therefore a main concern that must be made explicit and well formalized for all of the process aspects, i.e., product, activity, role and measurement aspects. While reuse of product, role and measurement models did not cause us much trouble (owing to the object-orientation of their representation), reusing activities has been rather problematic. The work reported in this paper emphasizes the main issues we encountered in our experience facing the problem of process reuse. Our experience has been acquired through the design, implementation and evaluation of two major versions of the APEL tool; a textual and graphical language for describing and enacting process models.","PeriodicalId":126787,"journal":{"name":"Proceedings 10th International Software Process Workshop","volume":"57 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":"132066562","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.654367
G. Cugola, C. Ghezzi
We address the workshop theme by discussing some issues concerning process support for product families. In particular, we discuss how the particular problem of supporting product family developments affects the notation used for process representation and enactment. Based on our current understanding of the problem, our conclusion is that the development of program families does not introduce new requirements, but stress some of the requirements that are intrinsic to most software processes to their extreme. That is, they do not demand new language mechanisms, but require specific processes to be put in place.
{"title":"Program families: some requirements issues for the process languages","authors":"G. Cugola, C. Ghezzi","doi":"10.1109/ISPW.1996.654367","DOIUrl":"https://doi.org/10.1109/ISPW.1996.654367","url":null,"abstract":"We address the workshop theme by discussing some issues concerning process support for product families. In particular, we discuss how the particular problem of supporting product family developments affects the notation used for process representation and enactment. Based on our current understanding of the problem, our conclusion is that the development of program families does not introduce new requirements, but stress some of the requirements that are intrinsic to most software processes to their extreme. That is, they do not demand new language mechanisms, but require specific processes to be put in place.","PeriodicalId":126787,"journal":{"name":"Proceedings 10th International Software Process Workshop","volume":"6 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":"125676871","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.654357
D. Perry
The author discusses two rather different approaches to process reuse: the first is the use of generic processes, and the second is the use of requirements for best in class processes. The first approach aims at providing a generalized approach that allows for as much commonality across projects while supporting the necessary customization and tailoring for each individual project. The second approach is one that is perhaps more realistic for company-wide process reuse where the differences between projects may be too great to be accommodated by generic processes.
{"title":"Practical issues in process reuse","authors":"D. Perry","doi":"10.1109/ISPW.1996.654357","DOIUrl":"https://doi.org/10.1109/ISPW.1996.654357","url":null,"abstract":"The author discusses two rather different approaches to process reuse: the first is the use of generic processes, and the second is the use of requirements for best in class processes. The first approach aims at providing a generalized approach that allows for as much commonality across projects while supporting the necessary customization and tailoring for each individual project. The second approach is one that is perhaps more realistic for company-wide process reuse where the differences between projects may be too great to be accommodated by generic processes.","PeriodicalId":126787,"journal":{"name":"Proceedings 10th International Software Process Workshop","volume":"33 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":"123707066","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.654375
R. Hitchings, Miguel Ángel Martínez
This paper provides a summary of our experience, from the perspective of process reuse, in building a new division from the ground up. In the course of building a new organization, we were faced with many choices in the reuse of process elements available from our larger parent organization. First, we give an overview of our organization to provide the context of our software development effort: large, complex and dynamic. Next, we explore our motivations for reuse. We see two primary reasons for and benefits of reuse in our business environment. To support this reasoning, we examine what we are doing today by identifying what works and what does not work in the context of some real examples. We summarize the lessons learned from the examination of our experiences to date and analyze these in the context of what we believe to be the underlying barriers and the actions we believe will enable us to overcome the barriers. Last, we assert our view of the future. In this future, we examine what is required to support our original motivation for reuse and raise some questions that need to be answered to create the future we envision. The intent of the questions is to generate a starting point for further research.
{"title":"Reuse of process elements-one company's experience","authors":"R. Hitchings, Miguel Ángel Martínez","doi":"10.1109/ISPW.1996.654375","DOIUrl":"https://doi.org/10.1109/ISPW.1996.654375","url":null,"abstract":"This paper provides a summary of our experience, from the perspective of process reuse, in building a new division from the ground up. In the course of building a new organization, we were faced with many choices in the reuse of process elements available from our larger parent organization. First, we give an overview of our organization to provide the context of our software development effort: large, complex and dynamic. Next, we explore our motivations for reuse. We see two primary reasons for and benefits of reuse in our business environment. To support this reasoning, we examine what we are doing today by identifying what works and what does not work in the context of some real examples. We summarize the lessons learned from the examination of our experiences to date and analyze these in the context of what we believe to be the underlying barriers and the actions we believe will enable us to overcome the barriers. Last, we assert our view of the future. In this future, we examine what is required to support our original motivation for reuse and raise some questions that need to be answered to create the future we envision. The intent of the questions is to generate a starting point for further research.","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":"126809141","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.654380
Badara Ali Kaba, J. Derniame
Online product families and their development processes are reusable and evolutive when they are fragmented enough. These fragments are useful if they are meaningfully interconnected. In a cooperative development process, the process entities are regularly updated from several locations. Moreover, the fragments can be differently interpreted, depending on the usage context and the adopted point of view. This paper addresses the access and transient update mechanisms for a family of configurable and evolutionary process fragments.
{"title":"Evolution of on-line process fragments families","authors":"Badara Ali Kaba, J. Derniame","doi":"10.1109/ISPW.1996.654380","DOIUrl":"https://doi.org/10.1109/ISPW.1996.654380","url":null,"abstract":"Online product families and their development processes are reusable and evolutive when they are fragmented enough. These fragments are useful if they are meaningfully interconnected. In a cooperative development process, the process entities are regularly updated from several locations. Moreover, the fragments can be differently interpreted, depending on the usage context and the adopted point of view. This paper addresses the access and transient update mechanisms for a family of configurable and evolutionary process fragments.","PeriodicalId":126787,"journal":{"name":"Proceedings 10th International Software Process Workshop","volume":"121 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":"132561512","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.654361
D. Avrilionis, P. Cunin
Despite the efforts to devise enactable process modelling languages that are "non-technical" and very readable, the definition of enactable software process models still involves large amounts of detail and requires programming skills. Efforts to design new process modelling languages and tools will help to bring down the costs for process model development. However we believe that only a highly reuse based approach to software process engineering can provide the results that are needed. We rely on the taxonomy for software reuse techniques introduced by W. Krueger (1992) and we examine the differences/specificities which arise when applying these techniques to the software process model reuse domain. We illustrate this taxonomy using the reuse oriented features of the Opsis environment (D. Avrilionis et al., 1992).
尽管人们努力设计“非技术”且可读性很强的可制定过程建模语言，但可制定软件过程模型的定义仍然涉及大量细节并需要编程技能。设计新的流程建模语言和工具的努力将有助于降低流程模型开发的成本。然而，我们相信只有基于高度重用的软件过程工程方法才能提供所需的结果。我们依赖于W. Krueger(1992)介绍的软件重用技术的分类法，并检查在将这些技术应用于软件过程模型重用领域时产生的差异/特殊性。我们使用Opsis环境的面向重用的特性来说明这种分类法(D. Avrilionis et al.， 1992)。
{"title":"Process model reuse support-the OPSIS approach","authors":"D. Avrilionis, P. Cunin","doi":"10.1109/ISPW.1996.654361","DOIUrl":"https://doi.org/10.1109/ISPW.1996.654361","url":null,"abstract":"Despite the efforts to devise enactable process modelling languages that are \"non-technical\" and very readable, the definition of enactable software process models still involves large amounts of detail and requires programming skills. Efforts to design new process modelling languages and tools will help to bring down the costs for process model development. However we believe that only a highly reuse based approach to software process engineering can provide the results that are needed. We rely on the taxonomy for software reuse techniques introduced by W. Krueger (1992) and we examine the differences/specificities which arise when applying these techniques to the software process model reuse domain. We illustrate this taxonomy using the reuse oriented features of the Opsis environment (D. Avrilionis et al., 1992).","PeriodicalId":126787,"journal":{"name":"Proceedings 10th International Software Process Workshop","volume":"65 4 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":"130808335","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.654385
S. Sutton, L. Osterweil
Product lines or families represent an important way of organizing software products. Product families might include, for example, successive revisions of a single application, versions of an application for different host platforms, or versions with varying features, e.g., different levels of security. A software product family can thus be viewed as a collection of products that are similar in some important respects yet systematically different in others. The family viewpoint emphasizes both the commonality among family members and the differences between them, and it draws attention to their interrelationships. Our work in software processes has lead us to conclude that software processes also can be usefully viewed in terms of families. As software process engineers, we also naturally view products in terms of the processes that create them and, conversely, we view processes in terms of the products they create. This suggests that product families and process families should be closely interrelated. Consequently, both products and processes may benefit from analysis in terms of families and family relationships. We begin to sketch out such an analysis and some of the issues that it raises.
{"title":"Product families and process families","authors":"S. Sutton, L. Osterweil","doi":"10.1109/ISPW.1996.654385","DOIUrl":"https://doi.org/10.1109/ISPW.1996.654385","url":null,"abstract":"Product lines or families represent an important way of organizing software products. Product families might include, for example, successive revisions of a single application, versions of an application for different host platforms, or versions with varying features, e.g., different levels of security. A software product family can thus be viewed as a collection of products that are similar in some important respects yet systematically different in others. The family viewpoint emphasizes both the commonality among family members and the differences between them, and it draws attention to their interrelationships. Our work in software processes has lead us to conclude that software processes also can be usefully viewed in terms of families. As software process engineers, we also naturally view products in terms of the processes that create them and, conversely, we view processes in terms of the products they create. This suggests that product families and process families should be closely interrelated. Consequently, both products and processes may benefit from analysis in terms of families and family relationships. We begin to sketch out such an analysis and some of the issues that it raises.","PeriodicalId":126787,"journal":{"name":"Proceedings 10th International Software Process Workshop","volume":"19 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":"131016675","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
扫码关注我们
求助内容：
应助结果提醒方式：