Software architecture evolution through evolvability analysis

Using LINQ as a universal tool for defining architectural assertions

“…It can be anticipated that examples that include reflections, functional programming, dynamic method definition or other programming concepts may require refactoring of DSL implementation of the model, or redefinition of T4 transformations used for model processing, or introducing other concepts of model transformations [10]. In parallel we intend to start building a default library of architectural assertions denoted in LINQ, that would cover existing good architectural and design practices [4], [5]. Such library -created in abstraction from the source code language -would trigger another research stream, namely existing software projects could be systematically verified against the predefined architectural assertions.…”

برامج المحاسبة التی تلبی محددات اختیار رضا المستخدم المناسب: دلیل تجریبی من لبنان (باللغة الإنجلیزیة)

“…That pertains to the research of Breivold et al, (2012). The ability and capability to efficiently and accurately obtain the users' emerging intentions, and emerging needs and requirements, was a core issue addressed by Breivold et al, (2012).…”

A method for handling evolvability in a complex embedded system

“…In [14], a method using the characteristics of a software system that is connected to evolution is described. The focus in that paper is on what impact that different architectural solutions will have on the ability to evolve the system.…”

“…Adding the different levels together in a graph, Figure 7, with dependences between the functions will give an overview that can be used for decision making when changes are needed. In addition to this the impact of different architectural solutions should be investigated, for example by using the methods described in [14]. The requirements on the functions/dependencies can and should be both functional and non functional.…”