Context Assumptions are constantly made by stakeholders or generated automatically in
software development. However, there is a lack of systematic analysis and comprehensive …

The term “case study” is not used consistently when describing studies and, most
importantly, is not used according to the established definitions. Given the misuse of the term …

Security threat modeling involves the systematic elicitation of plausible threat scenarios, and
leads to the identification and articulation of the security requirements in the early stages of …

Context: During software development, some architectural design decisions incur technical
debt, either deliberately or inadvertently. These have serious impact on the quality of a …

Citizens of the digital world are threatened. The digital systems that surround them are
increasingly able to make autonomous decisions over and above them and on their behalf …

Software developers use issue trackers (eg Jira) to manage defects, bugs, tasks, change
requests, etc. In this paper we explore (a) how architectural knowledge concepts (eg …

Context Stakeholders constantly make assumptions in the development of deep learning
(DL) frameworks. These assumptions are related to various types of software artifacts (eg …

Developers constantly make various assumptions regarding requirements, environment,
design decisions, etc. during software development. However, these assumptions are …

Data-intensive systems are software applications that process and generate Big Data. Data-
intensive systems support the use of large amounts of data strategically and efficiently to …

Presented is an approach to support margin allocation and management via a graph-
theoretical network of assumptions. In contrast to the document-centric approach, the …