Tailored Systems Architecture for Design of Space Science and Technology Missions Using DoDAF V2.0

The use of systems architecture, following a set of integrated descriptions from an architecture framework, has been well codified in Department of Defense acquisition and systems engineering. However, in the Space Science and Technology (S&T) community, this guidance and practice is not commonly adopted. This paper outlines an approach to leverage the changes made in DoD Architecture Framework 2.0 (DoDAF2.0), and the renewed emphasis on data and support to acquisition decision analysis. After decomposing the Space S&T design lifecycle into phases, design milestones and activities using process models, a set of DoDAF prescribed and Fit-for-Purpose views are constructed into a reference implementation of a system architecture. This approach attempts to make DoDAF2.0 more relevant and integrated with S&T missions, the decisions that are encountered, and facilitates re-use with existing documentation

Federated Embedded Systems – a review of the literature in related fields

This report is concerned with the vision of smart interconnected objects, a vision that has attracted much attention lately. In this paper, embedded, interconnected, open, and heterogeneous control systems are in focus, formally referred to as Federated Embedded Systems. To place FES into a context, a review of some related research directions is presented. This review includes such concepts as systems of systems, cyber-physical systems, ubiquitous computing, internet of things, and multi-agent systems. Interestingly, the reviewed fields seem to overlap with each other in an increasing number of ways

Practitioner requirements for integrated Knowledge-Based Engineering in Product Lifecycle Management.

The effective management of knowledge as capital is considered essential to the success of engineering product/service systems. As Knowledge Management (KM) and Product Lifecycle Management (PLM) practice gain industrial adoption, the question of functional overlaps between both the approaches becomes evident. This article explores the interoperability between PLM and Knowledge-Based Engineering (KBE) as a strategy for engineering KM. The opinion of key KBE/PLM practitioners are systematically captured and analysed. A set of ranked business functionalities to be fulfiled by the KBE/PLM systems integration is elicited. The article provides insights for the researchers and the practitioners playing both the user and development roles on the future needs for knowledge systems based on PLM

Enhanced software product line (ENSPL) for industrial test applications[QA75].

Pendekatan-pendekatan barisan produk perisian masa kini menghasilkan produk perisian yang mempunyai ikatan kuat dengan aset-aset perisian. Current software product lines (SPL) methodologies develop software products in the manner that is tightly coupled to the software assets

Integrated Ground Operations Demonstration Units Testing Plans and Status

Cryogenic propellant loading operations with their associated flight and ground systems are some of the most complex, critical activities in launch operations. Consequently, these systems and operations account for a sizeable portion of the life cycle costs of any launch program. NASA operations for handling cryogens in ground support equipment have not changed substantially in 50 years, despite advances in cryogenics, system health management and command and control technologies. This project was developed to mature, integrate and demonstrate advancement in the current state of the art in these areas using two distinct integrated ground operations demonstration units (GODU): GODU Integrated Refrigeration and Storage (IRAS) and GODU Autonomous Contro

Why and How Your Traceability Should Evolve: Insights from an Automotive Supplier

Traceability is a key enabler of various activities in automotive software and systems engineering and required by several standards. However, most existing traceability management approaches do not consider that traceability is situated in constantly changing development contexts involving multiple stakeholders. Together with an automotive supplier, we analyzed how technology, business, and organizational factors raise the need for flexible traceability. We present how traceability can be evolved in the development lifecycle, from early elicitation of traceability needs to the implementation of mature traceability strategies. Moreover, we shed light on how traceability can be managed flexibly within an agile team and more formally when crossing team borders and organizational borders. Based on these insights, we present requirements for flexible tool solutions, supporting varying levels of data quality, change propagation, versioning, and organizational traceability.Comment: 9 pages, 3 figures, accepted in IEEE Softwar