DPTASM 12: How about a very large organization?
In case of a very large organization:
It may be the case that your organization is really huge or it becomes so, over time. Then, it may really become very difficult to work with just one instance of Test Automation Common Infrastructure (TACI) and one Test Automation Development and Engineering Team. In that case, you may establish multiple instances of those (Test Automation Common Infrastructure (TACI) and Test Automation Development and Engineering Team). And, each instance may serve a logical segment/unit/portion of the huge organization.
DPM’s Productized Test Automation Service Model (DPTASM) is applicable in case of very large organization that has a very large number of Project and Product Teams that need to use Test Automation Service. Let’s consider this hypothetical example the practical side of which you are encouraged to take a look at.
Example: The organization in question has 500 Project and Product Teams that need to use Test Automation Service in testing around 500 Software Applications or Products. Each of the 500 Applications under Test (AUT or SUT) was built primarily with one of the 10 popular technologies (or with a combination of couple of those technologies).
In this case, it would be prudent to establish multiple Test Automation Development and Engineering Teams and instances of Test Automation Common Infrastructure (TACI). And, each of those (Team and Infrastructure Combination) may cater to the Test Automation needs of all the Software Products and Applications built primarily with a specific technology (or a couple of technologies).
In this case, the organization may end up with 10 Test Automation Development and Engineering Teams each of which is tightly coupled with its respective instance of Test Automation Common Infrastructure (TACI). And, the organization can still realize all the benefits offered by DPM’s Productized Test Automation Service Model! Next Page >>
It may be the case that your organization is really huge or it becomes so, over time. Then, it may really become very difficult to work with just one instance of Test Automation Common Infrastructure (TACI) and one Test Automation Development and Engineering Team. In that case, you may establish multiple instances of those (Test Automation Common Infrastructure (TACI) and Test Automation Development and Engineering Team). And, each instance may serve a logical segment/unit/portion of the huge organization.
DPM’s Productized Test Automation Service Model (DPTASM) is applicable in case of very large organization that has a very large number of Project and Product Teams that need to use Test Automation Service. Let’s consider this hypothetical example the practical side of which you are encouraged to take a look at.
Example: The organization in question has 500 Project and Product Teams that need to use Test Automation Service in testing around 500 Software Applications or Products. Each of the 500 Applications under Test (AUT or SUT) was built primarily with one of the 10 popular technologies (or with a combination of couple of those technologies).
In this case, it would be prudent to establish multiple Test Automation Development and Engineering Teams and instances of Test Automation Common Infrastructure (TACI). And, each of those (Team and Infrastructure Combination) may cater to the Test Automation needs of all the Software Products and Applications built primarily with a specific technology (or a couple of technologies).
In this case, the organization may end up with 10 Test Automation Development and Engineering Teams each of which is tightly coupled with its respective instance of Test Automation Common Infrastructure (TACI). And, the organization can still realize all the benefits offered by DPM’s Productized Test Automation Service Model! Next Page >>
Comments
Post a Comment