- •English for
- •Contents
- •Inside a component………………………………………….……...56
- •Theme 1. Doing a degree.
- •University of Birmingham Electronic and Computer Engineering Masters/mSc with Industrial Studies
- •International students
- •Theme 2. Most famous.
- •Gauss’s law
- •1. Introduction
- •2. Gauss's Law
- •Figure 1. Electric flux through surface area a.
- •Example 1: Field of point charge.
- •Figure 2. Electric field generated by point charge q.
- •Example 2: Problem 16
- •Figure 3. Problem 16.
- •3. Conductors in Electric Fields
- •Figure 4. Electric field of conductor.
- •Theme 3. Microprocessors.
- •25 Microchips that shook the world
- •Intersil icl8038 Waveform Generator (circa 1983*)
- •Ibm Deep Blue 2 Chess Chip (1997)
- •Intel 8088 Microprocessor (1979)
- •Xilinx xc2064 fpga (1985)
- •Microprocessors
- •Theme 4. Nanotechnology.
- •Nanotechnology
- •Huge Potential of nanotechnology in medicine
- •Theme 5. Inside a component.
- •Graphene tunnel barrier makes its debut
- •New Route to Electronics Inside Optical Fibers
- •Theme 6. Holography.
- •Check how many correct answers you can give.
- •Touchable hologram: is it real?
- •Holograms and Photographs
- •In an instant, however, view point of, whereas, in order to, no matter,
- •In addition, regardless of, unfortunately.
- •Theme 7. Operating systems.
- •Computer software or just software
- •Operating systems
- •Theme 8. Microprocessor concepts.
- •Microprocessor
- •Multicore designs
- •Theme 9. Robots.
- •Types of robots
- •Different Types of Robots
- •Industrial Robots
- •Theme 10. Network basics.
- •Network basics
- •All about Broadband/ics Routers
- •Notes to the text
- •Theme 11. Telecommunication network.
- •What is a telecommunications network?
- •Lan vs. Wan Comparison - Difference between lan and wan
- •Theme 12. The future of work. Lead-in
- •Gen y-ers bring their distinct style of communicating to the job
- •Specialized Reading
- •Working at home vs. The office: The face time faceoff
- •Listening
- •07.36 – 09.02
- •09.02 – 10.08
- •10.09 – 11.00
- •11.01 – 11.37
- •"No Silver Bullet"
- •Specialized Reading
- •Why is software engineering so hard?
- •9. The Size of Accidental
- •10. Obtaining the Increase
- •Listening
- •Speaking
- •Theme 14. Management.
- •Theme 15. E-commerce.
- •Theme 17. Banks.
- •How to … functions
- •Positive sentence
- •Negative sentence
- •Question
- •Infinitive.
- •4. How can you make it perfect?
- •10)Emulate excellent speakers (find their talks on the Internet or visit live talks).
- •Function 17. How to deal with Neologisms
- •6. Cловосложение:
- •Grammar minimums Grammar Minimum I Present Simple and Present Continuous
- •Grammar Minimum 2 Past Simple and Present Perfect
- •Edinburgh.
- •Grammar Minimum 3 Present Simple Passive and Past Simple Passive
- •Future Simple and “be going to”
- •Reported Speech
- •Grammar minimum 6 Conditional Sentences
- •English Tenses: Active Voice.
- •English Tenses: Passive Voice.
- •The list of Irregular Verbs
- •Infinitive Past Simple Past Participle Перевод
Specialized Reading
Task 1. Read the words and phrases. Give the Russian equivalents.
within a decade improvement in reliability divide the problems into two categories the problems facing software engineering the production of software improve software development reduce accidental problems to zero solve some problems the process of software development |
complexity conformity changeability invisibility high-level languages time-sharing to clarify requirements deadline target a 10 times improvement in smth |
Task 2. Read and translate the extract from lecture. What is lecture goal? What are the main ideas?
Why is software engineering so hard?
Thesis of Fred Brook’s “No Silver Bullet”. Kenneth M. Anderson, University of Colorado, Lecture 2
1. Lecture Goals
Introduce thesis of Fred Brook’s “No Silver Bullet”
Classic essay by Fred Brooks discussing “Why is SE so hard?”
2. No Silver Bullet
“There is no single development, in either technology or management technique, which by itself promises even one order-of-magnitude improvement within a decade in productivity, in reliability, in simplicity.” — Fred Brooks, 1986
i.e. There is no magical cure for the “software crisis”.
3. Why? Essence and Accidents
Brooks divides the problems facing software engineering into two categories:
essence: difficulties inherent in the nature of software;
accidents: difficulties related to the production of software;
Brooks argues that most techniques attack the accidents of software engineering.
4. An Order of Magnitude
In order to improve software development by a factor of 10:
first, the accidents of software engineering would have to account for 90% of the overall effort;
second, tools would have to reduce accidental problems to zero.
Brooks doesn't believe that the former is true…
and the latter is nigh impossible because each new tool or technique solves some problems while introducing others.
5. The Essence
Brooks divides the essence into four subcategories: complexity, conformity, сhangeability, invisibility.
6. What about “X”?
Brooks argues that past breakthroughs solve accidental difficulties: High-level languages, Time-Sharing, Programming Environments, OO Programming, Design…
7. Promising Attacks on the Essence
Buy vs. Build
Don't develop software when you can avoid it.
Rapid Prototyping
Use to clarify requirements.
Incremental Development
Don't build software, grow it.
Great designers
Be on the look out for them, when you find them, don't let go!
8. No Silver Bullet, Take 2
Brooks reflects on No Silver Bullet, ten years later.
- Lots of people have argued that their methodology, technique, or tool is the silver bullet for software engineering. If so, they didn't meet the deadline of 10 years or the target of a 10 times improvement in the production of software;
- Others misunderstood what Brooks calls “obscure writing”
e.g. “accidental” did not mean “occurring by chance”; instead, he meant that the use of technique A for benefit B unfortunately introduced problem C into the process of software development.