5.18. Technical and professional English III (Elective)

5.18. Technical and professional English III (Elective)

Figure 5.18: Connection Map. BEI201 Technical and professional English III

5.18.1. Justification ↑ Back to top

At this level, students engage with English as the primary medium for accessing and producing technical content in computing, engineering, and the sciences. Grammar structures are applied to reading scientific articles, writing technical reports, describing engineering processes, and participating in professional discussions. The course bridges everyday English fluency with the demands of technical communication.

5.18.2. Generales Goals ↑ Back to top

  1. Train students to read, understand, and produce technical communication in English.
  2. Provide linguistic tools for connecting ideas in descriptive and analytical writing about computing and engineering.

5.18.3. Contribution to Outcomes ↑ Back to top

AG-C04) Communication: Communicates effectively in complex computing activities. (Usage)
AG-C03) Individual and Team Work: Performs effectively as an individual and as a member or leader in diverse teams. (Familiarity)

5.18.4. Content ↑ Back to top

5.18.4.1. Technical Communication (12 hours) [Skills AG-C03,AG-C04] ↑ Back to top

Bibliography: (Soars and John, 2002b; Cambridge, 2006; MacGrew, 1999)

Topics

  1. Review of Tenses: Present, Past, and Future in technical documentation.
  2. Interrogative sentences with complex Wh- questions for system analysis.
  3. Words with more than one meaning in technical contexts (Polysemy).
  4. Expressions for describing professional activities and research interests.

Learning Outcomes

  1. By the end of the unit, students use various tenses to exchange detailed technical information and formulate precise questions about computing systems and engineering processes.
5.18.4.2. Comparing Architectures (12 hours) [Skills AG-C03,AG-C04] ↑ Back to top

Bibliography: (Soars and John, 2002b; Cambridge, 2006; MacGrew, 1999)

Topics

  1. Use of "What's it like?": Describing system characteristics and interfaces.
  2. Advanced comparative and superlative adjectives in benchmark analysis.
  3. Collocations in computing: high-performance, low-level, fault-tolerant.
  4. Reading: Architecture comparison reports (RISC vs. CISC, SQL vs. NoSQL).

Learning Outcomes

  1. Students analyze and describe differences between computing architectures, frameworks, and systems using varied comparative structures with technical precision.
5.18.4.3. Then and Now in Computing (12 hours) [Skills AG-C03,AG-C04] ↑ Back to top

Bibliography: (Soars and John, 2002b; Cambridge, 2006; MacGrew, 1999)

Topics

  1. Present Perfect vs. Simple Past: Contrasting historic events with current state.
  2. Time expressions: for, since, ever, never applied to technology evolution.
  3. Adverbs of time and manner in scientific narrative.
  4. Vocabulary: Generations of technology, legacy systems, current platforms.

Learning Outcomes

  1. Students differentiate and correctly apply the present perfect and the simple past to narrate the evolution of computing technologies and contrast historical achievements with the current state of the field.
5.18.4.4. Engineering Standards and Protocols (12 hours) [Skills AG-C03,AG-C04] ↑ Back to top

Bibliography: (Soars and John, 2002b; Cambridge, 2006; MacGrew, 1999)

Topics

  1. Modals of obligation and permission: Have to, Must, Can in professional norms.
  2. Giving technical recommendations: Should, Ought to — code reviews and design.
  3. Vocabulary: IEEE/ACM standards, coding conventions, security policies.
  4. Formal writing: Technical memos and engineering recommendations.

Learning Outcomes

  1. Students express engineering rules, standards, and professional recommendations using appropriate modal verbs in formal technical writing and peer discussion.
5.18.4.5. How Systems Are Built (12 hours) [Skills AG-C03,AG-C04] ↑ Back to top

Bibliography: (Soars and John, 2002b; Cambridge, 2006; MacGrew, 1999)

Topics

  1. Passive Voice: Present and Simple Past to describe engineering processes.
  2. Vocabulary: Manufacturing, deployment, integration, and testing.
  3. Expressions for giving technical opinions and discussing design trade-offs.
  4. Writing: Process description for a software or hardware system.

Learning Outcomes

  1. Students use the passive voice to describe how systems are designed, built, tested, and deployed, participating in technical discussions about engineering processes.
5.18.4.6. Debugging and Analysis (12 hours) [Skills AG-C03,AG-C04] ↑ Back to top

Bibliography: (Soars and John, 2002b; Cambridge, 2006; MacGrew, 1999)

Topics

  1. Past Continuous vs. Simple Past in incident and failure reports.
  2. Narrative and sequence connectors: while, when, suddenly, as a result.
  3. Vocabulary: Bugs, exceptions, crashes, logs, root cause analysis.
  4. Writing: Incident report for a software or network failure.

Learning Outcomes

  1. Students narrate debugging sessions, system failures, and experimental incidents using narrative tenses and technical sequencing connectors fluently.
5.18.4.7. Research and Innovation (12 hours) [Skills AG-C03,AG-C04] ↑ Back to top

Bibliography: (Soars and John, 2002b; Cambridge, 2006; MacGrew, 1999)

Topics

  1. Future Forms: Will, Going to, Present Continuous for research projection.
  2. Expressions of probability and certainty in scientific contexts.
  3. Vocabulary: Innovation cycles, research proposals, technology forecasting.
  4. Oral presentations: "The future of computing in my field".

Learning Outcomes

  1. Students project research goals and discuss future directions in computing and engineering using various future structures with appropriate degrees of certainty.
5.18.4.8. Technical English III (12 hours) [Skills AG-C03,AG-C04] ↑ Back to top

Bibliography: (Soars and John, 2002b; Cambridge, 2006; MacGrew, 1999)

Topics

  1. Programming and Web Development terminology: functions, APIs, frameworks.
  2. User Interface (UI/UX) descriptions and usability concepts.
  3. Basic project management vocabulary: sprints, milestones, deliverables.
  4. Writing: Simple technical specification or README document.

Learning Outcomes

  1. By the end of the course, students use specialized software development vocabulary to describe logical and functional components and produce basic technical documentation in English.

5.18.5. Bibliography ↑ Back to top

Soars, L. and John (2002b). American Headway N 2 Student Book. Editorial Oxford.

Cambridge (2006). Diccionario Inglés-Espanol Cambridge. Editorial Oxford.

MacGrew, J. (1999). Focus on Grammar Basic. Editorial Oxford.

Spotted a typo, an outdated course, a broken link, or have a suggestion? Let us know.

Scan to open on your phone