<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by David on Medium]]></title>
        <description><![CDATA[Stories by David on Medium]]></description>
        <link>https://medium.com/@david_49863?source=rss-5330212495e8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*dmbNkD5D-u45r44go_cf0g.png</url>
            <title>Stories by David on Medium</title>
            <link>https://medium.com/@david_49863?source=rss-5330212495e8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 05:57:32 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@david_49863/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Architecture series Part 1]]></title>
            <link>https://engineering.shipper.id/architecture-series-79518ae9335a?source=rss-5330212495e8------2</link>
            <guid isPermaLink="false">https://medium.com/p/79518ae9335a</guid>
            <category><![CDATA[diagrams]]></category>
            <category><![CDATA[architecture]]></category>
            <category><![CDATA[design-process]]></category>
            <dc:creator><![CDATA[David]]></dc:creator>
            <pubDate>Thu, 27 May 2021 04:01:13 GMT</pubDate>
            <atom:updated>2021-05-27T13:13:09.659Z</atom:updated>
            <content:encoded><![CDATA[<h3>Type of architecture diagrams</h3><p>Have you ever been in a meeting where you try to understand someone explaining about project architecture? Or business system flow?</p><p>But without a diagram.</p><p>I found it is incredibly hard to visualize problem statements above without proper visualization. Imagine as well if it is a remote work situation when you don’t sit in the same room with your audience. Unless you are subject matter experts in that specific domain, it might be tricky to understand the whole thing without visualization. Humans are visual and that’s how we trained. Diagrams are much needed so get things registered quickly in the brain.</p><p>There are several diagrams that are commonly used to help system abstraction.</p><p>In order to provide better understanding, let’s work with use cases as follows.</p><p>Let’s say you are working in a logistics company which provides warehousing solutions for your customers. There is a business initiative to help automating manual processes in the warehouse to be more efficient by utilizing robotic technology. There are several companies that provide these services, both in the hardware and software in the cloud. However, businesses would still like to keep data visible to internal usage and try to avoid vendors locked in.</p><p>Based on the use case above, we will dissect into several common modeling techniques that might help deliver content to the right audience.</p><blockquote><strong>The conceptual/context diagram</strong></blockquote><p>In this level of diagram, you want to highlight and emphasize high level ideas about the project and strategic objective you would like to achieve. Think about conceptual/context diagrams as a way to sell or get a buy-in from other stakeholders. At this level, we don’t have to worry about technical detail, data flows, or detailed implementation of the solution which will be discussed in the later conversations.</p><p>Modeling diagrams at the conceptual level will describe a clear understanding of overall project objectives and give an idea what kind of dependencies it might have, such as funding, capabilities gap, and interaction/dependencies with other systems/stakeholders.</p><p>Typical audiences of the conceptual review are usually executive management, business stakeholders, and representatives from enterprise architecture (in the larger organization).</p><p>Diagram below illustrates some sample of conceptual diagram</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/682/0*5Xx8fLBKRuJvWyx8" /></figure><p>Diagram above is showing the existing system architecture as well as the new system which the business requested. The abstraction stays at a high level since the goal is to get business buyout.</p><blockquote><strong>The logical/component diagram</strong></blockquote><p>At this point, you should already have the business /executive sponsored approved, and you are ready to depict a system design diagram about your application.</p><p>This is no longer a business abstraction but a logical representation of the system architecture. Your audience will be technical fellows (architects/developers/technical managers) which are interested to learn more about your architecture design. You will need to be able to illustrate how solutions work in terms of function and logical information. Details are encouraged in this level of diagram, but it is recommended to be kept at the component levels. (no need to go to class level diagram detail).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*r9bM_TF2Apr_gT2W" /></figure><p>From the diagram above, it represents logical implementation of the existing systems, in this case WMS, Logistic, and Dashboard applications. The robotic solution is depicted on the left side of the diagram as a new solution with integration with existing networks via VPC peering. Diagram above should be able to give detailed context to the technical team to brainstorm proposed solutions.</p><blockquote><strong>The physical/network diagram</strong></blockquote><p>This will be the lowest level abstraction of the component, along with details of technical components information, such as servers, interfaces, network connections and components, etc. The diagram should be able to depict a real life implementation of specific technology solutions. A lot of times, physical architecture could take the longest time to design because it should be detail oriented. A typical audience for this review will be technical teams.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*n4v6W7nTVIO6j2q8" /></figure><p>Diagram above looks very similar to logical representation, however physical diagrams typically contain more detailed information such as network information, url, port, etc.</p><blockquote><strong>The sequence diagram</strong></blockquote><p>Sometimes the overall overview is not enough and you will need to describe flow interaction between objects/components. This is where a sequence diagram could help. It captures interaction between objects in the context of collaborations. They are typically represented by vertical axis to represent when a message is sent from where and to where.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/661/0*cxrAn9cINnapFSIh" /></figure><p>Diagram above depicts an illustration flow from users to see inventory and get the price of the inventory. The benefit of sequence diagrams is clearly describing flow for specific use cases. This level of detail will be hard to be illustrated in the logical diagram.</p><blockquote><strong>Conclusion</strong></blockquote><p>There is no one size fits all solution. The need of the diagrams (or which diagrams) will vary on the organization size and project complexity. By preparing the right diagrams, it will help the project tremendously, especially in the early stages of the project phase, setting the right context and giving insight to stakeholders as well as the development team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V--nQMwIZQUoIYF2WoyGnA.png" /></figure><p><strong>Table 1. *indicates it is optional/nice to have but not mandatory</strong></p><p>Table above gives some guidelines on when to use which diagrams. Obviously the real implementation will vary and depends on each organization how they would like to implement it.</p><p>It is worth mentioning that architecture diagrams shouldn’t be treated just as supplemental documents or project checklists. Some organizations might spend more time shaping the document and level of detail for the architecture diagram, while others might go with a simpler approach. Whatever you do, I recommend keeping diagrams up-to-date since they represent the abstraction of your applications.</p><blockquote><strong>References</strong></blockquote><ul><li>Online Sequence diagrams tools (<a href="https://sequencediagram.org/">https://sequencediagram.org/</a>)</li><li>UML online tools (<a href="https://www.planttext.com/">https://www.planttext.com/</a>)</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=79518ae9335a" width="1" height="1" alt=""><hr><p><a href="https://engineering.shipper.id/architecture-series-79518ae9335a">Architecture series Part 1</a> was originally published in <a href="https://engineering.shipper.id/">Shipper.id Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>