Layers are autonomous: A group of changes in one layer does not affect the others. There are several advantages to using layered architecture: The database layer contains the tables, indexes, and data managed by each of the modules. This is where developers add customizations and new functionalities. The application core layer is the place where all system code is located. The business rules layer determines the behavior of the modules of the ERP: “If a new employee is entered into the HR and payroll modules, then insert an introductory course in the employee's training menu.” The functionality layer navigates through the different modules, presents screen sequences to the user, and does all data input operations. This is what the user sees and what they use. Searches and insert/delete/update operations are executed here.Īn ERP System (accounts payable, accounts receivable, stock management, HR management, production management, provider management, purchasing, treasury, finance, accounting, etc.) has a user interaction layer for each module: screens, forms, menus, reports. Programmers work in this layer most of the time.ĭatabase layer: This layer contains the tables, indexes, and data managed by the application. It determines how the pull-down menus work, how the buttons work, and how the system navigates through screens.īusiness rules layer: This layer contains rules that determine the behavior of the whole application, such as, “If an invoice is printed, then send an email to the customer, select all items sold, and decrease their stock in the stock management module.”Īpplication core layer: This server contains the main programs, code definitions, and basic functions of the application. It defines how the application looks.įunctionality layer: This is the layer that presents the functions, methods, and procedures of the system based on the business rules layer. It is the most visible layer of the application. User interaction layer: This is the layer that interacts with users through screens, forms, menus, reports, etc. Let’s see what this looks like: Layered architectureĪs you can see in the diagram above, a standard layered architecture has five parts: What Is the Structure of a Layered Architecture? It is an excellent example of a layered architecture. Gmail is divided into at least three layers, every one of them has a mission, and they exist separately to handle different processes at different levels. There is also another layer that interacts with a database where user email messages are stored (millions or maybe billions). There is an external layer that communicates with the users in their language. There is an internal layer that does all the processing. Google developed the Gmail application in different layers: They developed an internal version that does all the message processing, and then developed different external user interfaces that work in many languages. Have you ever wondered how Google makes Gmail work in different languages all over the world? Users can use Gmail every day in English, Spanish, French, Russian, and many more languages.ĭid Google develop different Gmail applications for each country? Of course not. At the end of the chapter, I will show you a real-word example (Amaze project management software), and then you will solve a similar case applying what you’ve learned. In this chapter, we are going to cover the layered architecture, what it is, and in what cases it is the perfect solution for a design problem.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |