Table 2 Identified requirements for creating IEC 62559 use cases and SGAM models
From: Quality properties of IEC 62559 use cases and SGAM models
ID | Name | Sources |
|---|---|---|
Requirements for IEC 62559-2 Use Cases (UC_ID) | ||
1 | The Use Case structure should be acc. the IEC 62559-2 standard | IEC TC 8 (2015), Trefke et al. (2013), Gottschalk and Uslar (2015) |
2 | The Use Case name should consists of a verb and the description | |
3 | The Use Case should contain a the correct Domain & Zone information acc. to the reference model | CEN-CENELEC-ETSI (2014) |
4 | The Use Case should contain a scope description that defines the system boundary | |
5 | The Use Case should contain a description in the narrative section for the specification of the functions | Cockburn (2001), CEN-CENELEC-ETSI (2014), Trefke et al. (2013) |
6 | The Use Case should contain consistent actors acc. the nature of the use case | Gottschalk and Sauer (2015), CEN-CENELEC-ETSI (2014), Neureiter et al. (2014) |
7 | The Use Case actors should be acc. the (business) roles responsibilities which are aimed to support | CEN-CENELEC-ETSI (2014) |
8 | The Business Use Case actors should use roles acc. the Conceptual Model or the Harmonized Role Model | CEN-CENELEC-ETSI (2014) |
9 | The Use Case should use actor (or roles) grouping for simplification when groupings are present and necessary (e.g. DSO) | CEN-CENELEC-ETSI (2014) |
10 | The Use Case actors and roles have consistent relationship regarding the refinement (specialization) | |
11 | The Use Case is consistent in nature (e. g. Business Use Cases, System Use Cases, ...) | Gottschalk and Sauer (2015), CEN-CENELEC-ETSI (2014), Trefke et al. (2013) |
12 | The Use Case should contain valid references (e.g. standards, legislation, regulation, grid codes, ...) | |
13 | The Use Case step-by-step analysis should make clear which information are passed in each step | |
14 | The Use Cases step-by-step analysis should specify the applicable requirements | CEN-CENELEC-ETSI (2014) |
15 | The Actors of The Use Case should be mentioned in the complete description | |
16 | The Use Case Diagram should show interactions | IEC TC 8 (2015) |
17 | The short description should give only a small overview under than 11 lines | Gottschalk et al. (2017) |
18 | The complete description should answer the questions of how, where, when, why, and under what conditions from the user’s point of view occurs | |
Requirements for SGAM Models (SGAM_ID) | ||
1 | The SGAM model structure should be acc. the SGAM Reference Architecture | CEN-CENELEC-ETSI (2012), Uslar et al. (2019), Englert and Uslar (2012) |
2 | The component layer should contain components (e.g. logical or physical actors, components) | |
3 | The communication layer should contain connections with a description of the way of communication between the communicating actors | |
4 | The information layer should contain connections with a description of the information exchange between the communicating actors | |
5 | The functions layer should contain information regarding the functionality | CEN-CENELEC-ETSI (2012), Neureiter et al. (2016), Englert and Uslar (2012) |
6 | The business layer should contain a purpose of the use case | CEN-CENELEC-ETSI (2012), Neureiter et al. (2016), Englert and Uslar (2012) |
7 | The element should be classified into the correct Zone | CEN-CENELEC-ETSI (2012) |
8 | The element should be classified into the correct Domain | CEN-CENELEC-ETSI (2012) |
9 | The components on the “Component Layer” should be arranged to the proper levels of abstractions | Santodomingo et al. (2014), CEN-CENELEC-ETSI (2014), Neureiter et al. (2014) |
10 | The mechanics of the information exchanges on “Communication Layer” should be arranged to an identical level of abstraction | Santodomingo et al. (2014), CEN-CENELEC-ETSI (2014), Neureiter et al.(2014) |
11 | The information exchanges on “Information Layer” should be arranged to an identical level of abstraction. | Santodomingo et al. (2014), CEN-CENELEC-ETSI (2014), Neureiter et al. 2014) |
12 | The functions on “Functional Layer” should be arranged to an identical level of abstraction. | Santodomingo et al. (2014), CEN-CENELEC-ETSI (2014), Neureiter et al. 2014) |
13 | The purposes on “Business Layer” should be arranged to an identical level of abstraction. | Santodomingo et al. (2014), CEN-CENELEC-ETSI (2014), Neureiter et al. (2014) |
14 | The actors from the Component Layer should also occur on the same place in the other layers as well | CEN-CENELEC-ETSI (2014) |
Generic Requirements (GEN_ID) | ||
1 | The description or model should be comprehensible | IEC TC 8 (13,16,), CEN-CENELEC-ETSI (2012), Cockburn (2001), Englert and Uslar (2012) |
2 | The description or model should be unambiguous | Gottschalk and Sauer (2015), IEC TC 8 (13,16,), CEN-CENELEC-ETSI (2012), Cockburn (2001), Balslev (2016), Uslar et al. (2019) |
3 | The description or model should be complete | (IEC TC 8 13,16,, CEN-CENELEC-ETSI (2012), Cockburn (2001), Balslev (2016), Uslar et al. (2019), Gottschalk and Uslar (2015) |
4 | The description or model should be relevant | Uecker et al. (2021), IEC TC 8 (13,16,), CEN-CENELEC-ETSI (2012), Cockburn (2001), Balslev (2016) |
5 | The description or model should be syntactic correct | IEC TC 8 (13,16,), CEN-CENELEC-ETSI (2012), Cockburn (2001), Englert 2012) |
6 | The description or model should be semantic correct | IEC TC 8 (13,16,), CEN-CENELEC-ETSI (2012), Cockburn (2001), Englert and Uslar (2012) |