FDAF Metamodel

The metamodel used by FDAF.
Specurity Aspects
Name
Description
Translates a UML model extended with aspects into Rapide and Rapide Analysis results.
Specification Elements
Name
Description
A person who has a stake in the success of the enterprise, including architects, designers, requirement engineers, etc. who use the framework to develop a system design.
Entity used by the stakeholders, including a system design documented in the UML and a requirement specification that includes the system’s functional and non-functional requirements, and a set of formal methods used in the FDAF.
Entity produced by the stakeholders, including a set of aspect-oriented formal design models and the analysis results.
Provides a collection of reusable aspects for architects to use. An architect can search the repository to select the appropriate aspect(s) according to the system’s non-functional requirements.
Merges crosscutting concerns into one entity.

  • Security Aspects

    • Security Aspect Analysis

      Translates a UML model extended with aspects into Rapide and Rapide Analysis results.
      Specification Elements:
      Aspect repository
      Aspect
      Input
      Output
      Stakeholder
      Threats:
      Spoofing
      Tampering with Data
      Repudiation
      Information Disclosure
      Denial of Service
      Elevation of Privileges

    Specification Elements

    • Stakeholder

      A person who has a stake in the success of the enterprise, including architects, designers, requirement engineers, etc. who use the framework to develop a system design.
      Applies to:

    • Input

      Entity used by the stakeholders, including a system design documented in the UML and a requirement specification that includes the system’s functional and non-functional requirements, and a set of formal methods used in the FDAF.
      Applies to:
      Entity

    • Output

      Entity produced by the stakeholders, including a set of aspect-oriented formal design models and the analysis results.
      Applies to:
      Entity

    • Aspect repository

      Provides a collection of reusable aspects for architects to use. An architect can search the repository to select the appropriate aspect(s) according to the system’s non-functional requirements.
      Applies to:
      Entity

    • Aspect

      Merges crosscutting concerns into one entity.
      Applies to:
      Entity