Enterprise-class business system development in combat

Enterprise-class business system development through a series of real enterprise ERP system development process. This includes requirements analysis, design modeling, development, and testing of the entire life cycle process, which will detail the methodology and technical practice. The approaches involved include Agile software development, four-color prototyping, domain-driven design, business architecture, technical architecture, and the use of specific EF, WF, Easyui and other technologies in the project. Domain-driven design examples of domain-level framework building summary: Based on the front-facing domain-driven design concepts and some best practice understanding, the domain model is the most central part of the system, we still use the example of the previous sales order, the core construction of this case system starts from the domain layer. The domain layer framework is built to accomplish two tasks: 1. The establishment of domain models, the determination of aggregation and aggregation roots, and the determination of relationships. 2. Establish a domain-level interface that supports DDD theory. Here is the code map, then the details of each part ... Read the full text posted @ 2015-11-26 11:10  Zhao Read (446) |  Comments (0)   edit   domain driven Design architecture patterns interactive process and best practices summary: The previous article focused on the DDD architecture and the main role of each layer, which describes how to interact with each layer and how best to implement the interaction. 1. Application Layer Application Layer service is called by the interface layer to start. 2. For situations where new domain objects are required, the application layer invokes the constructor of a domain object (aggregate root) in the realm layer or the factory creates a domain object, and then calls some method of the domain object to carry out the related business ... Read the full text posted @ 2015-11-25 15:07  Zhao Read (0)   edit   Domain Driven design summary of architectural patterns: Our traditional architecture pattern is a three-tier architecture: I think the traditional three-tier architecture has the following problems: 1. The business layer accesses the data access layer directly, that is, the business layer directly deals with the data, and binds the data implementation mechanism too tightly. 2. The status of the data access layer is too prominent and does not reflect the other basic service mechanisms required by the system. 3. The business layer does not have good guidance on how to build it. DDD Classic Layered Architecture: I. User interface ... Read the full text posted @ 2015-11-25 15:06  Zhao Read (0)   edit   domain driven Design Warehousing Summary: Before we know warehousing, we first look at the life cycle of domain objects. 1. First, the object is active by invoking the constructor or factory of the domain object, and the object can handle the related business logic. 2. If the object needs to be persisted, theYou need to store objects in persistent storage, such as a database, through persistent operations. 3. When you need to use an object, you can rebuild the object by accessing the persisted storage ... Read the full text posted @ 2015-11-25 15:03  Zhao Read (0)   Edit   field-driven Design Factory summary: The domain model contains domain objects, that is, entities, value objects, Domain Services. Domain objects contain the necessary business logic in addition to state information. To be able to use these domain objects, you need to instantiate these domain objects. There are two ways to instantiate a domain object: 1. Instantiate it by invoking the constructor of the realm object, such as Order order=new Order (), 2. By calling the realm ... Read the full text posted @ 2015-11-25 15:00  Zhao Read (0)   edit   domain driven design aggregation and aggregation root Instance II Summary: This example mainly describes a forum post and reply to the scene. Generally everyone's understanding is that the reply must be dependent on the post, and the reply is not a separate existence of the necessary, and the post and reply usually have some invariant constraint rules, such as the release of a reply, in the post to increase the number of replies at the same time, the post is no longer allowed to delete, etc. So the general understanding is that the post and reply belong to an aggregation, the post is the aggregation root, the reply is the aggregation of a real ... Read the full text posted @ 2015-11-25 14:58  Zhao Read |  comments (0)   edit   domain driven design aggregation and aggregation root instance summary: An example is given to illustrate how to divide the aggregation and aggregation root scenario: a business that orders, an order must have the corresponding customer information, orders under the order item, each order item must have the corresponding product information, the product has classified information. 1. Based on this basic requirement, we initially identified the entity, Value object and association relationship as (here the model first of EF): 2. After-depth analysis of the business, and aggregation and aggregation root ... Read the full text posted @ 2015-11-25 01:14  Zhao Read (0)   edit   domain driven design aggregation and aggregation root summary: After associating design with entity and value objects, The aggregation should be divided and the aggregation root determined. First we need to make clear why we need to divide the aggregation? It turns out that the smallest units of our system are usually modules, such as Customer information management module and employee Information Management module. But dieBlock Division for the design, or appear too coarse granularity. I. Aggregation and aggregation root 1. Defines clear relationships and boundaries between objects and implements ... Read the full text posted @ 2015-11-25 00:19  Zhao Read (+) |  Comments (0)   edit   Domain Driven design summary: After the entity and value objects are found, We need to design the association between objects. 1. Associate as few as possible and not create a complex network. Complex networks are not conducive to dividing boundaries, understanding and maintaining objects, and negatively impacting performance, usually by identifying relationships that need to exist throughout the business life cycle. For example, an order item needs to be linked to a product, but careful analysis, an order item does not need to be stored for the entire business life cycle ... Read the full text posted @ 2015-11-24 23:33  Zhao Read |  comments (1)   edit   domain driven design entity, value object, domain Service summary: The first step in building a domain model is to identify entities, value objects, and Domain Services. I. Entity 1. Entities are domain concepts that need to be uniquely identified in the domain. Typically in business, you need to uniquely identify and differentiate an object and need to keep track of it, such objects that we think are entities. The unique identity here usually refers to the unique identification of the business, such as the order number, employee number and other information, rather than the database because the technology needs to store the self-increment ... Read the full text posted @ 2015-11-24 23:23  Zhao Read (1)   edit   Basic concept of domain-driven design Abstract: Enterprise-class business system development We skip the need for collection, analysis, directly into the design. Domain driven Design (DDD) is a popular, more mature and successful software design method and theory in recent 10 years. Our early common software development approach is to get the product requirements, directly consider how the database table should be designed, this way has been the design and business requirements are disjointed, but more directly consider how it should be implemented, which is a bit of putting the cart before the horse. and D ... Read the full text posted @ 2015-11-24 22:47  Zhao Read (433) |  Comments (5)   Edit   Enterprise Business System Development-Preface Summary: The previous years have been doing Microsoft's solution implementation and software development work. In the study, project implementation, development and management of the process learned a lot of other people good things, but also summed up a lot of experience, I hope to be able to share with you through a series of software development content. This development series is the origin of this, twoYears ago as a software company's technical director, completed an enterprise ERP system development, I am in this project ... Read the full text posted @ 2014-09-18 14:33  Zhao Read (+) |  Comments (1)   Edit

Enterprise-Class business system development Combat