8.5.1 Process Modeling for Requirements Engineering: A Medical System Case Study

Abstract

Abstract. The Unified Requirements Modeling Language (URML) was created to support early systems engineering; permitting the capture of process, potential variation points, hazards, threats and mitigations during the elicitation process. It has been used on Siemens projects, but to date they have been proprietary, precluding public exposure and limiting the critical review needed to refine and improve the language. To that end, a standard medical process, phlebotomy, was modeled in detail to determine the efficacy of the language. One of the authors of this paper is an expert in the area of medical diagnostics and provided the domain expertise. The modeling experience exceeded our expectations, and provided some unanticipated benefits. The results of our study are presented in this paper.

Informing the State of Process Modeling and Automation of Blood Banking and Transfusion Services Through a Systematic Mapping Study

“…Second, Unified Requirements Modeling Language (URML), initially reported in 2010 with a proposed meta-model, was used to model the activities, starting from the physician's request for a blood transfusion, to collecting blood. 27,37 URML 37 claims to attend to two key shortcomings of earlier modeling languages such as UML and SysML, namely 1) not providing comprehensive interdisciplinary visualization of requirements and system models, and 2) the lack of integrated modeling solutions with process traceability. In a workflow, a task can have four different states: disabled, enabled, running, or finished (DERF).…”

“…One outcome of this was the suggestion to revisit policies that involve variable factors in relation to compliance with policies. 24 example, the activity of requirements elicitation was accomplished by experts in the domain identifying hazard-driven mitigating requirements to show how problems can be addressed by the respective BB&T actors, 27 with identified hazards to respective use cases and mitigating requirements.…”