注：几篇关于“绿地 / 棕地”的文章合辑，机翻，未校。
Greenfield vs Brownfield
绿地 vs 棕地
Greenfield vs Brownfield: Understanding the Software Development Differences
绿地与棕地：了解软件开发的差异
Software has become one of the strongest, most dynamic industries in the world. Developers have to use the right methodologies, services, and software tools. Otherwise, projects cannot get developed in the right way. Plus, software developers have to meet and exceed the demands of modern companies. Greenfield and brownfield are two unique software development concepts.
软件已成为世界上最强大、最具活力的行业之一。开发人员必须使用正确的方法、服务和软件工具。否则，项目就无法以正确的方式开发。此外，软件开发人员必须满足并超越现代公司的需求。绿地和棕地是两个独特的软件开发概念。
Each one provides a very different approach toward creating cutting-edge software. The key is for developers to understand the differences in service approaches. Some developers prefer greenfield services and others prefer brownfields services. Are you ready to find out why? Let’s get started. We’ll begin by going over the basics of both software construction methods.
每个人都为创建尖端软件提供了非常不同的方法。关键是开发人员要了解服务方法的差异。一些开发人员更喜欢绿地服务，而另一些开发人员更喜欢棕地服务。您准备好找出原因了吗？让我们开始吧。我们将首先介绍这两种软件构建方法的基础知识。
How Does a Greenfield Project & Brownfield Project Affect Software Development?
绿地项目和棕地项目如何影响软件开发？
The software industry isn’t the only one that uses greenfield projects/brownfield projects. Many industries besides IT use these two terms. The meaning of the terms is almost always the same. What is a greenfield project? A greenfield project is a new project that starts from scratch. Whereas, a brownfield project has already gotten worked on by people.
软件行业并不是唯一一个使用绿地项目/棕地项目的行业。除 IT 之外，许多行业都使用这两个术语。这些术语的含义几乎总是相同的。什么是绿地项目？绿地项目是从头开始的新项目。然而，一个棕地项目已经由人们参与。
A brownfield project now gets handed off to new people who can complete it. Brownfield cloud systems often have problems in which a team of experts must fix each issue. Both greenfield and brownfield services apply to the construction of any software application. In fact, software construction has never been the same since the rise of both methods.
现在，一个棕地项目被移交给可以完成它的新人。棕地云系统经常存在问题，专家团队必须解决每个问题。绿地和棕地服务都适用于任何软件应用程序的构建。事实上，自从这两种方法出现以来，软件构建从未相同。
What Is a Greenfield Product in Software Development?
什么是软件开发中的绿地产品？
“Greenfield product” and “greenfield project” almost always refer to the same IT services. Greenfield products are software projects where development begins from scratch. This type of product isn’t as common as it once was. Greenfield software projects are never built from an existing program/service.
“绿地产品”和“绿地项目”几乎总是指的是相同的 IT 服务。Greenfield 产品是从头开始开发的软件项目。这种类型的产品不像以前那样普遍。Greenfield 软件项目永远不会从现有程序/服务构建。
Leave that to the brownfield product. All brownfield projects get constructed from a current software program. We’ll get more into greenfield vs brownfield services later on in this article.
把这个问题留给棕地产品吧。所有棕地项目都是从当前的软件程序构建的。我们将在本文后面详细介绍绿地服务与棕地服务。
What Is the Greenfield Approach of Software Development?
什么是软件开发的绿地方法？
The greenfield approach refers to software development services. That product development creates a system that can adapt to a new environment. In other words, the development process begins with a clean slate. This means that no new services use a legacy code. The greenfield product approach is best for developers who want to start fresh on a project. These developers do not want to deal with dependencies and restrictions.
绿地方法是指软件开发服务。这种产品开发创建了一个可以适应新环境的系统。换句话说，开发过程从零开始。这意味着没有新服务使用旧代码。全新产品方法最适合希望重新开始项目的开发人员。这些开发人员不想处理依赖关系和限制。
What Is the Greenfield Code of Software Development?
什么是软件开发的绿地代码？
A greenfield code is part of the greenfield software development process. This is when developers begin a brand new project. This sometimes gets referred to as clean slate development. A greenfield code lacks any form of legacy code. This means that developers don’t have to deal with old development. Instead, they start afresh and can work from scratch on the product. Other than business rules, they do not have to adhere to any development restrictions.
绿地代码是绿地软件开发过程的一部分。这是开发人员开始一个全新项目的时候。这有时被称为 Clean Slate 开发。绿地代码缺少任何形式的遗留代码。这意味着开发人员不必处理旧的开发。相反，他们重新开始，可以从头开始处理产品。除了业务规则之外，它们不必遵守任何开发限制。
What Is a Brownfield Application in Software Development?
什么是软件开发中的棕地应用程序？
A brownfield application often refers to one of two key software development concepts.
棕地应用程序通常是指两个关键软件开发概念之一。
-
A major upgrade of the software application or relevant technology.
软件应用程序或相关技术的重大升级。
-
Redeveloping an existing application.
重新开发现有应用程序。
Here is an example. A developer can use brownfield applications to take care of backward compatibility issues. These existing issues can relate to any product. The technology developer can adjust current interfaces, existing file formats, and modules.
下面是一个示例。开发人员可以使用棕地应用程序来处理向后兼容性问题。这些现有问题可能与任何商品有关。技术开发人员可以调整当前接口、现有文件格式和模块。
What Is Greenfield Software Development?
什么是绿地软件开发？
Greenfield software development is the concept of developing systems for new environments. This means that the development phase of a product begins with a clean slate. Greenfield processes never need any existing legacy codes. The approach ensures that developers can start fresh on their projects. They won’t feel limited by existing restrictions while creating a product.
绿地软件开发是为新环境开发系统的概念。这意味着产品的开发阶段从零开始。绿地流程永远不需要任何现有的遗留代码。该方法确保开发人员可以重新开始他们的项目。他们在创建产品时不会感到受到现有限制的限制。
Pure greenfield projects have become rare in recent years. That’s because developers often have to interact with/update existing code. Or, they might need to enable some integrations. (Security integrators are common.) Here are three examples of greenfield software development processes.
近年来，纯粹的绿地项目已变得罕见。这是因为开发人员经常必须与现有代码交互/更新现有代码。或者，他们可能需要启用一些集成。（安全集成商很常见。以下是 greenfield 软件开发流程的三个示例。
-
Creating an app or website from scratch.
从头开始创建应用程序或网站。
-
Putting a new data center in place. Data centers are important. They help companies send and receive new information.
建立新的数据中心。数据中心很重要。他们帮助公司发送和接收新信息。
-
Starting a new riles engine.
启动新的 riles 引擎。
Let’s now go over three examples of greenfield software projects.
现在让我们看一下 3 个绿地软件项目示例。
-
Creating a new eCommerce solution for a business that hasn’t had one. (Primavera Ops and other services used to do this. But Primavera no longer gets good reviews.)
为没有电子商务解决方案的企业创建新的电子商务解决方案。（Primavera Ops 和其他服务过去曾执行此操作。但 Primavera 不再获得好评。
-
Rewriting an outdated software program using a new language. (No existing code gets used beyond applying business rules.)
使用新语言重写过时的软件程序。（除了应用业务规则之外，不会使用任何现有代码。
-
Constructing a new application that executes never-before-seen tasks.
构建一个执行前所未见任务的新应用程序。
What Are the Advantages of Greenfield Software Development?
绿地软件开发的优势是什么？
There are *four major advantages* of greenfield software development.
绿地软件开发有四大优势。
-
Greenfield development positions developers to put a technology solution in place. That software infrastructure solution is often state-of-the-art. It is always built from scratch to ensure articles of high-quality infrastructure.
绿地开发使开发人员能够实施技术解决方案。该软件基础架构解决方案通常是最先进的。它总是从头开始构建，以确保文章具有高质量的基础设施。
-
Greenfield infrastructure development gives software developers a clean slate with data.
绿地基础设施开发为软件开发人员提供了一张干净的数据板。
-
Developers don’t feel obligated to operate within any infrastructure constraints. For example, they don’t have to adhere to existing infrastructure. the system, or data.
开发人员不觉得有义务在任何基础设施限制下运营。例如，他们不必遵守现有的基础设施。系统或数据。
-
There are no ties to current software when using the greenfield development method. There also aren’t tied to existing business infrastructure processes or preconceived notions.
使用绿地开发方法时，与当前软件没有任何关系。它们也不局限于现有的业务基础设施流程或先入为主的观念。
What Are the Disadvantages of Greenfield Software Development?
绿地软件开发的缺点是什么？
There are *four major disadvantages* of greenfield software development. Let’s go over the data.
绿地软件开发有四个主要缺点。让我们回顾一下数据。
-
Greenfield development doesn’t provide a clear direction. This leads to a sharp increase in the degree of risk. For example, a company’s security can get affected. This happens when developers do not understand modern cybersecurity infrastructure.
绿地开发没有提供明确的方向。这导致风险程度急剧增加。例如，公司的安全性可能会受到影响。当开发人员不了解现代网络安全基础设施时，就会发生这种情况。
-
Every aspect of a new (not existing) system has to get defined. This can make developers have to work many hours.
新（不存在的）系统的每个方面都必须定义。这会使开发人员不得不工作很多小时。
-
There are almost too many development options when it comes to data. This can make developers second-guess which development approach to take.
在数据方面，几乎有太多的开发选择。这可能会使开发人员重新猜测要采用哪种开发方法。
-
It’s sometimes difficult to get everyone involved to make crucial decisions. This can lead to a time extension for many greenfield software projects. Sure, these disadvantages can seem scary. But don’t rule out greenfield processes taking care of the management of your software. It comes down to how you want to go about applying your software management plans.
有时很难让每个人都参与进来做出关键决策。这可能会导致许多绿地软件项目的时间延长。当然，这些缺点似乎很可怕。但不要排除绿地进程来管理您的软件。这归结为您希望如何应用您的软件管理计划。
What Is Brownfield Software Development?
什么是棕地软件开发？
Brownfield software development deals with developing/deploying a software system that is new. But here’s the catch. The brownfield developers conduct deployments with legacy/existing software systems. Brownfield development often takes place when a company wants to improve an application. This compels developers to adjust code that’s already gotten created.
棕地软件开发涉及开发/部署新的软件系统。但这里有一个问题。棕地开发人员使用旧式/现有软件系统进行部署。当公司想要改进应用程序时，通常会发生棕地开发。这迫使开发人员调整已经创建的代码。
This means that new software architecture has to coexist with current systems. Once this happens, functionalities and capabilities get boosted for a business*.* For example, the existing cloud of your own business could get restructured. And the restructuring of the cloud could happen through brownfield. But say management at your business wants to create a new cloud. That means brownfield software manufacturing wouldn’t work as a solution. Instead, a greenfield manufacturing project could create a new cloud.
这意味着新的软件架构必须与当前系统共存。一旦发生这种情况，企业的功能和能力就会得到提升。例如，您自己企业的现有云可能会进行重组。云的重组可能通过棕地进行。但是，假设您公司的管理层想要创建一个新的云。这意味着棕地软件制造不会成为一种解决方案。相反，绿地制造项目可以创建一个新的云。
Let’s go over three examples of common brownfield software development data processes.
让我们回顾一下常见的棕地软件开发数据流程的三个示例。
-
Putting a new management module into a current enterprise system.
将新的管理模块放入当前的企业系统中。
-
Integrating new features to the software that’s already gone through the development process.
将新功能集成到已经完成开发过程的软件中。
-
Boosting the functionality or management of an app by upgrading the code.
通过升级代码来增强应用程序的功能或管理。
Next, let’s discuss three examples of brownfield projects.
接下来，让我们讨论三个棕地项目的例子。
-
Inserting new management features into software that’s already gotten developed.
将新的管理功能插入到已经开发的软件中。
-
Code-revising that boosts functionality and adjusts application performance with QA testing.
代码修订，通过 QA 测试增强功能并调整应用程序性能。
-
Codebase updates that boost the management functionality of a program.
代码库更新可增强程序的管理功能。
What Are the Advantages of Brownfield Software Development?
棕地软件开发有哪些优势？
There are *four major advantages* of brownfield software development. Let’s now assess each piece of data.
棕地软件开发有四大优势。现在让我们评估每条数据。
-
Developers have a section to start that contains a predetermined direction for a business.
开发人员有一个部分要开始，其中包含预先确定的业务方向。
-
The developers/management can add improvements to any current technology solution.
开发人员/管理人员可以对任何当前的技术解决方案进行改进。
-
Developers can use defined technology solutions and defined processes to improve a business.
开发人员可以使用定义的技术解决方案和定义的流程来改进业务。
-
The developers can reuse existing data codes while inserting new features. The management of these steps might seem complicated. But most companies use tools that make the development processes simple.
开发人员可以在插入新功能的同时重用现有数据代码。这些步骤的管理可能看起来很复杂。但大多数公司使用的工具使开发过程变得简单。
What Are the Disadvantages of Brownfield Software Development?
棕地软件开发的缺点是什么？
There are *four major disadvantages of brownfield software development.*
棕地软件开发有四大缺点
-
Software developers must have tons of knowledge about current systems. The knowledge also applies to data and services that will get the new system built.
软件开发人员必须对当前系统有大量了解。这些知识也适用于构建新系统的数据和服务。
-
Designers might have to spend time re-engineering the portions of current complex environments.
设计人员可能不得不花时间重新设计当前复杂环境的各个部分。
-
Developers must have a thorough understanding of the business’ IT technologies. Otherwise, the project could fail for a business once it can land.
开发人员必须对企业的 IT 技术有透彻的了解。否则，一旦落地，该项目可能会失败。
-
Working with legacy code is a time-consuming process when it comes to development. This can land any company in hot water. How so? By any business dealing with expensive development costs.
在开发方面，使用遗留代码是一个耗时的过程。这可能会使任何公司陷入困境。怎么会这样呢？适用于任何处理昂贵开发成本的企业。
Greenfield Project Software Development Summary
绿地项目软件开发摘要
A greenfield project refers to developing a new application of software at any business. Developers can select the platform, architectures, and most technologies. This process enables software developers to start from the ground up.
绿地项目是指在任何企业开发新的软件应用程序。开发人员可以选择平台、体系结构和大多数技术。此过程使软件开发人员能够从头开始。
This enables a reduction in reps when it comes to the scoping/discovery process. Developers on behalf of a business can put an agile backlog in place with ease. This leads to the creation of an MVP: minimum viable product. This is a very important facility in technology. The developers then focus on creating new iterations to resolve testing issues. They can then plan for the launch of the software application.
这样可以减少范围界定/发现过程的代表。代表企业的开发人员可以轻松地将敏捷的积压工作安排到位。这导致了 MVP：最小可行产品的创建。这是技术中非常重要的设施。然后，开发人员专注于创建新的迭代以解决测试问题。然后，他们可以规划软件应用程序的启动。
Brownfield Project Software Development Summary
棕地项目软件开发摘要
Most brownfield projects start off with an end-to-end code audit. This is so developers recognize the basis of the application that they’re building. It helps to receive a report from the engineering and QA teams. Next, a vote review takes place. The brownfield developers can then figure out the future path of most projects. They’ll adjust the unfinished software until it is complete. Almost all brownfield projects focus on technologies already in play. Developers adjust the technologies until a required solution gets delivered. Here is an example of any business. They can salvage previous code and start from a certain project checkpoint. They then apply the code into an Agile process. Next thing you know- the incomplete software is now a functioning application.
大多数棕地项目都从端到端代码审计开始。这样，开发人员就可以认识到他们正在构建的应用程序的基础。它有助于接收来自工程和 QA 团队的报告。接下来，进行投票审查。然后，棕地开发商可以弄清楚大多数项目的未来路径。他们将调整未完成的软件，直到完成。几乎所有的棕地项目都侧重于已经发挥作用的技术。开发人员会调整技术，直到提供所需的解决方案。以下是任何企业的示例。他们可以挽救以前的代码并从某个项目检查点开始。然后，他们将代码应用到 Agile 流程中。接下来您知道 - 不完整的软件现在是一个正常运行的应用程序。
Greenfield vs Brownfield: Which Is Better for Software Development?
绿地 vs 棕地：哪个更适合软件开发？
Software is what fuels each service and product. That’s why choosing a software development process is so important. So, let’s get into greenfield vs brownfield. Here is the first notion to keep in mind. Greenfield software development carries risks.
软件是每项服务和产品的动力。这就是为什么选择软件开发流程如此重要的原因。那么，让我们来看看绿地与棕地。这是要记住的第一个概念。绿地软件开发存在风险。
That’s because developers have to start from scratch. This leads to agile approaches often serving as a winning approach. The greenfield approach takes longer than brownfield. This can lead to companies paying more money for greenfield development projects. This is fine if a business has tons of cash. But almost every business, of course, wants to conserve money.
这是因为开发人员必须从头开始。这导致敏捷方法通常是一种制胜方法。绿地方法比棕地方法需要更长的时间。这可能导致公司为绿地开发项目支付更多的钱。如果企业有大量现金，这很好。但当然，几乎每家企业都希望节省资金。
Brownfield projects often have a more stable infrastructure for business processes. This means Brownfield projects do not carry as many risks as greenfield projects. But a lot of brownfield development focuses on understanding current applications. This can sometimes prevent the value from getting delivered fast. Software experts recommend the iterative approach for brownfield projects.
棕地项目通常具有更稳定的业务流程基础设施。这意味着棕地项目不会像绿地项目那样带来那么多的风险。但是，许多棕地开发都侧重于了解当前的应用程序。这有时会阻止值快速交付。软件专家建议对棕地项目采用迭代方法。
This leads to refining architecture but also speeding up the development process. Plus, product quality can receive improvements.
这不仅优化了架构，也加快了开发过程。此外，产品质量还可以得到改进。
Here’s what it all comes down to. Neither approach is better or worse than the other. It depends on what a company wants to do. Would it prefer to create a new project from scratch? Or, would it prefer to boost the functional aspects of a current product?
归根结底是这样的。任何一种方法都没有比另一种更好或更差之分。这取决于公司想做什么。它是否更愿意从头开始创建新项目？或者，它更愿意提升当前产品的功能方面？
Only you and your staff can choose the right approach. (If you have trouble, check out our firm’s Plan Academy section.) One solution is to combine the two concepts into a “greenfield brownfield” project. Greenfield brownfield development projects have become more common in recent years. A greenfield brownfield project involves developers using some current processes. But they still apply many new processes and codes.
只有您和您的员工才能选择正确的方法。（如果您遇到问题，请查看我们公司的 Plan Academy 部分。一种解决方案是将这两个概念组合成一个 “绿地棕地” 项目。近年来，绿地棕地开发项目变得越来越普遍。绿地棕地项目涉及使用一些当前流程的开发人员。但他们仍然应用了许多新的流程和规范。
QC Testing
QC 测试
Understanding QC Testing
了解 QC 检测
QC testing is a central component of almost every software development process. Development procedures ensure that products are high-quality and ready for market. Three outcomes must take place once a software development process concludes.
QC 测试几乎是每个软件开发过程的核心组成部分。开发程序确保产品是高质量的并准备好进入市场。一旦软件开发过程结束，必须产生三种结果。
-
The product must meet the needs of the end-users.
产品必须满足最终用户的需求。
-
The product must address every customer requirement.
产品必须满足每个客户的要求。
-
The product should help all business goals get achieved.
该产品应有助于实现所有业务目标。
All three of these factors relate to the concept of quality. No matter the software product, quality matters more than anything else.
所有这三个因素都与质量概念有关。无论软件产品是什么，质量都比什么都重要。
Various techniques and methods must get applied to ensure the quality of software. This is where QC and QA testing come into play. Both of which contribute to ensuring that a company’s software delivers results. Are you ready to find out more about QC and QA testing? Let’s continue.
必须应用各种技术和方法来确保软件的质量。这就是 QC 和 QA 测试发挥作用的地方。这两者都有助于确保公司的软件交付结果。您准备好了解有关 QC 和 QA 测试的更多信息了吗？让我们继续。
The Basics of QC & QA Testing
QC & QA 测试的基础
The term QA stands for quality assurance. QC is an abbreviation for quality control. Both concepts connect to the notion of quality management. Sometimes QA testing and QC testing go hand-in-hand. But keep in mind that the two concepts have many differences.
QA 一词代表质量保证。QC 是 Quality Control 的缩写。这两个概念都与质量管理的概念有关。有时，QA 测试和 QC 测试是相辅相成的。但请记住，这两个概念有很多不同之处。
The mission of QA testing is to ensure that a requested quality can get achieved. QC testing focuses on enabling the requested quality to come to life. QA prevents software defects. Whereas, QC identifies the specific software defects.
QA 测试的任务是确保能够达到所要求的质量。QC 测试的重点是使所要求的质量成为现实。QA 可防止软件缺陷。而 QC 识别特定的软件缺陷。
What Is QC Testing?
什么是 QC 测试？
The QC testing process ensures that any piece of software is high-quality. A software project must meet certain processes, standards, and procedures. Otherwise, a development team cannot produce the required deliverables. (This applies to both internal and external deliverables.) So, what does a QC team do? It identifies software defects once a product gets developed. The recognition of defects takes place before the software gets released. The focus of QC is to both recognize and correct defects within software.
QC 测试过程确保任何软件都是高质量的。软件项目必须满足某些流程、标准和程序。否则，开发团队无法生成所需的可交付结果。（这适用于内部和外部可交付成果。那么，QC 团队是做什么的呢？一旦产品开发，它就会识别软件缺陷。缺陷的识别发生在软件发布之前。QC 的重点是识别和纠正软件中的缺陷。
What Is Quality Control Testing
什么是质量控制测试
QA testing focuses on ensuring that any software meets high-quality standards. QA testing helps assure companies that they use the right standards. This also applies to development procedures. The QA testing process also helps ensure that all procedures get executed well.
QA 测试的重点是确保任何软件都符合高质量标准。QA 测试有助于确保公司使用正确的标准。这也适用于开发过程。QA 测试过程还有助于确保所有程序都得到良好执行。
Your average QA team has two main tasks.
您的平均 QA 团队有两个主要任务。
-
Improving the development processes of software.
改进软件开发过程。
-
Improving the testing processes of software.
改进软件的测试过程。
Both tasks prevent defects from arising when a product goes through development.
这两项任务都可以防止在产品开发过程中出现缺陷。
What Is Software Testing?
什么是软件测试？
The software testing process is all about verification. Teams must verify the attributes of systems and many usage aspects. Why? To ensure that software operates the way that’s expected. Plus, software testers make sure that a product doesn’t have functions that it was never supposed to have. Software testing is a crucial aspect of QC. Testers use different techniques to detect issues involving the function of the software. Each software tester is on a mission to discover bugs. Plus, later on, the testers have to make sure that each bug got fixed.
软件测试过程完全是关于验证的。团队必须验证系统的属性和许多使用方面。为什么？确保软件按预期方式运行。此外，软件测试人员确保产品不具有它从未应该具有的功能。软件测试是 QC 的一个重要方面。测试人员使用不同的技术来检测涉及软件功能的问题。每个软件测试人员都肩负着发现错误的任务。此外，稍后，测试人员必须确保每个 bug 都得到修复。
What Is the Difference Between QC & QA in Testing?
在测试中，QC和QA有什么区别？
Try to visualize the following notion about the difference between QC and QA testing. The QA process ensures that an assembly line (when it comes to software development) works. Meanwhile, QC checks out the products that come off of the assembly line. The QC team then verifies that the products meet the specifications of the company. As you can infer, QA and QC are important when it comes to ensuring that a product is successful.
尝试可视化以下关于 QC 和 QA 测试之间差异的概念。QA 流程确保装配线（在软件开发方面）正常工作。同时，QC 检查从装配线上下来的产品。然后，QC 团队验证产品是否符合公司的规格。正如您可以推断的那样，在确保产品成功方面，QA 和 QC 非常重要。
The relationship between QA, QC, and other testing processes has a hierarchy.
QA、QC 和其他测试流程之间的关系具有层次结构。
QA sits at the very top of the pyramid. Why?
QA 位于金字塔的最顶端。为什么？
Because the goal of QA is to plan (and put in place) quality process evaluations.
因为 QA 的目标是规划（并实施）质量流程评估。
QC is in the middle of the pyramid. That’s because QC is about making QA processes come to life.
QC 位于金字塔的中间。这是因为 QC 是让 QA 流程栩栩如生。
This leads to QC testing. It’s how teams gather information about the quality of the software. Next, QC testers and other testers can go over the results of processes put in action. Other testers sit at the bottom of the pyramid.
这导致了 QC 测试。这是团队收集有关软件质量信息的方式。接下来，QC 测试人员和其他测试人员可以检查实施过程的结果。其他测试人员位于金字塔的底部。
What Comes First: QA or QC?
首先是 QA 还是 QC？
Quality control (QC) ensures that organizations discover software defects. The defects can then get corrected before going to market. Quality assurance (QA) is more of a proactive process. QA work begins before work on the deliverable itself starts. This means that QC is much more of a reactive process than QA. QC activity starts whenever a software development team begins a project.
质量控制 （QC） 确保组织发现软件缺陷。然后可以在进入市场之前纠正缺陷。质量保证 （QA） 更像是一个主动的过程。QA 工作在交付物本身的工作开始之前开始。这意味着 QC 更像是一个被动的过程，而不是 QA。每当软件开发团队开始一个项目时，QC 活动就会开始。
Which Is Best: QA or QC?
哪个最好：QA 还是 QC？
QA and QC have equal importance when it comes to the software development process. QA focuses on preventing bugs, issues, and defects that can affect a system. That is why QA is a function of a software company’s management team. Instead of prevention, QC encompasses recognizing the bugs, issues, and defects. Next, the QC team tries to fix them.
在软件开发过程中，QA 和 QC 同等重要。QA 侧重于防止可能影响系统的 bug、问题和缺陷。这就是为什么 QA 是软件公司管理团队的一项职能。QC 不是预防，而是包括识别错误、问题和缺陷。接下来，QC 团队尝试修复它们。
That’s why QC is more of a corrective software concept than QA. You need both QA and QC to ensure that you have a successful product. When used together, they help software teams deliver high-quality results to customers.
这就是为什么 QC 更像是一个纠正性软件概念，而不是 QA。您需要 QA 和 QC 以确保您拥有成功的产品。当一起使用时，它们可以帮助软件团队向客户提供高质量的结果。
What Are QA Tools?
什么是 QA 工具？
Quality assurance (QA) tools are for ISO-compliant/regulated companies. The tools help simplify and boost software quality processes. QA tools can assist companies in managing their quality procedures. All QA tools are digital. The digital tools specialize in streamlining deviations. They also focus on CAPAs. CAPA stands for corrective and preventive actions.
质量保证 （QA） 工具适用于符合 ISO 标准/受监管的公司。这些工具有助于简化和提高软件质量流程。QA 工具可以帮助公司管理其质量程序。所有 QA 工具都是数字化的。数字工具专门用于简化偏差。他们还专注于 CAPA。CAPA 代表纠正和预防措施。
QA Testing vs. QC Testing: A Comparison
QA 测试与 QC 测试：比较
Let’s go over ten key differences between QA testing and QC testing.
让我们来看看 QA 测试和 QC 测试之间的十个主要区别。
-
QA focuses on preventing defects. QC focuses on recognizing and fixing defects.
QA 侧重于防止缺陷。QC 侧重于识别和修复缺陷。
-
QA has a reputation for serving as a preventive technique. Whereas, QC serves as a corrective technique.
QA 以作为一种预防技术而闻名。而 QC 是一种纠正技术。
-
QA testing defines procedures and standards that relate to customer requirements. QC testing helps ensure that those procedures and standards get followed by developers.
QA 测试定义了与客户要求相关的程序和标准。QC 测试有助于确保开发人员遵循这些程序和标准。
-
QA testing focuses on building new or expansive processes. QC testing focuses on improving current or existing processes.
QA 测试侧重于构建新的或扩展的流程。QC 测试侧重于改进当前或现有流程。
-
QA serves as a software management tool. Whereas, QC is a corrective tool for software.
QA 用作软件管理工具。而 QC 是软件的纠正工具。
-
QA testing is the responsibility of the entire project team. QC testing is the duty of only the actual testing team.
QA 测试是整个项目团队的责任。QC 测试只是实际测试团队的职责。
-
QA focuses on verification. But the focus of QC is validation.
QA 侧重于验证。但 QC 的重点是验证。
-
QA testing is process-oriented. QC testing is product oriented.
QA 测试是面向过程的。QC 测试以产品为导向。
-
QA does not involve executing a code or program. Yet, QC testers get involved with executing codes and programs.
QA 不涉及执行代码或程序。然而，QC 测试人员参与执行代码和程序。
-
QA testing takes place before Quality Control processes come into play. QC testing only happens once Quality Assurance processes are complete.
QA 测试在质量控制流程开始发挥作用之前进行。只有在质量保证流程完成后，才会进行 QC 测试。
QA & QC Tests Improve the Quality of Software Products
QA 和 QC 测试提高了软件产品的质量
Some software developers make one crucial mistake. They choose to not invest enough time in the testing phase. Developers feel that testing increases development time. Sure, that can happen. But it doesn’t take place as often as many companies assume. Software testing can seem like a challenge. But it’s important. Testing helps ensure that products are reliable and meet high-quality standards even if cybersecurity is envolved.
一些软件开发人员犯了一个严重的错误。他们选择不在测试阶段投入足够的时间。开发人员认为测试会增加开发时间。当然，这可能会发生。但它并不像许多公司想象的那样频繁发生。软件测试似乎是一项挑战。但这很重要。测试有助于确保产品可靠并符合高质量标准，即使涉及网络安全也是如此。
The two most efficient ways to boost quality in a product is to conduct both QA and QC testing. QA testing will verify that processes are getting followed in the correct manner. QC testing can ensure that defined quality standards get exceeded.
提高产品质量的两种最有效方法是同时进行 QA 和 QC 测试。QA 测试将验证流程是否以正确的方式得到遵循。QC 测试可以确保超过规定的质量标准。
This applies to all sorts of software development techniques, methods, and approaches. As a result of testing, businesses end up saving both time and money. Plus, they discover new ways to gain competitive advantages over other companies.
这适用于各种软件开发技术、方法和途径。作为测试的结果，企业最终节省了时间和金钱。此外，他们还发现了获得优于其他公司竞争优势的新方法。
via：
-
Greenfield vs Brownfield - John Adams IT
https://www.johnadamsit.com/software-development-greenfield-vs-brownfield/
-
QC Testing - John Adams IT
-
Brownfield vs. Greenfield Development: What’s the Difference? | Synoptek
https://synoptek.com/insights/it-blogs/greenfield-vs-brownfield-software-development/
-
Greenfield vs. Brownfield Data Centers | Pure Storage Blog
https://blog.purestorage.com/purely-educational/greenfield-vs-brownfield-data-centers/