bpchain / chainboard-prototype Goto Github PK

As a developer I want the prototype to have a 1-to-1 relationship between all components so that I can focus on the core features.

Acceptance criteria:

• Infrastructure is running as displayed in our diagram, with a single UI, proxy server, and Docker Swarm.

Acceptance Criteria:

• Raw data is displayed using simple charts, line charts, bar charts using a library (e.g. d3.js)

As a service provider I want the platform to be secure, scalable and stable.

As a user, I want to see a webapp that is consistently designed (e. g. does not show the angular favicon)

As a user I want to receive guidance to making decisions based on the requirements.
-> Decision table (DMN)

As a user I want to have a platform to easily see differences in the statistics so that I can compare different blockchains.

Is part of epic #3

Acceptance criteria:

• Data about mining rate and other metrics is gathered from Docker Swarm and communicated via defined Socket to the Server

As a service provider, I would like to rest assured that all of the software is tested thoroughly and the test coverage is as high as possible, so that no unwanted behaviour can occur.

As a service provider, I would like to have my service (the private chain) running on powerful hardware such as the FSOC-Lab, so that I can provide meaningful results.

As a user I want to have an easily understandable overview and a separated more detailed view on the statistics.

• The API-Server is running in a docker and can communicate with all other components

As a service provider, I would like to provide more metrics and aggregated data from the private chain to the user, so that the user's decision making is improved.

As a User, I would like the diagrams displayed to me to have a sensible scale (perhaps it would be better to separate public and private chains because of the extreme difference in magnitude).

As a service provider I want the different components of the service to communicate via REST-API.

As a service provider I want to have a barrier between observing-users and active changing-users so that the stability of the platform can be guaranteed.

Acceptance Criteria:

• Raw Data from Proxy is received
• User can choose from 3 presets of chain configuration
• User can choose between private and public ethereum chain to be displayed

• The frontend runs in docker and can communicate with all other components.

As a user I want to upload different BPMN-scenarios so that I receive recommendations for blockchains and their specifications.
-> NoProcesses, NoNodes, Hashrates, Blocktime, etc.

• get some kind of "hello world" running on the future soc lab

As a user I want to have a visualization of fluctuations and dynamics of private blockchains so that my decision-making is supported.

As a user, I would like to see the raw data received from both the public and the private chain in a table, so that I can compare them quickly and get an overview of all the actual numbers.

As a team member I want to provide a report and a poster for the future soc-lab day until the 17th of April so that we can continue to use the resources of the future soc-lab.

As a service provider, I would like the software to be as configurable as possible, and therefore would like to have as many parameters migrated into config-files.

As a service provider, I would like to store data from the public chain in the database, so I can aggregate over it and provide better information to the user.