首页> 外文会议>e-Business Engineering, 2006. ICEBE '06. IEEE International Conference on >Modeling Architectural Non Functional Requirements: From Use Case to Control Case
【24h】

Modeling Architectural Non Functional Requirements: From Use Case to Control Case

机译:建模架构非功能需求:从用例到控制用例

获取原文

摘要

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
机译:尽管可以通过用例驱动的方法有效地对系统的功能需求进行建模,但没有用于对系统体系结构的非功能需求进行建模的标准或事实上的方法。通常,这种要求是以被动方式而不是主动方式处理的。然而,对解决方案体系结构提出的非功能性要求越来越成为导致项目难度和失败的因素。本文提出了一种控制案例方法来记录和建模非功能性需求。这种技术使控制案例能够从不同的角度(最典型的是各种操作条件)代表非功能性需求。此外,我们提出了对“ 4 + 1”视图模型的扩展,以通过添加控制案例视图来描述软件体系结构。因此,用例和控制用例视图的结合反映了整个系统生命周期视图的完整需求:设计,过程,实现和部署

著录项

相似文献

  • 外文文献
  • 中文文献
  • 专利
获取原文

客服邮箱:kefu@zhangqiaokeyan.com

京公网安备:11010802029741号 ICP备案号:京ICP备15016152号-6 六维联合信息科技 (北京) 有限公司©版权所有
  • 客服微信

  • 服务号