Events and user stories are related but not identical. A Yourdon event is any stimulus to the system that requires the system to respond, so, for example, a tick from an external clock could be an event. That might require a response, eg, by incrementing a counter, but it wouldn't necessarily lead to a result with direct business value to the customer, so wouldn't be a valid user story or use case.
至于 Edward Yourdon 的结构化分析方法，我不得不承认我不是很熟悉有了它，所以我无法回答你问题的这一部分。
A user story is a pattern for briefly describing a business, technical or other type of need. For example:
As a risk analyst I would like to add references to the application page so that we can store the references with the application, where the verifications team can then use them to help improve our risk rate in our underwriting.
Then in your user story you would decompose the story describing what tasks will be needed to complete the "would like" with a "done" check point being the "so that".
As far as Edward Yourdon's structured analysis methodology, I have to admit I'm not extremely familiar with it so I cant answer that part of your question.
发布评论
评论（3）
事件和用户故事相关但不相同。 Yourdon 事件是对系统的任何刺激，要求系统做出响应，因此，例如，来自外部时钟的滴答声可能是一个事件。 这可能需要响应，例如通过增加计数器，但它不一定会导致对客户具有直接业务价值的结果，因此不会是有效的用户故事或用例。
Events and user stories are related but not identical. A Yourdon event is any stimulus to the system that requires the system to respond, so, for example, a tick from an external clock could be an event. That might require a response, eg, by incrementing a counter, but it wouldn't necessarily lead to a result with direct business value to the customer, so wouldn't be a valid user story or use case.
用户故事是一种用于简要描述业务、技术或其他类型需求的模式。
例如：
作为风险分析师，我希望添加对应用程序页面的引用以便我们可以将引用与应用程序一起存储，其中然后，验证团队可以使用它们来帮助提高我们承保的风险率。
然后，在您的用户故事中，您将分解描述完成“想要”所需的任务的故事，其中“完成”检查点是“所以”。
Mike Cohn 有一篇关于用户故事及其优点的好文章 http://www.mountaingoatsoftware.com/articles/27-advantages-of-user-stories-for-requirements
至于 Edward Yourdon 的结构化分析方法，我不得不承认我不是很熟悉有了它，所以我无法回答你问题的这一部分。
A user story is a pattern for briefly describing a business, technical or other type of need.
For example:
As a risk analyst I would like to add references to the application page so that we can store the references with the application, where the verifications team can then use them to help improve our risk rate in our underwriting.
Then in your user story you would decompose the story describing what tasks will be needed to complete the "would like" with a "done" check point being the "so that".
Mike Cohn has a good article on User Stories and the advantage of them http://www.mountaingoatsoftware.com/articles/27-advantages-of-user-stories-for-requirements
As far as Edward Yourdon's structured analysis methodology, I have to admit I'm not extremely familiar with it so I cant answer that part of your question.
没错，UML 中的用户故事和用例是 Yourdon 事件的重写。 它们只是轮子的重新发明。
That´s right, user stories and use cases from UML are rewrites of Yourdon´s events. They are just a reinvention of the wheel.