140 likes | 436 Views
Prepared by: Gerald R. Gray, Guiding Principle Consulting. Systems Integration Design with Enterprise Architect. Agenda. EA Strengths/Weaknesses Pre-requisites Gridwise Architecture Interoperability Framework Creating common systems integration diagrams. EA Uses and Benefits.
E N D
Prepared by: Gerald R. Gray, Guiding Principle Consulting Systems Integration Design with Enterprise Architect
Agenda • EA Strengths/Weaknesses • Pre-requisites • Gridwise Architecture Interoperability Framework • Creating common systems integration diagrams Guiding Principle Consulting - CIM Users Group - San Francisco
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 • Built-in support for version control e.g. Subversion • Fast, built-in or custom document generation & HTML Guiding Principle Consulting - CIM Users Group - San Francisco
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 Guiding Principle Consulting - CIM Users Group - San Francisco
Pre-requisites • Sparx Enterprise Architect • http://www.sparxsystems.com.au/ • Version 8 recently released • $135 - $699 depending on version Guiding Principle Consulting - CIM Users Group - San Francisco
Following the GWAC Stack • Use Case • Business Process • Integration Requirements • Message Payloads Adapted from Gridwise Architecture Council Interoperability Framework Guiding Principle Consulting - CIM Users Group - San Francisco
Common Systems Integration Diagrams • Use Case diagrams • Business Activity Diagrams • Integration Requirements • Sequence Diagrams Guiding Principle Consulting - CIM Users Group - San Francisco
Adding a Use Case • Project Browser • New Package • New Diagram – Use Case • In the workspace add • Actors, cases, associations Guiding Principle Consulting - CIM Users Group - San Francisco
Adding a Business Process • Project Browser • Add New Package • New Diagram – Activity • Open workspace, right-click for Swimlanes and Matrix… • Add swimlanes • Add Activity and flows Guiding Principle Consulting - CIM Users Group - San Francisco
Integrations Requirements • Addition to the Activity diagram • Alignment of business user and the architect/software team • Object flow between two activities, typically spanning actors (swimlanes) • Add requirement (from common tools) • Add Integration to Type • Use object node to identify service Guiding Principle Consulting - CIM Users Group - San Francisco
Adding Sequence Diagram • Project Browser • Add New Package • New Diagram - Sequence diagram • Open workspace • Add Actors • Add flows (asynchronous) • Add returns (“Is Return” checkbox) • Service naming based on IEC 61968-1-2 Guiding Principle Consulting - CIM Users Group - San Francisco
Reference • EA Free Trial • http://www.sparxsystems.com/products/ea/trial.html • Subversion Documentation • http://svnbook.red-bean.com/en/1.5/index.html • EA Tutorials and Online Help • http://www.sparxsystems.com/resources/index.html Guiding Principle Consulting - CIM Users Group - San Francisco
Questions? • Contact: • gerald.gray@guiding-principle.com