Post by habiba123820 on Nov 5, 2024 8:30:55 GMT
Before we answer this question, let’**CENSORED** address the paradigm divide that exists within the question: the process-first paradigm versus the software-first paradigm . Each different paradigm will result in different answers and justifications for those answers. Let’**CENSORED** start by defining these paradigms.
The process-first paradigm
The process-first paradigm considers the process as something relatively immutable. The search is for a technology stack that best fits the process. The process is usually broken down into smaller components and each component is then mapped to a type of software.
In the process-first approach, people in Localization often start by listing their process as their requirements. But this process-first approach also has a big divide: people who are just starting wordpress web design agency to build their technology stack from scratch and people who already have systems for many of their processes in place.
Let’**CENSORED** start by looking at people who are building from scratch, assuming they have at least one computer-assisted translation (CAT) tool at their disposal. So, for example, let’**CENSORED** start with this process as an example:
Applicants make request by email
Project Managers meet with stakeholders to discuss requirements
Project Managers prepare assets for quotation
Project managers load assets into the CAT tool
Project Managers download the log file and generate a quote based on the log file
Interested parties approve the budget
Project Managers prepare assets and send files, translation memory and glossary kit to translators
Translators complete the task in their own computer-assisted translation (CAT) tools
Translators send the files back to the Project Managers
Project Managers evaluate assets
Project Managers deliver assets back to stakeholders
It is common for people to divide their process into categories: business management, translation management, accounting, communication, quality management, connectors . In this context, the CAT tool is the fundamental software component in any technology stack. Without it, you will not be able to leverage knowledge in the form of translation memory and terminology bases.
The software-first paradigm
The software-first paradigm looks at the different software available on the market first and then tries to build an effective process that leverages what each software does. The other components of the technology stack are typically added to the CAT tool. A major upgrade, for example, would be to add a business management system like Plunet or XTRF to track the different receivables and payments in each project, as well as the project status, ownership, suppliers, etc. Then you might consider adding a quality management software like Content-quo, you might use an intermediary software to integrate your connectors, add an accounting software like Xero or Quickbooks, and voila! You’re done. Literally done. Now you have a technology stack, but the question remains: what is the simplest and most effective way to manage your translations in a predictable way? With all these different software you’re considering.
The process-first paradigm
The process-first paradigm considers the process as something relatively immutable. The search is for a technology stack that best fits the process. The process is usually broken down into smaller components and each component is then mapped to a type of software.
In the process-first approach, people in Localization often start by listing their process as their requirements. But this process-first approach also has a big divide: people who are just starting wordpress web design agency to build their technology stack from scratch and people who already have systems for many of their processes in place.
Let’**CENSORED** start by looking at people who are building from scratch, assuming they have at least one computer-assisted translation (CAT) tool at their disposal. So, for example, let’**CENSORED** start with this process as an example:
Applicants make request by email
Project Managers meet with stakeholders to discuss requirements
Project Managers prepare assets for quotation
Project managers load assets into the CAT tool
Project Managers download the log file and generate a quote based on the log file
Interested parties approve the budget
Project Managers prepare assets and send files, translation memory and glossary kit to translators
Translators complete the task in their own computer-assisted translation (CAT) tools
Translators send the files back to the Project Managers
Project Managers evaluate assets
Project Managers deliver assets back to stakeholders
It is common for people to divide their process into categories: business management, translation management, accounting, communication, quality management, connectors . In this context, the CAT tool is the fundamental software component in any technology stack. Without it, you will not be able to leverage knowledge in the form of translation memory and terminology bases.
The software-first paradigm
The software-first paradigm looks at the different software available on the market first and then tries to build an effective process that leverages what each software does. The other components of the technology stack are typically added to the CAT tool. A major upgrade, for example, would be to add a business management system like Plunet or XTRF to track the different receivables and payments in each project, as well as the project status, ownership, suppliers, etc. Then you might consider adding a quality management software like Content-quo, you might use an intermediary software to integrate your connectors, add an accounting software like Xero or Quickbooks, and voila! You’re done. Literally done. Now you have a technology stack, but the question remains: what is the simplest and most effective way to manage your translations in a predictable way? With all these different software you’re considering.