| | |

Legal Compliance of Roles and Requirements

Ivan Jureta

The problem of regulatory compliance for a software system consists of ensuring through a systematic, tool-supported process that the system complies with all elements of a relevant law. To deal with the problem, we build a model of the law and contrast it with a model of the requirements of the system. In earlier work, we proposed a modelling language for law (Nòmos 2) along with a reasoning mechanism that answers questions about compliance. In this paper we extend Nòmos 2 to include the concepts of role and requirement so that we can reason about compliance in specific domains. Also, Nòmos 3 represents the distribution of responsibilities to roles, distinguishing social from legal roles. Nòmos 3 models allow us to reason about compliance of requirements and roles with the norms that constitute a law. A small case study is used to illustrate the elements of Nòmos 3 and the kinds of reasoning it supports.

Nomos-3-Legal-Compliance-of-Roles-and-RequirementsDownload

Ingolfo, S., Jureta, I., Siena, A., Perini, A. and Susi, A., 2014, October. Nomos 3: Legal compliance of roles and requirements. In International Conference on Conceptual Modeling (pp. 275-288). Springer, Cham.

Similar Posts

Requirements Loops: Decomposing an Example
| |

Requirements Loops: Decomposing an Example

ByIvan Jureta

An exercise I used to do with students in my Decision Analysis & Requirements Engineering lecture was to ask them to identify a problem that they have at university, and to describe it. My goal was to have them work in that lecture on problems that affected them. One group of students, in the 2019-2020…

| | | |

Acceptability Condition for the Relative Validity of Requirements

ByIvan Jureta

A requirements engineering artifact is valid relative to the stakeholders of the system-to-be if they agree on the content of that artifact. Checking relative validity involves a discussion between the stakeholders and the requirements engineer. This paper proposes (i) a language for the representation of information exchanged in a discussion about the relative validity of…

| | | | |

Tracing the Rationale Behind UML Model Change Through Argumentation

ByIvan Jureta

Neglecting traceability—i.e., the ability to describe and follow the life of a requirement—is known to entail misunderstanding and miscommunication, leading to the engineering of poor quality systems. Following the simple principles that (a) changes to UML model instances ought be justified to the stakeholders, (b) justification should proceed in a structured manner to ensure rigor…

| |

Structure and Design of Business Analysis and Requirements Engineering Methods

ByIvan Jureta

The work on Techne (here) can be seen as a case study in developing a new business analysis and requirements engineering mehods. I gave a general talk on this topic in 2013, at the Sauder School of Business, at the University of British Columbia, in Vancouver. The presentation used at the talk is below.

| | | |

Clarifying Goal Models

ByIvan Jureta

Representation and reasoning about information system (IS) requirements is facilitated with the use of goal models to describe the desired and undesired IS behaviors. One difficulty in goal modeling is arriving at a shared understanding of a goal model instance, mainly due to different backgrounds of the system stakeholders who participate in modeling, and the…

| | | | |

The Requirements Problem for Adaptive Systems

ByIvan Jureta

Requirements Engineering (RE) focuses on eliciting, modeling, and analyzing the requirements and environment of a system-to-be in order to design its specification. The design of the specification, known as the Requirements Problem (RP), is a complex problem-solving task because it involves, for each new system, the discovery and exploration of, and decision making in a…