Modeling Architectural Non Functional Requirements: From Use Case to Control Case
Modeling Architectural Non Functional Requirements: From Use Case to Control Case
复制标题
建模架构非功能性需求：从用例到控制用例
DOI：
10.1109/icebe.2006.71
复制
发表时间：
2006
期刊：
影响因子：
--
通讯作者：
C. Pavlovski
中科院分区：
文献类型：
--
作者：
Joe Zou;C. Pavlovski
虽然系统的功能需求可以通过用例驱动的方法有效地建模，但没有标准或事实上的方法来建模系统架构的非功能需求。这些要求往往是以被动而不是主动的方式处理的。然而，项目困难和失败的一个重要因素是强加在解决方案架构上的非功能性需求。本文提出了一种控制用例方法来记录和建模非功能需求。这种技术使控制案例能够从不同的角度来表示非功能需求，最典型的是各种操作条件。此外，我们提出了一个扩展的“4+1”视图模型描述软件体系结构，增加了控制的情况下，视图。用例和控制用例视图的结合反映了整个系统生命周期视图的完整需求：设计、过程、实现和部署
While the functional requirements of a system can be effectively modeled through the use case driven approach, there is no standard or de facto method for modeling non-functional requirements of the system architecture. Often such requirements are dealt with in a reactive manner rather than proactively. Yet increasingly a contributing factor in project difficulty and failure are the non-functional requirements imposed on the solution architecture. This paper proposes a control case approach to record and model non-functional requirements. This technique enables the control case to represent the nonfunctional requirements from different perspectives, most typically the various operating conditions. Furthermore, we propose an extension to the "4+1" view model for depicting software architecture by adding the control case view. The combination of both the use case and control case views thus reflects the complete requirements across the collective system life cycle views: design, process, implementation and deployment