B / S development experience
Author: Chen edge Contact: luandao2000@gmail.com blog: http: //blog.9cbs.net/luandao2000 home page: http: //www.spbase.com
Recently, a telecommunications project is used, using the BS structure, the tool is used by VS.NET, the language C #. There have been many problems in the development of bumps, but basically get better solutions. In fact, no matter what type of development, the early architecture design needs serious research. Our project is basically unfamiliar with the development of the Web because of the beginning of the beginning, before the company is basically developed on the Win32 platform, so there is no end to this kind of project. In several aspects, we will talk about some of the problems and solutions that appear in development. 1. The previous research and architecture design is not unknown. I used to think that my understanding and reinging calculations were better, and it was basically speaking that others' ideas. The people of some business ports of this time and the communication process have discovered that even if you are smart, you want to understand what others are talking about, it is basically unobportable. As we all know, telecommunications companies are typical state-owned enterprises, although various basic equipment is also a scientific product, but in management, the malpractices of state-owned enterprises basically have. The responsibility is divided into clear, the departmental differences, people are scattered, and there are many conferences. Such problems have caused a lot of difficulties to our early investigation, and there is more than 2 months in research. The last unique harvest is: Telecom, our customers, basically understand what they need a system that can do. At the same time after repeated operational exchanges, our project groups basically understand many details in the business, understand the specific needs of customers. There are too few people in the early stage, and the front desk is accepted basically started to do alone. In the case of studying the existing situation and the system of the customer, I think the business acceptance port of the front desk will be better, because the business is very large as the provincial business hall. The web page does not necessarily satisfy such a need in many ways (there is not much solution to Web development in the previous period). The view is that the existing system CS mode is too old, there are many problems in maintenance, so it is more likely to use BS mode to reduce maintenance investment. Of course, as a research and development of an industry class software, the customer's recommendations are basically your direction, and the final project is developed in BS mode. Because the development of the BS mode is not familiar, I start to view various information, compare various factors Comparison after J2EE and ASP.NET, after the use of ASP.NET to develop, of course, the most important reason is due to Win32 development Experience let me confident, I believe that it is not too difficult to develop WEB development. So started to study the development examples of VS.NET, began to study the N-layer architecture. Duwamish and PETSHOP are very good learning examples. In fact, I have always feel that I have a little small matter in order to make a simple data reading and writing operation, and then I will start the layering with the gradual deeper's gradual deeper. Concept has some understanding. After comparing the characteristics of these two examples, it is certain that it doesn't matter, it can only be said that it has embodied two different development methods of Microsoft. After reading the two articles of Sun Chamens, I was deeply inspired and decided to use the duwamish architecture to design the entire project. Although there is a comment on the online commentary: duwamish's structure is slightly bloated, and the resource consumption is large. However, from the carrier of the business object, use the type of DataSet to describe business objects, although it is indeed a larger number of objects from the resource, but from the functional hierarchical design, individual feels It does reflect the substance of layering. That is: each of the various modules. Every layer is responsible for the work you are paying attention to: the processing of business data processing, the interface layer provides input and output, and the data access layer completes the actual read and write work, indicates mapping of the labeling of the business object and database.
The layer is dependent on the interface to interact, complete the processing of the business. After the architecture is set, some discussions are made inside the project group. Of course, just look at Duwamish on the very floating level, and then basically set it. 2. There are some typical issues in the development. Of course, the determination of the business objects needed for business processes is first, and I start to study some of the features implemented by the original acceptor system. B, data access layer of transaction C, layer and layer interface design 3, how to test first column entries will continue to write
