共查询到20条相似文献,搜索用时 15 毫秒
1.
特征模型是面向特征的软件开发过程的重要概念和制品,该模型以特征为单位,刻画了领域产品的共性和可变性.在日趋频繁的软件演化过程中,保持特征模型的一致演化,对于支持高效的复用开发和按需配置至关重要.目前,大多数的研究是在需求层面进行共性和可变性分析,对特征模型的研究则集中在对共性和可变性的建模上.但是,由于特征变更在建模过程中存在\"涟漪\"效应,会导致新的共性和可变性演化.现有的分析方法还无法解决这个问题,会导致丢失一些潜在的产品共性,从而影响复用的效率.提出了一种特征模型扩展和演化分析方法.通过扩展特征关联关系和模型演化元操作,实现对特征变更\"涟漪\"效应的分析.发现潜在的产品共性,提出重构策略和半自动化的共性提取和特征重构支持方法.该方法还针对典型的配置冲突提出了冲突消解规则和策略.最后,通过案例分析验证了该方法的可用性和有效性. 相似文献
2.
The strategy of retrofitting quality onto a prototype and evolving it into a production quality system has at best led to severe problems and at worst to a complete failure. The present work reports on an environment and methodology that supports the development of high quality prototypes that can easily accommodate changes so that the prototypes can be evolved into production quality systems. An outline of the environment incorporating an architectural mechanism and associated tools that accommodates the intertwining of algebraic specifications, known as ADTSPEC, and implementations in a modular programming language, PARADOX PASCAL, is presented. A framework for applying the environment in the context of evolutionary development is detailed. An illustrative application is also presented. It demonstrates the effectiveness of the work, to support user participation at each stage of evolution and the engineering of high quality prototypes constructed in a systematic manner, incorporating the degree of rigour that is appropriate to the clarity of requirements. 相似文献
3.
基于本体的可信软件演化框架模型* 总被引:1,自引:0,他引:1
为系统化地考虑开放环境对软件可信性的影响和驱动作用,提出了一种基于本体空间并支持动态演化的框架模型。该模型采用本体空间的方法解决用户、系统和环境三者之间交互的语义问题,在此基础上,通过预定义的规则对软件行为的可信性和自主调整的必要性进行评估,依据评估结果从微观层次的规约制导和宏观层次的人机协同在软件生命周期内对其调整、配置与修正。应用实例及测试结果验证了该框架模型的有效性与可行性。 相似文献
4.
5.
软件特征定位是成功实施软件演化意图的前提条件。针对当前特征定位方法准确率低,定位空间庞大和自动化程度不高等问题,提出了一种面向行为主题的混合特征定位方法。该方法将软件系统的行为知识和主题知识进行有机整合,实现了行为知识对主题知识的约简,并最终通过分析主题知识与软件功能属性间的相似性实现特征定位。实验结果表明,与传统的基于文本的特征定位方法相比,该方法具有较好的查全率、查准率和综合性能,从而验证了该方法的有效性。 相似文献
6.
Orla Greevy Stphane Ducasse Tudor Gîrba 《Journal of Software: Evolution and Process》2006,18(6):425-456
Features encapsulate the domain knowledge of a software system and thus are valuable sources of information for a reverse engineer. When analyzing the evolution of a system, we need to know how and which features were modified to recover both the change intention and extent, namely which source artifacts are affected. Typically, the implementation of a feature crosscuts a number of source artifacts. To obtain a mapping between features and the source artifacts, we exercise the features and capture their execution traces. However, this results in large traces that are difficult to interpret. To tackle this issue we compact the traces into simple sets of source artifacts that participate in a feature's runtime behavior. We refer to these compacted traces as feature views. Within a feature view, we partition the source artifacts into disjoint sets of characterized software entities. The characterization defines the level of participation of a source entity in the features. We then analyze the features over several versions of a system and we plot their evolution to reveal how and which features were affected by code changes. We show the usefulness of our approach by applying it to a case study where we address the problem of merging parallel development tracks of the same system. Copyright © 2006 John Wiley & Sons, Ltd. 相似文献
7.
8.
N. A. M. Maiden 《Information and Software Technology》1991,33(10):780-790
Analogy is proposed as an alternative paradigm for the reuse of specifications during requirements analysis. First, critical determinants of analogies between software engineering problems are discussed in relation to a specification retrieval mechanism. Second, the process of specification reuse is examined. Specification reuse by analogy is knowledge-intensive, hence an important role is proposed for the analyst during specification reuse: analyst involvement would appear necessary to categorize a new problem, select between candidate reusable specifications, and customize the selected specification to the new domain. Finally, a specification reuse tool is proposed that recognises the collaborative nature of reuse by analogy. This tool assists and advises the analyst during reuse founded on cognitive models of analyst behaviour during analogous reasoning and reuse. The prototype version of this intelligent reuse advisor (Ira) is outlined. 相似文献
9.
Specification-Based Browsing of Software Component Libraries 总被引:6,自引:0,他引:6
Bernd Fischer 《Automated Software Engineering》2000,7(2):179-200
Specification-based retrieval provides exact content-oriented access to component libraries but requires too much deductive power. Specification-based browsing evades this bottleneck by moving any deduction into an off-line indexing phase. In this paper, we show how match relations are used to build an appropriate index and how formal concept analysis is used to build a suitable navigation structure. This structure has the single-focus property (i.e., any sensible subset of a library is represented by a single node) and supports attribute-based (via explicit component properties) and object-based (via implicit component similarities) navigation styles. It thus combines the exact semantics of formal methods with the interactive navigation possibilities of informal methods. Experiments show that current theorem provers can solve enough of the emerging proof problems to make browsing feasible. The navigation structure also indicates situations where additional abstractions are required to build a better index and thus helps to understand and to re-engineer component libraries. 相似文献
10.
为了有效协调管理和配置结构健康监测的硬软件系统,初步研究了结构健康监测的软件主体协作规范。首先研究了健康监测目前已有的相关规范,讨论分析了它们彼此之间的关系;然后,对软件主体协作规范进行研究,重点是FIPA规范的5个主要规范,为结构健康监测的软件主体协作规范提供指导和应用基础;最后,针对结构健康监测系统的需求,参照上述规范,提出了适合于结构健康监测系统的软件主体协作规范。以大型航空铝板结构为例,验证所提出的软件规范。 相似文献
11.
12.
需求变化是导致软件演化的根本原因,而问题空间与解空之间存在的缺口是软件难以成功演化的根源。通过系统接口,把变化的需求与支持它的特征迹联系起来,定义了基于需求和特征迹的软件演化。根据需求的不同,把软件演化分为功能演化、非功能演化和环境演化,并对软件演化方法进行了讨论。根据特征迹的私有消息、局部消息和公有消息之间的关系,对演化影响进行了定量分析,得到了可演化软件的一些性质。基于特征迹的软件演化,有利于演化定位、演化管理和演化的验证. 相似文献
13.
Xinyu Wang Jie Sun Xiaohu Yang Ye Wang Shanping Li Aleksander J. Kavs 《Expert Systems》2013,30(3):200-214
While Problem Frames have become a useful approach for requirements analysis, little research has been made to explore how to derive them from a complex problem context. The purpose of this paper is to propose such an approach. The proposed approach consists of three steps to drive the development of Problem Frames. In the first step, business process models are developed to capture the behavioural view of the problem context. In the second step, object analysis models are used to capture the structural view of the problem context. Together, these two views collectively and adequately capture the early context knowledge. These two types of model will then be used in the third step to construct context diagrams and derive Problem Frames. A complex real‐world problem – equity trading problem – is used to illustrate this approach. 相似文献
14.
软件需求规格说明自动生成工具 总被引:1,自引:0,他引:1
首先提出了一种面向业务流的需求分析方法,并给出了相应的条件有向图需求描述模型(CDGRD),然后详细地介绍了基于CDGRD的软件需求规格说明自动生成工具,最后以某大型企业信息系统项目为例,详细讨论了CD-GRD描述方法以及该自动生成工具的具体应用. 相似文献
15.
为了清晰、全面地获取构件化软件的演化历史信息, 通常需要提供演化信息表示和建模的有效手段。分析了构件化软件演化信息获取所需解决的若干问题, 提出了在软件构件模型基础上, 增加建模元素以表示软件演化信息的方法; 通过结合软件配置管理系统, 实现对构件化软件变化过程的追踪和管理。基于该方法和相应的系统支持, 可以为实施软件重构和后期开发提供指导。 相似文献
16.
17.
通过在软件体系结构层次实施软件重构,能够改善软件的质量、提高软件的易演化性。提出了基于演化信息实施软件体系结构重构的策略,通过分析体系结构的演化历史,采用概念格的方法分析其中构件间的演化依赖关系,从而达到改善体系结构质量的目的。 相似文献
18.
Abstract: Problem frames and assurance cases are two current research areas that can improve – and have improved – system dependability, in critical and noncritical systems alike. While these two techniques are effective separately, their synthesis is much more powerful. This paper describes the synthesis of these two techniques and the rationale behind the synthesis, the particular pieces that influence each other, and the beginning of a process to integrate the two in software system development. A detailed example of the application of the synthesis is also provided. 相似文献
19.
模拟执行是一种重要的需求规格说明书(SRS)的检测方法。文章基于面向嵌入式实时系统的需求描述模型RTRSM,提出了如何将组件化的思想和技术应用于模拟执行的检查方法中,从而增加了SRS的可靠性和正确性。最后,文章提出了根据需求描述模型直接生成框架代码的构想,这也是一种从需求直接生成嵌入式实时系统的探索。 相似文献