Automated legal sensemaking: the centrality of relevance and intentionality

Introduction: In a perfect world, discovery would ideally be conducted by the senior litigator who is responsible for developing and fully understanding all nuances of their client’s legal strategy. Of course today we must deal with the explosion of electronically stored information (ESI) that never is less than tens-of-thousands of documents in small cases and now increasingly involves multi-million-document populations for internal corporate investigations and litigations. Therefore scalable processes and technologies are required as a substitute for the authority’s judgment. The approaches taken have typically either substituted large teams of surrogate human reviewers using vastly simplified issue coding reference materials or employed increasingly sophisticated computational resources with little focus on quality metrics to insure retrieval consistent with the legal goal. What is required is a system (people, process, and technology) that replicates and automates the senior litigator’s human judgment. In this paper we utilize 15 years of sensemaking research to establish the minimum acceptable basis for conducting a document review that meets the needs of a legal proceeding. There is no substitute for a rigorous characterization of the explicit and tacit goals of the senior litigator. Once a process has been established for capturing the authority’s relevance criteria, we argue that literal translation of requirements into technical specifications does not properly account for the activities or states-of-affairs of interest. Having only a data warehouse of written records, it is also necessary to discover the intentions of actors involved in textual communications. We present quantitative results for a process and technology approach that automates effective legal sensemaking

Digitally enabled health service for the integrated management of hypertension: A participatory user-centred design process

This article describes a user-centred approach taken by a group of five procurers to set specifications for the procurement of value-based research and development services for IT-sup-ported integrated hypertension management. The approach considered the unmet needs of patients and health systems of the involved regions. The procurers established a framework for requirements and a solution design consisting of nine building blocks, divided into three domains: service delivery, devices and integration, and health care organisation. The approach included the development of questionnaires, capturing patients’ and professionals’ views on possible system functionalities, and a template collecting information about the organisation of healthcare, professionals involved and existing IT systems at the procurers’ premises. A total of 28 patients diagnosed with hypertension and 26 professionals were interviewed. The interviewees identified 98 functional requirements, grouped in the nine building blocks. A total of nine use cases and their corresponding process models were defined by the procurers’ working group. As result, a digitally enabled integrated approach to hypertension has been designed to allow citizens to learn how to prevent the development of hypertension and lead a healthy lifestyle, and to receive comprehensive, individualised treatment in close collaboration with healthcare professionals

Requirements traceability in model-driven development: Applying model and transformation conformance

The variety of design artifacts (models) produced in a model-driven design process results in an intricate relationship between requirements and the various models. This paper proposes a methodological framework that simplifies management of this relationship, which helps in assessing the quality of models, realizations and transformation specifications. Our framework is a basis for understanding requirements traceability in model-driven development, as well as for the design of tools that support requirements traceability in model-driven development processes. We propose a notion of conformance between application models which reduces the effort needed for assessment activities. We discuss how this notion of conformance can be integrated with model transformations

ARIES: Acquisition of Requirements and Incremental Evolution of Specifications

This paper describes a requirements/specification environment specifically designed for large-scale software systems. This environment is called ARIES (Acquisition of Requirements and Incremental Evolution of Specifications). ARIES provides assistance to requirements analysts for developing operational specifications of systems. This development begins with the acquisition of informal system requirements. The requirements are then formalized and gradually elaborated (transformed) into formal and complete specifications. ARIES provides guidance to the user in validating formal requirements by translating them into natural language representations and graphical diagrams. ARIES also provides ways of analyzing the specification to ensure that it is correct, e.g., testing the specification against a running simulation of the system to be built. Another important ARIES feature, especially when developing large systems, is the sharing and reuse of requirements knowledge. This leads to much less duplication of effort. ARIES combines all of its features in a single environment that makes the process of capturing a formal specification quicker and easier

Architecting specifications for test case generation

The Specification and Description Language (SDL) together with its associated tool sets can be used for the generation of Tree and Tabular Combined Notation (TTCN) test cases. Surprisingly, little documentation exists on the optimal way to specify systems so that they can best be used for the generation of tests. This paper, elaborates on the different tool supported approaches that can be taken for test case generation and highlights their advantages and disadvantages. A rule based SDL specification style is then presented that facilitates the automatic generation of tests

BlogForever D5.1: Design and Specification of Case Studies

This document presents the specification and design of six case studies for testing the BlogForever platform implementation process. The report explains the data collection plan where users of the repository will provide usability feedback through questionnaires as well as details of scalability analysis through the creation of specific log files analytics. The case studies will investigate the sustainability of the platform, that it meets potential users’ needs and that is has an important long term impact

Requirements analysis for decision-support system design: evidence from the automotive industry

The purpose of this paper is to outline the requirements analysis that was carried out to support the development of a system that allows engineers to view real-time data integrated from multiple silos such as Product Lifecycle Management (PLM) and Warranty systems, in a single and visual environment. The outcome of this study provides a clear understanding of how engineers working in different phases of the product-lifecycle could utilise such information to improve the decision making process and as a result design better products. This study uses data collected via in-depth semi-structured interviews and workshops that includes people working in various roles within the automotive sector. In order to demonstrate the applicability this approach, SysML diagrams are also provided