ISO/TR 19669:2017

TECHNICAL ISO/TR
REPORT 19669
First edition
2017-10
Health informatics — Re-usable
component strategy for use case
development
Informatique de santé — Stratégie de composants réutilisables pour
le développement de cas pratiques
Reference number
©
ISO 2017
© ISO 2017, Published in Switzerland
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form
or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior
written permission. Permission can be requested from either ISO at the address below or ISO’s member body in the country of
the requester.
ISO copyright office
Ch. de Blandonnet 8 • CP 401
CH-1214 Vernier, Geneva, Switzerland
Tel. +41 22 749 01 11
Fax +41 22 749 09 47
copyright@iso.org
www.iso.org
ii © ISO 2017 – All rights reserved

Contents Page
Foreword .v
Introduction .vi
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Symbols and abbreviated terms . 3
5 Objectives for the re-usable component strategy . 4
6 Use case basics . 4
6.1 General . 4
6.2 Use case scenarios, events and actions . 4
6.3 Use case actors . 4
7 Use case component candidates . 4
7.1 General . 4
7.2 Identify-ability . 5
7.3 Catalogue-ability . 5
7.4 Commonality . 5
7.5 Computability . 5
8 Use case components . 5
8.1 General . 5
8.2 Requirements . 5
8.3 Actors and roles . 6
8.4 Scenarios, events and actions . 6
8.5 Data objects and elements . 6
9 Use case scenarios . 7
9.1 General . 7
9.2 Events and event steps . 7
9.3 Actors and roles . 7
9.4 Actions taken . 7
9.5 Inputs and outputs . 7
10 Use case requirements template . 7
10.1 Preface and introduction . 7
10.2 Initiative overview . 8
10.2.1 General. 8
10.2.2 Initiative challenge statement . 8
10.3 Use case scope . 8
10.3.1 General. 8
10.3.2 Background. 8
10.3.3 In scope . 8
10.3.4 Out of scope . 8
10.3.5 Stakeholders . 8
10.4 Value statement . 9
10.5 Use case assumptions . 9
10.6 Pre-conditions . 9
10.7 Post-conditions . 9
10.8 Actors and roles . 9
10.9 Use case diagram .10
10.10 Use case scenario(s) .10
10.11 User story .11
10.12 Activity diagram .11
10.13 Flow .11
10.13.1 Base flow .11
10.13.2 Alternate flow .12
10.13.3 Functional requirements .12
10.13.4 Information interchange requirements .13
10.13.5 System requirements .13
10.13.6 Sequence diagram .13
10.14 Risks, issues and obstacles .13
10.15 Dataset requirements .13
11 Methodology for component capture, cataloguing and re-use .14
11.1 General .14
11.2 Component — Requirements .14
11.3 Derivation of common requirements from existing use case template .14
11.3.1 General.14
11.3.2 Re-use of common requirements in new use case scenario.14
11.4 Component – Actors/roles .17
11.4.1 General.17
11.4.2 Derivation of common actors/roles from existing use case template .17
11.4.3 Re-use of common actors/roles in new use case scenario .17
11.5 Component — Scenarios .17
11.5.1 General.17
11.5.2 Derivation of scenarios from existing use case template .18
11.5.3 Re-use of common scenarios in new use case .
...