Astah Academy is where you can learn the basics of modeling, practices in general, and also how to create diagrams using Astah.
Now that Agile methods have become mainstream in software development, working code and automated tests are being considered as the most important team artifacts. Is modeling obsolete? Is UML dead? I don’t think so. In this article, I’ll explore the spaces where modeling fits and plays an important role in this Agile age, especially when development scales to multiple teams and a shared understanding of the system’s “Big Picture” becomes essential.
As organizations adopt DevOps, they not only release smaller changes sooner, but they also change the way they develop software. Additionally, applications are no longer seen as giant monoliths, but rather as dispersed across dozens of services that may be built on different platforms (from Node.JS to .NET), depending on the team and technology-du-jour. To complicate matters even more, as technology is changing, so are business requirements. This is where an Application Model comes in.
There are lots of situations where you can utilize Mind Map, it can be used for almost any scenes. This tutorial shows you especially how you can utilize Mind Map effectively in software development activities.
Documenting user requirements can be challenging. Agile methodologies advocate building use cases and user stories, but there are no standard processes or notations available to help gather requirements for these. Without strong interpersonal communication and facilitation skills, the process can fail, leading towards ineffective requirements and inadequate software. This guide offers a path to overcome these obstacles. Through the simplicity and serenity of mind mapping, we will explore the “User Wish” – a vague shape of requirements before they are formalized. Taking this concept one step further, we will then clarify the requirements into UML.