Pub Date : 1994-10-10DOI: 10.1109/SPCON.1994.344414
M. Nguyen, R. Conradi
Identifies a taxonomy to characterize meta-process categories, and their characteristics. The taxonomy is applied to several existing software process-centered support environments (PSEs) and their support technologies. Up to now, meta-processes have been poorly understood, and thus hardly exploited properly. In some PSEs, meta-processes are supported, but their properties are not reflected clearly in any systematic framework. In this paper, some typical characteristics of meta-processes are recognized by clarifying: (i) the reasons why meta-processes are necessary for software development and maintenance; (ii) which effects they have on other components or fragments of a software process; (iii) how and when they should be accomplished; and (iv) who is responsible for performing them. These characteristics also contribute to recognizing the phases of meta-processes in software engineering. Identified characteristics and phases, serving as a framework for assessment, are then applied to evaluate five European PSEs, namely Adele2, EPOS, SPADE, Process Weaver and Process Wise Integrator. The intention of this evaluation is to illustrate the strengths and weaknesses of the identified PSE systems, providing a motivation for their further research and enhancement. In addition, it is also an initial step to validate and demonstrate the usefulness of this proposed assessment framework w.r.t. studying software meta-processes.<>
{"title":"Classification of meta-processes and their models","authors":"M. Nguyen, R. Conradi","doi":"10.1109/SPCON.1994.344414","DOIUrl":"https://doi.org/10.1109/SPCON.1994.344414","url":null,"abstract":"Identifies a taxonomy to characterize meta-process categories, and their characteristics. The taxonomy is applied to several existing software process-centered support environments (PSEs) and their support technologies. Up to now, meta-processes have been poorly understood, and thus hardly exploited properly. In some PSEs, meta-processes are supported, but their properties are not reflected clearly in any systematic framework. In this paper, some typical characteristics of meta-processes are recognized by clarifying: (i) the reasons why meta-processes are necessary for software development and maintenance; (ii) which effects they have on other components or fragments of a software process; (iii) how and when they should be accomplished; and (iv) who is responsible for performing them. These characteristics also contribute to recognizing the phases of meta-processes in software engineering. Identified characteristics and phases, serving as a framework for assessment, are then applied to evaluate five European PSEs, namely Adele2, EPOS, SPADE, Process Weaver and Process Wise Integrator. The intention of this evaluation is to illustrate the strengths and weaknesses of the identified PSE systems, providing a motivation for their further research and enhancement. In addition, it is also an initial step to validate and demonstrate the usefulness of this proposed assessment framework w.r.t. studying software meta-processes.<<ETX>>","PeriodicalId":163642,"journal":{"name":"Proceedings of the Third International Conference on the Software Process. Applying the Software Process","volume":"7 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1994-10-10","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"128505764","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 : 1994-10-10DOI: 10.1109/SPCON.1994.344424
M. Aoyama
This article reports on the first JSPS (Japanese Software Process Symposium) held on May 26-27, 1994 in Tokyo. Traditionally, process-oriented technologies, such as TQC and software factory, have been a part of culture embedded into Japanese software engineering. However, they are implicit and lack the "formal" approaches. The emergence of the software process concept such as process programming and ISO 9000-3 attracted the attentions of both academia and industry. Now, software process is one of the central topics of software engineering community in Japan. Just in time, the first JSPS was launched to present the current status of software process technologies to a large number of the researchers and practitioners and broaden the community.<>
{"title":"Report on the first Japanese Software Process Symposium","authors":"M. Aoyama","doi":"10.1109/SPCON.1994.344424","DOIUrl":"https://doi.org/10.1109/SPCON.1994.344424","url":null,"abstract":"This article reports on the first JSPS (Japanese Software Process Symposium) held on May 26-27, 1994 in Tokyo. Traditionally, process-oriented technologies, such as TQC and software factory, have been a part of culture embedded into Japanese software engineering. However, they are implicit and lack the \"formal\" approaches. The emergence of the software process concept such as process programming and ISO 9000-3 attracted the attentions of both academia and industry. Now, software process is one of the central topics of software engineering community in Japan. Just in time, the first JSPS was launched to present the current status of software process technologies to a large number of the researchers and practitioners and broaden the community.<<ETX>>","PeriodicalId":163642,"journal":{"name":"Proceedings of the Third International Conference on the Software Process. Applying the Software Process","volume":"10 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1994-10-10","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125308746","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 : 1994-10-10DOI: 10.1109/SPCON.1994.344412
S. Boyd
There are remarkable similarities in research and practice between the software process and business process communities. These similarities are remarkable, not as a result of the degree of similarity, and not as a result of the closeness of purpose motivating the two communities' efforts, but rather because of the significant differences in history, approach, form, mindset and context dividing the two groups. While the concept of a business process may appear more general from a logical viewpoint, at the moment software process engineering has the benefit of a longer history of general tool support and team-based interaction models. The software community has much to offer businesses as we move forward to more broadly positioned business process engineering systems, and of course, the general business community will bring with it a much wider market for ideas and products.<>
{"title":"Are software processes business processes too?","authors":"S. Boyd","doi":"10.1109/SPCON.1994.344412","DOIUrl":"https://doi.org/10.1109/SPCON.1994.344412","url":null,"abstract":"There are remarkable similarities in research and practice between the software process and business process communities. These similarities are remarkable, not as a result of the degree of similarity, and not as a result of the closeness of purpose motivating the two communities' efforts, but rather because of the significant differences in history, approach, form, mindset and context dividing the two groups. While the concept of a business process may appear more general from a logical viewpoint, at the moment software process engineering has the benefit of a longer history of general tool support and team-based interaction models. The software community has much to offer businesses as we move forward to more broadly positioned business process engineering systems, and of course, the general business community will bring with it a much wider market for ideas and products.<<ETX>>","PeriodicalId":163642,"journal":{"name":"Proceedings of the Third International Conference on the Software Process. Applying the Software Process","volume":"18 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1994-10-10","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"128036452","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 : 1994-10-10DOI: 10.1109/SPCON.1994.344409
I. Thomas
This paper addresses two issues: the position of an organization's software process with respect to its other business processes, and a comparison of characteristics for software and business process support mechanisms.<>
{"title":"Software processes and business processes","authors":"I. Thomas","doi":"10.1109/SPCON.1994.344409","DOIUrl":"https://doi.org/10.1109/SPCON.1994.344409","url":null,"abstract":"This paper addresses two issues: the position of an organization's software process with respect to its other business processes, and a comparison of characteristics for software and business process support mechanisms.<<ETX>>","PeriodicalId":163642,"journal":{"name":"Proceedings of the Third International Conference on the Software Process. Applying the Software Process","volume":"75 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1994-10-10","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114201279","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 : 1994-10-10DOI: 10.1109/SPCON.1994.344427
P. Jamart, A. van Lamsweerde
Software processes are enacted instances of process models. Process models are themselves instances of process meta-models that provide the various abstractions in terms of which process models can be described. This paper introduces a unified framework for software process modeling, enactment and evolution. The approach supports the customization/evolution of a process model and of its underlying meta-model. The process model and its meta-model are both described as specializations of kernel object classes using an object-oriented definition toolkit. Classes at one level become object instances at the upper level. The customization/evolution of models and meta-models is supported in a uniform way by creation/modification of kernel objects and by specialization of their classes. The overall approach is illustrated through a number of simple examples. Our definition toolkit has been written in Standard ML. This choice allows a precise semantics to be assigned to the various constructs using denotational semantics description techniques; at the same time executable prototypes of process-driven environments are produced from such descriptions.<>
{"title":"A reflective approach to process model customization, enactment and evolution","authors":"P. Jamart, A. van Lamsweerde","doi":"10.1109/SPCON.1994.344427","DOIUrl":"https://doi.org/10.1109/SPCON.1994.344427","url":null,"abstract":"Software processes are enacted instances of process models. Process models are themselves instances of process meta-models that provide the various abstractions in terms of which process models can be described. This paper introduces a unified framework for software process modeling, enactment and evolution. The approach supports the customization/evolution of a process model and of its underlying meta-model. The process model and its meta-model are both described as specializations of kernel object classes using an object-oriented definition toolkit. Classes at one level become object instances at the upper level. The customization/evolution of models and meta-models is supported in a uniform way by creation/modification of kernel objects and by specialization of their classes. The overall approach is illustrated through a number of simple examples. Our definition toolkit has been written in Standard ML. This choice allows a precise semantics to be assigned to the various constructs using denotational semantics description techniques; at the same time executable prototypes of process-driven environments are produced from such descriptions.<<ETX>>","PeriodicalId":163642,"journal":{"name":"Proceedings of the Third International Conference on the Software Process. Applying the Software Process","volume":"36 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1994-10-10","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114446379","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 : 1994-10-10DOI: 10.1109/SPCON.1994.344420
K. Inoue, A. Watanabe, H. Iida, K. Torii
Many kinds of software development processes have been modeled and actually described. However, most of those models and descriptions focus on manufacturing activities, such as editing and testing. In this paper, we study management activities in software development. We present a simple model for management activities, and propose a method to structure management processes using this method. The key of this method is that a simple manufacturing process is set out as a basis process, and management activities are added and embedded into it. Also, the process descriptions are categorized into four granularity classes. Using this method, we have actually modeled and described the quality management frameworks CMM (Capability Maturity Model) and ISO 9000-3. The obtained descriptions gave us intuitive overviews of those frameworks, and we could easily understand how to introduce those frameworks. Several statistics are obtained from those descriptions, and similarities and differences between CMM and ISO 9000-3 are studied based on these results.<>
{"title":"Modeling method for management process and its application to CMM and IS0 9000-3","authors":"K. Inoue, A. Watanabe, H. Iida, K. Torii","doi":"10.1109/SPCON.1994.344420","DOIUrl":"https://doi.org/10.1109/SPCON.1994.344420","url":null,"abstract":"Many kinds of software development processes have been modeled and actually described. However, most of those models and descriptions focus on manufacturing activities, such as editing and testing. In this paper, we study management activities in software development. We present a simple model for management activities, and propose a method to structure management processes using this method. The key of this method is that a simple manufacturing process is set out as a basis process, and management activities are added and embedded into it. Also, the process descriptions are categorized into four granularity classes. Using this method, we have actually modeled and described the quality management frameworks CMM (Capability Maturity Model) and ISO 9000-3. The obtained descriptions gave us intuitive overviews of those frameworks, and we could easily understand how to introduce those frameworks. Several statistics are obtained from those descriptions, and similarities and differences between CMM and ISO 9000-3 are studied based on these results.<<ETX>>","PeriodicalId":163642,"journal":{"name":"Proceedings of the Third International Conference on the Software Process. Applying the Software Process","volume":"121 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1994-10-10","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"124531964","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 : 1994-10-10DOI: 10.1109/SPCON.1994.344422
W. Humphrey
The personal software process (PSP) provides software engineers a way to improve the quality, predictability, and productivity of their work. It is designed to address the improvement needs of individual engineers and small software organizations. A graduate level PSP course has been taught at six universities and the PSP is being introduced by three industrial software organizations. The PSP provides a defined sequence of process improvement steps coupled with performance feedback at each step. This helps engineers to understand the quality of their work and to appreciate the effectiveness of the methods they use. Early experience with the PSP shows that average test defect rate improvements of ten times and average productivity improvements of 25% or more are typical.<>
{"title":"The personal process in software engineering","authors":"W. Humphrey","doi":"10.1109/SPCON.1994.344422","DOIUrl":"https://doi.org/10.1109/SPCON.1994.344422","url":null,"abstract":"The personal software process (PSP) provides software engineers a way to improve the quality, predictability, and productivity of their work. It is designed to address the improvement needs of individual engineers and small software organizations. A graduate level PSP course has been taught at six universities and the PSP is being introduced by three industrial software organizations. The PSP provides a defined sequence of process improvement steps coupled with performance feedback at each step. This helps engineers to understand the quality of their work and to appreciate the effectiveness of the methods they use. Early experience with the PSP shows that average test defect rate improvements of ten times and average productivity improvements of 25% or more are typical.<<ETX>>","PeriodicalId":163642,"journal":{"name":"Proceedings of the Third International Conference on the Software Process. Applying the Software Process","volume":"13 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1994-10-10","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126452133","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 : 1994-10-10DOI: 10.1109/SPCON.1994.344426
J. Cook, A. Wolf
To a great extent, the usefulness of a formal model of a software process lies in its ability to accurately predict the behavior of the executing process. Similarly, the usefulness of an executing process lies largely in its ability to fulfil the requirements embodied in a formal model of the process. When process models and process executions diverge, something significant is happening. We are developing techniques for uncovering discrepancies between models and executions under the rubric of process validation. Further, we are developing metrics for process validation that give engineers a feel for the severity of the discrepancy. We view the metrics presented here as a first step toward a suite of useful metrics for process validation.<>
{"title":"Toward metrics for process validation","authors":"J. Cook, A. Wolf","doi":"10.1109/SPCON.1994.344426","DOIUrl":"https://doi.org/10.1109/SPCON.1994.344426","url":null,"abstract":"To a great extent, the usefulness of a formal model of a software process lies in its ability to accurately predict the behavior of the executing process. Similarly, the usefulness of an executing process lies largely in its ability to fulfil the requirements embodied in a formal model of the process. When process models and process executions diverge, something significant is happening. We are developing techniques for uncovering discrepancies between models and executions under the rubric of process validation. Further, we are developing metrics for process validation that give engineers a feel for the severity of the discrepancy. We view the metrics presented here as a first step toward a suite of useful metrics for process validation.<<ETX>>","PeriodicalId":163642,"journal":{"name":"Proceedings of the Third International Conference on the Software Process. Applying the Software Process","volume":"30 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1994-10-10","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"123775102","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 : 1994-10-10DOI: 10.1109/SPCON.1994.344429
T. Allen
To begin our study of hardware development, we were faced with a dilemma. We could study the process or processes and learn something about individual development projects, but since each development was unique, how could we generalize? Furthermore, since we wanted to go beyond being merely descriptive in our analyses and develop normative conclusions, we were faced with the problem of evaluation. Since there are no universal criteria, how can you produce relative evaluations of unique activities? We solved both of these problems by seeking out instances in which the development activity was not unique. We took advantage of such formally sanctioned competitions by studying the National Aeronautics and Space Administration commissioned two or more contractors to develop prototypes of products, that N.A.S.A. would later procure. This enabled us then to obtain performance evaluations from the customer at a subsystem level. This is the level at which one or a very small group of engineers would be working, and thereby enabled us to relate observations of individual engineers to their performance outcome. We discuss some of the results and consider how this work may have some relevance to software development.<>
在开始研究硬件开发时，我们面临着一个困境。我们可以研究过程或过程，并了解个别开发项目，但由于每个开发都是独特的，我们如何进行概括?此外，由于我们希望在我们的分析中超越仅仅是描述性的，并发展规范性的结论，我们面临着评估的问题。既然没有普遍的标准，你如何对独特的活动进行相对的评估?我们通过寻找开发活动不是唯一的实例来解决这两个问题。我们利用这种正式批准的竞争，研究美国国家航空航天局(National Aeronautics and Space Administration，简称nasa)委托两家或更多的承包商开发产品原型，这些产品后来由nasa采购。这使我们能够在子系统级别上从客户那里获得性能评估。这是一个或一个非常小的工程师团队工作的水平，从而使我们能够将单个工程师的观察与他们的绩效结果联系起来。我们讨论一些结果，并考虑这项工作如何与软件开发相关。
{"title":"Some observations on the hardware development process","authors":"T. Allen","doi":"10.1109/SPCON.1994.344429","DOIUrl":"https://doi.org/10.1109/SPCON.1994.344429","url":null,"abstract":"To begin our study of hardware development, we were faced with a dilemma. We could study the process or processes and learn something about individual development projects, but since each development was unique, how could we generalize? Furthermore, since we wanted to go beyond being merely descriptive in our analyses and develop normative conclusions, we were faced with the problem of evaluation. Since there are no universal criteria, how can you produce relative evaluations of unique activities? We solved both of these problems by seeking out instances in which the development activity was not unique. We took advantage of such formally sanctioned competitions by studying the National Aeronautics and Space Administration commissioned two or more contractors to develop prototypes of products, that N.A.S.A. would later procure. This enabled us then to obtain performance evaluations from the customer at a subsystem level. This is the level at which one or a very small group of engineers would be working, and thereby enabled us to relate observations of individual engineers to their performance outcome. We discuss some of the results and consider how this work may have some relevance to software development.<<ETX>>","PeriodicalId":163642,"journal":{"name":"Proceedings of the Third International Conference on the Software Process. Applying the Software Process","volume":"23 1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1994-10-10","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125780798","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 : 1994-10-10DOI: 10.1109/SPCON.1994.344417
N. Madhavji, D. Holtje, Won-Kook Hong, T. Bruckhaus
Eliciting process models from software projects is a first significant step towards process improvement. In this paper, we present a method, called Elicit, for eliciting software process models from industrial software environments. What is significant about this method is that it has evolved from an intuitive state-the state that defines the immaturity of current elicitation methods-to a formally defined, repeatable, effective and quantified state. Over the last two years of its usage, the method has been used to elicit models from three industrial-scale processes: preliminary analysis, requirements engineering, and product planning and dependency management. The example given in the paper focuses on the requirements engineering process.<>
{"title":"Elicit: a method for eliciting process models","authors":"N. Madhavji, D. Holtje, Won-Kook Hong, T. Bruckhaus","doi":"10.1109/SPCON.1994.344417","DOIUrl":"https://doi.org/10.1109/SPCON.1994.344417","url":null,"abstract":"Eliciting process models from software projects is a first significant step towards process improvement. In this paper, we present a method, called Elicit, for eliciting software process models from industrial software environments. What is significant about this method is that it has evolved from an intuitive state-the state that defines the immaturity of current elicitation methods-to a formally defined, repeatable, effective and quantified state. Over the last two years of its usage, the method has been used to elicit models from three industrial-scale processes: preliminary analysis, requirements engineering, and product planning and dependency management. The example given in the paper focuses on the requirements engineering process.<<ETX>>","PeriodicalId":163642,"journal":{"name":"Proceedings of the Third International Conference on the Software Process. Applying the Software Process","volume":"12 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1994-10-10","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"121860055","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
扫码关注我们
求助内容：
应助结果提醒方式：