Gerald R. Gray, PhD
Electric Power Research InstituteSr. Program Manager – Enterprise Architecture & Integration
CIM UniversityJune 1, 2016
Enterprise Architect Best Practices
When you can do anything…
• Pick an organizing paradigm
– e.g. TOGAF
• In this example, a package for each phase
• Phase A – mind maps, reference models
• Phase B – use case, business activity, business architecture
• Phase C – application architecture, sequence diagrams, CIM data model
• Phase D – Technology architecture
Phase B• Use Cases
– Actors – separate package
• Business Activity diagrams
• ArchiMate Business Architecture
Phase B – Activity
• Swimlanes
– have Actors from the list
– Local names as well
• Other tips
– Control flow for activities in the same lane
– Object flow when crossing lanes
Application / Data Architecture
• CIM!
• But not just CIM – linking CIM to architecture
application Phase C
MR-MS OMS
End Device Event
ActivityRecord
Metering::EndDev iceEv ent
+ issuerID: String
+ issuerTrackingID: String
+ userID: String
Outage Analysis
«trace»
Version control
• Enterprise Architect is Version Control Compliant (VCC)
– Subversion (https://subversion.apache.org/)
– SlikSvn (https://sliksvn.com/download/)
– TortoiseSVN (https://tortoisesvn.net/)
• Make a local repository
– Windows Explorer, create a folder, right-click -
EA VCC Integration
• Select Package
• From the menu:
– Project
– Version Control
– Version Control Settings
Baselines
• Corporate edition
– Allows you to take a “snapshot” of your model
– Package Baselines…
– Give it a version number
• Compare baselines
• Compare baselines to a file
• Import/Export files