- REST API SEQUENCE DIAGRAM FULL
- REST API SEQUENCE DIAGRAM ANDROID
- REST API SEQUENCE DIAGRAM SOFTWARE
- REST API SEQUENCE DIAGRAM CODE
The word "component" is a hugely overloaded term in the software development industry, but in this context a component is a grouping of related functionality encapsulated behind a well-defined interface.
REST API SEQUENCE DIAGRAM CODE
REST API SEQUENCE DIAGRAM FULL
File system: A full local file system or a portion of a larger networked file system (e.g.Amazon S3, Microsoft Azure Blob Storage, etc) or content delivery network (e.g. Blob or content store: A blob store (e.g.Database: A schema or database in a relational database management system, document store, graph database, etc such as MySQL, Microsoft SQL Server, Oracle Database, MongoDB, Riak, Cassandra, Neo4j, etc.Serverless function: A single serverless function (e.g."public static void main") application, a batch process, etc. Server-side console application: A standalone (e.g.
REST API SEQUENCE DIAGRAM ANDROID
Mobile app: An Apple iOS app, an Android app, a Microsoft Windows Phone app, etc.Client-side desktop application: A Windows desktop application written using WPF, an OS X desktop application written using Objective-C, a cross-platform desktop application written using JavaFX, etc.Client-side web application: A JavaScript application running in a web browser using Angular, Backbone.JS, jQuery, etc.Server-side web application: A Java EE web application running on Apache Tomcat, an ASP.NET MVC application running on Microsoft IIS, a Ruby on Rails application running on WEBrick, a Node.js application, etc.In real terms, a container is something like: A container is something that needs toīe running in order for the overall software system to work. Not Docker! In the C4 model, a container represents an application or a data store. In many cases, a software system is "owned by" a single software development team. This includes the software system you are modelling, and the other software systems upon which your software system depends (or vice versa). actors, roles, personas, etc).Ī software system is the highest level of abstraction and describes something that delivers value to its users, whether they are human or not. Which in turn are implemented by one or more code elements (classes, interfaces, objects, functions, etc).Īnd people may use the software systems that we build.Ī person represents one of the human users of your software system (e.g. "System V.3" ĥth Edition 5th Edition 6th Edition 6th Edition 5th Edition->6th Edition PWB 1.0 PWB 1.0 5th Edition->PWB 1.0 LSX LSX 6th Edition->LSX 1 BSD 1 BSD 6th Edition->1 BSD Mini Unix Mini Unix 6th Edition->Mini Unix Wollongong Wollongong 6th Edition->Wollongong Interdata Interdata 6th Edition->Interdata PWB 1.2 PWB 1.2 PWB 1.0->PWB 1.2 USG 1.0 USG 1.0 PWB 1.0->USG 1.0 2 BSD 2 BSD 1 BSD->2 BSD Unix/TS 3.0 Unix/TS 3.0 Interdata->Unix/TS 3.0 PWB 2.0 PWB 2.0 Interdata->PWB 2.0 7th Edition 7th Edition Interdata->7th Edition TS 4.0 TS 4.0 Unix/TS 3.0->TS 4.0 PWB 2.0->Unix/TS 3.0 8th Edition 8th Edition 7th Edition->8th Edition 32V 32V 7th Edition->32V V7M V7M 7th Edition->V7M Ultrix-11 Ultrix-11 7th Edition->Ultrix-11 Xenix Xenix 7th Edition->Xenix UniPlus+ UniPlus+ 7th Edition->UniPlus+ 9th Edition 9th Edition 8th Edition->9th Edition 3 BSD 3 BSD 32V->3 BSD V7M->Ultrix-11 2.8 BSD 2.8 BSD 2 BSD->2.8 BSD 2.8 BSD->Ultrix-11 2.9 BSD 2.9 BSD 2.8 BSD->2.9 BSD 4 BSD 4 BSD 3 BSD->4 BSD 4.1 BSD 4.1 BSD 4 BSD->4.1 BSD 4.1 BSD->8th Edition 4.In order to create these maps of your code, we first need a common set of abstractions to create a ubiquitous language that we can use to describe the static structure of a software system.Ī software system is made up of one or more containers (applications and data stores),Įach of which contains one or more components, Label = "\n\n\n\nObject Oriented Graphs\nStephen North, 3/19/93",
0 kommentar(er)
