共查询到20条相似文献,搜索用时 15 毫秒
1.
In this paper we explore how the software engineering research community is currently dealing with the ethical issues that some empirical research presents. We discuss how the immaturity of the software engineering discipline is reflected in an approach to ethical issues that compares unfavourably with other more mature disciplines.We show that an analysis of recent published work measures an increase in empirical software engineering research currently being undertaken. We also discuss our survey of UK University Department Heads which explores how the software engineering research community is dealing with the ethical issues related to empirical work. Overall we found that whilst some UK Universities have taken ethical issues very seriously, others have not considered the issues. 相似文献
2.
为了描述、理解、评估、预测、控制、管理或者改善与软件相关的内容,研究者常常使用经验研究的方法.经验研究在软件工程领域已经得到广泛的应用并备受关注.为了了解近年来软件工程中经验研究的特点,并希望经验研究方法为更多研究者所了解,我们通过系统映射的方法,对软件工程中经验研究的典型期刊ESE(Empirical Software Engineering)近5年的论文做了一个调研,搜集了从2013年1月至2017年6月发表在该期刊的250篇论文.通过定性和定量的分析,给出了软件工程领域采用经验研究的主要目的,常用的经验研究方法、以及这些方法在软件工程各个领域中的使用情况和呈现的一些新特征.之后,分析了经验研究的主要数据来源、采集手段、常用的数理统计方法以及开源项目在经验研究中的使用情况等,给出了研究者对有效性和可重现性问题的关心程度.最后进行了本文的有效性分析,并进一步探讨了经验研究的发展方向和大数据时代下经验研究面临的机遇及一些开放性问题. 相似文献
3.
以培养应用型人才为目标,突出能力培养主线,分析新工科教育下应用型人才的能力要求,对软件工程课程教学案例的选择、设计思路和实施过程进行探讨,强调学生动手操作,通过对案例进行解剖和验证,掌握知识,提升能力。 相似文献
4.
Software, Software Engineering and Software Engineering Research: Some Unconventional Thoughts 总被引:1,自引:0,他引:1 下载免费PDF全文
Software engineering is broadly discussed as falling far short of expectations. Data and examples are used to justify how
software itself is often poor, how the engineering of software leaves much to be desired, and how research in software engineering
has not made enough progress to help overcome these weaknesses. However, these data and examples are presented and interpreted
in ways that are arguably imbalanced. This imbalance, usually taken at face value, may be distracting the field from making
significant progress towards improving the effective engineering of software, a goal the entire community shares. Research
dichotomies, which tend to pit one approach against another, often subtly hint that there is a best way to engineer software
or a best way to perform research on software. This, too, may be distracting the field from important classes of progress. 相似文献
5.
6.
Empirical studies in software engineering can involve a variety of organizations, each with their own set of policies and procedures geared at safeguarding the interests and responsibilities of the researchers, students, the collaborating company, the university, and possibly national funding agencies like the National Science Foundation and the National Institute of Health. Each of these organizations have differing goals for participating in these studies and bring widely different cultures and expectations to the table. While policies, procedures, contracts, and agreements set expectations, they by themselves cannot ensure ethical behavior. This position paper describes some of the common approaches to encourage ethical behavior and their limits for enforcing ethical behavior. 相似文献
7.
8.
9.
Protecting Research Subjects, Employees and Researchers: Implications for Software Engineering 总被引:1,自引:1,他引:0
Joan E. Sieber 《Empirical Software Engineering》2001,6(4):329-341
Human subjects research entails risks for subjects and, to a lesser extent, for researchers. This paper introduces the common types of risks to subjects of empirical software engineering research, and how risk can be a function of the context in which the research is conducted. Risks for researchers are also discussed. Government regulation of the ethics of human subjects research is introduced using the example of the Common Rule that governs much human subjects research taking place in the United States. 相似文献
10.
通过分析软件行业对软件人才实践能力的新要求,提出软件工程课程以学生为主体的教学改进方案。该方案提升学生的学习兴趣,提高课内实践的教学质量,增强学生对软件工程专业知识的实际运用能力。 相似文献
11.
The Information Systems (IS) discipline, and related research, focuses on the development, understanding, and use of technology to meet business needs. Technology, in particular software, is the basis for IS research, making software engineering a critical component of research in the IS domain. While the importance of software development is well accepted, what constitutes high quality software engineering research is not well defined. Perhaps this is because some software development clearly is not research and it is hard to distinguish between pure application development, and systems development that pushes the boundaries of knowledge. Sir Karl Popper argued that the scientific quality of research is not based on its empirical method, but on the nature of the questions asked. Our research suggests that software engineering can meet Popper's criteria for scientific research.Drawing on well-established research philosophies, we propose a software engineering research methodology (SERM) and discuss the utility of this methodology for contributing to and expanding the IS body of knowledge. We also describe the considerations that need to be addressed by SERM to enhance acceptability of software engineering research in IS. Our suggestions are corroborated with a review of current IS software engineering research reported in leading IS journals. 相似文献
12.
13.
计算机科学中,基准测试已经用来比较计算机系统性能、检索算法信息、数据库和其他一些技术。在研究领域,基准测试的创建和普遍使用经常伴随着快速的技术进步和团队建设。这些形成了科学学科的基准测试理论。基于这个理论,通过团队工作的方式定义基准测试来挑战软件工程研究,变得越来越具有科学性和需要。本文介绍一个成功使用基准测试促进研究状况的个案研究——逆向工程。 相似文献
14.
In this paper we discuss our study of the problems 12 software companies experienced in software development. In total we present qualitative data collected from 45 focus groups that involved over 200 software staff. We look at how different practitioner groups respond to software process improvement problems. We show our classification and analysis of this data using correspondence analysis. Correspondence analysis is a graphical data representation method new to software development research. The aim of the work we present is to develop a more holistic understanding of the problems practitioners are experiencing in their attempts to improve their software processes. Our main finding is that there is an association between a company's capability maturity and patterns of reported problems. Organizational problems are more associated with high maturity companies than with low maturity companies. Low maturity companies are closely linked to problems relating directly to projects such as documentation, timescales, tools and technology. Our findings also confirm differences in practitioner group problems. Senior managers cite problems with goals, culture and politics. Project managers are concerned with timescales, change management, budgets and estimates. Developers are experiencing problems with requirements, testing, documentation, communication, tools and technology. These associations are displayed graphically through correspondence analysis maps. 相似文献
15.
Using a Reliability Growth Model to Control Software Inspection 总被引:1,自引:0,他引:1
After a software inspection the project manager has to decide whether he can pass a product on to the next software development stage or whether it still contains a substantial number of defects and should be reinspected to further improve its quality. While a substantial number of defects remaining in a product after inspection is a reasonable precondition to schedule a reinspection, it is also important to estimate whether the likely number of defects to be found with a reinspection will lower the defect density under the target threshold. In this work we propose a reliability growth model and two heuristic linear models for software inspection, which estimate the likely number of additional defects to be found during reinspection. We evaluate the accuracy of these models with time-stamped defect data from a large-scale controlled inspection experiment on reinspection. Main findings are: (a) The two best models estimated the defect detection capability for reinspection with good accuracy: over 80% of the estimates had an absolute relative error of under 10%; (b) The reinspection decision correctness based on the estimates of all investigated models, overall around 80% correct decisions, was much better than the trivial models to always or never reinspect; the latter is the default decision in practice. 相似文献
16.
软件系统规模越来越大、越来越复杂,以工程的方法对软件进行开发、运行、维护和修复将会成为最有效的方法。软件人才工程能力的培养就显得越来越重要。本文作者在多年从事软件教学和软件专业教学计划制定的基础上,以优化课程体系、加强实践教学提高学生的工程能力为主线,从培养方案与教学计划制定、主要课程设置、工程实践条件、师资配备、师资培养等方面论述了如何提高软件专业学生工程能力的培养方案。 相似文献
17.
复杂软件系统的复杂性和不确定性引起了软件行为、交互行为以及故障行为的复杂性。在对复杂软件系统的可靠性、安全性等方面研究的过程中,故障的传播行为逐渐引起了学者的广泛关注,成为国内外学者的研究热点。回顾了故障传播的研究现状,对故障传播问题研究方向进行了梳理,重点对影响故障传播过程的两方面进行了详细的介绍,包括体系结构特征和故障类型。最后提出故障传播研究领域存在的挑战和未来的研究方向。 相似文献
18.
Traditionally computer sciences courses will assess software code.It is common and accepted good practice(as in written reports) to reference other sources of appropriate material.However there appears to be no explicit method,recommendation or advice available to computer science tutors and students on a referencing approach! This paper aims to stimulate discussion from peers involved in software engineering education.By discussing the apparent lack of "referencing within code" advice to students and proposing suggestions for appropriate solutions.This will be based on the authors' experience of assessing code and the current advice given to their students. 相似文献
19.
本文结合笔者的教学实践,提出团队式的教学组织和学习模式,从课堂教学手段、实践教学安排、学生学习方法、考核方式等多个方面进行阐述并进行了效果分析。 相似文献
20.
精品课程的建设可以提高课程的教学质量和教学水平,收到良好的教学效果。结合校级软件工程精品课程建设的实际,阐述按照专业培养目标进行课程建设的方法,提出选择教学内容和设计实验内容的建议。同时建设实训系统和辅助教学网站,培养学生软件开发和自主学习的能力,提出以案例驱动为主的课程教学创新模式。 相似文献