When the value is in September, the autumn is high. (I will think about 70 words.) Things that have always been considered in the near future are the title. People who have been developed from WEB are unusually familiar to screen migration, and one of our common mistakes is that the picture migration is incorrect. As far as the needs of rapid development, from an action action of a picture, it should consider its n type migration possibilities.
It is particularly important to say that the progress of the screen migration is considered to be possible. For example, an Action process, the conditions 1, 2, 3 migrate to a screen, and migrate to the B screen at the condition 4, 5, 6, and now migrate to the C screen when it is changed to the condition 6.
Before exploring the screen migration table, do some basic descriptions to enhance its necessity. The general web design is included in the specific implementation of the specific implementation of the screen migration. The picture migration map is simple, and a box represents a picture; some are rich, the representative screen is the actual browser display. The migration diagram of the development phase is best to concise, the direction of migration is still a bit, and there are other information supplements. Speaking of Web development, the word Action is probably familiar, how does ACTION action generate? What impact? How is the result? Developers must need such information: including the location of the action, the function of the action, the picture migration generated by action, and so on, the action is called an Action list. According to the standardized design document output, use the auxiliary development tool, "automatically generate the code of the screen migration control file and the business logic connection control unit" (taken from an advertisement), usually with Excel VBA, use Java to generate extremely similar logic code is also Nice.
In this argument, the author cares about the relationship between picture migration and productivity, so the application of the screen migration table is proposed. The screen migration table is created when the project is implemented, and is maintained and used in the entire process of the project, mainly for cope with possible changes in the future. Developers can learn from the screen migration table, which of the ACTION migrates to which screen is migrated under different conditions, some of which need to be completed, and it is characterized by detail, but not more business descriptions , Only limited to screen migration. From the ACTION of the screen, to the screen migration, in turn, you can contact the specific Class, track the development results from the head until tail, will inevitably produce the iterative effect of quality improvement.
