[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-241294-105":53,"doc-detail-241294-en":126},{"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":119,"head_meta":121,"extra_data":123,"updated_unix":125},105,"en","set-up-gui-scenario-duplicate-for-release-test","Set Up GUI Scenario Duplicate for Release Test","","This paper presents a project with Allied Telesis to duplicate an SD-WAN and AIO (Allied Telesis Internet-Based Orchestrator) simulated customer scenario for release testing. The original scenario applied exclusively to the Tokyo office and caused bugs that Christchurch developers struggled to troubleshoot due to remote-only access. The work focused on duplicating and documenting the scenario locally to remove interoffice communication barriers, improve debugging efficiency, and enable direct progression into testing for Christchurch teams.",{"@graph":63,"@context":118},[64,80,101],{"@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":26,"@type":70,"position":76},"https://docshare.wps.com/template/posters/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/set-up-gui-scenario-duplicate-for-release-test/241294/",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/set-up-gui-scenario-duplicate-for-release-test/241294.png","ImageObject",442,249,{"name":88,"@type":89},"Aran","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-10-17","2026-09-12",true,{"@type":98,"interactionType":99,"userInteractionCount":9},"InteractionCounter",{"@type":100},"ViewAction",{"@type":102,"mainEntity":103},"FAQPage",[104,110,114],{"name":105,"@type":106,"acceptedAnswer":107},"Why was the SD-WAN and AIO scenario duplicated for the Christchurch office?","Question",{"text":108,"@type":109},"The Tokyo-only scenario was difficult for Christchurch developers to access remotely, which slowed troubleshooting. Duplicating and documenting it locally removed interoffice communication barriers and enabled more direct testing.","Answer",{"name":111,"@type":106,"acceptedAnswer":112},"What agile method was used to manage project tasks?",{"text":113,"@type":109},"Kanban was used to visualize task status and manage work efficiently with improved team productivity and results.",{"name":115,"@type":106,"acceptedAnswer":116},"How were risks and quality assurance managed in the project?",{"text":117,"@type":109},"A Microsoft Risk Template tool was used to track possible risks and control actions. A Virginia Tech quality assurance table was used to define when QA activities occurred, their frequency, standards, and related actions.","https://schema.org",{"og:url":78,"og:type":120,"og:title":59,"og:site_name":91,"og:description":61},"article",{"robots":122,"canonical":78},"index,follow",{"doc_id":124,"site_id":56},241294,1792201625,{"code":4,"msg":5,"data":127},{"doc_id":124,"user_id":128,"nickname":88,"user_avatar":129,"doc_module":9,"category_id":25,"category_name":26,"doc_title":59,"doc_description":61,"doc_content":130,"file_id":131,"file_url":132,"file_type":133,"file_size":134,"view_count":9,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":73,"language":135,"language_code":57,"site_id":56,"html_lang":57,"table_of_contents":136,"faqs":137,"seo_title":138,"seo_description":61,"update_tm":139,"read_time":9},137455076865,"https://ap-avatar.wpscdn.com/davatar_29158cc5080c5b710cf443261637dec0","Set Up GUI Scenario Duplicate for Release Test  \nKunihito Uemura  \nAra | Te Pūkenga, Christchurch, NZ [kunihito.uemura@gmail.com](kunihito.uemura@gmail.com)  \nEddie Correia (Supervisor)  \nAra | Te Pūkenga, Christchurch, NZ [eddie.correia@ara.ac.nz](eddie.correia@ara.ac.nz)  \nDavid Weir (Supervisor)  \nAra | Te Pūkenga, Christchurch, NZ [david.weir@ara.ac.nz](david.weir@ara.ac.nz)  \nABSTRACT  \nThis paper describes the project done at Allied Telesis involving SD-WAN and AIO (Allied Telesis Internet-Based Orchestrator) (Allied Telesis, 2022) . Its focus was a simulated customer scenario to identify bugs that the Tokyo office was finding problematic. Christchurch developers needed access to scenarios as part of their troubleshooting steps. However, since it was located in Japan, the only way to access it was remotely. This project was implemented to duplicate the scenario to enable it to be used to resolve issues in the scenario and increase work efficiency.  \nKeywords: SD-WAN, network diagram, GUI, Kanban, 1. INTRODUCTION  \nAllied Telesis is a network infrastructure and telecommunication company. They provide equipment for enterprise and smaller customers, and design software for switches, routers and wireless access points, as well as build graphical user interfaces. They have 1,600 employees in over 30 countries and territories. With over 160 patents and 7 research and development centres, Allied Telesis is a company that aims to excel in performance and product reliability (Allied Telesis, 2023) . This document describes the project details, process, and methodology.  \nFigure 1  \nSet up GUI Scenario Duplicate for Release Test Poster  \nThis quality assured poster paper appears at the 14th annual conference of Computing and Information Technology Research and Education New Zealand (CITRENZ 2023) and the 36th Annual Conference of the National Advisory Committee on Computing Qualifications [hosted in Auckland], September 27-29.  \n2. BACKGROUND  \nSD-WAN and AIO (Allied Telesis Internet Based Orchestrator) are simulated customer scenarios that identify bugs. For several reasons, the SD-WAN and AIO scenario that exclusively applied to the Tokyo office has been problematic. Developers in Christchurch required access to the release test scenario as part of the troubleshooting procedure, but the only way to access the scenario was remotely as it was located in Japan. This made communication between the Christchurch and Tokyo offices difficult for the developers to track down and resolve the problem at hand.  \nTherefore, duplicating and documenting the SD-WAN and AIO scenario in the Christchurch office eliminated the interoffice communication that had hampered the developer's ability to debug issues. In addition, efficiency gains could be expected because Christchurch testers working in scenarios could directly proceed with testing.  \nIndustry Goals  \n• Scenario duplication. Make a duplicate SD-WAN and AIO scenario for the Christchurch office.  \n• Scenario accuracy. Make sure the scenarios perform as intended.  \n• Documentation. Create duplicate scenarios and content documentation for testing in the Christchurch office.  \nStudent Goals  \n• To gain networking skills and knowledge.  \n• To improve project and time management skills.  \n• To improve communication skills.  \n3. PROCESS  \nThis section describes the processes for providing the academic and industry deliverables were carried out in the project.  \n3.1 Project Management  \nProject management is one of the important processes to lead a project to success. The project was divided into five phases:  \n• Plan-Project Plan, schedules.  \n• Define-Scenario requirements.  \n• Analysis-Study the scenario.  \n• Design-Set up and commission the scenario.  \n• Test-Confirm scenario performance.  \n3.2 Kanban  \nKanban was utilised in the project, to manage tasks. Kanban methodology is one of the agile project management models and a visual method for project management. It is a project management stru","cbCaipAWrIilhCTD","https://ap.wps.com/l/cbCaipAWrIilhCTD","pdf",628287,"English","# ABSTRACT\n# 1. INTRODUCTION\n# 2. BACKGROUND\n# Industry Goals\n# Student Goals\n# 3. PROCESS\n## 3.1 Project Management\n## 3.2 Kanban\n## 3.3 Risk Management\n## 3.4 Quality Assurance\n# 4. OUTCOME\n## Industry Deliverables\n## Academic Deliverables\n# 5. CONCLUSION","[{\"question\":\"Why was the SD-WAN and AIO scenario duplicated for the Christchurch office?\",\"answer\":\"The Tokyo-only scenario was difficult for Christchurch developers to access remotely, which slowed troubleshooting. Duplicating and documenting it locally removed interoffice communication barriers and enabled more direct testing.\"},{\"question\":\"What agile method was used to manage project tasks?\",\"answer\":\"Kanban was used to visualize task status and manage work efficiently with improved team productivity and results.\"},{\"question\":\"How were risks and quality assurance managed in the project?\",\"answer\":\"A Microsoft Risk Template tool was used to track possible risks and control actions. A Virginia Tech quality assurance table was used to define when QA activities occurred, their frequency, standards, and related actions.\"}]","Set Up GUI Scenario Duplicate for Release Test | PDF",1789173283]