Visualization

Challenge    When defining a software solution, certain challenges are encountered. The  one I consider that is present in all projects is establishing a common language  between all the stakeholders, however, in software engineering there are  specific diagrams already defined which are very useful when it comes to this  communication challenge.    The two I consider the most useful are: the business process diagram (BPM),  which might fit more the visualization approach, and the use cases diagram,  that is closer to the mind mapping one. For this assignment I will focus on the  BPM diagram.    Selection    As described by Angela Myer in week 1, the visualization tool allows us to think  in a nonverbal way, this is exactly why we chose it, it allowed us to go from a  basic abstraction of the problem to a complex flow and accelerated the  communication.    Application    At first, the engineering team listens to the customer needs and pains, trying to  refine the most accurate and simple model of the business processes and  taking notes for what is called “business rules”.    In order to ease the communication, all stakeholders made some drawings and,  as diagrams are a very common tool for different disciplines, it comes natural  to generate a draft of the BPM diagram, maybe not by employing the precise  standard but in such a way both the solution provider and the customer make  clear every point.    Then, the engineering team presented a draft of the BPM diagram, the software  analyst explained briefly the standard and the diagram in detail to confirm there  were not any misunderstandings between the stakeholders.    Other diagrams were presented during the meetings, though, throughout the  whole project we kept on refining the BPM diagram as it became central and  communication was faster and faster due to the familiarity with such a useful  standard set of symbols.

Insight    I had not had the chance to ponder the power of diagrams and visualization  tools because I assumed their use since I was at the school, mainly because I  have not taken the complete responsibility for a project. Notwithstanding, I can  foresee I will encounter communication difficulties that I will know how to tackle  in advance as from now on I will spend some time paying more attention to the  specific advantages of each diagram.    Approach    Making a deeper reflection on the application of the visualization approach, I  consider that the manager hit the mark when planning the digital presentation  for the meetings, as information was presented clear and precise to the  customer. I guess the biggest challenge is not to forget applying these tools, so  I can prevent eternal discussions I have been involved myself.


Visualization Challenge When defining a software solution , certain challenges are encountered . The one I consider that is present in all projects is establishing a common language between all the stakeholders , however , in software engineering there are specific diagrams already defined which are very useful when it comes to this communication challenge . The two I consider the most useful are : the business process diagram ( BPM ) , which might fit more the visualization approach , and the use cases diagram , that is closer to the mind mapping one . For this assignment I will focus on the BPM diagram . Selection As described by Angela Myer in week 1 , the visualization tool allows us to think in a nonverbal way , this is exactly why we chose it , it allowed us to go from a basic abstraction of the problem to a complex flow and accelerated the communication . Application At first , the engineering team listens to the customer needs and pains , trying to refine the most accurate and simple model of the business processes and taking notes for what is called “ business rules ” . In order to ease the communication , all stakeholders made some drawings and , as diagrams are a very common tool for different disciplines , it comes natural to generate a draft of the BPM diagram , maybe not by employing the precise standard but in such a way both the solution provider and the customer make clear every point . Then , the engineering team presented a draft of the BPM diagram , the software analyst explained briefly the standard and the diagram in detail to confirm there were not any misunderstandings between the stakeholders . Other diagrams were presented during the meetings , though , throughout the whole project we kept on refining the BPM diagram as it became central and communication was faster and faster due to the familiarity with such a useful standard set of symbols . Insight I had not had the chance to ponder the power of diagrams and visualization tools because I assumed their use since I was at the school , mainly because I have not taken the complete responsibility for a project . Notwithstanding , I can foresee I will encounter communication difficulties that I will know how to tackle in advance as from now on I will spend some time paying more attention to the specific advantages of each diagram . Approach Making a deeper reflection on the application of the visualization approach , I consider that the manager hit the mark when planning the digital presentation for the meetings , as information was presented clear and precise to the customer . I guess the biggest challenge is not to forget applying these tools , so I can prevent eternal discussions I have been involved myself .