Friday, May 24, 2013

   Quick Links:   Articles     MA Blog     Community Blog     Templates     Books     BA Humor     Events     Jobs     Interview Questions         RSS Feeds

Business Analyst Articles: Business Analysis & Systems Analysis

Resources




BA ARTICLE ARCHIVE
» May 2013 (6)
» April 2013 (8)
» March 2013 (4)
» February 2013 (6)
» January 2013 (6)
» December 2012 (5)
» November 2012 (7)
» October 2012 (6)
» September 2012 (6)
» August 2012 (5)
» July 2012 (9)
» June 2012 (5)
» May 2012 (9)
» April 2012 (7)
» March 2012 (7)
» February 2012 (5)
» January 2012 (7)
» December 2011 (6)
» November 2011 (6)
» October 2011 (8)
» September 2011 (6)
» August 2011 (8)
» July 2011 (7)
» June 2011 (7)
» May 2011 (6)
» April 2011 (8)
» March 2011 (6)
» February 2011 (5)
» January 2011 (6)
» December 2010 (5)
» November 2010 (9)
» October 2010 (5)
» September 2010 (6)
» August 2010 (8)
» July 2010 (6)
» June 2010 (6)
» May 2010 (10)
» April 2010 (5)
» March 2010 (8)
» February 2010 (7)
» January 2010 (7)
» December 2009 (7)
» November 2009 (7)
» October 2009 (6)
» September 2009 (8)
» August 2009 (10)
» July 2009 (9)
» June 2009 (5)
» May 2009 (10)
» April 2009 (5)
» March 2009 (12)
» February 2009 (8)
» January 2009 (6)
» December 2008 (9)
» November 2008 (8)
» October 2008 (9)
» September 2008 (4)
» August 2008 (6)
» July 2008 (8)
» June 2008 (17)
» May 2008 (12)
» April 2008 (7)
» March 2008 (21)
» February 2008 (16)
» January 2008 (13)
» December 2007 (9)
» November 2007 (25)
» October 2007 (2)
» September 2007 (23)
» August 2007 (12)
» July 2007 (11)
» June 2007 (7)
» May 2007 (6)
» April 2007 (9)
» March 2007 (5)
» February 2007 (3)
» January 2007 (2)
Articles and White Papers
Minimize


Current Articles | Search | Subscribe (RSS)

» The How To of Essential Modeling

Statistics:Article Rating (5876 Views) (2 Comments) Print
Posted: Wednesday, November 05, 2008
Categories: Activity Diagram, Structured Systems Analysis (DFDs, ERDs, etc.), Data Analysis & Modeling

 

Also called abstract or business modelling, essential modelling can be an extremely valuable tool for the business analyst. Instead of modelling how things are done (the current system), or how they might be done (a proposed system), we model what is done, or what might be done. For example the purpose of a Customer Service Department is to provide customers with a level of service they expect (or the company defines). Things like call centres and customer relationship management systems are the how of customer service.

This switch in thinking is not always easy as we have to ignore the very practical matters of procedures, methods, people, technology etc. The more involved we are in the system that we are looking at, the more difficult it may be to look at things conceptually. We have to look at what business objective we are trying to achieve. The business analyst who can do this - and explain it to clients and management - becomes a most valuable asset to the business.

Author: Derrick Brown

Read More ...

Rating
Comments
Derrick has done an excellent job in discussing the importance of focusing on the essential. It has been my experience that we, as BA's, often need to move away from the safety of being grounded in the implementation details and focus more on the essential - (as well as be more willing to move up the ladder of abstraction).

However, his diagrams also clearly illlustrate that use cases are ESSENTIALLY data flow diagrams without the data flows. This makes them, especially for larger scale analysis efforts, profoundly different. They are not basically the same thing.

The data flows are the lithmus test of compeltedness in functional diagrams. As a function is defined by its data inputs and outputs, without labeled data flows many logical "holes" in our understaning of functionality (whether we are working on a logical or physical model) remain hidden.

Tony

posted @ Wednesday, November 05, 2008 7:46 AM by ajmarkos


Hmm, the use cases he identifies merely (and unfortunately) mirror the names on the bubbles. Otherwise there is no direct connnection of any interest. Use Cases capture behaviour and have no sequential connections, just relationships.
DFDs are no longer the subject of mirth in the world of more advanced analysis, but they are still definitely outside the pale. The analysis of inputs and outputs, formerly required when computer programs were sequential processors, has been replaced by objects and variations on objects that use messages to communicate with each other and do things. We capture these messsages in sequence and/or interaction diagrams, derived from use cases.

posted @ Monday, November 10, 2008 3:29 PM by evitts


Only registered users may post comments.
  

Do you twitter?: If you want short updates on what's going on in the BA world and at ModernAnalyst.com, simply follow us on Twitter: http://twitter.com/ModernAnalyst



 

Privacy Statement  |  Terms Of Use
Copyright 2006-2013 by Modern Analyst Media LLC