UML Requirements Modeling for Business Analysts

Are you a business analyst? Do you know any business analysts or managers of business analysts? This book is written explicitly for people responsible for requirements.

• About the book
• Purchase the book
• Contents
• Backcover text
• Excerpts

About the book (from the Introduction)

Are you thinking to yourself, "Why should I learn these models, diagrams, and techniques?" If so, one or more of these reasons may apply to you:

• To communicate more succinctly and effectively with your stakeholders, including your software development team
• To increase the likelihood that your requirements will be reviewed and understood
• To make your job easier
• To set you apart from your peers
• To enhance your tool set with powerful diagramming techniques
• To make it easier for others to catch any omissions and errors your requirements might have, in less time and earlier in the project lifecycle
• To support the testing process and authoring of a user guide
• To document requirements in a manner that facilitates traceability to architecture and implementation artifacts
• To understand system designs and documentation which utilize the Unified Modeling Language (UML) notation.

Intended Audience

If you’re a business analyst seeking practical advice and guidance to capture and document requirements, or are interested in requirements modeling using UML or use cases, this book is for you! If you are a manager of business analysts, this book is also for you, since it will serve as your reference guide for assisting your business analysts in becoming more effective in their requirements analysis efforts.

Purchase

• Purchase options from the publisher's web site, Technics Publications
• Printed book format direct from the publisher, Technics Publications
• PDF format (immediate download) direct from the publisher, Technics Publications
• Printed book format from Amazon
• Online format from Google Play
• Kindle format from Amazon

Table of Contents, List of Figures, List of Tables

The below item opens as a PDF document in a new browser window.

• Table of Contents, List of Figures, List of Tables

Back Cover Text

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 us 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 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 the 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 Norman

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, www.DaoustAssociates.com, a company based in Cambridge, Massachusetts, United States. He specializes in business analysis training, information modeling, and healthcare systems data integration.

Excerpts

Excerpts are available from the publisher's web site, Technics Publications

Contact

Contact the author, Norman Daoust