项目循环的环境
软件产品可以经历哪些环境。到目前为止我只看到：
- 设计
- 开发
- 测试
- 分阶段
- uat
- 性能
- 生产
还有其他吗？
What are the environments a software product can go through. Up to now I've only seen:
- designing
- development
- testing
- staging
- uat
- performance
- production
Anything else?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
你是对的。软件开发的传统方式（称为瀑布式）遵循这些步骤。尽管在过去的几年中创建了许多方法，并且它们正在改进当今的软件开发过程。
如果您现在不了解极限编程（XP）、测试驱动开发（TDD）、Scrum、看板、行为驱动开发（BDD）、敏捷统一流程、功能驱动开发（FDD）等方法论以及其他敏捷方法论（非常现在很常见）不用担心。互联网上有很多材料。其中一些方法侧重于源代码级别的构建和测试软件（TDD、BDD），其他方法则更侧重于整个流程的管理（Scrum、看板）。
这些方法子集中的核心思想是，需求在过程中发生变化，并且有必要在小交互中补充开发阶段和测试阶段，以便在小周期内交付具有有价值功能的软件，而不是遵循不灵活的传统方式来生产无关紧要的软件。
You are right. The tradicional way of software development (called waterfall) following these steps. Althrough in past then years many methodologies are created and them are improve the software development process nowadays.
If you don't now about the methodologies like Extreme Programing (XP), Test Driven Development (TDD), Scrum, Kanban , Behaviour Driven Development (BDD), Agile Unified Process, Feature Driven Development (FDD) and others Agile Methodologies (very common in these days) don't worry about. There are many material in the Internet. Some of that these methodologies are focused in the building and test software in the source code level (TDD, BDD), others are more focused with the management of the entire process (Scrum, Kanban).
Bu the manly idea in the subset of these methodologies is that the requirements change during the process and that is necessary to complement the stage of development with the test stage in small interactions to delivery a piece of software with valuable functionality in little cycle instead to follow inflexible traditional way to produce software that doesn't matter.
我看到的其他阶段之一是性能测试。此阶段更多的是基于产品的预期 SLA 的性能测量驱动。这是一种在 UAT 后和生产前对产品进行基准测试的方法
One of the other phases which I have seen is a performance testing. This phase is more Performance measurement driven, based on the expected SLAs for the product. It is a way of benchmarking the product post UAT and pre Production