Pub Date : 2002-02-25DOI: 10.1109/CSEE.2002.995222
Laurie A. Williams, Michael J. Lutz, G. Hislop, M. McCracken, Nancy R. Mead, J. F. Naveda
{"title":"Workshop 3: Integrating Agile Practices into Software Engineering Courses","authors":"Laurie A. Williams, Michael J. Lutz, G. Hislop, M. McCracken, Nancy R. Mead, J. F. Naveda","doi":"10.1109/CSEE.2002.995222","DOIUrl":"https://doi.org/10.1109/CSEE.2002.995222","url":null,"abstract":"","PeriodicalId":250569,"journal":{"name":"Conference on Software Engineering Education and Training","volume":"82 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2002-02-25","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122936382","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-02-25DOI: 10.1109/CSEET.2002.10008
C. Kaner
{"title":"Tutorial 4: Issues in Commmercial Law of Interest to Software Engineering Educators","authors":"C. Kaner","doi":"10.1109/CSEET.2002.10008","DOIUrl":"https://doi.org/10.1109/CSEET.2002.10008","url":null,"abstract":"","PeriodicalId":250569,"journal":{"name":"Conference on Software Engineering Education and Training","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2002-02-25","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129611120","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-02-25DOI: 10.1109/CSEE.2002.995191
E. Yourdon
Summary form only given, as follows. For years, veteran programmers and project managers in corporate IT departments have complained that universities teach software engineering material that is either obsolete, irrelevant, or far too theoretical in nature. And while academia might disagree with such criticisms, it would at least be useful to have some additional insights into the things that industry believes are important and relevant. This keynote presentation will focus on several of these "competencies," which the academic community may or may not wish to incorporate into the software engineering curriculum. For example, a major area of discussion and debate in industry today involves the tradeoffs between "light", agile software processes versus "heavy" processes such as the ones associated with the SEI-CMM. Similarly, industry practitioners are constantly debating the relative merits of a "zero-defect" quality approach, versus a "good-enough" approach to design, coding, and even testing. And industry practitioners are finding that the best way to teach these concepts, within their own corporate classrooms, involves "war-games" based on realistic simulation models of software projects.
{"title":"Preparing Software Engineers for the 'Real World'","authors":"E. Yourdon","doi":"10.1109/CSEE.2002.995191","DOIUrl":"https://doi.org/10.1109/CSEE.2002.995191","url":null,"abstract":"Summary form only given, as follows. For years, veteran programmers and project managers in corporate IT departments have complained that universities teach software engineering material that is either obsolete, irrelevant, or far too theoretical in nature. And while academia might disagree with such criticisms, it would at least be useful to have some additional insights into the things that industry believes are important and relevant. This keynote presentation will focus on several of these \"competencies,\" which the academic community may or may not wish to incorporate into the software engineering curriculum. For example, a major area of discussion and debate in industry today involves the tradeoffs between \"light\", agile software processes versus \"heavy\" processes such as the ones associated with the SEI-CMM. Similarly, industry practitioners are constantly debating the relative merits of a \"zero-defect\" quality approach, versus a \"good-enough\" approach to design, coding, and even testing. And industry practitioners are finding that the best way to teach these concepts, within their own corporate classrooms, involves \"war-games\" based on realistic simulation models of software projects.","PeriodicalId":250569,"journal":{"name":"Conference on Software Engineering Education and Training","volume":"56 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2002-02-25","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127713502","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-02-25DOI: 10.1109/CSEET.2002.10007
D. Port, B. Boehm
{"title":"Tutorial 1: Introducing Software Economics within SWE Project Courses","authors":"D. Port, B. Boehm","doi":"10.1109/CSEET.2002.10007","DOIUrl":"https://doi.org/10.1109/CSEET.2002.10007","url":null,"abstract":"","PeriodicalId":250569,"journal":{"name":"Conference on Software Engineering Education and Training","volume":"29 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2002-02-25","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132391983","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-02-25DOI: 10.1109/CSEE.2002.995209
Martin Höst
Empirical methods are important in software engineering. It is important to be able to evaluate new techniques and methods in a structured way before they are introduced in the software process. This paper presents how empirical methods may be taught by letting students take part in the execution and analysis of empirical investigations in projects. The projects that the students carry out include a role-play where teachers play the roles of managers for the students and responsible for ordering the work of the students. It is found that the project is well received and that it is probable that the students reach the related learning objectives of the course.
{"title":"Introducing Empirical Software Engineering Methods in Education","authors":"Martin Höst","doi":"10.1109/CSEE.2002.995209","DOIUrl":"https://doi.org/10.1109/CSEE.2002.995209","url":null,"abstract":"Empirical methods are important in software engineering. It is important to be able to evaluate new techniques and methods in a structured way before they are introduced in the software process. This paper presents how empirical methods may be taught by letting students take part in the execution and analysis of empirical investigations in projects. The projects that the students carry out include a role-play where teachers play the roles of managers for the students and responsible for ordering the work of the students. It is found that the project is well received and that it is probable that the students reach the related learning objectives of the course.","PeriodicalId":250569,"journal":{"name":"Conference on Software Engineering Education and Training","volume":"67 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2002-02-25","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"123741891","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-02-25DOI: 10.1109/CSEET.2002.10005
Deborah Wolfe
{"title":"Panel 2: The Canadian Engineering Profession and Software Engineering","authors":"Deborah Wolfe","doi":"10.1109/CSEET.2002.10005","DOIUrl":"https://doi.org/10.1109/CSEET.2002.10005","url":null,"abstract":"","PeriodicalId":250569,"journal":{"name":"Conference on Software Engineering Education and Training","volume":"25 5","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2002-02-25","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131860239","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-02-25DOI: 10.1109/CSEE.2002.995221
L. Thomas, M. Ratcliffe
Summary form only given, as follows. We envisage this workshop as a chance for Software Engineering Educators to share their challenges, successes and failures in teaching Software Engineering concepts to First Year (or beginning) students The specifics of the workshop will depend to some extent on the interests of the participants, but as a basis for organisation and discussion we will ask all participants to fill in a questionnaire to be provided in the conference registration kits. We will begin the workshop by sharing the basic results of the questionnaires and then ask participants to share their biggest challenges in teaching Software Engineering to beginners, what they have done that has been successful (and any things they have tried that didn't work), what students have trouble understanding, what topics may not even fit in an introductory course, etc. We will then break the group up into interest groups on particular topics (eg. reuse, programming, professionalism, design, testing, etc.) and those groups will brainstorm about one particular issue. The workshop will end with the groups sharing ideas. Our hope is that this workshop will not only be useful in and of itself but will also provide a springboard for participants to find colleagues with similar interests and enthusiasms.
{"title":"Workshop 2: First Year Software Engineering","authors":"L. Thomas, M. Ratcliffe","doi":"10.1109/CSEE.2002.995221","DOIUrl":"https://doi.org/10.1109/CSEE.2002.995221","url":null,"abstract":"Summary form only given, as follows. We envisage this workshop as a chance for Software Engineering Educators to share their challenges, successes and failures in teaching Software Engineering concepts to First Year (or beginning) students The specifics of the workshop will depend to some extent on the interests of the participants, but as a basis for organisation and discussion we will ask all participants to fill in a questionnaire to be provided in the conference registration kits. We will begin the workshop by sharing the basic results of the questionnaires and then ask participants to share their biggest challenges in teaching Software Engineering to beginners, what they have done that has been successful (and any things they have tried that didn't work), what students have trouble understanding, what topics may not even fit in an introductory course, etc. We will then break the group up into interest groups on particular topics (eg. reuse, programming, professionalism, design, testing, etc.) and those groups will brainstorm about one particular issue. The workshop will end with the groups sharing ideas. Our hope is that this workshop will not only be useful in and of itself but will also provide a springboard for participants to find colleagues with similar interests and enthusiasms.","PeriodicalId":250569,"journal":{"name":"Conference on Software Engineering Education and Training","volume":"8 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2002-02-25","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"124964991","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-02-19DOI: 10.1109/CSEE.2001.913841
J. Donaldson, J. Jenkins
Software Systems permeate just about every aspect of life throughout developed and industrialised nations today. When failures arise, the aftermath is highly complicated because there are so many ways that they may occur. The complexity of the situation becomes evident even before the apparent or actual causes are considered, especially when the rate of change of the technology is taken into account. Systems failures cause havoc everywhere. They may be total, partial or temporary; and examination of the subject has to consider: implemented systems, systems being enhanced and totally new projects. This paper considers some of the common causes of Systems Failures that are being investigated following the end of Esprit projects (Multispace and Space-UFO). The work takes a more specific look at the quality implications on software systems failures and then goes on to look at current research into what steps may be taken to systematically understand what has actually gone wrong. From that point, possible options open to provide credible and robust solutions to these types of problem, are discussed.
{"title":"Systems Failures","authors":"J. Donaldson, J. Jenkins","doi":"10.1109/CSEE.2001.913841","DOIUrl":"https://doi.org/10.1109/CSEE.2001.913841","url":null,"abstract":"Software Systems permeate just about every aspect of life throughout developed and industrialised nations today. When failures arise, the aftermath is highly complicated because there are so many ways that they may occur. The complexity of the situation becomes evident even before the apparent or actual causes are considered, especially when the rate of change of the technology is taken into account. Systems failures cause havoc everywhere. They may be total, partial or temporary; and examination of the subject has to consider: implemented systems, systems being enhanced and totally new projects. This paper considers some of the common causes of Systems Failures that are being investigated following the end of Esprit projects (Multispace and Space-UFO). The work takes a more specific look at the quality implications on software systems failures and then goes on to look at current research into what steps may be taken to systematically understand what has actually gone wrong. From that point, possible options open to provide credible and robust solutions to these types of problem, are discussed.","PeriodicalId":250569,"journal":{"name":"Conference on Software Engineering Education and Training","volume":"34 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2001-02-19","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122926962","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-02-19DOI: 10.1109/CSEET.2001.10005
David G. Kay
This tutorial will provide a broad overview of computer law with a focus on intellectual property law and how it relates to the practice of software development and dissemination. It will provide software engineering faculty with a framework for addressing legal issues that may commonly arise in the software engineering classroom.
{"title":"Computer Law Basics for Software Engineering Educators","authors":"David G. Kay","doi":"10.1109/CSEET.2001.10005","DOIUrl":"https://doi.org/10.1109/CSEET.2001.10005","url":null,"abstract":"This tutorial will provide a broad overview of computer law with a focus on intellectual property law and how it relates to the practice of software development and dissemination. It will provide software engineering faculty with a framework for addressing legal issues that may commonly arise in the software engineering classroom.","PeriodicalId":250569,"journal":{"name":"Conference on Software Engineering Education and Training","volume":"27 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2001-02-19","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"117197174","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-02-19DOI: 10.1109/CSEET.2001.10000
J. F. Naveda, J. Díaz-Herrera, H. Ellis, T. Hilburn, M. Lutz
{"title":"Software Engineering: Is It Process? Is It Design? (Panel)","authors":"J. F. Naveda, J. Díaz-Herrera, H. Ellis, T. Hilburn, M. Lutz","doi":"10.1109/CSEET.2001.10000","DOIUrl":"https://doi.org/10.1109/CSEET.2001.10000","url":null,"abstract":"","PeriodicalId":250569,"journal":{"name":"Conference on Software Engineering Education and Training","volume":"29 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2001-02-19","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"124570309","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
扫码关注我们
求助内容：
应助结果提醒方式：