Versions Compared

Old Version 7

changes.mady.by.user Alessandro Domanico

Saved on

compared with

New Version 8

changes.mady.by.user Alessandro Domanico

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Page Properties

Status

Status
colourYellow
titleIn progressIN PROGRESS
- missing library selection and Jira issues

Impact

Status
colourYellow
titleMedium

Driver

Alessandro Domanico

Approver

Claudio Rosazza

Contributors

Alessandro Domanico miz

Informed

Ilario Gavioli Alberto Mandelli

Due date

Resources

https://docs.google.com/document/d/1scNMAkKK9gLFbswDtkJr0bUiv2IPr7g9dakElBInvEs/edit?usp=sharing document

https://github.com/informatici/openhospital-ui

...

Option 1

Option 2

Option 3

Description

Replicate Open Hospital structure
(Spring + React + Material UI)

Use a different JS library
(e.g. Devias Kit, Creative Tim, Tabler, etc…)

Use existing softwares
(e.g. Grafana, Jasper, etc…)

Pros and cons

(plus) Same as Open Hospital, in the future the two projects could be easily merged

(plus) Homogeneity, same community can contribute to the project

(minus) The current material UI could be poor in terms of widgets and layout managers

(plus) Leverage special features

(minus) It may need specific knowledge

(plus) Some features granted by the software itself

(plus) Levering high quality features

(plus) In case of Jasper, it could be useful for porting the current reporting system in the “gui”

(minus) It could include several unwanted features making the application heavier than needed

(minus) Strong binding to an existing software can be risky

Estimated cost

Status
Status
colourGreen
titleSMALL
/
colourYellow
titleMEDIUM
/

Status
Status
colourRed
titleLarge
Status
colourGreen
titleSMALL
/
colourYellow
titleMEDIUM
/
Status
colourRed
titleLarge

Status
colourGreen
titleSMALL
/ status
colourYellow
titleMEDIUM
/
Status
colourRed
titleLarge

✅ Action items

  •  To decide the final Option
  •  To create Jira issues with analysis' outcome Alessandro Domanico and to group them under an Epic issue

\uD83C\uDF1F Outcome

Option 2: develop some components from scratch might be overkilling, one library will be used for the POC.