Concern-Oriented Reuse

重用可以提高软件质量，同时减少开发时间和成本。成功的重用技术包括从类库到组件、服务、框架和软件产品线。基于模型驱动工程（MDE）范式，领域特定知识可以通过将其嵌入到领域特定语言（DSL）、模型、模型转换工具和代码生成器中来重用。虽然每种技术都取得了重要的成功，但重用的最终目标，即软件生产的工业化，还没有成为现实。本研究计划的目标是阐述一个理论的重用，对齐现有的重用技术的优势，在一个统一的框架。我们的愿景是应用先进的技术来分离关注点，即，面向方面和面向功能的复用，定义了一个包含性的复用范例：面向关注点的复用（CORE）。一个关注点包含了关于开发问题的所有内容：1）所有相关抽象级别的模型，2）关注点提供给开发人员的选择和选项的描述，以及它们对非功能性需求的影响，3）描述如何根据开发人员的需求定制重用工件的接口，可能使用专门设计用于操纵关注点概念的DSL，以及4）一致性规则和模型转换，其自动化经验证的多视图开发策略和MDE生成方法。CORE旨在支持进化和协作，将使不断增长的用户社区能够为可重用问题的开放库做出世界范围的贡献。核心成果对软件开发的潜在影响（时间、质量和成本效益）是相当大的。当选择重用关注点中的解决方案时，开发人员不必查看冗长的非正式文档，而是从为每个解决方案变体提供的决策原理中受益。将可重用构件与特定于应用程序的模型和代码组合在一起是安全的，并得到工具和特定于关注点的DSL的支持。这减少了重用的工作量，使重用更不易出错，甚至对非专家也是可以访问的。最后，关注点库中可重用模型的可用性使MDE成为一个可行的开发选择。** 设想的共同框架将使人们有可能将每种再利用技术的最佳做法联合收割机结合起来。大规模采用CORE将使软件工程师成为关注专家。软件提供商可以出售关注点，多年来维护和发展关注点，例如，通过添加新的语言、功能和平台支持，因为它们变得相关。最终，库、重用和专业化将为软件开发提供一个清晰的结构，并因此使软件工程实践更接近于其他工程学科。

Reuse can increase the quality of software, while reducing development time and cost. Successful reuse techniques range from class libraries to components, services, frameworks, and Software Product Lines. Domain-specific knowledge can be reused by embedding it in domain-specific languages (DSL), models, model transformation tools and code generators based on the Model-Driven Engineering (MDE) paradigm. While each technique in isolation has had important success, the ultimate goal of reuse, namely the industrialization of software production, has not become reality.******The objective of this research program is to elaborate a theory of reuse that aligns the strengths of existing reuse technologies within a unifying framework. The vision is to apply advanced techniques for separation of concerns, i.e., aspect-orientation and feature-orientation, to define an encompassing reuse paradigm: concern-oriented reuse (CORE). A concern encapsulates everything about a development issue: 1) models at all relevant levels of abstraction, 2) a description of the choices and options that a concern offers to developers together with their impact on non-functional requirements, 3) an interface that describes how to customize the reused artifacts to the needs of the developer, potentially with a DSL specifically designed for manipulating the concepts of the concern, and 4) consistency rules and model transformations that automate proven multi-view development strategies and MDE generative approaches. Designed with support for evolution and collaboration, CORE will enable world-wide contributions from a growing user community to an open library of reusable concerns.******The potential impact of CORE on software development (time, quality and cost benefits) is considerable. When choosing to reuse a solution from a concern, developers do not have to look through lengthy informal documentation, but benefit from the decision rationales provided for each solution variant. Composition of the reusable artifacts with application-specific models and code is safe, supported by tools and concern-specific DSLs. This decreases the reuse effort, makes reuse less error prone, and even accessible to non-experts. Finally, the availability of a reusable models in the concern library makes MDE a viable development choice. ******The envisioned common framework would make it possible to combine best practices from each reuse technique. A large scale adoption of CORE would allow software engineers to become concern specialists. Software providers could sell concerns, maintaining and evolving the concern over years, e.g., by adding new languages, features, and platform support, as they become relevant. Ultimately, libraries, reuse, and specialization would provide a clear structure to software development, and as a result align the practice of software engineering closer to what is done in other engineering disciplines.