Getting Started with Enterprise Architect and Subversion

Getting Started with Enterprise
Architect and Subversion
Prepared by:
Gerald R. Gray, CIMple Integrations
Kay Stefferud, Enernex
EA Strengths/Weaknesses
Setup & Configuration
Creating common OpenSG diagrams
EA Uses and Benefits
• Supports IT system, software, and business processes
• Models, designs, builds, and tests software
• Uses standard Unified Modeling Language (UML)
• Can be used to create:
– Business Process Models
– Class diagrams and software artifacts
• Central repository for process and IT system information
• Interfaces with version control package e.g. Subversion
• Fast, built-in or custom document generation & HTML
EA Weaknesses
• May be a poor choice for complex system diagrams
– Visio is “prettier”
– PowerPoint also an option
• Complex User Interface
– Extensive feature set may lead to confusion
– Time saving “tricks” difficult to learn
• Diagrams not useful if team doesn’t see value
– UML/BPM may be used currently at their site
– Some users intimidated by tool
• Sparx Enterprise Architect
– Version 8 just released
– $135 - $699 depending on version
• Subversion
– Command-line client (required)
– TortoiseSVN (optional)
• Credentials to UCAIUG Microsoft SharePoint
• Added to the Source Code Access group in the
UCAIUG SharePoint user management (Tony
Adams, Kay Clinard)
• Coordinate with the appropriate team,
• Install
– Enterprise Architect (v7.5 or greater)
– Subversion command-line client
– TortoiseSVN (Windows)
Working Directory Creation
• C:\OpenSG\Test\Working
– In Windows Explorer, right-click on
• Using TortoiseSVN repo browse to:
• Enter credentials if prompted
• Right-click on folder in left-hand
• Select Export… to directory created
EA Configuration
• Start Enterprise Architect
• Open the project
• From main menu select
– Project Version Control Version Control
EA Configuration
Create a unique name
Select Subversion type
Point to working directory
Subversion exe path should prepopulate
– Click Save
EA Configuration
• Right-click on Package
• Select Package Control
• Select Add Branch to
Version Control…
• The key icon is added to
each package
Common OpenSG Diagrams
• Use Case
• Business Process
– Integration Requirements
• Sequence Diagram
Adding a Use Case
• Project Browser
– New Package – Storm Trooper Use Cases
– New Diagram – Use Case
– In the workspace add
• Actors, cases, associations
– Saves changes, check-in package
Adding a Business Process
• Project Browser
– Add New Package – Saloon Business Processes
– New Diagram – Activity
– Open workspace, right-click for Swimlanes and
– Add swimlanes
– Add Activity and flows
Integrations Requirements
• Addition to the Activity diagram
– Typically a hand-off from the business user to the
– Object flow between two activities, typically
spanning actors (swimlanes)
– Add requirement (from common tools)
• Add Integration to Type
• Use object node to identify service
Adding Sequence Diagram
• Project Browser
– Add New Package – Saloon Sequence Diagrams
– New Diagram – Saloon Sequence – Cleanup
• Open workspace
– Add Actors
– Add flows (asynchronous)
– Add returns (“Is Return” checkbox)
• EA Free Trial
• Subversion Documentation
• EA Tutorials and Online Help
• Test Repository