You are here:
(25 Jan 2007,
jUCMNav currently does not support scenarios, unlike its predecessor UCMNav. The goal of this project is to re-implement the scenario traversal mechanisms in jUCMNav to deprecate UCMNav completely.
Why does jUCMNav need to support scenarios?
. On-the-fly verifications that the author expressed the desired behaviour in the UCMs.
Regression testing purposes
. Verify that old behaviour is respected after changes.
. We need dynamic traversal mechanisms in order to generate MSCs or FitNesse tests from UCMs.
High Level Goals
Extensibility: The project lays the groundwork for what will come in future years. This is one of UCMNav's major flaws and we wish to avoid having history repeat itself.
Usability: The second main goal is to offer a usable framework; UCMNav's interface was too restrictive and didn't match the user's regular workflow.
Reusability: The scenario project contains complex algorithms. These should be broken down into reusable parts (to be used in the import/export wizards or future analysis functionality, for example).
Scenario Brainstorming, April 27th
Define the data model
Define scenario UI
- based on
Implement scenarios structure (views) with trivial text-editor.
Plan and implement simple core algorithm.
Enhance textual editor used.
Iteratively extend and refine the model
iew wiki text
ore topic actions
Topic revision: r4 - 25 Jan 2007,
ProjetSEG Web Home
Copyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Foswiki?