User story

Currently it is uncertain, if we need three or six connectors for the Bank-TaxAdvisor-Company scenario.
To find out, the connector samples need to be tested with switched consumer and provider roles.

Acceptance Criteria

• The test on the connector samples can be shown
• Each role should be able to act as consumer and provider

DoD General Criteria

• Product owner approved features
• Developers agreed to release

User story

1. As a user
2. I want / need to upload PDF documents
3. So that a knowledge graph can be created from the text information

Acceptance criteria

• If the document is of required .pdf format, upload and store the document.
• If the document is not of the required .pdf format, return an error message stating wrong format and upload cannot be done.
• User should be notified document(s) are uploaded successfully.

Definition of done (DoD)

• Added only after week 5
• The same for all features
• Here goes the project specific part

DoD general criteria

• Feature has been fully implemented
• Feature has been merged into the mainline
• All acceptance criteria were met
• Product owner approved features
• All tests are passing
• Developers agreed to release

Right now we are only able to exchange data one way between tax_advisor (consumer) and company (provider). We want to first of all implement it the other way around and also add the possibility to exchange the data with the third role, the bank

User story

As a tax advisor (:29191) , I am able to receive data / API endpoint from company (:19191) however I would like to able the send the data back to the company and also another role like bank (:39191) so that a multi way interaction is possible.

Acceptance Criteria

• In the resources and dataplane directories, create all the necessary json file to ensure an data interoperability / interaction between three roles. (register-data-plane.json, create-policy.json, fetch-catalog.json etc.)
• A single connector (example tax advisor) could receive but also send data using the same port 29191 and no need to create a new connector.
• For now, it is enough to use the sample data, asset and policy from the connector tutorial.
• If it is feasible, then dynamically create the json file, worst case scenario hard coded.

DoD General Criteria

• Feature has been merged into the main branch
• Feature has been added to the documentation
• Product owner approved features
• Developers agreed to release

User story

As a user, when I click the button to execute command in the connector, the connector should be able to establish a connection with other connector so that I can communicate with each other. Currently, when I click the command, all the steps that are necessary to establish a connection were not finalized (dataplane, accept policy, accept contract, fetch catalog).

Acceptance Criteria

• When I click the button, all the steps should be executed subsequently and the log where the connector is finalized should appear.
• There should be no crash again whenever a user click the button.
• Button should be moved in the send section in the dashboard.

DoD General Criteria

• Solution has been merged into the main branch
• All tests passed
• Acceptance Criteria is met.

User story

The metadata broker is is a node/element of the data space,
that stores and curates information about all the data within the data space.

Acceptance Criteria

• An independent node/element within the data space for the purpose of metadata storage (if possible maybe a connector with special features or an open source component from the Minimum Viable Dataspace)
• The metadata broker is accessible for every present and future connector in the data space

DoD General Criteria

• Feature has been merged into the main branch
• Feature has been added to the documentation
• Product owner approved features
• Developers agreed to release

User story

As a user, I would like to have a user documentation, so that I can understand better how the program works from the user perspective.

Acceptance Criteria

• There should be product vision section
• There should be product mission section
• (optional ) There should be usage section
• need to be added in the GitHub Wiki
• see https://github.com/amosproj/amos2023ws06-sales-lead-qualifier/wiki for reference
• a pdf file and md file should be created and the pdf file needs to be uploaded in the sprint-06/user-documentation.pdf

DoD General Criteria

• Feature has been merged into the main branch
• Feature has been added to the documentation
• Product owner approved features
• Developers agreed to release

User story

The build process video demonstrates that you mastered the build process.
Typically, the video will show your terminal window.

Acceptance Criteria

• Clone (the repository to start with a clean slate)

• Build (the product from the clean repo)

• Test (the product using automated test suites)

• Optional: Deploy (to production environment)

• Run (the product to show it starts up)

• The most common scenario is to git clone and then build, test, deploy, and run using your build tool. If you
  have a fully automated CI process using GitHub, please trigger and show that.

• If some steps cannot be automated, please carry them out by hand; you may want to copy over the
  commands from a separate text file to make things run smoothly.

DoD General Criteria

• Feature has been merged into the main branch
• Feature has been added to the documentation
• Product owner approved features
• Developers agreed to release

User story

So far we were only able to transfer JSON files between two connectors.
We now want to expand this to text files.

Acceptance Criteria

• Provider can send a text file.
• Consumer can receive the text file.
• Manual success in the backend is sufficient
• Documented where the transfer takes place

DoD General Criteria

• Feature has been merged into the main branch
• Feature has been added to the documentation
• Product owner approved features
• Developers agreed to release

User story

As DATEV, I would like to see a working frontend in the Kubernetes cluster via the flux pipeline to check if the application is successfully running in the cloud.

Acceptance Criteria

• Either the connector should be running and user could access the connector via <bank|tax|company>.amos.cloudness.dev:<:19193:29193:39193>
• The page should either have some kind of response, like hello world when accesing <bank|tax|company>.amos.cloudness.dev and not status error 404.

DoD General Criteria

• Solution has been merged into the main branch
• All tests passed
• Acceptance Criteria is met.

User story

As a user,
I would like to see the response text instead of response itself so that I know the basic frontend is working properly.

Acceptance Criteria

• Response should show the value saved into variable response and not "response" itself
• In the frontend, user should see the connector is running.

DoD General Criteria

• Solution has been merged into the main branch
• All tests passed
• Acceptance Criteria is met.

User story

Our application is currently running in the backend. As such a frontend, where user could see what is going on inside the connector is essential (moreover when we deployed via cloud). Furthermore, we are using CLI for most of the connector's command and it is tedious and not user-friendly. A frontend where user could send a request which translate to the command of the connector would be helpful for us in the long run. As a user, I would like to be able to differentiate between 3 connectors . The use of frontend is to differentiate the roles between connectors, i.e. tax advisor, company, and bank.

Acceptance Criteria

• If the connector is running, the user could access this via a website.
• Since there are 3 connectors that should be running, when user change port, I should be able to know which one is which role.
• A distinct feature to differentiate between 3 roles is necessary.
• It is sufficient, to just hard coded the login credentials when deploying the connector, that means directly deploy tax advisor's connector, company's connector, and bank's connector.

DoD General Criteria

• Feature has been merged into the main branch
• Feature has been added to the documentation
• Product owner approved features
• Developers agreed to release

User story

Our application is currently running in the backend. As such a frontend, where user could see what is going on inside the connector is essential (moreover when we deployed via cloud). Furthermore, we are using CLI for most of the connector's command and it is tedious and not user-friendly.
As a user, I should be able to see the button in the website where the connector is running and when I click this button, I should be able to run all the command line in the documentation, accepting policy, contract exchange, creating asset and transferring data without running the command line one by one in the terminal.

Acceptance Criteria

• The connector where the user run all the command line in the documentation, accepting policy, contract exchange, creating asset and transferring data without one by one running the command in the CLI.
• There should be a button that trigger these command lines in the webpage that host the connector port.
• (optional) it is best to receive a pop up box saying the processing is complete.

DoD General Criteria

• Feature has been merged into the main branch
• Product owner approved features
• Developers agreed to release

User story

Our application is deployed in cloud. After having implemented a working frontend with a locally accessible UI, the UI should be made accessible through the cloud also.

Acceptance Criteria

• Anyone could access the dataspace via website / https.

DoD General Criteria

• Feature has been merged into the main branch
• Feature has been added to the documentation
• Product owner approved features
• Developers agreed to release

Estimation: 8

User story

Our application is currently running in the backend. As such a frontend, where user could see what is going on inside the connector is essential (moreover when we deployed via cloud). Furthermore, we are using CLI for most of the connector's command and it is tedious and not user-friendly. A frontend where user could send a request which translate to the command of the connector would be helpful for us in the long run. This is issue focuses on running the accept policy without using the CLI.

Acceptance Criteria

• The connector where the user currently is could accept policy without running the CLI.
• There should a button or similar to accept policy and when the user clicks this button, behind the scene the command for agreeing to a policy should be executed and user should receive some kind of notification.
• User could run accept policy from the documentation without copying the command line in the terminal.

DoD General Criteria

• Feature has been merged into the main branch
• Feature has been added to the documentation
• Product owner approved features
• Developers agreed to release

User story

As a user, I would like to have an identity hub so that connector could get different roles. With different roles, we can see interplay of connectors.

Acceptance Criteria

• Discover where identity hub in the connector is implemented.
• After discovering the identity hub, the connector should either be given an identity from this hub or (optional) modify the identity hub to give user different identity.

DoD General Criteria

• Feature has been merged into the main branch
• Feature has been added to the documentation
• Product owner approved features
• Developers agreed to release

User story

As a company, I would like to have my own web frontend for the company connector so that I do not need to share port with other connectors, deploy separately in the cloud, and have my own functions.

Acceptance Criteria

• An additional file or configurations should be created for creating a web frontend for the company.
• The design could be taken from the dashboard from the frontend socket but it needs to show that this connector/page belongs to the company.
• When starting the connector by running the CLI, the connector should have its own web frontend when accessing the port.
• Accessing the company connector should now through different port (:3XXXX) and not localhost:3000.
• For testing purpose, you could either run the command starting the connector manually and see if there is a response or web using localhost:connector_port or create a dockerfile that run this connector and check locally.

DoD General Criteria

• Feature has been merged into the main branch
• Feature has been added to the documentation
• Product owner approved features
• Developers agreed to release

User story

As a user, I would like to have a build documentation, so that I can understand better how to build the program on a clean state computer.

Acceptance Criteria

• There should be a build process section
• There should be a requirement process section
• (optional ) Environment section
• need to be added in the GitHub Wiki
• see https://github.com/amosproj/amos2023ws06-sales-lead-qualifier/wiki for reference
• a pdf file and md file should be created and the pdf file needs to be uploaded in the sprint-06/build-documentation.pdf
• ReadMe file should also be updated.

DoD General Criteria

• Feature has been merged into the main branch
• Feature has been added to the documentation
• Product owner approved features
• Developers agreed to release

User story

Our application is currently running in the backend. As such a frontend, where user could see what is going on inside the connector is essential (moreover when we deployed via cloud). Furthermore, we are using CLI for most of the connector's command and it is tedious and not user-friendly. A frontend where user could send a request which translate to the command of the connector would be helpful for us in the long run. This issue answers the question, is it feasible to embed a frontend framework in our connector?

Acceptance Criteria

• Agree for a uniform framework that all the team members will use.
• Check the feasibility of embedding a frontend framework in the connector.
• If embedded is possible, user could check via website if the connector is running.

DoD General Criteria

• Feature has been merged into the main branch
• Feature has been added to the documentation
• Product owner approved features
• Developers agreed to release

Estimation: 5

Acceptance criteria:
A demo of successful data transfer from one connector to another can be presented.
Policies are not important.
Type of data (e.g. json, CSV) is also not important.

User story

As a connector, I would like to be able to check the other connector's status, whether they are running or stop so that I know I could or could not communicate with that connector.

Acceptance Criteria

• In the home section of the connector's dashboard, there should be a button. Next to the button there should be a drag down button to choose which connector to be checked.
• When a user clicks this button after selecting the desired connector, a request is sent to the other connector and depending on the result, the user / connector should receive a pop up message / notification, that says the connector is running / not available.

DoD General Criteria

• Feature has been merged into the main branch
• Feature has been added to the documentation
• Product owner approved features
• Developers agreed to release

User story

The catalog is a database table with information of all the data within the dataspace.

Acceptance Criteria

• The catalog is accessible by the metadata broker only
• Possible table columns: title, description, connector_id, ...

DoD General Criteria

• Feature has been merged into the main branch
• Feature has been added to the documentation
• Product owner approved features
• Developers agreed to release

User story

As a team member of AMOS Team 2, I would like to refactor and unify all changes made by the SDs so that in the future the effort to refactor will not be high.

Acceptance Criteria

• Delete unused branches, branches must really not be used or deleted branches would not affect the flux pipeline.
• Merge all changes that made in branches, resolved conflicts if necessary.
• Agree to a naming convention for the changes made by the SDs.
• Agree to a naming convention for the connector (producer/consumer vs bank/tax advisor/company

DoD General Criteria

• Solution has been merged into the main branch
• All tests passed
• Acceptance Criteria is met.
• Developers agree to release in main branch.

User story

Our application is currently running in the backend. As such a frontend, where user could see what is going on inside the connector is essential (moreover when we deployed via cloud). Furthermore, we are using CLI for most of the connector's command and it is tedious and not user-friendly. A frontend where user could send a request which translate to the command of the connector would be helpful for us in the long run. This issue focuses on asking and exchanging contracts to prepare the connector for data transfer.

Acceptance Criteria

• There should a button or similar for contract exchange. and when the user clicks this button, behind the scene the command for agreeing for exchanging contract should be executed and user should receive some kind of notification or feedback what is going on.
• The command line that need to be executed behind the scene is create contract definition, fetch catalog, negotiate contract, and get contract agreement id from the documentation.
• Currently, we will use the default configuration, but in the future when user click this button, the user could define the contract. Consider future use while resolving this issue.
• User could all contract command line from the documentation without copying the command line in the terminal or without running the CLI.

DoD General Criteria

• Feature has been merged into the main branch
• Feature has been added to the documentation
• Product owner approved features
• Developers agreed to release

User story

As a user, I would a new dockerfile so that I can easily build 3 connectors and easily deployed them on different ports.

Acceptance Criteria

• The Dockerfile should contain the command to run the frontend automatically for each web frontend.
• The Docker compose file needs to be updated so that when running the command docker compose up, docker could build all the images and run the connector on different ports.

DoD General Criteria

• Feature has been merged into the main branch
• Documentation should be updated
• Product owner approved features
• Developers agreed to release

User story

As a user,
I would like to see the status of the connector so that I know that the connector is running. I would like to be able to see that status without refreshing the page.

Acceptance Criteria

• When the user enter the login credentials (example bank 123) I should be able to see the connector status is running without refreshing the page.

DoD General Criteria

• Solution has been merged into the main branch
• All tests passed
• Acceptance Criteria is met.

User story

As a PO, I would like to have an updated Dockerfile so that I can build the application easily using Docker.

Acceptance Criteria

• The Dockerfile should reflect all changes happening in the main branch (03.06.2024)
• The PO should only build the application using the docker command, and the application should start running, that means no additional commands like npm to start local webhosting.
• Update the documentation / readme file.

DoD General Criteria

• Feature has been merged into the main branch
• Product owner approved features
• Developers agreed to release

User story

As a tax advisor, I would like to have my own web frontend for the tax connector so that I do not need to share port with other connectors, deploy separately in the cloud, and have my own functions.

Acceptance Criteria

• An additional file or configurations should be created for creating a web frontend for the tax advisor.
• The design could be taken from the dashboard from the frontend socket but it needs to show that this connector/page belongs to the tax advisor.
• When starting the connector by running the CLI, the connector should have its own web frontend when accessing the port.
• Accessing the tax advisor connector should now through different port (:2XXXX) and not localhost:3000.
• For testing purpose, you could either run the command starting the connector manually and see if there is a response or web using localhost:connector_port or create a dockerfile that run this connector and check locally.

DoD General Criteria

• Feature has been merged into the main branch
• Feature has been added to the documentation
• Product owner approved features
• Developers agreed to release

Please fetch the codebase from Eclipse EDC an check it into your Repo

Acceptance criteria:

• Two instances of a connector preferably with a docker image each are pushed to the main branch.
• The code base is a useful first draft for DATEV to fetch to their repository.

User story

Any time a connector claims access to protected data, the identity hub needs to check for authorization.
Authorization describes the process of giving or denying the user permission to access the data.

Acceptance Criteria

• The identity hub checks for a contract between parties
• If a valid contract exists, data transfer is permitted
• If no valid contract exists, permission is denied

DoD General Criteria

• Feature has been merged into the main branch
• Feature has been added to the documentation
• Product owner approved features
• Developers agreed to release

User story

As a user, I would like to be able to upload a text or json file to the react frontend application, so that I can transfer this file later.

Acceptance Criteria

• In the send section (app dashboard), there should be a text or button "submit" that asked the user for a file to be uploaded when clicked.
• The frontend should change the state, to show that the user file is already uploaded and then send a request to the backend.
• The backend should be able to target these files.
• Since, there is no persistent data storage yet, the server should simply give a response to the user which is the name of the file to the frontend.
• In the sent section (app dashboard) the user should be able to see the name of the file that user has submitted.
• see https://www.geeksforgeeks.org/file-uploading-in-react-js/ for reference.

DoD General Criteria

• Feature has been merged into the main branch
• Feature has been added to the documentation
• Product owner approved features
• Developers agreed to release

Estimation: 3

Acceptance criteria:
The connection process of two connectors on localhost is documented in detail.
How do we establish the connection?
What kind of communication takes place?
What happens in what order?
Who needs what kind of information from whom?

User story

As a user, I would like to know the capability of the EDC Connector, therefore it make senses to have 3 connectors containing 3 different roles to have multiple connections, This issue focuses on CRUD operations on the databases / persistent storage.

Acceptance Criteria

• Create: Create a new entry or role and save it into the persistent storage.
• Read: The connector could read user/role information from the persistent storage.
• Update: Update the entry in the persistent storage.
• Delete: Delete an existing role in the persistent storage.

DoD General Criteria

• Feature has been merged into the main branch
• Feature has been added to the documentation
• Product owner approved features
• Developers agreed to release

Hello together,

you will find a details about the use-case in die folowing document at ... https://github.com/projectamoscd/docs/blob/main/AMOS-IDS-UseCase.pptx

Best, Martin

User story

As a user, I would like to have a design documentation, so that I can understand how our application is designed.

Acceptance Criteria

• There should be at least a diagram containing the initial design of our work.
• There should be a component section
• (All components should be explained
• Must be added to the GitHub Wiki
• see https://github.com/amosproj/amos2023ws06-sales-lead-qualifier/wiki for reference
• a pdf file and md file should be created and the pdf file needs to be uploaded in the sprint-06/design-documentation.pdf

DoD General Criteria

• Feature has been merged into the main branch
• Feature has been added to the documentation
• Product owner approved features
• Developers agreed to release

User story

As a connector,
I want to be able to connect to other connector in cloud.

Acceptance Criteria

• Connector should be able to connect with other Connectors, communication is possible.
• configurations may need to be modified.

DoD General Criteria

• Feature has been merged into the main branch
• Feature has been added to the documentation
• Product owner approved features
• Developers agreed to release

User story

As a user,
I would like to see the status of the connector so that I know that the connector is running. I would like to be able to see that status without refreshing the page.

Acceptance Criteria

• The connector status should be adjusted dynamically according to the user role. if bank is logged , the message "bank connector is running" should show up without refreshing the page. This applies to tax and company.

DoD General Criteria

• Feature has been merged into the main branch
• Feature has been added to the documentation
• Product owner approved features
• Developers agreed to release

User story

The identity hub is is an node/element of the data space,
that ensures authorization for secure data transfer between two connectors.

Acceptance Criteria

• An independent node/element within the data space for the purpose of authorization exists (if possible maybe a connector with special features or an open source component from the Minimum Viable Dataspace)
• the identity hub is accessible for every present and future connector in the data space
• it is enough for the connector to connect to the Identity hub first.

• DoD General Criteria

• Feature has been merged into the main branch
• Feature has been added to the documentation
• Product owner approved features
• Developers agreed to release

User story

As a user, I would like to have a clear user interface to be able to do a connector's job, i.e. I could transfer the data via the UI and not from CLI. This issue is design only.

Acceptance Criteria

• There is an option to transfer data.
• There is an option to exit the connector, back to the login page.
• There is an option to accept policy.
• There is an option for contract
• Minimum design UI in the "homepage" of the connector or in this case dashboard.
• A html file in the main branch.
• should be compatible with the current framework (react)

DoD General Criteria

• Feature has been merged into the main branch
• Feature has been added to the documentation
• Product owner approved features
• Developers agreed to release

Estimation : 5

Acceptance criteria:
There is a docker image for a single connector available in order to start the deployment pipeline.

User story

At the beginning of every browser session,
the user needs to authenticate himself.
With a username and password he proves, who he claims to be.

Acceptance Criteria

• Username and password are fetched after user hits enter
• Password gets hashed and compared to the hashed password in the database
• If username doesn't exist or password is incorrect, we should be redirected to the login page with error message
• If username exists and password is correct, we should be redirected to the connector UI
• The connector UI should not be accessible via the URL only (meaning without authentication)

DoD General Criteria

• Feature has been merged into the main branch
• Feature has been added to the documentation
• Product owner approved features
• Developers agreed to release

User story

As a bank, I would like to have my own web frontend for the bank connector so that I do not need to share port with other connectors, deploy separately in the cloud, and have my own functions.

Acceptance Criteria

• An additional file or configurations should be created for creating a web frontend for the bank.
• The design could be taken from the dashboard from the frontend socket but it needs to show that this connector/page belongs to the bank.
• When starting the connector by running the CLI, the connector should have its own web frontend when accessing the port.
• Accessing the bank connector should now through different port (:1XXXX) and not localhost:3000.
• For testing purpose, you could either run the command starting the connector manually and see if there is a response or web using localhost:connector_port or create a dockerfile that run this connector and check locally.

DoD General Criteria

• Feature has been merged into the main branch
• Feature has been added to the documentation
• Product owner approved features
• Developers agreed to release

User story

The catalog needs to be dynamically editable

Acceptance Criteria

• Create: the metadata broker can create new valid entries in the catalog
• Read: the metadata broker can read entries from the catalog (with and without filtering)
• Update: the metadata broker can update existing entries in the catalog
• Delete: the metadata broker can delete existing entries in the catalog

DoD General Criteria

• Feature has been merged into the main branch
• Feature has been added to the documentation
• Product owner approved features
• Developers agreed to release

User story

As a user, I would like to have a clear user interface to be able to input my login credentials to the connector. This issue is only design only.

Acceptance Criteria

• Minimum design of UI during login page
• User could input username and password.
• an html file in the main branch
• should be compatible with the current framework (react)

DoD General Criteria

• Feature has been merged into the main branch
• Feature has been added to the documentation
• Product owner approved features
• Developers agreed to release

Estimation: 5

Acceptance criteria:
A working sample of a Gaia-X service.

User story

As a user, I would like to have my own connector so that I can transfer data to other connector which is owned by another user.

Acceptance Criteria

• In the backend there should 3 port that are in used as such 3 connectors that are running.
• All ports must be different.
• When user enters the the dashboard, user could differentiate which connector belongs to which role (tax advisor, company, or bank)
• For easy navigation, the dashboard should include 3 button for each connector that will redirect the user to that connector status.
• The connectors should be renamed to tax advisor, company, and bank.

DoD General Criteria

• Feature has been merged into the main branch
• Feature has been added to the documentation
• Product owner approved features
• Developers agreed to release

User story

As a user, I would like to know the capability of the EDC Connector, therefore it make senses to have 3 connectors containing 3 different roles to have multiple connections, This issue focuses on creating database to save these 3 connectors roles.

Acceptance Criteria

• A database or persistent storage that could save a connector role information and possibly credentials.

DoD General Criteria

• Feature has been merged into the main branch
• Feature has been added to the documentation
• Product owner approved features
• Developers agreed to release