This research introduces a new data-driven methodology for fault detection and isolation in dynamic systems, integrating fuzzy/Bayesian change point detection and decision trees induced by genetic programming for pattern classification. Tracking changes in sensor signals enables the detection of faults, and using decision trees generated by genetic programming allows for accurate categorization into specific fault classes. Change point detection utilizes a combination of fuzzy set theory and the Metropolis–Hastings algorithm. The primary contribution of the study lies in the development of a distinctive classification system, which results in a comprehensive and highly effective approach to fault detection and isolation. Validation is carried out using the Tennessee Eastman benchmark process as an experimental framework, ensuring a rigorous evaluation of the efficacy of the proposed methodology.
In order to improve the success rate of software projects various development methodologies have been proposed as alternative to traditional models of development, the agile methodologies. Some steps of the traditional methodology were changed or even canceled, on agile methods, particularly at requirements engineering phase. Traditional methodologies rely on the documentation to manage the project and share knowledge. Meanwhile, the agile methodologies focus on the interaction between those involved in the project to deal with the same goals. There are several challenges with respect to requirements engineering in agile methods. Among these are problems at the process of requirement’s elicitation and analyses. This work proposes to analyze tools, techniques, or patterns, like Test Driven Development, in order to better manage the process of requirement's elicitation and validation at Scrum. Resumo. No intuito de melhorar a taxa de sucesso dos projetos de software varias metodologias foram propostas como alternativa aos modelos tradicionais de desenvolvimento de software, as metodologias ageis. Nas metodologias ageis alguns passos foram substituidos ou ate mesmos cancelados, sobretudo na fase de engenharia de requisitos. As metodologias tradicionais dependem da documentacao para gerenciar o projeto, tanto como para disseminar o conhecimento. Enquanto isso, as metodologias ageis focam nas interacoes entre os envolvidos no projeto para lidar com o mesmo proposito. Existem diversos desafios com relacao a engenharia de requisitos dentro das metodologias ageis. Dentre esses, estao problemas no processo de elicitacao e analise de novos requisitos. Esse trabalho propoe analisar ferramentas, tecnicas ou padroes, como Test Driven Development, a fim de melhorar o cenario do processo de elicitacao e validacao de requisitos no Scrum.
Public Software can be defined as any software that is endorsed by a Public Agent and distributed for wide use by the society. The concept of Public Software is an outspread of the idea that "software" is an important asset for the welfare of society, and therefore providing citizens with proper software tools is a task of public interest, which in some cases should be performed by the government itself. When a Public Agent endorses a software and gives it the "seal" of Public Software, he is -- explicitly or implicitly -- declaring that such software complies with minimum technical requirements, and stimulates its wide use by the society In the present paper, we discuss the importance that such requirements encompasses Information Security and we propose a validation model that is strongly based on security evaluation. In a world where cyber-crime is a reality and cyber-war becomes more and more relevant, it is fundamental that the Public Agent verify the Information Security aspects of a software before declaring it a Public Software, for otherwise, this Public Agent can be stimulating that security flaws and vulnerabilities are spread in the society, possibly in critical applications. We additionally discuss the importance of a strong validation procedure to assure the appropriate behavior of software regarding its functionalities and Information Security aspects. We conclude describing the Brazilian experience with the "Brazilian Public Software Portal" Public Software repository of open-source software.