Модель проектирования - История изменений

Admin: /* Уровни проработки */

2017-12-15T09:49:11Z

‎Уровни проработки

Admin: /* Уровни проработки */

2017-02-01T13:52:22Z

‎Уровни проработки

Admin в 13:51, 1 февраля 2017

2017-02-01T13:51:51Z

Admin: Новая страница: «'''Модель проектирования''' (Design Model) - рабочий продукт программная система|программной…»

2016-12-19T11:22:09Z

Новая страница: «'''Модель проектирования''' (Design Model) - рабочий продукт программная система|программной…»

Новая страница

'''Модель проектирования''' (Design Model) - [[рабочий продукт]] [[программная система|программной системы]] в [[OMG Essence]] и [[RUP]].

Модель проектирования является абстракцией реализации системы. Она применяется для представления, а также для документирования эскиза системы программного обеспечения. Это обширный, составной рабочий продукт, заключающий все классы проектирования, подсистемы, пакеты, кооперации и взаимосвязи между ними.

[[Категория:Рабочие продукты]]
[[Категория:Незавершенные статьи]]

@@ Строка 14: / Строка 14: @@
 ! style="text-align: center; font-weight: bold;" | №
 ! style="text-align: center; font-weight: bold;" | Уровень проработки
 ! style="text-align: center; font-weight: bold;" | Описание
 ! style="text-align: center; font-weight: bold;" | Контрольные вопросы
 |-
 | 1
-| style="font-weight: bold;" | Структура и подход описаны
+| style="font-weight: bold;" | Структура и подход описаны (Structure and Approach Described)
-| Structure and Approach Described
 | Describing the system structure and approach enables the implementation effort to be planned and organized.
 | ❑ The overall technical approach has been described, including key buy, build or reuse decisions.
@@ Строка 33: / Строка 31: @@
 |-
 | 2
-| style="font-weight: bold;" | Взаимодействия и интерфейсы определены
+| style="font-weight: bold;" | Взаимодействия и интерфейсы определены (Collaborations and Interfaces Defined)
-| Collaborations and Interfaces Defined
 | Defining the interfaces between major system elements enables them to be developed and tested independently.
 | ❑ The collaborations necessary to support the required system behaviors have been described.
@@ Строка 43: / Строка 40: @@
 |-
 | 3
-| style="font-weight: bold;" | Паттерны проектирования определены
+| style="font-weight: bold;" | Паттерны проектирования определены (Design Patterns Identified)
-| Design Patterns Identified
 | Design patterns can be used to help ensure that appropriate and consistent approaches are used throughout the implementation
 | ❑ The design patterns to be followed have been identified.

@@ Строка 22: / Строка 22: @@
 | Structure and Approach Described
 | Describing the system structure and approach enables the implementation effort to be planned and organized.
-| ❑The overall technical approach has been described, including key buy, build or reuse decisions.
+| ❑ The overall technical approach has been described, including key buy, build or reuse decisions.
-❑The system structure and other critical technical implementation decisions have been documented.
+❑ The system structure and other critical technical implementation decisions have been documented.
-❑Key structural elements within the system have been identified, named and briefly described.
+❑ Key structural elements within the system have been identified, named and briefly described.
-❑Any architectural patterns that will be used have been referenced and their impact explained.
+❑ Any architectural patterns that will be used have been referenced and their impact explained.
-❑The dependencies between the system and other systems are understood and described.
+❑ The dependencies between the system and other systems are understood and described.
 |-
 | 2
@@ Строка 36: / Строка 36: @@
 | Collaborations and Interfaces Defined
 | Defining the interfaces between major system elements enables them to be developed and tested independently.
-| ❑The collaborations necessary to support the required system behaviors have been described.
+| ❑ The collaborations necessary to support the required system behaviors have been described.
-❑The interfaces needed to support these collaborations have been described.
+❑ The interfaces needed to support these collaborations have been described.
-❑It is clear which system elements implement which interfaces.
+❑ It is clear which system elements implement which interfaces.
 |-
 | 3
@@ Строка 46: / Строка 46: @@
 | Design Patterns Identified
 | Design patterns can be used to help ensure that appropriate and consistent approaches are used throughout the implementation
-| ❑The design patterns to be followed have been identified.
+| ❑ The design patterns to be followed have been identified.
-❑Supporting explanation has been provided on the motivation and application of the design pattern in the context of the system being developed.
+❑ Supporting explanation has been provided on the motivation and application of the design pattern in the context of the system being developed.
 |}
 [[Категория:Рабочие продукты]]
-[[Категория:Незавершенные статьи]]
+[[Категория:Недопереведенные статьи]]