S o it often happens to have outdated documentation or documentation with the text up-to-date, but the diagrams out-of-date, which is of course really confusing for newcomers. Moreover when there are schema or diagrams inside the documentation, updating those nice diagrams is yet another challenge because those diagrams are sometimes created using yet another tool. When the software changes or evolves, it may be difficult to sync the documentation, just because sometimes code and documentation are stored in two different tools. In software development, keeping documentation consistent with the actual code is a real challenge. The key problem I was trying to solve is : “keeping the documentation up to date”. Why PlantUML? Why did you decide to create it? What problem were you trying to solve? Anything else you would like to say to our readers?.Who else / what topics would you like to see covered on this site?.Are you open to get (code) contributions from other people interested in helping in the development of PlantUML?.What is the roadmap for PlantUML? Do you plan to go beyond UML?.Why do you think is that? Any extension you would like to see? There’s a growing ecosystem of extensions / adaptations around PlantUML.What do you think makes PlantUML stand out from their competitors? PlantUML is not the only “textual UML tool”.How is PlantUML developed? What is the internal architecture of the tool?.How popular is the tool? Why do you think PlantUML is so successful?.Why is PlantUML free & open source? How do you monetize it?.Why PlantUML? Why did you decide to create it? What problem were you trying to solve?.If the relationship between the diagram elements is one-to-one, then simply leave it blank. It’s optional, but sometimes useful to add the standard UML notation for multiplicity: 1, 1.n, or *. You can also show inheritance on both actions and actors with the standard UML notation of a connector with an open arrowhead. In my example, you can Mark a habit as done, or Mark a habit as done AND add a comment in the same action. When one action is an extension of another action (or a more specific version of that action), use extend to show that relationship.So, the Update the habit history action is dependent on the other actions. But you wouldn’t update the habit history without one of the four actions: Add a habit, Delete a habit, Mark a habit as done or Add a comment. For example when you Add a comment in the habit tracker app, you must Update the habit history. When one action is dependent on another action, use an include relationship.You can show specific relationships between the actions (or classes and methods) with include and extend. Use case diagrams can show information that makes it easier to program
0 kommentar(er)
