[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-0-en-105":3,"doc-seo-657646-105":59,"doc-detail-657646-en":130},{"code":4,"msg":5,"data":6},0,"success",[7,13,18,23,28,33,38,43,48,51,55],{"id":8,"doc_module":4,"doc_module_name":9,"category_name":10,"show_sort_weight":11,"slug":12},1,"Document","Story & Novel",90,"story-novel",{"id":14,"doc_module":4,"doc_module_name":9,"category_name":15,"show_sort_weight":16,"slug":17},2,"Literature",80,"literature",{"id":19,"doc_module":4,"doc_module_name":9,"category_name":20,"show_sort_weight":21,"slug":22},4,"Exam",70,"exam",{"id":24,"doc_module":4,"doc_module_name":9,"category_name":25,"show_sort_weight":26,"slug":27},5,"Comic",60,"comic",{"id":29,"doc_module":4,"doc_module_name":9,"category_name":30,"show_sort_weight":31,"slug":32},6,"Technology",50,"technology",{"id":34,"doc_module":4,"doc_module_name":9,"category_name":35,"show_sort_weight":36,"slug":37},7,"Healthcare",40,"healthcare",{"id":39,"doc_module":4,"doc_module_name":9,"category_name":40,"show_sort_weight":41,"slug":42},8,"Research & Report",30,"research-report",{"id":44,"doc_module":4,"doc_module_name":9,"category_name":45,"show_sort_weight":46,"slug":47},9,"Religion & Spirituality",20,"religion-spirituality",{"id":46,"doc_module":4,"doc_module_name":9,"category_name":49,"show_sort_weight":46,"slug":50},"World Cup","world-cup",{"id":52,"doc_module":4,"doc_module_name":9,"category_name":53,"show_sort_weight":52,"slug":54},10,"Lifestyle","lifestyle",{"id":56,"doc_module":4,"doc_module_name":9,"category_name":57,"show_sort_weight":24,"slug":58},19,"General","general",{"code":4,"msg":60,"data":61},"ok",{"site_id":62,"language":63,"slug":64,"title":65,"keywords":66,"description":67,"schema_data":68,"social_meta":123,"head_meta":125,"extra_data":127,"updated_unix":129},105,"en","the-system-context-architectural-viewpoint","The System Context Architectural Viewpoint","","A software architecture description often must define a system’s environment through external dependencies, and view-based approaches benefit from explicitly modeling this via a Context view. This short paper explains why adding a Context view strengthens architectural descriptions, outlines a corresponding Context viewpoint to specify what it should contain, and describes how it can be developed and standardized within a viewpoint framework.",{"@graph":69,"@context":122},[70,84,105],{"@type":71,"itemListElement":72},"BreadcrumbList",[73,77,79,82],{"item":74,"name":75,"@type":76,"position":8},"https://docshare.wps.com","Home","ListItem",{"item":78,"name":9,"@type":76,"position":14},"https://docshare.wps.com/document/",{"item":80,"name":40,"@type":76,"position":81},"https://docshare.wps.com/document/research-report/",3,{"item":83,"name":65,"@type":76,"position":19},"https://docshare.wps.com/document/the-system-context-architectural-viewpoint/657646/",{"url":83,"name":65,"@type":85,"image":86,"author":91,"headline":65,"publisher":94,"fileFormat":97,"inLanguage":63,"description":67,"dateModified":98,"datePublished":99,"encodingFormat":97,"isAccessibleForFree":100,"interactionStatistic":101},"DigitalDocument",{"url":87,"@type":88,"width":89,"height":90},"https://docshare.wps.com/thumbnails/the-system-context-architectural-viewpoint/657646.png","ImageObject",300,407,{"name":92,"@type":93},"I feel Different","Person",{"url":74,"name":95,"@type":96},"DocShare","Organization","application/pdf","2026-10-30","2026-10-26",true,{"@type":102,"interactionType":103,"userInteractionCount":8},"InteractionCounter",{"@type":104},"ViewAction",{"@type":106,"mainEntity":107},"FAQPage",[108,114,118],{"name":109,"@type":110,"acceptedAnswer":111},"What problem does a Context view solve in software architecture descriptions?","Question",{"text":112,"@type":113},"It defines the system’s environment and external dependencies by answering how the system relates technically to elements in its wider environment.","Answer",{"name":115,"@type":110,"acceptedAnswer":116},"Why was a context viewpoint missing from the original viewpoint set?",{"text":117,"@type":113},"The original set focused on internal structures and assumed the system context would be defined elsewhere, so a context viewpoint was not included as a formal viewpoint.",{"name":119,"@type":110,"acceptedAnswer":120},"What concerns does the Context view address?",{"text":121,"@type":113},"It focuses on the identity and responsibilities of external entities, including defining interactions even when they are irregular or only occur periodically.","https://schema.org",{"og:url":83,"og:type":124,"og:title":65,"og:site_name":95,"og:description":67},"article",{"robots":126,"canonical":83},"index,follow",{"doc_id":128,"site_id":62},657646,1792985761,{"code":4,"msg":5,"data":131},{"doc_id":128,"user_id":132,"nickname":92,"user_avatar":133,"doc_module":4,"category_id":39,"category_name":40,"doc_title":65,"doc_description":67,"doc_content":134,"file_id":135,"file_url":136,"file_type":137,"file_size":138,"view_count":8,"is_deleted":4,"is_public":8,"is_downloadable":8,"audit_status":8,"page_count":19,"language":139,"language_code":63,"site_id":62,"html_lang":63,"table_of_contents":140,"faqs":141,"seo_title":142,"seo_description":67,"update_tm":129,"read_time":52},962093541761,"https://ap-avatar.wpscdn.com/davatar_29158cc5080c5b710cf443261637dec0","The System Context Architectural Viewpoint  \nEoin Woods Barclays Global Investors [eoin.woods@barclaysglobal.com](eoin.woods@barclaysglobal.com)  \nNick Rozanski Barclays Global Investors [nicholas.rozanski@barclaysglobal.com](nicholas.rozanski@barclaysglobal.com)  \nAbstract  \nA common requirement when describing the architecture of a software system is the ability to define the environment of a system, in terms of its external dependencies. In a view-based architectural description approach (such as “4+1” or “Rozanski and Woods”) this need is met by adding a Context view containing this information to the architectural description and ideally defining a corresponding Context viewpoint to guide and standardise such views. This short paper explains the benefits of adding a Context view to architectural descriptions and providesan outline definition of the corresponding viewpoint to explain their content and how they are developed.  \n1. Introduction  \nThe authors of this paper are also the authors of a set of viewpoints for software architecture (known informally as the “Rozanski and Woods set” and defined in [1]) . The original set of viewpoints defined in our book defines 6 viewpoints to guide the architectural design of information systems. However a “context”view that shows the overall context of the system being designed was not part of the set. This short paper explains why a context viewpoint was not defined in the original set and why, in the light of experience, the authors have found one to be necessary in practice. An outline definition of a context viewpoint for our viewpoint set is then provided, along with a brief discussion of how other viewpoint set authors have addressed this need.  \n2. Motivation for the Work  \nThe process of software architecture involves both inward looking and outward looking concerns. The former are concerned with the details of the internals of the system and the latter are concerned with how the system interacts with its environment and serves the needs of its primary stakeholders (such as acquirers, end-users and support staff members) .  \nMost software architecture definition and description techniques focus on internal concerns and in particular how the system’s internal structures are designed and represented. This is perfectly natural, asthe deliverables from software architecture activities  \nare a set of descriptions of the system’s internal structures, albeit with their design directly motivated and traceable to a set of stakeholder concerns.  \nWhen we defined our viewpoint set, we also focused on the internal structures of the system and our viewpoint set comprises 6 viewpoints, namely the Functional, Information, Concurrency, Development, Deployment and Operational viewpoints. All of these viewpoints guide the development of views that describe one or more aspects of the system’s internal structure.  \nWhen defining the viewpoint set, we made the assumption that the system’s requirements had been largely defined and that the work products of this activity would include clear statements of the system’s requirements including the system’s runtime context (i.e. the external actors that the system would be expected to interact with) . While we recognise that there is extensive interplay between architecture, design and requirements definition, leading to an iterative approach resulting in interaction and change to the requirements, our assumption was that the system context would be defined by someone other than the architect. After all, if the system context isn’t well defined, how can the requirements be written?  \nExperience has shown us to be wrong!  \nIn reality, the software architect usually needs to include a definition of the system’s context as part of their architectural description (and so create a view for it) . The reasons for this include:  \n• the system context simply not being included in the requirements gathering exercise;  \n• a system context being loosely defined b","cbCail8ILz2Drd9R","https://ap.wps.com/l/cbCail8ILz2Drd9R","pdf",215751,"English","# 1. Introduction\n# 2. Motivation for the Work\n# 3. Defining the Context Viewpoint\n## 3.1. Overview of the Viewpoint\n## 3.2. Concerns","[{\"question\":\"What problem does a Context view solve in software architecture descriptions?\",\"answer\":\"It defines the system’s environment and external dependencies by answering how the system relates technically to elements in its wider environment.\"},{\"question\":\"Why was a context viewpoint missing from the original viewpoint set?\",\"answer\":\"The original set focused on internal structures and assumed the system context would be defined elsewhere, so a context viewpoint was not included as a formal viewpoint.\"},{\"question\":\"What concerns does the Context view address?\",\"answer\":\"It focuses on the identity and responsibilities of external entities, including defining interactions even when they are irregular or only occur periodically.\"}]","The System Context Architectural Viewpoint | PDF"]