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

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

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

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

4. Non-web and non-mvc mup design ideas

Heard-codenong-SH <xwj90@hotmail.com> 13:39:39
For a question, the proportion of items can be easily divided into the {category}/{name}/{action} mode.
I think there were some projects in the past that couldn't be done like this.

Chen Yong-Entrepreneurship-Beijing (** 9107533) 13:40:17
@ I heard that: Yes, but the MVC Architecture products can all be like this.

Tinny-PM-Shenzhen (** 722310) 13:42:10
Our content management system can do this, but it seems that it is not easy to do so in the process management system.

Chen Yong-Entrepreneurship-Beijing (** 9107533) 13:41:08
For other projects, if you can say your "Mode", you can also find a method. However, if the mode itself cannot be said, it cannot match.
@ Tinny: it is estimated that your content management system is designed based on MVC.
Tinny-PM-Shenzhen (** 722310) 13:43:00
Yes

Chen Yong-Entrepreneurship-Beijing (** 9107533) 13:42:23

The question "which projects can correspond to" depends on "which projects provide their design rules". For example, if MVC has its own design rules, I can correspond to them; if no rules are designed, there will be no matching.
Heard-codenong-SH <xwj90@hotmail.com> 13:42:32
Is the scope limited to Web UI projects? It seems that none of the Web UI can do this.
Chen Yong-Entrepreneurship-Beijing (** 9107533) 13:42:33
This is not a problem of user story tree, but a problem of design.

Chen Yong-Entrepreneurship-Beijing (** 9107533) 13:42:59
@ I heard: Good,The following describes non-web practices.
This idea is built upon the creation of a Web software, which has not been tested on a non-web environment (and may not have a chance in the future)
However, we can see some "Dawn ".
For example, we assume a non-web or non-UI thing, or even a DLL
At first glance, this dll has no interface at all, and there is no URL link for access.

But it must contain many classes, and each class has many methods, right?
Some of them are public and some are private, but after all, these methods will be called.
For example, if I provide an agile development DLL, you can call it to operate the agile development database.
So if I want to design the "create user Story" function, I will not design the following classes and Methods: Agile. createstory (INT fatherid ,...)
However, agile. stroy. Create (INT fatherid,...) is a namespace.
Why?
Because agile itself is too big, many functions in it will drive people crazy.How good is splitting? In addition, it is best to classify the business data that was mentioned last time (specifically in the first phase of the activity.

Chen Yong-Entrepreneurship-Beijing (139107533) 13:47:54
So, for a web, I will use/agile/stories/create? Fatherid =... to design
If it is a DLL, I will use agile. stroy. Create (INT fatherid,...) to design
Both,They all follow the "business data-business operations" concept we mentioned in the first phase of the activity.
Chen Yong-Entrepreneurship-Beijing (** 9107533) 13:49:09
In this way, we can use the demand management method to directly generate the design.

Heard-codenong-SH <xwj90@hotmail.com> 13:48:52
What are the differences between this method and the traditional object-oriented/process class design and naming conventions/best practices, as well as their advantages and disadvantages?
Chen Yong-Entrepreneurship-Beijing (** 9107533) 13:49:38
@ I heard that this method has almost no relationship with the process-oriented method, but it has a relationship with the object-oriented method.
Or even close to the peering relationship.
Heard-codenong-SH <xwj90@hotmail.com> 13:49:53
See if requriment-driven design can be summarized
Tinny-pm-Shenzhen (86722310) 13:51:44
Yes, in fact, business data can be attributed to entity classes, oriented to such object design
Chen Yong-Entrepreneurship-Beijing (139107533) 13:50:23
Business Data = Function Point Analysis "file" in FPA = controller in MVC = Class in object-oriented model (controller is Class)
Business Operation = Function Point Analysis: "Ei/EO/EQ" in FPA = action in MVC = method in object-oriented (action is actually a method)

Chen Yong-Entrepreneurship-Beijing (** 9107533) 13:52:27
MUP was created in the following ways: when we wrote controller, actoin, class, and method, we were very casual. We could write uppercase letters and lowercase letters at will. We used to write user stories at random, you can also write it as needed.
The result is that these casual things come together, and it is difficult to have a clear ing relationship.
In MUP, the three things of user story-MVC-OO are connected by the two concepts of business data/Business Operation analyzed by function points.
The advantage of concatenating is that when writing code, @ will say the sentence: requriment-driven design
This can greatly save the redesign time.
Well, let's talk about the design.