Verfügbarkeit: UML for the IT business analyst

UML for the IT business analyst: a practical guide to requirements gathering using the unified modelling language

Gespeichert in:

Bibliographische Detailangaben
1. Verfasser:	Podeswa, Howard (VerfasserIn)
Format:	Buch
Sprache:	English
Veröffentlicht:	Australia [u.a.] Course Technology 2010
Ausgabe:	2. ed.
Schlagworte:	Wirtschaft Business > Computer network resources > Case studies Object-oriented methods (Computer science) UML (Computer science) Betriebsanalyse Informationstechnik UML Fallstudiensammlung
Online-Zugang:	Inhaltsverzeichnis
Beschreibung:	XXV, 372 S.
ISBN:	9781598638684 1598638688

Internformat

MARC


LEADER	00000nam a2200000zc 4500
001	BV035679984
003	DE-604
005	20091026
007	t
008	090817s2010 xxu \|\|\|\| 00\|\|\| eng d
020			\|a 9781598638684 \|c pbk \|9 978-1-59863-868-4
020			\|a 1598638688 \|9 1-59863-868-8
035			\|a (OCoLC)463075094
035			\|a (DE-599)BVBBV035679984
040			\|a DE-604 \|b ger \|e aacr
041	0		\|a eng
044			\|a xxu \|c US
049			\|a DE-473
050		0	\|a QA76.9.O35
082	0		\|a 005.117 \|2 22
084			\|a ST 515 \|0 (DE-625)143677: \|2 rvk
100	1		\|a Podeswa, Howard \|e Verfasser \|4 aut
245	1	0	\|a UML for the IT business analyst \|b a practical guide to requirements gathering using the unified modelling language \|c Howard Podeswa
250			\|a 2. ed.
264		1	\|a Australia [u.a.] \|b Course Technology \|c 2010
300			\|a XXV, 372 S.
336			\|b txt \|2 rdacontent
337			\|b n \|2 rdamedia
338			\|b nc \|2 rdacarrier
650		4	\|a Wirtschaft
650		4	\|a Business \|x Computer network resources \|v Case studies
650		4	\|a Object-oriented methods (Computer science)
650		4	\|a UML (Computer science)
650	0	7	\|a Betriebsanalyse \|0 (DE-588)4006164-4 \|2 gnd \|9 rswk-swf
650	0	7	\|a Informationstechnik \|0 (DE-588)4026926-7 \|2 gnd \|9 rswk-swf
650	0	7	\|a UML \|0 (DE-588)4469781-8 \|2 gnd \|9 rswk-swf
655		7	\|0 (DE-588)4522595-3 \|a Fallstudiensammlung \|2 gnd-content
689	0	0	\|a Informationstechnik \|0 (DE-588)4026926-7 \|D s
689	0	1	\|a Betriebsanalyse \|0 (DE-588)4006164-4 \|D s
689	0	2	\|a UML \|0 (DE-588)4469781-8 \|D s
689	0		\|5 DE-604
856	4	2	\|m Digitalisierung UB Bamberg \|q application/pdf \|u http://bvbr.bib-bvb.de:8991/F?func=service&doc_library=BVB01&local_base=BVB01&doc_number=017734263&sequence=000002&line_number=0001&func_code=DB_RECORDS&service_type=MEDIA \|3 Inhaltsverzeichnis
999			\|a oai:aleph.bib-bvb.de:BVB01-017734263

Datensatz im Suchindex

_version_	1804139385995657216
adam_text	Table df Contents Introduction .................................................. XIX Chapter 1 Who Are IT Business Analysts? ........................1 Chapter Objectives ..............................................1 The IT and Non-IT BA ...........................................1 Perspective on the IT BA Role .....................................2 Why Modeling Is a Good Thing ...................................3 The Behavioral (Dynamic) Model ..................................3 The Structural (Static) Model .....................................4 For Those Trained in Structured Analysis ............................5 Mapping the BABOK 2 to This Book ...............................6 Chapter Summary ............................................. 13 Endnotes..................................................... 14 Chapter 2 The BA s Perspective on Object Orientation .............17 Chapter Objectives ............................................. 17 What Is 00?.................................................. 18 The UML Standard ............................................. 18 Cognitive Psychology and OO ....................................18 Objects ......................................................19 The BA Perspective .........................................19 Attributes and Operations ......................................19 The BA Perspective .........................................19 Operations and Methods .......................................20 The BA Perspective .........................................20 Encapsulation ................................................. 20 The BA Perspective .........................................20 ¡x Table of Contents OO Concept: Classes ...........................................21 The BA Perspective .........................................22 OO Concept: Relationships ......................................22 OO Concept: Generalization .................................22 OO Concept: Association ....................................24 OO Concept: Aggregation ...................................25 OO Concept: Composite Aggregation (Composition) .............26 OO Concept: Polymorphism .....................................27 Polymorphic Objects ........................................27 Polymorphic Operations .....................................27 The BA Perspective .........................................28 Use Cases and Scenarios ........................................28 The BA Perspective .........................................29 Business and System Use Cases ...................................29 The BA Perspective .........................................30 Chapter Summary .............................................30 Endnotes.....................................................31 Chapter 3 Steps of B.O.O.M ...................................33 Chapter Objectives .............................................33 B.O.O.M. and SDLCs ............................................33 The B.O.O.M. Steps ............................................34 Step 1 : Initiation ...........................................34 Step 2: Discovery ...........................................35 Step 3: Construction ........................................37 Step 4: Final Verification and Validation (V&V) ..................37 Step 5: Closeout ...........................................37 What Do You Define First—Attributes or Operations? ................37 Developing the Structural Model Alongside the Behavioral Model .....38 Tailoring B.O.O.M. for Your Project ...............................38 What Do You Show Stakeholders? ................................41 Chapter Summary .............................................42 Endnotes.....................................................42 Chapter 4 Analyzing End-to-End Business Processes ..............43 Chapter Objectives .............................................43 Interviews During the Phases ....................................43 B.O.O.M. Steps ................................................45 Step 1 : The Initiation Phase .....................................45 What Happens During the Initiation Phase? ....................45 How Long Does the Initiation Phase Take? .....................45 Deliverables of the Initiation Step: BRD (Initiation Version) ........45 Step 1a: Model Business Use Cases ................................46 Table of Contents xi How Do You Document Business Use Cases? ....................47 Step 1ai: Identify Business Use Cases (Business Use-Case Diagram) ......47 Other Model Elements ......................................48 Putting Theory into Practice .....................................48 Case Study D1: Business Use-Case Diagrams ........................49 Step 1aii: Scope Business Use Cases (Activity Diagram) ...............63 Activity Diagrams for Describing Business Use Cases ..............65 Case Study D2: Business Use-Case Activity Diagram with Partitions (Swimlanes) ......................................73 Chapter Summary .............................................78 Endnotes.....................................................78 Chapter 5 Scoping the IT Project with System Use Cases ...........79 Chapter Objectives .............................................79 Step 1 b: Model System Use Cases .................................79 Step 1bi: Identify Actors (Role Map) ..............................80 Finding Actors .............................................80 Stereotypes and Actors .....................................81 The Role Map .............................................82 Modeling Actors with Overlapping Roles .......................82 What s the Point of Defining Generalized Actors? ...............84 Case Study E1: Role Map ........................................84 Step Ibii: Identify System Use-Case Packages (System Use-Case Diagram) ......................................86 What Criteria Are Used to Group System Use Cases into Packages? ....................................86 Naming Use-Case Packages ..................................86 Diagramming System Use-Case Packages .......................87 What If a Use-Case Package Is Connected to All of the Specialized Actors of a Generalized Actor? .............88 Case Study E2: System Use-Case Packages ..........................89 Step 1biii: Identify System Use Cases (System Use-Case Diagram) .......91 Features of System Use Cases ................................91 What Is the Purpose of Segmenting the User Requirements into System Use Cases? ..................92 Modeling System Use Cases ..................................92 Is There a Rule of Thumb for How Many System Use Cases a Project Would Have? ..................95 Case Study E3: System Use-Case Diagrams ..........................95 Step 1c: Begin Structural Model (Class Diagrams for Key Business Classes) .........................101 Step 1d: Set Baseline for Discovery (BRD/lnitiation) .................101 Chapter Summary ............................................102 Endnotes....................................................102 xii Table of Contents Chapter 6 Storyboarding the User s Experience .................103 Chapter Objectives ............................................103 Step 2: Discovery .............................................104 Lifecycle Considerations ....................................104 Step 2ai: Describe System Use Cases ..........................104 The Use-Case Description Template ..............................105 The Fundamental Approach Behind the Template ..............106 Documenting the Basic Flow ....................................109 Use-Case Writing Guidelines ................................109 Basic Flow Example: CPP System/Review Case Report ............110 Documenting Alternate Flows ..................................111 Typical Alternate Flows ....................................111 Alternate Flow Documentation ..............................112 Example of Use Case with Alternate Flows: CPP System/Review Case Report .............................113 Documenting an Alternate of an Alternate ...................114 Documenting Exception Flows ..................................114 Guidelines for Conducting System Use-Case Interviews ..............115 Activity Diagrams for System Use Cases ...........................115 Related Artifacts .............................................115 Decision Tables ...........................................116 Case Study F1: Decision Table ...................................119 Decision Trees ............................................122 Case Study F2: Decision Tree ....................................123 Condition/Response Table ..................................124 Business Rules ............................................124 Advanced Use-Case Features ....................................125 Include ..................................................126 Extend ..................................................129 Generalized Use Case ......................................133 Case Study F3: Advanced Use-Case Features .......................136 Chapter Summary ............................................138 Endnotes....................................................138 Chapter 7 Lifecycle Requirements for Key Business Objects .......141 Chapter Objectives ............................................141 What Is a State-Machine Diagram? ..............................142 Step 2aii: 1. Identify States of Critical Objects ......................144 Types of States ...........................................144 Case Study G1: States ..........................................145 Step 2aii: 2. Identify State Transitions ............................147 Depicting State Transitions in UML ...........................147 Mapping State-Machine Diagrams to System Use Cases ..........149 Table of Contents xiii Case Study G2: Transitions ......................................150 Step 2a¡¡: 3. Identify State Activities ..............................153 Case Study G3: State Activities ..................................155 Step 2aii: 4. Identify Composite States ............................157 Case Study G4: Composite States ................................158 Step 2aii: 5. Identify Concurrent States ...........................160 Concurrent State Example ..................................160 Chapter Summary ............................................161 Endnotes....................................................162 Chapter 8 Gathering Across-the-Board Business Rules with Class Diagrams ..........................163 Chapter Objectives ............................................163 Step 2b: Structural Analysis .....................................164 FAQs about Structural Analysis ..............................165 Step 2bi: Identify Entity Classes .................................166 FAQs about Entity Classes ..................................167 Indicating a Class in UML ...................................167 Naming Conventions ......................................167 Grouping Classes into Packages ..............................168 The Package Diagram ......................................169 Why It s Worth Pausing to Do Some Structural Modeling When Stakeholders Introduce New Terms ............169 Interview Questions for Finding Classes .......................170 Challenge Questions .......................................170 Supporting Class Documentation ............................171 Case Study H1: Entity Classes ...................................172 Step 2bii: Model Generalizations ................................175 Subtyping ...............................................175 Generalization ...........................................175 Case Study H2: Generalizations .................................179 Step 2biii: Model Transient Roles ................................180 Example of Transient Role ..................................181 How Does a Transient Role Differ from a Specialization? .........181 Some Terminology ........................................182 Why Indicate Transient Roles? ...............................182 Rules about Transient Roles .................................182 Indicating Transient Roles ..................................182 Sources of Information for Finding Transient Roles ..............182 Interview Questions for Determining Transient Roles ............183 What If a Group of Specialized Classes Can All Play the Same Role? . .183 Case Study H3: Transient Roles ..................................184 xiv Table of Contents Step 2biv: Model Whole/Part Relationships ........................186 The Whole Truth ........................................186 Examples of Whole/Part Relationships ........................186 Why Indicate Whole/Part Relationships? ......................186 How Far Should You Decompose a Whole into Its Parts? .........187 Sources of Information for Finding Aggregation and Composite Aggregation ................................187 Rules Regarding Aggregation and Composite Aggregation .......187 Indicating Aggregation and Composite Aggregation in the UML ...................................187 The Composite Structure Diagram ...............................188 Interview Questions for Determining Aggregation and Composite Aggregation ................................189 Challenge Question .......................................190 Case Study H4: Whole/Part Relationships .........................190 Step 2bv: Analyze Associations ..................................192 Examples of Association ....................................192 Why Indicate Association? ..................................192 Why Isn t It the Developers Job to Find Associations? ...........193 Discovering Associations ...................................193 Rules Regarding Associations ...............................193 The Association Must Reflect the Business Reality ...............195 Redundant Association Rule of Thumb .......................196 Exception to the Rule of Thumb .............................196 Case Study H5: Associations ....................................199 Step 2bvi: Analyze Multiplicity ..................................202 Example of Multiplicity ....................................202 Why Indicate Multiplicity? ..................................202 Indicating Multiplicity in the UML ...........................202 Rules Regarding Multiplicity ................................203 Sources of Information for Finding Multiplicity .................204 The Four Interview Questions for Determining Multiplicity .......204 Case Study H6: Multiplicity .....................................205 Chapter Summary ............................................208 Endnotes....................................................209 Chapter 9 Optimizing Consistency and Reuse in the Requirements Documentation ............213 Chapter Objectives ............................................213 Where Do You Go from Here? ..................................214 Does the Business Analyst Need to Put Every Attribute and Operation in the Structural Model? ..............214 Table of Contents xv Step 2bv¡¡: Link System Use Cases to the Structural Model ...........215 How Do You Find the Modeling Elements Involved in a System Use Case? ......................................215 How Do You Document the Links Between System Use Cases and the Structural Model? .........................215 Case Study 11: Link System Use Cases to the Structural Model ........216 Step 2bviii: Add Attributes .....................................221 Example .................................................221 Why Indicate Attributes? ...................................221 Don t Verification Rules about Attributes Belong with the System Use-Case Documentation? .............221 Sources of Information for Finding Attributes ..................222 Rules for Assigning Attributes ...............................222 Derived Attributes ........................................223 Indicating Attributes in the UML ............................223 Meta-Attributes ..............................................225 Case Study I2: Add Attributes ...................................226 Step 2bix: Add Lookup Tables ...................................231 Why Analyze Lookup Tables? ...............................231 Example .................................................231 Rules for Analyzing Lookup Tables ...........................231 Challenge Question .......................................232 Indicating Lookup Tables in the UML .........................232 Case Study ІЗ: Analyze Lookup Tables ............................233 Step 2bx: Add Operations ......................................236 An Example from the Case Study ............................236 How to Distribute Operations ...............................237 Case Study I4: Distribute Operations .............................238 Step 2bxi: Revise Class Structure .................................241 Rules for Reviewing Structure ...............................242 Challenge Question .......................................242 Case Study I5: Revise Structure ..................................242 Chapter Summary ............................................244 Endnotes....................................................244 Chapter 10 Designing Test Cases and Completing the Project .......245 Chapter Objectives ............................................245 Step 2c: Specify Testing ........................................246 Who Does These Tests and How Does the BA Fit In? .............246 What Is Testing? ..........................................247 General Guidelines ........................................247 Structured Testing .........................................248 When Is Testing Performed? ................................248 xvi Table of Contents Principles of Structured Testing (Adapted for 00) ..............248 Structured Walkthroughs ...................................250 Requirements-Based (Black-Box) Testing ......................252 Test Template ............................................253 Decision Tables for Testing .....................................254 Case Study J1: Deriving Test Cases from Decision Tables .............255 Boundary-Value Analysis .......................................256 Case Study J2: Select Test Data Using Boundary-Value Analysis .......258 White-Box Testing ............................................260 Who Does White-Box Testing? ..............................260 Limitations of White-Box Testing ............................260 White-Box Coverage Quality Levels ..........................260 Sequencing of White-Box Tests ..............................261 System Tests .................................................263 Beyond the System Tests .......................................266 Step 2d: Specify Implementation Plan ............................267 Post-Implementation Follow-Up .............................268 Step 2e: Set Baseline for Development ...........................268 Chapter Summary ............................................268 Endnotes....................................................270 Chapter 11 What Developers Do with Your Requirements .........271 Chapter Objectives ............................................271 OO Patterns .................................................272 Examples ................................................272 Visibility ....................................................272 Example .................................................273 Visibility Options ..........................................273 Control Classes ...............................................274 Boundary Classes .............................................274 Sequence Diagrams ...........................................274 Example: A Sequence Diagram ..............................275 Communication Diagrams ......................................277 Other Diagrams ..............................................277 Timing Diagrams ..........................................278 Deployment Diagrams .....................................278 Layered Architecture ..........................................278 Monolithic, Two-Tier, Three-Tier, and N-Tier Architecture .........279 Interfaces ...................................................279 Міх -Ins ..................................................... 280 Implementing 00 Using an 00 Language ........................280 Implementing OO Using Procedural Languages ....................281 Table of Contents xvii Implementing a Database from a Structural OO Model Using an RDBMS ........................................281 Chapter Summary ............................................281 Endnotes....................................................282 Appendix A The B.O.O.M. Process ..............................283 1 : Initiation ..................................................284 2: Discovery ..................................................284 Appendix В Business Requirements Document (BRD) Template ......287 Business Requirements Document (BRD)..........................288 Table of Contents .............................................289 Version Control ..............................................291 Executive Summary ...........................................292 Scope .......................................................294 Risk Analysis .................................................295 Business Case ................................................296 Timetable ...................................................296 Business Use Cases ............................................296 Actors ......................................................296 User Requirements ............................................298 State-Machine Diagrams .......................................301 Nonfunctional Requirements ...................................301 Business Rules ................................................302 State Requirements ...........................................302 Structural Model .............................................303 Test Plan ....................................................304 Implementation Plan ..........................................305 End-User Procedures ..........................................306 Post Implementation Follow-Up .................................306 Other Issues .................................................306 Sign-Off .....................................................306 Endnote ....................................................306 Appendix С Business Requirements Document Example: CPP Case Study ...................................307 Business Requirements Document (BRD)..........................308 Table of Contents .............................................309 Version Control ..............................................312 Executive Summary ...........................................313 Scope .......................................................314 Risk Analysis .................................................316 xviii Table of Contents Business Case ................................................318 Timetable ...................................................318 Business Use Cases ............................................319 Actors ......................................................323 User Requirements ............................................324 State-Machine Diagrams .......................................332 Nonfunctional Requirements ...................................333 Business Rules ................................................334 State Requirements ...........................................334 Structural Model .............................................334 Test Plan ....................................................341 Implementation Plan ..........................................341 End-User Procedures ..........................................342 Post Implementation Follow-Up .................................342 Other Issues .................................................342 Sign-Off .....................................................342 Appendix D Decision Table Template ............................343 Appendix E Test Script Template ...............................345 Test Template ................................................345 Appendix F Glossary of Symbols ...............................347 Appendix G Glossary of Terms and Further Reading ...............353 Index ...........................................359
any_adam_object	1
author	Podeswa, Howard
author_facet	Podeswa, Howard
author_role	aut
author_sort	Podeswa, Howard
author_variant	h p hp
building	Verbundindex
bvnumber	BV035679984
callnumber-first	Q - Science
callnumber-label	QA76
callnumber-raw	QA76.9.O35
callnumber-search	QA76.9.O35
callnumber-sort	QA 276.9 O35
callnumber-subject	QA - Mathematics
classification_rvk	ST 515
ctrlnum	(OCoLC)463075094 (DE-599)BVBBV035679984
dewey-full	005.117
dewey-hundreds	000 - Computer science, information, general works
dewey-ones	005 - Computer programming, programs, data, security
dewey-raw	005.117
dewey-search	005.117
dewey-sort	15.117
dewey-tens	000 - Computer science, information, general works
discipline	Informatik
edition	2. ed.
format	Book
fullrecord	<?xml version="1.0" encoding="UTF-8"?><collection xmlns="http://www.loc.gov/MARC21/slim"><record><leader>01861nam a2200481zc 4500</leader><controlfield tag="001">BV035679984</controlfield><controlfield tag="003">DE-604</controlfield><controlfield tag="005">20091026 </controlfield><controlfield tag="007">t</controlfield><controlfield tag="008">090817s2010 xxu \|\|\|\| 00\|\|\| eng d</controlfield><datafield tag="020" ind1=" " ind2=" "><subfield code="a">9781598638684</subfield><subfield code="c">pbk</subfield><subfield code="9">978-1-59863-868-4</subfield></datafield><datafield tag="020" ind1=" " ind2=" "><subfield code="a">1598638688</subfield><subfield code="9">1-59863-868-8</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(OCoLC)463075094</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(DE-599)BVBBV035679984</subfield></datafield><datafield tag="040" ind1=" " ind2=" "><subfield code="a">DE-604</subfield><subfield code="b">ger</subfield><subfield code="e">aacr</subfield></datafield><datafield tag="041" ind1="0" ind2=" "><subfield code="a">eng</subfield></datafield><datafield tag="044" ind1=" " ind2=" "><subfield code="a">xxu</subfield><subfield code="c">US</subfield></datafield><datafield tag="049" ind1=" " ind2=" "><subfield code="a">DE-473</subfield></datafield><datafield tag="050" ind1=" " ind2="0"><subfield code="a">QA76.9.O35</subfield></datafield><datafield tag="082" ind1="0" ind2=" "><subfield code="a">005.117</subfield><subfield code="2">22</subfield></datafield><datafield tag="084" ind1=" " ind2=" "><subfield code="a">ST 515</subfield><subfield code="0">(DE-625)143677:</subfield><subfield code="2">rvk</subfield></datafield><datafield tag="100" ind1="1" ind2=" "><subfield code="a">Podeswa, Howard</subfield><subfield code="e">Verfasser</subfield><subfield code="4">aut</subfield></datafield><datafield tag="245" ind1="1" ind2="0"><subfield code="a">UML for the IT business analyst</subfield><subfield code="b">a practical guide to requirements gathering using the unified modelling language</subfield><subfield code="c">Howard Podeswa</subfield></datafield><datafield tag="250" ind1=" " ind2=" "><subfield code="a">2. ed.</subfield></datafield><datafield tag="264" ind1=" " ind2="1"><subfield code="a">Australia [u.a.]</subfield><subfield code="b">Course Technology</subfield><subfield code="c">2010</subfield></datafield><datafield tag="300" ind1=" " ind2=" "><subfield code="a">XXV, 372 S.</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="650" ind1=" " ind2="4"><subfield code="a">Wirtschaft</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Business</subfield><subfield code="x">Computer network resources</subfield><subfield code="v">Case studies</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Object-oriented methods (Computer science)</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">UML (Computer science)</subfield></datafield><datafield tag="650" ind1="0" ind2="7"><subfield code="a">Betriebsanalyse</subfield><subfield code="0">(DE-588)4006164-4</subfield><subfield code="2">gnd</subfield><subfield code="9">rswk-swf</subfield></datafield><datafield tag="650" ind1="0" ind2="7"><subfield code="a">Informationstechnik</subfield><subfield code="0">(DE-588)4026926-7</subfield><subfield code="2">gnd</subfield><subfield code="9">rswk-swf</subfield></datafield><datafield tag="650" ind1="0" ind2="7"><subfield code="a">UML</subfield><subfield code="0">(DE-588)4469781-8</subfield><subfield code="2">gnd</subfield><subfield code="9">rswk-swf</subfield></datafield><datafield tag="655" ind1=" " ind2="7"><subfield code="0">(DE-588)4522595-3</subfield><subfield code="a">Fallstudiensammlung</subfield><subfield code="2">gnd-content</subfield></datafield><datafield tag="689" ind1="0" ind2="0"><subfield code="a">Informationstechnik</subfield><subfield code="0">(DE-588)4026926-7</subfield><subfield code="D">s</subfield></datafield><datafield tag="689" ind1="0" ind2="1"><subfield code="a">Betriebsanalyse</subfield><subfield code="0">(DE-588)4006164-4</subfield><subfield code="D">s</subfield></datafield><datafield tag="689" ind1="0" ind2="2"><subfield code="a">UML</subfield><subfield code="0">(DE-588)4469781-8</subfield><subfield code="D">s</subfield></datafield><datafield tag="689" ind1="0" ind2=" "><subfield code="5">DE-604</subfield></datafield><datafield tag="856" ind1="4" ind2="2"><subfield code="m">Digitalisierung UB Bamberg</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=017734263&sequence=000002&line_number=0001&func_code=DB_RECORDS&service_type=MEDIA</subfield><subfield code="3">Inhaltsverzeichnis</subfield></datafield><datafield tag="999" ind1=" " ind2=" "><subfield code="a">oai:aleph.bib-bvb.de:BVB01-017734263</subfield></datafield></record></collection>
genre	(DE-588)4522595-3 Fallstudiensammlung gnd-content
genre_facet	Fallstudiensammlung
id	DE-604.BV035679984
illustrated	Not Illustrated
indexdate	2024-07-09T21:43:15Z
institution	BVB
isbn	9781598638684 1598638688
language	English
oai_aleph_id	oai:aleph.bib-bvb.de:BVB01-017734263
oclc_num	463075094
open_access_boolean
owner	DE-473 DE-BY-UBG
owner_facet	DE-473 DE-BY-UBG
physical	XXV, 372 S.
publishDate	2010
publishDateSearch	2010
publishDateSort	2010
publisher	Course Technology
record_format	marc
spelling	Podeswa, Howard Verfasser aut UML for the IT business analyst a practical guide to requirements gathering using the unified modelling language Howard Podeswa 2. ed. Australia [u.a.] Course Technology 2010 XXV, 372 S. txt rdacontent n rdamedia nc rdacarrier Wirtschaft Business Computer network resources Case studies Object-oriented methods (Computer science) UML (Computer science) Betriebsanalyse (DE-588)4006164-4 gnd rswk-swf Informationstechnik (DE-588)4026926-7 gnd rswk-swf UML (DE-588)4469781-8 gnd rswk-swf (DE-588)4522595-3 Fallstudiensammlung gnd-content Informationstechnik (DE-588)4026926-7 s Betriebsanalyse (DE-588)4006164-4 s UML (DE-588)4469781-8 s DE-604 Digitalisierung UB Bamberg application/pdf http://bvbr.bib-bvb.de:8991/F?func=service&doc_library=BVB01&local_base=BVB01&doc_number=017734263&sequence=000002&line_number=0001&func_code=DB_RECORDS&service_type=MEDIA Inhaltsverzeichnis
spellingShingle	Podeswa, Howard UML for the IT business analyst a practical guide to requirements gathering using the unified modelling language Wirtschaft Business Computer network resources Case studies Object-oriented methods (Computer science) UML (Computer science) Betriebsanalyse (DE-588)4006164-4 gnd Informationstechnik (DE-588)4026926-7 gnd UML (DE-588)4469781-8 gnd
subject_GND	(DE-588)4006164-4 (DE-588)4026926-7 (DE-588)4469781-8 (DE-588)4522595-3
title	UML for the IT business analyst a practical guide to requirements gathering using the unified modelling language
title_auth	UML for the IT business analyst a practical guide to requirements gathering using the unified modelling language
title_exact_search	UML for the IT business analyst a practical guide to requirements gathering using the unified modelling language
title_full	UML for the IT business analyst a practical guide to requirements gathering using the unified modelling language Howard Podeswa
title_fullStr	UML for the IT business analyst a practical guide to requirements gathering using the unified modelling language Howard Podeswa
title_full_unstemmed	UML for the IT business analyst a practical guide to requirements gathering using the unified modelling language Howard Podeswa
title_short	UML for the IT business analyst
title_sort	uml for the it business analyst a practical guide to requirements gathering using the unified modelling language
title_sub	a practical guide to requirements gathering using the unified modelling language
topic	Wirtschaft Business Computer network resources Case studies Object-oriented methods (Computer science) UML (Computer science) Betriebsanalyse (DE-588)4006164-4 gnd Informationstechnik (DE-588)4026926-7 gnd UML (DE-588)4469781-8 gnd
topic_facet	Wirtschaft Business Computer network resources Case studies Object-oriented methods (Computer science) UML (Computer science) Betriebsanalyse Informationstechnik UML Fallstudiensammlung
url	http://bvbr.bib-bvb.de:8991/F?func=service&doc_library=BVB01&local_base=BVB01&doc_number=017734263&sequence=000002&line_number=0001&func_code=DB_RECORDS&service_type=MEDIA
work_keys_str_mv	AT podeswahoward umlfortheitbusinessanalystapracticalguidetorequirementsgatheringusingtheunifiedmodellinglanguage

Verfügbarkeit

Es ist kein Print-Exemplar vorhanden.

Fernleihe Bestellen Achtung: Nicht im THWS-Bestand! Inhaltsverzeichnis

MARC

Datensatz im Suchindex

Es ist kein Print-Exemplar vorhanden.

Ähnliche Einträge