软件规划：集成
我目前是一群学生的团队负责人，他们正在研究一个由电气和计算机工程专业的学生组成的课程项目。我是一名电气工程专业的学生，我还没有参与该项目的软件组件。我觉得软件开发和测试的计划可以更有条理，但真的不知道从哪里开始。团队指定了一名软件主管，并集体集思广益，以通俗易懂的方式（即，没有与编程、脚本和其他语言或框架相关的技术术语）来确定项目应该能够做什么。您建议团队如何更好地规划开发、测试和集成过程？团队考虑的标准是不同功能和系统之间的一致输入+输出、系统之间的通信协议以及操作条件。提前致谢。
I'm currently the team leader of a group of students working on a project for a course right now consists of both electrical and computer engineering students. I'm one of the electrical engineering students, and I have yet to work on the software components of the project yet. I feel that the planning for the software development and testing could be more organized, but didn't really know where to get started. The team has assigned a software lead, and collectively brainstormed on what the project should be able to do in layman's terms (i.e. without technical jargons related to programming, script, and other languages or framework). What would you suggest the team doing to better plan the development, testing, and integration process? The criteria that the team is taking into account are consistent input + output between different functions and systems, communication protocols between systems, and operating condition. Thanks in advance.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
由于团队已经就项目的一些高级要求进行了集思广益，因此您正在顺利完成一个组织良好的项目。我建议您合作编写并审查您正在开发的技术规范。将所有内容都写在纸上、定义离散组件/模块等以及定义这些部分的交互/期望的行为都将有助于在项目早期解决细节并识别潜在问题和误解。在项目早期花时间做这件事将有助于避免以后浪费时间。
使用版本控制。让小组成员互相交流并了解规格或要求的任何变化。如果这是一个复杂的项目，我建议制定一些里程碑，以便您在截止日期之前拥有关键的功能，以便您可以在时间允许的情况下开始添加任何值得拥有的功能。
在线查看“功能规范”模板和示例，了解您的模板和示例可能包含的内容。不要太认真地对待它们，也不要严格遵循它们——你知道正确定义你的项目需要什么，什么是不必要的。但我认为将所有内容写在纸上并进行讨论对您的项目最有帮助。
Since the team has already brainstormed on some high-level requirements for the project, you are well on your way to a decently-organized project. I would suggest that you collaboratively write up and review a more technical specification of what you are developing. The act of getting it all on paper, defining discrete components/modules/etc, and defining the interactions/expectations for these parts will all help to iron out details and identify potential problems and misunderstandings early in the project. Spending the time to do this early in the project will help to avoid wasted time later.
Use version control. Keep the group talking to one another and informed of any changes to the specs or requirements. If it is a complex project, I would suggest making some milestones, so that you have your crucial functionality before the deadline so that you can start adding any nice-to-have functionality as time allows.
Take a look at "functional specification" templates and examples online to get some good ideas of what yours might include. Don't take them too seriously, and don't follow them to the letter - you know what is needed to properly define your project, and what is not necessary. But I think getting it all on paper and talking it over is what will help your project the most.
首先让它发挥作用，然后再让它变得更好。这意味着尽早集成，然后才添加更多功能。不要花太多时间提前计划，因为你的计划可能无论如何都行不通。我在实践中见过很多次这样的情况：人们在单独编码一周后才开始集成各个部分。它永远不会按照计划进行。
拥有一个可用的应用程序还可以加快开发速度，因为可以进行实际测试，而不必依赖于实际上不起作用的占位符。它似乎也有心理作用。
First make it work, then make it good. This means integrating early and only then adding more functionality. Do not use too much time planning it in advance, as your plan will probably not hold anyway. I have seen this in practice too many many times when people start integrating parts only after a week of coding them separately. It never goes according to the plan.
Having a working application also speeds up the development because actual testing can be done instead of having to rely on placeholders that do not actually function. It appears to have a psychological effect as well.