# Requirements Analysis in Disruptive Engineering Solutions Using the Paradigm of Living Systems
## 2 Related Work  
To analyze current research about methods for requirements analysis, we have investigated papers published in the databases of Clarivate Analytics and SCOPUS. The combination of words \"requirements analysis [in the topic]\" AND \" product [in the title]\" AND \"method [in the title]\" listed 89 papers in Clarivate Analytics. With the support of VOSviewer [29], connections between the most representative concepts and issues included in these papers have been analyzed. They show that \"uncertainty\" is mostly connected to \"(customer/product) requirements\" and the \"way\" they are approached, whereas \"techniques\" influence \"quality requirements\" and \"impact\", and they depend on \"product line\". \"Customer\" connects \"techniques\" and \"uncertainty\". The bulk of aspects treated in the selected papers is on planning, assessment, functionality, and innovation--this was also revealed by VOSviewer. A detailed look within the content of the selected papers reveals that the major focus of the proposed methods is not on analyzing the completeness and consistency of requirements, but rather on how to use them to better apply results to new product designs. Searches were reconsidered, with a focus on \"requirement consistency [in the title]\", combined with \"requirement analysis [in the topic]\". Clarivate Analytics and SCOPUS reported 14 papers, but only 10 of them were related to product design. An important remark is that most of the papers dealing with quality analysis of requirements are older than 10 years. This might be connected with the fact that in the last decade, agile methods and methodologies have gained more attention. However, new contexts can change the game, as is the case with disruptive innovations that target non-consumers, where new methods must be added to enhance the modern practices promoted by agile methodologies [30]. Searches on \"requirement completeness [in the title]\" from Clarivate Analytics and SCOPUS returned 21 titles, of which 6 papers were focused on methods for assessing the completeness of requirements. The conclusion is that only very little research has focused on analyzing the consistency and completeness of requirements. Another remark is that the majority of research is focused on software products. Software products are much more complex than other products from the perspective of requirement definition, because of their invisibility (intangibility), complexity, and intensity of effort [30]. Requirement analysis in terms of completeness and consistency is an essential aspect in product innovation--this is either done in the early stages or in any other subsequent stages of product development, and it is independent of the types of methodologies and tools used to collect requirements from stakeholders. Table 1 illustrates the main findings from the literature review. A methodology that analyzes requirement consistency based on semantics, using UML formats. A technique for automatic analysis of consistency between software requirements and detailed designs, achieved at the expense of using imprecise data-flow analysis techniques. It is based on a language for specifying detailed designs, an analysis technique to create a model of a design through data-flow analysis of the language constructs, and a method to automatically generate and check properties derived from requirements to ensure a design's consistency with them. A method for business modeling and elicitation of functional requirements specification. The main advantage of this method is information requirement specification adequacy as a natural way of analyzing user needs. This method is based on requirement specification, in terms of outcomes, data resources and processes. A framework that correlates the partial models with the requirement levels to increase consistency between requirements, functions, and system elements. A benefit emerging with this is the advantageous traceability of requirements.