Bugzilla – Full Text Bug Listing
| Summary: | Different perspectives for different approaches of using Papyrus | ||
|---|---|---|---|
| Product: | [Modeling] Papyrus | Reporter: | Tatiana Fesenko <tatiana.fesenko> |
| Component: | Core | Assignee: | Project Inbox <mdt-papyrus-inbox> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | ansgar.radermacher, sebastien.gerard, vincent.lorenzo, yann.tanguy |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Tatiana Fesenko
(In reply to comment #0) > Some groups of users may need some kinds of diagrams and don't nedd others. > Even the same group can use different diagrams in different phases of > development. In that case unused CreateActions could be annoying. > > Introduce different perspectives for SysML, UML, etc. Basically different > perspective mean to filter unused CreateDiagramAction in the toolbar. > > It also would be helpful to allow the user to manage perspectives and define > his own. This comment is a bit off-topic: I find the current Papyrus perspective really annoying, as it removes important features. It disables for instance the "Check-for-updates" and "Install new SW" items which are crucial. Another bug in it by the way: Window->Show view still contains "wrong" model explorer (not the Papyrus model explorer) which will confuse all but the experienced users. You still can adapt the perspective configuration to your needs (right-click / customize perspective), add "Check-for-updates" and "Install new SW" for instance (which in my opinion is crucial for Eclipse but not for UML modeling). That said, I also find the default Papyrus perspective too restrictive and probably confusing for Eclipse users, this perspective will be modified. Currently the "new project / model" wizard starts the selection of the language (UML Model, UML Profile, SysML Model, other UML or non-UML model). This language is then used in the wizard to filter the available diagram and model templates. At the end of the creation wizard, the user is asked whether the perspective should be switch to Papyrus perspective or not. The user should have the choice to switch to Papyrus generic perspective or to more specific perspective relevant for the language selected. Let's say one decide to use Papyrus for SysML modeling exclusively, it should be possible to select "SysML" during the wizard as the modeling language and to switch to a SysML perspective which mask any non-SysML diagrams. Perspective is principally used here to filter the visible diagram in the GUI (although it could also be used to filter other menu or action). Another expected usage of perspectives is to provide configuration support for specific methodologies. Lets consider a model based process where one start modeling with requirement modeling (using SysML Requirement), then create high level feature description (with UML Use Case Diagram), then create a functional model (EAST-ADL2 Diagram), then create a software and hardware description (UML/Marte related Diagrams). In such a case it is preferable to configure the tool giving access to a precise set of diagrams depending on the modeling activity that the user is supposed to realize. Perspective appears to be a good candidate for such tool methodology or company-specific configurations. The Architecture Framework and associated viewpoint definitions address this. |