{"title":"A software factory model based on ISO9000 and CMM for Chinese small organizations","authors":"Chao Li, Han Li, Mingshu Li","doi":"10.1109/APAQS.2001.990033","DOIUrl":"https://doi.org/10.1109/APAQS.2001.990033","url":null,"abstract":"With the concepts and practices of software factory all over the world, the paper proposes a general software factory model (SFM). The model is presented through a static view and a dynamic view. Based on the general model and the specific situation of Chinese small organizations, a customized model, Software Factory Model-Chinese Small Organizations (SFM-CSO), is presented. Furthermore, an implementation of SFM-CSO based on ISO9000 and CMM (SFM-CSO [ISO/CMM]) is introduced, providing a practical guidance for Chinese small organizations to improve software product quality and productivity by adopting the software factory concept.","PeriodicalId":145151,"journal":{"name":"Proceedings Second Asia-Pacific Conference on Quality Software","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2001-12-10","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"133508856","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}
{"title":"A path-based approach to the detection of infinite looping","authors":"Jian Zhang","doi":"10.1109/APAQS.2001.990006","DOIUrl":"https://doi.org/10.1109/APAQS.2001.990006","url":null,"abstract":"Infinite looping is a common type of program error This paper studies the detection of infinite loops in imperative programs. A sufficient condition is given, which is based on program paths. For a simple loop, if we can establish the infeasibility of certain paths within the loop body, we can conclude that the loop does not terminate. Several examples are given to show the effectiveness of the approach. Its main benefits are that it is accurate and it can be supported by automated tools.","PeriodicalId":145151,"journal":{"name":"Proceedings Second Asia-Pacific Conference on Quality Software","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2001-12-10","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129231576","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}
{"title":"Special requirements for software process improvement applied in teleworking environments","authors":"Hong Guo","doi":"10.1109/APAQS.2001.990038","DOIUrl":"https://doi.org/10.1109/APAQS.2001.990038","url":null,"abstract":"The paper argues that, in the management of software development projects involving teleworkers, certain processes and base practices need more careful management than in projects carried out in the traditional centralized development environment. Based on the results of our surveys (a series of studies conducted in software engineering principles and in management methodology of teleworking), a number of key issues specific to telework conditions have been identified. A new Software Process Improvement approach for Teleworking Environment (SPITE) has been developed as a major contribution to the software industry, which fills an important gap in software process modeling. The focus of the paper is to present an in-depth analysis of some of these issues that are not addressed in the current process models. Three processes and twenty-five base practices are created and used to provide major input to the development of SPITE.","PeriodicalId":145151,"journal":{"name":"Proceedings Second Asia-Pacific Conference on Quality Software","volume":"119 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2001-12-10","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116010361","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}
{"title":"Incremental fault-tolerant design in an object-oriented setting","authors":"E. Johnsen, Olaf Owe, E. Munthe-Kaas, J. Vain","doi":"10.1109/APAQS.2001.990023","DOIUrl":"https://doi.org/10.1109/APAQS.2001.990023","url":null,"abstract":"With the increasing emphasis on dependability in complex, distributed systems, it is essential that system development can be done gradually and at different levels of detail. We propose an incremental treatment of faults as a refinement process on object-oriented system specifications. An intolerant system specification is a natural abstraction from which a fault-tolerant system can evolve. With each refinement step a fault and its treatment are introduced, so the fault-tolerance of the system increases during the design process. Different kinds of faults are identified and captured by separate refinement relations according to how the tolerant system relates to abstract properties of the intolerant one in terms of safety, and liveness. The specification language utilized is object-oriented and based upon first-order predicates on communication traces. Fault-tolerance refinement relations are formalized within this framework.","PeriodicalId":145151,"journal":{"name":"Proceedings Second Asia-Pacific Conference on Quality Software","volume":"21 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2001-12-10","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116825862","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}
{"title":"A software product model emphasizing relationships","authors":"S. Chou, Chung-Wei Huang","doi":"10.1109/APAQS.2001.990047","DOIUrl":"https://doi.org/10.1109/APAQS.2001.990047","url":null,"abstract":"Managing software products during software development is essential. A model is needed to model products and facilitates product management. Important product management functions include: 1) version control, 2) configuration management, 3) product consistency management, and 4) reference completeness management. The paper proposes a product model to facilitate the functions. Since product relationships play an important role in product management, the model emphasizes them.","PeriodicalId":145151,"journal":{"name":"Proceedings Second Asia-Pacific Conference on Quality Software","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2001-12-10","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129447539","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}
{"title":"Class and module in SOFL","authors":"Shaoying Liu, J. Dong","doi":"10.1109/APAQS.2001.990026","DOIUrl":"https://doi.org/10.1109/APAQS.2001.990026","url":null,"abstract":"SOFL is a formal language and method for system specification and design. It was developed by integrating Petri Nets, Data Flow Diagrams, and VDM-SL. As the major feature of the original SOFL method is to use structured techniques for analysis and specification, and object-oriented techniques for design and implementation, SOFL has its own implementation language that is similar to C++. However during our recent work of applying SOFL to software systems, the transformation of structured specifications to object-oriented implementations creates some difficulties, simply because of paradigms mismatch. In this paper we extend SOFL to a formal object-oriented language and method while keeping its structured features. This will allow powerful object-oriented reuse mechanisms, such as class inheritance and object composition, to be utilized in the early phases, and transformation from SOFL specifications to commercial object-oriented programming languages to be readily achieved.","PeriodicalId":145151,"journal":{"name":"Proceedings Second Asia-Pacific Conference on Quality Software","volume":"28 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2001-12-10","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129110885","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}
{"title":"Railway power SCADA system commissioning \"case example\"","authors":"I. Hampton, K. Lam","doi":"10.1109/APAQS.2001.990018","DOIUrl":"https://doi.org/10.1109/APAQS.2001.990018","url":null,"abstract":"The Mass Transit Railway Corporation Ltd., installed and commissioned their first computer based Power Remote Control System in the late 1980s. The system was successfully replaced in February 2000. The paper describes the methodology adopted to prepare and facilitate the transition of the replacement computer based control system into operational service and a system review following one year of service operation.","PeriodicalId":145151,"journal":{"name":"Proceedings Second Asia-Pacific Conference on Quality Software","volume":"29 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2001-12-10","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114239362","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}
{"title":"Priorities of process improvement outcomes based on process capability levels","authors":"T. Varkoi, M. Lepasaar, H. Jaakkola","doi":"10.1109/APAQS.2001.990040","DOIUrl":"https://doi.org/10.1109/APAQS.2001.990040","url":null,"abstract":"How are software process improvement outcomes related to targeted capability levels? The answer can serve as a feasible path forward for the improvement work in a software organization. The article provides guidance on what to include in the improvement effort at different levels of process capability. The reduction of premature documentation and practices reveals the essential work products needed to support the achievement of the desired capability level. This results in increased effectiveness of the improvement process even in the very beginning of the improvement work. The article opens up the process improvement process by presenting the relevant work products for each capability level. The key outcome is a step-wise approach to process improvement work products to lower the threshold for initiating the software process improvement work.","PeriodicalId":145151,"journal":{"name":"Proceedings Second Asia-Pacific Conference on Quality Software","volume":"57 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2001-12-10","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"133922804","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}
I. Crnkovic, Annita Persson Dahlkvist, D. Svensson
{"title":"Complex systems development requirements - PDM and SCM integration","authors":"I. Crnkovic, Annita Persson Dahlkvist, D. Svensson","doi":"10.1109/APAQS.2001.990048","DOIUrl":"https://doi.org/10.1109/APAQS.2001.990048","url":null,"abstract":"Software is being increasingly incorporated into increasingly extensive industrial and other applications. There is a demand for total control of entire applications including their software components. As a consequence, the development procedure, production operations and maintenance, previously separate processes, are being integrated in comprehensive process systems. In the integration of these processes, many difficulties are encountered because of the different natures of the processes and the different approaches made to the problem. In the integration process, many activities overlap and much data is duplicated, thus making a complex process even more complex. software configuration management (SCM) and product data management (PDM) which are used to solve similar problems in different ways are examples of overlapping processes. Attempts to integrate SCM and PDM systems to obtain a more efficient development process have not proved particularly successful. The paper analyses the main characteristics of SCM and PDM, development processes that are PDM- or SCM-centered, their common characteristics and their differences. The problems encountered when using both systems are analyzed. An analysis of the possible integration of these systems is presented and the potential benefits and problems involved in such integration are discussed.","PeriodicalId":145151,"journal":{"name":"Proceedings Second Asia-Pacific Conference on Quality Software","volume":"39 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2001-12-10","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131725711","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}
{"title":"Towards a verification of the rule-based expert system of the IBM SA for OS/390 Automation Manager","authors":"C. Sinz, W. Küchlin, T. Lumpp","doi":"10.1109/APAQS.2001.990042","DOIUrl":"https://doi.org/10.1109/APAQS.2001.990042","url":null,"abstract":"We formally verify consistency aspects of the rule-based expert system of IBM's System Automation software for IBM's e-server zSeries. Starting with a formalization of the expert system in propositional dynamic logic (PDL), we are able to encode termination and determinism properties. To circumvent direct proofs in PDL or its extension /spl Delta/PDL, we further translate versions of the occurring decision problems to propositional logic, where we can apply advanced SAT and BDD techniques. In our experiments we revealed some inconsistencies, and after correcting them, we successfully verified a non-looping property for a part of the expert system.","PeriodicalId":145151,"journal":{"name":"Proceedings Second Asia-Pacific Conference on Quality Software","volume":"52 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2001-12-10","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"121356638","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}