Universal Architecture Description Framework

Abstract

Currently software architecting commonly follows a pattern that is sufficiently different from the systems and hardware architecting pattern of work that it is unnecessarily difficult for management and system engineering people as well as hardware and software people to understand and correlate the two processes. This can lead to a frustrated acceptance on the part of management and systems people that the software people know what they are doing and can be left alone motivated by an inability to understand their methods. Obviously, the whole of the system must be brought under an effective integration, optimization, and management influence, not just the hardware aspects, especially since the hardware component is a decreasing subset in terms of cost and complexity. It is possible to reorder the software development pattern slightly to encourage improved hardware-software integration and management visibility while simultaneously improving the software development process. A model is emerging from research and work activity that promises to supply system and software engineers with a complete model that will be comprehensively effective in transforming a problem space defined by a user community into a precise definition of the problem and solution spaces at the system level as well as throughout the lower tier levels, no matter the physical entities that the system solution will be composed of, including hardware, software, people and procedures, and facilities. In that there is no established name for the aggregate entity, the title Universal Architecting Description Framework has been selected to stretch across the application of the models in an integrated fashion as it could be applied on an unprecedented development program today. This paper offers one form combining unified modeling language (UML), system modeling language (SysML), and four artifacts from traditional structured analysis (TSA). Other UADF are possible and the author has covered two others in a new book by this title.

Leveraging Variability Modeling Techniques for Architecture Trade Studies and Analysis

“…Desire to support such Object Oriented Systems Engineering perspectives inspired several unambiguous language definitions [Ogren, ]. Success from the Software Engineering domain using UML motivated the profile extension to SysML, a subset of UML, as well as the addition of a Requirement Diagram and a Parametric Diagram [Rasmussen et al, ; Grady, ]. The fundamental pillars of SysML include: Structure, Behavior, Requirements, and Parametrics [Friedenthal et al, ].…”

Design of a reference control architecture for the energy management of electric vehicles

“…A number of publications discuss the application of a RA or design pattern within systems engineering (Cloutier and Griego, 2008;Howard et al, 1999;Grady, 2009;Cloutier and Verma, 2007). It is stated that at a generic level, a RA describes the relationship between a solution and a problem within a defined context.…”

“…Recursion within the architecture of a system relates to the reuse of common elements or patterns, often at different levels of system hierarchy (Grady, 2009;Cloutier and Verma, 2007;Yavuz and Bradshaw, 2002). Studies have highlighted that because the same element is reused the modularity and understandability of the design are improved (Cloutier and Verma, 2007;Yavuz and Bradshaw, 2002).…”

A model to develop a platform for personalised health applications

“…A system architecture description can be said to consist of a comprehensive modelling set that includes coverage of the problem and solution spaces plus a means to capture the requirements derived from the models. [97] Recent approaches to building SW architectures include UML, Systems Modeling Language (SysML), Department of Defense Architecture Framework (DoDAF), among others. All these methodologies share the fact that a SW architecture is based on a collection of models.…”

“…All these methodologies share the fact that a SW architecture is based on a collection of models. A model can be defined in this scope as [97]:…”