Pub Date : 2002-10-06DOI: 10.1109/STEP.2002.1267630
D. Budgen, G. Hoffnagle, M. Muller, F. Robert, A. Sellami, S. Tilley
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.
{"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}
Pub Date : 2002-10-06DOI: 10.1109/STEP.2002.1267601
M. Mannion
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.
{"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}
Pub Date : 2002-10-06DOI: 10.1109/STEP.2002.1267604
R. Bunting, F. Coallier, G. Lewis
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.
{"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}
Pub Date : 2002-10-06DOI: 10.1109/STEP.2002.1267618
D. Smith, L. O'Brien, M. Barbacci, F. Coallier
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.
{"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}
Pub Date : 2002-10-06DOI: 10.1109/STEP.2002.1267620
Ibrahim Mohamed, S. Mansor
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.
{"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}
Pub Date : 2002-10-06DOI: 10.1109/STEP.2002.1267593
F. Coallier, G. Hoffnagle, P. Layzell, L. O'Brien, D. Poo
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?
{"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}
Pub Date : 2001-12-01DOI: 10.1109/STEP.2002.1267595
Pierre Bourque, F. Robert, J. Lavoie, A. Lee, Sylvie Trudel, T. Lethbridge
This paper is the result of a workshop held in Montreal in October 2002 during the Software Technology and Practice Conference (STEP 2002). The purpose of the paper is to present a preliminary mapping of two related but distinct software engineering body of knowledge initiatives, and also a list of proposals to improve them: the guide to the Software Engineering Body of Knowledge (SWEBOK) and the Software Engineering Education [body of] Knowledge (SEEK). The SWEBOK guide is aimed at identifying and describing the body of knowledge of a software engineering professional who has an undergraduate degree and four years of experience. The intended audiences of the SWEBOK Guide include industry, academia and policy-making organizations. The SEEK is aimed at delimiting the knowledge that professionals teaching software engineering agree is necessary for anyone to obtain an undergraduate degree in this field. The mapping shows that, though there are no major "school of thought" divergences between the two bodies of knowledge, there are a number of differences in the details of each breakdown in terms of vocabulary, level of detail, decomposition approach and topics encompassed.
{"title":"Guide to the Software Engineering Body of Knowledge (SWEBOK) and the Software Engineering Education Knowledge (SEEK) - a preliminary mapping","authors":"Pierre Bourque, F. Robert, J. Lavoie, A. Lee, Sylvie Trudel, T. Lethbridge","doi":"10.1109/STEP.2002.1267595","DOIUrl":"https://doi.org/10.1109/STEP.2002.1267595","url":null,"abstract":"This paper is the result of a workshop held in Montreal in October 2002 during the Software Technology and Practice Conference (STEP 2002). The purpose of the paper is to present a preliminary mapping of two related but distinct software engineering body of knowledge initiatives, and also a list of proposals to improve them: the guide to the Software Engineering Body of Knowledge (SWEBOK) and the Software Engineering Education [body of] Knowledge (SEEK). The SWEBOK guide is aimed at identifying and describing the body of knowledge of a software engineering professional who has an undergraduate degree and four years of experience. The intended audiences of the SWEBOK Guide include industry, academia and policy-making organizations. The SEEK is aimed at delimiting the knowledge that professionals teaching software engineering agree is necessary for anyone to obtain an undergraduate degree in this field. The mapping shows that, though there are no major \"school of thought\" divergences between the two bodies of knowledge, there are a number of differences in the details of each breakdown in terms of vocabulary, level of detail, decomposition approach and topics encompassed.","PeriodicalId":271935,"journal":{"name":"10th International Workshop on Software Technology and Engineering Practice","volume":"352 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2001-12-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114828001","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 : 1900-01-01DOI: 10.1109/STEP.2002.1267617
Enterprise Integration has the goal of providing timely and accurate exchange of consistent information between business functions to support strategic and tactical business goals in a manner that appears to be seamless. 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. This workshop discussed unsolved issues related to enterprise integration and focused on ways to address these unmet needs.
{"title":"Introduction - Enterprise integration","authors":"","doi":"10.1109/STEP.2002.1267617","DOIUrl":"https://doi.org/10.1109/STEP.2002.1267617","url":null,"abstract":"Enterprise Integration has the goal of providing timely and accurate exchange of consistent information between business functions to support strategic and tactical business goals in a manner that appears to be seamless. 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. This workshop discussed unsolved issues related to enterprise integration and focused on ways to address these unmet needs.","PeriodicalId":271935,"journal":{"name":"10th International Workshop on Software Technology and Engineering Practice","volume":"134 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"123216757","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
扫码关注我们
求助内容：
应助结果提醒方式：