Extension Details

Extensions add functionality to HeRA. Extensions can be classified as follows:

  • Construction Components: Allow to create requirements artifacts. Examples are the UseCaseExtension, RequirementsExtension?, and GlossaryExtension?.
  • Argumentation Components: Analyze the requirements artifacts and give heuristic feedback: the CritiqueExtension? evaluates if the requirements documentation adheres to best practices and wording rules. The GlossaryExtension? gives hints on technical terms that should be defined in a glossary. The SecReqExtension? helps to identify and refine security relevant requirements in a specification.
  • Inference Components: These type of components derive different kinds of models from requirements. This allows requirements engineers to take a new perspective and find inconsistencies in the requirements. Examples for this type of extensions are UMLUseCaseExtension, EPCExtension, and EffortEstimationExtension?.

HeRA is only useful, if at least one construction extension is installed. Construction extensions allow to construct requirements artifacts (e.g. requirements, use cases, glossaries). The main reason to use HeRA instead of word processors are the argumentation and inference components.

This page gives an overview of the extensions in HeRA. Each extension is an eclipse project. There are some reasonable combinations of extensions. To help building these standard distributions, we added a meta project. HeraMeta consists of an ant build-script that allows to compile all extensions belonging to these distributions.