Exercise 30. Translate words and word combinations. Memorize them.

To be divided into sub-disciplines; software requirements; analysis and specification; validation of requirements; to use the standards for; software development; software testing; software maintenance; to need enhancements for; to be first completed; this subfield deals with; software configuration management; such as versioning and source control; to be managed in a standardized way; software engineering management; to borrow heavily from the field of; encounter in; to be hotly debated; among practitioners; with the main paradigms; to be agile or waterfall; software engineering tools; software quality; to be considered; the foundations of.

Exercise 31. Answer the following questions.

1. How many sub-disciplines can software engineering be divided into?

2. What are they?

3. Is the design of software usually done with Computer-Aided Software Engineering (CASE) tools?

4. What does the design use?

5. Software systems often have problems, don’t they?

6. What do software systems need?

7. What does the management of software systems borrow?

8. What is hotly debated among practitioners with the main paradigms?

9. Software engineering is related to the disciplines of computer science, isn’t it?

10. What is software engineering considered to be?

11. Many of the foundations of software engineering come from different universities, don’t they?

12. What does it borrow from the field of project management?

13. Who has been dealing with the complexity of large systems for many decades?

14. What is applied to many software engineering problems?

Exercise 32. Say whether the following statements are true or false. Correct the false ones.

1. Software can be divided into ten sub-disciplines. 2. Software requirements mean the analysis, specification, and validation of requirements for hardware. 3. The design of software is seldom done with Computer-Aided Software Engineering (CASE) tools and use standards for the format, such as the Unified Modeling Language (UML). 4. Software systems often have problems and need enhancements for a long time after they are first written. 5. Since software systems are very simple, their configuration has to be managed in a standardized and structured method. 6. The management of software systems borrows heavily from management. 7. There are nuances encountered in software not seen in other management sciences. 8. The process of building software is hotly debated among practitioners with the main paradigms being agile or waterfall. 9. Software engineering is related to the many disciplines. 10. Many of the foundations of software engineering come from computer virus. 11. The building of a software system is usually considered a project and the management of it borrows many principles from the field of project management. 12. Systems engineers have been dealing with the complexity of large systems.

Exercise 33. Be ready to retell the text (ex.29)

Exercise 34. Memorize the following words and word combinations.

aspect – аспект (властивість, за якою група даних об’єднується в інформаційно-пошукові системи)

quality attributes – якісні характеристики, атрибути

boilerplate code – заготовки програмного коду, які розробляються програмістами-майстрами

design general-purpose code – код загального призначення

generative programming – програмування на базі попередніх знань

template - шаблон

agile software development – гнучка розробка ПЗ (яка забезпечує простоту внесення змін)

proponent – прихильник, той хто пропонує

fade in importance – втрачати важливість

Extreme Programming – екстремальне програмування (одна з методологій розробки ПЗ)

Scrum – методологія управління проектами для розробки ПЗ

Lean software development – розробка «бережливого» ПЗ

Model Driven Design (Architecture) – модельно-орієнтований підхід до розробки ПЗ

Software Product Lines – лінія продуктів ПЗ (продукти, які доповнюють один одного)

succession – послідовність, безперервний ряд

editor-in-chief – головний редактор

entity-relationship modeling – модель «сутність-звязок»

modular programming – модульність (в програмуванні)

Exercise 35. Read and translate the text.

Дата добавления: 2015-08-27