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.

Sign up for GitHub

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

Jump to bottom

[Task] - Persist RQA #17

Closed
2 tasks
levinkerschberger opened this issue May 15, 2023 · 1 comment
Closed
2 tasks

[Task] - Persist RQA #17

levinkerschberger opened this issue May 15, 2023 · 1 comment
Labels
task

Comments

@levinkerschberger
Copy link
Collaborator

levinkerschberger commented May 15, 2023 •
edited by franksn90
Loading

Goal

A storage will keep data out of our code.

Description

We are working with multiple types of data now.

  • Domain-Architecture-Mappings
  • Loadtest-Specification-Parameters
  • Runtime Quality Analysis Definitions
  • Domain-Storys

For all these, dqedit takes care of storing the data. dqanalyzer is just responsible for RQAs. Could be stored in same DB.

MongoDB, Relational Database, something else?
Choose a storage and document the reasons for the decision.

User Story
@julianbrott julianbrott changed the title [Task] - Choose Storage [Task] - Persist RQA Aug 3, 2023
@julianbrott
Copy link
Contributor

@levinkerschberger according to our documentation the task is done, should this ticket be closed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
task
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@julianbrott @levinkerschberger