软件任务/项目规划书籍？
我正在寻找一本书，告诉您如何将软件（或任何东西；不一定是特定于软件的）任务或项目拆分为离散的块，并帮助阐明所有不明显的问题和细微差别当你刚开始编程时。
我应该买一本关于用例的书吗？ 如果是这样，那又怎样？
我正在寻找一本书，它可以帮助我从一个简单的故事（例如“用户希望能够为自己指定电子邮件地址，或指定他们没有电子邮件地址”）转变为 UI 图，以及编码任务列表和测试要求（因此编写单元测试变得非常简单）。
我厌倦了开始执行一项任务却因为没有经过充分考虑而在中间感到困惑。
谢谢！
I'm looking for a book that tells you how to split up a software (or anything; doesn't have to be software-specific) task or project into discrete chunks, and helps elucidate all the issues and nuances that aren't apparent when you just start programming.
Should I get a book on use cases? If so, what?
What I'm looking for is a book that can help me go from a simple story like "The user wants to be able to specify an email address for themselves, or specify that they don't have an email address" to a UI diagram, along with a list of coding tasks, and testing requirements (so writing unit tests becomes very straightforward).
I'm tired of starting on a task only to be flummoxed in the middle of it because it wasn't thought through properly.
Thanks!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（8）
《Code Complete》是一本包含大量有关规划项目的信息的书，特别是不同的规划方法，包括伪代码的使用以及其他接近它的方法。
"Code Complete" is a book that contains a great deal of information on planning projects, specifically different ways to plan, including the use of pseudo-code, among other ways of approaching it.
我喜欢这个：软件工程 - 从业者的方法。 它涵盖了软件工程的不同方面（不仅仅是实施）。
I liked this one: Software Engineering - A Practioner's Approach. It goes over different aspects of software engineering (not only implementation).
我强烈建议研究思维导图——这是一本好书：
映射内部空间：学习和教学视觉映射
和开源思维导图工具：< a href="http://freemind.sourceforge.net/wiki/index.php/Main_Page" rel="nofollow noreferrer">FeeMind
但不要陷入与任何软件的斗争 - 你可以使用蜡笔。 思维导图有点像 WBS（工作分解结构），是一种自由形成的有组织的思维。 当将大型应用程序（项目）分解为较小的部分时，您经常会发现不同的分支、非常定义和非常未定义的区域以及外部交互都有重复的功能，以使系统正常工作......用一些图片以图形方式表示这一点也有帮助
I highly recommend looking into mindmapping - here's a good book:
Mapping Inner Space: Learning and Teaching Visual Mapping
and open source mindmapping tool: FeeMind
but don't get stuck in wrestling with any software - you can use crayons. mindmapping is sort of a WBS (work breakdown structure) and sort of free formed organized thinking. When breaking a BIG application (project) to smaller pieces you often find that you have repeated functionality down different branches, very defined and very undefined areas and external interactions to make the system work...graphically representing this with some pics also helps
由于您（也在）寻找从用户故事/用例到测试用例的简单路径，您可能会发现 BDD 和框架，例如 StoryQ 很有趣，因为它将您的用例转换为许多单元测试。
Since you are (also) looking for an easy path from user stories/ use cases to test cases you might find BDD and frameworks like StoryQ interesting, as it convert your use cases to a number of unit tests.
虽然不是特定于软件，但 PMI 的 PMBOK 很好地概述了项目规划流程的运作方式。
PMBOK
While not specific to software, the PMI's PMBOK is a great overview on how the project planning process works.
PMBOK
尝试 XP 系列极限编程 -- 我似乎记得极限编程安装特别对此类问题进行了很好的讨论。
Try the books in the XP Series on extreme programming -- I seem to recall Extreme Programming Installed in particular having a good discussion of these types of issues.
Steve McConnell 的书 Rapid Development: Taming Wild Software Schedules 在我大学的本科生中使用软件工程过程和项目管理课程。 它是 Code Complete 的伴侣。 CC 处理编码问题，而快速开发则讨论管理问题。
Steve McConnell's book Rapid Development: Taming Wild Software Schedules is used in my university's undergraduate course on Software Engineering Process and Project Management. It's very much a companion to Code Complete. CC deals with the coding issues, while Rapid Development talks about management issues.
Scott Ambler 的对象入门也是您提到的主题的有用概述。
Scott Ambler's The Object Primer is also a useful overview for the topics you mention.