[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-167258-105":53,"doc-detail-167258-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","architecture-viewpoint-template-for-isoiecieee-42010-2-rich-hilliard","Architecture Viewpoint Template for ISO/IEC/IEEE 42010 - 2 - Rich Hilliard","","Architecture viewpoint template aligned with ISO/IEC/IEEE 42010:2011, enabling architects and organizations to document an architecture viewpoint through a structured outline and reusable “slots.” The template specifies required elements (“Musts”), recommended elements (“Shoulds”), optional items, and user-filled placeholders to complete an architecture description. Guidance explains conventions, terminology, and how the viewpoint forms a “contract” between architects and stakeholders by capturing architecture-relevant concerns and framing them for the resulting views.",{"@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":11,"@type":70,"position":76},"https://docshare.wps.com/template/presentations/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/architecture-viewpoint-template-for-isoiecieee-42010-2-rich-hilliard/167258/",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/architecture-viewpoint-template-for-isoiecieee-42010-2-rich-hilliard/167258.png","ImageObject",442,249,{"name":88,"@type":89},"Gloria","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/octet-stream","2026-09-29","2026-08-31",true,{"@type":98,"interactionType":99,"userInteractionCount":101},"InteractionCounter",{"@type":100},"ViewAction",9,{"@type":103,"mainEntity":104},"FAQPage",[105,111,115],{"name":106,"@type":107,"acceptedAnswer":108},"What is the purpose of this architecture viewpoint template?","Question",{"text":109,"@type":110},"It helps architects document an architecture viewpoint according to ISO/IEC/IEEE 42010:2011 using a predefined outline and information slots to be elaborated.","Answer",{"name":112,"@type":107,"acceptedAnswer":113},"What do “Musts,” “Shoulds,” and optional items mean in the template?",{"text":114,"@type":110},"“Musts” identify elements required to satisfy the standard, “Shoulds” are recommended but not required, and optional items are explicitly marked as optional.",{"name":116,"@type":107,"acceptedAnswer":117},"Why does the template ask for concerns and typical stakeholders?",{"text":118,"@type":110},"Because the standard requires documenting concerns and stakeholders for which a viewpoint is intended, and these define what the resulting views must address as a contract between architects and stakeholders.","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},167258,1788210982,{"code":4,"msg":5,"data":128},{"doc_id":125,"user_id":129,"nickname":88,"user_avatar":130,"doc_module":9,"category_id":8,"category_name":11,"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":136,"language":137,"language_code":57,"site_id":56,"html_lang":57,"table_of_contents":138,"faqs":139,"seo_title":140,"seo_description":61,"update_tm":126,"read_time":76},2336474459895,"https://ap-avatar.wpscdn.com/avatar/22000baeef7a5ed0655?x-image-process=image/resize,m_fixed,w_180,h_180&k=1786071322749376916","Architecture viewpoint template\nfor use with ISO/IEC/IEEE 42010:2011\nArchitecture Viewpoint Template for ISO/IEC/IEEE 42010\nRich Hilliard\nr.hilliard@computer.org\nVERSION 2.2\nAbstract\nThis is a template for specifying architecture viewpoints in accordance with ISO/IEC/IEEE 42010:2011, Systems and software engineering—Architecture description.\nUsing the template\nThis is a template that architects and organizations can use for documenting an architecture viewpoint in accordance with ISO/IEC/IEEE 42010:2011 [6]. In particular, the requirements on viewpoints are found in Clause 7 of that Standard.\nThe template provides an outline for an architecture viewpoint and defines a set of “slots” or information items to be elaborated by the architect using the template to define and specify a viewpoint. Each slot is identified by a heading name followed by a brief description of its intended content and guidance for developing that content.\nThe template uses a few conventions, as follows.\n* “Musts” are items which must be present to satisfy the Standard. Musts are marked like this.\n∆ “Shoulds” are items recommended to be present, but not required by the Standard. Shoulds are marked like this.\nOptional items are marked with this: (optional). Guidance that defines, explains or otherwise amplifies upon the required items, or terms used therein, looks like this.\n\u003CItems> like \u003Cthis> signal names to be filled-in by a user of the template and used throughout the resulting AD.\nThe source files for this version of the template is packaged as a LATEX section. It is designed to be included in a LATEX document such as those using the report, book or article document class. (Other versions for Microsoft Word and XML will also be made available.)\nLicense\nThe Architecture Viewpoint Template is copyright ©2012–2014 by Rich Hilliard.\nThe latest version is always available at: \u000bhttp://www.iso-architecture.org/42010/templates/.\nThe template is licensed under a Creative Commons Attribution 3.0 Unported License. The terms of use are here:\u000bhttp://creativecommons.org/licenses/by/3.0/\nThis license gives you the user the right to share and remix this work to define new architecture viewpoints. It does not require you to share the results of your usage (i.e., new viewpoint definitions), but if your use is non-proprietary, we encourage you to share your viewpoint definition with others for their use via the WG42 Viewpoint Repository\u000bhttp://www.iso-architecture.org/viewpoints/.\nVersion history\nThis template is based on one originally designed for use with IEEE std 1471:2000 [5] which was published as [3]. That template formed the basis for the viewpoint tem- plate in [4], which appeared during the development ISO/IEC/IEEE 42010:2011 and subsequently appeared in Annex B of the published ISO/IEC/IEEE 42010:2011.\nThe present document is an enhanced version of these earlier templates, with additional guidance, clarifications and examples for readers.\nrev 2.2\t7 October 2014, Moved bibliography from bibtex to biblatex. Released revision with minor formatting fixes.\nrev 2.1b\tJune 2012, initial release on 42010 website.\nComments or questions\nContact the author Rich Hilliard ⟨r.hilliard@computer.org⟩ with comments, suggestions, improvements or questions.\nFor more information on ISO/IEC/IEEE 42010, visit the website: \u000bhttp://www.iso-architecture.org/42010/.\nThe template begins here . . .\n1\t\u003CViewpoint Name>\n* Provide the name for the viewpoint.\nIf there are any synonyms or other common names by which this viewpoint is known or used, record them here.\n2\tOverview\nProvide an abstract or brief overview of the viewpoint. Describe the viewpoint’s key features.\n3\tConcerns and stakeholders\nArchitects looking for an architecture viewpoint suitable for their purposes often use the identified concerns and typical stakeholders to guide them in their search. Therefore it is important (and required by the Standard) to document the concerns and stakeholders for which a viewpoint is intended.\n3","cbCainpKAars4Lv8","https://ap.wps.com/l/cbCainpKAars4Lv8","doc",57344,7,"English","# Using the template\n## Template purpose and required viewpoints\n## Template structure: slots and conventions\n## License and version history\n## Viewpoint template sections","[{\"question\":\"What is the purpose of this architecture viewpoint template?\",\"answer\":\"It helps architects document an architecture viewpoint according to ISO/IEC/IEEE 42010:2011 using a predefined outline and information slots to be elaborated.\"},{\"question\":\"What do “Musts,” “Shoulds,” and optional items mean in the template?\",\"answer\":\"“Musts” identify elements required to satisfy the standard, “Shoulds” are recommended but not required, and optional items are explicitly marked as optional.\"},{\"question\":\"Why does the template ask for concerns and typical stakeholders?\",\"answer\":\"Because the standard requires documenting concerns and stakeholders for which a viewpoint is intended, and these define what the resulting views must address as a contract between architects and stakeholders.\"}]","Architecture Viewpoint Template for ISO/IEC/IEEE 42010 - 2 - Rich Hilliard | DOC"]