• 中国计算机学会会刊
  • 中国科技核心期刊
  • 中文核心期刊

J4 ›› 2013, Vol. 35 ›› Issue (5): 67-76.

• 论文 • 上一篇    下一篇

一种面向特征的软件产品线非功能需求建模方法

孙连山,王今雨   

  1. (陕西科技大学电气与信息工程学院,陕西 西安 710021)
  • 收稿日期:2012-04-12 修回日期:2012-09-06 出版日期:2013-05-25 发布日期:2013-05-25
  • 基金资助:

    国家自然科学基金资助项目(61202019)

A featureoriented approach to modeling
nonfunctional requirements in software product line      

SUN Lianshan,WANG Jinyu   

  1. (College of Electrical and Information Engineering,Shaanxi University of Science and Technology,Xi’an 710021,China)
  • Received:2012-04-12 Revised:2012-09-06 Online:2013-05-25 Published:2013-05-25

摘要:

分析传统非功能需求定义的不足,基于需求分析阶段的系统抽象—“需求模型”重新定义非功能需求,规范并简化功能需求与非功能需求之间的关系。扩展面向特征的软件产品线建模方法,在特征模型中显式地建模功能需求、非功能需求、非功能需求类型以及它们之间的相互关系,沿用传统特征模型中固有的变化性建模机制建模并管理非功能需求的变化性,显式地复用与非功能需求相关的建模知识和资产,为进一步研究定量评估产品线变体质量的新技术奠定基础。设计了一个基于多视图的特征建模方法,指导开发者在迭代的过程中建模非功能需求和功能需求,支持关注点分离和模型的复杂性管控。实现了工具原型并进行了实例验证。

关键词: 非功能需求, 软件产品线, 特征模型, 多视图

Abstract:

Analyzing traditional definitions of NonFunctional Requirements (NFR), this paper redefined NFR as constraints on 'requirements model' that is an available system abstraction at requirements analysis stage. The proposed definition formulates the relationships among NFR and functional requirements. Furthermore, this paper extended a traditional featureoriented software product line requirements modeling approach to explicitly model NFR, functional requirements, the type of NFR, as well as various relationships among them, and to model NFRs variability in the same way of modeling variability in traditional feature model. The proposed approach enables explicitly compilation and customization of NFRrelated assets across projects, and is a solid basis for quantitative evaluation on the quality of the derived products. Furthermore, we presented a multipleview based and featureoriented approach to guide developers to iteratively model both NFR and functional requirements, and meantime to achieve goals including separation of concerns and model complexity management. Finally, a tool prototype was implemented and a case study was conducted.

Key words: nonfunctional requirements;software product line;feature model;multiple views