Documenting Software Using A Container Diagram

http://bit.do/dgeXm EdrawSoft secret sale page.
If you're every going to talk with someone about a computer system, then there are two diagrams I would use to document any software. The first would be a context diagram and the second which I cover here a container diagram. For the other techniques and diagrams, see my playlist Documenting software in 60 seconds https://www.youtube.com/playlist?list=PL67_9ze31skoZwr7Gs1KRBMxdOseRit41 Content: 00:00 To show the software architecture and system responsibilities 00:05 It's worth drawing a container diagrams 00:08 Zoom in of a context diagram 00:12 We are showing the high-level technology choices and how parts of the system communicate 00:17 Only include the most important infrastructure 00:22 The arrows shows are showing dependencies 00:27 We can see the customer and administration team actually use different systems 00:32 Which would be normal for an onlineshop 00:34 Because managing orders and inventory requires a lot of system resources 00:40 Each system interaction is described 00:43 We have given the version number for the software used 00:45 The containers have a purpose 00:49 We've given port numbers and protocols where needed 00:54 Essential for developers and sysadmins Excellent reading material to help you visualise, document and explore your software architecture (C4 Diagraming) https://leanpub.com/software-architecture-for-developers Software Development Done Right Blogs https://www.clouded.ch/blog/ SUBSCRIBE ON YOUTUBE: https://goo.gl/CyKqGI