We don’t allow questions seeking recommendations for software libraries, tutorials, tools, books, or other off-site resources. You can edit the question so it can be answered with facts and citations.
Closed 6 years ago.
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
接受
或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
发布评论
评论(1)
您可以使用“4+1视图模型”。
请参阅 http://www.ibm.com/developerworks/wireless/library/ wi-arch11/
请参阅http: //www.cs.ubc.ca/~gregor/teaching/papers/4+1view-architecture.pdf
重点是从用户的角度来写。
用例。
商业实体。 不是表格。 真实实体。 在现实世界中。
进程。 不是程序。 真实的人真正做的真实流程。
物理视图。 计算机和磁盘之类的东西。 当您处理用户和需求时,这更像是一个附录。 稍后,您可以将其详细阐述为技术细节。
开发视图。 不关用户的事。 整个包的一部分,但与用户的高层讨论无关。
You can use the "4+1 View Model".
See http://www.ibm.com/developerworks/wireless/library/wi-arch11/
See http://www.cs.ubc.ca/~gregor/teaching/papers/4+1view-architecture.pdf
The point is to write from a user's perspective.
Use Cases.
Business Entities. Not Tables. Real Entities. In the Real World.
Processes. Not Programs. Real Processes that Real People Really Do.
Physical View. Computers and Disks and stuff. This is more of an appendix than anything else when you're addressing Users and Requirements. Later, you can elaborate this into technical details.
Development View. None of the user's business. A part of the total package, but not relevant for high-level discussions with users.