You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »


Goals

  • Release stable version 1.0 of Apache StreamPipes
  • Ensure that post-1.0 versions are backwards compatible
  • Ensure that the feature set users expect from a 1.0 release is complete
  • Ensure that no critical bugs are present
  • Have the code base in a state which allows for future improvements


Non-Goals

  • Identify features we see as future improvements, but not critical for the 1.0 release


Features

Are there any features which are missing and critical for an 1.0 release?


IDDescription/Reason1.0 relevancy
F.1 Improved start pageThe StreamPipes start page is too much centered arount technical terms. Users should find resources based on physical assets such as machines. Links to directly create dashboards/pipelines should be present on the main entry page.
F.2 Improved asset managementUsers should be able to better link StreamPipes resources to physical assets (e.g., machines). Users should be able to filter resources such as pipelines and dashboards by their linked asset.
F.3 Details for connected data sourcesCurrently, after creating an adapter, there is no way to have an overview of the connected data stream. There should be a details page for each adapter showing the schema, live preview of the data and transformation rules.
F.4 OPC-UAFeature-completeness of the OPC-UA connectors. Currently, we are missing authentication options.
F.5 MQTTFeature-completeness of the MQTT connectors. 


Bugs

Are there any critical bugs we need to address before releasing 1.0?

IDDescription/Reason1.0 relevancy
B.1




Usability

Are there any usability painpoints we need to address before releasing 1.0?









User Experience (Usability of the UI)



Developer Experience (Usability of SDK/Extensions)



User Acceptance

Are there any issues which negatively impact user acceptance? E.g., frustrations users experience when trying the product for the first time or in the long run.



Code Quality

Where do we need to improve the code quality to make sure that future backwards compatibility is guaranteed?







  • No labels