An autonomous satellite architecture integrating deliberative reasoning and behavioural intelligence

This paper describes a method for the design of autonomous spacecraft, based upon behavioral approaches to intelligent robotics. First, a number of previous spacecraft automation projects are reviewed. A methodology for the design of autonomous spacecraft is then presented, drawing upon both the European Space Agency technological center (ESTEC) automation and robotics methodology and the subsumption architecture for autonomous robots. A layered competency model for autonomous orbital spacecraft is proposed. A simple example of low level competencies and their interaction is presented in order to illustrate the methodology. Finally, the general principles adopted for the control hardware design of the AUSTRALIS-1 spacecraft are described. This system will provide an orbital experimental platform for spacecraft autonomy studies, supporting the exploration of different logical control models, different computational metaphors within the behavioral control framework, and different mappings from the logical control model to its physical implementation

Classification of product data for a Digital Product Passport in the manufacturing industry

The European Commission set out the goal of carbon neutrality by 2050, which shall be achieved by fostering the twin transition - sustainability through digitalization. A keystone in this transition is the implementation of a prospering Circular Economy (CE). However, product information required to establish a flourishing CE is hardly available or even accessible. The Digital Product Passport (DPP) offers a solution to that problem but in the current discussion, two separate topics are focused on: its architecture and its application on batteries. The content of the DPP has not been an essential part of the discussion, although access to high-quality data about a product's state, composition and ecological footprint is required to enable sustainable decision-making. Therefore, this paper presents a classification of product data for circularity in the manufacturing industry to emphasize the discussion about the DPP's content. Developed through a systematic literature review combined with a case-study-research based on common operational information systems, the classification comprises three levels with 62 data points in four main categories: (1) Product information, (2) Utilization information, (3) Value chain information and (4) Sustainability information. In this paper, the potential content structure of a DPP is demonstrated for a use case in the machinery sector. The contribution to the science and operations community is twofold: Building a guideline for DPP developers that require scientific input from available real-world data points as well as motivating manufacturers to share the presented data points enabling a circular product information management

The Impact of Requirements on Systems Development Speed: A Multiple-Case Study in Automotive

Automotive\ua0manufacturers have historically adopted rigid\ua0requirements\ua0engineering processes. This allowed them to meet safety-critical\ua0requirements\ua0when producing\ua0a\ua0highly complex and differentiated product out of the integration of thousands of physical and software components. Nowadays, few software-related domains are as rapidly changing as the\ua0automotive\ua0industry.\ua0In\ua0particular, the needs of improving\ua0development\ua0speed\ua0are increasingly pushing companies\ua0in\ua0this domain toward new ways of developing software.\ua0In\ua0this paper, we investigate how the goal to increase\ua0development\ua0speed\ua0impacts how\ua0requirements\ua0are managed\ua0in\ua0the\ua0automotive\ua0domain. We start from\ua0a\ua0manager perspective, which we then complement with\ua0a\ua0more general perspective. We used\ua0a\ua0qualitative\ua0multiple-case\ua0study, organized\ua0in\ua0two steps.\ua0In\ua0the first step, we had 20 semi-structured interviews, at two\ua0automotive\ua0manufacturers. Our sampling strategy focuses on manager roles, complemented with technical specialists.\ua0In\ua0the second step, we validated our results with 12 more interviews, covering nine additional respondents and three recurring from the first step.\ua0In\ua0addition to validating our qualitative model, the second step of interviews broadens our perspective with technical experts and change managers. Our respondents indicate and rank six aspects of the current\ua0requirements\ua0engineering approach that\ua0impact\ua0development\ua0speed. These aspects include the negative\ua0impact\ua0of\ua0a\ua0requirements\ua0style dominated by safety concerns as well as decomposition of\ua0requirements\ua0over many levels of abstraction. Furthermore, the use of\ua0requirements\ua0as part of legal contracts with suppliers is seen as hindering fast collaboration. Six additional suggestions for potential improvements include domain-specific tooling, model-based\ua0requirements, test automation, and\ua0a\ua0combination of lightweight upfront\ua0requirements\ua0engineering preceding\ua0development\ua0with precise specifications post-development. Out of these 12 aspects, seven can likely be addressed as part of an ongoing agile transformation. We offer an empirical account of expectations and needs for new\ua0requirements\ua0engineering approaches\ua0in\ua0the\ua0automotive\ua0domain, necessary to coordinate hundreds of collaborating organizations developing software-intensive and potentially safety-critical\ua0systems

Use of IBM Collaborative Lifecycle Management Solution to Demonstrate Traceability for Small, Real-World Software Development Project

The Standish Group Study of 1994 showed that 53 percent of software projects failed outright and another 31 percent were challenged by extreme budget and/or time overrun. Since then different responses to the high rate of software project failures have been proposed. SEI’s CMMI, the ISO’s 9001:2000 for software development, and the IEEE’s JSTD-016 are some examples of such responses. Traceability is the one common feature that these software development standards impose. Over the last decade, software and system engineering communities have been researching subjects such as developing more sophisticated tooling, applying information retrieval techniques capable of semi-automating the trace creation and maintenance process, developing new trace query languages and visualization techniques that use trace links, applying traceability in specific domains such as Model Driven Development, product line systems and agile project environment. These efforts have not been in vain. The 2012 CHAOS results show an increase in project success rate of 39% (delivered on time, on budget, with required features and functions), and a decrease of 18% in the number of failures (cancelled prior to completion or delivered and never used). Since research has shown traceability can improve a project’s success rate, the main purpose of this thesis is to demonstrate traceability for a small, real-world software development project using IBM Collaborative Lifecycle Management. The objective of this research was fulfilled since the case study of traceability was described in detail as applied to the design and development of the Value Adjustment Board Project (VAB) of City of Jacksonville using the scrum development approach within the IBM Rational Collaborative Lifecycle Management Solution. The results may benefit researchers and practitioners who are looking for evidence to use the IBM CLM solution to trace artifacts in a small project

ENABLING UTXO-BASED BACKWARDS AND FORWARDS TRACEABILTY

Increased regulation creates challenging requirements for production environments, changes mindsets, breaks off IT silos, and creates IT landscapes with greater integration. Many researchers and practitioners hope to meet future product traceability requirements beyond one\u27s company borders using DLT approaches. However, interdisciplinary teams still face different organizational and technical integration and standardization challenges in supply networks. This paper uses a Design Science Research (DSR) approach to consolidate confusing event terminologies in supply chains and develops a modified UTXO token considering EPCIS 2.0 standards. The results present an evaluated input-output traceability system (IOTS) that maps holistic meta-events. We use a simple cross-organizational example and visualization tools that multiple organizations can use to ensure efficient and easy backward and forward traceability of objects and events. Finally, we conclude the results with a detailed discussion and future research directions

Requirements reuse and requirement patterns: a state of the practice survey

Context. Requirements engineering is a discipline with numerous challenges to overcome. One of these challenges is the implementation of requirements reuse approaches. Although several theoretical proposals exist, little is known about the practices that are currently adopted in industry. Objective. Our goal is to contribute to the investigation of the state of the practice in the reuse of requirements, eliciting current practices from practitioners, and their opinions whenever appropriate. Besides reuse in general, we focus on requirement patterns as a particular strategy to reuse. Method. We conducted an exploratory survey based on an online questionnaire. We received 71 responses from requirements engineers with industrial experience in the field, which were analyzed in order to derive observations. Results. Although we found that a high majority of respondents declared some level of reuse in their projects (in particular, non-functional requirements were identified as the most similar and recurrent among projects), it is true that only a minority of them declared such reuse as a regular practice. Larger IT organizations and IT organizations with well-established software processes and methods present higher levels of reuse. Ignorance of reuse techniques and processes is the main reason preventing wider adoption. From the different existing reuse techniques, the simplest ones based on textual copy and subsequent tailoring of former requirements are the most adopted techniques. However, participants who apply reuse more often tend to use more elaborate techniques. Opinions of respondents about the use of requirement patterns show that they can be expected to mitigate problems related to the quality of the resulting requirements, such as lack of uniformity, inconsistency, or ambiguity. The main reasons behind the lack of adoption of requirement patterns by practitioners (in spite of the increasing research approaches proposed in the community) are related to the lack of a well-defined reuse method and involvement of requirement engineers.Peer ReviewedPostprint (author's final draft

Novel development of distributed manufacturing monitoring systems to support high cost and complexity manufacturing

In the current manufacturing environment, characterized by diverse change sources (e.g. economical, technological, political, social) and integrated supply chains, success demands close cooperation and coordination between stakeholders and agility. Tools and systems based on software agents, intelligent products and virtual enterprises have been developed to achieve such demands but either because of: (i) focus on a single application; (ii) focus on a single product; (iii) separation between the product and its information; or (iv) focus on a single system characteristic (e.g. hardware, software, architecture, requirements) their use has been limited to trial or academic scenarios. In this thesis a reusable distributed manufacturing monitoring system for harsh environments, capable of addressing traceability and controllability requirements within stakeholders and across high cost and complexity supply chains is presented. [Continues.