AgileEAS.NET Agile Development platform case-drugstore system-Project Summary 01/29 Update SLTechnology News&Howtos

AgileEAS.NET Agile Development platform case-drugstore system-Project Summary

2025-01-29 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Internet Technology >

Shulou(Shulou.com)06/03 Report--

The beginning

In the previous chapter, we explained how to use the AgileEAS.NET agile development platform to develop the drugstore system, but we did not explain some of the functions of AgileEAS.NET in general, we described them in detail

Some of the related features of the platform, we only include most of the functions of the platform in the development process of the drugstore system, and some functions are not used. Maybe we will continue to talk about these functions later. This article will focus on the previous

The developed drugstore system, let's make a summary and review. Relatively speaking, some of the supporting documents in the previous articles still need to be improved, but generally speaking, they are already very detailed. I originally intended to release the outline design documents, but

It is that I don't have a very good UML modeling tool on this machine, so I ran aground and said sorry to everyone. Next we will summarize the experience and experience in the process of drugstore system development.

Outline

1. Which problems have been solved by AgileEAS.NET in the development of drugstore system.

2. Which technologies of AgileEAS.NET platform are used in the drugstore system.

3. And analyze the application of these technologies in other fields.

Development problems solved by AgileEAS.NET platform

The problems we encountered in the drugstore have also been analyzed in front of specific documents, and the functions provided by the platform are also relatively powerful. The main function diagrams are as follows:

From the figure above, we can also find that our non-functional requirements, such as the drugstore system, need to support distributed access support. Including some deployment and other requirements, and so on.

1. Printing problem:

Our options:

Crystal report: the report solution provided by Microsoft is powerful. I think all reports can be made by using this report. The only disadvantage is that it needs to be installed by the client, otherwise it can not be used.

FastReport: very powerful reports. Support can be dragged, not free, for a fee. There is an open source version, but it doesn't seem to be .NET.

AgileEAS.NET platform reports: provides powerful visual designers, and also supports the design of complex cross reports, and is free, permanent, and open source reports. And provide support for the two schemes.

One is a platform-based report designer, and the other is an independent designer.

2. Distributed access support

Our choice:

Self-development: based on WCF or directly using Remoting,WebService to communicate between server and client.

There are some free and commercial free distributed access middleware on the market:

AgileEAS.NET distributed access middleware: provides a hot switch between normal mode and distributed access mode, which can be simply configured through a configuration file. For more information, please refer to the distributed access configuration in a series of articles.

Set up and deploy. Specific article "AgileEAS.NET platform development example-intelligent upgrade and server deployment".

3. ORM question:

Our choice:

Open source free ORM components:

NHibernate:NHibernate is porting the Hibernate core part of Java to Microsoft .NET Framework. It is an object-relational mapping tool that aims to persist .NET objects to a relational database.

The Spring.NET:Spring.NET framework includes many features, and Spring.NET 1.0 includes a complete IoC container and AOP class library. Version 1.1 adds Web, ORM and data modules.

Castle:Castle, written by Hamilton Verissimo, has been under development since 2003 and released 1.0 RC2 in November 2006. Version 1.0 RC3 was released in September 2007. Castle is a Lightweight container (Container), implements the IoC (Inversion of Control) concept, is a comprehensive application (Application) framework (Framework), and provides a series of related tools

IBatis:iBATIS is a framework that can design and implement a better persistence layer for Java/.NET applications. IBATIS associates objects with stored procedures or SQL statements that use XML descriptors.

ORM provided by AgileEAS.NET platform:

Two modes are supported, one is ActiveRecord mode, and the other is the combination of table schema and ActiveRecord. Generally speaking, they all provide functional support for ORM access. And based on the ORM component, it provides

Powerful database model designer, through the designer to provide solution generation and database related two-way engineering related work.

4. Resource Manager

At present, there are not many open source resource management platforms for lifecycle management of such components in the market. of course, just like the functions provided by OSGI, it can be regarded as such a resource management platform.

Different modules can be identified by such a platform and provide related basic services.

There are many examples of related OSGI platforms, so I won't elaborate on them here.

AgileEAS.NET provides the development idea of platform + plug-in, provides a resource management platform for such plug-ins, manages the allocation and recovery of plug-in resources, and manages the life cycle of plug-ins.

For the description of the specific plug-in contract of the resource management platform and the use of the resource management platform, please refer to the introduction of the relevant articles in the drugstore below.

"AgileEAS.NET platform development example-drugstore system-preparation development environment (middle)"

5. Authority control system:

With regard to permissions, we all have a lot of experience, and if we analyze them in depth, it may be impossible to analyze them completely. everyone has several ideas about the design of permissions.

Soft RBAC standard access model, about the specific introduction, online search, information is also very much, the train of thought is also very clear.

Generally speaking, when we are developing an application system, the problem of access control may also be worried. at this time, we need the control of the permission system, so if we develop some basic permissions by ourselves.

Yes, it also takes a lot of energy and time.

The platform itself provides a simple access control module, analysis of the principle of authority allocation and control, AgileEAS.NET platform authority management = Windows2000 access control ideas, through ACL to control the phase of the module.

Turn off permissions. For specific permission configuration and allocation, please refer to the following article: "AgileEAS.NET platform development example-drugstore system-function release [permission configuration] [part 2]"

6. Smart client:

With regard to the smart client, I think everyone's ideas for architectures such as Cmax S are basically the same. the key is whether it can be easily applied when the component is combined with its own application. Of course, if

If you develop it yourself, you don't need to consider the content of this piece.

The platform also provides support in this respect, providing the choice of two modes, one is WebService and the other is Remoting. Under the .NET platform, the way to use Remoting can be updated quickly.

High efficiency.

7. Other

Rapid plug-in construction and convenient test environment support, through the test environment provided by the platform, it is very convenient to run debugging programs. Higher development efficiency.

AgileEAS.NET platform technology used in drugstore development

In the process of the development of the drugstore system, we also use all aspects of the technology provided by the platform, basically understand the development process of the drugstore system, the use of the platform can be said to have mastered the essence of things, how to quickly

Using the platform to develop functional modules is our goal. It is also an important purpose of developing the drugstore system.

1. ORM technology:

Object-relational mapping, the platform provides the functional support of ORM, which is used in the drugstore system. Through the code generator, it provides the automatic generation of the underlying code of ORM, which can achieve code consistency and better performance.

Readability and maintainability, etc.

2. Distributed and smart clients:

Through the distributed access component + smart client support provided by the platform, it provides distributed data communication, smart client + server deployment functions and other functions, which can be completed only through the use of related tools.

3. Basic functions:

Rights management module: provides the management function of rights.

Resource management platform: provides plug-in management functions.

4. Report service:

Report: provide designer + report printing service.

5. The development idea of plug-in + platform:

The development idea of plug-in + platform.

6. software engineering:

Software + factory = software engineering

This platform provides the agile parallel development method of plug-in + platform.

Application of AgileEAS.NET technology in other fields

The above describes some of the functions provided by the AgileEAS.NET platform, which are the main functions, but not all. There are many functions that we have to continue to explore before we can find them. Let's take a look at the other features of the AgileEAS.NET platform.

The application of application scenarios.

1. Use ORM alone to quickly complete the persistence of data.

The ORM component is responsible for general persistence services and provides a hyperemia model to support related data access.

2. Use the report service alone:

You can use it without ORM:

Through a separate access component, to provide access to the report definition file, and then use the printing service, for specific separation from use, please refer to the following article

"AgileEAS.NET platform development example-drugstore system-report development (advanced article)"

3. Distributed deployment and smart client

Because the tool is developed on the AgileEAS.NET platform, there will be some limitations when it comes to use, but generally speaking, there are not many restrictions. As long as it is well configured.

4. Plug-in + platform

We have also analyzed the content of software engineering above, and we know that the main value of the platform is to improve the software development process, provide development speed, reduce development costs, and can be realized.

Agile parallel development method, through each developer is responsible for the development of a functional module, and finally assembled into the platform to complete integration and deployment. And these modules will not affect the development because of the separation of functions, of course, the use of agile development

The refinement of household stories is also based on this idea of distribution.

5. Basic services

Rights management: it must be a plug-in in accordance with the platform contract in order to be assigned and managed by permissions, otherwise it cannot be identified by the platform.

Therefore, the rights management function must comply with the plug-in contract, and cannot exist separately from the contract.

Other underlying basic services also need the support of related basic components, and the platform provides the support of related components such as AOP,IOC.

6. More services

Continuous update and strong team support.

Powerful workflow + form designer.