Lecture 3 - EH2750 Power Systems Advanced Course - Smartgrids Use Case Methodology & UML

Oct 25, 2026

Lecture 3 for EH2750 Computer Applications in Power Systems, Advanced Course, dated 3rd Sept 2012, covers a structured approach to smart grids requirements and use case development. The session reviews existing use cases via the EPRI repository, then details Step 4 for drafting use cases, including goals, narratives, actors, assumptions, contracts and preconditions, triggering events, and step-by-step scenarios. It then introduces UML, explaining unified modeling language concepts and core diagram types such as class and use case diagrams, plus related behavioral and structural views.

LanguageEnglish

CategoryTechnology

FormatPDF

Pages14

Reading Time35 min

AccessFree to download

Outline of the lecture

Smartgrids Use Case Methodology

Review existing Use Cases

Step 4 – Drafting Use Cases

UML – The Unified Modeling Language

Structural classification

Dynamic Behaviour

Model Management

The UML Diagrams

Class diagrams

6/9/2012 | | EH2750 Computer Applications in Power Systems, Advanced Course. | | --- | --- | | Lecture 3
3rd Sept 2012
Professor Lars Nordström
Dept of Industrial Information & Control systems, KTH [larsn@ics.kth.se](larsn@ics.kth.se) | | | | Outline of the lecture | | --- | --- | | Smartgrids Use Case Methodology Short re-cap of last lecture
UML – The Unified Modeling Language What is UML
UML Diagrams
Break
UML Class Diagrams
UML Use Case Diagrams UML Sequence Diagrams | | | | | 6/9/2012 | | A structured approach is needed
• The IEC Publically Available Specification 62559
-Developed initially by the EPRI in the US as part of the
Intelligrid project
-Adopted by the IEC as a PAS in 2008
• The 62559 is not a standard, it is instead a suggested way to work
with developing requirements on new computer applications for power systems.
| | --- | --- | | | | | | Review existing Use Cases | | --- | --- | | • The EPRI Use Case Repository
-A huge collection of Use Cases exist online
-Developed initially in the Intelligrid project in the late 1990s and continued during 2008+
-The level of granularity & completeness very varied
| | | | | 6/9/2012 | | Step 4 – Drafting Use Cases | | --- | --- | | • Important contents of a Use Case
-The goal of the use case, which is usually its name. e.g.“Utility remotely connects or disconnects customer”.
-The narrative. A short English text version of the story.
-The actors. An actor is anything in the system that communicates. e.g. a “customer” or a “meter”.
-The assumptions that the use case is based on . These can constitute requirements in and of themselves.
-The contracts and preconditions that exist between the actors,
-The triggering event that led to the scenario taking place.
-The steps. A numbered list of events that tell the story in detail. | | | | | | | Mapping the Use Case to architecture | | --- | --- | | | | 6/9/2012 How to make things understandable | | Step 4 – Drafting Use Cases | | --- | --- | | • Important contents of a Use Case
-The goal of the use case, which is usually its name. e.g.“Utility remotely connects or disconnects customer”.
-The narrative. A short English text version of the story.
-The actors. An actor is anything in the system that communicates. e.g. a “customer” or a “meter”.
-The assumptions that the use case is based on . These can constitute requirements in and of themselves.
-The contracts and preconditions that exist between the actors,
-The triggering event that led to the scenario taking place.
-The steps. A numbered list of events that tell the story in detail. | | | | | 6/9/2012 | | Outline of the lecture | | --- | --- | | Smartgrids Use Case Methodology Short re-cap of last lecture
UML – The Unified Modeling Language What is UML
UML Diagrams
Break
UML Class Diagrams UML Use Case Diagrams UML Sequence Diagrams | | | | | | | UML – Unified Modeling Language | | --- | --- | | •The most wide-spread system modeling language
• Designed for (object-oriented) software
• Maintained by Object Management Group (OMG)
[www.uml.org](www.uml.org)
•Areas within UML at the highest level
-Structural classification,
-Dynamic behavior
-Model management . | | | | | 6/9/2012 | | Structural classification | | --- | --- | | ”Structural classification describes the things in the system and their relationships to other things. Classifiers include classes, use cases, components, and nodes. Classifiers provide the basis on top of which dynamic behavior is built. Classification views include the static view, use case view, and implementation view .”
Source: Uniﬁed Modeling Language Reference Manual, ISBN 0-201-30998-X, Addison-Wesley
In Power System terms, comparable to the topology of a power system, its line parameters and nominal values for generation and load. | | | | | | | Dynamic Behavi

FAQs

What is the role of the IEC 62559 public specification in this lecture?

It is presented as a suggested way to work on developing requirements for new computer applications for power systems. It is not treated as a standard.

What key elements should a use case contain when drafting?

The lecture lists the use case goal (usually its name), a narrative, the actors, assumptions, contracts and preconditions, the triggering event, and numbered steps describing the scenario in detail.

How does the lecture explain UML and its main focus areas?

UML is described as a widely spread system modeling language designed for (object-oriented) software, maintained by OMG. At the highest level, it covers structural classification, dynamic behavior, and model management.

Oct 25, 2026

Upload by How to eat