A Method for Identifying Software Requirements Based on Policy Commitments
Authors:
- Jessica D. YoungJYJessica D. Young
- Annie I. AntonAAAnnie I. Anton
- 1 September 2010
- conference paper
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- No. 1090705X,p. 47-56
Abstract
Online policy documents-such as privacy policies, notices of privacy practices, and terms of use-describe organizations' information practices for collecting, storing, and using consumers' personal information. Organizations need to ensure that the commitments they express in their policy documents reflect their actual business practices. This compliance is significant in the United States where the Federal Trade Commission regulates fair business practices. Therefore, the requirements engineers developing systems for organizations need to understand the policy documents in order to know the information practices with which the software must comply. The requirements engineers also must ensure that the commitments expressed in these policy documents are incorporated into the software requirements. In this paper, we present a summative case study of a commitment analysis approach. The approach was developed during a formative case study of four healthcare organizations' policy documents. Within this approach, we obtain requirements from policy documents based on our theory of commitments, privileges, and rights. During our summative case study we applied our commitment analysis approach to eight healthcare organizations' policy documents in order to validate the methodology. We discuss the results of the summative study, in which we found that most of the statements express organizational practices or procedures. The top seen classification conveys pledges made by the organization based on organizational practices. The second most seen classification expresses actions that the user is entitled to perform based on organizational practices.Keywords
This publication has 26 references indexed in Scilit:
- Commitment analysis to operationalize software requirements from privacy policiesRequirements Engineering, 2010
- Evaluating existing security and privacy requirements for legal complianceRequirements Engineering, 2009
- Towards a Framework for Tracking Legal Compliance in Healthcare2007
- Financial privacy policies and the need for standardizationIEEE Security & Privacy, 2004
- A requirements taxonomy for reducing Web site privacy vulnerabilitiesRequirements Engineering, 2003
- Precluding incongruous behavior by aligning software requirements with security and privacy policiesInformation and Software Technology, 2003
- Goal decomposition and scenario analysis in business process reengineering1994
- Goal-directed requirements acquisitionScience of Computer Programming, 1993
- Program design by informal English descriptionsCommunications of the ACM, 1983
- Some Fundamental Legal Conceptions as Applied in Judicial ReasoningThe Yale Law Journal, 1913