![]() ![]() The plugins are developed by the team who build the open source editor that is used in draw.io". Service/Product: (earlier known as draw.io)Ĭompany: "The draw.io plugins are owned by, a Germany consultancy that specializes in Atlassian and Google Cloud. There are some interesting tools (some free and some commercial) which can be used to represent your design ideas and system:ĭiagrams using AWS and other cloud provider icons Here is a quora post with interesting discussion (specially post by Timothy High and Ramakrishnan T). This is why many architects had been using Power Point for representing their architecture work, line and box diagrams using other drawing tools. If we come to this conclusion instead of UML modeling tools, other simple tools are easy to use and more effective. May be they are easy to explain to the senior management (but they should not be lower level design doc then, just functional architecture ? ). Still good diagrams and models are liked by many people and even with icons of projects and companies. This may be the only option in some cases but should not be default way of doing it. Sometimes now too you have to deliver something fast, you already have lots of experience so sometimes you define it upfront and try to implement it quickly (and forget the collective approach mentioned above). Design (and architecture) is craftsmanship. Models are a way to present your design ideas. Take a picture from the board and attach it in the document or project wiki wherever you want to keep it for reference. Design (thinking to take technical decisions) is still required but it should be a collective approach with the team, doing it on board, brainstorming with those who are going to implement it. In this case you may have to update your design decisions. Too much upfront design and once for all is also not practical, but you will have to understand the requirements, analyze them, take design decisions, build an increment and review the design decisions if quick demonstration of the software to the customer brings new requirements or new discoveries about old requirements. ![]() I had been of opinion that design or architecture is for taking technical decisions to achieve business requirements and if these decisions can't help building the system and can't help in achieving functional and non functional requirements, better is call it documentation. ![]() One who maintains the software would refer to that design. Slowly this became a documentation practice of weeks and months, even some teams were developing software and then for compliance creating design (UML diagrams), I guess the good use of that was for maintenance. During old times when term architecture in software or IT was not popular hardly people were using UML diagrams to represent their design. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |