UML Requirements Modeling for Business Analysts (Paperback)

Norman Daoust

ISBN 10: 193550424X / ISBN 13: 9781935504245

Published by Technics Publications LLC, Bradley Beach, 2012

About this Item

Paperback. 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 utilising the UML for business analysis, present a brief history of the UML and its diagram categories, and describe a set of general modelling 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: Use Case Diagrams; Activity Diagrams; Interaction Overview Diagrams; Class Diagrams; Object Diagrams; State Machine Diagrams; Timing Diagrams; Sequence Diagrams; Communication Diagrams; Composite Structure Diagrams; Component Diagrams; Deployment Diagrams; 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. This book provides you with a collection of best practices, guidelines, and tips for using the Unified Modeling Language (UML) for business analysis. Shipping may be from our UK warehouse or from our Australian or US warehouses, depending on stock availability.

Seller Inventory # 9781935504245

Bibliographic Details

• Title: UML Requirements Modeling for Business Analysts (Paperback)
• Publisher: Technics Publications LLC, Bradley Beach
• Publication Date: 2012
• Language: English
• ISBN 10: 193550424X
• ISBN 13: 9781935504245
• Binding: Paperback
• Edition: 1st Edition
• Condition: new

About this title

Synopsis

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.

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.