在 RESTful 应用程序中模拟用户流的最有效方法是什么？
如何以一种非常简单且有效的方式传达用户通过我的应用程序所采取的路径？
我目前在 Ruby 和 Rails 环境中工作，因此我倾向于根据 RESTful URI 来可视化我的应用程序。例如，如果我希望我的用户注册，我可以匹配一个名为 /users/new 的新路由。问题是，我希望看到超越该特定操作的内容，并可视化创建帐户需要多少页面或表单以及与该流程相关的一些业务逻辑。换句话说，我希望看到工作流程图和一些实现细节（在界面级别）的组合。
我正在考虑展示包裹在盒子中的模型图片，并通过箭头将它们与相应的 GET、POST、PUT、DELETE 方法和附加的 URI 关联起来。我认为这是一个好主意，但我还没有看到激发我灵感的例子。
根据您的经验，什么可以帮助您了解全局？ Balsamiq 模型允许定义链接并浏览应用程序，但它无助于概念化。
How can I communicate in a very simple and effective way the path the user takes through my application?
I'm currently working in a Ruby and Rails environment, so I tend to visualize my application in terms of RESTful URIs. So for example, if I want my users to sign up, I could match a new route called /users/new. The thing is, I would like to see beyond that specific action, and visualize how many pages or forms does it take to create an account and some business logic associated with the process in general. In other words, I'd like to see a mix of a workflow diagram and some implementation details (at an interface level).
I was thinking in showing mockup pictures wrapped in boxes, and relate them through arrows with their corresponding GET, POST, PUT, DELETE methods and URIs attached to them. I think it is a good idea, but I haven't seen examples yet that inspire me.
In your experience, what helps you see the big picture? Balsamiq mockups allow to define links and navigate through the app, but it doesn't help to conceptualize.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
您是否想过使用思维导图？你可以尝试免费的 FreeMind
如果你坚持使用UML，您可以考虑活动图。
Have you thought of using a mind-map? You could try the free FreeMind
If you stick with UML, you could consider an Activity diagram.
我认为你走在正确的道路上。显示不同的屏幕以及屏幕之间用户交易的可能组合是一种很好的技术。基本上，您将能够显示用户在应用程序中的流程，并强调用户在此过程中将做出的决定。
此处提供了一个很好的示例 http://vimeo.com/43869717
这种技术称为故事板。您应该能够找到一些例子。但我上面提到的技术是最好的故事板技术之一。我一直使用它来向我的团队展示全局并从用户角度展示应用程序工作流程。
I think you're on the right path. Showing different screens with possible combinations of users' transactions between them is a good technique. Basically you would be able to show user's flow through your application and stress out decisions a user will make on the way.
The good example for it was presented here http://vimeo.com/43869717
This technique called Storyboarding. You should be able to find some examples. But the one I mentioned above is one of the best Storyboarding techniques. I use it all the time to show the big picture and present application workflow from user perspective to my team.