2004-05-10
Today, I submitted the system development plan today. After signing from the contract, the project is officially implemented today. In the morning, I learned the basic user needs. Check out the existing software that users cannot run. And users communicate with the user's instruction manual, which has a preliminary understanding of the outline of the system.
2004-05-11
According to the results of yesterday's research, a preliminary example of example is established in the morning, and now prepares to refine the illustration of the example. By analyzing the user business process and the analysis, the user's case is drawn. Differential use cases have been divesed. The use case participants will evolve into subsequent designed users, and the use case will evolve to the system's function, and the relationship between them will evolve into user permissions. The use case model can evolve into a use case-analysis model, the boundary class of the system can evolve into the user UI, the control class can evolve to system logic, and the physical class can evolve to the system's database model. This analysis and design process uses the use case model as the core, and the software development method of iteration and increment is used, and the system modeling is expanded in the process of RUP process guiding ideology. In the afternoon, I made some investigations in the second-hand car market and took a description of the existing software.
2004-05-12
Referring to the instructions for the use of the evaluation software yesterday, think about it, and made an assessment software in Visio, and communicated with users tomorrow. I feel that I have some experience in the assessment of used cars. I didn't have a demand research list, because it was prepared for the needs of the needs of experience. Before the contract is signed, I have a understanding of the business needs of the user. Now it is mainly to in depth, system demand we will slowly provide, non-functional demand decisions technology architecture, I have considered it. In fact, there is no best demand analysis method, and users who have been in contact with each project are different. The characteristics of the business are different, and it is necessary to flexibly adopt demand analysis methods. Based on the use case model, the RUP development process designed as the core of architecture is very good. But how to effectively transform the needs of users into a use case model is not a simple matter. According to the understanding of the user business process, the preliminary example of the establishment is still not enough, and the next step will be described in detail. The text description of the use case is a good supplement with an example. Analyze the user's business processes, find which objects participate in this process, what responsibilities have, can evolve the system's analysis class diagram model.
2004-05-13
In the morning, I sent a diagram of the interface of the two-handed car yesterday. I communicated with the business personnel. Through examples, I understood some of the methods of the second-hand car assessment, which has a further understanding of the assessment business. I found that I still have to understand some user specific business, and then discuss with users. Don't know the user's business, you don't know what questions, how to model it. The use of examples and use examples is a tool for caught demand. Tools can only carry your needs, but many demand skills need to accumulate. In fact, the needs of users is to understand the business processes of the user, see if the business process can be improved, analyze the business process, find an example of the example, find the object of the process, determine their duties, and further improve the analysis. The class diagram is the most important view, and the contour of its system is basically clear.
The interface schematic can quickly communicate with the user, which can be effectively obtained. Users can see an interface without having to use an example to be effective. After a sufficient grasp of the needs of the user, use the case to carry the need to model the modeling of the system. I don't have to happily use the example of painting. Now I think about the actual work of the user. After understanding, I will display more detailed demand in the case, and the demand specification specification. As the project manager, we must grasp the rhythm of the entire project, and strictly enforce it according to the development plan.
2004-06-02
For a few more time, I have finished the user research and write the system requirements specifications. I have left 4 demand documents to the user, allowing them to review them. Now return to the company to do design. My plan is 18 working days to do design, 22 working days to develop. I want to be a system prototype to the user. However, these two weeks I was responsible for the agricultural projects, a project, manufacturer didn't want to do it, coordinate for a long time, and some trivial things, I didn't fully put into design, although there is no writing design document, but some I have to consider things in the design, I have already had a number. I have comprehensively adopted SOA architecture mode. This is a very popular software architecture mode. I want to try it with it. The software architecture design already considers that the interface part of the software, I am letting my artist gave me an interface prototype. These aspects are fixed, and the software is generally like, others are refining the software function. 2004-06-04
The architecture and interface design of the used car identification assessment system has planned, and now consider the authority management of the system. Traditional permission design is hardcoding in the module, permission judgment on each function button. Such permissions and specific functional coupling are too strong. Another way is to set a proxy class at the entrance of each module, allowing it to handle permissions, so that modules and permissions are isolated by the proxy authority class. In fact, most applications have only dealt with what the user has permission, but not considering what data has permission. This is also a more complicated issue. Is to solve the WHO (who) handle what (data). The processing of data can be encapsulated to functionality, and the functionality can be packaged to the role, and the role can be packaged to the user. This uses no direct contact, which is related to the role.
2005-01-12
Now the software has been developed, and the trial operation in the second-hand car market is 4 months. When I brought the system acceptance, the user began to arrange personnel testing, raise the problem, let me refer to other similar software, let me contact a similar software in the province, modify the software. Ha ha! Why is the software development will be like this! ! !
