面向方面的软件产品线需求建模

为了将软件产品线的横切关注点在开发的早期阶段分离出来,完成系统分析向设计阶段的顺利过渡,提出了一种面向方面的软件产品线需求分析模型,并给出该模型需求分析的基本步骤.通过冷库管理系统的实例,给出了识别和描述功能需求、非功能需求和横切关注点的方法,利用UML类图完成方面和功能整合,在此基础上介绍了用关系矩阵和合并非功能需求集合的方法来描述非功能需求.实验结果表明,该方法能够有效简化软件产品线需求建模的复杂性.     

基于软件产品线的需求分析研究

软件产品线方法是一种面向特定领域的、大规模、大粒度的软件复用技术.在软件产品线的开发过程中,产品线需求分析是软件产品线开发的关键活动之一,软件产品线需求分析奠定了产品线构架的基础.通过分析软件产品线开发过程和软件产品线需求分析的特点,阐述了软件产品线需求分析方法以及软件产品线需求分析的实践风险.以领域分析和建模为切入点,对软件产品线的领域分析、需求建模和用例建模等关键方法和技术进行了重点的研究.     

一种基于UML的软件产品线可变性建模方法

将UML引入到软件产品线开发中,在产品线可变性分析的基础上,提出了一种基于UML的产品线可变性建模方法。该方法不仅支持可选、多选一等可变点类型的描述,还支持软件产品线可变性的约束建模。在此基础上,还通过一个手机应用软件的产品线可变性建模实例验证了该方法的有效性。     

基于UML的软件产品线建模方法研究

软件产品线方法是一种面向特定领域的、大规模、大粒度的软件复用技术。文章简要介绍了基于UML的软件产品线建模方法。由于软件产品线对于产品线成员公共性和变化性的特殊关注,其用例模型、交互模型、状态模型、静态模型、特征模型和单一软件系统相比都有所区别。文章对各种模型进行描述的同时,以报业排版软件产品线样张打印功能为例,进行具体说明。     

一种基于UML建模的实时测控系统设计

为了实现软件产品工程化、标准化的目标,在实时测控软件的开发过程中需要引入现代软件工程思想和方法来规范开发流程、保证软件质量.由于实时测控软件特殊应用领域,实时测控软件通常采用模块化设计方法和多层次体系结构.在软件建模方面,UML建模方法也被用于对实时测控软件进行建模.在实时测控系统软件的开发过程中,本文采用了多层次的体系结构,并分别采用UML用例图、类图和顺序图对软件的功能、结构和信息活动进行建模,最终完成软件系统的构建.     

基于场景元模型的软件产品线追踪方法

针对软件产品线需求追踪方法进行了研究,基于软件产品线领域需求分析、设计、实现三个阶段的信息传播,提出了一种基于场景元模型的多层次软件产品线追踪模型,完整描述了追踪信息变化的整体框架;建立了需求—用例追踪矩阵、用例—动作追踪矩阵、动作—构件追踪矩阵;根据矩阵运算,描述了具体追踪实现过程,通过一个ATM案例验证了该方法对于软件产品线领域需求获取以及需求变更等问题的解决有较好的效果。     

基于模型对比和组合的软件产品线领域需求建模

软件产品线作为系统化的软件复用方式,可以提高软件的开发效率和质量.软件产品线变化性建模是软件产品线的关键技术,通过建立变化性模型以记录软件产品线成员产品的共性和变化性.目前的软件产品线变化性建模方法大都通过领域专家进行分析建立,这种方法过度依赖于领域专家的分析能力,在系统规模较小的情况下,变化性分析比较容易,但是如果系统规模变大,则系统的规模对于变化性分析的影响会越来越大.文中提出一种半自动的软件产品线领域需求建模方法,基于关注点分离的思路,利用特征模型表示软件产品线中系列产品的不同方面的特征信息,通过特征模型的对比和组合实现领域需求模型的构建.为有效地实现特征模型对比与组合,文中提出一种基于标记和结构的特征模型对比方法,同时,文中实现了基于约束的特征模型组合.基于公开的特征模型,文中对提出的方法进行了验证,实验结果表明,文中提出的领域需求建模方法能够在一定准确率的情况下有效地实现领域需求模型的构建.     

基于UML建模思想的查课系统的规划

本文论述了应用UML建模思想分析和规划了智能查课系统的开发过程,确定系统需求和要实现的功能。用表示系统静态特征的UML类图、用例图和描述系统动态行为特征的时序图对其开发过程进行了不同层面的描述,以便读者理解。     

基于UML的精品课程远程教育网站模型设计

UML是面向对象的统一建模语言,所设计的软件模型具有可重用性的特点。使用UML新方法开发精品课程网站,用UML用例图做需求分析,用UML类图和顺序图进行系统静态和动态设计,最终用PHP程序语言和MYSQL数据库来实现网站软件。经UML建模后的精品课程远程教育网站模型可以多次应用,从而提高网站软件的开发效率。     

产品线可变性的需求方法研究

软件产品线领域需求记录了不同软件产品的共性和可变性。在现有需求过程框架下,对产品线需求获取方法与需求分析方法进行了研究,完善了产品线需求可变性的管控机制。以原子需求为视点,提出了利用需求场景获取产品线领域需求的方法;通过原子需求构建的产品需求矩阵与用例需求矩阵,分析得出需求资源的可变性关系;通过可变性关系的形式化描述,建立产品线可变性用例模型。     

Managing requirements specifications for product lines - An approach and industry case study

Software product line development has emerged as a leading approach for software reuse. This paper describes an approach to manage natural-language requirements specifications in a software product line context. Variability in such product line specifications is modeled and managed using a feature model. The proposed approach has been introduced in the Swedish defense industry. We present a multiple-case study covering two different product lines with in total eight product instances. These were compared to experiences from previous projects in the organization employing clone-and-own reuse. We conclude that the proposed product line approach performs better than clone-and-own reuse of requirements specifications in this particular industrial context.     

Identified adjustability dimensions when generating a product specific requirements specification by requirements reuse

A requirements reuse setups typically includes reusable requirement set(s) containing a collection of reusable requirements and a number of product specific requirements sets which are drawn from the reusable set(s). The ideal scenario when reusing requirements is that all the product requirements can be drawn directly from the reusable set. However, this is rarely the case in product development as new requirements are likely to surface. A critical issue in requirements reuse therefore becomes how to enable products to efficiently reuse requirements as well incorporating changes to the product set. In this paper the objective is not to present a specific method for requirements reuse but to introduce and discuss the possible dimensions of adjustability when generating a product requirement set by reusing requirements from a reusable set. Six adjustability dimensions have been identified. An extensive state of the art is included to introduce the presented methods related to each adjustability dimensions. The options for implementing each adjustability dimensions in a requirement reuse approach are illustrated along with a discussion regarding the benefits and issues resulting from each option. This discussion should help practitioners to better understand the possible methods that can be implemented and to design a user friendly and sustainable approach. A case study, describing how the dimensions are incorporated in two requirements reuse approaches, for Danfoss Solar Inverters (SI) and Danfoss Frequency Drives is provided. As a result an overview of how each adjustability dimensions is implemented in each case is presented. The case study demonstrates that all the identified adjustability dimensions were important elements in requirements reuse implementation. The case study furthermore highlights the need, not only to understand the effects of each adjustability dimension but also of the dependencies to case specific criterions. The classification of adjustability dimensions in requirements reuse and the options for their implementation has not been outlined by previous research and should be a useful contribution both to researchers and practitioners working in the field of requirements reuse.     

面向软件产品家族的变化性建模方法

用户需求和运行环境的变化增加了软件产品开发、维护和演化的难度.另一方面,如果能对同类软件(比如软件产品家族)的变化性实施有效的控制,则可以极大地促进软件复用,提高软件生产效率和质量.对变化性建模是控制变化性的有效手段,既有助于变化性的识别和规约,又能够提供足够的机制支持变化性的演化.提出了一种面向产品家族的变化性建模方法,以变化性的管理策略为指导,从扩展的用况(use case)模型入手捕获系统行为的变化性,以特征模型来组织功能性需求和质量属性并识别其变化性,两种模型对变化性的建模采用相同的机制.还结合一个实例讨论了产品家族变化性建模的全过程.该研究对产品家族变化性的分析与建模具有一定的参考作用.     

An approach to developing domain requirements as a core asset based on commonality and variability analysis in a product line

The methodologies of product line engineering emphasize proactive reuse to construct high-quality products more quickly that are less costly. Requirements engineering for software product families differs significantly from requirements engineering for single software products. The requirements for a product line are written for the group of systems as a whole, with requirements for individual systems specified by a delta or an increment to the generic set. Therefore, it is necessary to identify and explicitly denote the regions of commonality and points of variation at the requirements level. In this paper, we suggest a method of producing requirements that will be a core asset in the product line. We describe a process for developing domain requirements where commonality and variability in a domain are explicitly considered. A CASE environment, named DREAM, for managing commonality and variability analysis of domain requirements is also described. We also describe a case study for an e-travel system domain where we found that our approach to developing domain requirements based on commonality and variability analysis helped to produce domain requirements as a core asset for product lines.     

从领域需求到产品线体系结构的映射——一种面向特征的方法

领域需求之间的依赖关系对软件产品线的体系结构有很大的影响,在已有的面向特征的管理产品线需求依赖的方法中很少有研究从需求到产品线体系结构的映射.基于一种特征依赖的分类方法,提出了从领域需求到特征,以及从特征到产品线体系结构的映射规则.通过这些映射规则,一致的需求通过映射得到一致的产品线核心资产,从而减少产品线中核心资产的不一致性并增加产品线的复用程度.用金融领域的现货交易产品线作为实例说明这个方法的实用性.     

基于产品线工程方法提高组件容器的可复用性(英文)

组件容器为组件提供部署和运行环境,是基于组件的分布式应用开发的核心。近年来,开发网构软件的需求驱动着组件技术持续改进,新型组件不断涌现,这对组件容器的开发效率提出更高的要求。因此,在组件容器开发过程中大规模复用已有的软件资产变得非常重要。在许多情况下,产品线工程已被证实是有效的系统化复用的工程方法。首先探讨将产品线工程应用于组件容器开发所面临的主要困难,并提出相应的解决方案;然后给出了一个组件容器的产品线——PLACE的设计,解释了其两个主要部分:产品线体系结构和产品派生流程;最后,通过一个实际案例,展示利用PLACE设计开发组件容器的完整过程,结果证实体系结构和源代码的复用性都有一定程度的提高。     

两阶段过程模型下的产品线复用策略优化

考虑了软件产品线工程中各软件模块复用策略的选择问题. 在建立软件产品线开发两阶段过程模型的基础上, 归纳出6种典型的复用策略及其实现方式, 提出考虑开发成本、工时、故障率的情况下进行复用策略的选择优化模型, 解决在满足可获得预算、开发周期、系统可靠性需求的约束下产品线质量最优问题. 并基于贝叶斯理论构建易测试函数, 为产品线开发中领域测试强度的估算提供了方法. 最后, 以邮箱服务系统为实例说明该模型的有效 性.     

Requirements engineering in software product line engineering

Many attempts have been made to increase the productivity and quality of software products based on software reuse. Software product line practice is one such approach, one that focuses on developing a family of products which have a majority of features in common. Hence, there are numerous requirements that are common across the family, but others are unique to individual products. Traditional requirements engineering methods were conceived to deal with single product requirements and are usually not flexible enough to address the needs arising from reusing requirements for a family of products. There is also the additional burden of correctly identifying and engineering both product-line-wide requirements and product-specific requirements as well as evolving them. Therefore, in this special issue, we want to highlight the importance and the role of requirements engineering for product line development as well as to provide insights into the state of the art in the field.     

Reducing the verification cost of evolving product families using static analysis techniques

Software product line engineering enables proactive reuse among a set of related products through explicit modeling of commonalities and differences among them. Software product lines are intended to be used in a long period of time. As a result, they evolve over time, due to the changes in the requirements. Having several individual products in a software family, verification of the entire family may take a considerable effort. In this paper we aim to decrease this cost by reducing the number of verified products using static analysis techniques. Furthermore, to reduce model checking costs after product line evolution, we restrict the number of products that should be re-verified by reusing the previous verification result. All proposed techniques are based on static analysis of the product family model with respect to the property and can be automated. To show the effectiveness of these techniques we apply them on a set of case studies and present the results.     

Effective development of automation systems through domain-specific modeling in a small enterprise context

High development and maintenance costs and a high error rate are the major problems in the development of automation systems, which are mainly caused by bad communication and inefficient reuse methods. To overcome these problems, we propose a more systematic reuse approach. Though systematic reuse approaches such as software product lines are appealing, they tend to involve rather burdensome development and management processes. This paper focuses on small enterprises. Since such companies are often unable to perform a “big bang” adoption of the software product line, we suggest an incremental, more lightweight process to transition from single-system development to software product line development. Besides the components of the transition process, this paper discusses tool selection, DSL technology, stakeholder communication support, and business considerations. Although based on problems from the automation system domain, we believe the approach may be general enough to be applicable in other domains as well. The approach has proven successful in two case studies. First, we applied it to a research project for the automation of a logistics lab model, and in the second case (a real-life industry case), we investigated the approaches suitability for fish farm automation systems. Several metrics were collected throughout the evolution of each case, and this paper presents the data for single system development, clone&own and software product line development. The results and observable effects are compared, discussed, and finally summarized in a list of lessons learned.