Automated analysis of the SCR-style requirements specifications

The SCR(Software Cost Reduction)requirements method is an effective method for specifying software system requirements.This paper presents a formal model analyzing SCR-style requirements.The analysis model mainly applies state translation rules,semantic computing rules and attributes to define formal semantics of a tabular notation in the SCR requirements method,and may be used to analyze requirements specifications to be specified by the SCR requirements method.Using a simple example,this paper introduces how to analyze consistency and completeness of requirements specifications.     

Eliciting dependability requirements: a control cases based approach

At present,great demands are posed on software dependability.But how to elicit the dependability requirements is still a challenging task.This paper proposes a novel approach to address this issue.The essential idea is to model a dependable software system as a feedforward-feedback control system,and presents the use cases+control cases model to express the requirements of the dependable software systems.In this model,while the use cases are adopted to model the functional requirements,two kinds of control cases(namely the feedforward control cases and the feedback control cases)are designed to model the dependability requirements.The use cases+control cases model provides a unified framework to integrate the modeling of the functional requirements and the dependability requirements at a high abstract level.To guide the elicitation of the dependability requirements,a HAZOP based process is also designed.A case study is conducted to illustrate the feasibility of the proposed approach.     

Managing Software Requirements Changes Based on Negotiation-Style Revision

For any proposed software project,when the software requirements specification has been established,requirements changes may result in not only a modification of the requirements specification but also a series of modifications of all existing artifacts during the development.Then it is necessary to provide effective and flexible requirements changes management.In this paper,we present an approach to managing requirements changes based on Booth’s negotiation-style framework for belief revision.Informally,we consider the current requirements specification as a belief set about the systemto-be.The request of requirements change is viewed as new information about the same system-to-be.Then the process of executing the requirements change is a process of revising beliefs about the system-to-be.We design a family of belief negotiation models appropriate for different processes of requirements revision,including the setting of the request of requirements change being fully accepted,the setting of the current requirements specification being fully preserved,and that of the current specification and the request of requirements change reaching a compromise.In particular,the prioritization of requirements plays an important role in reaching an agreement in each belief negotiation model designed in this paper.     

Knowledge Based Software Engineering for Software Development

Information revolution means that the software such as MIS developed by software engineers must be capable of rapid adaptation to constantly changing circumstances and demands in order to remain capable of effectively fulfilling their missions. The key to achieve these goals is to maintain an update understanding of the workers＇ requirements, how well thcse are currently met, and how well current and future needs might be met by conceivable solution options. This paper proposes an engineering approach of knowledge based software systems for the development and evolution of software systems. This approach captures the changing requirements of the works, together with the details of the solutions that are intended to meet them, in a repository.     

Multi-mode interaction middleware for software services

Due to the independency, variability, and tailorability of software service in the open environment, the research of middleware which supports software services multi-mode interaction is thus of great importance. In this paper, an agent-based multi-mode interaction middleware model and its supporting system for software services were proposed. This model includes an interaction feature decomposition and configuration model to enable interaction programming, an agent-based middleware model, and a programmable coordination media based on reflection technology. The decomposition and configuration model for interaction features can assist programmers in interaction programming by analyzing and synthesizing interaction features. The agent-based middleware model provides a runtime framework for service multi-mode interaction. The programmable coordination media is able to effectively support software service coordination based on multimode interaction. To verify feasibility and efficiency of the above method, the design, implementation and performance analysis of Artemis-M3C, a multi-mode interaction middleware for software services, were introduced. The result shows that the above method is feasible and that the Artemis-M3C system is practical and effective in multi-mode interaction.     

An Empirical Study on the Impact of Automation on the Requirements Analysis Process

Requirements analysis is an important phase in a software project. The analysis is often performed in an informal way by specialists who review documents looking for ambiguities, technical inconsistencies and incomplete parts. Automation is still far from being applied in requirements analyses, above all since natural languages are informal and thus difficult to treat automatically. There are only a few tools that can analyse texts. One of them, called QuARS, was developed by the Istituto di Scienza e Tecnologie dell＇Informazione and can analyse texts in terms of ambiguity. This paper describes how QuARS was used in a formal empirical experiment to assess the impact in terms of effectiveness and efficacy of the automation in the requirements review process of a software company.     

Software Information Base（SIB）and Its Integration with Data Flow Diagram（DFD）Tool

Software in formation base is the main technique of the integration of software engineering environment.Data flow diagram tool is an important software tool to support software requirement analysis phase.This article introduces the functions,structures of a Software Information Base(SIB),and a Data Flow Diagram tool first.The E-R data model of SIB and its integration with Data Flow Diagram tool are emphatically described.     

基于Bayes网的软件失效预测模型

Owing to the complexity of software development,the software reliability model should not only have the capability of dealing with multiple complex factors,but also provide the furtction of flexibility in construction.So far,no software reliability model is universally applicable.The main reason for this is of too many conditions ,thus making software reliability models introvert.Bayesian network is a powerful tool for solving this problem,which exhibits strong adaptability in dealing with problems involving complex variant factors.In the paper,software failure predication model based oft Markov.Bayesian network is established and analyzed thoroughly.Then a method of solving the model is given.Finally,through an example the validity of the model is validated.     

A Component-Based Software Configuration Management Model and Its Supporting System

Software configuration management(SCM)is an important key technology in software development.Component-based software development (CBSD)is an emerging paradigm in software development.However,to apply CBSD effectively in real world practice,supporting SCM in CBSD needs to be further investigated.In this paper,the objects that need to be managed in CBSD is analyzed and a component-based SCM model is presented.In this model,Components,as the integral logical constituents in a system,are managed as the basic configuration items in SCM,and the relationships between/among components are defined and maintained.Based on this model.a configuration management system is implemented.     

一种混沌理论下的需求演化模型

需求的不确定性和易变性一直是影响软件生命周期,困扰软件开发效率和开发质量的重要因素。通过对动力系统和软件复杂性理论的研究,提出了一种混沌演化模型,该模型可以对软件需求的演化过程进行指导,同时也可以评价需求过程的质量。研究表明,只要需求演化过程的变化图和模型的轨迹图一致,那么需求的演化过程就可以看成是正常的。通过对具体实例的分析,进一步说明了该模型在评价需求演化过程上是有效可行的。     

具有不确定需求的软件测试用例生成方法研究

软件测试是软件开发重要的一部分,是保证软件质量,提高软件可靠性的重要途径。测试在需求分析阶段就开始介入,而在现实中很多需求是不确定的,在软件测试的过程中会面临许多不确定性的挑战。主要研究具有不确定需求的软件测试用例生成方法,利用基于标记迁移系统的Partial Models（部分模型）对不确定的需求进行建模,进而基于建立的模型生成有效的测试用例。针对模型中具有的不确定性引入概率,对不确定的部分进行概率表示,进一步基于标记迁移系统和Partial Models的特点提出测试用例生成方法。由于模型中具有不确定信息,由此生成的测试用例具有一定的概率,基于此对测试用例进行优先级排序。     

基于UML用例图的软件产品线需求建模方法

软件产品线方法是一种面向特定领域的、大规模、大粒度的软件复用技术。明确建模和描述软件产品线需求是软件产品线开发的关键问题之一。而传统的UML用例图等方法不足以完整描述产品线需求,特别是其变化性。通过分析软件产品线开发过程和软件产品线需求建模的特殊性,采用扩展UML用例图标签的方法,实现对软件产品线需求的明确描述。以网络图书销售软件产品线为例,进行具体说明。     

面向软件动态演化的需求建模及其模型规范化

针对目前需求工程阶段对软件动态演化考虑不足的现状,在分析软件动态演化面临的挑战的基础上,设计了面向动态演化的需求元模型(dynamic-evolution-orientedrequi rements meta-model,DERM)。该元模型以特征为基本部件,按特征组合的方式建立需求模型,需求模型由行为特征和属性特征组成。行为特征被区分为计算行为特征和交互行为特征,以实现计算和交互的相对隔离;属性特征通过其作用域,指定其在行为特征模型中的作用范围,从而将行为特征模型和属性特征模型统一为需求模型。在此基础上,讨论了需求模型的参照完整性、依赖一致性和互斥一致性,并进一步把需求模型规范化为需求模型第一范式到第三范式,需求模型规范化的过程提供了一种保证需求模型一致性的方法。最后通过案例研究,表明了该方法的可行性及其对软件动态演化的有效支持。     

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

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

面向Agent的分析与建模

传统分析方法注重目标软件系统的功能,分析的结果是一个完全,一致和无二义的软件需求规范。     

从用户需求到软件规约：一种问题变换的方法

研究的目的是在获取用户需求和领域描述的基础上规约出对软件规格的描述.提供了一种实现从用户需求到软件规约的平滑和可推理的变换方法.在深入研究问题框架方法的基础上,采用Hoare 的通信顺序进程语言CSP及Lai的最弱环境演算符实现了整个问题图的变换,且导出的软件规格是具有高抽象粒度的程序代码模型,能够被FDR模型检测工具所验证.该工作为实现嵌入式软件开发从需求到软件代码、文档的自动转化及验证等奠定了理论基础.此外,把该理论与模型检测工具FDR联合起来会有助于提高嵌入式软件开发的效率和准确性.     

基于OWL的软件工程数据建模

网络本体语言(Web ontology language,OWL)是语义网技术的一个重要组成部分,适合于对复杂的数据进行语义描述和建模.在软件系统的开发过程中通常会产生大量结构复杂、语义丰富的数据,而建立一个灵活的语义模型是对各类软件工程数据进行统一管理的基础.从设计和实现海量软件工程数据管理平台的需求出发,提出了一种基于OWL的软件工程数据描述模型.该模型不仅能够对源代码、需求、测试、版本和缺陷数据进行描述,同时还能对这些数据之问的语义关联进行描述.通过案例分析对模型的有效性进行了讨论.     

基于UML的软件形式化需求分析与验证

针对软件开发中传统的需求分析方法所存在的需求描述不完整、具有二义性和不一致性问题,提出一种形式化需求分析方法。介绍根据用户需求采用形式化方法获取软件需求说明书并设计软件的统一建模语言（UML）模型的过程,及对该UML模型进行形式化描述,采用形式化验证技术对形式化后的UML模型进行需求验证,以确保设计的UML模型的正确性。实验结果表明,形式化的需求分析方法克服了传统需求分析方法中存在的问题。