10.1 Убери лишнее слово:

1. judgement, violation, opinion, belief, view, mind;

2. boot, target, object, objective, goal, aim;

3. approximation, approach(ing), fit, fitting, bringing/drawing near, elaborate;

4. inaccuracy, insulate, inexactitude, imprecision, ambiguity, uncertainty;

5. conflate, integrate, yield, merge, bind, combine, integrate, unite, join together;

6. method, tactic, line, mode, approach, template, procedure, technique;

7. confirmation, variation, permutation, transformation, change, version;

8. fill out, pad, expand, embellish, sustain;

9. reject, cast off, discard, restrict, abandon, dispose of;

10. pivotal, essential, key, sufficient, crucial, fundamental, cen­tral;

10.2 Прочитай, переведи текст software architect и ответь на вопросы:

1. What is the main task of software architect?

2. What aspect of the looks software architect in the construction of the system?

3. A technical standard which selects a software architect?

4. What can focus on what the software architect?

5. What can use the software architects?

A software architect will make the overall design (the structure) and plan (technical and operational) for a system that is to be built making sure that every aspect is covered such as security, performance, manageability and so on with the goal to build a solid system as they have significant insight into the requirements and constraints for this system from the business, users and investors. The role of software architect generally has certain common traits: 

Architects makes high-level design choices much more often than low-level choices. In addition, the architect may sometimes dictate technical standards, including coding standards, tools, or platforms. Software architects may also be engaged in the design of the architecture of the hardware environment, or may focus entirely on the design methodology of the code.

Architects can use various software architectural models that specialize in communicating architecture.

10.3 Прочитай, переведи текст quality assurance и замени выделенные словосочетания в тексте:

1. successful,

2. introduction,

3. leadership,

4. enough,

5. important,

6. continuous,

7. source code.

8. Implement

9. strongly.

Even with the best architecture and 1) (руководством) in the world, poor delivery can cause an otherwise 2) (успешный) project to fail. Quality assurance is a large part of an architect's role, but it's more than just doing code reviews. For example, you need a baseline to assure against, and this means the 3) (введение) of standards and working practices. From a software development perspective, these could include coding standards, design principles and 4) (исходный код) analysis tools through to the use of 5) (непрерывной) integration, automated unit testing and code coverage tools. It's safe to say that most projects don't do enough quality assurance, and therefore you need to figure out what's 6) (важный) and make sure that it's 7) (достаточно) assured. The important parts of a project are anything that is architecturally significant, business critical, complex or 8) (сильно) visible. You just need to be pragmatic and 9) (реализовать) that you can't necessarily assure everything, doing something rather than doing nothing.