Software technology serial (1)
The charm of PowerBuilder (1) Alternative perspective for application development barriers
Author: breeze profile http://gentlebreeze.home4u.china.com
It is first thought of the problem of software reuse first. How to make software development standardization, sharing, assemble is the goal of people in this industry for many years. Most of the current technologies and systems are surrounded by this topic. From the development process of software structure, this issue can be clearly seen. What needs to be explained is that we don't think .NET is completely tried to solve this problem, .NET solves the problem of system interoperability, which is connected and collaboratory in different systems. The solution that truly solve these problems has not surpassed the structure as the cornerstone. However, the obstacles encountered in the reality in the application of software development are not just a problem, or commercial software companies are more complicated in the process of customer service, more realities. We see such a reality, the customer is not interested in our promise, and they can't understand why the business function that is not complex is always changed, and it can't be realized. What is even more embarrassing is not only business logic, but even integration, connectivity, etc., the things we have previously market it is not achieved, and customers can also bear or not. We believe that the most realistic obstacle to application software development is the contradiction between customer business logic implementation and software development efficiency. Mainly manifested in the following points 1. Since customer competitive pressure is increased, the development time is getting shorter and shorter 2. It is necessary to understand the user's business logic to implement software.
3. The customer's business logic is increasingly personalized to challenge product development of completely standardized models 4. Available for the specialty and temporary requirements of customer business logic. 5. Ability makes customers make customers as soon as possible Understand whether the software meets their requirements and modified in time
Obstacles Eliminates Powerbuilder 1. It is difficult to quickly reduce the cost of customer demand. You need a certain industry knowledge, communication skills and abstract capabilities, which is not a problem with technical category. The technical category only solves the providing method to help you describe the needs and adjustment of the examber, such as UML. So we believe that the time to understand the customer needs is relatively fixed. In this case, try to reduce the overall time only to reduce the time of software development, that is, it is necessary to have a fast implementation of the business logic and the communication with the customer to quickly respond to the customer's changes. A lot of 3GL is relatively strong, but the development time is too long, especially the interface and logic separation, which has increased dramatic, a simple requirement to write basic code and connect code on multiple levels, which makes the developer do not take more time spend more Energy is in understanding business logic. The overall budget of the item is known is that there is a limit and can only balance and cannot be taken into account. The 4GL of PowerBuilder is reflected on the principle of rapid implementation. In particular, the integration of calculation logic and interface constructs can be achieved in the field of data calculations. Calculate columns and access to computational columns, packets and packet calculations, etc., simultaneous logic and interface simultaneously can be implemented simultaneously. We say that ADO / JDBC is a good data access model, but there is no data computing power. It is a simple calculation for the results set with JDBC. The method loop method, and use PowerBuilder you need to do it is Click . The data calculation capacity is concentrated in the efficiency principle of commercial software development. Other other RADs separate the interface and the data itself, which naturally has the advantages of flexibility, but forcing the developer to perform frequent switching to complete the logic and interface. According to Sybase's explanation: You should focus on the understanding of business logic rather than code implementation. Second, the low-cost system and project implementation of technology is ultimately profitable. If the cost of customer demand as described above is also difficult to reduce, we must strive to reduce overall development costs. In addition to achieving the rate of learning curves, average wage, cultivation, loss risk, etc. The main way of lowering technology costs is focused and open. Because the customer never needs to solve it, only the key problem is solved. Just as many technicians know, the cost of application software is still mainly focused on access, calculation, and data performance on relational databases, and different languages have different models, this problem plasted developers. Powerbuilder keeps this low-cost advantage in this area, and the version 11 version is about to encapsulate calendar controls to the data window or even the tree structure expression form of the data window. In addition, efforts to expand this area of specialty, For example, handheld devices, web. Also make good areas and other systems can integrate such as J2EE and .NET (this will be discussed in detail in later serial load). This allows yourself in the area that can be dissolved into other architectures, regardless of .NET and Java itself do not provide sufficient powerful and low-cost data calculation models, which always limits their application, this openness The way it makes your own specials to zoom in quickly. When we use Java to do service development, if there is a data window as a data calculation model, it is to be implemented. This idea is different from Java and Microsoft attempting to do. Third, business exchange and procedures integration risk often comes from such a reality: users don't see the results often unable to explain their needs, this is the importance of prototype methods. Many analysts have drawn flow charts, IPOs look to customers, and let customers confirm, the result is that customers have to learn these graphics, but in the end, I can't say it clearly. It doesn't mean that modeling is not important, but must have good ways and customer exchange needs, so that customers may confirm the demand, only in modeling is not enough.
