Choice of design and development methodology Sample Clauses

Choice of design and development methodology. The choice of a design and development methodology can be understood in two ways: first, a methodology for the ARM development and second, a methodology for the generation of specific concrete architectures. We have so far only provided high-level views of either case. In reality, one needs more guidance, viz. a recipe on how to derive all aspect of the ARM model as well as how to derive the best practices. Simply dissecting them into design steps and processes, as has been done so far, is not enough; one needs to know how to achieve each step. In the case of the ARM there are, to our knowledge, no standardised approaches for developing such a model. Furthermore, the IoT usage domain is, compared to typical reference- architecture domains, extremely wide and varied, and common denominators are thus rather few and abstract. For examples of reference architectures and models the reader is directed to the literature [18], [6], [1], [19], [14], [16], [15]. This high level of abstraction in terms of the domain to be modelled stands in contrast to input needed for established and standardised methodologies such as, for instance, Aspect-Oriented Programming, Model-Driven Engineering, Pattern-Based Design, and SysML. All these methodologies were designed for very concrete use cases and application scenarios. Unfortunately, this high degree of specificity is even defining their inner workings. In other words, if one applies them to generalised use cases one does often not get generalised models on the abstract level of an ARM, but one does actually not yield anything, since the processes of which said methodologies are constituted, do not work for generalised use cases. We illustrate the above issue with two examples, Model-Driven Engineering and Pattern-Based Design. In the first case, the methodology is not directly applicable, while, in the second case, the methodology can potentially be generalised for deriving the best-practice transformation shown in Figure 9. Model-Driven Engineering for the generation of Model-Driven Architectures is standardised by the Object Management Group (OMG) [2]. Its application area is the development of software systems. It provides an approach in four steps: