Trustworthy Software Development

Abstract

Abstract. This paper presents an overview on how existing development methodologies and practices support the creation of trustworthy software. Trustworthy software is key for a successful and trusted usage of software, specifically in the Cloud. To better understand what trustworthy software applications actually mean, the concepts of trustworthiness and trust are defined and put in contrast to each other. Furthermore, we identify attributes of software applications that support trustworthiness. Based on this groundwork, some wellknown software development methodologies and best practices are analyzed with respect on how they support the systematic engineering of trustworthy software. Finally, the state of the art is discussed in a qualitative way, and an outlook on necessary research efforts and technological innovations is given.

From Trustworthy Principles to a Trustworthy Development Process: The Need and Elements of Trusted Development of AI Systems

“…While concrete requirements and best practices for trustworthy development processes are continuously discussed in the more specific field of AI, their identification can draw from the common ground determined for general software development. With its main aim to reach trustworthy products, i.e., software that can satisfy objectives of trustworthiness based on predefined requirements [22,23], a trustworthy development process is the procedure through which such trustworthy products are created [23], i.e., the procedure by which the requirements for considering the outcome trustworthy are ensured. For software in general, characteristics of trustworthy products have been agreed upon and are often reported among security, privacy, reliability, or business integrity [24].…”

Prioritization of global software requirements' engineering barriers: An analytical hierarchy process

“…Similarly, Kamal et al [56] also indicate that de facto distributed regulations are required to limit the boundaries in complex systems that will help practitioners to underline their tasks easily. Paulus et al [57] and Khan et al [6] underlined that BA5 (Lack of trustworthiness) is a critical barrier in the context of GSD. In global distributed environment, the development activities are dependent on geographically distributed practitioners.…”

“…Paulus et al. [57] and Khan et al. [6] underlined that BA5 (Lack of trustworthiness) is a critical barrier in the context of GSD.…”

Geração de planos de adaptação baseados em modelos de qualidade para plataformas cloud

“…De acordo com Paulus et al [71], a definição de Trust em um sistema, uma propriedade pessoal do usuário, é expressa através de probabilidades e reflete o nível de sua convicção de que se engajar no sistema para algum propósito produz um resultado acei-tável. Assim, Trust caracteriza um estado em que o resultado ainda é desconhecido, baseado nas percepções subjetivas e requisitos de cada usuário.…”

“…Dessa forma, níveis relativamente altos de trust podem não significar um resultado positivo do sistema (por exemplo, se os thresholds mínimos dos requisitos forem ainda mais altos). O mesmo ocorre em relação a utilidade: é possível que alguém se envolva em um sistema mesmo se a trust dessa pessoa em relação a um resultado for baixa (por exemplo, se o resultado dos ganhos de utilidade forem altos) [71].…”