Digital surveillance technologies using artificial intelligence (AI) tools such as computer vision and facial recognition are becoming cheaper and easier to integrate into governance practices worldwide. Morocco serves as an example of how such technologies are becoming key tools of governance in authoritarian contexts. Based on qualitative fieldwork including semi-structured interviews, observation, and extensive desk reviews, this chapter focusses on the role played by AI-enhanced technology in urban surveillance and the control of migration between the Moroccan–Spanish borders. Two cross-cutting issues emerge: first, while international donors provide funding for urban and border surveillance projects, their role in enforcing transparency mechanisms in their implementation remains limited; second, Morocco’s existing legal framework hinders any kind of public oversight. Video surveillance is treated as the sole prerogative of the security apparatus, and so far public actors have avoided to engage directly with the topic. The lack of institutional oversight and public debate on the matter raise serious concerns on the extent to which the deployment of such technologies affects citizens’ rights. AI-enhanced surveillance is thus an intrinsically transnational challenge in which private interests of economic gain and public interests of national security collide with citizens’ human rights across the Global North/Global South divide.
MULTIFILE
Crime scenes can always be explained in multiple ways. Traces alone do not provide enough information to infer a whole series of events that has taken place; they only provide clues for these inferences. CSIs need additional information to be able to interpret observed traces. In the near future, a new source of information that could help to interpret a crime scene and testing hypotheses will become available with the advent of rapid identification techniques. A previous study with CSIs demonstrated that this information had an influence on the interpretation of the crime scene, yet it is still unknown what exact information was used for this interpretation and for the construction of their scenario. The present study builds on this study and gains more insight into (1) the exact investigative and forensic information that was used by CSIs to construct their scenario, (2) the inferences drawn from this information, and (3) the kind of evidence that was selected at the crime scene to (dis)prove this scenario. We asked 48 CSIs to investigate a potential murder crime scene on the computer and explicate what information they used to construct a scenario and to select traces for analysis. The results show that the introduction of rapid ID information at the start of an investigation contributes to the recognition of different clues at the crime scene, but also to different interpretations of identical information, depending on the kind of information available and the scenario one has in mind. Furthermore, not all relevant traces were recognized, showing that important information can be missed during the investigation. In this study, accurate crime scenarios where mainly build with forensic information, but we should be aware of the fact that crime scenes are always contaminated with unrelated traces and thus be cautious of the power of rapid ID at the crime scene.
DOCUMENT
In software architecture, the Layers pattern is commonly used. When this pattern is applied, the responsibilities of a software system are divided over a number of layers and the dependencies between the layers are limited. This may result in benefits like improved analyzability, reusability and portability of the system. However, many layered architectures are poorly designed and documented. This paper proposes a typology and a related approach to assign responsibilities to software layers. The Typology of Software Layer Responsibility (TSLR) gives an overview of responsibility types in the software of business information systems; it specifies and exemplifies these responsibilities and provides unambiguous naming. A complementary instrument, the Responsibility Trace Table (RTT), provides an overview of the TSLR-responsibilities assigned to the layers of a case-specific layered design. The instruments aid the design, documentation and review of layered software architectures. The application of the TSLR and RTT is demonstrated in three cases.
DOCUMENT
