Product Backlog

An attempt to reorganize the Backlog such that it is easier for partners to engage in WP7.

Backlog

Each major item here represents a backlog item, e.g. a user story: "As a , I want [so that ]." Please prioritize at each Sprint conclusion.

The Backlog items are ordered by priority, separated in sections for better readability.

US-Data-Dictionary - As a modeler (WP3) and validator (WP4), I need a user-friendly data dictionary, so that I can work effectively.

US-Test-Meta-Model - As a validator (WP4), I need a meta model to represent tests that is aligned with the data dictionary.
US-Consistent-DataDictionary - TODO, complete review, etc.
US-Papyrus-Print - As a Validator (WP4), I want to "print" papyrus models, so that they can be made part of a report. (TODO: ensure it's part of the release)
US-Latex-Traceability - TODO see issue, High priority WP4
US-SysML-Traceability - As a modeler (WP3) and validator (WP4), I want traceability between ProR requirements and SysML model elements, so that I can understand how the requirements have been modelled.
US-Toolchain-Quality - As tool vendor (WP7), I want to offer my customers a toolchain of high quality.
US-Model-Validation - As a modeler (WP3) and validator (WP4), I want automatic SysML model validation.
US-Team-Support - As a modeler (WP3) and validator (WP4), I want to be able to work concurrently with other users.
US-Luna-Migration - As a modeler (WP3), I need a toolchain based on Luna, so that I can take advantage of the latest Papyrus improvements.
US-Developer-Doku - As a developer (WP7), I want to have clear development guidelines
US-User-Doku - As a modeler (WP3) or validator (WP4), I want to have comprehensive documentation, so that I find answers quickly both as a new and as advanced user.
US-Scade-Traceability - As a modeler (WP3) or validator (WP4), I want to be able to create and access traces to requirements and SysML.

US-SysML-to-B - As a modeler (WP3), I want to transform SysML to B, so that we have an alternative to Scade.