Visualize current system limitation and why 

 Challenge – showing current system performances and its limitations 

 I work on an automatic microscope . I design the next generation . The next generation must   meet the marketing requirement . It means , I need to create a new microscope ( or a new   upgrade kit ) , so it will give our customers the new , more advance performances . For example ,   our customers need to see smaller elements , which are below current system resolution . Or the   new generation microscope , must work 30 % faster . When looking for a new solution , we first   must understand what the limitations in current system . If everybody in the developing team   will understand it , it will lead to the most optimal solution . The question is how to explain   current system limitations ( 10s ’ of modules ) . 

 Selection – Visualize the current system with a block diagram . 

 Showing ( Visualizing ) to my colleagues the current performance with a block diagram of the   microscope , is the best tool . By breaking the system into smaller modules , it ’s easier to   understand each functionality and the system flow . I also ask from each module owner to   preset his own module , to the rest of the developing team . So , few people are involve in the   presentation , and this will also stimulate the brainstorming . 

 Application - 

 I prepare block diagram of current system , and on the diagram , I draw each module in the   microscope system - no more than 15 blocks . If I have more , I unify few blocks into one , and   specify the module functionality ( of all of them ) . Then I ask from ( some ) of the colleagues to   present ( to the rest of the developing group ) their module functionality and its limitations . At   this phase , I draw the input and the output of the module . We do it module by module . 

 After several hours , everybody in the team , will be ‘ on the same page ’ , and will understand the   current system limitations . And the relations / dependencies between the modules . 

 Insight – This method causes for everybody in the team , to understand the design of the   system , and its restriction .   The drawing , shows the system flow – how the microscope creates   high resolution images , and the application needs . Engineers from different disciplines , now   discuss and ask questions ( freely ) , the module owner . For example - application engineer   understand the limitations of the electronic engineer ’s design .   Next step will be “ What if .. ” ,   with the above design thinking tool , everybody will be evolve , and will suggest ideas , that will   take into consideration the impact on other modules too . 

 Approach- 

 Before using Visualization tool , engineers from different disciplines , learned just the interfaces   between their module to the relevant modules . There was no open discussion about the design 

 considerations . And developers did n’t understand the big picture like the project manager and   the chief engineer . 


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: Visualize current system limitation and why 

 Challenge – showing current system performances and its limitations 

 I work on an automatic microscope . I design the next generation . The next generation must   meet the marketing requirement . It means , I need to create a new microscope ( or a new   upgrade kit ) , so it will give our customers the new , more advance performances . For example ,   our customers need to see smaller elements , which are below current system resolution . Or the   new generation microscope , must work 30 % faster . When looking for a new solution , we first   must understand what the limitations in current system . If everybody in the developing team   will understand it , it will lead to the most optimal solution . The question is how to explain   current system limitations ( 10s ’ of modules ) . 

 Selection – Visualize the current system with a block diagram . 

 Showing ( Visualizing ) to my colleagues the current performance with a block diagram of the   microscope , is the best tool . By breaking the system into smaller modules , it ’s easier to   understand each functionality and the system flow . I also ask from each module owner to   preset his own module , to the rest of the developing team . So , few people are involve in the   presentation , and this will also stimulate the brainstorming . 

 Application - 

 I prepare block diagram of current system , and on the diagram , I draw each module in the   microscope system - no more than 15 blocks . If I have more , I unify few blocks into one , and   specify the module functionality ( of all of them ) . Then I ask from ( some ) of the colleagues to   present ( to the rest of the developing group ) their module functionality and its limitations . At   this phase , I draw the input and the output of the module . We do it module by module . 

 After several hours , everybody in the team , will be ‘ on the same page ’ , and will understand the   current system limitations . And the relations / dependencies between the modules . 

 Insight – This method causes for everybody in the team , to understand the design of the   system , and its restriction .   The drawing , shows the system flow – how the microscope creates   high resolution images , and the application needs . Engineers from different disciplines , now   discuss and ask questions ( freely ) , the module owner . For example - application engineer   understand the limitations of the electronic engineer ’s design .   Next step will be “ What if .. ” ,   with the above design thinking tool , everybody will be evolve , and will suggest ideas , that will   take into consideration the impact on other modules too . 

 Approach- 

 Before using Visualization tool , engineers from different disciplines , learned just the interfaces   between their module to the relevant modules . There was no open discussion about the design 

 considerations . And developers did n’t understand the big picture like the project manager and   the chief engineer .
### Output: 