More about software requirements: thorny issues and practical advice
Gespeichert in:
1. Verfasser: | |
---|---|
Format: | Buch |
Sprache: | English |
Veröffentlicht: |
Redmond, Wash.
Microsoft Press
2006
|
Schriftenreihe: | Best practices
|
Schlagworte: | |
Online-Zugang: | Inhaltsverzeichnis |
Beschreibung: | XV, 201 S. Ill., graph. Darst. |
ISBN: | 0735622671 9780735622678 |
Internformat
MARC
LEADER | 00000nam a2200000 c 4500 | ||
---|---|---|---|
001 | BV021631179 | ||
003 | DE-604 | ||
005 | 20060919 | ||
007 | t | ||
008 | 060627s2006 ad|| |||| 00||| eng d | ||
020 | |a 0735622671 |9 0-7356-2267-1 | ||
020 | |a 9780735622678 |9 978-0-7356-2267-8 | ||
035 | |a (OCoLC)254953945 | ||
035 | |a (DE-599)BVBBV021631179 | ||
040 | |a DE-604 |b ger |e rakwb | ||
041 | 0 | |a eng | |
049 | |a DE-824 |a DE-473 |a DE-859 |a DE-M347 | ||
050 | 0 | |a QA76.76.D47 | |
082 | 0 | |a 005.1068 |2 22 | |
084 | |a ST 230 |0 (DE-625)143617: |2 rvk | ||
100 | 1 | |a Wiegers, Karl E. |e Verfasser |4 aut | |
245 | 1 | 0 | |a More about software requirements |b thorny issues and practical advice |
264 | 1 | |a Redmond, Wash. |b Microsoft Press |c 2006 | |
300 | |a XV, 201 S. |b Ill., graph. Darst. | ||
336 | |b txt |2 rdacontent | ||
337 | |b n |2 rdamedia | ||
338 | |b nc |2 rdacarrier | ||
490 | 0 | |a Best practices | |
650 | 4 | |a Computer software |x Development |x Management | |
650 | 0 | 7 | |a Softwareentwicklung |0 (DE-588)4116522-6 |2 gnd |9 rswk-swf |
650 | 0 | 7 | |a Anforderungsdefinition |0 (DE-588)4193804-5 |2 gnd |9 rswk-swf |
650 | 0 | 7 | |a Requirements engineering |0 (DE-588)4213997-1 |2 gnd |9 rswk-swf |
689 | 0 | 0 | |a Softwareentwicklung |0 (DE-588)4116522-6 |D s |
689 | 0 | 1 | |a Anforderungsdefinition |0 (DE-588)4193804-5 |D s |
689 | 0 | |5 DE-604 | |
689 | 1 | 0 | |a Requirements engineering |0 (DE-588)4213997-1 |D s |
689 | 1 | |5 DE-604 | |
856 | 4 | 2 | |m HEBIS Datenaustausch Darmstadt |q application/pdf |u http://bvbr.bib-bvb.de:8991/F?func=service&doc_library=BVB01&local_base=BVB01&doc_number=014846084&sequence=000001&line_number=0001&func_code=DB_RECORDS&service_type=MEDIA |3 Inhaltsverzeichnis |
943 | 1 | |a oai:aleph.bib-bvb.de:BVB01-014846084 |
Datensatz im Suchindex
_version_ | 1812981230496382976 |
---|---|
adam_text |
MICROSOFT MORE ABOUT SOFTWARE REQUIREMENTS: THORNY ISSUES AND PRACTICAL
ADVICE KARL WIEGERS TABLE OF CONTENTS PREFACE XIII PART I ON ESSCIII;
J R**QUIRT ( O»NTS CONCEPTS 1 REQUIREMENTS ENGINEERING OVERVIEW 3
"REQUIREMENT" DEFINED 3 DIFFERENT TYPES OF REQUIREMENTS 4 BUSINESS
REQUIREMENTS 5 USER REQUIREMENTS 5 FUNCTIONAL REQUIREMENTS 6 SYSTEM
REQUIREMENTS 6 BUSINESS RULES 7 QUALITY ATTRIBUTES 7 EXTERNAL INTERFACES
7 CONSTRAINTS 7 REQUIREMENTS ENGINEERING ACTIVITIES 7 LOOKING AHEAD 9 2
COSMIC TRUTHS ABOUT SOFTWARE REQUIREMENTS 11 REQUIREMENTS REALITIES 11
REQUIREMENTS STAKEHOLDERS 14 REQUIREMENTS SPECIFICATIONS 16 PART II ON
THE MANAGEMENT IEW OF REQUIREMENTS 3 THE BUSINESS VALUE OF BETTER
REQUIREMENTS 21 TELL ME WHERE IT HURTS 21 WHAT CAN BETTER REQUIREMENTS
DO FOR YOU? 23 THE INVESTMENT 25 THE RETURN 26 AN ECONOMIC ARGUMENT 28
THINK OF THIS BOOK? MICROSOFT IS INTERESTED IN HEARING YOUR FEEDBACK
ABOUT THIS PUBLICATION SO WE CAN » ISIWW 'Y-^,1 CONTINUALLY IMPROVE OUR
BOOKS AND LEARNING RESOURCES FOR YOU. TO PARTICIPATE IN A BRIEF J"***
ONLINE SURVEY, PLEASE VISIT: WWW.MICROSOFT.COM/LEARNING/BOOKSURVEY/ VII
VIII TABLE OF CONTENTS 4 HOW LONG DO REQUIREMENTS TAKE? 29 INDUSTRY
BENCHMARKS 29 YOUR OWN EXPERIENCE 30 INCREMENTAL APPROACHES 31 PLANNING
ELICITATION 32 5 ESTIMATING BASED ON REQUIREMENTS 33 SOME ESTIMATION
FUNDAMENTALS 33 ESTIMATION APPROACHES 35 GOALS AREN'T ESTIMATES 37
ESTIMATING FROM REQUIREMENTS 37 MEASURING SOFTWARE SIZE 38 STORY POINTS
40 USE CASE POINTS 41 TESTABLE REQUIREMENTS 45 THE REALITY OF ESTIMATION
47 PART III ON CUSTOMER INTERACTIONS 6 THE MYTH OF THE ON-SITE CUSTOMER
51 USER CLASSES AND PRODUCT CHAMPIONS 51 SURROGATE USERS 53 NOW HEAR
THIS 54 7 AN INQUIRY, NOT AN INQUISITION 57 BUT FIRST, SOME QUESTIONS TO
AVOID 57 QUESTIONS FOR ELICITING BUSINESS REQUIREMENTS 59 USER
REQUIREMENTS AND USE CASES 60 QUESTIONS FOR ELICITING USER REQUIREMENTS
62 OPEN-ENDED QUESTIONS 65 WHY ASK WHY? 66 8 TWO EYES AREN'T ENOUGH 69
IMPROVING YOUR REQUIREMENTS REVIEWS 69 TABLE OF CONTENTS IX PART IV ON
USE CASES 9 USE CASES AND SCENARIOS AND STORIES, OH MY! 77 USE CASES 77
SCENARIOS 79 USER STORIES 82 10 ACTORS AND USERS 85 11 WHEN USE CASES
AREN'T ENOUGH 89 THE POWER OF USE CASES 89 PROJECT TYPE LIMITATIONS 90
EVENT-RESPONSE TABLES 91 USE CASES DON'T REPLACE FUNCTIONAL REQUIREMENTS
93 USE CASES REVEAL FUNCTIONAL REQUIREMENTS 96 PART V ON WRITING
REQUIREMENTS 12 BRIDGING DOCUMENTS 103 13 HOW MUCH DETAIL DO YOU NEED?
105 WHO MAKES THE CALL? 105 WHEN MORE DETAIL IS NEEDED 107 WHEN LESS
DETAIL IS APPROPRIATE 108 IMPLIED REQUIREMENTS 110 SAMPLE LEVELS OF
REQUIREMENTS DETAIL 110 14 TO DUPLICATE OR NOT TO DUPLICATE 113
CROSS-REFERENCING 114 HYPERLINKS 114 TRACEABILITY LINKS 115
RECOMMENDATION 116 15 ELEMENTS OF REQUIREMENTS STYLE 117 I SHALL CALL
THIS A REQUIREMENT 117 SYSTEM PERSPECTIVE OR USER PERSPECTIVE? 119
PARENT AND CHILD REQUIREMENTS 120 WHAT WAS THAT AGAIN? 121 COMPLEX LOGIC
121 NEGATIVE REQUIREMENTS 122 X TABLE OF CONTENTS OMISSIONS 124
BOUNDARIES 125 AVOIDING AMBIGUOUS WORDING 126 16 THE FUZZY LINE BETWEEN
REQUIREMENTS AND DESIGN 129 SOLUTION IDEAS AND DESIGN CONSTRAINTS 130
SOLUTION CLUES 131 PART VI ON THE REQUIREMENTS PROCESS 17 DEFINING
PROJECT SCOPE 137 VISION AND SCOPE 137 CONTEXT DIAGRAM 138 USE CASE
DIAGRAM 140 FEATURE LEVELS 141 MANAGING SCOPE CREEP 143 18 THE LINE IN
THE SAND 147 THE REQUIREMENTS BASELINE 148 WHEN TO BASELINE 149 19 THE
SIX BLIND MEN AND THE REQUIREMENTS 153 LIMITATIONS OF NATURAL LANGUAGE
154 SOME ALTERNATIVE REQUIREMENTS VIEWS 154 WHY CREATE MULTIPLE VIEWS?
157 SELECTING APPROPRIATE VIEWS 159 RECONCILING MULTIPLE VIEWS 161 PART
VII ON MANAGING REQUIREMENTS 20 HANDLING REQUIREMENTS FOR MULTIPLE
RELEASES 165 SINGLE REQUIREMENTS SPECIFICATION 166 MULTIPLE REQUIREMENTS
SPECIFICATIONS 167 REQUIREMENTS MANAGEMENT TOOLS 168 21 BUSINESS
REQUIREMENTS AND BUSINESS RULES 171 BUSINESS REQUIREMENTS 171 BUSINESS
RULES 172 BUSINESS RULES AND SOFTWARE REQUIREMENTS 173 TABLE OF CONTENTS
XI 22 MEASURING REQUIREMENTS 177 PRODUCT SIZE 177 REQUIREMENTS QUALITY
178 REQUIREMENTS STATUS 179 REQUESTS FOR CHANGES 180 EFFORT 181 23
EXPLOITING REQUIREMENTS MANAGEMENT TOOLS 183 WRITE GOOD REQUIREMENTS
FIRST 183 EXPECT A CULTURE CHANGE 184 CHOOSE A DATABASE-CENTRIC OR
DOCUMENT-CENTRIC TOOL 184 DON'T CREATE TOO MANY REQUIREMENT TYPES OR
ATTRIBUTES 185 TRAIN THE TOOL USERS 186 ASSIGN RESPONSIBILITIES 186 TAKE
ADVANTAGE OF TOOL FEATURES 186 REFERENCES 189 INDEX 195 MICROSOFT IS
INTERESTED IN HEARING YOUR FEEDBACK ABOUT THIS PUBLICATION SO WE CAN
CONTINUALLY IMPROVE OUR BOOKS AND LEARNING RESOURCES FOR YOU. TO
PARTICIPATE IN A BRIEF ONLINE SURVEY, PLEASE VISIT:
WWW.MICROSOFT.COM/LEARNING/BOOKSURVEY/ |
adam_txt |
MICROSOFT MORE ABOUT SOFTWARE REQUIREMENTS: THORNY ISSUES AND PRACTICAL
ADVICE KARL WIEGERS TABLE OF CONTENTS PREFACE XIII PART I ON ESSCIII;
J R**QUIRT ( O»NTS CONCEPTS 1 REQUIREMENTS ENGINEERING OVERVIEW 3
"REQUIREMENT" DEFINED 3 DIFFERENT TYPES OF REQUIREMENTS 4 BUSINESS
REQUIREMENTS 5 USER REQUIREMENTS 5 FUNCTIONAL REQUIREMENTS 6 SYSTEM
REQUIREMENTS 6 BUSINESS RULES 7 QUALITY ATTRIBUTES 7 EXTERNAL INTERFACES
7 CONSTRAINTS 7 REQUIREMENTS ENGINEERING ACTIVITIES 7 LOOKING AHEAD 9 2
COSMIC TRUTHS ABOUT SOFTWARE REQUIREMENTS 11 REQUIREMENTS REALITIES 11
REQUIREMENTS STAKEHOLDERS 14 REQUIREMENTS SPECIFICATIONS 16 PART II ON
THE MANAGEMENT IEW OF REQUIREMENTS 3 THE BUSINESS VALUE OF BETTER
REQUIREMENTS 21 TELL ME WHERE IT HURTS 21 WHAT CAN BETTER REQUIREMENTS
DO FOR YOU? 23 THE INVESTMENT 25 THE RETURN 26 AN ECONOMIC ARGUMENT 28
THINK OF THIS BOOK? MICROSOFT IS INTERESTED IN HEARING YOUR FEEDBACK
ABOUT THIS PUBLICATION SO WE CAN » ISIWW 'Y-^,1 CONTINUALLY IMPROVE OUR
BOOKS AND LEARNING RESOURCES FOR YOU. TO PARTICIPATE IN A BRIEF J"***
ONLINE SURVEY, PLEASE VISIT: WWW.MICROSOFT.COM/LEARNING/BOOKSURVEY/ VII
VIII TABLE OF CONTENTS 4 HOW LONG DO REQUIREMENTS TAKE? 29 INDUSTRY
BENCHMARKS 29 YOUR OWN EXPERIENCE 30 INCREMENTAL APPROACHES 31 PLANNING
ELICITATION 32 5 ESTIMATING BASED ON REQUIREMENTS 33 SOME ESTIMATION
FUNDAMENTALS 33 ESTIMATION APPROACHES 35 GOALS AREN'T ESTIMATES 37
ESTIMATING FROM REQUIREMENTS 37 MEASURING SOFTWARE SIZE 38 STORY POINTS
40 USE CASE POINTS 41 TESTABLE REQUIREMENTS 45 THE REALITY OF ESTIMATION
47 PART III ON CUSTOMER INTERACTIONS 6 THE MYTH OF THE ON-SITE CUSTOMER
51 USER CLASSES AND PRODUCT CHAMPIONS 51 SURROGATE USERS 53 NOW HEAR
THIS 54 7 AN INQUIRY, NOT AN INQUISITION 57 BUT FIRST, SOME QUESTIONS TO
AVOID 57 QUESTIONS FOR ELICITING BUSINESS REQUIREMENTS 59 USER
REQUIREMENTS AND USE CASES 60 QUESTIONS FOR ELICITING USER REQUIREMENTS
62 OPEN-ENDED QUESTIONS 65 WHY ASK WHY? 66 8 TWO EYES AREN'T ENOUGH 69
IMPROVING YOUR REQUIREMENTS REVIEWS 69 TABLE OF CONTENTS IX PART IV ON
USE CASES 9 USE CASES AND SCENARIOS AND STORIES, OH MY! 77 USE CASES 77
SCENARIOS 79 USER STORIES 82 10 ACTORS AND USERS 85 11 WHEN USE CASES
AREN'T ENOUGH 89 THE POWER OF USE CASES 89 PROJECT TYPE LIMITATIONS 90
EVENT-RESPONSE TABLES 91 USE CASES DON'T REPLACE FUNCTIONAL REQUIREMENTS
93 USE CASES REVEAL FUNCTIONAL REQUIREMENTS 96 PART V ON WRITING
REQUIREMENTS 12 BRIDGING DOCUMENTS 103 13 HOW MUCH DETAIL DO YOU NEED?
105 WHO MAKES THE CALL? 105 WHEN MORE DETAIL IS NEEDED 107 WHEN LESS
DETAIL IS APPROPRIATE 108 IMPLIED REQUIREMENTS 110 SAMPLE LEVELS OF
REQUIREMENTS DETAIL 110 14 TO DUPLICATE OR NOT TO DUPLICATE 113
CROSS-REFERENCING 114 HYPERLINKS 114 TRACEABILITY LINKS 115
RECOMMENDATION 116 15 ELEMENTS OF REQUIREMENTS STYLE 117 I SHALL CALL
THIS A REQUIREMENT 117 SYSTEM PERSPECTIVE OR USER PERSPECTIVE? 119
PARENT AND CHILD REQUIREMENTS 120 WHAT WAS THAT AGAIN? 121 COMPLEX LOGIC
121 NEGATIVE REQUIREMENTS 122 X TABLE OF CONTENTS OMISSIONS 124
BOUNDARIES 125 AVOIDING AMBIGUOUS WORDING 126 16 THE FUZZY LINE BETWEEN
REQUIREMENTS AND DESIGN 129 SOLUTION IDEAS AND DESIGN CONSTRAINTS 130
SOLUTION CLUES 131 PART VI ON THE REQUIREMENTS PROCESS 17 DEFINING
PROJECT SCOPE 137 VISION AND SCOPE 137 CONTEXT DIAGRAM 138 USE CASE
DIAGRAM 140 FEATURE LEVELS 141 MANAGING SCOPE CREEP 143 18 THE LINE IN
THE SAND 147 THE REQUIREMENTS BASELINE 148 WHEN TO BASELINE 149 19 THE
SIX BLIND MEN AND THE REQUIREMENTS 153 LIMITATIONS OF NATURAL LANGUAGE
154 SOME ALTERNATIVE REQUIREMENTS VIEWS 154 WHY CREATE MULTIPLE VIEWS?
157 SELECTING APPROPRIATE VIEWS 159 RECONCILING MULTIPLE VIEWS 161 PART
VII ON MANAGING REQUIREMENTS 20 HANDLING REQUIREMENTS FOR MULTIPLE
RELEASES 165 SINGLE REQUIREMENTS SPECIFICATION 166 MULTIPLE REQUIREMENTS
SPECIFICATIONS 167 REQUIREMENTS MANAGEMENT TOOLS 168 21 BUSINESS
REQUIREMENTS AND BUSINESS RULES 171 BUSINESS REQUIREMENTS 171 BUSINESS
RULES 172 BUSINESS RULES AND SOFTWARE REQUIREMENTS 173 TABLE OF CONTENTS
XI 22 MEASURING REQUIREMENTS 177 PRODUCT SIZE 177 REQUIREMENTS QUALITY
178 REQUIREMENTS STATUS 179 REQUESTS FOR CHANGES 180 EFFORT 181 23
EXPLOITING REQUIREMENTS MANAGEMENT TOOLS 183 WRITE GOOD REQUIREMENTS
FIRST 183 EXPECT A CULTURE CHANGE 184 CHOOSE A DATABASE-CENTRIC OR
DOCUMENT-CENTRIC TOOL 184 DON'T CREATE TOO MANY REQUIREMENT TYPES OR
ATTRIBUTES 185 TRAIN THE TOOL USERS 186 ASSIGN RESPONSIBILITIES 186 TAKE
ADVANTAGE OF TOOL FEATURES 186 REFERENCES 189 INDEX 195 MICROSOFT IS
INTERESTED IN HEARING YOUR FEEDBACK ABOUT THIS PUBLICATION SO WE CAN
CONTINUALLY IMPROVE OUR BOOKS AND LEARNING RESOURCES FOR YOU. TO
PARTICIPATE IN A BRIEF ONLINE SURVEY, PLEASE VISIT:
WWW.MICROSOFT.COM/LEARNING/BOOKSURVEY/ |
any_adam_object | 1 |
any_adam_object_boolean | 1 |
author | Wiegers, Karl E. |
author_facet | Wiegers, Karl E. |
author_role | aut |
author_sort | Wiegers, Karl E. |
author_variant | k e w ke kew |
building | Verbundindex |
bvnumber | BV021631179 |
callnumber-first | Q - Science |
callnumber-label | QA76 |
callnumber-raw | QA76.76.D47 |
callnumber-search | QA76.76.D47 |
callnumber-sort | QA 276.76 D47 |
callnumber-subject | QA - Mathematics |
classification_rvk | ST 230 |
ctrlnum | (OCoLC)254953945 (DE-599)BVBBV021631179 |
dewey-full | 005.1068 |
dewey-hundreds | 000 - Computer science, information, general works |
dewey-ones | 005 - Computer programming, programs, data, security |
dewey-raw | 005.1068 |
dewey-search | 005.1068 |
dewey-sort | 15.1068 |
dewey-tens | 000 - Computer science, information, general works |
discipline | Informatik |
discipline_str_mv | Informatik |
format | Book |
fullrecord | <?xml version="1.0" encoding="UTF-8"?><collection xmlns="http://www.loc.gov/MARC21/slim"><record><leader>00000nam a2200000 c 4500</leader><controlfield tag="001">BV021631179</controlfield><controlfield tag="003">DE-604</controlfield><controlfield tag="005">20060919</controlfield><controlfield tag="007">t</controlfield><controlfield tag="008">060627s2006 ad|| |||| 00||| eng d</controlfield><datafield tag="020" ind1=" " ind2=" "><subfield code="a">0735622671</subfield><subfield code="9">0-7356-2267-1</subfield></datafield><datafield tag="020" ind1=" " ind2=" "><subfield code="a">9780735622678</subfield><subfield code="9">978-0-7356-2267-8</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(OCoLC)254953945</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(DE-599)BVBBV021631179</subfield></datafield><datafield tag="040" ind1=" " ind2=" "><subfield code="a">DE-604</subfield><subfield code="b">ger</subfield><subfield code="e">rakwb</subfield></datafield><datafield tag="041" ind1="0" ind2=" "><subfield code="a">eng</subfield></datafield><datafield tag="049" ind1=" " ind2=" "><subfield code="a">DE-824</subfield><subfield code="a">DE-473</subfield><subfield code="a">DE-859</subfield><subfield code="a">DE-M347</subfield></datafield><datafield tag="050" ind1=" " ind2="0"><subfield code="a">QA76.76.D47</subfield></datafield><datafield tag="082" ind1="0" ind2=" "><subfield code="a">005.1068</subfield><subfield code="2">22</subfield></datafield><datafield tag="084" ind1=" " ind2=" "><subfield code="a">ST 230</subfield><subfield code="0">(DE-625)143617:</subfield><subfield code="2">rvk</subfield></datafield><datafield tag="100" ind1="1" ind2=" "><subfield code="a">Wiegers, Karl E.</subfield><subfield code="e">Verfasser</subfield><subfield code="4">aut</subfield></datafield><datafield tag="245" ind1="1" ind2="0"><subfield code="a">More about software requirements</subfield><subfield code="b">thorny issues and practical advice</subfield></datafield><datafield tag="264" ind1=" " ind2="1"><subfield code="a">Redmond, Wash.</subfield><subfield code="b">Microsoft Press</subfield><subfield code="c">2006</subfield></datafield><datafield tag="300" ind1=" " ind2=" "><subfield code="a">XV, 201 S.</subfield><subfield code="b">Ill., graph. Darst.</subfield></datafield><datafield tag="336" ind1=" " ind2=" "><subfield code="b">txt</subfield><subfield code="2">rdacontent</subfield></datafield><datafield tag="337" ind1=" " ind2=" "><subfield code="b">n</subfield><subfield code="2">rdamedia</subfield></datafield><datafield tag="338" ind1=" " ind2=" "><subfield code="b">nc</subfield><subfield code="2">rdacarrier</subfield></datafield><datafield tag="490" ind1="0" ind2=" "><subfield code="a">Best practices</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Computer software</subfield><subfield code="x">Development</subfield><subfield code="x">Management</subfield></datafield><datafield tag="650" ind1="0" ind2="7"><subfield code="a">Softwareentwicklung</subfield><subfield code="0">(DE-588)4116522-6</subfield><subfield code="2">gnd</subfield><subfield code="9">rswk-swf</subfield></datafield><datafield tag="650" ind1="0" ind2="7"><subfield code="a">Anforderungsdefinition</subfield><subfield code="0">(DE-588)4193804-5</subfield><subfield code="2">gnd</subfield><subfield code="9">rswk-swf</subfield></datafield><datafield tag="650" ind1="0" ind2="7"><subfield code="a">Requirements engineering</subfield><subfield code="0">(DE-588)4213997-1</subfield><subfield code="2">gnd</subfield><subfield code="9">rswk-swf</subfield></datafield><datafield tag="689" ind1="0" ind2="0"><subfield code="a">Softwareentwicklung</subfield><subfield code="0">(DE-588)4116522-6</subfield><subfield code="D">s</subfield></datafield><datafield tag="689" ind1="0" ind2="1"><subfield code="a">Anforderungsdefinition</subfield><subfield code="0">(DE-588)4193804-5</subfield><subfield code="D">s</subfield></datafield><datafield tag="689" ind1="0" ind2=" "><subfield code="5">DE-604</subfield></datafield><datafield tag="689" ind1="1" ind2="0"><subfield code="a">Requirements engineering</subfield><subfield code="0">(DE-588)4213997-1</subfield><subfield code="D">s</subfield></datafield><datafield tag="689" ind1="1" ind2=" "><subfield code="5">DE-604</subfield></datafield><datafield tag="856" ind1="4" ind2="2"><subfield code="m">HEBIS Datenaustausch Darmstadt</subfield><subfield code="q">application/pdf</subfield><subfield code="u">http://bvbr.bib-bvb.de:8991/F?func=service&doc_library=BVB01&local_base=BVB01&doc_number=014846084&sequence=000001&line_number=0001&func_code=DB_RECORDS&service_type=MEDIA</subfield><subfield code="3">Inhaltsverzeichnis</subfield></datafield><datafield tag="943" ind1="1" ind2=" "><subfield code="a">oai:aleph.bib-bvb.de:BVB01-014846084</subfield></datafield></record></collection> |
id | DE-604.BV021631179 |
illustrated | Illustrated |
index_date | 2024-07-02T14:57:09Z |
indexdate | 2024-10-15T12:00:35Z |
institution | BVB |
isbn | 0735622671 9780735622678 |
language | English |
oai_aleph_id | oai:aleph.bib-bvb.de:BVB01-014846084 |
oclc_num | 254953945 |
open_access_boolean | |
owner | DE-824 DE-473 DE-BY-UBG DE-859 DE-M347 |
owner_facet | DE-824 DE-473 DE-BY-UBG DE-859 DE-M347 |
physical | XV, 201 S. Ill., graph. Darst. |
publishDate | 2006 |
publishDateSearch | 2006 |
publishDateSort | 2006 |
publisher | Microsoft Press |
record_format | marc |
series2 | Best practices |
spelling | Wiegers, Karl E. Verfasser aut More about software requirements thorny issues and practical advice Redmond, Wash. Microsoft Press 2006 XV, 201 S. Ill., graph. Darst. txt rdacontent n rdamedia nc rdacarrier Best practices Computer software Development Management Softwareentwicklung (DE-588)4116522-6 gnd rswk-swf Anforderungsdefinition (DE-588)4193804-5 gnd rswk-swf Requirements engineering (DE-588)4213997-1 gnd rswk-swf Softwareentwicklung (DE-588)4116522-6 s Anforderungsdefinition (DE-588)4193804-5 s DE-604 Requirements engineering (DE-588)4213997-1 s HEBIS Datenaustausch Darmstadt application/pdf http://bvbr.bib-bvb.de:8991/F?func=service&doc_library=BVB01&local_base=BVB01&doc_number=014846084&sequence=000001&line_number=0001&func_code=DB_RECORDS&service_type=MEDIA Inhaltsverzeichnis |
spellingShingle | Wiegers, Karl E. More about software requirements thorny issues and practical advice Computer software Development Management Softwareentwicklung (DE-588)4116522-6 gnd Anforderungsdefinition (DE-588)4193804-5 gnd Requirements engineering (DE-588)4213997-1 gnd |
subject_GND | (DE-588)4116522-6 (DE-588)4193804-5 (DE-588)4213997-1 |
title | More about software requirements thorny issues and practical advice |
title_auth | More about software requirements thorny issues and practical advice |
title_exact_search | More about software requirements thorny issues and practical advice |
title_exact_search_txtP | More about software requirements thorny issues and practical advice |
title_full | More about software requirements thorny issues and practical advice |
title_fullStr | More about software requirements thorny issues and practical advice |
title_full_unstemmed | More about software requirements thorny issues and practical advice |
title_short | More about software requirements |
title_sort | more about software requirements thorny issues and practical advice |
title_sub | thorny issues and practical advice |
topic | Computer software Development Management Softwareentwicklung (DE-588)4116522-6 gnd Anforderungsdefinition (DE-588)4193804-5 gnd Requirements engineering (DE-588)4213997-1 gnd |
topic_facet | Computer software Development Management Softwareentwicklung Anforderungsdefinition Requirements engineering |
url | http://bvbr.bib-bvb.de:8991/F?func=service&doc_library=BVB01&local_base=BVB01&doc_number=014846084&sequence=000001&line_number=0001&func_code=DB_RECORDS&service_type=MEDIA |
work_keys_str_mv | AT wiegerskarle moreaboutsoftwarerequirementsthornyissuesandpracticaladvice |