11 agile development user Story Series: Analysis of csdn blog user stories

This is the first article in the agile development user story series. (Topic directory)

It is often asked whether there are complete user stories. I have searched for about two or three articles on the Internet, but most of them are just to describe the syntax of user stories, it does not involve the granularity of user stories or the organizational structure of a large number of stories.

We wanted to use our Martian as a case study, but we were never started considering that everyone was not familiar with our work. The day before yesterday, I suddenly thought why not use the csdn Blog system that everyone is familiar with for a demonstration, so this article is available.

The method used in the analysis process is the 10th of the series of agile user stories: the eight steps are the methods mentioned in the code structure generated from the user stories (the first four steps ), if you only calculate the time used to generate a story tree using word, it takes less than one hour (of course, this is when the system has been completed, if you have not started brainstorming, it may take two people a morning, generally, about 20% is missing. Of course this is very fast ). The advantage of this method is that you don't have to worry about what to do next, but you can focus on the business being analyzed.

Definition

Subsystem	It has no special meaning and is used as a directory.
Module	It has no special meaning and is used as a directory.
Business Data	Generally, it is a term that needs to be managed by the user in the system.Business Information. Generally, each core information includes 4 ~ 9. Otherwise, consider merging or splitting.
Business Operations	It is generally a verb or verb-object phrase.Business Operations. The most common business operation is the "add, delete, modify, query (view all, view a single)" operation.

The following three subsystems are described in the csdn blog user story Analysis page:

For front-end functions, refer: Http://blog.csdn.net/cheny_com

The background functions can be accessed after Logon: Http://write.blog.csdn.net/postlist

For community functions, refer: Http://blog.csdn.net/

The following is the help text in the Martian help system. As the hover content cannot be displayed, some explanatory text is displayed after the graph.

Note: The following is a partial explanation of the graph (not limited to the places where the graph is marked, roughly from left to right, from top to bottom)

Others' blog

If you refer to blogs of yourself and others as "blogs", the number of operations involved is far greater than 9. Moreover, blog users can clearly perceive the differences between the two, split the two.

Self-blog
You can view two views of your blog. However, the data format, display purpose, and display method of your blog are roughly the same as those of others, so you do not need to count them separately.
Comment
The comment is directly displayed in the comment list regardless of its length, so there is no "view comment details ".
View blog configuration information
The blog title, description, and other content have the same purpose (that is, the website information is briefly described). Therefore, the content is merged and called "blog configuration information ".
Blog
It refers to the setting of the content displayed on the left of the blog, not the topic referred to in the "blog series.
View custom topic details
That is, "display the content of the topic in the blog topic list ". In the Function Analysis of FPA, this is the most often forgotten function, also known as "implicit operation ".
Other omissions
For the blog administrator, "Recommended columns", "recommended experts", and "Recommended blogs" are all business data. However, as I have never seen the actual operation interface, I did not analyze it.
These business data is oriented to several "view all recommendation columns" (that is, the push box on the left or right side of the page) of common users, I am writing it below my blog homepage-homepage article. In fact, the administrator should have a page for "view all recommendation columns", but the logic may be different from ours, so it may be counted as another user story.
The advantage of this method is thatNoun-verbThe advantage of the method is that the analysis results of different persons are roughly the same. The difference is generally that the name, description, and location of a specific story are slightly different, but there is little difference in the existence and quantity of the story. In fact, the prototype of this method is functional point analysis, while the term is Ilf (this document does not analyze EIF), and the verb is EI/EO/EQ. It is said that the difference between different people using the Function Points Analysis Method for the Analysis of the same system is less than 10% (Say 5%), which is the reason for this method to be used for early quotation and estimation.
If you have any questions, please leave a message below :)