Directive
by
Oktay Türetken
—
last modified
Apr 26, 2012 11:35
Definitions
Term: term |
Domain: Cross-cutting issues | ||||
---|---|---|---|---|---|
Engineering and Design (KM-ED) |
Adaptation and Monitoring (KM-AM) |
Quality Definition, Negotiation and
Assurance (KM-QA) |
Generic (domain independent) |
||
D o m a i n : L a y e r s |
Business Process Management (KM-BPM) |
A compliance source from which the compliance requirements
originate [Turetken et.al., 2012]. A directive can be in the form of a regulation, legislation or law, such as Sarbanes-Oxley, HIPAA; standards or code of practices, such as ISO/IEC 27000 series; internal or external policies; or business partner contracts. A directive typically consists of a set of sections or clauses in a hierarchical form. Interpretation of these sources results into compliance requirements expressed at various abstraction levels [Turetken et.al., 2011]. |
|||
Service Composition and
Coordination (KM-SC) |
|||||
Service Infrastructure (KM-SI) |
|||||
Generic (domain independent) |
Competencies
- Tilburg: Business Process Compliance Management; Oktay Turetken, Amal Elgammal, Mike Papazoglou, Willem-Jan van den Heuvel
References
- [Turetken et.al., 2011] Turetken, O., Elgammal, A., van den Heuvel, W-J., Papazoglou, M. (2011). Enforcing Compliance on Business Processes through the use of Patterns, European Conference on Information Systems (ECIS 2011)
- [Turetken et.al., 2012] Turetken, O., Elgammal, A., van den Heuvel, W-J., Papazoglou, M. (2012). Capturing Compliance Requirements: A Pattern-Based Approach, IEEE Software, May/June 2012