The Uml digram

 

The blog post, UML Diagrams – Everything You Need to Know to Improve Team Collaboration, provides a clear explanation of Unified Modeling Language(UML) Diagram, its usage and types ending with how it helps to visualize the project. Starting off, the blog covers the usage of UML diagrams, continuing with its key uses, forward design, modeling before coding to plan a system, and backward design, modeling after coding to document a finished system. Also, it covers the thirteen UML diagram types and what each type shows and describes what each type represents and how it contributes to visualizing processes effectively.

I chose this article as it summarizes clearly what the UML diagram, its usage, how the UML diagram can be used to collaborate with other teammates. First was that since the class, I felt that I needed to understand UML diagrams better as I still did not get what use does it has. The fact that it emphasizes UML diagram as white board for building and analyzing the system the team gave me some reason for understanding more about UML diagram. Not only that, but the article also clearly goes in-depth about the UML diagram that goes way in depth compared to the course of behavioral and structural diagrams and how they can fit together in real-world workflows. Overall, this blog clarified how UML diagrams support collaboration as a visual tools to help team members to see and discuss system structures and behaviors. It made me view UML not just as an academic requirement but as a practical communication tool that can strengthen teamwork in future software projects.

           After looking at the article and learning more about UML diagram, I felt like even though it might not be perfect, that I might have to use it for future use. When coding I have something on my mind to create, but when trying to explain it or comment on the structure of the code. Sometimes others don’t understand or sometimes I cannot remember why I did that later. Not only that, but the rough draft of the structure can also be used when talking with other teammates because I cannot do everything by myself and we need to see the same picture, and I think UML diagram will be the virtual whiteboard for it.  

 

https://www.bluescape.com/resource-library/uml-diagrams-everything-you-need-to-know-to-improve-team-collaboration

Comments

Post a Comment

Popular posts from this blog

Is Agile going to fail?

  This article by Jeff Gothelf asks the question “Is Agile finally over?” after 20+ years of implementation to tech field. He argues that even though Agile’s widespread adaptation hasn’t got the result that Agile was intended for. Many companies claimed to be “Agile” as they copy each other, but the implementation of it was shallow or almost non-existent to make changes according to it. Therefore, he says that agile does not seems working as companies try to make employee follow set of rules instead of working in following the basic principles of Agile. He concluded that organizations need to focus on true organizational agility rather than rigid framework adoption. This article caught my attention while searching through the internet as it criticizes Agile’s current status in the business world as ideal of agile does not really fit in reality in organization experience. The vague promises and core ideas are often overlooked to the ‘wants’ of either customer or the organization...
Read more

Waterfall 2.0

  When looking around the internet, I found that there was waterfall 2.0 version of the waterfall software development methodology that we learned at start of class. After I saw the article, I found out that even the most established practices can transform to meet the demands of new era. Therefore, I chose this article as it provides basic summarization of waterfall 2.0 and the difference between traditional waterfall model. As we talked about why waterfall method was being replaced by agile and scrum, I thought there will be some people who will try to improve and use the old working method so using this article showed me how waterfall transformed to adopt need of current workflow. Therefore, I decided to look into it as a background for finding out about the improved version as it revives the dying method into a new form.              This article uses baking as an example to illustrate the principles of waterfall 2...
Read more

Clean code and reality.

  The article examines the question, “is clean code by Robert Martin still matters?” From author’s 16-year coding experience, he writes about reality in writing clean code and its criticism. He acknowledges that t in the end meeting the deadline with functional and bug free code is more important then elegant code following the principle of clean code. However, he argues in the end as a developer, trying to integrate small aspects of clean code into your code base is going to make your skill improve as an engineer in the long run even if many people will not care about it. I selected this article as it addresses some uncertainty that I had with clean code. All the code I have written feels like I got pressure to deliver functional code as quickly as possible and now I’m supposed to write elegant, maintainable code so I wanted to see the real live example from experience if clean code was that necessary. The author’s real-world experience and practical approach toward the subjec...
Read more