ISO/TR 19669:2017
Health informatics — Re-usable component strategy for use case development
ISO/TR 19669:2017 specifies a use case development methodology, facilitated by a dynamic catalogue of re-usable components. Use cases are a basic tool in describing requirements for health and healthcare settings, service provision, information technology and software products. Use case development often follows a uniform template with components such as actors, roles, scenarios, event steps, actions, data objects/elements and requirements statements. ISO/TR 19669:2017 includes a basic use case template and the methods of component identification, capture, cataloguing and re-use. This document also includes guidance for software designed to implement the methodology in the form of a use case authoring tool.
| Get this standard | Prices exclude GST | |
|---|---|---|
| PDF ( Single user document) |
$281.74 NZD
|
|
| HardCopy |
$319.13 NZD
|
|
| Networkable PDF |
Price varies
|
Foreword
Introduction
1 Scope
2 Normative references
3 Terms and definitions
4 Symbols and abbreviated terms
5 Objectives for the re-usable component strategy
6 Use case basics
6.1 General
6.2 Use case scenarios, events and actions
6.3 Use case actors
7 Use case component candidates
7.1 General
7.2 Identify-ability
7.3 Catalogue-ability
7.4 Commonality
7.5 Computability
8 Use case components
8.1 General
8.2 Requirements
8.3 Actors and roles
8.4 Scenarios, events and actions
8.5 Data objects and elements
9 Use case scenarios
9.1 General
9.2 Events and event steps
9.3 Actors and roles
9.4 Actions taken
9.5 Inputs and outputs
10 Use case requirements template
10.1 Preface and introduction
10.2 Initiative overview
10.2.1 General
10.2.2 Initiative challenge statement
10.3 Use case scope
10.3.1 General
10.3.2 Background
10.3.3 In scope
10.3.4 Out of scope
10.3.5 Stakeholders
10.4 Value statement
10.5 Use case assumptions
10.6 Pre-conditions
10.7 Post-conditions
10.8 Actors and roles
10.9 Use case diagram
10.10 Use case scenario(s)
10.11 User story
10.12 Activity diagram
10.13 Flow
10.13.1 Base flow
10.13.2 Alternate flow
10.13.3 Functional requirements
10.13.4 Information interchange requirements
10.13.5 System requirements
10.13.6 Sequence diagram
10.14 Risks, issues and obstacles
10.15 Dataset requirements
11 Methodology for component capture, cataloguing and re-use
11.1 General
11.2 Component — Requirements
11.3 Derivation of common requirements from existing use case template
11.3.1 General
11.3.2 Re-use of common requirements in new use case scenario
11.4 Component – Actors/roles
11.4.1 General
11.4.2 Derivation of common actors/roles from existing use case template
11.4.3 Re-use of common actors/roles in new use case scenario
11.5 Component — Scenarios
11.5.1 General
11.5.2 Derivation of scenarios from existing use case template
11.5.3 Re-use of common scenarios in new use case
11.6 Component — Events
11.6.1 General
11.6.2 Derivation of events from existing use case template
11.6.3 Re-use of common events in new use case scenario
11.7 Component — Actions
11.7.1 General
11.7.2 Derivation of actions from existing use case template
11.7.3 Re-use of common actions in new use case scenario event steps
11.8 Component — Data objects/elements
11.8.1 General
11.8.2 Derivation of data objects/elements from existing use case template
11.8.3 Re-use of common data objects/elements in new use case data requirements
12 Progression — Use case development to implementation
12.1 General
12.2 Use case requirements phase
12.2.1 General
12.2.2 Subject matter experts
12.2.3 Use case analysts
12.2.4 Initial sketch of the clinical/business case
12.2.5 Comprehensive statement of the clinical/business case
12.2.6 Components of the clinical/business case
12.2.7 Finalization of clinical/business case requirements
12.3 Anchor for traceability
12.4 Fulfilment of clinical/business case requirements
Bibliography
Keep me up-to-date
Register to receive notifications when updates are made to this standard.
Related Information
Similar Standards
-
BS 30440:2023
Validation framework for the use of artificial intelligence (AI) within healthcare. Specification
-
BS EN 1064:2020
Health informatics. Standard communication protocol. Computer-assisted electrocardiography
-
BS EN 1068:2005
Health informatics. Registration of coding systems
-
BS EN 12251:2004
Health informatics. Secure user identification for health care. Management and security of authentication by passwords
Foreword
Introduction
1 Scope
2 Normative references
3 Terms and definitions
4 Symbols and abbreviated terms
5 Objectives for the re-usable component strategy
6 Use case basics
6.1 General
6.2 Use case scenarios, events and actions
6.3 Use case actors
7 Use case component candidates
7.1 General
7.2 Identify-ability
7.3 Catalogue-ability
7.4 Commonality
7.5 Computability
8 Use case components
8.1 General
8.2 Requirements
8.3 Actors and roles
8.4 Scenarios, events and actions
8.5 Data objects and elements
9 Use case scenarios
9.1 General
9.2 Events and event steps
9.3 Actors and roles
9.4 Actions taken
9.5 Inputs and outputs
10 Use case requirements template
10.1 Preface and introduction
10.2 Initiative overview
10.2.1 General
10.2.2 Initiative challenge statement
10.3 Use case scope
10.3.1 General
10.3.2 Background
10.3.3 In scope
10.3.4 Out of scope
10.3.5 Stakeholders
10.4 Value statement
10.5 Use case assumptions
10.6 Pre-conditions
10.7 Post-conditions
10.8 Actors and roles
10.9 Use case diagram
10.10 Use case scenario(s)
10.11 User story
10.12 Activity diagram
10.13 Flow
10.13.1 Base flow
10.13.2 Alternate flow
10.13.3 Functional requirements
10.13.4 Information interchange requirements
10.13.5 System requirements
10.13.6 Sequence diagram
10.14 Risks, issues and obstacles
10.15 Dataset requirements
11 Methodology for component capture, cataloguing and re-use
11.1 General
11.2 Component — Requirements
11.3 Derivation of common requirements from existing use case template
11.3.1 General
11.3.2 Re-use of common requirements in new use case scenario
11.4 Component – Actors/roles
11.4.1 General
11.4.2 Derivation of common actors/roles from existing use case template
11.4.3 Re-use of common actors/roles in new use case scenario
11.5 Component — Scenarios
11.5.1 General
11.5.2 Derivation of scenarios from existing use case template
11.5.3 Re-use of common scenarios in new use case
11.6 Component — Events
11.6.1 General
11.6.2 Derivation of events from existing use case template
11.6.3 Re-use of common events in new use case scenario
11.7 Component — Actions
11.7.1 General
11.7.2 Derivation of actions from existing use case template
11.7.3 Re-use of common actions in new use case scenario event steps
11.8 Component — Data objects/elements
11.8.1 General
11.8.2 Derivation of data objects/elements from existing use case template
11.8.3 Re-use of common data objects/elements in new use case data requirements
12 Progression — Use case development to implementation
12.1 General
12.2 Use case requirements phase
12.2.1 General
12.2.2 Subject matter experts
12.2.3 Use case analysts
12.2.4 Initial sketch of the clinical/business case
12.2.5 Comprehensive statement of the clinical/business case
12.2.6 Components of the clinical/business case
12.2.7 Finalization of clinical/business case requirements
12.3 Anchor for traceability
12.4 Fulfilment of clinical/business case requirements
Bibliography