UML Requirements Modeling for Business Analysts: Steps to Modeling Success

This book provides you with a collection of best practices, guidelines, and tips for using the Unified Modeling Language (UML) for business analysis. The contents have been assembled over the years based on experience and documented best practices. Over sixty easy to understand UML diagram examples will help you to apply these ideas immediately. If you use, expect to use, or think you should use the Unified Modeling Language (UML) or use cases in your business analysis activities, this book will help you:

  • communicate more succinctly and effectively with your stakeholders including your software development team,
  • increase the likelihood that your requirements will be reviewed and understood,
  • reduce requirements analysis, documentation, and review time.
  • The first three chapters explain the reasons for utilizing the UML for business analysis, present a brief history of the UML and its diagram categories, and describe a set of general modeling guidelines and tips applicable to all of the UML diagram types. Each of the next thirteen chapters is dedicated to a different UML diagram type:

    1. Use Case Diagrams
    2. Activity Diagrams
    3. Interaction Overview Diagrams
    4. Class Diagrams
    5. Object Diagrams
    6. State Machine Diagrams
    7. Timing Diagrams
    8. Sequence Diagrams
    9. Communication Diagrams
    10. Composite Structure Diagrams
    11. Component Diagrams
    12. Deployment Diagrams
    13. Package Diagrams

    The next two chapters explain additional diagram types that are important for business analysts and that can be created using UML notation:

  • Context Diagrams using Communication diagram notation
  • Data Models using Class diagram notation
  • These chapters are followed by a chapter that describes criteria for selecting the various diagram types. The final chapter presents a case study.

    1112351566
    UML Requirements Modeling for Business Analysts: Steps to Modeling Success

    This book provides you with a collection of best practices, guidelines, and tips for using the Unified Modeling Language (UML) for business analysis. The contents have been assembled over the years based on experience and documented best practices. Over sixty easy to understand UML diagram examples will help you to apply these ideas immediately. If you use, expect to use, or think you should use the Unified Modeling Language (UML) or use cases in your business analysis activities, this book will help you:

  • communicate more succinctly and effectively with your stakeholders including your software development team,
  • increase the likelihood that your requirements will be reviewed and understood,
  • reduce requirements analysis, documentation, and review time.
  • The first three chapters explain the reasons for utilizing the UML for business analysis, present a brief history of the UML and its diagram categories, and describe a set of general modeling guidelines and tips applicable to all of the UML diagram types. Each of the next thirteen chapters is dedicated to a different UML diagram type:

    1. Use Case Diagrams
    2. Activity Diagrams
    3. Interaction Overview Diagrams
    4. Class Diagrams
    5. Object Diagrams
    6. State Machine Diagrams
    7. Timing Diagrams
    8. Sequence Diagrams
    9. Communication Diagrams
    10. Composite Structure Diagrams
    11. Component Diagrams
    12. Deployment Diagrams
    13. Package Diagrams

    The next two chapters explain additional diagram types that are important for business analysts and that can be created using UML notation:

  • Context Diagrams using Communication diagram notation
  • Data Models using Class diagram notation
  • These chapters are followed by a chapter that describes criteria for selecting the various diagram types. The final chapter presents a case study.

    44.95 In Stock
    UML Requirements Modeling for Business Analysts: Steps to Modeling Success

    UML Requirements Modeling for Business Analysts: Steps to Modeling Success

    by Norman Daoust
    UML Requirements Modeling for Business Analysts: Steps to Modeling Success

    UML Requirements Modeling for Business Analysts: Steps to Modeling Success

    by Norman Daoust

    Paperback

    $44.95 
    • SHIP THIS ITEM
      In stock. Ships in 1-2 days.
    • PICK UP IN STORE

      Your local store may have stock of this item.

    Related collections and offers


    Overview

    This book provides you with a collection of best practices, guidelines, and tips for using the Unified Modeling Language (UML) for business analysis. The contents have been assembled over the years based on experience and documented best practices. Over sixty easy to understand UML diagram examples will help you to apply these ideas immediately. If you use, expect to use, or think you should use the Unified Modeling Language (UML) or use cases in your business analysis activities, this book will help you:

  • communicate more succinctly and effectively with your stakeholders including your software development team,
  • increase the likelihood that your requirements will be reviewed and understood,
  • reduce requirements analysis, documentation, and review time.
  • The first three chapters explain the reasons for utilizing the UML for business analysis, present a brief history of the UML and its diagram categories, and describe a set of general modeling guidelines and tips applicable to all of the UML diagram types. Each of the next thirteen chapters is dedicated to a different UML diagram type:

    1. Use Case Diagrams
    2. Activity Diagrams
    3. Interaction Overview Diagrams
    4. Class Diagrams
    5. Object Diagrams
    6. State Machine Diagrams
    7. Timing Diagrams
    8. Sequence Diagrams
    9. Communication Diagrams
    10. Composite Structure Diagrams
    11. Component Diagrams
    12. Deployment Diagrams
    13. Package Diagrams

    The next two chapters explain additional diagram types that are important for business analysts and that can be created using UML notation:

  • Context Diagrams using Communication diagram notation
  • Data Models using Class diagram notation
  • These chapters are followed by a chapter that describes criteria for selecting the various diagram types. The final chapter presents a case study.


    Product Details

    ISBN-13: 9781935504245
    Publisher: Technics Publications, LLC
    Publication date: 09/01/2012
    Pages: 268
    Product dimensions: 7.80(w) x 9.90(h) x 0.80(d)

    About the Author

    Norman Daoust is a business analyst trainer, requirements modeler, data modeler, healthcare electronic data exchange specialist, fretted instrument specialist, and organic gardener. He is the principal consultant for Daoust Associates, a company based in Cambridge, Massachusetts, United States. He specializes in business analyst training, information modeling, and healthcare systems data integration.

    Table of Contents

    CHAPTER 2: UML Modeling for Business Analysis 11
    UML History 12
    UML Diagram Categories 12
    CHAPTER 3: General UML Diagram Guidelines 15
    Guidelines 15
    Diagram Notation 16
    Diagram Tips 18
    How-to-Model Tips 19
    Naming Guidelines 20
    CHAPTER 4: Example Model Introduction 21
    Somestate Department of Motor Vehicles Glossary 21
    Somestate Department of Motor Vehicles Business Rules 22
    CHAPTER 5: Use Case Models 23
    Purpose 23
    Guidelines 24
    Diagram Notation 25
    Diagram Examples 30
    Diagram Tips 33
    Use Case Template 34
    Use Case Text Example 37
    Use Case Text Formats 40
    How-to-Model Tips 42
    Naming Guidelines 48
    Modeling Process Summary 50
    Case Study Example Diagram 53
    Relationship to Other UML Diagrams 54
    CHAPTER 6: Activity Diagrams 55
    Purpose 55
    Guidelines 55
    Diagram Notation 56
    Diagram Examples 65
    Diagram Tips 71
    How-to-Model Tips 74
    Naming Guidelines 74
    Modeling Process Summary 75
    Case Study Example Diagram 76
    Relationship to Other UML Diagrams 78
    CHAPTER 7: Interaction Overview Diagrams 79
    Purpose 79
    Guidelines 79
    Diagram Notation 80
    Diagram Example 86
    Diagram Tips 88
    How-to-Model Tips 88
    Naming Guidelines 89
    Modeling Process Summary 89
    Case Study Example Diagram 90
    Relationship to Other UML Diagrams 91
    CHAPTER 8: Class Models 93
    Purpose 94
    Guidelines 95
    Diagram Notation 95
    Diagram Examples 100
    Diagram Tips 102
    Data Element List, Partial Example 105
    Class Model, Partial Text Example 105
    How-to-Model Tips 107
    Naming Guidelines 111
    Modeling Process Summary 112
    Case Study Example Diagram 114
    Relationship to Other UML Diagrams 115

    CHAPTER 9: Object Diagrams 117
    Purpose 117
    Guidelines 117
    Diagram Notation 118
    Diagram Example 119
    Diagram Tips 120
    How-to-Model Tips 121
    Naming Guidelines 121
    Modeling Process Summary 121
    Case Study Example Diagram 123
    Relationship to Other UML Diagrams 124
    CHAPTER 10: State Machine Models 125
    Purpose 125
    Guidelines 125
    Diagram Notation 126
    Diagram Examples 130
    Diagram Tips 133
    State Machine Table Example 134
    How-to-Model Tips 134
    Naming Guidelines 135
    Modeling Process Summary 136
    Case Study Example Diagram 137
    Relationship to Other UML Diagrams 138
    CHAPTER 11: Timing Diagrams 139
    Purpose 139
    Guidelines 139
    Diagram Notation 139
    Diagram Examples 143
    Diagram Tips 145
    How-to-Model Tips 146
    Naming Guidelines 146
    Modeling Process Summary 146
    Case Study Example Diagram 147
    Relationship to Other UML Diagrams 148
    CHAPTER 12: Sequence Diagrams 149
    Purpose 149
    From the B&N Reads Blog

    Customer Reviews