A Engenharia de Software tem desenvolvido técnicas e métodos para apoiar o desenvolvimento de software confiável, flexível, com baixo custo de desenvolvimento e fácil manutenção. A avaliação da manutenibilidade contribui para fornecer meios para produzir software com alta qualidade. Este trabalho apresenta um experimento controlado para avaliar a manutenibilidade entre as abordagens de web services: RESTful e SOAP-WSDL. Esta avaliação foi conduzida usando 3 programas implementados na linguagem de programação Java e com a mesma arquitetura. Com base na arquitetura projetada, os web services desenvolvidos foram utilizados como objetos em estudos de caso, possibilitando avaliar e comparar a sua manutenibilidade. Os resultados obtidos demonstraram relações entre as informações sobre o custo e a qualidade dos serviços web, que contribuíram para esclarecer os critérios para a obtenção de uma boa relação entre o custo da manutenção e a evolução dos serviços web. Para concluir, os resultados indica que os web services RESTful são mais manuteníveis do lado do servidor, e os web services SOAP-WSDL são mais manuteníveis do lado do cliente. Os estudos realizados no experimento controlado são promissores e podem auxiliar na redução de custo na manutenção dos serviços web, melhorando dessa forma a qualidade do software no geral / Software Engineering has developed techniques and methods to support the development of reliable software, exible, low development cost and easy maintenance. The evaluation of maintainability contributes in this direction, providing the means to produce software with high quality. This paper presents an controlled experiment to evaluate the maintainability between the approaches of web services: RESTful and SOAP-WSDL. This evaluation was conducted using four programs implemented in the Java programming language, using the same architecture. Based on the designed architecture, Web services were developed as objects used in case studies, allowing to evaluate and compare its maintainability. The results showed relationships between the information on the cost and quality of web services, which contributed to clarify the criteria for obtaining a good relationship between the cost of maintenance and evolution of web services. In conclusion, the results indicate the RESTful web services are more maintainable server side in contrast to the SOAP-WSDL web services are more maintainable client side. Studies in controlled experiments are promising and may help reduce the maintenance cost of web services, thus improving overall software quality

O plano de bacias e o relatório de situação são considerados instrumentos estratégicos para o gerenciamento de recursos hídricos nas bacias hidrográficas do Estado de São Paulo. Contudo, sua efetivação tem sido alvo de muitas críticas, que partem, até mesmo, de representantes dos Comitês. Tais críticas centram-se, principalmente, em dois aspectos, quais sejam: as limitações técnicas dos mesmos para embasar a produção de documentos norteadores de práticas plenamente sustentáveis em termos sócio-ambientais, assim como os obstáculos políticos quanto à capacidade de incitar a efetivação de uma gestão democrática em todas as fases do processo, o que envolveria outras instâncias do sistema de gerenciamento de recursos hídricos. Diante disso, o presente trabalho visa investigar a pertinência dessas críticas, partindo da hipótese de que o tempo de existência do Comitê pode estar diretamente relacionado tanto com a percepção dos problemas relacionados aos diversos usos da água, quanto à sua caracterização como instância política representativa de diferentes usuários. A fim de propiciar uma reflexão sociológica sobre a questão, fez-se uma pesquisa de campo a partir do caso de dois diferentes Comitês de Bacias atuantes no estado de São Paulo. Ao final, podemos constatar que parte de nossas percepções foi confirmada e parte não, sustentando a hipótese de que os comitês estruturados mais cedo foram aqueles onde os problemas relacionados aos recursos hídricos eram mais evidentes na região - como é o caso da bacia dos rios PCJ. No entanto, o tempo de existência de um comitê não pode caracterizá-lo como instância política representante dos interesses dos diversos usuários que dele fazem parte, pois os problemas com relação ao processo de elaboração do Relatório de situação e do plano de bacia, embora em proporções diferenciadas, existem e são comuns em todos os colegiados regionais, independentemente do seu tempo de atuação junto ao sistema de gestão hídrico. / The Basins Plan and the Situation Report are strategic instruments for the administration of hydric resources in the hydrographic basins in São Paulo State. However, their implantation have been receiving criticisms even from the representatives of the Committees. Such criticisms are mainly focused in two aspects, which are, the technical limitations of the same ones to base the production of documents which are orientation of practices fully maintainable in socio-environmental terms, and the political obstacles for the implantation of a democratic administration in all phases of the process, what would involve other authorities of the Hydric Resources Administration System. Due to the above mentioned, the present work seeks to investigate the pertinence of those criticisms, starting from the hypothesis that the time of existence of the Committee can be directly related to the perception of the problems related to the several uses of the water, as well as its characterization as representative political authority of different users. In order to propitiate a sociological reflection on the subject, it make a research on field starting from the case of two different Committees of Basins in São Paulo state. Finally, we can verify that, part of our perceptions was true, sustaining the hypothesis that earlier structured committees were those where the problems related to hidric resources were more evident in the area - as in the case of the basin of therivers PCJ. However, the time of existence of a committee cannot characterize it as a representative political authority of the different users that are part of it, because there are problems in the process of elaboration of the Situation Report and of the Basins Plan, although in different proportions, and they are common in all the regional committees, independently of its time of participation at Hydric Resources Administration System.

A geração de produtos de sucesso está associada ao cumprimento dos anseios e desejos dos consumidores. Diversos fatores caracterizam esses anseios, sendo que um grupo de fatores possui especial característica, esse grupo abrange a confiabilidade, a mantenabilidade e a segurança. A gestão desses três fatores implica num olhar profundo em todo ciclo de vida do produto e não somente no projeto, na manufatura, ou na fase de testes funcionais. O projeto que segue busca discutir a implementação de um sistema de gestão para confiabilidade, mantenabilidade e segurança em empresas que desenvolvem produtos com fins lucrativos, mantendo profunda atenção as diretrizes da engenharia simultânea. Serão abordados aspectos dessa implementação, primeiramente definindo o que deve ser gerido, as razões pelas quais se deve buscar essa gestão, em qual estrutura organizacional o mecanismo de gestão deve ser aplicado, quais ferramentas de gestão são pertinentes e como essas ferramentas podem ser implementadas, ressaltando que cuidados merecem atenção e que resultados são esperados. Por fim será apresentado um caso de implementação de uma das ferramentas mais importantes para o sistema de gestão, o sistema FRACAS, \"Failure Reporting, Analysis and Corrective Action System\", que organiza e padroniza a coleta de dados, possibilita análises e fundamenta a tomada de ações de melhoria. Para o desenvolvimento de toda a discussão serão abordados temas diversos como o ciclo de vida dos produtos, projetos, programas, qualidade, sistemas de informação, tecnologias de banco de dados e obviamente confiabilidade, mantenabilidade e segurança. O estudo de caso partirá de um produto já existente que possua dados de campo, seguindo para a construção de um sistema de informação capaz de coletar, organizar, filtrar e pré-analisar as informações. O principal objetivo do trabalho é gerar diretrizes para empresas que desenvolvem produtos que exijam grande esforço de engenharia na otimização de seu processo de decisão, mostrando algumas opções para controlar suas operações, seus programas e projetos no âmbito da confiabilidade, mantenabilidade, disponibilidade e segurança. / The creation of successful products is linked with the ability to reach longings and desires of costumers. Several factors compose these desires and a group of factors have a special characteristic, this group embraces reliability, maintainability and safety. The management of these three factors carries in a deep look of the entire product\'s life cycle and not only in design, manufacture or in functional test phase. The following work intend discuss an implementation of a management system for reliability, maintainability and safety in companies that develop products seeking profit and keeping intense attention to rules from concurrent engineering. Will be discussed aspects of this implementation, firstly defining what should be managed, the reasons to manage, what kind of organizational structure should control this management system, what management tools are relevant and how these tools can be implemented, what special attention any aspect needs and what results are expected. Finally will be presented an implementation case of one of most important tool for the management system, the system FRACAS, \"Failure Reporting, Analysis and Corrective Action System\", that organizes and standardizes the data collection, making some analysis possible and creating basis for the decision making process. During the development of all this discussion a broad number of subjects will be pointed, like product\'s life cycle, designs, projects, quality, information systems, data base technology e obviously reliability, maintainability and safety. The case will start from a preexistent product that already have available field data, following to construction of an information system capable to collect, organize, filter and pre-analyze the information. The main goal of this work is to orientate companies that develop products that demand huge engineering efforts in optimization of making decisions process, showing some options to control their operations, their programs and projects, concerning reliability, maintainability, availability and safety.

This project examines how the quality of a code generator used in an Object-Relational Mapping (ORM) framework can be improved in terms of maintainability, testability and reusability by changing the design from a top-down perspective to a bottom up. The resulting generator is tested in a case study to verify that the new design is more cohesive and less coupled than an existing code generator.

Abstract: The diploma thesis is focused on the analysis of reliability and diagnostics of the electric rotary machines originated in industrial energetic practice. There are diagnostic methods in the diploma thesis having been used in practice and analysis of measurement results of the functional measurement on the real electric machines.

is study has focused on the technical sustainability dimension of sustainable soŸware engineering. Sustainabilitywithin soŸware engineering is something that has recently started to gain traction, where most of theresearch has focused on the environmental dimension.e purpose of this study was to investigate the technicalsustainability dimension, and contribute by continuing to build upon previous research which has suggestedsustainability as a part of non-functional requirements and as a part of soŸware quality.is study was conducted with a qualitative approach. is approach used interviews with people withexperience of working in soŸware development to collect data. e interviews were used to gain in-depthinformation of the dišerent aspects in soŸware development, e.g. development processes.e results, based on the interviews, showed that from a technical sustainability perspective there are issueswith where the focus of the work is in soŸware development and also problems related to how timemanagementis used.e results also showed that there was some lacking in understanding the benets and tradeošs ofdecisions made in the project, for example regarding the soŸware design, which can result in unnecessarycomplexity is acquired.e study found that the culture within soŸware development projects and companies needs to be changedtowards a culture which promotes the development of high quality soŸware. Because non-functional requirementsand soŸware quality are components of technical sustainability, therefore is the technical sustainabilityhigher if the quality is high. It was further found that this culture would be possible if changes were made tothe way prioritisations are made, and the way testing is performed should be extended. Finally it was foundthat the understanding of the benets and tradeošs of decisions and ideas needs to be increased and extendedcollectively.e study concluded that the technical sustainability dimension can be achieved through these changes andthat the problem and solution therefore are not small and local but rather a big and complex issue where thesolution spans several solutions that encompasses dišerent aspects and perspectives.

Developing software without considering the potential changes it mighthave to undergo in the future can be a costly mistake. This is becauseits maintenance costs can become very expensive as they can consumeover 90% of the total life-cycle costs. Incorporating maintainability insoftware has for this reason become highly attractive since it can significantlyreduce the maintenance costs and therefore save companies andsoftware developers a fortune. This thesis presents a software tool thathas been developed to aid Bombardier in the verification of computerbasedinterlocking (CBI) systems. The tool automatically generates testcases which represent the different tests that verify the interlocking system.The paper is divided into two parts. The first part focuses on themaintainability of the tool while the second part investigates whetherthe tool can speed up the testing process of CBI-systems at Bombardier.The results show that the tool is highly maintainable and that tests onCBI-systems can be performed significantly faster with it. / Att utveckla mjukvara utan hänsyn till de eventuella förändringar somden måste genomgå i framtiden kan bli ett kostsamt misstag. Dettaberor på att dess underhållskostnader kan bli mycket dyra eftersom dekan konsumera över 90% av de totala kostnaderna. Det har därför blivitväldigt attraktivt att lägga fokus på underhållbarhet när man utvecklarmjukvara eftersom det kan avsevärt minska underhållskostnadernaoch därmed spara mjukvaruutvecklare och företag en förmögenhet. Idenna uppsats presenteras ett verktyg som har utvecklats för att hjälpaBombardier med verifiering av datorställverk. Verktyget automatisktgenererar testfall som representerar de olika testen som verifierar ställverket.Uppsatsen är uppdelad i två delar. Den första delen fokuserarpå verktygets underhållbarhet medan den andra delen undersöker omverktyget kan påskynda testprocessen för datorställverk på Bombardier.Resultaten visar att verktyget är väldigt underhållbart och att

This project presents a case study of modifiability analysis on the Information Systems which are central to the core business processes of Royal Institution of Technology in Stockholm, Sweden by creating, updating and using models. The case study was limited to modifiability regarding only specified Information Systems. The method selected was Enterprise Architecture together with Enterprise Architecture Analysis research results and tools from the Industrial Information and Control Systems department of the same University. Jointly used with the ArchiMate modelling language, to create the models and perform the analysis. The results demonstrated to be very varied in regards to system models and modifiability. The Alumni Commu-nity system seemed to have very high modifiability whereas the Ladok på Webben system seemed to have the low modifiability, and other systems ranging differently or in between. The case study results found three slightly more critical systems of all the systems analysed: Ladok på Webben, Nya Antagningen & La-dok Nouveau. The first two showed to have either very low or low modifiability while being highly coupled to the other systems. Therefore any modification to these two systems would most likely cause effects that would require change in interconnected systems. Whereas Ladok Nouveau, while having average modifia-bility, has a critical position to process activities, is nearly isolated from all other systems, making them indi-rectly dependent on the system through the interconnected LADOK database. The study showed that the systems developed at KTH are comparable with systems developed by commercial enterprises in terms of modifiability. The study also provided insight into an Enterprise Architecture where the systems have dif-ferent development origins and how this could affect modifiability and analysis.

Studiens syfte är att bedöma till vilken utsträckning AI kan ersätta en människa i rollen som mjukvaruutvecklare utifrån ett kvalitativt perspektiv på kod. Detta görs genom att besvara forskningsfrågorna som lyder: “Hur använder mjukvaruutvecklare sig av generativ AI vid utvecklingsutmaningar?” och “Vad är mjukvaruutvecklares uppfattning om kvaliteten på autogenererad kod skapad av en generativ AI såsom Chat GPT?”. För att besvara frågorna har en kvalitativ metod applicerats. En litteraturundersökning startade studien och tillsammans med en ny modell som baseras på McCall quality model och Boehm quality model. Från detta har en intervjuguide skapats som används i semistrukturerade intervjuer genomförda med erfarna mjukvaruutvecklare. Resultatet visar att kod skapad av generativ AI är ett bra hjälpmedel och verktyg som kan effektivisera en mjukvaruutvecklare och att det används på det sättet idag. Däremot så visar resultaten också att koden som genereras av en generativ AI inte är tillräckligt bra och kan inte användas utan att förändringar eller åtgärder görs då det saknas kvalitet. Slutsatserna som dras är att mjukvaruutvecklare använder sig av generativ AI som ett hjälpmedel men att AI:n inte är kapabel att hantera en uppgift på egen hand, därav är det inget hot mot någon anställning för mjukvaruutvecklare. Framtida forskning bör göras på autogenererad kod. Fler verktyg bör undersökas för att utvidga kunskapen om dess kapacitet samt bör det undersökas vilken inverkan generativ AI kan ha på andra branscher. / The aim of this study, conducted and written in Swedish, is to assess the potential of replacing a human software developer with generative AI. The study evaluates the quality of code generated by a generative AI model, this is done by answering the following research questions: “How do software developers use generative AI for development challenges'' and “How do software developers perceive the quality of code autogenerated by a generative AI such as Chat GPT”. To answer the questions we employ a qualitative research method. The study began with a literature review and based our evaluation of software quality on a hybrid model that modifies and combines McCall quality model and Boehm software quality model. The literature review and the hybrid model was used as a base to shape an interview guide. The interview guide was used in semistructured interviews conducted with experienced software developers. The results suggest that autogenerated code from generative AI is a viable aid for software developers as it makes them more effective in a number of tasks. However, the results also show that the autogenerated AI code has insufficient quality as a complete solution, and therefore often requires further fine-tuning and improvements from software developers. From the results, we conclude that software developers do use generative AI as a tool while writing code. Generative AI enhances software developers effectiveness but the current state of generative AI cannot fully replace a human software developer hence it is not a threat to any employment. Future research should be conducted on auto generated code. Some more tools should be studied to broaden the knowledge on its capabilities as well as looking at the implications that generative AI have on other industries.

Studien undersöker de automatiserade testverktygen: Ghost Inspector och Selenium. En limiterad litteraturstudie och två fallstudier görs, för att undersöka och utvärdera testverktygen. Detta för att kunna tillgodose riktlinjer som är användbara, vid val av ett verktyg för att utföra regressionstestning på webbapplikationer.IStone använder Ghost Inspector som verktyg vid regressionstest på webb applikationer, eftersom det ger dem en effektiv konfigurering och underhålls- process. Selenium kräver mer ansträngning för konfigurering och underhåll, eftersom verktygen inte är en tjänst. Miljön i Ghost Inspector underlättar för iStone att exekvera test kontinuerligt och förser projektteamet med det senaste testresultatet. / The study evaluates the automatic testing tools: Ghost Inspector and Selenium. and focuses on comparing them in terms of the set up and maintenance processes. The study includes a limited literature study and two case studies. The purpose is to evaluate the tools and provide guidelines for choosing a regression testing tool when testing the functionality of web applications.IStone use Ghost Inspector as regressions testing tool on web applications, since it offers an effective set up and maintenance process. Selenium requires more effort to set up and maintain, since Selenium is not a service. The Ghost Inspector environment comforts iStone with the ability of executing test continuously and supplies the latest test results to the project team.