Addressing Legal Requirements in Requirements Engineering

Otto, Paul N.; Antón, Annie I.

doi:10.1109/re.2007.65

Cited by 128 publications

(144 citation statements)

References 33 publications

Supporting

Mentioning

143

Contrasting

Order By: Relevance

“…Grau et al compare and contrast six dialects of i* [14], while Regev and Wegmann review GORE methods in order to improve definitions of goal types using principles from regulation mechanisms [38]. Otto and Antón include goal modeling techniques related to law in their survey of RE and legal requirements [33], while Decreus et al look at six techniques transforming i* to business process models [11]. Mussbacher et al provide an extensive qualitative comparison of the Aspect-oriented User Requirements Notation (AoURN) to URN and other aspect-oriented techniques, including scenario-based techniques and other goal-oriented techniques [32].…”

Section: Related Workmentioning

confidence: 99%

Goal-oriented requirements engineering: an extended systematic mapping study

et al. 2017

View full text Add to dashboard Cite

Over the last two decades, much attention has been paid to the area of goal-oriented requirements engineering (GORE), where goals are used as a useful conceptualization to elicit, model, and analyze requirements, capturing alternatives and conflicts. Goal modeling has been adapted and applied to many sub-topics within requirements engineering (RE) and beyond, such as agent orientation, aspect orientation, business intelligence, model-driven development, and security. Despite extensive efforts in this field, the RE community lacks a recent, general systematic literature review of the area. In this work, we present a systematic mapping study, covering the 246 top-cited GORE-related conference and journal papers, according to Scopus. Our literature map addresses several research questions: we classify the types of papers (e.g., proposals, formalizations, meta-studies), look at the presence of evaluation, the topics covered (e.g., security, agents, scenarios), frameworks used, venues, citations, author networks, and overall publication numbers. For most questions, we evaluate trends over time. Our findings show a proliferation of papers with new ideas and few citations, with a small number of authors and papers dominating citations; however, there is a slight rise in papers which build upon past work (implementations, integrations, and extensions). We see a rise in papers concerning adaptation/variability/evolution and a slight rise in case studies. Overall, interest in GORE has increased. We use our analysis results to make recommendations concerning future GORE research and make our data publicly available.

show abstract

Section: Related Workmentioning

confidence: 99%

Goal-oriented requirements engineering: an extended systematic mapping study

et al. 2017

View full text Add to dashboard Cite

show abstract

“…For this study, we treat the policy documents from the Google Top 1000 websites and the Fortune 500 as separate sets for comparison. The only preprocessing done was to manually extract the plain text so that they could be analyzed using 15 http://cran.r-project.org/web/packages/tm/ the koRpus statistical readability package. 16 The Google Top 1000 had a median FRE of 31.82 with a standard deviation of 13.52 and the Fortune 500 had a median FRE of 27.49 with a standard deviation of 12.43.…”

Section: A Readability Resultsmentioning

confidence: 99%

“…Otto and Antón found both the identification of relevant laws and regulations as well as the difficulty of navigating and searching laws and regulations as important challenges for requirements engineering in a legal domain [15]. Herein, we provide initial research that addresses both concerns for requirements engineers concerned with policy compliance.…”

Section: A Policy Documents In Requirements Engineeringmentioning

confidence: 98%

“…For example, "collecting," "collected," and "collection" all refer to the same root concept: "collect." We used the Porter stemming algorithm [43], which is available as a part of the Snowball package in R. We removed stopwords using the list of common English stopword provided by the tm text mining package 15 for R. In addition to dropping extremely common words, we also dropped extremely rare words. We used term-frequency inverse-document-frequency (tf-idf) analysis to do so [44].…”

Section: B a Topic Model For Policy Documentsmentioning

confidence: 99%

See 1 more Smart Citation

Automated text mining for requirements analysis of policy documents

Massey

Eisenstein

Antón

et al. 2013

2013 21st IEEE International Requirements Engineering Conference (RE)

Self Cite

View full text Add to dashboard Cite

Abstract-Businesses and organizations in jurisdictions around the world are required by law to provide their customers and users with information about their business practices in the form of policy documents. Requirements engineers analyze these documents as sources of requirements, but this analysis is a time-consuming and mostly manual process. Moreover, policy documents contain legalese and present readability challenges to requirements engineers seeking to analyze them. In this paper, we perform a large-scale analysis of 2,061 policy documents, including policy documents from the Google Top 1000 most visited websites and the Fortune 500 companies, for three purposes: (1) to assess the readability of these policy documents for requirements engineers; (2) to determine if automated text mining can indicate whether a policy document contains requirements expressed as either privacy protections or vulnerabilities; and (3) to establish the generalizability of prior work in the identification of privacy protections and vulnerabilities from privacy policies to other policy documents. Our results suggest that this requirements analysis technique, developed on a small set of policy documents in two domains, may generalize to other domains.

show abstract

“…Thus, building a legally compliant system is an engineering problem and is recognized as a significant issue, especially in systems governed by law (Massey et al 2010;Maxwell et al 2012). This challenge comes from ambiguities and domain-specific definitions found in governmental rules (Breaux et al 2006;Otto and Antón 2007).…”

Section: Introductionmentioning

confidence: 99%

Regulatory Rules for Security Requirements of Financial Information Systems: Attempt to Formalize

Ebad

2017

Eur J Secur Res

View full text Add to dashboard Cite

As a result of the economic growth and increasing technology usage, financial systems are becoming pervasive and automate customer processes and data. These systems, like other systems that are governed by law, are required to comply with governmental regulations. However, this requirement is not easy to implement because of the challenge that comes from domain-specific definitions and the ambiguities that exist in laws. Moreover, mining financial data requires a combination of domain and technical knowledge plus an understanding of how the financial markets are manipulated. Thus, there is a business need to formalize security texts, extract rules, and then enforce them throughout the supply chain. Most of the approaches that have tried to achieve this need were validated on healthcare systems. Using a case study from Saudi Arabia, we applied a well-known approach proposed by Breaux and Antón on a quite different domain, Saudi stock exchange (Tadawul). Security in Saudi Arabia is an issue because of the highincome Saudi economy. Without such validation on non-healthcare domains, it is premature to automate Breaux and Antón approach which is currently performed manually. We also used readability analysis of Tadawul's regulations based on proven metrics. As a result, we extracted and formalized two rights, eight obligations, eighteen constraints, and seven rules. From readability view, Tadawul's regulations considerably need reading skills. Our analysis can help standards organizations, requirements engineers, systems administrators, and policy makers by ensuring that their systems conform to law.

show abstract

Addressing Legal Requirements in Requirements Engineering

Cited by 128 publications

References 33 publications

Goal-oriented requirements engineering: an extended systematic mapping study

Goal-oriented requirements engineering: an extended systematic mapping study

Automated text mining for requirements analysis of policy documents

Regulatory Rules for Security Requirements of Financial Information Systems: Attempt to Formalize

Contact Info

Product

Resources

About