COTRIX

From D4Science Wiki
Revision as of 14:33, 7 October 2014 by Anton.ellenbroek (Talk | contribs) (Created page with "the stand alone version of Cotrix (see the ICIS-cotrix for a review of the same capacity installed to realize the ICIS scenario) '''Functionality''' The Feature set specified b...")

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

the stand alone version of Cotrix (see the ICIS-cotrix for a review of the same capacity installed to realize the ICIS scenario)

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.