Procasor To Eclipse Gui Mapping
This page describes GUI in the developed reprotool project and shows mapping from the procasor project. Reader should have at least basic user experience with procasor project.
The goal of the GUI mapping is tight integration with eclipse platform and extension of the existing views and components. For example, standard console view will be used to show the output of the linguistic tools.
Table of contents: <wiki:toc max_depth="2" />
Use case editor will be composed of the two main parts. In the upper section of the editor will be tree table showing steps of the use case. Lower section will be occupied with area for editing of the step.
Sentence analysis view will enable user to select type of the selected use case step (action type). After the action type is selected the view will be populated with additional boxes. For example Subject, Verb, Direct object and Indirect object boxes will be added when user selects Send action type.
Text in the box will correspond to the text marked in the Use case step editor.
- Allow multiple actions in one sentence. For example "Customer pays and System handles payment".
- Allow zero or more representative objects. For example "System sends information to the order system and customer care system". No representative object sentence example: "User logs in".
- Allow conditions, for example "If information includes payment information, system validates credit card".
All these improvements are based on the paper Improved Processing of Textual Use Cases: Deriving Behavior Specifications
In procasor are use cases bound to (procase) use case model. But this functionality seems to be important only for behavioral protocol generation.
Therefore it should be moved into use cases models, which will be included in procase plugin. Filtering of the use cases according to model may be added to the view menu in project overview.
