MIRA - Model-based Integrated Requirements Analysis
What is MIRA
The Requirements Analysis (MIRA) supports you
to elicit, analyze, document and validate the information gathered in the requirements engineering phase.
MIRA offers three different artifacts:
- A Glossary is used to capture the vocabulary of the problem domain.
- The Requirement Sources (documents, external systems, stakeholders) give information about the origins of the requirements.
- The requirements package lists Requirements of the system under development.
MIRA offers two different representation forms of the artifacts:
- Structured text guides you eliciting all information needed in an informal way.
- Formalized requirements enable advanced analysis and testing methods
MIRA enables advanced tracing of its artifacts:
- The glossary and the requirement sources are highlighted automatically in every occurrence in a text.
- Requirements can be related to other requirements by n:m-relationships.
- Requirements can be traced to the component architecture.
Different methods support you analyzing the requirements:
- Check lists guide you through your requirements review phase.
- Automated check on textual and formalized requirements decrease the effort in the review phase.
- Create a test suite to test the formalized requirements against the architecture.
- Simulating requirements eases the validation of requirements.
Further functionality allows you to have different views on your Requirements Analysis:
- Export documents (html or doc) enables you to communicate with stakeholders that are not using AutoFOCUS3.
- A requirements hierarchy allows you to visualize tracing between requirements.
- Double-clicking on a folder gives you an overview of all contained elements.
- A requirements list under each component gives you a quick overview about all requirements belonging to one component.