软件需求工程——方法及工具

文中从需求工程的基本概念和研究内容出发,简单介绍了需求工程生命周期和需求规范等概念;比较全面地总结了现有的有代表性的需求工程开发方法和工具,对其中一些重要的方法及工具作了分类和评述。     

软件需求工程——方法及工具

文中从需求工程的基本概念和研究内容出发,简单介绍了需求工程生命周期和需求规范等概念;比较全面地总结了现有的有代表性的需求工程开发方法和工具,对其中一些重要的方法及工具作了分类和评述.     

软件需求工程中常见问题及解决办法

从需求工程的主要内容出发,总结出了在需求工程中的常见问题,提出了一些解决办法。重点介绍了进行需求验证的方法和准则。     

一种基于MBSE的飞行传感器系统需求建模方法

针对传统的基于文档式的需求工程方法无法满足当前复杂系统的需求分析,论文提出一种基于模型系统工程(Model-Based Systems Engineering,MBSE)思想的传感器系统需求建模分析的方法,辅以DOORS工具对需求进行管理。首先,基于DOORS对飞行传感器系统的需求管理进行研究,以支持系统的需求演进,方便后续的需求建模分析;其次,在Rhap?sody环境下采用SysML用例图对飞行传感器系统需求进行静态建模分析,从参与者的角度分析系统需求用例;最后,通过对某型号无人机传感器系统应用实例的分析来验证该方法的有效性和可行性。     

软件项目需求波动风险分析及对策

从需求波动风险的定义出发,总结了需求波动形成的原因和对软件项目的影响,列举了一些代表性的风险分析和评估方法。最后提出了基于面向对象方法的系统需求工程的分析设计思路。     

应用软件开发的需求风险及控制

在应用软件开发过程中,由于软件需求本身的隐含性、用户与开发者之间的沟通障碍,以及需求随着时间、用户的变化而变更等原因,可能使需求分析偏离实际需求而最终导致软件开发的失败,这种可能性称为需求风险。需求分析是软件开发过程中最初始、最基础的工作,也是最重要的工作之一,其成败将直接并最终决定软件开发的成败,并且呈倍增效应。需求分析的关键是使隐含的需求明确,使变更的需求可控,采用座谈会、需求调查表、需求启发、角色扮演等方法可以使需求明确化;采用面向对象的方法及UML工具、领域专家的全程参与、需求分级、二次开发接口等方法可以使需求变更处于可控范围内。实践证明,这些都是控制需求风险的有效方法。     

基于产品线需求分析的过程改进研究

以简化软件产品线中的需求分析过程、实现过程复用为目的,总结了当前软件生产线需求分析的特点以及分析过程,通过建立领域用户需求模型指导需求获取分析过程,采用基于改进原型法的需求获取方法,基于领域用户需求模型建立需求复用库,引入本体描述用户需求模型等方法,对软件产品线的需求分析过程进行了改进,并设计实现了一套图形化需求建模工具,有效地简化了需求分析过程,实现了过程复用。其研究结果应用到了D2G软件生产平台中。     

安全需求工程研究综述

近年来,安全需求工程逐渐成为软件工程领域的研究热点之一。在开发周期的早期阶段引进安全分析和安全工程实践比在应用设计阶段才引进分析的投资回报要高出12%-21%。归纳安全需求工程发展过程及其主要研究活动,给出安全需求工程的相关定义,并分析了几个典型的安全需求工程框架。通过总结安全需求工程领域的若干研究活动,提出安全需求工程研究的两大思路,并从6个方面介绍安全需求工程的研究进展,探讨安全需求工程研究存在的不足。作为总结,给出了安全需求工程领域最有前途的发展方向。     

可信软件需求获取与分析研究综述及展望*

需求获取与分析是可信软件领域的研究热点,近年来得到了广泛的关注和快速的发展。首先分析了中小型软件系统中需求获取方法与分析方法的国内外研究现状,接着对新近出现的可信软件中需求获取与分析方法进行了分析和综述;最后对需求获取与分析方法的研究动态进行了总结与展望。     

基于SysML的需求分析研究

现在的系统一般都包括软件和硬件,需求分析在系统的生命周期中是非常重要的阶段.如果需求分析做的不好,会带来诸如项目失败、成本超出预算、延后等一系列问题.系统越复杂,需求分析活动就越发重要和困难.针对需求工程,提出了基于SysML进行需求分析的方法.该方法的主要优点是用户需求以图形化建模的方式表示,需求的关系被显示映射,系统分解在系统开发活动的早期就可以被考虑.最后,针对可信系统的用户需求,使用该方法进行了演示.     

面向过程分析的需求自动生成工具POSRAG

该文从需求工程的重要性出发,通过研究现有的需求分析方法和工具,发现其存在的问题,提出一种面向过程的需求分析技术,并在此基础上设计一套软件需求自动生成工具POSRAG(Process-OrientedSoftwareRequirementsAutomaticGenerator),其主要特征是以可视化过程建模为基础,通过正确的引导和提示,帮助用户和设计人员获取完整的用户需求,完成软件需求分析,并自动生成需求文档。文章详细描述了该系统的设计方案和实现过程。     

Formal methods and requirements engineering: Challenges and synergies

Formal methods (FM) are already making important contributions to both theory and practice in the field of requirements engineering (RE). This article presents an overview of work in this area drawing on discussions and presentations which took place at an international workshop held in December 1996. Our aim is first to outline the current demonstrated capability of FM to support RE and then to present some of the recent developments which seem most likely to result in practical methods in the near future. Some of the significant themes identified are: the use of theorem-provers and model-checking tools, the application of formally-based requirements acquisition strategies, development of reusable software architectures which can anchor requirements elaboration, and formal treatment of inconsistency and the use of multiple notations.     

Supporting scenario-based requirements engineering

Scenarios have been advocated as a means of improving requirements engineering yet few methods or tools exist to support scenario based RE. The paper reports a method and software assistant tool for scenario based RE that integrates with use case approaches to object oriented development. The method and operation of the tool are illustrated with a financial system case study. Scenarios are used to represent paths of possible behavior through a use case, and these are investigated to elaborate requirements. The method commences by acquisition and modeling of a use case. The use case is then compared with a library of abstract models that represent different application classes. Each model is associated with a set of generic requirements for its class, hence, by identifying the class(es) to which the use case belongs, generic requirements can be reused. Scenario paths are automatically generated from use cases, then exception types are applied to normal event sequences to suggest possible abnormal events resulting from human error. Generic requirements are also attached to exceptions to suggest possible ways of dealing with human error and other types of system failure. Scenarios are validated by rule based frames which detect problematic event patterns. The tool suggests appropriate generic requirements to deal with the problems encountered. The paper concludes with a review of related work and a discussion of the prospects for scenario based RE methods and tools     

Sharing requirements engineering experience using patterns

Many practitioners - especially those in small and medium enterprises -work in organizations that don't yet implement dedicated requirements engineering methods. Furthermore, these organizations often lack the appropriate knowledge and tools for implementing RE. For this target group of practitioners, we propose patterns as a format for RE knowledge transfer, which can provide guidance by offering easy access to proven methods and tools. As an example, we provide four patterns for basic RE activities.     

嵌入式实时系统的软件需求检测

以需求描述模型HRFSM(hierarchical finite state machines based on rules)为基础,提出了一个嵌入式实时系统软件的动态执行模型(dynamic execution model,简称DEM)和基于该模型的检测方法.由于DEM能将控制流、数据流和时间有效地集成为一体,故提出的检测方法能检测嵌入式实时系统的软件需求的一致性和完全性.该检测方法由3种侧重点不同的检测形式组成,并能在检测过程中提供一些重要的检测信息.分析员可以利用基于该检测方法的工具灵活地对嵌入式实时系统的软件需求进行检测,以提高分析和检测软件需求的效率.     

Determining Stakeholder Needs in the Workplace: How Mobile Technologies Can Help

Mobile technologies offer exciting new opportunities to improve important requirements processes. However, providing usable, useful mobile requirements engineering (RE) tools is challenging due to mobile devices' limitations and limited knowledge on successfully using mobile RE tools in the field. You can use the reported lessons learned as an initial guide to develop and use mobile RE tools successfully. We believe that mobile RE tools will complement rather than replace traditional approaches, and the combination of context-aware and conventional elicitation and negotiation approaches has the potential to improve the quality of requirements. Evaluation studies also revealed several issues, including biases arising from the limited information available on mobile devices; integrated training, process guidance, and tool support for analysts; and guidance for end users to discover and document their own requirements. Further work in the mobile RE field is needed to address these issues. Mobile RE tools help elicit stakeholder heeds in the workplace. The authors discuss lessons learned that practitioners can adopt and use in their work     

Bayesian networks for enhancement of requirements engineering: a literature review

Requirements analysis is the software engineering stage that is closest to the users’ world. It also involves tasks that are knowledge intensive. Thus, the use of Bayesian networks (BNs) to model this knowledge would be a valuable aid. These probabilistic models could manage the imprecision and ambiguities usually present in requirements engineering (RE). In this work, we conduct a literature review focusing on where and how BNs are applied on subareas of RE in order to identify which gaps remain uncovered and which methods might engineers employ to incorporate this intelligent technique into their own requirements processes. The scarcity of identified studies (there are only 20) suggests that not all RE areas have been properly investigated in the literature. The evidence available for adopting BNs into RE is sufficiently mature yet the methods applied are not easily translatable to other topics. Nonetheless, there are enough studies supporting the applicability of synergistic cooperation between RE and BNs. This work provides a background for understanding the current state of research encompassing RE and BNs. Functional, non-functional and -ilities requirements artifacts are enhanced by the use of BNs. These models were obtained by interacting with experts or by learning from databases. The most common criticism from the point of view of BN experts is that the models lack validation, whereas requirements engineers point to the lack of a clear application method for BNs and the lack of tools for incorporating them as built-in help functions.     

Requirements engineering for multi-channel services: the SEB method and its application to a multi-channel bank

The widespread usage of technology for service provision to customers has created a new and challenging environment for the design of interactive systems, with the emergence of technology enabled multi-channel services. Requirements engineers involved in the design of such service systems must actively work together with interaction designers and service managers to better integrate customer service experience and technology components, requiring unifying methods and tools within the emerging field of service science management and engineering. This paper proposes the service experience blueprint (SEB), a multidisciplinary method for the design of technology enabled multi-channel service systems and illustrates its application in two examples of redesign of banking services that involved an extensive study with more than 4,000 bank customers. The SEB method is based on concepts and tools from RE and interaction design, such as goal-oriented analysis and conceptual modeling, but also uses methods developed in the service and marketing fields, such as service blueprinting. SEB brings marketing research methods to the requirements process, as they can provide a useful contribution for the elicitation of customer experience requirements in service environments. By bringing together goal-oriented modeling and use case modeling from requirements engineering, with service blueprinting from service design, the SEB method contributes to creating a shared understanding and a unifying language to better support the design of new technology enabled multi-channel service systems, where technology and service issues are deeply intertwined.