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 75.
vii. lappuse
... Interface Functionality Tree Step 1 ... 83 Step 2 ... 83 Step 3 ........ .... 83 7.7 Example Problem : Reverse Engineering the External Interface Architecture ........ 7.8 Example Problem Functionality Tree 7.9 Alternate Kickoff ...
... Interface Functionality Tree Step 1 ... 83 Step 2 ... 83 Step 3 ........ .... 83 7.7 Example Problem : Reverse Engineering the External Interface Architecture ........ 7.8 Example Problem Functionality Tree 7.9 Alternate Kickoff ...
viii. lappuse
... External Interface .. 12.5 Example Problem Functionality Module ..... 158 .159 .159 162 162 163 163 164 13 Interface Prototyping ... .... 169 13.1 Chapter Overview ....... 169 13.2 Purpose of Prototypes .... 169 13.2.1 Clarify ...
... External Interface .. 12.5 Example Problem Functionality Module ..... 158 .159 .159 162 162 163 163 164 13 Interface Prototyping ... .... 169 13.1 Chapter Overview ....... 169 13.2 Purpose of Prototypes .... 169 13.2.1 Clarify ...
ix. lappuse
... External Interface Simulation ........... 13.3.5 Full Functional Simulation ............... 13.3.6 Robust Functional Simulation ...... 13.3.7 External Interface Mockup ..... 13.3.8 Full Functional Mockup ..... 13.3.9 Release ...
... External Interface Simulation ........... 13.3.5 Full Functional Simulation ............... 13.3.6 Robust Functional Simulation ...... 13.3.7 External Interface Mockup ..... 13.3.8 Full Functional Mockup ..... 13.3.9 Release ...
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 xi Chapter 1: Overview.
... 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 xi Chapter 1: Overview.
xii. lappuse
... external interface . During design , developers use the external interface architecture as the upper level of the design archi- tecture , thus ensuring architectural identity between requirements and design . Within this upper level of ...
... external interface . During design , developers use the external interface architecture as the upper level of the design archi- tecture , thus ensuring architectural identity between requirements and design . Within this upper level of ...
Saturs
xi | |
3 | |
13 | |
21 | |
Quality Requirements | 37 |
Stimulus Identification and Cohesion | 49 |
Stimulus Organization and Architecture | 71 |
Reusable Requirements | 89 |
Requirements Encapsulation Design | 139 |
Requirements Encapsulation | 149 |
Interface Prototyping | 163 |
Requirements Evolution | 193 |
Software Requirements Specification | 212 |
Cost Savings Estimate Details | 216 |
Glossary | 224 |
Index | 232 |
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 Overview Checkbox Classification SS cohesion command stimuli command-data stream common service modules communication protocols context diagram cost create stimuli data declarations data stimuli descrip development team device drivers end of method enterprise model Equation error responses Example Problem external interface mockup external response external system Figure FileDialog Formal methods functional simulation Functionality Module functionality screen functionality tree Furniture Data SS Furniture List SS human interface human user interface Identify information-hiding input interface prototype inventory system Level List of Furniture look and feel ments message area method that performs Mode SS modify notation Prioritize private void programmatic protocol public void quality attributes quality requirements quantity Reqmts requirements encapsulation requirements reuse response behavior response method reusable requirements component shipping wt Software Engineering software system stim stimulus methods Stimulus Response stimulus set this.add
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.