PERSONAS, TAXONOMIES AND ONTOLOGIES MAPPING PEOPLE TO THEIR WORK AND WORK TO THEIR SYSTEMS (DATE)
OVERVIEW INTRODUCTION PERSONAS TAXONOMIES ONTOLOGIES INTEGRATION INTO IT MODERNIZATION EFFORTS CONCLUSION REFERENCES
INTRODUCTION LETTING THE GOAL, USER AND TASK DEFINE THE SYSTEM RATHER THAN THE OTHER WAY AROUND GIVING A VOICE TO THE END USER IN SERVICE, SYSTEM AND TECHNOLOGY CHOICE AND DEVELOPMENT DEVELOP SYSTEMS AND PROCESSES THAT ARE MISSION FOCUSED BUT SERVICE ENTERPRISE GOALS
PERSONAS WHAT THEY ARE: A NARRATIVE RELATING TO A DESIRED USER OR CUSTOMER'S DAILY BEHAVIOR PATTERNS, USING SPECIFIC DETAILS, NOT GENERALITIES REPRESENTATIONS OF A GROUP OF CUSTOMERS SO THAT THE COMPANY CAN FOCUS ITS EFFORTS STRUCTURED AND FOCUSED ARCHETYPES (MODELS) EMPIRICAL & DATA-DRIVEN CONCEPTUAL WHAT THEY ARE NOT: SPECIFIC INDIVIDUALS ANECDOTAL / HYPOTHETICAL OVERLY BROAD AND UNBOUNDED UNSOURCED ATYPICAL BIASED
PERSONAS HOW CAN WE USE THEM IN IT MODERNIZATION EFFORTS? DEVELOP A FACT-BASED MODEL OF TARGET USERS, THEIR WORK ENVIRONMENTS, AND THE TASKS THEY PERFORM TO SUPPORT THE MISSION CAPTURE CONCRETE REAL-WORLD EXAMPLES OF USER ACTIVITY AND CROSS-INITIATIVE INTERACTION BETWEEN SERVICES AND TECHNOLOGIES
TAXONOMIES WHAT THEY ARE: A TAXONOMY, OR TAXONOMIC SCHEME, IS A PARTICULAR CLASSIFICATION, ARRANGED IN A HIERARCHICAL STRUCTURE OR CLASSIFICATION SCHEME. A CLASSIFICATION OF THINGS OR CONCEPTS, AS WELL AS TO THE PRINCIPLES UNDERLYING SUCH A CLASSIFICATION. WHAT THEY ARE NOT: LISTS OF ATTRIBUTES NON-STRUCTURED UN-CONSTRAINED UN-LINKED / DISCONNECTED ORGANIZED BY HIERARCHICAL AND CONTEXTUAL PARENT-CHILD RELATIONSHIPS
TAXONOMIES HOW CAN WE USE THEM IN IT MODERNIZATION EFFORTS? STRUCTURE VARIOUS JOB ROLES AND MISSION SUPPORT ROLES INTO CLASSIFICATIONS THAT CAN BE MAPPED TO SERVICE DEVELOPMENT ACTIVITIES COLLECT BUREAU STAFF OPERATIONS AND TASK DATA BASED ON JOB ROLES AND LOCATION WITHIN THE DEPARTMENT AND GEOGRAPHIC LOCATION CREATE A COMMON CLASSIFICATION STRUCTURE THAT CAN BE RE-USED FOR MULTIPLE ACTIVITIES AND INITIATIVES
ONTOLOGIES WHAT THEY ARE: FORMALLY REPRESENTS KNOWLEDGE AS A SET OF CONCEPTS WITHIN A DOMAIN, AND THE RELATIONSHIPS BETWEEN THOSE CONCEPTS. IT CAN BE USED TO REASON ABOUT THE ENTITIES WITHIN THAT DOMAIN, AND MAY BE USED TO DESCRIBE THE DOMAIN AN EXPECTATION THAT THERE BE A CLOSE RESEMBLANCE BETWEEN THE REAL WORLD AND THE FEATURES OF THE MODEL WHAT THEY ARE NOT: NON-RESTRICTED NON-SEMANTIC COMPONENTS THAT LACK MEANING DISCONNECTED UNSTRUCTURED DESCRIBE INDIVIDUALS (INSTANCES), CLASSES (CONCEPTS), ATTRIBUTES, AND RELATIONS USES SET LANGUAGES TO SPECIFY AND ENCODE COMPONENT INTERACTIONS
ONTOLOGIES HOW CAN WE USE THEM IN IT MODERNIZATION EFFORTS? THEY CAN BE USED TO CREATE A MODEL OF THE TASKS PERFORMED BY STAFF AND THEIR INTERACTION WITH RESOURCES AND TECHNOLOGY STANDARDIZE HOW WE DESCRIBE AND MODEL TECHNOLOGY THAT CAN BE EASILY UNDERSTOOD BY ALL LEVELS OF THE IT SUPPORT CHAIN CLEARLY AND EASILY IDENTIFY INTERRELATIONSHIPS OF RESOURCES, STAFF, AND ACTIVITY AMONG PREVIOUSLY DISPARATE APPEARING INDIVIDUALS
OVERVIEW PERSONAS MODEL PEOPLE AND ENVIRONMENTS TAXONOMIES MODEL ORGANIZATIONS AND SYSTEMS ONTOLOGIES MODEL ACTIVITIES AND CONCEPTS
OVERVIEW WHY SHOULD WE USE THESE TECHNIQUES? WHERE CAN WE USE THIS? WHAT CAN BE MODELED? WHO CAN USE THIS? HOW CAN WE USE THIS METHODOLOGY? WHEN DO YOU USE THIS APPROACH?
INTEGRATION INTO IT TRANSFORMATION THE WHY? STANDARDIZATION OF GOAL-SEEKING CONCEPTS ANYBODY CAN PICK IT UP AND RUN WITH THE MODEL Persona Resource SPEAK WITH A COMMON LEXICON AND LANGUAGE (UML) VISUAL VERSUS VERBAL Customer Task Goal REQUIRES DEVELOPER OF MODEL TO TRANSLATE CONCEPTS
INTEGRATION INTO IT TRANSFORMATION THE WHERE? MODELING USER BEHAVIORS, PATTERNS AND INTERACTION WITH RESOURCES Persona Resource USEFUL FOR DESIGNING COMPLEX IT SYSTEMS Customer Task Goal OUTPUTS CAN BE USED IN DEVELOPMENT WORKFLOW ON MULTI-DISCIPLINARY TEAMS CAPTURES ITEMS NOT CAUGHT IN BRAINSTORMING OR STORIES process to perform task...do this......and this. After doing this... to acheve
INTEGRATION INTO IT TRANSFORMATION THE WHAT? MAP PROCESS ACTIVITY TO REACH A GOAL Persona Resource CAPTURE RESOURCES REQUIRED TO PERFORM TASK within this uses this SEE INTERACTIONS, DEVELOP VERBS to perform this operational environment Customer Task Goal REFLECTS REALITY VERSUS HYPOTHETICAL...do this... to acheve REQUIRES RIGOR TO DEVELOP MODEL process to perform task...and this. After doing this...
INTEGRATION INTO IT TRANSFORMATION THE WHO? MULTI-DISCIPLINARY PROJECT TEAMS outputs inputs Team 2 INFORMATION DESIGNED TO BE USED AND SHARED AT ALL LEVELS OF A PROCESS Persona Resource TEAM MEMBERS NOT REQUIRED TO LEARN THE OTHER MEMBERS SPECIALITIES to perform this within this Customer Task...do this... uses this operational environment Goal to acheve MODEL CAN BE SHARED WITH USER TO CHECK THE PROCESS process to perform task...and this. After doing this... inputs Team 1 outputs
INTEGRATION INTO IT TRANSFORMATION THE HOW? INTEGRATION OF MODELING TO SERVICE AND TECHNOLOGY DEVELOPMENT AND IMPLEMENTATION Analysis Users Design CRM USE IT AT THE START TO ENSURE REQUIREMENTS ARE PROPERLY ACQUIRED Implementation Testing Evaluation SPM SD Users IDENTIFY TARGET USERS IDENTIFY ACTIVITY/RESOURCE OVERLAPS (COMPLIMENTARY OR INTERFERENCE) PROCESS CYCLES AROUND THROUGH REGRESSION AND REFINEMENT (FROM EVALUATION BACK TO ANALYSIS, FROM USERS BACK TO USERS)
INTEGRATION INTO IT TRANSFORMATION THE WHEN? UTILIZATION AT THE START OF PROJECT SCOPING - + Apirak.com My Website Buy content +...from concept, planning and system modeling... IDENTIFIES WHO AND WHAT IS INVOLVED Blog RDX Wall Art: The Making Of is a new short documentary highlighting some of the pioneers highlighting more... - Forun RDX Wall Art: The Making Of iand new short documentary iand new short isa new short - isa new short documentary - highlighting iand new sho documentary - some of the pioneers highlighting iand new sho more... SHAPES WHAT IS DELIVERED HELPS BUILD DELIVERABLE TIMELINES BASED ON REALITY...to implementation testing, and deployment COMPLETING MODELS AT START HELPS REDUCE RESOURCE EXPENDITURES DUE TO POOR HYPOTHESIS
PERSONA EXAMPLE BIOLOGIST FOCUS: ORNITHOLOGY [BIRDS] 60% FIELD WORK / 25% LAB / 15% OFFICE REGULAR ACTIVITIES FIELD COUNTS LAB EQUIPMENT FIELD SCIENTIFIC SAMPLING EQUIPMENT COMMUNICATION MANAGEMENT, OTHER BIOLOGISTS, AND ACADEMICS SHOOTS PHOTOS VOICE AND EMAILS COLLECTS SPECIMENS ONLINE SYSTEMS TO UPDATE FIELD DATA TECHNOLOGY USED GEOGRAPHIC LOCATION - NORTHWEST CONUS CELL PHONE (NO DATA SERVICE) ISSUES LAPTOP CONNECTIVITY (VOICE AND DATA) DSLR CAMERA OUTDATED AND HEAVY EQUIPMENT FOR FIELD USE
TAXONOMY EXAMPLE Person Science Managerial Support Life Physical Social Biology Botany Parasitology Ornithology Herpetology Mammalogy Lab Field THIS IS WHERE THE SAMPLE PERSONA RESIDES IN THE TAXONOMY
TAXONOMY EXAMPLE Person GROUP BY BIOLOGY SPECIALITY Science Managerial Support Life Physical Social GROUP BY ORNITHOLOGY SPECIALITY Biology Botany Parasitology Ornithology Herpetology Mammalogy Lab Field
ONTOLOGY EXAMPLE USER USES DEVICE SENDS DATA TO LOG SYSTEM ACCESSES MAINTAINS STATE OF PLACED CALL ALLOWS / PROVIDES NETWORK SENDS DATA TO PROCESSING SYSTEM OPERATING ENVIRONMENT
CONCLUSION INTEGRATING ALL THREE (3) TECHNIQUES CAN CREATE A FINE- GRAINED AND COMPREHENSIVE MODEL OF GOAL-CENTRIC WORK CAPTURES REALISTIC ACTIVITY VERSUS HYPOTHETICALS ALLOWS FOR VISUAL MAPPING OF ELEMENTS IN THE SYSTEM FOR EASY REFERENCE BY DISPARATE GROUPS CAPTURES ELEMENTS THAT MAY HAVE NOT BEEN IDENTIFIED THROUGH OTHER SYSTEM DEVELOPMENT MEANS PRIVATE SECTOR ADOPTION OF METHODOLOGY WITH PROVEN RESULTS
CONCLUSION CREATES RE-USABLE LIBRARY OF RESEARCH AND DATA, LOWERING COST OVER TIME LOW BARRIER TO TRANSLATION OF IDEAS ACROSS MULTIPLE DISCIPLINES (CRM VS. ENGINEERING VS. MANAGEMENT) SIMPLE AND CONCISE, HOWEVER UPFRONT EFFORT REQUIRED TO COLLECT BASE DATA CAN BE USED TO MASSAGE RELATIONSHIPS WITH STAFF - DATA OBSERVATION SESSIONS PRODUCE RESULTS THROUGH CUSTOMER INPUT REDUCES POSSIBLE MISTAKES AND RE-ENGINEERING
REFERENCES USER EXPERIENCE - HTTP://EN.WIKIPEDIA.ORG/WIKI/USER_EXPERIENCE USER-CENTRIC DESIGN - HTTP://EN.WIKIPEDIA.ORG/WIKI/USER-CENTERED_DESIGN CONTEXTUAL DESIGN - HTTP://EN.WIKIPEDIA.ORG/WIKI/CONTEXTUAL_DESIGN PERSONAS - HTTP://EN.WIKIPEDIA.ORG/WIKI/PERSONA_(MARKETING) TAXONOMIES - HTTP://EN.WIKIPEDIA.ORG/WIKI/TAXONOMY ONTOLOGIES IN IT/IS - HTTP://EN.WIKIPEDIA.ORG/WIKI/ ONTOLOGY_(INFORMATION_SCIENCE) ONTOLOGIES (CLASSICAL) - HTTP://EN.WIKIPEDIA.ORG/WIKI/ONTOLOGY
REFERENCES W3C PERSONA EXAMPLES - HTTP://WWW.W3.ORG/WAI/REDESIGN/PERSONAS JUST ASK: INTEGRATING ACCESSIBILITY THROUGHOUT DESIGN - HTTP:// UIACCESS.COM/ACCESSUCD/PERSONAS.HTML CREATING USER-CENTERED TAXONOMIES - HTTP://WEB.FUMSI.COM/GO/ARTICLE/ MANAGE/3126 A TAXONOMY OF STAKEHOLDERS : HUMAN ROLES IN SYSTEM DEVELOPMENT - HTTP:// EASYWEB.EASYNET.CO.UK/IANY/CONSULTANCY/STAKEHOLDER_TAXONOMY/ STAKEHOLDER_TAXONOMY.HTM ONTOLOGY-BASED SOFTWARE DEVELOPMENT TECHNIQUES - HTTP://WWW.ERCIM.EU/ PUBLICATION/ERCIM_NEWS/ENW58/SAEKI.HTML USING ONTOLOGIES FOR KNOWLEDGE MANAGEMENT: AN INFORMATION SYSTEMS PERSPECTIVE - HTTP://WWW.CS.TORONTO.EDU/PUB/ERIC/ASIS99.PDF