Модель проектирования — различия между версиями
Admin (обсуждение | вклад) м (→Уровни проработки) |
Admin (обсуждение | вклад) м (→Уровни проработки) |
||
| Строка 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;" | Уровень проработки | ||
| − | |||
! 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 | | 1 | ||
| − | | style="font-weight: bold;" | Структура и подход описаны | + | | style="font-weight: bold;" | Структура и подход описаны (Structure and Approach Described) |
| − | + | ||
| Describing the system structure and approach enables the implementation effort to be planned and organized. | | 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. | ||
| Строка 33: | Строка 31: | ||
|- | |- | ||
| 2 | | 2 | ||
| − | | style="font-weight: bold;" | Взаимодействия и интерфейсы определены | + | | style="font-weight: bold;" | Взаимодействия и интерфейсы определены (Collaborations and Interfaces Defined) |
| − | + | ||
| Defining the interfaces between major system elements enables them to be developed and tested independently. | | 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. | ||
| Строка 43: | Строка 40: | ||
|- | |- | ||
| 3 | | 3 | ||
| − | | style="font-weight: bold;" | Паттерны проектирования определены | + | | style="font-weight: bold;" | Паттерны проектирования определены (Design Patterns Identified) |
| − | + | ||
| Design patterns can be used to help ensure that appropriate and consistent approaches are used throughout the implementation | | 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. | ||
Текущая версия на 12:49, 15 декабря 2017
Модель проектирования (Design Model) - рабочий продукт программной системы в OMG Essence и RUP.
Модель проектирования является абстракцией реализации системы. Она применяется для представления, а также для документирования эскиза системы программного обеспечения. Это обширный, составной рабочий продукт, заключающий все классы проектирования, подсистемы, пакеты, кооперации и взаимосвязи между ними.
Модель проектирования:
- Позволяет команде понимать структуру решения и подход.
- Определяет взаимодействия между элементами системы, которые необходимы в соответствии с системными требованиями.
- Помогает подобрать и определить оптимальный набор системных элементов и интерфейсов
Уровни проработки
OMG Essence определяет следующие уровни проработки (levels of detail) для рабочего продукта "Модель проектирования" и контрольные вопросы на каждом уровне:
| № | Уровень проработки | Описание | Контрольные вопросы |
|---|---|---|---|
| 1 | Структура и подход описаны (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 system structure and other critical technical implementation decisions have been documented. ❑ 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. ❑ The dependencies between the system and other systems are understood and described. |
| 2 | Взаимодействия и интерфейсы определены (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 interfaces needed to support these collaborations have been described. ❑ It is clear which system elements implement which interfaces. |
| 3 | Паттерны проектирования определены (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.
❑ Supporting explanation has been provided on the motivation and application of the design pattern in the context of the system being developed. |