Thoughts on software engineering knowledge, and how to organize it

10th International Workshop on Software Technology and Engineering Practice Pub Date : 2002-10-06 DOI:10.1109/STEP.2002.1267596

D.J. Bagert, M. Barbacci, D. Budgen, T. Lethbridge, W. Suryn, H. van Vliet

{"title":"Thoughts on software engineering knowledge, and how to organize it","authors":"D.J. Bagert, M. Barbacci, D. Budgen, T. Lethbridge, W. Suryn, H. van Vliet","doi":"10.1109/STEP.2002.1267596","DOIUrl":null,"url":null,"abstract":"SWEBOK describes what knowledge a software engineer who has a Bachelor's degree and four years of experience should have. SEEK describes the knowledge to be taught in an undergraduate program in software engineering. Although different in scope and purpose, there are many similarities between the two, and after all, even experienced developers need an education, don't they? A full-day workshop on the alignment between SWEBOK and SEEK, held at STEP 2002, revealed a number of issues that received either a scant or a scattered treatment in either or both documents. These issues include: software architecture, software measurement, and software quality. In addition, topics of debate were whether or not user interface design should be considered part of software design, or rather deserves its own, separate treatment; and whether maintenance/evolution merits a separate discussion, or should rather be seen as the default mode of operation in software development. This paper elaborates the discussions of this workshop.","PeriodicalId":271935,"journal":{"name":"10th International Workshop on Software Technology and Engineering Practice","volume":"26 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2002-10-06","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"6","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"10th International Workshop on Software Technology and Engineering Practice","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/STEP.2002.1267596","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}

引用次数: 6

Abstract

SWEBOK describes what knowledge a software engineer who has a Bachelor's degree and four years of experience should have. SEEK describes the knowledge to be taught in an undergraduate program in software engineering. Although different in scope and purpose, there are many similarities between the two, and after all, even experienced developers need an education, don't they? A full-day workshop on the alignment between SWEBOK and SEEK, held at STEP 2002, revealed a number of issues that received either a scant or a scattered treatment in either or both documents. These issues include: software architecture, software measurement, and software quality. In addition, topics of debate were whether or not user interface design should be considered part of software design, or rather deserves its own, separate treatment; and whether maintenance/evolution merits a separate discussion, or should rather be seen as the default mode of operation in software development. This paper elaborates the discussions of this workshop.

查看原文本刊更多论文

对软件工程知识的思考，以及如何组织这些知识

SWEBOK描述了一个拥有学士学位和四年工作经验的软件工程师应该具备的知识。SEEK描述了在软件工程本科课程中要教授的知识。尽管在范围和目的上有所不同，但两者之间有许多相似之处，毕竟，即使是经验丰富的开发人员也需要接受教育，不是吗?在STEP 2002上举行的关于SWEBOK和SEEK之间一致性的全天研讨会上，揭示了一些在其中一个或两个文件中得到很少或分散处理的问题。这些问题包括:软件架构、软件度量和软件质量。此外，辩论的主题是用户界面设计是否应该被视为软件设计的一部分，或者应该单独对待;维护/演进是否值得单独讨论，或者应该被视为软件开发中的默认操作模式。本文对本次研讨会的讨论进行了详细的阐述。

本文章由计算机程序翻译，如有差异，请以英文原文为准。

求助全文

约1分钟内获得全文求助全文

来源期刊

10th International Workshop on Software Technology and Engineering Practice

自引率

0.00%

发文量