This article aims to explore object-oriented enterprise software development architectures, mainly to apply in the enterprise information management system. Now, with the development of OOP (object-oriented), OOD (object-oriented design) and OOA (object-oriented analysis), the Object Modeling Technique is finally formed. Using object-oriented software development methods, designers can decompose the huge and complex software system into multiple objects, each of which work together to complete the goal. Object models can clearly and concise simulate objective reality, which can help us to describe and solve practical problems with a manner that we are more easily understood and accepted. Next, an object-oriented layered architecture will be proposed.
1. Object environment
The object environment is a container for loading an object. It is inclusive to the entire life cycle of the object. He consists of the object persistence, the object activity layer, and the object representation layer.
1.1 Object lasting layer
Object-lasting layers are packaged for corporate data. Business activities will produce a lot of data. Object persistence layers are the core layer of the system; it encapsulates enterprise data into various persistent objects. And provide an increase, delete, modification, query, and transaction functions for persistent objects.
Object-lasting layers consist of persistent layers, persistent objects, and persistent objects. The persistence layer environment provides persistence, safety mechanism, transaction processing, etc., usually the database management system (DBMS) and the server are responsible. Persistent layer management provides access to the object. A set of interfaces are typically provided to the outer layer.
1.2 object activity layer
Object activity layers are packaged on enterprise business processes. Enterprise business processes are a series of activities that enterprises with customer demand and input various raw materials to creating valuable products or services for customers, consisting of a series of work links or processes, and have a successful order. There must be a certain point to point, time and space. Object activity layers are an abstract description of this series of business processes; it is an activity of a series of activities of business processes as a system object. It can behave as a persistent object to assist each other with other persistent objects or temporary objects; the result may generate new persistent objects, or change a target state, and so on. And the activity of the object changes with the change of the business process.
The object activity layer consists of a series of object activity scenarios; an object activity scene is an abstract description of a business process an activity, which is actually an active target. Object activity scenarios are started by an object representation layer or system trigger, and the activity scene is often stopped with the object of activity between the object.
1.3 object representation layer
The object representation layer is an output and input package of object activity layer data. People are the user of the system, express the object's object to the data you can understand, or transform the data input into the system, is an indispensable process. The object representation layer includes the output and input of the object.
1.3.1
Object output
Objects generated by object movable layers may be output to various devices. The most common device now is the video terminal. The format displayed in the video terminal is: text, chart, multimedia, etc. Object representation is responsible for outputting objects to these formats.
1.3.2
Object input
Regardless of how the input is intelligent, it is quite difficult to convert the input data into object. Now general video terminal inputs use a graphical user interface (GUI). Object representation is responsible for transforming input data to objects and is provided to the object activity layer.
Three-layer object architecture
2. Three-layer object architecture features
(1) Pure object system: The three-layer object architecture is based on object-oriented software development theory. In the system, everything is an object.
(2) Pure Software Hierarchical Separation: The three-layer object architecture is not to pay attention to the physical structure, which is set to the physical layer. (3) Has strong architerating: due to the pure software hierarchy, it can be adapted to large, medium and small enterprise software development modes.
3. Comparison with the N layer architecture
There may be many people asking, what is the same and different from the N-layer architecture and the three-layer object architecture?
(1) Their goals are the same. They are all organized complex systems by separating their concerns, so that the localization of changes is reduced to the overall impact, reducing the vulnerability of the system, and extends the life of the system. And the entire architecture is completed, then the changed local also enhances production efficiency because the change can be implemented faster.
(2) The three-layer object architecture is a framework of the pure software, and the layer is unidentified. The N-layer architecture is a layer that is physically separated.
(3) The three-layer object architecture is based on object-oriented, and the overall concept is an object structure. The N layer architecture is a separation point in physical structure and development logic, and the overall concept is not necessarily an object structure. For distributed three-layer object architecture is a supplement to an object of an N-layer architecture. Both are not excluded, the former is the latter expansion relationship.
(4) The three-layer object architecture is a stronger structure, which can not only be a suitable distributed large system architecture, but also a non-distributed small system architecture; this is determined by the physical platform built its physical platform. The N-layer architecture is now the most widely known and widely accepted distributed enterprise system architecture scheme, which must be distributed.
4. Three-layer object development level
(1) Realize the persistence layer of the object. Now with the rapid development of B2B e-commerce, data exchange between companies and enterprises is increasingly frequent, and the development of corporate informationization will increasingly urgently requires enterprise data exchange standards. If software vendors and industry companies can define industry data standards, provide standard interfaces; the most maintained reuse of the persistence layer of the object is maintained, and the company will no longer rely on a single software vendor software product. Dacted and win-win.
(2) Establish a secondary development to establish an application system. Due to the implementation of the object's persistence layer, it makes it easy, and it also reduces the technical threshold. Secondary development can be fully engaged in business logic development, flexibly build object activity layers and object representations.
(3) Enterprises maintain and conduct department-level development. The market changes, often leading to the implementation of business processes. So companies need department-level development. With existing object persistence layers and object representations, new activity scenarios of the object activity layer can be quickly developed to meet demand.
5. Conclude
This paper proposes an object-oriented layered system, which clarifies its structure, proposes some new concepts, and compares with existing frameworks. Using J2EE technology can be easy to architecture three-layer objects; EJB, JDO and other technologies are a nice development object persistence layer, which is also very good for developing object activity layers and object expression layers, Struts and TapeStry. Since individual level is limited, it is inevitable that there is nothing, I hope everyone criticates.
6. Reference
[1] Object-Oriented Systems Analysis and Design Ronald J.Norman
[2] UML object design and programming Liu Rundong
[3] Applying MDA TO
Enterprise
Computing David S. Frankel
