A small outline on how to develop a upper-level application architecture.

Suppose that you take decided on future functionality. Then you know on the nose who or what leave supply the data, who / what will consume IT, and what data transformations the system itself must perform.

Take a piece of paper and a pencil. If you are not very confident in your abilities, then also an live band to edit the scheme. More advanced readers bathroom turn to professional tools for architectural design in physics form.

Like a sho detect out who will access your system to transfer Beaver State cod data, and what your program will entree. Those systems or users who access the program themselves, draw schematically on the piece of paper at the summit. Those that the program testament accession (including the database) are below.

Now imbibe a rectangle under each matter drawn on top with the name UI or API - these are the interfaces that the user or the external command system will access. Sometimes the UI toilet also access code the API. Combine all the rectangles with the UI in cardinal outline and name them a introduction layer. Combine wholly the rectangles with the API and name them a layer of services.

For systems closed below, specify the components that will be responsible for accessing these systems. Immix all of these components in one circle and call it a data access layer.

Between the service of process level and the information access layer, draw a great outline and name IT the business logical system layer. In the weeny rectangles inside this outline, list the main business sector tasks. One component of your system will solve united clientele job.

Now on the rightist, draw a few long rectangles from big top to bottom and write in them: logging, contour, performance monitoring, exception handling and something else that is the common infrastructure (or end-to-remainder functionality) for all layers of your program.

You got the logical architecture of the application. Spread layers across servers to beget physical architecture.

Nowadays you need to solve in detail each littler square.

I'll hide a small working example low cat.

As an example, I'll bring forward a totally virtual project for a senior high school operation monitoring system. I'll take it for two reasons. First of all, we all went to school. Secondly, with many of us, children are now in the same school. Because of this, I hope that the bailiwick wish be clear to everyone.

So, our system will be designed for maintaining electronic diaries of students and electronic classrooms. In addition, lease the system cause some additional set of functions that allows students, parents and teachers to exchange messages, and the school management to ascertain the learning process.

So, students, their parents, teachers and school management will be users of our system. In addition, users will be system administrators, who need to receive information well-nig events in the scheme and perform many service operations. We will not heel the use cases, we are not talking or so them.

Users will interact with our organization either through a web-interface or using a mobile application. Both user interfaces are committed for schools that cannot open the development of their own website. The sleep will be able to access our system through web-services.

There will comprise four services: an electronic diary, an electronic journal, educational operation governance and administration.

Nether the services layer on that point will be a layer of business sector logic, consisting of a dozen components that solve user business problems.

Data will be stored in the database. What is more, there will be two bases: military and archive.

The system will export / import data from files. In addition, there will be two external systems to which our system will constitute conterminous remotely: a credit information system and an selective information system of the Department of Education.

End-to-end functionality will be composed of mechanisms for logging, monitoring, configuration direction, and security.

As a result, we get just so much a simple scheme:

Now you can choose the physical nodes. The web drug user interface and services will be deployed in a web cluster. Layers of business logic and information access will be enforced on the application server. Databases will embody hosted in a isolable failover bunch. Later information technology bequeath be executable to show all the nodes in the variety of a beautiful diagram of physical architecture.

I desire the example is clear.

Ready to delve deeper into the topic, I offer to pay attention to the "Microsoft Application Architecture Design Guide . " The manual is printed in the form of a character reference, thusly that you can chop-chop discovery recommendations for the invention of each layer of the system.