共享代码和库的用户故事
我正在开发一个需要使用用户故事的项目，该项目的一部分是针对 ASP.NET 数据库执行身份验证。通过阅读本文，故事将遵循类似的模式：
作为未注册的用户，我想注册该应用程序，以便创建一个帐户......等等。
从“接受”的角度来看，我将其视为完成工作的后端部分，然后是用户可以与之交互的 UI。但是还有其他不相关的项目可以使用相同的功能，因此这将成为共享框架/库的一部分。
当代码进入没有前端的库时，应该如何编写用户故事？即使用户不会直接使用该功能，故事是否仍然应该从最终用户的角度编写？
I am working on a project that requires the use of user stories and part of the project is to perform authentication against an ASP.NET database. From reading up on this a story would follow a similar pattern of:
As a un-registered user I want to register with the application so that an account is created......and so on.
From a "acceptance" point of view I see this as a back-end part that does the work and then the UI that the user can interact with. But there are other, non-related, projects that can use the same functionality, so this will be part of a shared framework/library.
With the code going into a library that doesn't have a front-end how should the user-stories be written? Should the stories still be written from the point of an end-user even though the user will not use the functionality directly?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
不要执着于将每个用户故事都放入模板中。故事的“最终用户”视图可以让开发人员清楚地可视化功能的使用情况，并在此过程中了解上下文以更好地实现故事。它还可以帮助您垂直拆分故事，并避免编写诸如“迁移数据库”之类的故事。
如果您考虑到这两点，请写出对您的情况有意义的故事。在您的情况下，我会将调用应用程序视为最终用户，并将故事写为“作为应用程序，我想创建一个帐户，以便......”。对我来说，这提供了我在实施故事时需要牢记的正确背景。
Don't get fixated into fitting every user story into a template. The "end-user" view of the story is there to give clarity to the developers to visualise the usage of the feature, and in the process understand the context to implement the story better. It is also there to help you split stories vertically, and avoid writing stories like "migrate the database".
If you have those two in mind, then write the stories that make sense for your situation. In your case, I would consider the calling application as the end-user, and write the story as "As an application, I would like to create an account, so that..". To me that gives the correct context that I need to keep in mind when implementing the story.