Managing Software Requirements: A Unified ApproachAddison-Wesley Professional, 2000 - 491 lappuses A classic treatise that defined the field of applied demand analysis, Consumer Demand in the United States: Prices, Income, and Consumption Behavior is now fully updated and expanded for a new generation. Consumption expenditures by households in the United States account for about 70% of Americaâ__s GDP. The primary focus in this book is on how households adjust these expenditures in response to changes in price and income. Econometric estimates of price and income elasticities are obtained for an exhaustive array of goods and services using data from surveys conducted by the Bureau of Labor Statistics, providing a better understanding of consumer demand. Practical models for forecasting future price and income elasticities are also demonstrated. Fully revised with over a dozen new chapters and appendices, the book revisits the original Taylor-Houthakker models while examining new material as well, such as the use of quantile regression and the stationarity of consumer preference. It also explores the emerging connection between neuroscience and consumer behavior, integrating the economic literature on demand theory with psychology literature. The most comprehensive treatment of the topic to date, this volume will be an essential resource for any researcher, student or professional economist working on consumer behavior or demand theory, as well as investors and policymakers concerned with the impact of economic fluctuations. |
No grāmatas satura
1.–5. rezultāts no 83.
vii. lappuse
... 18 The Problem Domain 19 Stakeholder Needs 19 Moving Toward the Solution Domain 20 Features of the System 20 Software Requirements 20 An Introduction to Use Cases 21 Summary 21 Chapter 3 The Software Team Software Development as a Team vii.
... 18 The Problem Domain 19 Stakeholder Needs 19 Moving Toward the Solution Domain 20 Features of the System 20 Software Requirements 20 An Introduction to Use Cases 21 Summary 21 Chapter 3 The Software Team Software Development as a Team vii.
viii. lappuse
... Stakeholders and the Users 39 Step 4 : Define the Solution System Boundary 41 Step 5 : Identify the Constraints to Be Imposed on the Solution Summary 44 Looking Ahead If 46 46 Chapter 5 Business Modeling 49 Purpose of Business Modeling ...
... Stakeholders and the Users 39 Step 4 : Define the Solution System Boundary 41 Step 5 : Identify the Constraints to Be Imposed on the Solution Summary 44 Looking Ahead If 46 46 Chapter 5 Business Modeling 49 Purpose of Business Modeling ...
ix. lappuse
... Stakeholder and User Needs Features 87 87 88 Managing Complexity by Picking the Level of Abstraction Attributes of Product ... Stakeholders Logistics 105 105 " Warm - Up Materials " 105 Role of the Facilitator 106 Setting the Agenda 108 ...
... Stakeholder and User Needs Features 87 87 88 Managing Complexity by Picking the Level of Abstraction Attributes of Product ... Stakeholders Logistics 105 105 " Warm - Up Materials " 105 Role of the Facilitator 106 Setting the Agenda 108 ...
xvii. lappuse
... managers , general managers , and a variety of “ stakeholders " whose day - to - day operations will be affected by the development of the new system . All of these people can become frustrated by the problems xvii I.
... managers , general managers , and a variety of “ stakeholders " whose day - to - day operations will be affected by the development of the new system . All of these people can become frustrated by the problems xvii I.
xviii. lappuse
... stakeholders , marketing , and management— everyone , really , who has the need and requirement to contribute to the requirements solution . You'll discover that it is crucial that the members of both teams , including the nontechnical ...
... stakeholders , marketing , and management— everyone , really , who has the need and requirement to contribute to the requirements solution . You'll discover that it is crucial that the members of both teams , including the nontechnical ...
Saturs
V | 5 |
VI | 6 |
VII | 7 |
VIII | 9 |
IX | 10 |
X | 13 |
XI | 15 |
XV | 16 |
CLXXXII | 222 |
CLXXXIII | 223 |
CLXXXIV | 225 |
CLXXXV | 227 |
CLXXXVI | 228 |
CLXXXVII | 230 |
CLXXXVIII | 231 |
CXC | 232 |
XVI | 17 |
XVII | 18 |
XIX | 19 |
XXI | 20 |
XXIV | 21 |
XXVI | 23 |
XXVII | 24 |
XXVIII | 25 |
XXXI | 26 |
XXXIII | 27 |
XXXV | 28 |
XXXVI | 31 |
XXXVII | 33 |
XXXVIII | 35 |
XL | 36 |
XLI | 38 |
XLII | 39 |
XLIII | 41 |
XLIV | 44 |
XLV | 46 |
XLVII | 49 |
XLVIII | 50 |
L | 51 |
LII | 52 |
LIII | 54 |
LIV | 55 |
LVI | 56 |
LVII | 57 |
LVIII | 58 |
LIX | 59 |
LXI | 61 |
LXIII | 62 |
LXIV | 63 |
LXV | 65 |
LXVII | 66 |
LXVIII | 68 |
LXXI | 70 |
LXXII | 72 |
LXXIII | 73 |
LXXIV | 77 |
LXXV | 79 |
LXXVI | 81 |
LXXVII | 82 |
LXXVIII | 83 |
LXXX | 84 |
LXXXI | 87 |
LXXXII | 88 |
LXXXIII | 90 |
LXXXIV | 91 |
LXXXV | 93 |
LXXXVI | 94 |
LXXXIX | 95 |
XC | 99 |
XCII | 100 |
XCIII | 101 |
XCIV | 103 |
XCV | 104 |
XCVII | 105 |
C | 106 |
CI | 108 |
CII | 109 |
CIII | 113 |
CIV | 114 |
CV | 116 |
CVII | 117 |
CIX | 118 |
CX | 120 |
CXII | 121 |
CXIII | 122 |
CXVI | 125 |
CXVII | 126 |
CXVIII | 127 |
CXIX | 128 |
CXX | 129 |
CXXI | 130 |
CXXII | 135 |
CXXIII | 136 |
CXXIV | 138 |
CXXV | 139 |
CXXVI | 140 |
CXXVII | 141 |
CXXVIII | 142 |
CXXIX | 143 |
CXXXI | 144 |
CXXXII | 145 |
CXXXIII | 147 |
CXXXIV | 149 |
CXXXV | 150 |
CXXXVII | 151 |
CXXXIX | 153 |
CXL | 155 |
CXLI | 159 |
CXLII | 161 |
CXLIII | 163 |
CXLIV | 165 |
CXLVI | 166 |
CXLVII | 167 |
CXLVIII | 169 |
CXLIX | 170 |
CL | 174 |
CLII | 175 |
CLIII | 177 |
CLIV | 179 |
CLV | 180 |
CLVII | 183 |
CLVIII | 185 |
CLIX | 187 |
CLX | 191 |
CLXI | 194 |
CLXII | 195 |
CLXIII | 197 |
CLXV | 199 |
CLXVI | 200 |
CLXVIII | 203 |
CLXIX | 207 |
CLXX | 208 |
CLXXII | 209 |
CLXXIII | 210 |
CLXXIV | 211 |
CLXXV | 213 |
CLXXVI | 214 |
CLXXVII | 215 |
CLXXVIII | 218 |
CLXXIX | 219 |
CLXXXI | 220 |
CXCI | 234 |
CXCII | 236 |
CXCIV | 237 |
CXCVI | 242 |
CXCVII | 245 |
CXCVIII | 246 |
CXCIX | 247 |
CC | 248 |
CCI | 249 |
CCII | 250 |
CCIII | 251 |
CCIV | 252 |
CCV | 253 |
CCVI | 254 |
CCVII | 255 |
CCX | 256 |
CCXII | 258 |
CCXIII | 260 |
CCXIV | 261 |
CCXV | 262 |
CCXVI | 264 |
CCXVIII | 268 |
CCXIX | 270 |
CCXX | 271 |
CCXXI | 274 |
CCXXII | 276 |
CCXXIII | 277 |
CCXXIV | 279 |
CCXXV | 280 |
CCXXVII | 281 |
CCXXVIII | 282 |
CCXXIX | 284 |
CCXXX | 285 |
CCXXXI | 286 |
CCXXXII | 287 |
CCXXXIII | 288 |
CCXXXIV | 289 |
CCXXXVI | 290 |
CCXXXVII | 291 |
CCXXXVIII | 292 |
CCXL | 293 |
CCXLI | 294 |
CCXLII | 295 |
CCXLIII | 297 |
CCXLIV | 298 |
CCXLV | 299 |
CCXLVI | 301 |
CCXLVIII | 302 |
CCXLIX | 303 |
CCL | 304 |
CCLI | 305 |
CCLII | 307 |
CCLIII | 308 |
CCLIV | 309 |
CCLV | 311 |
CCLVI | 313 |
CCLVII | 314 |
CCLIX | 315 |
CCLX | 316 |
CCLXII | 317 |
CCLXIII | 318 |
CCLXV | 319 |
CCLXVI | 320 |
CCLXVIII | 321 |
CCLXIX | 322 |
CCLXX | 323 |
CCLXXII | 326 |
CCLXXIII | 327 |
CCLXXIV | 328 |
CCLXXVI | 330 |
CCLXXVIII | 331 |
CCLXXIX | 333 |
CCLXXX | 335 |
CCLXXXI | 336 |
CCLXXXII | 337 |
CCLXXXIII | 340 |
CCLXXXIV | 341 |
CCLXXXV | 342 |
CCLXXXVI | 344 |
CCLXXXVII | 345 |
CCLXXXVIII | 346 |
CCLXXXIX | 347 |
CCXC | 348 |
CCXCIII | 350 |
CCXCVI | 351 |
CCXCVIII | 353 |
CCXCIX | 354 |
CCC | 355 |
CCCI | 356 |
CCCII | 357 |
CCCIII | 359 |
CCCIV | 360 |
CCCVI | 361 |
CCCVIII | 362 |
CCCIX | 363 |
CCCX | 364 |
CCCXI | 365 |
CCCXII | 367 |
CCCXIII | 369 |
CCCXV | 371 |
CCCXVII | 372 |
CCCXVIII | 373 |
CCCXX | 376 |
CCCXXI | 379 |
CCCXXIII | 381 |
CCCXXIV | 382 |
CCCXXV | 384 |
CCCXXVII | 385 |
CCCXXVIII | 389 |
CCCXXIX | 390 |
CCCXXX | 391 |
CCCXXXI | 392 |
CCCXXXII | 393 |
CCCXXXIII | 394 |
CCCXXXV | 395 |
CCCXXXVI | 396 |
CCCXXXVIII | 399 |
CCCXXXIX | 403 |
CCCXL | 435 |
CCCXLI | 447 |
CCCXLII | 457 |
CCCXLIII | 465 |
CCCXLIV | 477 |
481 | |
Citi izdevumi - Skatīt visu
Managing Software Requirements (paperback): A Use Case Approach Dean Leffingwell,Don Widrig Priekšskatījums nav pieejams - 2003 |
Managing Software Requirements: A Use Case Approach, 2/E Leffingwell Priekšskatījums nav pieejams - 2003 |
Managing Software Requirements: A Use Case Approach Dean Leffingwell,Don Widrig Priekšskatījums nav pieejams - 2003 |
Bieži izmantoti vārdi un frāzes
activities actors baseline behavior Booch business modeling button Chapter complex context Control Light Control Switch customer's define described design constraints detail development process development team elements elicitation ensure environment example Figure functionality Grady Booch High High HOLIS home automation Homeowner identified implementation important input interact interview iteration Ivar Jacobson James Rumbaugh Lumenations marketing ments Modern SRS Package Object-Oriented organization Philippe Kruchten priority problem analysis product features project management project team prototype Rational Unified Process relationships release requirements management requirements workshop result role sales order scope management simply software development software development process software product software systems solution spiral model stakeholders storyboards subsystems systems engineering team members Team Skill techniques tion trace matrix traceability typically understand Unified Modeling Language use-case model user interface user needs user's validation verification Vision document waterfall model workflow