Proceedings of the (19th) International Conference on Software Engineering最新文献

{"title":"Applying Design of Experiments to Software Testing","authors":"I.S. Dunietzl, C. Mallows, A. Iannino, W. K. Ehrlich, B. D. Szablak","doi":"10.1109/ICSE.1997.610252","DOIUrl":"https://doi.org/10.1109/ICSE.1997.610252","url":null,"abstract":"Recently, a class of experimental designs has been devised that guarantee input domain coverage up to all combinations of k test factors taken t at a time. With such designs, all pair-wise combinations (or triplets or quadruplets, etc.) are selected at least once. To evaluate their applicability to software testing, we analyzed the extent to which software coverage (i.e., code execution) achieved by these designs for r = 1 ,...,k is representative of that achieved by exhaustively testing all factor combinations. The block coverage obtained for tS2 was comparable with that achieved by exhaustively testing all factor combinations but higher-order values of t were required for path coverage. Implications of these results for software testing are discussed. field, and that there is a total of 151 characters that can be entered across all 20 screen fields, then there are 95’5’~4.3x102g8 different inputs or test cases corresponding to the different ways a user can populate the screen. Clearly, exhaustive input testing is not feasible and hence, a software tester needs to efficiently generate an effective set of test cases as a means of verifying the correct operation of the software.","PeriodicalId":127923,"journal":{"name":"Proceedings of the (19th) International Conference on Software Engineering","volume":"35 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1997-05-17","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126434408","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":"Architecting Families of Software-Intensive Products","authors":"A. Ran, H. Kellock, P. Hjort","doi":"10.1109/ICSE.1997.610416","DOIUrl":"https://doi.org/10.1109/ICSE.1997.610416","url":null,"abstract":"Nokia is an international telecommunications group with headquarters in Helsinki, Finland. The group produces a range of telecommunications equipment for cellular and fixed networks, from switches and transmission equipment to cellular phones. Developing software for these products presents a number of difficult problems partly due to complex and often conflicting requirements that include: achieving function reliability without replicating parts and thus increasing the costs, providing feature variation in products while achieving reuse, doing parallel development by geographically distributed teams while controlling performance and integration of products In this talk we present our experiences of addressing these problems in several Nokia products with special focus on Synfonet Synchronous Digital Hierarchy network transport system. These products represent a class of configurable, dish-ibuted, embedded, real-time, dependable systems with several optional levels of software and hardware fault tolerance and function protection. For example Synfonet supports live removal and insertion of cards while preserving configuration data and enabling hot-restart of re-inserted cards. This capability is based on a reliable storage system that transparently distributes data over several cards. The system maintains at all times a number of copies necessary to preserve the state while one or several cards may be removed, and to resolve possible conflicts due, for example, to stale or otherwise incorrect configuration on newly inserted cards. Constraints of specific operating system, storage media, and other systemspecific characteristics could not be satisfied by any COTS products available at the time of system design. Therefor the reliable storage system and a number of other generic components were developed in house. To cover the costs of developing such complex software components we had to design for reuse of these components in several products. Permission to make digitalhard copies of all or part ofthis material for personal or cla..srooni use i s granted without fee provided that the copies are not made or distrihuted for profit or conmiercial advantage, the copyright notice, the title ofthe publication and its date appear, and notice is given that copyright is by permission ofthe ACM, Inc. To copy otherwise, to repuhlish, to post on servers or to redistribute to lists, requires specific permission and/or fee ICSE 97 Boston MA USA Copyright 1997 ACM 0-89791-914-9197105 ..%3.50 Rather than targeting component-based reuse relying on very general and flexible design and extensive parametrization of the components we approached the problem from the other end. We designed an architecture for a family of transport networks products and made the general components reusable by being an integral part of this specific software architecture. Designing and managing software architecture for a product family presents a number of problems that can be avoided. Som","PeriodicalId":127923,"journal":{"name":"Proceedings of the (19th) International Conference on Software Engineering","volume":"8 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1997-05-17","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129503900","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":"Tutorial: Evaluating Softiare Technology","authors":"S. Pfleeger","doi":"10.1109/ICSE.1997.610450","DOIUrl":"https://doi.org/10.1109/ICSE.1997.610450","url":null,"abstract":"This tutorial provides an overview of how to evaludte a software method, tool or process to determine its effcct on products, processes or resources I t includes a discussion of measurement theory, invwttgative design and analyiis. with many real-lifi examples to illustrate its points.","PeriodicalId":127923,"journal":{"name":"Proceedings of the (19th) International Conference on Software Engineering","volume":"9 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1997-05-17","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115001259","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":"Software Engineering (on) the World Wide Web","authors":"D. Eichmann","doi":"10.1109/ICSE.1997.610482","DOIUrl":"https://doi.org/10.1109/ICSE.1997.610482","url":null,"abstract":"INTRODUCTION The advent of the World Wide Web has accorded an extraordinarv level of attention, both at the level of the the Web before the conference is even held. The traditional aspect of the workshop is comprised of presentation blocks used to initiate two discussion sessions, which will focus on general public and at technical levels. Starting with a fairly simple architecture (HTML-based browsers and HTTP servers), the Web’s architectural complexity has expanded areas for d z m c e d attention. the nature and adequacy of current approaches, and","PeriodicalId":127923,"journal":{"name":"Proceedings of the (19th) International Conference on Software Engineering","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1997-05-17","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"134044714","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":"Redesigning the Systems Development Process","authors":"D. Bond, Patricia L. Rishi","doi":"10.1145/253228.253465","DOIUrl":"https://doi.org/10.1145/253228.253465","url":null,"abstract":"A process redesign effort was initiated to study and enhance the process used to develop sofhvare systems which manage the AT&T communications network. A diverse team of people, including developers, technologists, testers, systems engineers and customers, applied a business transformation methodology to take a fresh look at the software development process and proactively apply ideas to improve it. The methodology consisted of three steps: assessment, redesign, and implementation. Based on the assessment findings, the team redesigned the process to promote broader use of existing best practices and introduce process enabling technologies such as objectoriented (00) technology, concurrent engineering, layered architecture, reuse, and just-in-time. The project is currently in the implementation phase.","PeriodicalId":127923,"journal":{"name":"Proceedings of the (19th) International Conference on Software Engineering","volume":"30 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1997-05-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126042611","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":"Total Software Process Model Evolution in EPOS Experience Report","authors":"M. Nguyen, Alf Inge Wang, R. Conradi","doi":"10.1145/253228.253363","DOIUrl":"https://doi.org/10.1145/253228.253363","url":null,"abstract":"This paper presents a case study of Norwegian banking software house where the objective is to adopt a categorization framework for managing evolution in software projects to identify project profiles and evolution patterns, and to suggest improvements to better support frequent evolutions. Based on an analysis of collected evolution data from an ongoing case study, we elaborate a QIP-inspired method and own techniques to evolve corresponding process models in our Process-centered Software Engineering Environment, called EPOS. The method describes also how to synthesize and reuse evolution experience from completed projects to improve planning and estimation in new similar projects. The collected data demonstrates that requirement changes which are detected in later development phases, are major causes for cost overruns in the studied organization.","PeriodicalId":127923,"journal":{"name":"Proceedings of the (19th) International Conference on Software Engineering","volume":"55 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1997-05-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129726677","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":"Automatic Checking of Instruction Specifications","authors":"M. Fernández, N. Ramsey","doi":"10.1145/253228.253300","DOIUrl":"https://doi.org/10.1145/253228.253300","url":null,"abstract":"Mary Fernandez AT&T Labs 600 Mountain Ave. Murray Hill, NJ 07974 mff@research.att.com Retargeting applications that process machine code is a tedious and error-prone task. We help automate retargeting by describing instruction sets in a high-level specification language and by generating automatically the code for encoding and decoding instructions. Moreover, we provide automated assistance for checking machine descriptions. We check a specification for consistency both internally and externally. Internal checking forbids impossible instruction specifications, e.g., those that specify two values for a single bit. Internal checking warns about implausible specifications, e.g., those that don't specify values for all bits. Internal checks catch many mistakes, but they cannot guarantee that a specification accurately describes a target machine. Externally, we check a specification for consistency with an independent assembler. This technique increases a user's confidence in a specification's correctness and permits debugging in isolation of the target application. External validation is effective: it identified errors in specifications of the Intel Pentium, the MIPS, and the SPARC, after code generated from the latter two had been used in applications for over a year.","PeriodicalId":127923,"journal":{"name":"Proceedings of the (19th) International Conference on Software Engineering","volume":"23 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1997-05-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"130604335","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":"Assessing software review meetings: A controlled experimental study using CSRS","authors":"Philip M. Johnson, Danu Tjahjono","doi":"10.1145/253228.253252","DOIUrl":"https://doi.org/10.1145/253228.253252","url":null,"abstract":"Software review is a fundamental component of the software quality assurance process, yet significant controversies exist concerning efficiency and effectiveness of various review methods. A central question surrounds the use of meetings: traditional review practice views them as essential, while more recent findings question their utility. We conducted a controlled experimental study to assess several measures of cost and effectiveness for a meeting and non-meeting-based review method. The experiment used CSRS, a computer mediated collaborative software review environment, and 24 three person groups. Some of the data we collected included: the numbers of defects discovered, the effort required, the presence of synergy in the meeting-based groups, the occurrence of false positives in the non-meetingbased groups, and qualitative questionnaire responses. This paper presents the motivation for this experiment, its design and implementation, our empirical findings, conclusions, and future directions.","PeriodicalId":127923,"journal":{"name":"Proceedings of the (19th) International Conference on Software Engineering","volume":"72 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1997-05-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"124085183","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":"Manipulating Recovered Software Architecture Views","authors":"A. Yeh, David R. Harris, Melissa P. Chase","doi":"10.1145/253228.253265","DOIUrl":"https://doi.org/10.1145/253228.253265","url":null,"abstract":"Automatically recovered (reverse engineered) architectural views of legacy software are valuable for carrying out many software engineering tasks. However, while directly recovered views provide some relevant information, they often are either too fragmented or complex to be really useful in practice. This paper describes methods for making views more useful. We automatically combine and/or simplify views to produce hierarchies, hybrids, and abstractions. The methods we use take advantage of the source code fragments underlying the views to cross-reference between parts from different views.","PeriodicalId":127923,"journal":{"name":"Proceedings of the (19th) International Conference on Software Engineering","volume":"64 23","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1997-05-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"134195619","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":"Software Processes Are Software Too, Revisited: An Invited Talk on the Most Influential Paper of ICSE 9","authors":"L. Osterweil","doi":"10.1145/253228.253440","DOIUrl":"https://doi.org/10.1145/253228.253440","url":null,"abstract":"The ICSE 9 paper, “Software Processes are Software Too”’ suggests that software processes are themselves a form of software and that there are considerable benefits that will derive from basing a discipline of software process development on the more traditional discipline of application software development. This paper attempts to clarify some misconceptions about this original ICSE 9 suggestion and summarizes some research carried out over the past ten years that seems to confirm the original suggestion. The paper then goes on to map out some future research directions that seem indicated. The paper closes with some ruminations about the significance of the controversy that has continued to surround this work. Introduction “Software Processes are Software Too.” How many times I have heard that phrase quoted back to me in the past ten years! And how many times it has been (sometimes amusingly) misquoted too. Often I have been flattered to have had the ICSES paper [15] and its catchy title referred to as being “classic” and “seminal”. But often I have also been asked, “what does that really mean?” The idea is, alas, still misunderstood and misconstrued in some quarters. But amazingly, and gratifyingly, the phrase is still used, and the discussion of the idea still continues, even after ten years. The suggestion that software, and the processes that deal with it, might somehow be conceptually similar remains a powerfully appealing one that seems to have *This work was supported in part by the Air Force Materiel Command, Rome Laboratory, and the Defense Advanced Research Projects Agency under Contract F3060294-C0137. permission to &ke digitafiard copies of all or part ofthis mate&l for perSonal or classroom use is granted without fee provided that the copies we not made or distributed for profit or commercial advantage, the copy@bt notice, the title ofthe publication and its date appear, and notice is &‘a that copyright is by permission oftbe ACM, Inc. To copy otherwise, to republish, to post on servers or to redistribute to lists, requires specific permission and/or fee ICSE 97 Boston MA USA Copyright 1997 ACM 0-89791-914-9/97/05 ..$3.50 led to a considerable body of investigation, The suggestion was immediately controversial, and continues to be argued. Subsequently I discuss why I believe this discussion indicates a pattern of behavior typical of traditional scientific inquiry, and therefore seems to me to do credit to the software engineering community. But what of the (in)famous assertion itself? What does it really mean, and is it really valid? The assertion grew out of ruminations about the importance of orderly and systematic processes as the basis for assuring the quality of products and improving productivity in developing them. Applying the discipline of orderly process to software was not original with me. Lehman [13] and other8 [18] had suggested this long before. But I was troubled because I had started to see the development of a who","PeriodicalId":127923,"journal":{"name":"Proceedings of the (19th) International Conference on Software Engineering","volume":"18 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1997-05-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131748751","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}