Shulou(Shulou.com)06/03 Report--

Second: the relationship between user story tree and Area in MVC Chen Yong-Entrepreneurship-Beijing (* * 9107533) 13:15:15

The following topic is the relationship between user stories and design.

The design as a whole includes both vertical and horizontal designs.

MVC, for example, can be understood as solving the problem of vertical design. He said: any code should include an M that represents business logic, a View that represents the interface, and of course a Data that represents data storage.

Most of the other MVM and the like also solve this vertical problem.

However, MVC, etc., regardless of horizontal design issues, such as: what modules should my product have? Which areas should my website be divided into?

There has always been no methodology for this, because each product must be different and there will not be a consistent method of decomposition.

Now, however, with user stories, especially the organizational structure of the large-scale user stories mentioned last time, the problem is half solved.

Chen Yong-Entrepreneurship-Beijing (* * 9107533) 13:18:13 for example, my user story has been organized according to this, so how should I divide the modules / regions?

We saw this structure last time:

It expresses a kind of "business" modularity, but it is not designed.

However, the modularization of the business is a good method of horizontal segmentation, that is, our most important implementation code, which is ultimately the result of "two knives", which is cut into multiple business modules vertically and then into layers such as MVC.

If it's not easy to understand, take a look at our own code structure and compare it to the figure above:

Chen Yong-Entrepreneurship-Beijing (9107533) 13:22:21

The three directories of Agile Products Portal in the figure below actually correspond to the three business modules in the figure above.

The picture above is very wide, this is only part of it, and most of the other directories are in the picture below.

Chen Yong-Entrepreneurship-Beijing (9107533) 13:24:02

Therefore, if the function tree of the business is well built, then the division of the module can be directly based on its structure, and the two almost completely correspond to each other, omitting a lot of horizontal design work.

The vertical design is in the specific catalog, for example, let's expand it:

In this partial catalog, what we see is the problem solved by the design of MVC: the vertical hierarchical problem.

The story tree just now solves the horizontal module problem.

This is the advantage of the "story tree", because you can design some kind of root level, that is, the module, which directly produces the module design. However, Agile's original "storysheet" cannot solve this problem.

Add: above, the root directory of the story tree can basically quickly outline the division of Area in MVC (also known as Area in Category,Asp.net).

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.