{"id":3428,"date":"2013-08-05T08:29:48","date_gmt":"2013-08-05T15:29:48","guid":{"rendered":"https:\/\/www.jamasoftware.com\/?p=3428"},"modified":"2023-01-12T16:56:46","modified_gmt":"2023-01-13T00:56:46","slug":"elements-of-requirements-style-part-1","status":"publish","type":"post","link":"https:\/\/www.jamasoftware.com\/legacy\/blog\/2013\/08\/05\/elements-of-requirements-style-part-1\/","title":{"rendered":"Elements of Requirements Style, Part 1"},"content":{"rendered":"<p><span style=\"font-size: 13px; line-height: 19px;\">Writing requirements is hard! There is no simple, formulaic approach to software specification. High-quality requirements begin with proper grammar, accurate spelling, well-constructed sentences, and a logical organization. This series of four articles, adapted from my book <\/span><i style=\"font-size: 13px; line-height: 19px;\">More about Software Requirements<\/i><span style=\"font-size: 13px; line-height: 19px;\"> (Microsoft Press, 2006), presents numerous style guidelines to keep in mind when writing functional requirements.<\/span><\/p>\n<p>I\u2019m not a fan of arbitrary rules about writing requirements. Some I\u2019ve heard are:<\/p>\n<ul>\n<li>A requirement may not contain the word <i>and<\/i>. An \u201cand\u201d indicates the presence of two requirements, which must be separated.<\/li>\n<li>A requirement may not contain more than one sentence.<\/li>\n<li>A requirement may not contain more than 22 words.<\/li>\n<\/ul>\n<p>These sorts of simplistic rules are intended to help analysts write good requirements, but there are too many cases in which they don\u2019t constitute good advice. As you develop your requirements specifications, remember your key objective: clear and effective communication among the project stakeholders.<\/p>\n<h2>I Shall Call This a Requirement<\/h2>\n<p><i>Shall<\/i> is the traditional keyword for identifying a functional requirement. Functional requirements describe behaviors the system shall exhibit under certain circumstances or actions the system shall let the user take. Some people object to the use of <i>shall<\/i> because it feels stilted. It\u2019s not the way people normally talk, at least not outside English period-piece movies. True\u2014but so what? In fact, this is a plus. Using a distinctive word sharply separates a requirement from other information in a specification document. <i>Shall<\/i> serves as a symbol that signals the presence of a discrete requirement.<\/p>\n<p>Too many requirements specifications use a random mix of different verbs: <i>shall, must, should, could, would, is recommended, is desirable, is requested, will, can, may,<\/i> and <i>might<\/i>. Many of these words are used interchangeably in casual conversation, but this can become confusing in a written specification. The reader is left to wonder whether there\u2019s a subtle but important distinction between these various keywords. Does <i>must<\/i> have some different connotation than <i>can<\/i>? Does <i>might<\/i> (which conveys a sense of possibility in normal dialog) mean the same thing as <i>may<\/i> (which conveys a sense of permission)? I\u2019ve also heard of conventions in which <i>shall<\/i> identifies a requirement, but <i>will<\/i> indicates a design statement and <i>must<\/i> signifies a constraint. Oh, my.<\/p>\n<p>Some organizations follow a convention I find risky. In this scheme, <i>shall<\/i> indicates a function that is required, <i>should<\/i> means that the function is desired, and <i>may<\/i> indicates that the function being described is optional. This raises two problems. First, two concepts are being combined: the statement of intended functionality and the relative priority of that functionality. The second problem is that the priority information is being communicated using words that have similar meanings in everyday conversation.<\/p>\n<p>My preference is to use the keyword <i>shall<\/i> to identify functional requirements whenever possible. Avoid <i>should<\/i>, <i>may<\/i>, <i>might<\/i>, and similar words that don\u2019t make it clear whether the statement is a requirement. My colleague Brian Lawrence suggests that you replace <i>should<\/i> with <i>probably won\u2019t<\/i> and see if that would be all right with the customer. It probably won\u2019t.<\/p>\n<p>A requirement in the form, \u201cThe system should do X\u201d can be restated in the form, \u201cWhen Y happens, the system shall do X.\u201d And instead of using the shall\u2013should\u2013may convention to communicate priority, I\u2019d rather see requirements written as follows:<\/p>\n<ol>\n<li>\u201cThe system shall \u2026 [Priority = High].\u201d<\/li>\n<li>\u201cThe system shall \u2026 [Priority = Medium].\u201d<\/li>\n<li>\u201cThe system shall \u2026 [Priority = Low].\u201d<\/li>\n<\/ol>\n<p>The goal of clear and unambiguous communication is more elusive when requirements writers use a mix of nearly synonymous verbs and expect all readers to reach the same conclusions about what they\u2019re trying to say. Frankly, I don\u2019t understand the objection to <i>shall<\/i>. But if you don\u2019t like it, pick an alternative word\u2014such as <i>must<\/i>\u2014and use it consistently.<\/p>\n<h2>System Perspective or User Perspective?<\/h2>\n<p>Various conventions for writing functional requirements exist. Some people believe that requirements should describe only the system\u2019s behavior, because \u201cthe system\u201d is what you create by implementing all the functional requirements. However, I think it\u2019s appropriate to write functional requirements from either the system\u2019s perspective or the user\u2019s perspective. Use whichever structure offers the clearest communication in a given situation.<\/p>\n<p>Requirements written from the system\u2019s perspective conform to the following general structure:<\/p>\n<p><i>Conditions:<\/i>\u00a0\u00a0 \u201cWhen [some conditions are true]\u2026\u201d<\/p>\n<p><i>Result:<\/i>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \u201c\u2026 the system shall [do something]\u201d<\/p>\n<p><i>Qualifier<\/i>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \u201c\u2026[response time goal or quality objective].\u201d<\/p>\n<p>The \u201cconditions\u201d part of the requirement could reflect an event that triggers the system to respond in some way. Here\u2019s a simple example, from an information system for ordering meals on-line from a company cafeteria:<\/p>\n<p>\u201cWhen the patron indicates that he does not wish to order any more food items, the system shall display all food items ordered, the individual food item prices, and the total payment amount within 1 second.\u201d<\/p>\n<p>This requirement describes an event that the system can detect, followed by the action the system takes in response to that event. This requirement also includes a performance goal, the 1-second response time. This element constitutes a nonfunctional requirement associated with this specific bit of system functionality.<\/p>\n<p>When stating such performance goals, it\u2019s important to make clear whether they are critical values or merely desirable targets. Is the system acceptable if it takes 1.2 seconds to display the order details? How about 10 seconds? Precise response times are more critical for hard real-time systems than for information systems.<\/p>\n<p>In some cases, it makes more sense to describe actions that the system will let the user take under particular circumstances. When writing functional requirements from the user\u2019s perspective, keep the following general structure in mind:<\/p>\n<p><i>User type:<\/i>\u00a0\u00a0\u00a0\u00a0 \u201cThe [user class or actor name]\u2026\u201d<\/p>\n<p><i>Result type:<\/i>\u00a0\u00a0 \u201c\u2026 shall be able to [do something]\u2026\u201d<\/p>\n<p><i>Object:<\/i>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \u201c\u2026 [to something].<\/p>\n<p><i>Qualifier:<\/i>\u00a0\u00a0\u00a0\u00a0\u00a0 [response time goal or quality objective]<\/p>\n<p>It\u2019s more meaningful to refer to the affected user class by name, rather just saying <i>user<\/i>. Here\u2019s an illustration of a functional requirement written from the user\u2019s perspective:<\/p>\n<p>\u201cThe patron shall be able to reorder any meal he had ordered within the previous six months, provided that all food items in that order are available on the menu for the meal date.\u201d<\/p>\n<p>Note that these examples are written in the active voice. They explicitly identify the entity\u2014the system or a specific user type\u2014that takes each action. Most of the functional requirements I read are written in passive voice:<\/p>\n<p>Passive: \u201cWhen the output state changes, it is logged in the event log.\u201d<\/p>\n<p>Whenever you can, recast such requirements in the much clearer active voice:<\/p>\n<p>Active: \u201cWhen the output state changes, the system shall record the new state and the time of the state change in the event log.\u201d<\/p>\n<p>With active voice, the reader doesn\u2019t have to deduce which entity is doing what. The more explicit and precise you can make the requirements, the easier it will be for the readers to understand them and use them to guide the project work they do.<\/p>\n<p>This is the first of a four-part series. Check back soon for\u00a0Elements of Requirements Style, Parts 2, 3 and 4.<\/p>\n<p>&nbsp;<\/p>\n<p><i>Jama Software has partnered with Karl Wiegers to share licensed content from his books and articles on our web site via a series of blog posts, whitepapers and webinars.\u00a0 Karl Wiegers is an independent consultant and not an employee of Jama. \u00a0He can be reached at\u00a0<\/i><i><a href=\"http:\/\/www.processimpact.com\">http:\/\/www.processimpact.com<\/a><\/i><i>.\u00a0 Enjoy these free\u00a0<\/i><i><a href=\"https:\/\/www.jamasoftware.com\/resources\/\">requirements management resources<\/a><\/i><i>.<\/i><i><\/i><\/p>\n<p><i>\u00a0<\/i><\/p>\n<input class=\"fooboxshare_post_id\" type=\"hidden\" value=\"3428\"\/>","protected":false},"excerpt":{"rendered":"<p>Writing requirements is hard! There is no simple, formulaic approach to software specification. High-quality requirements begin with proper grammar, accurate spelling, well-constructed sentences, and a logical organization. This series of four articles, adapted from my book More about Software Requirements (Microsoft Press, 2006), presents numerous style guidelines to keep in mind when writing functional requirements. [&hellip;]<\/p>\n","protected":false},"author":68,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":""},"categories":[50],"tags":[51,115,38],"industry":[],"class_list":["post-3428","post","type-post","status-publish","format-standard","hentry","category-requirements-management","tag-business-requirements","tag-elements","tag-karl-wiegers"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v28.1 (Yoast SEO v28.1) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>Elements of Requirements Style, Part 1 - Jama Software<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.jamasoftware.com\/blog\/2013\/08\/05\/elements-of-requirements-style-part-1\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Elements of Requirements Style, Part 1\" \/>\n<meta property=\"og:description\" content=\"Writing requirements is hard! There is no simple, formulaic approach to software specification. High-quality requirements begin with proper grammar, accurate spelling, well-constructed sentences, and a logical organization. This series of four articles, adapted from my book More about Software Requirements (Microsoft Press, 2006), presents numerous style guidelines to keep in mind when writing functional requirements. [&hellip;]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.jamasoftware.com\/blog\/2013\/08\/05\/elements-of-requirements-style-part-1\/\" \/>\n<meta property=\"og:site_name\" content=\"Jama Software\" \/>\n<meta property=\"article:published_time\" content=\"2013-08-05T15:29:48+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2023-01-13T00:56:46+00:00\" \/>\n<meta name=\"author\" content=\"Karl Wiegers\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Karl Wiegers\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"6 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.jamasoftware.com\\\/blog\\\/2013\\\/08\\\/05\\\/elements-of-requirements-style-part-1\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.jamasoftware.com\\\/blog\\\/2013\\\/08\\\/05\\\/elements-of-requirements-style-part-1\\\/\"},\"author\":{\"name\":\"Karl Wiegers\",\"@id\":\"https:\\\/\\\/www.jamasoftware.com\\\/#\\\/schema\\\/person\\\/e6a00f0ad439a5e1865476b36481aa47\"},\"headline\":\"Elements of Requirements Style, Part 1\",\"datePublished\":\"2013-08-05T15:29:48+00:00\",\"dateModified\":\"2023-01-13T00:56:46+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.jamasoftware.com\\\/blog\\\/2013\\\/08\\\/05\\\/elements-of-requirements-style-part-1\\\/\"},\"wordCount\":1243,\"keywords\":[\"business requirements\",\"elements\",\"karl wiegers\"],\"articleSection\":[\"Requirements &amp; Requirements Management\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.jamasoftware.com\\\/blog\\\/2013\\\/08\\\/05\\\/elements-of-requirements-style-part-1\\\/\",\"url\":\"https:\\\/\\\/www.jamasoftware.com\\\/blog\\\/2013\\\/08\\\/05\\\/elements-of-requirements-style-part-1\\\/\",\"name\":\"Elements of Requirements Style, Part 1 - Jama Software\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.jamasoftware.com\\\/#website\"},\"datePublished\":\"2013-08-05T15:29:48+00:00\",\"dateModified\":\"2023-01-13T00:56:46+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.jamasoftware.com\\\/#\\\/schema\\\/person\\\/e6a00f0ad439a5e1865476b36481aa47\"},\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.jamasoftware.com\\\/blog\\\/2013\\\/08\\\/05\\\/elements-of-requirements-style-part-1\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.jamasoftware.com\\\/blog\\\/2013\\\/08\\\/05\\\/elements-of-requirements-style-part-1\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.jamasoftware.com\\\/blog\\\/2013\\\/08\\\/05\\\/elements-of-requirements-style-part-1\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.jamasoftware.com\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Elements of Requirements Style, Part 1\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.jamasoftware.com\\\/#website\",\"url\":\"https:\\\/\\\/www.jamasoftware.com\\\/\",\"name\":\"Jama Software\",\"description\":\"Jama Connect\u00ae #1 in Requirements Management\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.jamasoftware.com\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.jamasoftware.com\\\/#\\\/schema\\\/person\\\/e6a00f0ad439a5e1865476b36481aa47\",\"name\":\"Karl Wiegers\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/6d4992a28dda9ae47cf239c04be9a0bc554586672cba38949c070d2fed228aef?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/6d4992a28dda9ae47cf239c04be9a0bc554586672cba38949c070d2fed228aef?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/6d4992a28dda9ae47cf239c04be9a0bc554586672cba38949c070d2fed228aef?s=96&d=mm&r=g\",\"caption\":\"Karl Wiegers\"},\"description\":\"Subject matter expert Karl Wiegers writes on best practices for writing requirements, requirements management, and requirements traceability.\",\"sameAs\":[\"alison@makes-magic.com\"],\"url\":\"https:\\\/\\\/www.jamasoftware.com\\\/blog\\\/author\\\/kwiegers\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Elements of Requirements Style, Part 1 - Jama Software","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.jamasoftware.com\/blog\/2013\/08\/05\/elements-of-requirements-style-part-1\/","og_locale":"en_US","og_type":"article","og_title":"Elements of Requirements Style, Part 1","og_description":"Writing requirements is hard! There is no simple, formulaic approach to software specification. High-quality requirements begin with proper grammar, accurate spelling, well-constructed sentences, and a logical organization. This series of four articles, adapted from my book More about Software Requirements (Microsoft Press, 2006), presents numerous style guidelines to keep in mind when writing functional requirements. [&hellip;]","og_url":"https:\/\/www.jamasoftware.com\/blog\/2013\/08\/05\/elements-of-requirements-style-part-1\/","og_site_name":"Jama Software","article_published_time":"2013-08-05T15:29:48+00:00","article_modified_time":"2023-01-13T00:56:46+00:00","author":"Karl Wiegers","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Karl Wiegers","Est. reading time":"6 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.jamasoftware.com\/blog\/2013\/08\/05\/elements-of-requirements-style-part-1\/#article","isPartOf":{"@id":"https:\/\/www.jamasoftware.com\/blog\/2013\/08\/05\/elements-of-requirements-style-part-1\/"},"author":{"name":"Karl Wiegers","@id":"https:\/\/www.jamasoftware.com\/#\/schema\/person\/e6a00f0ad439a5e1865476b36481aa47"},"headline":"Elements of Requirements Style, Part 1","datePublished":"2013-08-05T15:29:48+00:00","dateModified":"2023-01-13T00:56:46+00:00","mainEntityOfPage":{"@id":"https:\/\/www.jamasoftware.com\/blog\/2013\/08\/05\/elements-of-requirements-style-part-1\/"},"wordCount":1243,"keywords":["business requirements","elements","karl wiegers"],"articleSection":["Requirements &amp; Requirements Management"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/www.jamasoftware.com\/blog\/2013\/08\/05\/elements-of-requirements-style-part-1\/","url":"https:\/\/www.jamasoftware.com\/blog\/2013\/08\/05\/elements-of-requirements-style-part-1\/","name":"Elements of Requirements Style, Part 1 - Jama Software","isPartOf":{"@id":"https:\/\/www.jamasoftware.com\/#website"},"datePublished":"2013-08-05T15:29:48+00:00","dateModified":"2023-01-13T00:56:46+00:00","author":{"@id":"https:\/\/www.jamasoftware.com\/#\/schema\/person\/e6a00f0ad439a5e1865476b36481aa47"},"breadcrumb":{"@id":"https:\/\/www.jamasoftware.com\/blog\/2013\/08\/05\/elements-of-requirements-style-part-1\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.jamasoftware.com\/blog\/2013\/08\/05\/elements-of-requirements-style-part-1\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.jamasoftware.com\/blog\/2013\/08\/05\/elements-of-requirements-style-part-1\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.jamasoftware.com\/"},{"@type":"ListItem","position":2,"name":"Elements of Requirements Style, Part 1"}]},{"@type":"WebSite","@id":"https:\/\/www.jamasoftware.com\/#website","url":"https:\/\/www.jamasoftware.com\/","name":"Jama Software","description":"Jama Connect\u00ae #1 in Requirements Management","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.jamasoftware.com\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.jamasoftware.com\/#\/schema\/person\/e6a00f0ad439a5e1865476b36481aa47","name":"Karl Wiegers","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/6d4992a28dda9ae47cf239c04be9a0bc554586672cba38949c070d2fed228aef?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/6d4992a28dda9ae47cf239c04be9a0bc554586672cba38949c070d2fed228aef?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/6d4992a28dda9ae47cf239c04be9a0bc554586672cba38949c070d2fed228aef?s=96&d=mm&r=g","caption":"Karl Wiegers"},"description":"Subject matter expert Karl Wiegers writes on best practices for writing requirements, requirements management, and requirements traceability.","sameAs":["alison@makes-magic.com"],"url":"https:\/\/www.jamasoftware.com\/blog\/author\/kwiegers\/"}]}},"_links":{"self":[{"href":"https:\/\/www.jamasoftware.com\/legacy\/wp-json\/wp\/v2\/posts\/3428","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.jamasoftware.com\/legacy\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.jamasoftware.com\/legacy\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.jamasoftware.com\/legacy\/wp-json\/wp\/v2\/users\/68"}],"replies":[{"embeddable":true,"href":"https:\/\/www.jamasoftware.com\/legacy\/wp-json\/wp\/v2\/comments?post=3428"}],"version-history":[{"count":0,"href":"https:\/\/www.jamasoftware.com\/legacy\/wp-json\/wp\/v2\/posts\/3428\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.jamasoftware.com\/legacy\/wp-json\/wp\/v2\/media?parent=3428"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.jamasoftware.com\/legacy\/wp-json\/wp\/v2\/categories?post=3428"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.jamasoftware.com\/legacy\/wp-json\/wp\/v2\/tags?post=3428"},{"taxonomy":"industry","embeddable":true,"href":"https:\/\/www.jamasoftware.com\/legacy\/wp-json\/wp\/v2\/industry?post=3428"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}