6.2.5. Architecture¶
Architecture Verification and other RFG-based analyses
The children of this rule can be reordered.
Nested Rules
Instantiate and import an AUTOSAR classic ECU extract of System Description into an RFG |
|
Import the raw ARXML model into an RFG |
|
Add dependencies implemented via AUTOSAR classic RTE |
|
Performs a language schema verification on an RFG |
|
Analyse dependencies in IR and create a dependency graph (RFG) for it |
|
Extract Freedom from Interference Architecture Mapping from Annotations in existing Architecture and Mapping views |
|
Mapping Sanity Check |
|
Imports PlantUML C4 files into the RFG |
|
Architecture check using GXL files for architecture and mapping |
|
Analyze data flow to annotate variables referenced by accesses through pointer dereference |
|
Copy routines matching the given name pattern into the Entries View |
|
Import a GXL file as a view into an RFG |
|
Imports an IBM Rhapsody model into the RFG |
|
Instantiate and import an AUTOSAR classic ECU extract of System Description into an RFG |
|
Copy the content of the given RFG view to a new view (overwriting its previous content) and remove all nodes that are not children of the given root node |
|
Create new Node and Edge types |
|
Modifies the RFG using user-defined python functions |
|
Insert System node into view |
|
Obfuscate names in the given RFG |
|
Remove all view nodes that are not children of the given root node |
|
Remove the view |
|
Strip basepath from Source.Path attribute of nodes |
|
Compute the transitive closure of a given view with respect to a given edge type |
|
Copy the content of the given RFG view to a new view (overwriting its previous content) |
|
Copy the content of the given RFG view to a new view (overwriting its previous content) |
|
Check equality of the given two graphs |
|
Match two subgraph structures and transform found matchings |
|
Rename the given RFG view (overwriting a possibly existing view with target name first) |
|
Imports an Enterprise Architect model (in XMI1.1 format) into the RFG |
|
Exports an architecture view to a .qea file for Enterprise Architect (Unsupported preview) |
|
Imports an Enterprise Architect model from a .qea/.qeax file into the RFG |
|
Replace each non-hierarchical edge in a view by a (possibly empty) set of edges, depending on the edge type, its stereotype, and its target multiplicity |
|
Imports a PlantUML model into the RFG |
|
Set RFG view roles for architecture check in Gravis |
|
Create a hierarchical mapping |
|
Create a tagged-value based mapping |
|
Architecture modelling via Python scripts for both mapping and architecture |
|
Performs an architecture analysis (reflexion-based), creates result views and violation messages |
|
Use the processline framework for architecture analysis and customized RFG-based analyses |
|
Find cycles in the RFG and report them as violations |
|
Create a view containing cycles of a certain base view |
|
Create a view containing callgraph cycles at module/class level |
|
Create a view containing dead functions of a certain base view |
|
Report dead code findings considering several client projects (i.e., findings that appear in all projects) |
|
Report dead code findings considering several client projects (i.e. findings that appear in all projects) |
|
Create a clone view |
|
Exports a view of an RFG into a file in GXL format |
|
Save the intermediate RFG |
|
Use an architecture and mapping initially generated from code information to do architecture verification |
|
“Generate architecture from code, using a modelling including a detailed design down to attribute / operation level |
|
Generate UML-based Architecture from RFG representation of code |
|
Generate architecture from code, where directories are represented as packages and files as components %s |
|
Add members to the entries view if they and their parent types satisfy specific rules |
|
Extracts attached properties and dependency properties from code and inserts them in a separate RFG view |
|
Analyze COM usages in C# code and add dependencies in the RFG |
|
Additional transformation steps for C#-based RFGs |
|
Import content of XAML files and add entries from data bindings used in XAML files |
|
Export architecture view into Enterprise Architect format using EA’s COM-based API (Windows-only) |
Options
Setting an option for this rule means setting the default for all nested rules.
This rule shares the following common options: exclude_messages_in_system_headers, excludes, includes, justification_checker, post_processing, provider, severity
The following places define options that affect this rule: Analysis-GlobalOptions
This rule has no individual options.