Aspect-oriented requirements engineering with AoURN

软件需求工程侧重于软件需求的获取、分析、规范、验证和管理。面向目标和面向场景的建模技术已被证明特别适合于发现和分析需求。用户需求表示法(User Requirements Notation，URN)集成了两种互补的可视化语言：面向目标的需求语言(Goal-Oriented Requirements Language，GRL)，用于表示业务目标、非功能需求、备选方案、决策和基本原理；以及用例图(Use Case Maps，UCMS)场景表示法，用于表示叠加在体系结构组件上的因果行为流。URN中还支持这两个视图之间的各种链接。在过去的一年里，URN开始用一种新的方式进行扩展，基于“方面”的概念来组合目标和场景，从而产生了AoGRL和AoUCM。方面使建模师能够更好地封装横切关注点，从而提高模型的模块化、可重用性、可伸缩性和可维护性。

Software requirements engineering focuses on the elicitation, analysis, specification, validation, and management of software requirements. Goal-oriented and scenario-oriented modelling techniques have shown to be particularly well suited for the discovery and analysis of requirements. The User Requirements Notation (URN) integrates two complementary visual languages: the Goal-oriented Requirement Language (GRL) for business goals, non-functional requirements, alternatives, decisions and rationales, and the Use Case Maps (UCMs) scenario notation for causal flows of behavior superimposed on architectural components. Various links between these two views are also supported in URN. In the past year, URN started being extended with a new way of composing goals and scenarios based on the concept of "aspects", leading to AoGRL and AoUCM. Aspects enable modellers to better encapsulate crosscutting concerns leading to improved modularity, reusability, scalability, and maintainability of models.