![]() Mermaid is a simple and easy-to-use library that allows developers to generate diagrams and flowcharts from text or code. The key is to choose the diagrams that best communicate the design and help the team understand the system being built.įor all of the diagrams, I will ask ChatGPT to use Mermaid.js syntax to generate. It’s important to note that not all of these diagrams will be necessary or useful in every project. However, there are some common diagrams that are often used in software development, including: The number and types of diagrams will depend on the specific project, the team, and the organization. Let’s see how ChatGPT can speed me up in doing so.Īs a senior developer or technical lead, there is no set number of diagrams that are required. It will give you way more control to make your diagrams look exactly like you want but obviously it will take much more time to create one compared to mermaid.js diagrams.Hello folks! I’m looking for a way to make use of ChatGPT for solving business use cases and helping me draw diagrams as well. I’ve talked about excalidraw in my previous posts. You can also alternatively create similar diagrams in free-form mode with excalidraw which I also like. I’ve covered how to edit and manage mermaid diagrams in your favorite tools in a past article. Renders to a nice sequence diagram: Mermaid Tooling Mermaid draws a sequence diagram using a text formatted like this: sequenceDiagram One of the diagram types mermaid support is sequence diagrams. Mermaid is an open source software that draws different types of diagrams using simple structured text. Using Mermaid.js for quick Diagramming Tool It makes sense to make the user journey mapping practice before finalizing user stories when planning a product. As you see here, this process does not replace but complements user stories. Let’s roll back to our user journey mapping with sequence diagrams. If user story is describing a bigger goal, it can be planned as an epic and sub stories and tasks can be planned under it. Often a user story is planned as a story and engineering team can break it down to sub-tasks about the implementation steps. They are essential when the engineering team is planning their implementation in project management tools. User stories written in this traditional sense brings clear, structured, short and written form to your product features. A traditional story would look like: As a, I want to, so that I can get Written user stories are best to summarize a capability, a feature or a user goal. User stories are key when developing a product. Waiter -> Guests: Brings food to the table.Īs you see, if we were to design a food ordering feature, we may want to visualize traditional way of ordering food and also visualize our better food ordering experience with our new product feature. Waiter -> Geusts: Comes to the table and asks for order. Host -> Guests: Shows and sits the Guests to a table. Guests -> Host: Can I have a table for 2? ![]() Waiter brings food to the table to the GuestsĪ journey like this can be visualized in a sequence diagram like this: sequenceDiagram.Kitchen tells Waiter that order is ready.Waiter comes to the table and asks for order from Guests.Host shows and sits the Guests to a table.Guest asks Host can I have a table for 2?.The order of things between which participants happen.Īnd example to this would be, order a food at a restaurant.Sequence diagram is a type of diagram that does great job telling 2 things: So a simple looking feature may require couple different team members to collaborate and communicate. Your feature may require a tech lead to configure things first in your product, then tell their editors to do other things while editors may need to work with their development team to accomplish other goals. User journeys can easily highlight differences between these users and how they interact with your product or each other. Similarly, your small biz client’s users may need different things than your enterprise client. A user who is new to your overall product may take your new feature in a different way than a power user. It’s also important to think maturity of your users adoption of your product. There are many other user personas you may need to consider when designing a feature. Anybody who interacts with your product is your user, including you as “admin” or “owner”. “Users” is a very general and broad definition and often used without much nuance of different user personas. Nothing matters other than how your users perceive your product. In your product, single most important thing is to put your users first. I want to talk about an effective product planning process I’ve been following recently.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |