Screen LibraryJava software development with event B : a practical guide /
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...
Saved in:
| Main Authors: | |
|---|---|
| Published: |
Morgan & Claypool,
|
| Publisher Address: | [San Rafael, California] : |
| Publication Dates: | [2020] |
| Literature type: | Book |
| Language: | English |
| Series: |
Synthesis lectures on software engineering,
#5 |
| Subjects: | |
| Summary: |
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 |
| Carrier Form: | x, 89 pages : illustrations (some color) ; 24 cm. |
| Bibliography: | Includes bibliographical references (pages 83-84) and index. |
| ISBN: |
9781681736877 168173687X 9781681736891 1681736896 |
| Index Number: | QA76 |
| CLC: |
TP312B TP311.52 TP312.8JA |
| Call Number: | TP312.8JA/C357 |