Use Case: VITO/Maximize residual heat use
Search
Asset Publisher
Description Of The Use Case
Name of use case
| Use case identification | ||
| ID | System configuration(s) | Name of use case |
| UC17 | [List of system configurations which this UC can be applied to] | [start with verb expressing key action] Maximize the use of residual heat and cold at a business park |
Version management
| Version management |
| |||
| Version No. | Date | Author(s) | Changes | Approval status |
| [X.Y] | [DD/MM/YYYY] | [List of names] | [Difference to previous version] | [Draft, Work in progress, Review, Final] |
| 1.0 | 07/07/2017 | Pieter Valkering | First version | Work in progress |
Scope and objectives of use case
| Scope and objectives of use case | |
| Scope | A 4th generation heat network is rolled out at the Thor business park in Genk, where buildings are also equipped with PV panels, thermal day-to-day and seasonal storage, gas boilers and heat pumps. One use case is to use the heat network to recuperate low temperature residual heat from the heat pumps in other buildings at the Thor park. The residual heat and cold from the EnergyVille buildings 1 and 2 can then be maximally used to supply the other buildings at the Thor park. |
| Objective(s) | [identify specific objectives] O1: Analyse the extent to which residual heat and cold from the EnergyVille buildings can be used to supply other buildings at the Thor business park. |
| Belongs to use case group (if applicable) | [Specify an arbitrary group name here in order to link multiple related UCs together] Self-sufficiency, heat storage, storage long-term, cooling |
Narrative of use case
| Narrative of use case |
| Short description |
| |
| Complete description |
| [More verbose description; include for example details about control domain, requirements towards input signals or applicable system operating modes (normal, emergency, …) ] |
Optimality Criteria
(Directly associated with objectives. E.g. by what metric to 'minimise' something)
| Optimality Criteria | |||
| ID | Name | Description | Reference to mentioned use case objectives |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Use case conditions
| Use case conditions |
| Assumptions |
| [Assumption; assumed relation to other systems: e.g. higher level controller sends a signal] |
| Prerequisites |
| [Triggering Event (update of control signal or disturbance ...)]
|
General remarks
| General remarks |
| [everything which doesn't fit in any of the other categories] … |
Graphical RepresentationS Of Use Case
| Graphical representation(s) of use case |
| Examples of typical diagram types associated with use cases:
a) UML Use case diagram
b) UML Sequence diagram(s)
|
Technical Details
Actors
| Actors | |||
| Grouping | Group description | ||
|
|
| ||
|
|
| ||
|
|
| ||
| Actor name | Actor type | Actor description | Further information specific to this use case |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Step By Step Analysis Of Use Case Optional
Overview of use case scenarios
Identify all relevant use case scenarios; rel. e.g. to Sequence Diagram or Use Case diagram
| Scenario conditions | ||||||
| No. | Scenario name | Scenario description | Primary actor | Triggering event | Pre-condition | Post-condition |
| 1 |
|
|
|
|
|
|
| 2 |
|
|
|
|
|
|
| 3 |
|
|
|
|
|
|
Steps – Scenarios
Alternative / complementary to sequence diagrams.
| Scenario | ||||||||
| Scenario name : |
| |||||||
| Step No. | Event | Name of process/ activity | Description of process/ activity | Service
| Information producer (actor) | Information receiver (actor) | Information exchanged (IDs) | Requirements R-ID |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Common Terms And Definitions
| Common terms and definitions | |
| Term | Definition |
|
|
|
|
|
|
