[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-191447-105":53,"doc-detail-191447-en":127},{"code":4,"msg":5,"data":6},0,"success",[7,14,19,24,29,34,39,44,49],{"id":8,"doc_module":9,"doc_module_name":10,"category_name":11,"show_sort_weight":12,"slug":13},11,1,"Template","Presentations",90,"presentations",{"id":15,"doc_module":9,"doc_module_name":10,"category_name":16,"show_sort_weight":17,"slug":18},12,"Resumes",80,"resumes",{"id":20,"doc_module":9,"doc_module_name":10,"category_name":21,"show_sort_weight":22,"slug":23},14,"Invoices",70,"invoices",{"id":25,"doc_module":9,"doc_module_name":10,"category_name":26,"show_sort_weight":27,"slug":28},15,"Posters",60,"posters",{"id":30,"doc_module":9,"doc_module_name":10,"category_name":31,"show_sort_weight":32,"slug":33},16,"Social Media",50,"social-media",{"id":35,"doc_module":9,"doc_module_name":10,"category_name":36,"show_sort_weight":37,"slug":38},17,"Forms",40,"forms",{"id":40,"doc_module":9,"doc_module_name":10,"category_name":41,"show_sort_weight":42,"slug":43},18,"Letters",30,"letters",{"id":45,"doc_module":9,"doc_module_name":10,"category_name":46,"show_sort_weight":47,"slug":48},21,"Paper Templates",5,"papers-templates",{"id":50,"doc_module":9,"doc_module_name":10,"category_name":51,"show_sort_weight":4,"slug":52},158,"General","general-158",{"code":4,"msg":54,"data":55},"ok",{"site_id":56,"language":57,"slug":58,"title":59,"keywords":60,"description":61,"schema_data":62,"social_meta":120,"head_meta":122,"extra_data":124,"updated_unix":126},105,"en","what-verb-and-who-where-when-why-how-mappings","What-Verb and Who-Where-When-Why-How Mappings","","Document content provides structured mappings between common software/engineering terms and action verbs, pairing abstract nouns (fact, data, document components, assets, constraints, errors) with standardized operations (defined, mapped, categorized, produced, stored, tested, verified, modeled). It also supplies a complementary role-and-intent matrix connecting actor types (teams, stakeholders, owners, users) with contextual dimensions such as location, time, rationale, objectives, procedures, rules, and strategies, enabling consistent requirement phrasing and ontology-like classification in workflow design.",{"@graph":63,"@context":119},[64,80,102],{"@type":65,"itemListElement":66},"BreadcrumbList",[67,71,74,77],{"item":68,"name":69,"@type":70,"position":9},"https://docshare.wps.com","Home","ListItem",{"item":72,"name":10,"@type":70,"position":73},"https://docshare.wps.com/template/",2,{"item":75,"name":51,"@type":70,"position":76},"https://docshare.wps.com/template/general/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/what-verb-and-who-where-when-why-how-mappings/191447/",4,{"url":78,"name":59,"@type":81,"image":82,"author":87,"headline":59,"publisher":90,"fileFormat":93,"inLanguage":57,"description":61,"dateModified":94,"datePublished":95,"encodingFormat":93,"isAccessibleForFree":96,"interactionStatistic":97},"DigitalDocument",{"url":83,"@type":84,"width":85,"height":86},"https://docshare.wps.com/thumbnails/what-verb-and-who-where-when-why-how-mappings/191447.png","ImageObject",442,249,{"name":88,"@type":89},"Logic","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-10-05","2026-09-03",true,{"@type":98,"interactionType":99,"userInteractionCount":101},"InteractionCounter",{"@type":100},"ViewAction",8,{"@type":103,"mainEntity":104},"FAQPage",[105,111,115],{"name":106,"@type":107,"acceptedAnswer":108},"What does the document’s first table provide?","Question",{"text":109,"@type":110},"It provides mappings from “What” terms (e.g., fact, data, document, system components, assets, constraints) to corresponding “Verb” actions (e.g., defined, mapped, produced, configured, protected, modeled).","Answer",{"name":112,"@type":107,"acceptedAnswer":113},"What does the second table (Who/Where/When/Why/How) focus on?",{"text":114,"@type":110},"It organizes how different actor roles relate to contextual elements like location, time, objectives, procedures, rules, and strategies, helping structure requirements and behavior descriptions.",{"name":116,"@type":107,"acceptedAnswer":117},"How can these mappings be used in practice?",{"text":118,"@type":110},"They can be used to standardize requirement wording and classify elements in workflow or system design by consistently pairing entities (“What”/“Who”) with intended actions and context (“Verb”/“Why”/“How”).","https://schema.org",{"og:url":78,"og:type":121,"og:title":59,"og:site_name":91,"og:description":61},"article",{"robots":123,"canonical":78},"index,follow",{"doc_id":125,"site_id":56},191447,1788408649,{"code":4,"msg":5,"data":128},{"doc_id":125,"user_id":129,"nickname":88,"user_avatar":130,"doc_module":9,"category_id":50,"category_name":51,"doc_title":59,"doc_description":61,"doc_content":131,"file_id":132,"file_url":133,"file_type":134,"file_size":135,"view_count":101,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":40,"language":136,"language_code":57,"site_id":56,"html_lang":57,"table_of_contents":137,"faqs":138,"seo_title":139,"seo_description":61,"update_tm":126,"read_time":140},1099513958762,"https://ap-avatar.wpscdn.com/avatar/1000023916a998db790?x-image-process=image/resize,m_fixed,w_180,h_180&k=1784791008015729253","| What | Verb |\n| --- | --- |\n| fact, data, information, knowledge, file | abstracted, defined, designed, specified, formulated |\n| input, output | mapped, categorized, classified |\n| service, function, functionality, capability | acquired, bought, purchased, consumed, supplied |\n| activity, task, action, operation, procedure, process | produced, developed, created, constructed |\n| product, result, application | owned, outsourced, delegated,(re)used, adopted |\n| document, deliverable | modified, enhanced, refined, adapted |\n| component, module, unit, subsystem, system | collected, aggregated, combined |\n| algorithm, program, code, S/W | delivered, documented, inquired, notified |\n| computer, H/W, device, equipment, machine | read, written, deleted, edited, changed |\n| sector, domain, industry | transferred, communicated, accessed, retrieved |\n| environment, problem, scenario, use case | searched, discovered |\n| technology, protocol | managed, maintained |\n| asset, resource, artifact | (un)installed, configured, deployed |\n| supply, commodity, material, consumable | processed, analyzed, transformed |\n| instrument, tool, facility, building | stored, saved, encapsulated |\n| budget, fund | performed, executed, invoked, called |\n| element, entity, object, Thing, artifact | tested, emulated, demonstrated |\n| criterion, class, type, dimension, category | verified, checked, evaluated |\n| attribute, characteristic | presented, represented, visualized |\n| association, relation, interaction, flow, group | digitalized, virtualized, automated |\n| constraint, restriction, limitation | protected, secured |\n| interface, node, level, layer | considered, faced, mitigated, constrained, limited |\n| error, fault, failure, risk, threat | distributed, centralized |\n| event, contingency, condition, probability | (de)modularized, connected, integrated |\n| agreement, decision | detected, monitored, predicted, forecasted, modeled |\n\n\n| Who | Where | When | Why | How |\n| --- | --- | --- | --- | --- |\n| role team, organization individual, human actor, stakeholder acquirer, supplier buyer, customer\u003Cbr>owner\u003Cbr>user, consumer agent, delegate analyst, architect expert, engineer | location, place | time, date | requirement, need | action |\n|  | space | duration | objective, goal | procedure, process |\n|  | address | timing, schedule | mission, vision | rule |\n|  | layer, level, node | period | Rationale | standard |\n|  | device, machine | phase | strategy, plan | constraint, condition |\n|  | building, facility | event, contingency | condition, constraint | instruction, plan |\n|  | construct | scenario, use case priority order, sequence concurrence synchronicity | restriction, prohibition rule, law policy | cost, quality |","cbCaio9hzBXsKh1B","https://ap.wps.com/l/cbCaio9hzBXsKh1B","pdf",1195588,"English","# What-Verb mappings\n## Abstract to action operations\n# Who-Where-When-Why-How mappings\n## Actor, context, rationale, procedure","[{\"question\":\"What does the document’s first table provide?\",\"answer\":\"It provides mappings from “What” terms (e.g., fact, data, document, system components, assets, constraints) to corresponding “Verb” actions (e.g., defined, mapped, produced, configured, protected, modeled).\"},{\"question\":\"What does the second table (Who/Where/When/Why/How) focus on?\",\"answer\":\"It organizes how different actor roles relate to contextual elements like location, time, objectives, procedures, rules, and strategies, helping structure requirements and behavior descriptions.\"},{\"question\":\"How can these mappings be used in practice?\",\"answer\":\"They can be used to standardize requirement wording and classify elements in workflow or system design by consistently pairing entities (“What”/“Who”) with intended actions and context (“Verb”/“Why”/“How”).\"}]","What-Verb and Who-Where-When-Why-How Mappings | PDF",6]