Posts tagged software diagrams
Well, this has been quite an exciting month for us! We had our Creately for Confluence go live last week, and today, we’re happy to announce the beta release of Creately for JIRA, a diagramming plugin for everyone’s favourite issue tracking and project management software, Atlassian JIRA.
Creately for JIRA helps your development team to improve the quality of detailing on their JIRA issues by easily creating and including Creately diagrams. Issues keep bouncing to and fro, and you cannot just replace a diagram with text when explaining a requirement. Now with Creately’s full integration into the JIRA interface, you can easily add flowcharts, use cases, mockups, mindmaps, UML or any other diagrams to your JIRA issues.
- Easy-to-use interface
- User loved functionality
- Contextual toolbar with the 1-click create and connect features
- A vast library of smart objects
- Access to images from Google and Iconfinder.com
- In-line commenting
With Creately for JIRA, when you invite your team to edit the JIRA issue, they can edit the attached diagrams too. Working with Creately for JIRA is just absolute wonder, read our usage guide to see how to use Creately for JIRA.
Creately for JIRA plugin is now available for free downloads. This is only the beta release, so let us know if you have any suggestions on how we can improve.
As promised in the last post, we will be detailing the (b) Behavioral, (c) Grouping and (d) Annotational part of Things in this post.
Behavioral things encapsulates the dynamic parts of all UML models. These behavioral things are shown below:
This is known as a behavior, which consists of messages that are exchanged among certain elements to finish a task that is specific.
This is something that is useful when the state of an object in its life cycle is significant. This is concerned with the sequence of states an object goes through in reply to events, which are external factors that are responsible for state change.
This is considered as a device where elements of a UML model can be grouped together. Consequently, there is only one thing under this section that is available.
A package is available for gathering behavioral and structural things.
This is defined as a way to capture remarks, descriptions, and comments of UML model elements. Like Grouping, there is only one thing available under this section.
A comment is used to deliver things like notes and constraints of an element.
So here we have covered all aspects relating to (1) Things, which were started on the first post. The last post in this series, which we will publish later this week, will cover (2) Relationships and (3) Diagrams. All in all, we hope these posts have been useful to you when it comes to UML diagramming.
The real purpose behind these recent posts on UML have been to offer anyone, irrespective of their experience in UML, with an effective ”crash course” in understanding this area. We think this aim has been achieved. After this series is over, we hope to bring more interesting insights into UML during the coming weeks and months. Till then, Happy Diagramming!