漫论毕业设计教案策划

针对当今高等学校理工类专业毕业设计的教案构建与策划，提出了关于把毕业设计时间进程安排成三个学期(毕业设计传统的时间安排一般为一个学期)的改革思想。并提出了关于毕业设计指导方法中的五个典型指导重点，四环节指导流程和多种多样指导形式的具体实施举措与办法。同时，依据我们多年来指导毕业设计的实践体验，结合我校电气工程及其自动化专业毕业设计改革与创新的实施情况，进行了总结研究。     

对建筑电气专业毕业设计指导工作的探讨

本文就怎样指导建筑电气专业毕业设计工作，提出了一些自己的看法。文章从毕业设计韪选择的角度，从毕业设计任务指导书，以及具体毕业设计指导过程、内容、难点及时间安排上，谈了谈自己的看法。     

高校毕业设计网络管理系统

根据高校毕业设计指导和管理的要求,提出了一套基于B／S的网络毕业设计管理系统。实现了毕业设计课题的双向选择、课题内容及基本要求查询,毕业设计网上指导、学生去向查询、毕业设计工作通知发布,毕业论文上载等功能。该系统从毕业设计工作的起始阶段开始对毕业设计工作的全过程进行动态管理。使用结果表明本系统运行安全可靠,功能较全,能满足高校毕业设计网络管理的要求。为高校毕业设计指导和管理提供了新的模式。     

提高毕业设计质量的实践

毕业设计论文质量直接影响到整个教学质量以及本科生的专业素质。在近年来教学实践的基础上，积极探索本科生毕业设计的指导方法，并结合毕业设计实例，对课题的拟定、设计指导、论文撰写以及毕业答辩准备等主要环节进行了较为详细的说明。提出了切实有效的改进措施，旨在培养学生的独立工作能力、综合应用能力和创新能力。     

电气工程及其自动化专业毕业设计研究

毕业设计是学生在大学期间的最后学习阶段，运用所学知识和能力独立进行的一次综合训练。毕业设计环节的教学质量与学校对毕业设计的规定和组织、学生素质和态度、教师水平与指导情况以及毕业设计环境等多种因素相关。本文主要分析了电气工程及其自动化专业的毕业设计课题分布，学校、教师、就业单位和学生对毕业设计的要求和希望。指出了毕业设计中的一些问题并提出了相应的解决方向。     

通过毕业设计培养学生的科研能力

本科生的毕业设计是培养学生基本科研能力的一个很好的机会，对学生未来的学习和工和有着十分重要的意义，近年来，我们将自身的科研课题与本科生的毕业设计相结合，通过毕业设计有意识地培养学生的基本科研素质，实践表明，这种方法能够充分发挥指导教师和学生两方面的积极性，为圆满地完成毕业设计创造了良好的条件。并且，这种初步的科研经历对学生今后的工作实践和进一步深造有着很大的帮助。     

在毕业设计中强化电子信息工程专业学生的情报意识

毕业设计是工科本科教学中最重要的综合性实践教学过程，文献检索是毕业设计中的最重要环节之一。本文以电子信息工程专业的本科毕业设计教学实践为基础，结合该专业的具体特点，首先强调了在毕业设计过程中文献检索的重要意义；然后从指导教师和学生两个角度详细介绍了在毕业设计过程中加强文献检索，培养学生情报意识的具体方法；最后就如何改进教学管理制度，加强培养学生情报意识进行了详细的探讨。     

毕业设计(论文)质量评价体系研究与实践

毕业设计（论文）质量直接影响着本科人才培养质量和学校总体教学水平，在多年的毕业设计（论文）工作中。采取早准备、严格过程检查、严把簧辩关、学生与指，教师之间采用双向选择、实行指导教师负责制、建立不断完善的质量评价体系、成立以学科带头人和学术组长组成的毕业设计（论文）质量检查专家工作组，从毕业设计（论文）选题、过程、答辩到成绩评定等全过程进行跟踪检查，形成了一套切实可行的方法，全面提高了毕业设计（论文）质量。     

提高工科类毕业设计质量的探索

针对毕业设计现状,本文结合实践经验提出改善毕业设计质量的有效方法,包括:以真题为毕业设计题目;学生自主选题;教师为主导,学生为主体进行毕业设计;公平合理的奖惩体系;严格的管理与监督机制等,而学院领导的重视以及严格的管理机制尤为重要.提高毕业设计质量的原动力是让学生充分认识到毕业设计的深刻意义,让教师意识到指导毕业设计有助于提高科研素质.     

基于.NET平台的毕业设计管理系统中若干关键技术的研究与实现

毕业设计（论文）是高等学校人才培养过程中不可或缺的重要环节，为了使整个毕业设计过程更具公开性、公平性、安全性，为指导教师和管理人员提供方便、科学、合理的计划、统筹、交流、评价等管理手段，因此基于Web的毕业设计管理系统设计和实现过程中的相关技术和技巧也就成为关键问题。本文阐述了笔者在设计开发一套毕业设计管理系统的过程中总结出来的诸如数据库端性能优化，.NET平台下Excel数据的使用、系统状态智能更新以及简单安全性等方面的若干关键编程技术和技巧。     

利用快速原型降低软件项目风险

在软件项目管理中,如何减小风险是一个重要的课题。针对由于实际的软件项目中出现的需求不明确、需求的理解偏差、关键性能的可实现性等问题而造成的风险,通过采用快速原型法开发模式,解决需求的二义性问题,评估在开发中的技术方案,缩短产品与用户见面的时间,提高需求分析的质量,缩短开发时间,降低开发成本。     

Research comes in from the cold

Political and economic upheavals have forced researchers in eastern Europe to take a fresh look at how they collaborate with other countries. The author reports from Belarus on how they are coming to terms with the new situation. At least five different types of collaboration now exist: agreements between academies and other state-funded structures; bilateral agreements between research organisations; projects funded by the west; individual grants and fellowships to eastern scientists from western foundations; and projects funded by the European Commission. Agreements between academies and other state-funded structures are mainly intended and used for bilateral visits. The process of signing new agreements is very slow, often due to a lack of financial resources on both sides, but some have been successful     

"电路"课的课程设计

针对常规的电路课程实验的缺陷，提出在“电路”课程教学中开展课程设计，并用实验验证设计效果；讨论了有关课题选择、时间安排、实验条件及学生成绩评定依据等问题；给出了学生的设计作品实例。这种既动脑又动手的课程设计在培养学生的自学能力、用工程的观念独立解决实际问题的能力以及培养学生耐心、协作、实事求是等工程师基本素质等方面起着重要的作用。     

Evaluating the Relative Performance of Engineering Design Projects: A Case Study Using Data Envelopment Analysis

This paper presents a case study of how Data Envelopment Analysis (DEA) was applied to generate objective cross-project comparisons of project duration within an engineering department of the Belgian Armed Forces. To date, DEA has been applied to study projects within certain domains (e.g., software and R&D); however, DEA has not been proposed as a general project evaluation tool within the project management literature. In this case study, we demonstrate how DEA fills a gap not addressed by commonly applied project evaluation methods (such as earned value management) by allowing the objective comparison of projects on actual measures, such as duration and cost, by explicitly considering differences in key input characteristics across these projects. Thus, DEA can overcome the paradigm of project uniqueness and facilitate cross-project learning. We describe how DEA allowed the department to gain new insight about the impact of changes to its engineering design process (redesigned based on ISO 15288), creating a performance index that simultaneously considers project duration and key input variables that determine project duration. We conclude with directions for future research on the application of DEA as a project evaluation tool for project managers, program office managers, and other decision-makers in project-based organizations.     

Impact of Cooperative R&D Projects on ICT‐Based Technology Convergence

This study examines how the characteristics of cooperative research and development (R&D) projects in the public domain impact information and communication technology (ICT) convergence. Based on the analysis of 416 cooperative R&D projects under the ICT‐based industry convergence R&D program in Korea, the study finds that the characteristics of cooperative R&D projects significantly impact ICT convergence. Moreover, the participation of public research institutes and universities is critical for ICT convergence compared with that of firms. However, in firm‐to‐firm cooperation, the participation of small and medium enterprises contributes to cross‐sectional convergence, while the participation of large firms leads to overall and longitudinal convergence. R&D inputs such as the number of partners and government subsidies exhibit an inverted U‐shaped relationship (negative quadratic effect) with technology convergence. Project duration and homogeneous partners are also critical factors for ICT convergence. The results indicate several implications and guidelines on how to effectively organize cooperative R&D projects to facilitate technology convergence.     

“If only we'd known sooner” developing knowledge oforganizational changes earlier in the product development process

Managers of canceled innovation projects may berate themselves retrospectively for not having known about downstream organizational changes earlier in the development process. The assumption that knowledge of changes can and should be captured in the early stages of product development is prevalent in both research and practice. This paper reports on a field study of 13 innovation projects in two Fortune 500 corporations. It details 51 change initiatives that the projects challenge their organizations to undertake. Findings provide insight into the difficulties of capturing knowledge of downstream organizational changes. The paper presents a model in which informational knowledge of what new activities are required to implement a new product must be complemented with interpretive knowledge of how those activities relate to the organization and strategy of the firm     

Software fault content and reliability estimations fortelecommunication systems

The problem of software fault content and reliability estimations is considered. Estimations that can be used to improve the control of a software projects are emphasized. A model of how to estimate the number of software faults is presented, which takes into account both the development process and the developed software product. A model of how to predict, before the testing has started, the occurrences of faults during the testing stage is also presented. These models, together with software reliability growth models, have been evaluated on a number of software projects     

Project Management: At the Crossroads?

The articles in this issue were chosen based around the fundamental ingredients of projects, examining how humans organize to accomplish worthwhile endeavors and make sense of an ambiguous environment.