J. Moll, J. Jacobs, B. Freimut, J. Trienekens, F. Coallier, P. Hoffnagle, P. Layzell, Liam O'Brien, D. Poo
{"title":"The importance of life cycle modeling to defect detection and prevention","authors":"J. Moll, J. Jacobs, B. Freimut, J. Trienekens, F. Coallier, P. Hoffnagle, P. Layzell, Liam O'Brien, D. Poo","doi":"10.1109/STEP.2002.1267624","DOIUrl":"https://doi.org/10.1109/STEP.2002.1267624","url":null,"abstract":"In many low mature organizations dynamic testing is often the only defect detection method applied. Thus, defects are detected rather late in the development process. High rework and testing effort, typically under time pressure, lead to unpredictable delivery dates and uncertain product quality. This paper presents several methods for early defect detection and prevention that have been in existence for quite some time, although not all of them are common practice. However, to use these methods operationally and scale them to a particular project or environment, they have to be positioned appropriately in the life cycle, especially in complex projects. Modeling the development life cycle, that is the construction of a project-specific life cycle, is an indispensable first step to recognize possible defect injection points throughout the development project and to optimize the application of the available methods for defect detection and prevention. This paper discusses the importance of life cycle modeling for defect detection and prevention and presents a set of concrete, proven methods that can be used to optimize defect detection and prevention. In particular, software inspections, static code analysis, defect measurement and defect causal analysis are discussed. These methods allow early, low cost detection of defects, preventing them from propagating to later development stages and preventing the occurrence of similar defects in future projects.","PeriodicalId":271935,"journal":{"name":"10th International Workshop on Software Technology and Engineering Practice","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2002-10-06","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131242979","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":"Improvements to the Guide to the Software Engineering Body of Knowledge (SWEBOK) and to the Software Engineering Education Body of Knowledge (SEEK)","authors":"P. Bourque, T. Lethbridge","doi":"10.1109/STEP.2002.1267594","DOIUrl":"https://doi.org/10.1109/STEP.2002.1267594","url":null,"abstract":"This workshop focused on the differences and similarities between two bodies of knowledge: the Guide to the Software Engineering Body of Knowledge (SWEBOK) (www.swebok.org) and the Software Engineering Education Body of Knowledge (SEEK) (http://sites.computer.org/ccse/). . It also considered what we can learn from those differences, and what changes the differences suggest for either body of knowledge.","PeriodicalId":271935,"journal":{"name":"10th International Workshop on Software Technology and Engineering Practice","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2002-10-06","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"124210535","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":"Mining and managing software assets","authors":"L. O'Brien, F. Hansen, R. Seacord, D. Smith","doi":"10.1109/STEP.2002.1267614","DOIUrl":"https://doi.org/10.1109/STEP.2002.1267614","url":null,"abstract":"Mining and managing software assets are important for strategic reuse of assets in new systems. This report outlines the SEI's Options Analysis for Reengineering (OAR) method, which is an approach for mining components and discusses component repositories and in particular the SEI's Knowledge-Based Automated Component Ensemble Evaluation (K-BACEE). OAR is a systematic, architecture-centric method for mining existing components for a product line or new software architecture. The method incorporates a set of scalable techniques and activities to collaboratively analyze existing components, determine viable mining options, and evaluate the most promising options. Once mined, software assets need to be managed to be useful. Compatibility with other legacy assets, commercial-off-the-shelf software products, and other software components needs to be understood and codified in such a way that it can be easily shared with other development projects within the organization. Towards this end, the SEI has developed K-BACEE which is a component repository that uses codified integration knowledge to assist system integrators in selecting ensembles of highly compatible components.","PeriodicalId":271935,"journal":{"name":"10th International Workshop on Software Technology and Engineering Practice","volume":"4 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2002-10-06","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129558560","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":"STEP 2002 - a roadmap for empirical software engineering","authors":"D. Budgen, S. Tilley","doi":"10.1109/STEP.2002.1267629","DOIUrl":"https://doi.org/10.1109/STEP.2002.1267629","url":null,"abstract":"An important influence in the evolution of any form of craft into an engineering discipline is the use that is made of evidence, and the adoption of systematic practices for its collection, analysis and propagation. The availability of evidence makes it possible to use analysis as the basis for making the key transition from knowing how to achieve an effect to understanding why the effect occurs, and any limitations associated with it.","PeriodicalId":271935,"journal":{"name":"10th International Workshop on Software Technology and Engineering Practice","volume":"5 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2002-10-06","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"133806640","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}
D. Budgen, G. Hoffnagle, M. Muller, F. Robert, A. Sellami, S. Tilley
{"title":"Empirical software engineering: a roadmap report from a workshop held at STEP 2002, Montreal, October 2002","authors":"D. Budgen, G. Hoffnagle, M. Muller, F. Robert, A. Sellami, S. Tilley","doi":"10.1109/STEP.2002.1267630","DOIUrl":"https://doi.org/10.1109/STEP.2002.1267630","url":null,"abstract":"The growing awareness of the need to employ evidence-based arguments to support the practices of software engineering, rather than arguments based upon advocacy, has led to a growing interest in the related area of empirical practices. This workshop, held at STEP 2002, set out to address two questions. What techniques do we need for empirical software engineering? What are the 'grand challenges' that empirical software engineering should be addressing as a matter of priority? For practical reasons, these were addressed in reverse order, and we began by identifying what each participant saw as being the challenges facing the wider acceptance and use of empirical techniques in software engineering. We then classified and grouped the challenges so identified under the three headings of resource, technical, and strategic. The next step involved examining how the particular challenges could be addressed, what proposals for action we would put forward, and how these proposals might be followed up. A core element we identified was the need to provide some form of centralized resource (such as a Web site) that could support both research and teaching. In this paper we outline the role that such a site could have, and also identify some of the elements that are likely to be needed in any educational module that addresses this topic.","PeriodicalId":271935,"journal":{"name":"10th International Workshop on Software Technology and Engineering Practice","volume":"70 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2002-10-06","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116201967","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":"Organizing for software product line engineering","authors":"M. Mannion","doi":"10.1109/STEP.2002.1267601","DOIUrl":"https://doi.org/10.1109/STEP.2002.1267601","url":null,"abstract":"Software product line engineering is the discipline of engineering a set of software-intensive systems sharing a common, managed set of features that satisfy the specific needs of a particular market segment or mission and that are developed from a common set of core assets in a prescribed way. The organizational characteristics required to successfully carry out software product line engineering will vary according to an organization's needs. However in general competitive advantage in software product line engineering lies in an organization's capacity to learn and adapt its products accordingly. This paper presents the conditions for a learning organization from management theory and argues that these conditions must prevail for software product line engineering to succeed.","PeriodicalId":271935,"journal":{"name":"10th International Workshop on Software Technology and Engineering Practice","volume":"6 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2002-10-06","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"128685055","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":"Interdisciplinary influences in software engineering practices","authors":"R. Bunting, F. Coallier, G. Lewis","doi":"10.1109/STEP.2002.1267604","DOIUrl":"https://doi.org/10.1109/STEP.2002.1267604","url":null,"abstract":"In consideration of the future of software engineering as an interdisciplinary activity, this paper explores the existing coverage of interdisciplinary software engineering areas in established or emerging software engineering frameworks. In particular we investigate the Software Engineering Body of Knowledge (SWEBOK), the Capability Maturity Model (CMM) and related Capability Maturity Model Integration (CMMI), and the Rational Unified Process (RUP). Following the investigation of the interdisciplinary elements of these frameworks we explore potential areas of advancement and opportunities, that is, where and how future body of knowledge, process, and framework revisions might benefit from the interdisciplinary approach.","PeriodicalId":271935,"journal":{"name":"10th International Workshop on Software Technology and Engineering Practice","volume":"6 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2002-10-06","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"130620595","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 roadmap for enterprise integration","authors":"D. Smith, L. O'Brien, M. Barbacci, F. Coallier","doi":"10.1109/STEP.2002.1267618","DOIUrl":"https://doi.org/10.1109/STEP.2002.1267618","url":null,"abstract":"The ability to provide integration between business functions that may be supported across multiple applications is a critical need for modern organizations. However, problems often emerge from overly ambitious or imprecise requirements resulting from inadequate plans for integrating different systems (legacy or otherwise). This paper analyzes the field of enterprise integration and provides an analysis of the extent of the problem and current trends that address the problem. It identifies gaps in the field, outstanding research issues, and provides an initial roadmap toward a solution.","PeriodicalId":271935,"journal":{"name":"10th International Workshop on Software Technology and Engineering Practice","volume":"48 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2002-10-06","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129125443","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":"Semantic modeling for school information system (SIS)","authors":"Ibrahim Mohamed, S. Mansor","doi":"10.1109/STEP.2002.1267620","DOIUrl":"https://doi.org/10.1109/STEP.2002.1267620","url":null,"abstract":"The influence of information and communication technology (ICT) brings a shift from industrial economy to knowledge economy (k-economy). Schools and educational institutions are forced to follow the trend, aligned with their roles in educating and producing knowledgeable citizens. An integrated information system requires a good data modeling technique. REA (Resource-Event-Agent) data model is a solution for this situation, using semantic modeling and thus building value chain. This study intends to model the school information system (SIS) using REA data modeling method, using a real case study to implement the model. Microsoft Access 2000 is used as both, the database and interface. It is not, at this stage, to compare with other techniques because this REA modeling is still under initial stage. The focus is more on the client server environment, and the next stage is to link the SIS to the Internet to take advantage of the REA semantic modeling.","PeriodicalId":271935,"journal":{"name":"10th International Workshop on Software Technology and Engineering Practice","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2002-10-06","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129251009","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}
F. Coallier, G. Hoffnagle, P. Layzell, L. O'Brien, D. Poo
{"title":"STEP2002: advances and opportunities in software engineering practice","authors":"F. Coallier, G. Hoffnagle, P. Layzell, L. O'Brien, D. Poo","doi":"10.1109/STEP.2002.1267593","DOIUrl":"https://doi.org/10.1109/STEP.2002.1267593","url":null,"abstract":"Will Software Engineering achieve the maturity of other engineering disciplines, or is this but a mirage given the continuous increases in system and application complexity and the shrinkage of cycle time? Is the first publication of the Guide to the Software Engineering Body of Knowledge (SWEBOK) and the CMMI, among others, a sign of this coming maturity or merely initial stepping stones? What are the key practices and technology that will make a difference? How do Agile Methodologies fit into the recognized software engineering body of knowledge? What research is most needed? Are CASE tools gaining back credibility? Is re-use coming of age with internet applications?","PeriodicalId":271935,"journal":{"name":"10th International Workshop on Software Technology and Engineering Practice","volume":"17 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2002-10-06","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114924986","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}