Analyse efficace des Cas d’Utilisation dans Enterprise Architect

Enterprise Architect 12.1, Build 1229.

Enterprise Architect fournit un centre d’apprentissage intégré avec un guide étape par étape pour vous aider à démarrer.

The UML Tutoriel sur le site Web de Sparx Systems peut vous aider à fournir un aperçu technique des 13 diagrammes UML pris en charge par Enterprise Architect.

Vous pouvez examiner la vidéo suivante du site communautaire qui présente la création d’un diagramme et la création d’un cas d’utilisation.
http://community.sparxsystems.com/tutorials/951-exploring-enterprise-architect-through-video-part-4

Veuillez vous référer à la rubrique Aide Agile Exigence Processes. Le site communautaire fait également référence à Agile Business Analyst.

Automatique. Les éléments qui apparaissent dans le Glossaire sont automatiquement mis en surbrillance lorsqu’ils sont utilisés dans des champs de texte dans Enterprise Architect.

Oui, vous pouvez facilement exporter le Glossaire d’Enterprise Architect vers un document Word, RTF ou PDF. Vous pouvez apprendre à le faire à partir de la rubrique Aide System Document Templates. See the Glossaire section.

Le Glossaire est stocké dans le référentiel modèle d’Enterprise Architect, à l’intérieur de la table: t_Glossaire.

Glossaire definitions are not stored or displayed in the Project Browser. To access the Glossaire, use the Project menu, or the keyboard shortcut, Alt+2.

Yes, through the Automation Interface or via the table in the model repository, t_glossary. For more information on using the Automation Information to access the Glossaire, see the Help topic Term Class.

Yes. It is possible to undertake an XML import of Glossaire terms.

The related Import process covers Glossaire terms in the exported XML format. For an alternative using an Excel import see: Community Site article Simple VBA Excel to EA importer.

Yes.

1. Select the Actor you would like to change.
2. Right-click to invoke the context menu.
3. Choose Appearance | Select Alternate Image. This will open the Image Manager, which will display a list of loaded images. You can use a button on the right of screen to Add New images.
4. Choose a suitable image.
5. Click OK to replace the stick figure.

For more information, see the Help topic Using the Image Manager.

It is also possible to download an image library from the Sparx Systems website.

Include and Extend are UML connector types. For details, see the Help topics Include and Extend.

Non. Ceci n’est pas supporté

A Cas d’Utilisation scenario is intended to be a simple scenario conveying a single alternate flow. Where there is more complex detail involving multiple alternate flows, then it is best depicted using an Extend connection to the alternate Cas d’Utilisation and placing the nested Alternate scenario in this extended Cas d’Utilisation.

Non.

Use the in-built diagram generation to create an Activity diagram.

Oui. You can automatically create a Realization relationship between a Cas d’Utilisation and a Exigence. Simply drag the Exigence from the Project Browser onto a Cas d’Utilisation diagram. If the relationship already exits, Enterprise Architect will automatically add the dependency relationship where it already exists.

You also have the option of placing a Exigence or a Cas d’Utilisation onto a blank diagram and using Insert All Related Elements command to build an appropriate Dependency diagram.

A realization connector shows that the source element implements, or realizes, the destination element. Dependency connectors model a much broader range of relationships between elements. Once you create a Dependency you can further refine its meaning by applying a specialized stereotype.

For more detailed explanations, please refer to the Help topics Dependency and Realization.

Oui

When you have created a structured scenario, you can generate any of these diagrams from it:

• Activity
• With ActivityParameter
• With Action
• With Action Pin
• Rule Flow
• State
• Sequence
• Robustness

For more information, please refer to the Help topic Generate Diagrams.

The values in the 'Uses', 'Results' and 'State' columns, whilst optional, are significant if you want to generate a diagram from the specification.

Result: Indicates the result or outcome of completing this step. This information is often quite valuable for testing purposes to ensure accurate and timely results are being produced.

State: The name of the State that the system enters, as a result of completing a particular step in the scenario. This information is typically used to create a State machine so Business Analysts can identify the contributing factors that cause State Change within a system.

Yes, the Structured Scenario Editor was available in Enterprise Architect 11.

It was first introduced in Enterprise Architect 8, however the Structured Scenario Editor has undergone many enhancements since its inception.

Yes. The scope of this is very open. It is commonly a Realization or Dependency relationship to a Exigence, Feature or another element elsewhere in the model.

Yes. For more information, please refer to the previous webinar on Model-Driven Cas d’Utilisation Analysis with Structured Scenarios.

Yes. You can link to functional and non-functional Exigences on a single line.