软件工程的经济学方法

随着软件工程、管理、经济等多学科的日益渗透与发展,逐渐形成了运用经济学观念、方法研究与解决软件工程问题的软件工程经济学SEE(Software Engineering Economics)这一交叉新学科。SEE引起了计算机、软件、管理、经济等多方面专家、学者、实业家、软件开发人员和管理人员以及用户的广泛重视。本文旨在综合分析当前这一学科要点的基础上,对SEE在软件工程中有较突出意义的方面做一个概括的综述。文中还归纳指出了当前SEE中的主要研究课题。     

软件工程技术、经济、管理、法律整合工具探究

由于现代软件工程涉及到技术、经济、管理、法律等多领域,衍生出相互交叉的二级学科,传统CASE工具不能很好地满足现代软件工程以及未来发展需要.本文提出整合软件工程技术、经济、管理、法律的系统化CASE工具,并以文档自动化为主要特征加以详细描述,最后给出一个可自动化的经济学实例.     

教育软件工程的研究框架与发展趋势

教育软件的开发一直缺少相适应的开发方法的研究。教育软件工程是近年来出现的崭新的研究方向,是软件工程和教育学相互融合深入的产物。首先从总体上讨论了教育软件的概念、教育软件工程在软件产品开发中和生存周期的关系,然后描述了当前应用的具有代表性的教育软件开发模型,最后是关于教育软件工程的未来研究课题内容、研究趋势整体框架和研究发展分层结构。     

面向对象的组合软件工程研究

组合软件工程技术是当今软件工程技术发展的主流。本文综述了作者在基于对象的组合软件工程研究方面的最新进展，包括语义模型、描述语言、设计方法学和支持环境等方面。     

软件开发周期模型的选择策略

经典的软件工程瀑布模型在整个软件开发界已经广泛地使用了，但瀑布模型开发出的软件却并不尽如人意。因此怎样开发出更可靠，执行效率更高，功能更完善的软件就刺激了软件工程研究人员去开发新的软件开发模型。如：原型法，软件综合法以及可重用软件。但是由于这些软件开发新模型的介导者经常使用不同的术语，因而很难对它们进行比较。本文为此讨论了一个框架，用于：１）作为分析软件开发模型异同的一个基础；２）作为软件工程研究     

软件工程及其相关技术

本文评述了软件工程的基本内容，重点介绍了软件工程的相关技术：软件复用、构件集成与纽装以及一系列软件开发模型。     

计算机实践向理论的回归

软件工程研究软件开发过程所需的模型、方法和工具。UML是软件工程实践中的重要工具,它可以对软件进行规约、可视化、构造和建档。本文以UML的状态图为例,讨论了其在十字路口的信号灯的控制中的应用,指出了其在软件需求分析中的建模作用,并揭示了软件工程与计算机科学之间的关系。最后,指出了当今软件工程的发展与实践是在向 向计算机科学理论回归,从而作为计算机科学的理论基础的离散数学对实践的指导作用就显而易见了。     

基于UML的图形界面系统对象模型的研究

按照面向对象软件工程的思想,以UML建模语言,以Visio2003为建模工具,研究与建立了小型监控组态软件图形界面系统的对象模型,并且研究和建立了对象模型内部的各子模型,以及各子模型之间的关系。该对象模型已借助面向对象编程语言VisualC＋＋6．0实现。模型的建立过程对于同类软件模型的研究和开发具有参考价值。     

软件工程学科建设的若干问题

一、引言在文中,我们指出了软件工程教育的重要性、紧迫性和任务的繁重性;给出了软件工程的若干定义和重要特征。其中有待解决的重要问题之一是软件工程教育的课程建设问题。目前国内外尚无成功的课程模式和成熟的教材,其原因之一是软件工程领域尚处于幼年时期,它的变化与发展之快令人难于预料,以致于在编写有关书籍时墨迹未干,许多内容就已过时了;原因之二在于软件工程所涉及的范围太广了,它不但包含了计算机科学的基础知识,还包含了管理科学、经济学、通讯技术、人类工程学以及     

谈信息经济学及其内容(一)

谈信息经济学及其内容（一）文：乌家培／中国信息经济学会理事长信息经济学是对信息的经济研究、对信息经济的研究、对信息（学）与经济（学）关系的研究。看了这段文字，你一定会觉得信息经济学于我们太遥远、太陌生，而独罢全文，你便觉得它正在走进我们的生活一、从１...     

支持成本度量和过程改进的软件工程环境

描述了如何在软件工程环境中增加面向软件过程的成本度量和成本控制功能。阐述了面向软件过程的成本模型,与产品分解的成本模型不同,提出把可复用的软件过程作为成本度量的对象;介绍了软件过程及成本度量的本体,使得度量的对象和度量数据都有语义背景,并说明如何在软件工程环境下进行成本度量和过程改进,最后给出了功能模块。     

A Software Engineering Environment (SEE) for Weapon System Software

A software engineering environment (SEE) has been designed, developed, and used for the life-cycle support of weapon system software. This SEE consists of two types of facilities: software production and integration. The software production facility consists of a software system that runs on a commercial multicomputer configuration. The approach features increased management visibility of the software development process, increased programmer productivity through automation, reducing the cost-of-change during maintenance, and the use of automated regression testing to improve software quality. These facilities have been used for eight years to develop and maintain weapon system software for several projects. This paper describes accomplishments, refinements to the code and test functions, and a general approach to extend the capabilities into the requirements and design phases. Techniques are described that simultaneously allow different methodologies, programming languages, and target computers to be implemented on the same host computer. Also discussed is the Implementation of a SEE in a distributed computer network.     

Software Engineering Economics

This paper summarizes the current state of the art and recent trends in software engineering economics. It provides an overview of economic analysis techniques and their applicability to software engineering and management. It surveys the field of software cost estimation, including the major estimation techniques available, the state of the art in algorithmic cost models, and the outstanding research issues in software cost estimation.     

软件工程系列课程考核探索

软件教育已由面向编程转向以软件工程为中心,软件工程专业是适应信息技术发展的新兴专业,文章探索了该专业系列课程的考核模式,给出了作者的实践,介绍了《软件工程》课程及实验考核方式的研究成果,给出了《软件体系结构》课程的考核模式及《软件工程经济》课程考核模式,讨论了《软件项目管理》课程考核模式。     

Software engineering education

A primary charter of TCSE is supporting and promoting software engineering education. The paper looks at the major issues in SEE and their goals.     

Success factors of systematic reuse

Systematic software reuse is a paradigm shift in software engineering from building single systems to building families of related systems. The goal of software reuse research is to discover systematic procedures for engineering new systems from existing assets. Implementing systematic reuse is risky. Not doing it is also risky. Trying systematic reuse unsuccessfully can cost precious time and resources and may make management sceptical of trying it again. But if your competitors do it successfully and you do not, you may lose market share and possibly an entire market. There is no cookbook solution-each organization must analyze its own needs, implement reuse measurements, define the key benefits it expects, identify and remove impediments, and manage risk. Reliable data on how much this costs and the benefits an organization will derive are insufficient. The article addresses issues from management, measurement, law, economics, libraries, and the design of reusable software     

可信软件非功能需求可满足性经济学方法分析

针对软件可信性的重要性以及非功能需求的策略选取对软件可信性的影响,提出了一种在早期需求工程阶段将用于辅助决策的经济学和需求工程相结合的方法,并提出了可信软件非功能需求可满足性的策略选取框架,以辅助策略选取。首先,对功能需求及经济学方法概念进行了定义和转换,例如,将软件开发过程中的非功能需求看作经济学生产过程中的生产要素、软件的利益相关者看作生产过程中的生产者等;并定义了非功能需求分解模型。在此基础上,基于模糊集合论和信息熵对软件非功能需求进行模糊排序从而获取利益相关者的关键非功能需求,并利用经济学中生产过程的相关方法计算使用策略的可信性效益,辅助策略的选取。以移动基础维护管理平台为例,使用提出的方法,说明了所提方法的可行性。     

Behavioral economics in software quality engineering

This article describes empirical research results regarding the “history effect” in software quality evaluation processes. Most software quality models and evaluation processes models assume that software quality may be deterministically evaluated, especially when it is evaluated by experts. Consequently, software developers focus on the technical characteristics of the software product. A similar assumption is common in most engineering disciplines. However, in regard to other kinds of goods, direct violations of the assumption about objective evaluation were shown to be affected by the consequences of cognitive processes limitations. Ongoing discussion in the area of behavioral economics raises the question: are the experts prone to observation biases? If they are, then software quality models overlook an important aspect of software quality evaluation. This article proposes an experiment that aims to trace the influence of users’ knowledge on software quality assessment. Measuring the influence of single variables for the software quality perception process is a complex task. There is no valid quality model for the precise measurement of product quality, and consequently software engineering does not have tools to freely manipulate the quality level for a product. This article proposes a simplified method to manipulate the observed quality level, thereby making it possible to conduct research. The proposed experiment has been conducted among professional software evaluators. The results show the significant negative influence (large effect size) of negative experience of users on final opinion about software quality regardless of its actual level.     

Development of Software Engineering: A Research Perspective

In the past 40 years, software engineering has emerged as an important sub-field of computer science and has made significant contribution to the software industry. Now it is gradually becoming a new independent discipline. This paper presents a survey of software engineering development from a research perspective. Firstly, the history of software engineering is reviewed with focus on the driving forces of software technology, the software engineering framework and the milestones of software engineering development. Secondly, after reviewing the past academic efforts, the current research activities are surveyed and new challenges brought by Internet are analyzed. Software engineering researches and activities in China are also reviewed. The work in Peking University is described as a representative.     

Ethical issues in empirical studies of software engineering

The popularity of empirical methods in software engineering research is on the rise. Surveys, experiments, metrics, case studies, and field studies are examples of empirical methods used to investigate both software engineering processes and products. The increased application of empirical methods has also brought about an increase in discussions about adapting these methods to the peculiarities of software engineering. In contrast, the ethical issues raised by empirical methods have received little, if any, attention in the software engineering literature. This article is intended to introduce the ethical issues raised by empirical research to the software engineering research community and to stimulate discussion of how best to deal with these ethical issues. Through a review of the ethical codes of several fields that commonly employ humans and artifacts as research subjects, we have identified major ethical issues relevant to empirical studies of software engineering. These issues are illustrated with real empirical studies of software engineering.