Software Requirements: Encapsulation, Quality, and ReuseCRC Press, 2016. gada 19. apr. - 264 lappuses Software Requirements: Encapsulation, Quality, and Reuse describes how to make requirements easy to change by using encapsulation. It introduces the Freedom methodology that shows how to encapsulate requirements thereby promoting reuse and quality. Encapsulating requirements reduces software life cycle costs by making requirements and the code that |
No grāmatas satura
1.–5. rezultāts no 89.
vii. lappuse
... ..............................................................................77 7.2 Stimulus Set Architecture........................................................................ 77 7.3 New Stimulus Response....................
... ..............................................................................77 7.2 Stimulus Set Architecture........................................................................ 77 7.3 New Stimulus Response....................
xi. lappuse
... their help to specify the external interface of the software that they will use. With the assistance of the developers, customers specify the software external interface in terms of stimulus–response pairs organized xi Preface.
... their help to specify the external interface of the software that they will use. With the assistance of the developers, customers specify the software external interface in terms of stimulus–response pairs organized xi Preface.
xii. lappuse
... stimulus–response pairs organized into cohesive sets called “stimulus sets.” The stimulus sets are themselves organized hierarchically into a “functionality tree” that defines the architecture of the external interface. During design ...
... stimulus–response pairs organized into cohesive sets called “stimulus sets.” The stimulus sets are themselves organized hierarchically into a “functionality tree” that defines the architecture of the external interface. During design ...
6. lappuse
... (stimulus–response pair) is implemented by one functionality module, as described briefly above and in detail in Chapters 11 and 12. With each requirement mapping to one code module, traceability becomes trivial, and the need to maintain ...
... (stimulus–response pair) is implemented by one functionality module, as described briefly above and in detail in Chapters 11 and 12. With each requirement mapping to one code module, traceability becomes trivial, and the need to maintain ...
7. lappuse
... (stimulus–response pair) is located in a single module, as described in Chapters 11 and 12. In all other methodologies, the code that implements a requirement tends to be scattered among many modules, often in unobvious ways. Thus ...
... (stimulus–response pair) is located in a single module, as described in Chapters 11 and 12. In all other methodologies, the code that implements a requirement tends to be scattered among many modules, often in unobvious ways. Thus ...
Saturs
Chapter 10 | 111 |
Chapter 11 | 145 |
Chapter 12 | 155 |
Chapter 13 | 169 |
Chapter 14 | 199 |
Appendix A | 223 |
Appendix B | 227 |
Appendix C | 235 |
Citi izdevumi - Skatīt visu
Software Requirements: Encapsulation, Quality, and Reuse Rick Lutowski Ierobežota priekšskatīšana - 2016 |
Software Requirements: Encapsulation, Quality, and Reuse Rick Lutowski Priekšskatījums nav pieejams - 2005 |
Bieži izmantoti vārdi un frāzes
activate app server behavior table black box capability requirements categ Chapter Checkbox Classification SS cohesion command stimuli command-data stream common service modules communication protocols context diagram cost create stimuli data declarations data stimulus descrip development team device drivers end of method enterprise model Equation external interface mockup external system Figure FileDialog Formal methods fully implemented functional simulation functionality module functionality screen functionality tree Furmasco Furniture Data SS Furniture List SS human interface human user interface Identify information-hiding input interface prototype Internal Response inventory system list of furniture look and feel ments message area method that performs Mode SS modify percent postal address priority private void programmatic protocol public void quality attributes quality requirements quantity Reqmts requirements encapsulation requirements reuse response behavior response method reusable requirements component selected shipping wt software system stim stimulus methods Stimulus Normal NSR stimulus set stimulus–response TextField this.add xxx xxxxxxxxxxxxxxxxxxxxxx