Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DEECo feature model #170

Open
iliasger opened this issue Feb 3, 2015 · 1 comment
Open

DEECo feature model #170

iliasger opened this issue Feb 3, 2015 · 1 comment
Labels

Comments

@iliasger
Copy link
Member

iliasger commented Feb 3, 2015

Diagram that shows the variability points. First sketch:

Mandatory features

  • Execution – single-threaded (vs multi-threaded vs actor-based)
  • Sceduling - WALL-TIME vs DISCRETE
  • Distribution – centralized (single node with all components) vs decentralized
    • Scheduling policy (only with single-threaded execution) – RATE-MONOTONIC vs EDF
  • Simulation Logging for capturing the simulation progress with configurable levels
    • Simulation frames (structured records) with state of ensembles, etc.
    • For each class, specification of information to be logged (hierarchical logging)

Optional features

  • Network stack (no network stack goes together with centralized deployment)
    • Gossip – MANET vs IP-based vs MANET & IP-based
    • Network implementation – OMNET++ vs faking delays (direct)
  • Security – Stumpf’s
  • Trustworthiness – Stumpf’s
  • Visualization – Filipek’s
    • Extension point of visualization tool: property sheet
    • Visualization should work with logger (file) that can be visualized incrementally
  • Adaptation – IRM-based vs Period-Adapting (Hujecek)
  • Environment simulation – MATSIM vs SUMO vs custom
@iliasger
Copy link
Member Author

deecofeaturediagram

Green: Features implemented, but not yet integrated to jDEECo 3.0
Red: Features not yet implemented

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant