Business System Analysis Bookstore
In Association with Amazon.com
Help PicoSearch
Looking for Business Analysis Training

Business Modeling With UML: Business Patterns at Work

Buy the Book
Summary TOC Back Cover Look Inside Comments Reviews
Magnus Penker, Hans-Erik Eriksson
January 2000, John Wiley & Sons, Hardcover, 416 pages, ISBN 0471295515

Instructor-led, virtual, and self-paced training for Business Analysts What Do Business Analysts Do?
How to Gather, Analyze, and Define Business System Requirements
How to Model, Analyze, and Improve Business Processes
Introduction to Business Process Analysis
How to Model Business Processes using Context Diagrams
How to Model Business Processes with Swimlane Diagrams
How to Improve Business Processes using Process Models
How to Become Agile in Business Analysis
How to Model and Analyze Business System Data
How to Jump-Start Requirements Gathering with User Stories
How to Discover and Develop Use Cases
Introduction to Business Use Case Documentation and Modeling
How to Capture Functional Requirements with Use Cases and Diagrams
How to Clarify and Confirm Business Requirements with Use Cases
How to Develop and Use UML Models for Business Analysis
Introduction to UML Fundamentals for Business Analysts
Business Analysis and Requirements Gathering Blitz
e-Learning, virtual workshops and webinars Try our new Virtual Workshops and e-Coaching
for today's Business System Analysts (BA's) and Subject Matter Experts (SME's)

Summary
Buy the book

From the authors of UML Toolkit comes a nuts-and-bolts guide for applying UML's vast capabilities to business systems.

To perform effective business modeling and develop a successful information system, you need a reliable modeling language that allows you to establish the necessary components and satisfy all of management's concerns. You need UML. With its eagerly anticipated new set of business extensions and techniques, UML is the premiere language for both traditional business modeling and the later stages of analysis and design. Finally, only one modeling language is needed for every phase of project development.

This invaluable book, the first of its kind, provides in-depth guidance on business modeling as well as discussions of how patterns, business objects, business rules, CORBA, COM, and Java all fit in to help improve every stage of object-oriented software development.

UML (Unified Modeling Language) is a drawing tool to create "blueprints" for object-oriented systems. It has been officially adopted by the OMG. Think of UML as the AutoCAD of the computer industry. Where AutoCAD is used to create architectural blueprints for buildings, UML is used to diagram blueprints of object-oriented computer systems. Business Modeling is the first phase of software development with UML, in which business concerns are clearly outlined so that an information system with the appropriate Business Objects may be developed.

Topics covered: Business modeling basics, UML notation and Erickson-Penker Business Extensions, class diagrams and powertypes, object diagrams, statecharts, activity diagrams and swimlanes, sequence and collaboration diagrams, collaboration and use case diagrams, component and deployment diagrams, stereotypes, business architectures, business processes, resources, goals, business rules, Object Constraint Language (OCL) and collections, business views and patterns, business goal allocation, business goal decomposition, business goal-problem, and software architectures

 
analysis bookstore top
BA books: Table of Contents
Buy the book

Acknowledgments
Introduction

Chapter 1 Business Modeling
The Role of Models
UML
Business Process Modeling

Understanding the Business
Information System Support
Improvement
Innovation
Design New Processes
Outsourcing

Business Modeling with UML
Summary

Chapter 2 UML Primer
UML Basics
Unified Modeling Language
Class Diagram
Object Diagram
Statechart Diagram
Activity Diagram
Sequence Diagram
Collaboration Diagram
Use-Case Diagram
Component Diagram
Deployment Diagram

Extending UML
Stereotypes
Tagged Values
Constraints

Summary

Chapter 3 Modeling the Business Architecture
Architecting a Business
Good Architecture

Business Concepts
Eriksson-Penker Business Extensions
Business Processes
Resources
Goals
Business Rules
Relationships
General Mechanisms

Summary

Chapter 4 Business Views
Four Common Business Views
Business Vision View
Business Process View
Business Structure View
Business Behavior View

Summary

Chapter 5 Business Rules
Business Rule Syntax
Rules in UML

Object Constraint Language
Using OCL in Models
OCL Expressions
Navigation
Collections

Business Rules Categories
Derivations
Constraints
Existence

Fuzzy Business Rules
Summary

Chapter 6 Business Patterns
Types of Patterns
How Business Patterns Are Used

Pattern Categories
Pattern Form
The Patterns in This Book
Resource and Rule Patterns
Goal Patterns
Process Patterns

The Business Patterns Template
Name
Intent
Motivation
Applicability
Structure
Participants
Consequences
Example
Related Patterns
Source/Credit

Patterns in UML
Other Work in Patterns
Summary

Chapter 7 Resource and Rule Patterns
Actor-Role Pattern
Business Definitions Pattern
Business Event-Result History Pattern
Contract Pattern
Core-Representation Pattern
Document Pattern
Employment Pattern
Geographic Location Pattern
Organization and Party Pattern
Product Data Management Pattern
Thing-Information Pattern
Title-Item Pattern
Type-Object-Value Pattern
Summary

Chapter 8 Goal Patterns
Business Goal Alloction Pattern
Business Goal Decomposition Pattern
Business Goal-Problem Pattern
Summary

Chapter 9 Process Patterns
Basic Process Structure Pattern
Process Interaction Pattern
Process Feedback Pattern
Time-To-Customer Pattern
Process Layer Supply Pattern
Process Layer Control Pattern
Action Workflow Pattern
Process-Process Instance Pattern
Resource Use Pattern
Process Instance State Pattern
Summary

Chapter 10 From Business Architecture to Software Architecture
Software Development Process
What Is Software Architecture?
Myths about Software Architectures
Designing a Good Architecture

Modeling the Software Architecture
Software Architectural Views

Using the Business Architecture to Define the Software Architecture
Identify the Information Systems
Find Functional Requirements
Find Nonfunctional Requirements
Act as Basis for Analysis and Design
Identify Suitable Components

Summary

Chapter 11 A Business Model Example
Bob's Mail Order
Visions and Goals
Goal Model
Conceptual Model

Business Processes
Resources and Organization
Resource Modeling
Organizational Modeling

Process Decomposition
Support Systems
System Requirements
System Requirement Specification

Summary

Appendix A Eriksson-Penker Business Extensions
Views
Diagrams and Models
Stereotypes and Constraints
Tagged Values

Appendix B Business Patterns Summary

Resource and Rules Patterns
Goal Patterns
Process Patterns

Glossary
References
Index
 
analysis bookstore top
Back Cover
Buy the book

Following up on their bestselling book, UML Toolkit, Hans-Erik Eriksson and Magnus Penker now provide expert guidance on how to use UML to model your business systems. In this informative book, key business modeling concepts are presented, including how to define Business Rules with UML's Object Constraint Language (OCL) and how to use business models with use cases. The authors then provide 26 valuable Business Patterns along with an e-business case study that utilizes the techniques and patterns discussed in the book.

 
analysis bookstore top
Business System Analysis Books: Reviews
Buy the book

Amazon.com
Until now, the Unified Modeling Language (UML) has been primarily used to design software, but should you use it to model your entire business as well? That's the intriguing argument of Business Modeling with UML, a text that combines leading-edge enhancements to UML with some solid thinking about business. Written for any manager with some technical background, this book looks at the possibilities of UML used to model entire organizations.

The book makes a strong case for the advantages of modeling businesses in UML. With models, an organization can provide better software, define and implement new goals, and even decide whether to outsource certain operations. The Erickson-Penker Business Extensions for UML, invented by the authors and presented within the text, permit UML to document the entire business enterprise. This book shows how to model businesses, from business architecture to processes, business rules, and goals. Short case studies--for Web-centric and more traditional companies--are used to illustrate key concepts here.

Later sections of the book will perhaps take a little more background in software engineering to appreciate fully as the book presents a handful of business patterns, which offer reusable solutions to common problems (just like software patterns). The authors also look at how to leverage a business model to create better software.

In engineering, a new car is modeled and thoroughly tested on a computer before any physical prototype is ever built. As the authors point out, a business that has accurate models can test out new ideas cheaply and then adapt to changing market conditions quickly. This title makes a case that UML--a tool traditionally used by software developers--is ready to tackle the job. Read this notably informative and intelligent book to see the possible benefits of business modeling in UML for your organization. --Richard Dragan

 
analysis bookstore top
 
NEW RELEASES
Agile
Benchmarking
Best Practices
Business Systems Analysis
CASE
Data Analysis
  Data Models
Data Normalization
Data Repository
Entity Relationship Diagrams
Miscellaneous
Data Warehouse
Enterprise Architecture
Enterprise Resource Planning (ERP)
  Peoplesoft
SAP
Miscellaneous
Humor
Internet
  E-Commerce
Miscellaneous
Interviewing Techniques
Methodologies
  Information Engineering
Structured System Development
System Development Life Cycle (SDLC)
Miscellaneous
Object Oriented
  Business Objects
Object Oriented Analysis
Object Oriented Design
Object Oriented Modeling
Object Oriented Testing
State Transition Diagrams
Problem Analysis
Process Analysis
  Data Flow Diagrams
Decision Tables
Event Response Diagrams
Flowcharts
Process Models
Miscellaneous
Process Improvement (BPI)
Related Topics
  Knowledge Management
Philosophies
Request for Proposal (RFP)
Risk Management
Six Sigma
Software Reuse
Strategic Planning
Requirements
  Business Rules
Prototyping
Requirements Analysis
Requirements Definition
Requirements Documentation
Requirements Engineering
Requirements Gathering
Requirements Management
Requirements Traceability
System Specifications
User Interfaces
Miscellaneous
Test Management
  Defect Tracking
Test Planning
Testing Methodologies
Testing Tools
Validation & Verification
Miscellaneous
Testing Phases
  Acceptance Testing
Configuration Testing
Integration Testing
Performance Testing
System Testing
Unit Testing
Usability Testing
Testing Techniques
  Black Box Testing
Object Oriented Testing
Regression Testing
Test Cases
Test Data Engineering
Walkthroughs
White Box Testing
Miscellaneous
Unified Modeling Language (UML)
Usability Engineering
  Prototyping
Task Analysis
Usability Testing
User Interfaces
Miscellaneous
Use Cases
Workflow Analysis
Working in Teams
  Conducting Meetings
Facilitation
JAD
Rapid Application Development (RAD)
Miscellaneous
Search:
Keywords:
Home Links Add a book Request Link Exchange BA Skills Test Training Needs Assessment