- Добавил: literator
- Дата: 1-06-2020, 21:50
- Комментариев: 0

Автор: Nestor Cataño Collazos
Издательство: Morgan and Claypool
Год: 2020
Страниц: 101
Язык: английский
Формат: pdf (true), djvu
Размер: 10.1 MB
The cost of fixing software design flaws after the completion of a software product is so high that it is vital to come up with ways to detect software design flaws in the early stages of software development, for instance, during the software requirements, the analysis activity, or during software design, before coding starts. It is not uncommon that software requirements are ambiguous or contradict each other. Ambiguity is exacerbated by the fact that software requirements are typically written in a natural language, which is not tied to any formal semantics. A palliative to the ambiguity of software requirements is to restrict their syntax to boilerplates, textual templates with placeholders.