Pub Date : 1991-10-21DOI: 10.1109/ICSP.1991.664344
D. Frailey
Texas Instruments has been defining and installing a corporate-wide software process for nearly three years. We have learned first hand some of the difficulties of modeling a software process intended for widespread use. For example, processes can be modeled in many ways and at many levels; terminology is more important than we thought; tailoring imposes additional restrictions on the process model; and endusers come in many flavors with varying documentation and training requirements. This paper summarizes some of oul' experiences. I. INTRODUCTION In early 1989, Texas Instruments began a corporate-wide software improvement thrust. This thrust was manifested at three levels in the company: corporate, operating group, and software project. The major job of the corporate effort was to define a preferred software engineering process for use throughout the company. This task was staffed by a team representing all major operating groups. Other corporate level tasks included coordination of and participation in nine SEI assessments, assistance with the formation of software improvement teams in each of the major operating groups, and work with pilot projects. The operating level software improvement teams actually performed the SEI assessments, devised operating procedures, and developed specific action plans for software improvement within their respective business entities. At the project level, pilot projects began to apply the procedures and processes and quality improvement teams were started to carry out continuous process improvement. This paper focuses on the corporate level effort to define a software process. Texas Instruments is a highly diversified electronics-based company. Major operating entities participate in such businesses as semiconductor devices, computer systems, military electronics, information systems, computer aided software engineering tools for business applications, factory automation, and consumer electronics products. This diversity made it necessary for us to face problems that a more focused organization might be able to ignore.
{"title":"Defining a Corporate-Wide Software Process","authors":"D. Frailey","doi":"10.1109/ICSP.1991.664344","DOIUrl":"https://doi.org/10.1109/ICSP.1991.664344","url":null,"abstract":"Texas Instruments has been defining and installing a corporate-wide software process for nearly three years. We have learned first hand some of the difficulties of modeling a software process intended for widespread use. For example, processes can be modeled in many ways and at many levels; terminology is more important than we thought; tailoring imposes additional restrictions on the process model; and endusers come in many flavors with varying documentation and training requirements. This paper summarizes some of oul' experiences. I. INTRODUCTION In early 1989, Texas Instruments began a corporate-wide software improvement thrust. This thrust was manifested at three levels in the company: corporate, operating group, and software project. The major job of the corporate effort was to define a preferred software engineering process for use throughout the company. This task was staffed by a team representing all major operating groups. Other corporate level tasks included coordination of and participation in nine SEI assessments, assistance with the formation of software improvement teams in each of the major operating groups, and work with pilot projects. The operating level software improvement teams actually performed the SEI assessments, devised operating procedures, and developed specific action plans for software improvement within their respective business entities. At the project level, pilot projects began to apply the procedures and processes and quality improvement teams were started to carry out continuous process improvement. This paper focuses on the corporate level effort to define a software process. Texas Instruments is a highly diversified electronics-based company. Major operating entities participate in such businesses as semiconductor devices, computer systems, military electronics, information systems, computer aided software engineering tools for business applications, factory automation, and consumer electronics products. This diversity made it necessary for us to face problems that a more focused organization might be able to ignore.","PeriodicalId":309190,"journal":{"name":"Proceedings. First International Conference on the Software Process,","volume":"631 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1991-10-21","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"123349162","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 : 1991-10-21DOI: 10.1109/ICSP.1991.664339
H. Iida, T. Ogihara, K. Inoue, K. Torii
ARSTRACT This paper describes a way to define software development processes formally. Software development processes are assumed to be sequential sentences of activities, and they are defined by the set of sentences with context free grammars. The sequence of development activities is defined formally, and the characteristics and behasvior of the development processes become clearer. This paper also describes a method to construct a menu oriented navigation system from the grammar. The menus provided by this system guide the developers to the next activities in the development. The system works with the interpreter for the process description language PDL.
{"title":"Generating a Menu-Oriented Navigation System from Formal Description of Software Development Activity Sequence","authors":"H. Iida, T. Ogihara, K. Inoue, K. Torii","doi":"10.1109/ICSP.1991.664339","DOIUrl":"https://doi.org/10.1109/ICSP.1991.664339","url":null,"abstract":"ARSTRACT This paper describes a way to define software development processes formally. Software development processes are assumed to be sequential sentences of activities, and they are defined by the set of sentences with context free grammars. The sequence of development activities is defined formally, and the characteristics and behasvior of the development processes become clearer. This paper also describes a method to construct a menu oriented navigation system from the grammar. The menus provided by this system guide the developers to the next activities in the development. The system works with the interpreter for the process description language PDL.","PeriodicalId":309190,"journal":{"name":"Proceedings. First International Conference on the Software Process,","volume":"55 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1991-10-21","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"128944386","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 : 1991-10-21DOI: 10.1109/ICSP.1991.664342
M. Saeki, T. Kaneko, M. Sakamoto
This paper reports on an approach to software process modeling with its method. Our model consists of two sub models - one is for tasks which are performed in a software process and another is for resources which perform the tasks, e.g. human participants, project teams, computerized tools and so on. The formal specification language LOTOS (Language of Temporal Ordering Specification) is used to define software processes based on our modeling technique. We have developed the method to represent software processes by using LOTOS based on the methods for software specification & design. Furthermore we have applied our method to an example problem proposed for the 6th Software Process Workshop, and discussed our approach.
{"title":"A Method for Software Process Modeling and Description Using Lotos","authors":"M. Saeki, T. Kaneko, M. Sakamoto","doi":"10.1109/ICSP.1991.664342","DOIUrl":"https://doi.org/10.1109/ICSP.1991.664342","url":null,"abstract":"This paper reports on an approach to software process modeling with its method. Our model consists of two sub models - one is for tasks which are performed in a software process and another is for resources which perform the tasks, e.g. human participants, project teams, computerized tools and so on. The formal specification language LOTOS (Language of Temporal Ordering Specification) is used to define software processes based on our modeling technique. We have developed the method to represent software processes by using LOTOS based on the methods for software specification & design. Furthermore we have applied our method to an example problem proposed for the 6th Software Process Workshop, and discussed our approach.","PeriodicalId":309190,"journal":{"name":"Proceedings. First International Conference on the Software Process,","volume":"80 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1991-10-21","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125968758","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 : 1991-10-21DOI: 10.1109/ICSP.1991.664350
Masato Suzuki, T. Katayama
Meta-operations are introduced into a software process model HFSP for modeling dynamic and flexible features of software processes. As process enaction is characterized as growing trees of activity decompositions in HFSP, these operations are most naturally considered as operations over these trees, which allow changing enaction status, creating new trees and communicating among them from inside and outside of the trees. A Formal description of these operations are given together with their application to the description of ISPW6 Example Process.
{"title":"Meta-Operations in the Process Model Hfsp for the Dynamics and Flexibility of Software Processes","authors":"Masato Suzuki, T. Katayama","doi":"10.1109/ICSP.1991.664350","DOIUrl":"https://doi.org/10.1109/ICSP.1991.664350","url":null,"abstract":"Meta-operations are introduced into a software process model HFSP for modeling dynamic and flexible features of software processes. As process enaction is characterized as growing trees of activity decompositions in HFSP, these operations are most naturally considered as operations over these trees, which allow changing enaction status, creating new trees and communicating among them from inside and outside of the trees. A Formal description of these operations are given together with their application to the description of ISPW6 Example Process.","PeriodicalId":309190,"journal":{"name":"Proceedings. First International Conference on the Software Process,","volume":"108 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1991-10-21","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122697815","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 : 1991-10-21DOI: 10.1109/ICSP.1991.664338
Xiping Song, L. J. Osterweil
A number of software design methodologies have been developed and compared over the past 20 years. A good comparison would aid in codifying, enhancing and integrating these design methodologies. However, the existing comparisons are based largely upon the experiences of practitioners and the understandings of the authors. Consequently, these comparisons tend to be subjeckve and to be affected by application domains. 11 is the purpose of this paper to introduce a systematic approach to objectively compare design methodologies. Our approach is based on modeling the design methodologies and classifying their components. Modeling the design methodologies ent,ails decomposing the methodologies into romponents. The classification of the components illustrates which components address similar design issues and/or have similar structures. Similar components can be identified and may be further modeled to aid in understanding more precisely their similarities and differences. The models of the methodologies are also used as the bases for conjectures and conclusions about the differences between the methodologies. In this paper we demonstrate this approach by using it to compare JSD [Jacks831 and Booch’s Object 0 ciented Design (BOOD) [Booch86]. The results of this comparison also demonstrate that process modeling [OsterU, Kelln881 is valuable as a powerful tool in analysis of software development approaches.
{"title":"Comparing Design Methodologies through Process Modeling","authors":"Xiping Song, L. J. Osterweil","doi":"10.1109/ICSP.1991.664338","DOIUrl":"https://doi.org/10.1109/ICSP.1991.664338","url":null,"abstract":"A number of software design methodologies have been developed and compared over the past 20 years. A good comparison would aid in codifying, enhancing and integrating these design methodologies. However, the existing comparisons are based largely upon the experiences of practitioners and the understandings of the authors. Consequently, these comparisons tend to be subjeckve and to be affected by application domains. 11 is the purpose of this paper to introduce a systematic approach to objectively compare design methodologies. Our approach is based on modeling the design methodologies and classifying their components. Modeling the design methodologies ent,ails decomposing the methodologies into romponents. The classification of the components illustrates which components address similar design issues and/or have similar structures. Similar components can be identified and may be further modeled to aid in understanding more precisely their similarities and differences. The models of the methodologies are also used as the bases for conjectures and conclusions about the differences between the methodologies. In this paper we demonstrate this approach by using it to compare JSD [Jacks831 and Booch’s Object 0 ciented Design (BOOD) [Booch86]. The results of this comparison also demonstrate that process modeling [OsterU, Kelln881 is valuable as a powerful tool in analysis of software development approaches.","PeriodicalId":309190,"journal":{"name":"Proceedings. First International Conference on the Software Process,","volume":"29 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1991-10-21","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129179115","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
扫码关注我们
求助内容：
应助结果提醒方式：