3.9 Прочитай, переведи текст suitability of the term и ответь на вопросы:

1. What did David Parnas do?

2. What did Steve McConnell do?

3. What do people think hearing about software development?

4. What did Donald Knuth do?

5. What did Edsger W. Dijkstra say?

Many people believe that software engineering implies a certain level of academic training, professional discipline, adherence to formal processes, and especially legal liability that often are not applied in cases of software development. A common analogy is that working in construction does not make one a civil engineer, and so writing code does not make one a software engineer. Furthermore, because computing doesn't utilizes the methods of mathematical physics common to all conventional engineering disciplines it's more appropriate to call those engaged in this occupation as software developers, computer scientists or similar.

In 1978, a prominent computing scientist, E. W. Dijkstra, wrote in a paper that the coining of the term software engineer was not useful since it was an inappropriate analogy, "The existence of the mere term has been the base of a number of extremely shallow—and false—analogies, which just confuse the issue...Computers are such exceptional gadgets that there is good reason to assume that most analogies with other disciplines are too shallow to be of any positive value, are even so shallow that they are only confusing.

In each of the last few decades, at least one radical new approach has entered the mainstream of software development (e.g. Structured Programming, Object Orientation), implying that the field is still changing too rapidly to be considered an engineering discipline. Proponents argue that the supposedly radical new approaches are evolutionary rather than revolutionary.

Individual commentators have disagreed sharply on how to define software engineering or its legitimacy as an engineering discipline. David Parnas has said that software engineering is, in fact, a form of engineering. Steve McConnell has said that it is not, but that it should be. Donald Knuth has said that programming is an art and a science. Edsger W. Dijkstra claimed that the terms software engineering and software engineer have been misused and should be considered harmful, particularly in the United States.

3.10 Прочитай, переведи текст subdisciplines и сопоставь словосочетания к каждому из предложений:

1. Software design,

2. Requirements engineering,

3. Software construction,

4. Software maintenance,

5. Software testing,

6. Software engineering management,

7. Software engineering process,

8. Software configuration management,

9. Software engineering tools and methods,

10. Software quality management.

Software engineering can be divided into ten subdisciplines. They are:

1. … : The elicitation, analysis, specification, and validation of requirements for software.

2. … : The process of defining the architecture, components, interfaces, and other characteristics of a system or component. It is also defined as the result of that process.

3. … : The detailed creation of working, meaningful software through a combination of coding, verification, unit testing, integration testing, and debugging.

4. … : The dynamic verification of the behavior of a program on a finite set of test cases, suitably selected from the usually infinite executions domain, against the expected behavior.

5. … : The totality of activities required to provide cost-effective support to software.

6. … : The identification of the configuration of a system at distinct points in time for the purpose of systematically controlling changes to the configuration, and maintaining the integrity and traceability of the configuration throughout the system life cycle.

7. … : The application of management activities—planning, coordinating, measuring, monitoring, controlling, and reporting—to ensure that the development and maintenance of software is systematic, disciplined, and quantified.

8. … : The definition, implementation, assessment, measurement, management, change, and improvement of the software life cycle process itself.

9. … : The computer-based tools that are intended to assist the software life cycle processes (see Computer-aided software engineering) and the methods which impose structure on the software engineering activity with the goal of making the activity systematic and ultimately more likely to be successful.

… : The degree to which a set of inherent characteristics fulfills requirements.

THERE IS/THERE ARE

Оборот there is / there are служит для выражения наличия (отсутствия) какого-либо предмета в опреде­ленном месте или в определенное время. Перевод пред­ложения с таким оборотом нужно начинать с обстоя­тельства места, а если его нет, то со сказуемого.

Present Indefinite

There is a picture on the wall. На стене картина.

Is there a picture on the wall? На стене есть картина?

There are pictures on the wall. На стене картины.

Are there pictures on the wall? На стене есть картины?

Past Indefinite

There was a picture on the wall. На стене была кар­тина.

Was there a picture on the wall? На стене была кар­тина?

There were pictures on the wall. На стене были кар­тины.

Were there pictures on the wall? На стене были кар­тины?

There will be pictures on the wall. На стене будут картины.

Will there be pictures on the wall? На стене будут картины?

Выбор формы глагола to be зависит от числа суще­ствительного, следующего сразу за ним:

There is a chair and two armchairs in the room.

There are two armchairs and a chair in the room.

Вопросительные предложения с оборотом there is / there are строятся следующим образом

Общий вопрос: Is there anything in the bag? Will there be lessons tomorrow?

Специальный вопрос: What is there in the bag?

Разделительный вопрос. There are some pupils in the classroom, aren’t there?