And data flow means that a component passes data to another component. I also like to separate the connections between components into two different kinds: A dependency means that a component has a reference to another component. I have not tried to force it to form any specific acronym, so it’s really just my architecture, with components created where they make sense. The way that things are split into components makes sense, and I always know how to split up a feature and where each piece of needed functionality goes. Over the years, I have come up with an architecture that works for me. Architecture with No Pronounceable Acronym Display formatting of information, accessing the backend over the network, navigating through the application, you name it, the * handles it. ![]() There exist a number of MV architectures, MVC, MVP, MVVM, … What these have in common is that the M (model) and V (view) have very clear and limited responsibilities and then everything else apparently goes into the part. Now we will look at which entities to create and when. The first part of this series described an application as a group of interconnected entities. ![]() And I want to have a clear view of where each piece of functionality should go, to make sure the components stay comprehensible. To me, application architecture has one primary question to answer: Where does this functionality belong? An application I’m working on is going to have features, each feature consisting of several pieces of interacting functionality.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |