Table 4 Catalog of functional automated analysis methods
From: A catalog of automated analysis methods for enterprise models
Type | Id | Domain | Name |
|---|---|---|---|
IoC | FIC001 | BA, DA, AA, TA | Impact of removing elements (Sunkle et al. 2013) |
FIC002 | BA, DA, AA, TA | Impact of removing a relation between two elements (Sunkle et al. 2013) | |
Al | FAG001 | BA, AA | Business-Application Alignment (The Open Group 2012) |
FAG002 | BA, TA | Business-Technology Alignment (The Open Group 2012) | |
FAG003 | AA, TA | Application-Technology Alignment (The Open Group 2012) | |
Coh | FCH001 | BA | Every business active structure has at least one direct/derived assignment (The Open Group 2012) |
FCH002 | BA | Every business process realizes as least one business service (The Open Group 2012) | |
FCH003 | AA, TA | Every application component uses infrastructure service, node, or device (The Open Group 2012) | |
FCH004 | BA, AA | Every application service is used at least in one business process (The Open Group 2012) | |
Cor | FCO001 | DA | Data security compliance at transport level (Guadamuz 2001) |
FCO002 | DA | Data security compliance at persistence level (Guadamuz 2001) | |
FCO003 | BA | Business layer single point of fail (Lam 2002) | |
FCO004 | AA | Application layer single point of fail (Schmidt 2006) | |
FCO005 | TA | Technology layer single point of fail (Schmidt 2006) | |
FCO006 | BA, DA, AA, TA | Overall architecture single point of fail (Schmidt 2006) | |
FCO007 | AA | Integration protocols compatibility at application service level (The Open Group 2012) | |
FCO008 | TA | Communication and transport protocols compatibility at technology level (Donoso 2009) | |
FCO009 | TA | Requirement compliance at infrastructure level (Florez et al. 2014) | |
Con | FCF001 | BA, DA, AA, TA | Metamodel conformance (Gómez et al. 2014) |
FCF002 | DA | Reference architecture conformance at Data/Information level (Angelov et al. 2009) | |
FCF003 | AA | Reference architecture conformance at Application level (Angelov et al. 2009) | |
FCF004 | AA | Reference architecture conformance at Application Integration level (Angelov et al. 2009) | |
FCF005 | TA | Reference architecture conformance at Technology level (Angelov et al. 2009) | |
Ga | FGP001 | BA | Business process Gap Analysis (The Open Group 2011) |
FGP002 | DA | Data/Information Architecture GAP Analysis (The Open Group 2011) | |
FGP003 | AA | Application Architecture GAP Analysis (The Open Group 2011) | |
FGP004 | AA | Application-Integration Architecture GAP Analysis (The Open Group 2011) | |
FGP005 | TA | Technology Architecture GAP Analysis (The Open Group 2011) | |
GS | FGR001 | BA, DA, AA, TA | Circular reference (Bollobás 1982) |
FGR002 | BA, DA, AA, TA | Derived associations (The Open Group 2012) | |
FGR003 | BA, DA, AA, TA | Element depth by typed relations (The Open Group 2012) | |
FGR004 | BA, DA, AA, TA | Minimum spanning tree (Bollobás 1982) | |
FGR005 | BA, DA, AA, TA | Shortest path by typed relations (Bollobás 1982) | |
FGR006 | BA, DA, AA, TA | Element dependency (Bollobás 1982) | |
Cou | FCN001 | BA, DA, AA, TA | Counting of elements by types (The Open Group 2012) |
FCN002 | BA, DA, AA, TA | Counting of relationships by types (The Open Group 2012) | |
Pr | FPR001 | DA, AA | Data/Information versus Application (Angelov et al. 2009) |
FPR002 | BA, DA | Data/Information versus Process (Angelov et al. 2009) | |
FPR003 | BA | Process responsibility assignment (Kofman et al. 2009) | |
HR | FHR001 | BA | Business layer passive elements RACI matrix (Fischer et al. 2007) |
FHR002 | AA | Application layer passive elements RACI matrix (Fischer et al. 2007) | |
FHR003 | TA | Technology layer passive elements RACI matrix (Fischer et al. 2007) |