000 06380cam a2200541Ii 4500
001 ocn870333319
003 OCoLC
005 20190328114807.0
006 m o d
007 cr cnu---unuuu
008 140212s2014 ne ob 001 0 eng d
040 _aOPELS
_beng
_erda
_epn
_cOPELS
_dIDEBK
_dYDXCP
_dN$T
_dE7B
_dUMI
_dCOO
_dCDX
_dCHVBK
_dDEBBG
_dEBLCP
_dDEBSZ
_dTEFOD
_dOCLCF
_dOCLCQ
_dMERUC
_dOCLCQ
_dOCLCO
_dU3W
_dD6H
_dCEF
_dINT
_dOCLCQ
_dWYU
_dOCLCQ
019 _a870950542
_a871321968
_a1065707135
020 _a9780124172937
_q(electronic bk.)
020 _a0124172938
_q(electronic bk.)
020 _z9780124186736
020 _z0124186734
035 _a(OCoLC)870333319
_z(OCoLC)870950542
_z(OCoLC)871321968
_z(OCoLC)1065707135
050 4 _aQA76.9.O35
_bW39 2014eb
072 7 _aCOM
_x051210
_2bisacsh
082 0 4 _a005.1/17
_223
100 1 _aWazlawick, Raul Sidnei,
_eauthor.
245 1 0 _aObject-oriented analysis and design for information systems : modeling with UML, OCL, and IFML /
_h[electronic resource]
_cRaul Sidnei Wazlawick.
264 1 _aAmsterdam :
_bElsevier, Morgan Kaufmann is an imprint of Elsevier,
_c2014.
300 _a1 online resource
336 _atext
_btxt
_2rdacontent
337 _acomputer
_bc
_2rdamedia
338 _aonline resource
_bcr
_2rdacarrier
504 _aIncludes bibliographical references and index.
520 _aObject-Oriented Analysis and Design for Information Systems clearly explains real object-oriented programming in practice. Expert author Raul Sidnei Wazlawick explains concepts such as object responsibility, visibility and the real need for delegation in detail. The object-oriented code generated by using these concepts in a systematic way is concise, organized and reusable. The patterns and solutions presented in this book are based in research and industrial applications. You will come away with clarity regarding processes and use cases and a clear understand of how to expand a use case. Wazlawick clearly explains clearly how to build meaningful sequence diagrams. Object-Oriented Analysis and Design for Information Systems illustrates how and why building a class model is not just placing classes into a diagram. You will learn the necessary organizational patterns so that your software architecture will be maintainable. Learn how to build better class models, which are more maintainable and understandable. Write use cases in a more efficient and standardized way, using more effective and less complex diagrams. Build true object-oriented code with division of responsibility and delegation.
588 0 _aPrint version record.
505 0 _aFront Cover; Object-Oriented Analysis and Design for Information Systems; Copyright Page; Contents; Acknowledgments; About the Author; Foreword; Preface; 1 Introduction; 1.1 This book; 1.2 Object-oriented systems development; 1.3 Unified Modeling Language (UML); 1.4 Unified Process (UP); 1.5 The process so far; 1.6 Questions; 2 Business Modeling; 2.1 Introduction to business modeling; 2.2 General view of the system; 2.3 Business use cases; 2.3.1 Business actors and business workers; 2.3.2 Automation opportunities; 2.4 Business activity diagram; 2.4.1 Basic elements; 2.4.2 Control flow nodes.
505 8 _a2.5 State-dependent aspects of a business2.6 Remarks; 2.7 The process so far; 2.8 Questions; 3 High-Level Requirements; 3.1 Introduction to high-level requirements; 3.2 System actors; 3.3 System use cases; 3.3.1 Single session; 3.3.2 Interactive; 3.3.3 Consistent result; 3.3.4 Essential; 3.3.5 Brief; 3.3.6 System boundary; 3.4 How to find system use cases in the business model; 3.5 Requirements; 3.5.1 Requirements elicitation; 3.5.2 Eliciting requirements is not design!; 3.5.3 Requirements challenges; 3.5.4 Evident and hidden functional requirements; 3.5.5 Nonfunctional requirements.
505 8 _a3.5.6 Permanence and transience of nonfunctional requirements3.5.7 Mandatory and desired requirements; 3.5.8 Supplementary requirements; 3.6 Preliminary conceptual model; 3.7 The process so far; 3.8 Questions; 4 Use Case Based Project Planning; 4.1 Introduction to effort estimation and risk analysis in software projects; 4.1.1 Ad hoc techniques; 4.1.2 Parametric techniques; 4.1.3 Risk analysis; 4.2 Use case point analysis; 4.2.1 UAW -- unadjusted actor weight; 4.2.2 UUCW -- unadjusted use case weight; 4.2.3 UUCP -- unadjusted use case points; 4.2.4 TCF -- technical complexity factor.
505 8 _a4.2.5 EF -- environmental factors4.2.6 UCP -- adjusted use case points; 4.2.7 Effort; 4.2.8 Calendar time and average team size; 4.2.9 Counting methods for detailed use cases; 4.3 Planning an iterative project; 4.3.1 Estimating the duration of iterations; 4.3.2 Number of iterations; 4.3.3 Effort per use case point; 4.3.4 Team load capacity; 4.3.5 Defining use case priority; 4.3.6 Planning phase and iterations; 4.4 The process so far; 4.5 Questions; 5 Expanded Use Cases; 5.1 Introduction to expanded use cases; 5.2 Main flow; 5.3 Alternate flows; 5.3.1 Scenarios; 5.3.2 Variants.
505 8 _a5.3.3 Exception handling5.4 Writing recommendations; 5.4.1 Essential versus real use case; 5.4.2 Explicit information; 5.4.3 Identification and selection; 5.4.4 Mandatory steps; 5.4.5 Complementary steps; 5.4.6 Unsuitable steps; 5.5 Included use cases and fragments; 5.6 Expansion of stereotyped use cases; 5.6.1 Report expanded; 5.6.2 CRUD expanded; 5.7 Other sections of an expanded use case; 5.7.1 Stakeholders; 5.7.2 Preconditions; 5.7.3 Success post-conditions; 5.7.4 Open issues; 5.8 System sequence diagrams; 5.8.1 Elements of a sequence diagram.
650 0 _aObject-oriented methods (Computer science)
650 7 _aCOMPUTERS
_xProgramming
_xObject Oriented.
_2bisacsh
650 7 _aObject-oriented methods (Computer science)
_2fast
_0(OCoLC)fst01042803
650 7 _aObjektorientierte Programmierung
_2gnd
_0(DE-588)4233947-9
650 7 _aSoftwareentwicklung
_2gnd
_0(DE-588)4116522-6
650 7 _aUML
_2gnd
_0(DE-588)4469781-8
650 7 _aOCL
_gProgrammiersprache
_2gnd
_0(DE-588)4680186-8
655 0 _aElectronic book.
655 4 _aElectronic books.
776 0 8 _iPrint version:
_aWazlawick, Raul Sidnei.
_tObject-oriented analysis and design for information systems
_z9780124186736
_w(DLC) 2013043354
_w(OCoLC)861211345
856 4 0 _3ScienceDirect
_uhttp://www.sciencedirect.com/science/book/9780124186736
999 _c246873
_d246873