[Online discussion] agile development user story classification and organizational structure (Phase 3-3)

Phase I: activity description, one, two, three, four, five

Phase II: activity description, one, two, three, four, five, six

Phase III:Activity description,One,II.,3,4th,5th

3: Relationship between user story tree and controller and action in MVC Chen Yong-Entrepreneurship-Beijing (** 9107533) 13:26:18
Of course, it is not enough to only solve the module design. However, take a closer look at the two figures: Code Figure: story tree:

Compare the last two figures above
Sprintcalendars = sprintcalendarscontroller, sprints = sprintscontroller ......
The "file story" we mentioned last time, that is, the "Business Data" that users can understand, can correspond well to the Controller in MVC (not exactly)
This greatly simplifies "what controllers are in a system ?" This design problem.
Take a closer look:

Is the "business data-business operations" ing of the user story Chen Yong-start a business-Beijing (** 9107533) 13:31:28
However, it is the controller of the user story (it reused itemscontroller and can be considered stroiescontroller = itemscontroller) and its method.
View All stories = index, view User story details = Details ......
There are still a lot of functions not shown below, and they also correspond one by one.
This solves the problem: "How many actions should I have in my controller? What are they ?" This design problem occurs.
Therefore, if the user story tree is reasonably arranged, the three common layers of MVC: Area-controller-action can directly borrow the structure of the user story without re-designing. This is a very important concept in MUP.

Tinny-PM-Shenzhen (** 722310) 13:36:32
Not too clear,How to determine the number of actions.
Is it solved by the design personnel merging on their own?Chen Yong-Entrepreneurship-Beijing (** 9107533) 13:35:26
For example, where is the code of this user story? If you do not rely on your mind to remember, most of them need a trace matrix. But now it is basically unnecessary. You can simply find it by digging down the structure of the user story.
This is why we add English to the user story. This English is the location of the corresponding areas/controller/action. For example, where is the code for "editing user stories?
Now the problem is simple. "edit user Story" is located in products/stories/edit, and the code will naturally be found.
@ Tinny: there are multiple "business operations" types of user stories, just how many actoin

For example:

The corresponding stories/index, stories/edit, stories/changetype, stories/changestatus, stoires/hide ....

There are several stories that are not written in English, because it is found that it is not good to write them directly on the title, which may lead to some user stories with long names and redundant information. Therefore, a field will be created in the future, which can be displayed or not displayed.