Software Requirements: Encapsulation, Quality, and Reuse

Pirmais vāks
CRC 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

Lietotāju komentāri - Rakstīt atsauksmi

Ierastajās vietās neesam atraduši nevienu atsauksmi.


InformationHiding Secrets
What Are Requirements?
Freedom Requirements Process
Quality Requirements
Stimulus Identification and Cohesion
Stimulus Organization and Architecture
Reusable Requirements
Requirements Encapsulation Design
Requirements Encapsulation
Interface Prototyping
Requirements Evolution
Software Requirements Specification
Cost Savings Estimate Details

Incremental Development
Responses and Behavior Tables

Citi izdevumi - Skatīt visu

Bieži izmantoti vārdi un frāzes

Populāri fragmenti

9. lappuse - A condition or capability needed by a user to solve a problem or achieve an objective; (2) A condition or capability that must be met or possessed by a system or system component to satisfy a contract, standard, specification, or other formally imposed document; (3) A documented representation of a condition or capability as in (1) or (2).
vi. lappuse - ... the interfaces to people, to machines, and to other software systems. No other part of the work so cripples the resulting system if done wrong. No other part is more difficult to rectify later. Therefore, the most important function that the software builder performs for the client is the iterative extraction and refinement of the product requirements.
132. lappuse - The inevitable pain of software development: Why there is no silver bullet.
132. lappuse - Formal methods: The very idea, some thoughts about why they work when they work. Science of Computer Programming 42: 1 (January), Figure 2.
4. lappuse - SOFTWARE DECISION MODULE The Software Decision Module hides software design decisions that are based upon mathematical theorems, physical facts, and programming considerations such as algorithmic efficiency and accuracy. The secrets of this module are NOT described in the requirements document. This module differs from the other modules in that both the secrets and the interfaces are determined by software designers. Changes in these modules are more likely to be motivated by a desire to improve...
4. lappuse - Module includes the programs that need to be changed if any part of the hardware is replaced by a new unit with a different hardware/software interface but with the same general capabilities. This module implements virtual hardware that is used by the rest of the software.
65. lappuse - Annual Meeting of the International Society for General Systems Research, Budapest, Hungary, 1987b. van Gigch, JP The systems paradigm as an inductive methodology for critical thinking.
4. lappuse - The secrets of this module are the data structures and algorithms used to implement the virtual hardware. A: 2 BEHAVIOR-HIDING MODULE The Behavior-Hiding Module includes programs that need to be changed if there are changes in the sections of the requirements document that describe the required behavior (chapters 3 and 4).
132. lappuse - Proceedings of the 27th Annual Meeting of the Society for General Systems Research, Detroit, MI, May, Appendix 6.

Bibliogrāfiskā informācija