Computer World. Матросова Т.А. - 45 стр.

UptoLike

ВУЗ: 

УлГТУ | Ульяновск

Составители: 

Рубрика: 

44
your application. Sequence diagrams are closely related to collaboration diagrams.
While the collaboration diagram's main focus is to show how objects are associated
with each other, sequence diagrams show the time ordering of messages between
objects.
Why use Sequence Diagrams?
Unless you are using business objects in your applications, you won't have much
need for sequence diagrams. This is because if you're not using business objects,
most of your application logic resides inside methods of user interface objects or in
functions and procedures–and there really isn't much messaging that occurs between
objects. However, once you decide to elevate your programming by using business
objects in your applications, sequence diagrams help you answer two very important
questions:
1. Which objects should be assigned a particular responsibility?
2. In what order should messages pass between objects?
These questions are very difficult to answer correctly when you simply try to
envision object messaging in your head. In contrast, when you document your
thought process in a sequence diagram, suddenly the answers to these questions
become crystal clear. At a higher level, it also helps you comprehend the overall flow
of a particular process. In addition, sequence diagrams help you easily identify
unnecessary messages between objects and factor them out. You may also discover
that objects you originally thought should be involved in a particular process
shouldn't be involved at all!
TEXT 7
Translate the text in written form.
In our competitive and dynamic world, businesses require quality software
systems that meet current needs and are easily adapted. These requirements are best
met by modeling business rules at a very high level, where they can be easily
validated with clients, and then automatically transformed to the implementation
level. The Unified Modeling Language (UML) is becoming widely used for both
database and software modeling, and version 1.1 was adopted in November 1997 by
the Object Management Group (OMG) as a standard language for object-oriented
analys is and design. Initially based on a combination of OMT (Object Modeling
Technique) and OOSE (Object-Oriented Software Engineering) methods, UML was
refined and extended by a consortium of several companies, and is undergoing minor
revisions by the OMG Revision Task Force.
TEXT 8
Read the text and find equivalents of the following expressions in the text:
отказоустойчивость; параллельная обработка данных; компьютерные
технологии; инструкции; отказоустойчивые компьютеры; базы данных,
работающие в оперативном ре жиме ; неисправность; архитектура с

Страницы