Astah Academy is where you can learn the basics of modeling, practices in general, and also how to create diagrams using Astah.
CTO – Kenji explains a well-known analysis pattern called “Header-Detail” using a “Purchase Order”.
Nabi Zamani(at Nabisoft.com), a friend of astah, talks about how he has used modeling with Astah in his globally distributed Agile team.
Janet Gregory, co-author of “Agile Testing” talks about “Learning Journeys for the Whole Team”. She talks about how the Agile testing is different from the traditional testing and also tells us the importance of building the trust between testers and developers.
Rick Steiner, co-author of “A Practical Guide to SysML” talks about why SysML and approach to take.
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.
Michael Chonoles, the author of many UML books, talks about most common misconceptions on UML modeling.
Geoffrey Biggs talks about improving the traceability and management of safety information using SafeML.
Explaining the concepts and model elements of SysML
Geoffrey shows the drawing of SafeML models using a sample of an automated wheelchair.
CTO – Kenji talks about Agile in Korea and the translated book “Agile and Scrum” by Kenji.
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.
Basics of Astah SysML Requirement Table.
CTO – Kenji Hiranabe explaining the basic of UML Class diagram with a sample diagram.
Michael Chonoles, the author of many UML books, talks about the history and essential aspects of Modeling.
CTO – Kenji Hiranabe explaining the basics of UML Sequence diagram.
Astah Support – Satomi explaining the basics of UML UseCase diagram.
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.
CTO of Astah.net, Kenji Hiranabe and Satomi shows how to create “Impact Mapping” using Astah. Impact mapping is a strategic planning technique that prevents organisations from getting lost while building products and delivering projects, by clearly communicating assumptions, helping teams align their activities with overall business objectives and make better roadmap decisions. by Gojko Adzic (http://impactmapping.org/)
Tim Kelly, a developer of GSN (Goal Structuring Notation) talks about the origin of GSN, benefits, which industries that are adopting GSN and the future of GSN – interviewed by Michael Jesse Chonoles.
Fundamental lecture of GSN by Prof. Shuichiro Yamamoto at Nagoya University.
Sandy Friedenthal, father of SysML, talks about MBSE(Model-based System Engineering) and SysML.
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.