反射式集成框架的规约描述方法研究

反射式集成框架的规约描述方法,主要研究在分布式实时应用领域基于构件的软件开发模式中集成框架的形式化规约描述问题.这种描述方法通过引入反射技术,除了描述集成框架中组成要素的业务逻辑之外,还对各要素的实时性能约束、运行时状态的变化以及可能具有的需求变更等特征进行形式化规约,从而支持软件在需求分析阶段的演化进程,并以指导与实现实时应用软件开发时业务逻辑与系统非功能性特征的关注分离.     

基于．NET的信息系统框架设计与实现

当今信息系统应用程序的规模和复杂性睾日俱增，传统的软件开发方法难以满足用户的需求。基于框架进行二次开发可以有效地提高软件的开发效率。论文首先对．NET框架进行了介绍，然后对软件开发中的通用过程进行了提炼和封装．最后提出和实现了一个基于．Net技术的企业应用系统可复用框架。     

组件化松耦企业应用集成关键技术研究

传统的软件开发模式和系统集成方法造成了企业数据孤岛和紧密耦合局面，严重阻碍企业信息化的进程，文中提出基于XML建立了产品数据共享统一模型，遵守组件软件开发规范，应用中间件技术封装企业旧系统，基于WebServices进行新系统开发，从而建立组件化松耦合企业应用集成框架。     

基于.NET的信息系统框架设计与实现

当今信息系统应用程序的规模和复杂性与日俱增,传统的软件开发方法难以满足用户的需求.基于框架进行二次开发可以有效地提高软件的开发效率.论文首先对.NET框架进行了介绍,然后对软件开发中的通用过程进行了提炼和封装,最后提出和实现了一个基于.Net技术的企业应用系统可复用框架.     

回转钻进随钻测量装置数据处理软件设计

根据回转钻进随钻测量装置数据处理软件的作用进行需求分析,详细阐述了软件各项功能的开发需求;根据软件开发需求设计了软件功能模块,阐述了各功能模块的作用,绘制了功能开发框架;根据需求和开发框架确定数据处理流程。实际应用结果验证了该软件具有良好的性能。     

软件开发和硬件平台之间呈现出来的相互关系

现阶段我国社会经济发展进程向前推进的速度较为稳定,与此同时我国所处的时代是一个知识经济时代,各项科学技术发展和应用的速度得到了大幅度的提升,因此软件开发也逐渐得到了我国社会各个行业中相关企业的重视,但是在各个企业的工作软件开发人员实际工作的过程中,一般难以对软件开发和硬件平台之间呈现出来的相互关系形成明确的了解,所以开发出来的软件在实际运行的过程中,难以满足企业的实际需求,笔者依据实际工作经验及相关文献资料的记载,针对软件开发工作和硬件平台之间呈现出来的相互非关系展开分析,向可以在今后相关的工作人员对这个问题进行分析的时候起到一定程度的借鉴性作用,最终在我国社会经济发展进程向前推进的过程中做出一定的贡献.     

软件过程的比较框架研究

软件过程在软件开发中占有非常重要的地位。根据项目的需求和特点，选择一个合适的软件过程可以使项目的开发事半功倍。为了指导软件过程的选择，本文给出了一个简明的软件过程比较框架，并依据这个比较框架，对几个典型的软件过程进行了分析和比较。     

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

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

Struts+Hibernate下实现Excel文件的导入导出

在软件开发中Excel文件的导入导出功能是经常遇到的一种需求，例如：导入由Excel保存的原始数据，利用Excel打印等。本文介绍了在stnlts＋Hibemate的框架下实现此功能的方法和实现过程。利用框架式的方法实现，不仅可以有很好的封装性，而且有很好的日志处理方法。     

基于反射的松耦合软件框架的研究

在软件开发过程中，我们经常要根据需求时软件进行更改，如果软件系统具有自我描述和自适应的能力，那么时软件的更改就可以通过修改软件系统的自描述文件来完成，这可以极大的减少更改的工作量。本文提出了基于反射的松耦合软件框架，在此框架下开发的软件可具有较好的自适应性。     

RePizer: a framework for prioritization of software requirements

The standard software development life cycle heavily depends on requirements elicited from stakeholders. Based on those requirements, software development is planned and managed from its inception phase to closure. Due to time and resource constraints, it is imperative to identify the high-priority requirements that need to be considered first during the software development process. Moreover, existing prioritization frameworks lack a store of historical data useful for selecting the most suitable prioritization technique of any similar project domain. In this paper, we propose a framework for prioritization of software requirements, called RePizer, to be used in conjunction with a selected prioritization technique to rank software requirements based on defined criteria such as implementation cost. RePizer assists requirements engineers in a decision-making process by retrieving historical data from a requirements repository. RePizer also provides a panoramic view of the entire project to ensure the judicious use of software development resources. We compared the performance of RePizer in terms of expected accuracy and ease of use while separately adopting two different prioritization techniques, planning game (PG) and analytical hierarchy process (AHP). The results showed that RePizer performed better when used in conjunction with the PG technique.     

Requirements Engineering and Downstream Software Development: Findings from a Case Study

Requirements management is being recognized as one of the most important albeit difficult phases in software engineering. The literature repeatedly cites the role of well-defined requirements and requirements management process in problem analysis and project management as benefiting software development throughout the life cycle: during design, coding, testing, maintenance and documentation of software. This paper reports on the findings of an investigation into industrial practice of requirements management process improvement and its positive effects on downstream software development. The evidence reveals a strong relationship between a well-defined requirements process and increased developer productivity, improved project planning through better estimations and enhanced ability for stakeholders to negotiate project scope. These results are important since there is little empirical evidence of the actual benefits of sound requirements practice, in spite of the plethora of claims in the literature. An account of these effects not only adds to our understanding of good requirements practice but also provides strong motivation for software organizations to develop programs for improvement of their requirements processes.     

An intelligent assistant for requirements validation

The process of determining user requirements for software systems is often plagued with uncertainty, ambiguity, and inconsistency. Rapid prototyping offers an iterative approach to requirements engineering that can be used to alleviate some of the problems with communication and understanding. Since the systems development process is characterized by changing requirements and assumptions, involving multiple stakeholders with often differing viewpoints, it is beneficial to capture the justifications for the decisions in the development process in a structured manner. Thisdesign rationale captured during requirements engineering can be used in conjunction with the rapid prototyping process to support various stakeholders involved in systems development. CAPS (the Computer Aided Prototyping System) has been built to help software engineers rapidly construct prototypes of proposed software systems. REMAP (Representation and MAintenance of Process knowledge) provides a conceptual model and mechanisms to represent and reason with (design) rationale knowledge. In this paper, we describe how in the context of evolving requirements, the CAPS system augmented with REMAP helps firm up software requirements through iterative negotiations via examination of executable prototypes and reasoning with design rationale knowledge.     

A Quality-Enhancing Software Function Deployment Model

Software quality has become a topic of increasing importance during the past decade. the quality of software is primarily determined by the quality of the software development process. Even small improvements in the software development process can result in a significant improvement in software quality. the use of software metrics technologies to assess design quality is a key issue in the management of information systems.

Software Quality Function Deployment (SQFD) is a useful requirement-gathering tool, especially in communication with users and meeting user requirements. However, software quality cannot be reviewed in isolation. Without an assessment of the goals of a project, the efficiency of software function derived from customer requirements is meaningless.

This article proposes an enhanced software quality function deployment process of integrating Goal-Question-Metrics and Software Quality Function Deployment. A software development process with this model will enhance the quality of the software. A case study is also presented to illustrate the enhanced software quality function deployment process. the main contribution of this article is to help software developers produce higher-quality software that not only meets customer requirements, but also achieves the goals of the project.     

面向不确定需求的适应性软件体系结构设计

需求不确定性是软件开发的主要风险来源之一。首先讨论了不确定需求的含义、产生的原因及其影响;然后分析了需求与软件体系结构的关系;指出了软件体系结构对满足需求和控制软件风险的重要性;提出了在不确定需求的情形下,需求分析与体系结构设计的协同建模方法及适应性软件体系结构的设计思想;论证了不确定需求情形下软件体系结构的演化过程,以保障生命周期内软件产品质量的开发思路。     

复杂软件需求开发方法研究

软件需求开发方法研究是当前复杂软件系统开发中最重要的问题之一。本文首先基于软件开发生命周期模型,对软件需求开发工作进行了介绍。进而总结了软件需求所必须包含的内容,分析了软件需求的特性。基于迭代改进的开发方法,本文将需求开发工作分解为需求捕获、需求分析、需求编写和需求确认四部分活动,并对每部分工作的详细活动和目的进行了分析和总结。软件开发工程实践证明,科学的软件需求开发方法是提高软件开发效率,提高软件开发质量的重要手段。     

The Scrum software development process for small teams

In today's software development environment, requirements often change during the product development life-cycle to meet shifting business demands, creating endless headaches for development teams. We discuss our experience in implementing the Scrum software development process to address these concerns     

Semantic decoupling: reducing the impact of requirement changes

The continuous stream of requirements changes that often takes place during software development and can create major problems in the development process. This paper defines a concept we call semantic coupling that can be used during all the phases of a system specification and design to reduce the impact of changing requirements. Within the general framework of the intent specifications, traceability matrices representing the mappings between different abstraction levels are used to evaluate the sensitivity of a given design to requirement changes. The practicality of using the approach on real software is demonstrated using the specification of the control software for a NASA robot designed to service the heat-resistant tiles on the Space Shuttle.