Title: Did not end without tail - Project development notes: Changes in the development mode
Keywords: distributed development C # project division updata UML IDEF
November 22: A little excited, a little frustrating
Thank you for your opinions! In fact, there were many problems before I didn't write this project note. I didn't realize. In the process of writing, you can experience a lot of procedures Our team is coming over in the process of confusion. There are fewer parts of the process to fill in the previously developed experience, and the ability of individual cattle people in the team. If you have any meaning and good suggestions, welcome to discuss.
In fact, it is already possible to find some problems with the development process I have said. But I think it is a note. That is still the main record fact, so the problem of the process may also have no great help now. Everyone is as an experience and lesson. But still welcome to find a good idea to solve problems.
The next time I said yesterday. After the project is trying to use UML or IDEF without results, plus us to discuss the frame itself (this is back, the process of discussing is very trouble, and the results are limited, we also discuss from the framework Some summary was obtained). It also discusses many times around the demand document. It is preparing to further develop the next development as a previous development process, an opportunity appears.
Ha, saying that this is a bit ridiculous. In fact, there is a terms that leaders submitted to the customer have a very short time to pay a detailed design. This income project team is only known to the first two weeks of submitting to customers' detailed design. This is troublesome, I haven't got it in the form of design, what should I use? I have worried about our needs. I learned from the side to the detailed design. This Dongdong customer is not very concerned. It is just that there is this article, and there is no way to come back. of. Then I used the experience of my previous ASP, I can use a pure page that can be connected to the need for a pure page that can be connected as a detailed design to meet the needs of the demand. The result of bargaining is not bad. Finally, agree to use this way.
Due to the preliminary work, and the characteristics of our framework itself, add this "opportunity", I defined the following development model:
1. Complete the database design, complete the interface display
l
Complete the work of the interface to make a system explanation in contact with the needs of the needs. Design and database design based on the requirements of the demand.
l correspond to the part of the framework
1) The generation of template files in the interface
2) Generation of overload controls in the interface
3) Generation of the scheduling interface of the main program of the interface
4) The generation of the database table, the generation of some data fixtures. And the corresponding DataAccess.Base layer is generated with the data file of the Commondata layer
l effect
Demanders can communicate with users using the interfaces we make, and further clarify the needs of users. And you can implement communication with our customers in advance. The design and preparation of the database will prepare two layers of DataAccess.Base and Commondata according to the table of the database. (Part of the preparation of stored procedures, this is also our special development process constraint.)
2. Complete interface logic
l
The tool generates a database table from DataAccess.Template until the WebService layer method, providing all provided database tables out of selectall (); addItem (); UpdateItem (); deleteItem () and so on. And the method of the stored procedure already defined from the call from WebService. And respond to all controls of all controls in the interface. Only the most simple increase, modify and delete.
l correspond to the part of the framework
i. Use your own tool to complete the code shelf for DataAccess.Template, DataAccess, BusinessRules, BusinessFacade, WebService. The DataAccess.Template, DataAccess, BusinessRules are organized according to the table structure of the database; and BusinessFacade, WebService is organized in accordance with the business structure of the client already in a step. Ii. Implement the logic of the interface. Corresponding to the operations of all interfaces need to complete the implementation of data from the Web Service and the return data (defined interface). And simple information verification of the interface.
III. Based on the generated file, the response is modified according to the interface, and the method of joining businessRules, BusinessFacade, WebService.
IV. New ways to add DataAccess when adding a new method.
l effect
A program that can run from the interface. But it is not a program that can run from the business. Just complete all the simple operations of the data on the interface (add-to-handre).
3. Complete business logic
l
The last most work is the true business core. Through the above two steps, we have implemented parts that will be completed. This part of the work is to specifically to judge the business process in addition to achieving the most basic new, modification, and delete, it needs to be implemented. For example, when deleting a commodity, it is necessary to judge whether this item has been used to wait for these business processes.
l Some of the operating frame
1) BusinessRules, for special business adding methods and calls.
2) The method corresponding to the previous layer is added to the DataAccess and the call to the stored procedure.
l effect
Finally completed.
It involves a lot of division of labor arrangements in these three stages. And the implementation of each process will bring our needs, test, and customer feedback to a new stage.
The current work of the project is in the second step. I think the next few articles will discuss the thinking of this development mode and the problems in the specific implementation process. It will also discuss the ideas of some of the gadgets we have developed.
I have to go to class in the future. Beijing is so cold, at 8:00 in the morning, pain!
(Here are some things to make a replenishment: demand staff is very complicated in our team. They have to be a priority demand research. To be the approval of user ui, do testing, technical support. Special The identity makes our demand staff understand the business's understanding, and it is very close to the relationship. But it is also a bit of overlying to the development process. So the demand staff here is in the project. Demand people may have different.)
