Example of agileeas. NET platform development-pharmacy system-System Architecture Design

 

Introduction

 

This article describes how to use agileeas. net agile development platform for the development of the pharmacy system, first we need to design the system architecture of the pharmacy system according to the requirements document, in order to continue the subsequent development work, the whole

After the architecture is properly managed, the detailed design and database modeling are completed step by step. After such a complete step, the specific coding work can be carried out, first, let's take a look at the functional requirements and non-

Functional requirements determine the system architecture design, and break down the relevant functions provided by the agileeas. NET platform for analysis.

 

Analysis

I. layered structure of agileeas. NET platform

1. Logic Architecture Design Analysis Based on agileeas. NET platform

We can see that agileeas. there is no essential difference between the architecture design on the net development platform and the hierarchy and design in the architecture design we usually talk about. It is only on the underlying data access layer (DAL ).

There are some minor differences in the design. Next we will plot and analyze the differences.

The model used by the agileeas. NET platform is a congestion model, which means that the model itself contains not only data-related information, but also some operations.

You can check the Dal layer on the agileeas. NET platform and I will not post the relevantCode.

2. Design and Analysis of the physical architecture of agileeas. NET platform

Agileeas is given above. of course, there is a simple form of distributed access in the physical architecture of the. NET platform, that is, directly accessing the database without using the distributed access service, but directly using the UI Layer through the Dal layer or service

Layer to directly connect to the database to access data, rather than the distributed form. The specific access diagram is as follows:

Through the above analysis, we should. with some understanding of the design architecture support of the. NET platform, we should consider how to use agileeas when designing the architecture.. NET platform provides

Support for non-functional requirements. Next we will look at how to combine the pharmacy system to analyze the architecture.

Pharmacy system-Architecture Design

 

 

First of all, we can say that the current layered structure is very popular and easy to understand and use, of course, any current architecture can achieve a certain degree of separation of duties and low coupling and high cohesion through layering.

But we will not layer it for the sake of hierarchy, it will only make our work more and more complex. We have to pay attention to a balance when we're done.

Next we will analyze the possible hierarchical structure of the pharmacy system based on the pharmacy.

Of course, only the main functional modules are provided, and some statistical analysis and basic data maintenance modules are not included. As long as we meet these main functional requirements, next, let's take a look at some non-functional requirements.

When designing the architecture, we must consider non-functional requirements clearly. Otherwise, the structure can only fail.

Non-functional requirements are as follows:

1. Remote Access must be supported for multiple users.

2. High Performance, fast efficiency, and ease of use.

3. scalability and maintenance.

Based on the above non-functional requirements, the agile development platform agileeas. NET provides us with the following high-strength support:

1. Remote Access is supported for multiple users.

Of course, the service layer can also be used in common forms. This does not affect the use of specific functions. Here, the platform provides support for distributed services by default. Seamless switching is possible. Detailed hierarchical design and

The original structure does not conflict, but the Dal layer is already a congestion model by default.

2. High Performance and ease of use.

3. scalability and maintainability

Because the platform adopts the organization of Platform + plug-in, the following requirements can be met:

1. scalability.

2. parallel development.

3. The platform provides plug-in configuration and management. Including resource allocation and recovery, and lifecycle management.

Next, we will analyze the non-functional requirements mentioned above. The development work we must complete was originally designed to support distributed access. Now we don't need to implement this content, agileeas.. NET platform is already for me

We achieved this by simply meeting the corresponding service definition requirements when using the distributed access service. Our specific usage requirements and definition requirements will be described in the subsequent service layer development process.

Architecture Design of the pharmacy system:

1. Based on the previous non-functional requirements, we have designed the following Architecture:

2. If access is too frequent or there is a large amount of data interaction, we can also extract DTO.

3. Use the architecture with the MVC framework:

Of course, how to design specific application scenarios depends on the needs of our application scenarios. Our series will be developed based on the first architecture as the final version, the main reason for choosing this architecture is simple.

And can meet the requirements.

 

Summary

 

This article mainly analyzes agileeas. net Architecture and analysis of the overall architecture design of the pharmacy system, we did not pay attention to some details, the future of more detailed content, will be in the development process

. Of course, due to my limited level, some shortcomings or design analysis errors, please specify.

 

Pharmacy system source code

More communication

Official blog: http://www.smarteas.net/

Http://www.agilelab.cn/

If you have any questions about using the agileeas. NET development platform, use the following contact methods or communication methods.

1. Telephone-Email:

He gozhou: hegezhou_hot@163.com mobile phone: 18691480181 blog: http://www.cnblogs.com/hegezhou_hot/

2. QQ chat group:

308961614 Network Name: h.o. t