Page History

Gather

• Capture requirements in dedicated diagrams, matrixes, and tables, create glossaries and use them consistently in your requirements
• Use for requirements: domain model based glossary , use cases, UI sketch diagrams

Import, interchange and synchronize

Once imported, requirements become first class citizens in the modeling world. Here is how support that:

• Importing requirements in ReqIF format from requirement management tools, like IBM DOORS 9.4 and 9.5, IBM DOORS Next Generation, PTC Integrity, Polarion, Siemens Teamcenter, and other tools
• Import requirements from the most commonly used formats as Comma Separated Values (CSV) and Microsoft Excel
• Keep data synchronized in real time with IBM DOORS and IBM DOORS NG via No Magic's Cameo DataHub

Visualize

Once requirements are imported into model or captured they can be visualized in multiple predefined views:

• Requirement table and diagram
• Relation Maps: -
  • Structure map – showing requirements hierarchy
  • Derivation map – showing requirements derivation
• Matrices:
  • Satisfy – showing requirements coverage with design
  • Verify – showing requirements coverage with test cases
  • Derive – showing requirement supplier - client relation
  • Refine - showing further refinement of requirements

Link

Align requirements with your model:

• Link and trace from requirements to other model elements of business, software, or systems architecture
• Link with artifacts imported from other tool chain products: PLM tools (e.g. Teamcenter), CAD tools (e.g. Catia), and others

Publish

• Built-in Microsoft Word Requirements report for publishing full requirements documentation for communicating to non-model users, reviewing or signing
• Web portal for requirements projects review by stakeholders. No product installation is required to read requirements - automated publishing to web server makes up to date requirements available for wide audience
• Fully customizable report templates to fit your organization requirements for document appearance and contents

Analyze

• Traceability - visualizing, navigating, and analyzing traces from requirements to architecture, business processes or other models related to requirements. Manage Changes with powerful traceability functionality.
• Validation - a facility for evaluating completeness and correctness of the models using built-in and custom validation suites. E.g. you will find not covered requirements, and it will be faster to communicate issues to other team members or fix them.
• Metrics – a new generation of model-based customizable metrics allows tracking of required project parameters and coverage with design or test cases. Metrics results are tracked over time and allows trends discovery
• Relation Maps show relations in dynamic and compact way:
  • Containment Map - shows requirements hierarchy map
  • Derivation Map – show requirements origination map
• Matrices:
  • Satisfy – shows requirements coverage with design
  • Verify – shows requirements coverage with test cases
  • Derive – shows requirement supplier - client relation
  • Refine - shows further refinement of requirements

Collaborate

Work on requirements in teams by using MagicDraw Teamwork Server repository which enables effective team collaboration, change and configuration management, allows for restricting access to the project, and multisite support

Simulate

Integration with OMG standard-based model execution, debugging, animation, and user interface prototypes supporting framework – Cameo Simulation Toolkit. It allows simulating future capability based on requirements parameters or imitate live user interface of future system

Tailor and Extend

• Support for custom requirement types and adding custom properties for requirements
• Validation of custom rules
• Ability to customize existing metric suites and introduce your own
• Customizable report templates for generating Microsoft Word, Excel, PowerPoint, or other types of documents tailored according to the requirements in your specific organization
• Ability to customize the product so that only the frequently used functionality is visible to end user
• Use OpenAPI or scripts to add additional functionality or automate repeatable modeling tasks