Use case methodology – Part 4: Best practices in use case development for IEC standardization processes and some examples for application outside standardization
Introduction: 0.1 General The IEC 62559 use case template and methodology evolved from work originally performed by the Electric Power Research Institute (EPRI) as part of the IntelliGrid program. The primary purpose of that effort was to develop descriptions of existing and future power systems and their functions and requirements. In the evolution of this effort, the value of use cases as a means to accurately and completely describe the requirements for these systems and functions was demonstrated. The use case template was contributed to the IEC and this became a Publicly Available Specification (IEC PAS 62559:2008). As the best practice of use cases evolved, IEC PAS 62559:2008 was cancelled and replaced by IEC 62559-2:2015 to reflect these updates. This methodology was originally developed as part of the IntelliGrid Architecture developed by the Electrical Power Research Institute (EPRI) as a means to implement the “IntelliGrid vision” of the automated, self-healing, and efficient power system of the future. However, the aim of IEC 62559 has changed in such a way that it is now intended to describe a methodology which is generic enough to become applicable for all domains served by IEC or other standardization bodies. Initially, IEC 62559 was dedicated to the smart grid domain, but with the introduction of systems committees within IEC’s organizational structure, the focus was widened to allow the use of the use case methodology also for other domains like active assisted living or sm
Scope: This document specifies best practices for an entity to engage in a use cases redaction process to determine and describe their user requirements for systems, based on the business needs. It complements the information in IEC TR 62559-1, IEC 62559-2 [3] and IEC 62559-3 [4] by providing users with best practices in: use cases drafting process, determining the skill sets of the people required, use case repository management, and using use cases for IEC or enterprise projects.
Contents:
- FOREWORD
- INTRODUCTION
- Scope