Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
C
citygml-energy
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 26
    • Issues 26
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 0
    • Merge Requests 0
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • energyade
  • citygml-energy
  • Issues
  • #149

Closed
Open
Opened Nov 27, 2017 by Moritz Robert Lauster@mlausterMaintainer

Modularization of the Energy ADE UML model

Created by: JoachimBenner

We frequently speak about Energy ADE modules like "Building physics module" or "Energy systems module", but formally speaking the UML model has no modular structure. This at least hinders the maintenance of the data model.

Therefore, for a first official version a number of sub-folders should be integrated in the main folder EnergyADE of the UML model:

  • EnergyADE Core
  • Building Physics
  • Occupance
  • Material and Construction
  • Energy systems
  • Time series and schedules

In each of these sub-folders the corresponding UML elements and diagrams are aggeegated. It is debatable whether this modular structure of the conceptional model is also reflected in the GML encoding (separate namespaces and XML-schema files for different modules). I personally strongly prefer to stay with one Energy ADE namespace and one schema file.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: energyade/citygml-energy#149