Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Data Analysis f...  A picture is worth a 1000 words
Previous Previous
 
Next Next
New Post 12/22/2009 10:02 AM
User is offline L M Smith
4 posts
No Ranking


A picture is worth a 1000 words 

In an article that I wrote for Modern Analyst last March about the Zachman Architecture with John Zachman <<http://bit.ly/6WRJnP>>  I talked about the value of models.

Here is a wonderful resource to describe some interesting types of pictures that can be used to describe data, information, concepts and other parts of an Enterprise Architecture or Requirements: http://www.visual-literacy.org/periodic_table/periodic_table.html

Thank you to Karen Lopez for sharing the information.

Twitter: SilverData

Loretta Mahon Smith

 
New Post 12/22/2009 5:55 PM
User is offline Jarett Hailes
155 posts
6th Level Poster




Re: A picture is worth a 1000 words 

Very neat, thanks for sharing Loretta!

 
New Post 2/25/2010 8:53 AM
User is offline Tony Markos
493 posts
5th Level Poster


Re: A picture is worth a 1000 words 

So, what is the essential difference between a Use Case, Data Flow Diagram, BPM diagram, BPMN diagram, and Activity Diagram?  If the framework can not address this basic, fundamental question (and it does not), then all it is doing is adding to the dysfunctional thinking that prevades - albiet under the guise of sophistication.

Tony Markos

 
New Post 2/25/2010 11:10 AM
User is offline L M Smith
4 posts
No Ranking


Re: A picture is worth a 1000 words 

I don't believe that the "Periodic table for Visualization Methods"  is a framework, it is just a reference tool for identifying different types of visual represtation techniques.  It is up to the Business Analyst to select the method that would best suit his or her audience's needs.  The website www.visual-literacy.org was developed to create course materials for fourteen universities on how to create good visual presentations.  And in reality, it is a great example of a visual way of introducing a large number of concepts to an untrained audience.

The essential differences of diagram types are (as far as I know) explained through the Business Analysts best practices, and other course work.

If the comment was regarding the actual Zachman Framework, my answer would be different.  John has always said that the framework provides the what of enterprise architecture; and that methodologies provide the "how to".  Whether you choose TOGAF, DODAF, or some other framework...and a BA would use the standard diagram choice for that methodology.

 

 

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Data Analysis f...  A picture is worth a 1000 words

Community Blog - Latest Posts

As Business Analysts in Agile teams, we often hear about Definition of Ready (DOR) and Definition of Done (DOD). But beyond the buzzwords, these two concepts are powerful tools to drive clarity, consistency, and quality in our work. Definition of Ready ensures a user story is truly ready for development. It answers: Is this story clear, feasible...
In today's fast-paced digital world, successful projects aren't just built on great code—they're built on clarity. And that clarity often comes from one key player: the Business Analyst. At the heart of every great product or system is a need—a business goal, a customer pain point, or a regulatory requirement. But busines...
I have always loved cooking. I learned from my Grandma June and her kitchen was her sanctuary, a small, warm sunlit space filled with jars of spices, stacks of cookbooks, and the comforting smell of something always on the stove or baking in the oven. Grandma June was as great a cook as she was a teacher to me. She never followed a recipe “to...

 






 

Copyright 2006-2025 by Modern Analyst Media LLC