From 14266a9468f789397758a0cfddf3b3c5cfae3b71 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?C=C3=A9dric=20Bonhomme?= Date: Thu, 23 Nov 2017 07:25:18 +0100 Subject: [PATCH] Updated feature organizations (markdown) --- feature-organizations.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/feature-organizations.md b/feature-organizations.md index da8b1c1..0e3720e 100644 --- a/feature-organizations.md +++ b/feature-organizations.md @@ -16,10 +16,13 @@ software. - an other goal is to have a more decentralized model (the back office is a central point): - (public) risk models should be shareable (and exportable/importable) between organizations. This would be easy for a specific MONARC instance. Also this would be doable between MONARC instances via an API (with some development efforts). - the back office is a failure point. Models are directly provided by the database of the server, without a proper API. If the back office is down (or just the database service) some functionalities (like the creation of an analysis) of the front offices are blocked; -- when switching from [Angular to Vue.js](https://github.com/monarc-project/MonarcAppFO/wiki/feature-front-end) it will be a waste of time to rewrite views from the back office that are already present in MONARC (and views to manage servers and clients will simply disappear) +- when switching from Angular to Vue.js [3](https://github.com/monarc-project/MonarcAppFO/wiki/feature-front-end) it will be a waste of time to rewrite views from the back office that are already present in MONARC (because views to manage the servers and the clients could simply be deleted) -Consequently the main goal is to simplify the architecture of MONARC. Make MONARC more decentralized. And make future developments easier. +Consequently the main goals are: +- to simplify the architecture of MONARC; +- to make MONARC more decentralized; +- to make future developments easier. # Specifications