Difference between revisions of "Cotrix"
(Created page with "'''Functionality''' The Feature set specified by the EA-CoP in several VME-DB workshops was fully implemented; VME’s can be described and maintained by users, with a VME-DB ma...") |
|||
| Line 1: | Line 1: | ||
| + | The Code list management in iMarine is achieved through a specialized tool; [[Ecosystem_Approach_Community_of_Practice:_Codelistmanager | Cotrix]]. Cotrix is more than a tool, and is rather a framework for software developers to manage reference data. Cotrix also aims to demonstrate that developing for the iMarine infrastructure does not limit the deployment options to one environment, but with some preparation, software components can be deployed both in the iMarine infrastructure as in a EA-CoP infrastructure. | ||
| + | |||
| + | This appraoch lowers the levels for collaborative development | ||
| + | |||
| + | |||
'''Functionality''' | '''Functionality''' | ||
Latest revision as of 16:29, 2 September 2014
The Code list management in iMarine is achieved through a specialized tool; Cotrix. Cotrix is more than a tool, and is rather a framework for software developers to manage reference data. Cotrix also aims to demonstrate that developing for the iMarine infrastructure does not limit the deployment options to one environment, but with some preparation, software components can be deployed both in the iMarine infrastructure as in a EA-CoPCommunity of Practice. infrastructure.
This appraoch lowers the levels for collaborative development
Functionality
The Feature set specified by the EA-CoPCommunity of Practice. in several VME-DB workshops was fully implemented; VME’s can be described and maintained by users, with a VME-DB manager fully in charge of users and content management. The capabilities were further enriched with mapping and historic support features, even beyond the initial requirements. The VME-DB team saw Generality in the approach and delivered solutions, and immediately recognized how and where VME-DB features could be re-utilized. No Security related issues were reported.
Usability
Some issues remain open on Human factors; the design and Aesthetics of iMarine solutions often do not match with existing or expected solutions. Especially the complexity of UI design could be reduced for end-users, who although appreciating the rich options, would sometimes prefer more productivity oriented screens and work-flows. This is considered a design issue that often occurs with new software release. The Consistency in design and work-flow of all iMarine components was appreciated. However, being newly released, the Documentation and training materials were deemed incomplete.
Reliability
No issues related to failures, recoverability, predictability, or accuracy that are not related to ‘poor’ data remain open as of July 2014.
Performance
No issues related to speed, efficiency, throughput, and response time remain open. There are still comments with the pre-views of the VREVirtual Research Environment.’s, but this is not solvable, as new fact-sheets have to be generate on the fly from a complex set of information.
Supportability
The EA-CoPCommunity of Practice. at large does not validate supportability. It considers the presented solution well designed, even with their focus on usability. They missed the localizability to support their local languages and metrics. Translation facilities were not expected or needed.
