Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Eclipse WG Unconference France 2014 Requirements"

Line 5: Line 5:
 
== Interest in Audience ==
 
== Interest in Audience ==
  
* Looking for tools to fill the gap between Behavioral-Driven Development and RE
+
* Looking for tools to fill the gap between Behavioral-Driven Development and RE  
 
* RE-solution wanted for model-based development
 
* RE-solution wanted for model-based development
 
* Solution wanted for ReqIF-based RE
 
* Solution wanted for ReqIF-based RE
Line 18: Line 18:
 
* Formalization of Requirements.
 
* Formalization of Requirements.
 
* Make entry in PolarSys tools easy, via more user guidance and better default configurations, especially for novices.
 
* Make entry in PolarSys tools easy, via more user guidance and better default configurations, especially for novices.
 +
* Scalability
 +
 +
== Next Steps ==
 +
 +
* Two directions:
 +
  * More Tooling
 +
  * What to do with it
 +
  * Usability must be improved

Revision as of 09:25, 17 June 2014

Random Notes

  • Is there a RE tools for which we have requirements?

Interest in Audience

  • Looking for tools to fill the gap between Behavioral-Driven Development and RE
  • RE-solution wanted for model-based development
  • Solution wanted for ReqIF-based RE
  • Open Mind
  • Coming from Systems Engineering, interest in learning more about ReqIF, ProR, RMF
  • Coming from Topcased Requirements, looking for new trends
  • Requirements as Entry point for Polarsys Toolchain
  • Coming from DOORS, looking for alternative
  • Creating awareness of ReqCycle
  • Deepening knowledge on RE, i.e. ReqIF, looking for tool for safety requirements modeling
  • Looking for industry-strength RE solution
  • Formalization of Requirements.
  • Make entry in PolarSys tools easy, via more user guidance and better default configurations, especially for novices.
  • Scalability

Next Steps

  • Two directions:
 * More Tooling
 * What to do with it
 * Usability must be improved

Back to the top