REAL Business Requirements, Use Cases, and Decision Models
Featured articles showcased in this issue:
> BAs Will Falter Until They Learn to Discover REAL, Business Requirements
> What Every Business Analyst Needs to Know About Rulebook Management
> From Research to Implementation: Use Case Diagrams – Usage and Benefits
> Evolving the Decision Model With Views
> Webinar: Enhancing Business Process Management with Business Rules
> Conference: Requirements Engineering Conference
Also in this issue:
> More Business Analyst Humor
> Even more Resources for Business Analysts
> New Interview Questions
- Adrian Marchis, Editor
BAs Will Falter Until They Learn to Discover REAL, Business Requirements
by Robin F. Goldsmith, President of Go Pro Management Inc.
Widely-accepted conventional requirements models continue to create creep—changes to settled requirements which are a major cause of project overruns. Business Analysts and others will continue to encounter such creep so long as they follow flawed models focusing on requirements of a product or system being created without adequately also discovering the REAL, business requirements the product must satisfy to provide value...
What Every Business Analyst Needs to Know About Rulebook Management
by Ronald G. Ross, Principal, Business Rule Solutions, LLC
How many business rules does your company have? A hundred? A thousand? Ten thousand? More? How easy is it to change any one of those rules? How easy is it to determine where the rule is implemented? How easy is it to find out why it was implemented in the first place? Many companies today are starting to realize they have significant problems in managing their business rules...
From Research to Implementation: Use Case Diagrams – Usage and Benefits
by Brad Botz, Business Analyst & Principal at Prime Proficiency
Some people use them. Some people don't use them. Some people create them using sophisticated tools. Some use basic drawing programs. As part of the Unified Modeling Language, Use Case diagrams are often the starting point for many software projects. However, questions about Use Case diagrams still linger in the minds of many Business Analysts...
Evolving the Decision Model With Views
by Barbara von Halle & Larry Goldberg, KPI LLC
When introducing the Decision Model we frequently quote John Zachman’s classic gem “It occurs to me that once the underlying structure of a discipline is discovered, friction goes to zero! The processes (methodologies) become predictable and repeatable.”
UPCOMING WEBINARS & EVENTS
Webinar: Enhancing Business Process Management with Business Rules
Thu, Feb 18, 2010 10:00 AM Pacific (5:00 PM GMT) Register Now!
Requirements Engineering Conference
September 2010 - Sydney, Australia Get Info
MORE FROM ModernAnalyst.com
More Informative Articles
> Top Tips for Successful SOA (Service Oriented Architecture) Pilots
> Uncover the Hidden Truth in Your Data with Interactive Visual Analytics
> Complex Project Management
Recent Blog Posts
> Agile Development: What we can learn from property developers – or what they’ve learned from us
> Why Business Analysts Should Not Perform Quality Assurance
> Measuring the Success of Training Activities
Interesting Forum Posts
> Reusable Requirements Toolkit?
> Where to put Reporting requirements?
> Lets Create a Task!
Relevant Interview Questions
> What does the term 'Problem Domain' mean to a business analyst?
> What are the seven business analysis knowledge areas as defined by the BABOK v2.0?
> How is the Business Analysis Planning and Monitoring (BABOK v2.0) knowledge area defined?
Featured JOBs for Business Analysts
> Technical Business Analyst with ability to communicate with both business and development teams
> CRM Business Analyst responsible for the requirements processes for a Global CRM project
> Business Analyst for assessments for work requested by the DIRECTV Sales and Marketing and Operations group