Puyuan EOS Development Platform Training Summary
2004-02-22
(This article is the experience of the technical person in charge of a software company to summarize the training after receiving the Puyuan EOS platform 3.0. The latest version of Puyuan EOS products is 5.0, the author's "5 big disadvantages" is still existing, It is still a question worth thinking.)
One EOS Development Platform
Pu EOS is a rapid development platform. Based on this platform, new systems can be customized by the functionality of existing components.
The EOS Professional is included with permissions and public two component libraries, and optional components include workflow, management and other parts. Easily call and customize new features through the default component library.
EOS provides a Studio development environment, and the customization process is fully imaged and can be implemented in a drag.
For a new business system, developers can build the entire system by ordering "performance automaton", "business automation", and the like. The system will automatically generate the corresponding code and submit it to the server.
EOS provides a database map mapping tool called a data dictionary that maps the database table into a naming entity object. The named object is called to access the database.
EOS provides an JSP generator that automatically generates a corresponding CRUD template operation interface according to an entity.
EOS supports a variety of application servers. Support deploying on a distributed system.
Advantages of the second EOS development platform
1 can develop protocol products very quickly
In the case of business needs, several developers familiar with EOS can quickly develop product prototypes. This is suitable for adoption of bidding in unfamiliar sectors.
2 Learning curve is lower than J2EE
Some complex technologies of EOS are transparent to developers. Developers don't want to know too much EJB, application servers, etc., as long as you operate EOS's various tools, you can develop and deploy. Just pay attention to the business.
3 Change the ability to change the strain ability
The entire development is based on graphical process interfaces, rarely involving program code, if the customer's needs change, just update the graphics and regenerate the code. Other modifications are less.
4 components can be accumulated
EOS provides some basic packages, and a large number of functions have been packaged. At the same time, in the implementation of different fields, a component package characteristic of the field can also accumulate for future use.
Disadvantages of the three EOS development platform
1 EOS components have no unified standards
There is no unified standard for EOS components. This has had a big impact on follow-up development and expansion. All products in the future are firmly bound to the EOS platform, the transplantability is poor, and the flexibility of J2EE is completely lost.
2 EOS some concept definition
For example, dynamic EJBs, data dictionary, components, etc., have not given a determination definition. It may be difficult to understand or deviation. In fact, dynamic ejb and data dictionary are in the concept of speculation and have nothing to do.
3 EOS will lead to a decline in company technology
The high transparency of EOS also brings a decrease in technology levels. Programmers can't master core technologies, so once unexpected, it is difficult to resolve themselves.
4 EOS can't be compatible with old products
EOS has a poor portability, and the old product is completely unable to port it on the EOS platform.
5 EOS tools still have a certain gap
Its tools have a certain gap in terms of use, maturity, etc. For example, various tools have not been integrated into the same operating interface.
Four personal opinions of EOS
Through 2 days of training, it has a general understanding of EOS. It can be considered that EOS is a relatively stable rapid development platform. However, some concepts or methods have a large risk.
The first is the idea of the entire EOS software, which is positioned in a graphics rapid development platform that generates final code by modeling business modeling. The international standard is MDA (Model Driven Architecture). The MDA development just starts, and its core is MOF or metadata, and is the IMG standard.
Confused EOS, it is just through the customization of the flowchart, and there is no global architecture or profile design, and the second is not modeled in the business. If you take the process and object-oriented comparison, EOS is the process-oriented design. However, its finished product is an object-oriented language Java code, writes the object-oriented Java code, which is the reason why it is poor transplantation. Second, the so-called component. According to my understanding, the component is a set of business functions or models that can be repeatedly used. The reuse range should be a complete set of functions instead of a class, such as a order system, may contain multiple classes, but multiplexing is multiplexed system. There is a portlet standard in Java, which is a standard defined by the portal. Each portlet can correspond to a set of components. As long as the ordering system implements the portlet standard, you can reuse the orders in any place on the web. The widely accepted components in Java are Pojo or JavaBean, which is a domain model with business features.
The components in the EOS are actually a function in a class. According to my analysis, EOS actually defines the business process in the XML file, and then calls and executes the flow with many functions of the fixed entrance. According to this way, multiplexes actually to the function. Each function is a similar parameter, typically an XML document and an entity object, and the like.
EOS does not give system interface or extension criteria, which is difficult to develop or expand, and develop a complex system risk. Standard, related to the success or failure of EOS.
EOS is not suitable for technical developers. A large number of operations and shielding of core technologies will lose interest in people who are keen from technology. This platform is relatively low for technical levels, but technical supporters familiar with business may be effective. Software development is the work of people rather than machines, so people's initiative play a very important role in development. Ignore the cultivation of people and can only bring higher flow rates.
EOS cannot be used to replace and transplant the existing OA product. However, it can be used to carry out bidding in new fields. However, it cannot be ignored is that due to the difficultiness of EOS expansion and the lack of core technologies, the dependence on EOS will inevitably.
The above is my summary of EOS3.0. After a few days of training, I think the actual platform of EOS is a lot more than propaganda, and it is still unable to use true enterprise development.
