Sentence examples for collaborative procedure from inspiring English sources
In this paper, we create specification properties to evaluate the level of success of a collaborative procedure formally.
Traditional PBD has focused on end-user programming for a single user, and does not support parallel collaborative procedure model construction from examples provided by multiple experts.
Once again, this was a collaborative procedure and students had to cooperate, negotiate, use the affordances of the multi-touch device and finally construct "their own unique artifact" that would finally compare with other teams' artifacts.
Level 1 cooperation is feasible for regulators who adopt ICH requirements but are not yet full members of ICH, and who can leverage on the assessments completed by stringent regulatory authorities (SRA) (WHO collaborative procedure 2017).
The Singapore experience (Deloitte & Touche LLP 2017; Lim 2016) can serve as a feasible model for other APEC economies as they develop strategies and procedures that leverage on assessments conducted by stringent regulatory authorities, in line with WHO's recommendation (WHO Good Regulatory Practices 2016; WHO collaborative procedure 2017).
Human-human collaborative procedures are developed to ensure that relevant information is correctly heard and actions are correctly executed.
To address this, previous efforts have used formal proof analyses to assess the robustness of collaborative procedures to miscommunications.
However, these analyses only indicate strict success or failure: outcomes that fail to capture the degrees of success of collaborative procedures.
We demonstrate the use of these properties to formally evaluate realistic collaborative procedures from a nuclear power plant with and without both generated miscommunications and erroneous human behavior.
The primary goal of this research is to create a suitable architecture for use, initially, in intranet (corporate portal) collaborative procedures, but also scalable for later use in more generic forms of ontology-driven knowledge management systems.
The scenarios with the coordination mechanisms are denoted as coordinated, whereas the uncoordinated term is used to designate deployments that do not use such collaborative procedures.
