000			02923nam a2200313 a 4500
003			AR-sfUTN
008			170717b ||||| |||| 00| 0 d
020			_a3540760067
040			_cAR-sfUTN
041			_aeng
080			_a004.413 M119 _22000
100	1		_aMacaulay, Linda A.
245	1	0	_aRequirements engineering / _cLinda A. Macaulay.
260			_aBerlin: _bSpringer, _c1996
300			_a202 p.
336			_2rdacontent _atexto _btxt
337			_2rdamedia _asin mediación _bn
338			_2rdacarrier _avolumen _bnc
505	8	0	_aCONTENIDO Part 1 Introduction 1 Objectives 1 why is a requirements stage necessary? 3 what is a requirement? 4 Requirements engineering 5 The requirements engineering process 6 The requirements engineer 8 Approaches to the problem of requirements 9 Rationale for this book 19 Summary 21 Part 2 The role of requirements engineering techniques 23 Objectives 23 The requirements engineering process 23 Human communication within requirements 29 Knowledge development 35 The requirements document 39 Management 45 Requirements for RE techniques 48 The contribution of various approaches 51 Summary 54 Part 3 Specific techniques 1 - organizational requirements: objectives 57 An illustrative problem situation 58 Soft systems methodology 63 ETHICS 70 Eason's approach to information technology and organizational change 76 Eason's techniques for cost-benefit assessment of the organizational impact of a technical system proposal 80 Summary 76 82 Part 4 Specific techniques 2 - group session approaches: objectives 83 An illustrative problem situation 84 Characteristics of group session approaches 91 The role of the facilitator 93 Joint application design (JAD) 94 Quality function deployment (QFD) 98 Co-operative requirements capture (CRC) 102 Summary 111 Part 5 Specific techniques 3 - interactive approaches: objectives 113 An illustrative problem situation 115 Designer-as-apprentice 116 Focus groups 117 Future workshops, Metaphorical design and design mock-ups 118 Prototyping 121 Co-operative prototyping 122 Co-operative evaluation124 Summary 125 Part 6 Requirements and the customer-supplier relationship: objectives 127 Scenario 1 - an invitation to tender (ITT) 129 Scenario 2 - responding to a specific customer request 131 Scenario 3 - developing a generic product 133 Scenario 4 - tailoring a product 136 Scenario 5 - responding to a business centre within the same organization 138 Scenario 6 - responding to the needs of a specific business function 139 Scenario 7 - responding to the needs of colleagues within the same business 141 Conclusions 142
650			_aTECNICAS INFORMATICAS
650			_aANALISIS DE SISTEMAS
650			_aINGENIERIA DE REQUERIMIENTOS
650			_aREQUIREMENTS
650			_aSYSTEMS ENGINEERING
650			_aSYSTEM ANALYSIS
650			_aSYSTEM FAILURES-ENGINEERING
942			_cLIB _2udc
999			_c60919 _d60919