!procedure $ stakeholder($ label,$ name ="") $ element( "Motivation", "meaning", "passive", $ label, $ name) $ element( "Motivation", "value", "passive", $ label, $ name) $ element( "Motivation", "constraint", "motive", $ label, $ name) !procedure $ constraint($ label,$ name ="") $ element( "Motivation", "requirement", "motive", $ label, $ name) !procedure $ requirement($ label,$ name ="") $ element( "Motivation", "principle", "motive", $ label, $ name) !procedure $ principle($ label,$ name ="") $ element( "Motivation", "motivation-outcome", "motive", $ label, $ name) $ element( "Motivation", "goal", "motive", $ label, $ name) $ element( "Motivation", "assessment", "motive", $ label, $ name) !procedure $ assessment($ label,$ name ="") $ element( "Motivation", "driver", "motive", $ label, $ name) !procedure $ element($ layer,$ type,$ structure,$ label,$ name ="") ' v5 Added Motivation, migrated to Styles, added Structure type ' PlantUML ArchiMate Sequence Diagram template v5 As PlantUML supports both of these diagrams, I have written a support library which can be included in any PlantUML diagram to define each of the ArchiMate concepts and include them within a sequence diagram. It supports many types of diagram, including Sequence Diagrams and basic ArchiMate. PlantUML is a tool which allows you to quickly create UML diagrams based on a (fairly) simple text syntax. There are many tools which can be used to create sequence diagrams, but, as I am a nerd, and enjoy over-complicating things, PlantUML floats my boat in many ways, mainly because it still feels like a fun techie tool (and works well with Markdown too!). I’ve always had a love of sequence diagrams, for those that don’t know what a sequence diagram is, this may not be the blog for you! Sequence diagrams have always struck me as one of the more useful, and practical design documents to use to describe how a system works.ĪrchiMate, of course, works on a slightly larger level, but I think great things can happen when you combine the two, and have used many diagrams to help describe some of the more intricate detail within an architecture.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |