#Program word diagrams architecture how to

It’s going to be in draft status starting out. Let’s do a sequence diagram for just creating a new work order. Application Architecture Sequence Diagram

#Program word diagrams architecture how to

So, there is the object diagram, and taking that object diagram into consideration, let’s figure out how to put this application together. And there may be a manager, who is an employee, and a technician has a manager so I will add that. Indicate this inheritance relationship with an open triangle. Then we need someone to assign the work order, an assignee and they could assign it to a technician, and the technician is also an employee. Others may be “completed” and maybe “canceled”.Īlso, I need a submitter, somebody who is going to submit the work order.

It will include statuses like “draft”, or “submitted”, or maybe “assigned” or “in progress”. I need a status object, whether it is an enum or enumerated class. This is going to be a class diagram or just an object diagram.Ī work order does need a status. Let us just put the work order right here in the middle. Now, what about our core object model or domain model? I love domain-driven design – the pattern and the language that it gives us. Alright, so that is our dependency diagram. I like that all incoming references, no outgoing references for core. So, I am going to make sure that the UI, data access, and unit tests references core. You are only as stable as your most stable library. NET standard and your most stable libraries. The core needs to have no other dependencies than. Now I did not put any arrows here, and that needs to be communicated. And, if I put in acceptance tests, over here, most of the time they are linked to data, access, core, and UI. Unit tests are going to be linked to core integration tests, and they are going to be linked to data, access, and core most of the time. These are going to be projects, so I need to have them here. I know that I need some unit tests, so we’re going to have a unit test library, and I’m going to have some integration tests.

I am not going to worry about my handwriting. Net standard 2 and I’m going to have a UI project also, I am going to have a data access project … I am going to have a core library, which is. So, I am just going to quickly spec it out not getting into explaining why.

Net, Blazor Web Assembly, C#, SQL server, and we are going to pull it up in Azure, one of the first things to think about is what it will look like. If I am laying out a visual studio solution, and it is going to be. You know I am a fan of Onion Architecture. Application Architecture Dependency Diagram So let’s just take these and go through them one at a time to see how quickly we can use these particular diagrams to describe a work order application in a fashion where you would actually understand what. And a lot of times, an activity diagram will be interesting or an overall dependency diagram.

So, we need to make use of a state machine diagram. Then you might have some patterns, in the case of a work order, it has a status and it has a workflow. Also, we are going to make ample use of sequence diagrams. The OO diagram is going to be your bread and butter diagram you could think of it as a class diagram. We need some diagrams that are going to communicate it. Let’s pretend that we are starting a work order application.