Internet of things (IoT) and digital twin – Best practices for use case projects
Introduction: The concept of use cases was introduced in the 1980s in system engineering by Ivar Jacobson [1]1 to enable the capture and specification of the requirements of a system, using textual, structural, and visual modelling techniques. The practice of providing use cases has been widely used at research level [2]. It has been nearly systematically used at standardization level as shown in the following examples: methodology for use cases from IEC 62559 [3], [4], [5]; use cases in the ambient assisted living (AAL) domain [6]; use cases in the big data domain [7], including three iterations from NIST [8], [9], [10]; use cases in the IoT domain [11]; use cases in the AI domain [12], including a companion standard on security and privacy [13]; use cases in the digital twin domain [14]; use cases in the blockchain domain [15]; use cases on privacy-by-design in the consumer domain [16]; This document describes best practices for use case projects. It is structured as follows: Clause 5 provides an introduction on existing definitions (5.1), and specifies a conceptual model of use cases. Clause 6 explains the purpose of use case projects (6.1), and provides examples of use case projects (6.2). Clause 7 explains the purpose of use case templates (7.1), providing a conceptual model of a use case template (7.2), and describing the content of a template: description blocks, predefined fields, instructions, and samples (7.3). Clause 8 explains the purpose of use case project plans (8.1), coveri
Scope: This document describes best practices for use case projects in terms of projects, templates and plans, with the objective to improve the consistency of content across different use case projects and enable sharing of knowledge between projects. A long-term goal is to foster interoperability between tools supporting the collection and maintenance of use cases. This document is intended for developers of use case projects, including in the context of standardization. The document can be used to complement existing methodology standards such as IEC 62559 [3], [4], [5].
Contents:
- FOREWORD
- INTRODUCTION
- Scope