Includes bibliographical references and index.

Object-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.

Print version record.

Front 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.

2.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.

3.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.

4.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.

5.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.