News

Software Center partners join forces and shapes a new competence center, CoDig, Continuous Digitalization. The competence center is funded by the participating companies and the universities together with by Vinnova through the program Advanced Digitalization. The CoDig vision is to significantly increase the competitiveness of the Swedish industry by enabling transformation of the software-intensive systems industry into a modern world-leading digitalized industry that fully embraces continuous value delivery by taking advantage

The project Trace Evidence 4 Continuous Quality Product Process Assurance Justification (#50) has published its proposal for a knowledge management strategy for seamless compliance with the machinery regulation. The link to the publication is: https://link.springer.com/chapter/10.1007/978-3-031-42307-9_17 Gallina, B., Olesen, T.Y., Parajdi, E., Aarup, M. (2023). A Knowledge Management Strategy for Seamless Compliance with the Machinery Regulation. In: Yilmaz, M., Clarke, P., Riel, A., Messnarz, R. (eds) Systems, Software and Services Process

Information Needs in CI/CD – Data Validation Across Different Organization in Europe Here comes the link for information needs that I have obtained from 5 different European organizations. In this survey, I am validating the results. I am requesting you to fill the survey where you share the importance, frequency and effort for each need based on Likert scale. Do not scare with the number of questions in the survey,

Advenica is joining the research collaboration Software Center, where we will be part of researching, and applying, the latest knowledge on the effects of the digital transformation. This is part of the company’s strategy to constantly improve our product development methodology and tools, using cutting edge know-how and industry best practice ways of working, in relevant research fields. The Software Center’s mission is to significantly improve the Software Engineering capacity

Architects commonly use informal diagrams for the early design and communication of software systems. Due to their notational freedom and effectiveness for communication, informal diagrams are often preferred over models with a fixed syntax and semantics as defined by a modeling language. But precisely because of this lack of established semantics, these diagrams are of limited use in later development stages for analysis tasks such as consistency checking or change