Reflection on visualization 

 Challenge and selection 

 I get the help of the tool of visualization and visual thinking because it is the easiest and the   way that I am mostly talented in . I can get a shared and diverse idea of stakeholders and it   helps me to plan it overall . I usually use this on customers who are in an interest of developing   a software for their companies to make it efficient and so that they can provide their services   too using these programs . I use strawman technique for the questions that I ask from them   prior to start of the software development process which is the requirement gathering process .   Helps me to define the scope , boundaries relationship between the entities and the key   elements . 

 Application 

 Usually start the process with a straw man graphic of the problem domain . Ill draw from the   requirements which the client provides . The materials are voice records , use case scenarios , various   documentations of the requirements , and user stories . Plus the interviews . 

 If needed I might have to use various approaches like “ front - stage / back - stage ” and etc . The template I   often start with also has a column on the left to identify Partners and Value Chain Providers and a   column on the right to identify requirements , such as , the things what the client need in order to get   this project a success . So that I can map the users and what they want from this system to be developed .   Also I will have a column which specifies the propriety level of the requirement . So that I can inform the   developers what requirements are most crucial in the system . The straw man graphic is simple , using   simple shapes and icons available in Visio or on the Internet . If the front - stage / back - stage view does n’t   work , then I will create a different type of visual , either based on a high - level process flow with swim   lanes for different stakeholders , or another format for example ( Activity diagram with swim lanes ) . 

 For the activity , I will divide the stakeholders into participants each representing a different area of   interest of their requirements . Each group receives a set of sticky notes to make comments and get into   details of each requirement . I give them two - three questions to answer , like 1 ) What key elements are   missing from the graphic ? 2 ) What would you change about the graphic to make it more accurately   reflect your problem space ? 3 ) What key insights do you have about the relationships between the   entities in your problem space ? I give them some time to discuss the questions and mark up the graphic .   As each group intelligences out , I record shared aims in the visions of each collection , and then   additional intuitions that come from the group conversation on an other copy of the graphic . After the   meeting , I convert each group ’s set of sticky notes as an artifact , create a view that syndicates the   common and new thoughts from the group session . 

 Insight & Approach 

 I have learned from having this exercise with several groups of clients that , while the graphic ,   specifically the revised graphic that includes their comment is significant to strengthen the   comprehension of the problem . The more valuable feature of the activity is the shared insights and   shared learning that occurs while they are working to define their problem space . The graphics can fast   recognize where they are in the graphic and can more vastly increase new insights about relationships   between key entities . They can also identify variables in the problem scope . Later I learnt that the   greatest valuable aspect is the shared insights and learning , I would use the visualization activity as a   preliminary fact for a sequence of design thinking activities . Then the revised graphic . 


EMAIL: 
ID_NUM: 
NAME_STUDENT: 
PHONE_NUM: 
STREET_ADDRESS: 
URL_PERSONAL: 
USERNAME: 

### Task: You are a PII (Personal Identity Information) Detection. Given a essays written by students, you have to identify ONLY the following:
NAME_STUDENT - The full or partial name of a student that is not necessarily the author of the essay. This excludes instructors, authors, and other person names.
EMAIL - A student’s email address.
USERNAME - A student's username on any platform.
ID_NUM - A number or sequence of characters that could be used to identify a student, such as a student ID or a social security number.
PHONE_NUM - A phone number associated with a student.
URL_PERSONAL - A URL that might be used to identify a student.
STREET_ADDRESS - A full or partial street address that is associated with the student, such as their home address.
### Input: Reflection on visualization 

 Challenge and selection 

 I get the help of the tool of visualization and visual thinking because it is the easiest and the   way that I am mostly talented in . I can get a shared and diverse idea of stakeholders and it   helps me to plan it overall . I usually use this on customers who are in an interest of developing   a software for their companies to make it efficient and so that they can provide their services   too using these programs . I use strawman technique for the questions that I ask from them   prior to start of the software development process which is the requirement gathering process .   Helps me to define the scope , boundaries relationship between the entities and the key   elements . 

 Application 

 Usually start the process with a straw man graphic of the problem domain . Ill draw from the   requirements which the client provides . The materials are voice records , use case scenarios , various   documentations of the requirements , and user stories . Plus the interviews . 

 If needed I might have to use various approaches like “ front - stage / back - stage ” and etc . The template I   often start with also has a column on the left to identify Partners and Value Chain Providers and a   column on the right to identify requirements , such as , the things what the client need in order to get   this project a success . So that I can map the users and what they want from this system to be developed .   Also I will have a column which specifies the propriety level of the requirement . So that I can inform the   developers what requirements are most crucial in the system . The straw man graphic is simple , using   simple shapes and icons available in Visio or on the Internet . If the front - stage / back - stage view does n’t   work , then I will create a different type of visual , either based on a high - level process flow with swim   lanes for different stakeholders , or another format for example ( Activity diagram with swim lanes ) . 

 For the activity , I will divide the stakeholders into participants each representing a different area of   interest of their requirements . Each group receives a set of sticky notes to make comments and get into   details of each requirement . I give them two - three questions to answer , like 1 ) What key elements are   missing from the graphic ? 2 ) What would you change about the graphic to make it more accurately   reflect your problem space ? 3 ) What key insights do you have about the relationships between the   entities in your problem space ? I give them some time to discuss the questions and mark up the graphic .   As each group intelligences out , I record shared aims in the visions of each collection , and then   additional intuitions that come from the group conversation on an other copy of the graphic . After the   meeting , I convert each group ’s set of sticky notes as an artifact , create a view that syndicates the   common and new thoughts from the group session . 

 Insight & Approach 

 I have learned from having this exercise with several groups of clients that , while the graphic ,   specifically the revised graphic that includes their comment is significant to strengthen the   comprehension of the problem . The more valuable feature of the activity is the shared insights and   shared learning that occurs while they are working to define their problem space . The graphics can fast   recognize where they are in the graphic and can more vastly increase new insights about relationships   between key entities . They can also identify variables in the problem scope . Later I learnt that the   greatest valuable aspect is the shared insights and learning , I would use the visualization activity as a   preliminary fact for a sequence of design thinking activities . Then the revised graphic .
### Output: 