[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-0-en-105":3,"doc-seo-649978-105":59,"doc-detail-649978-en":129},{"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":122,"head_meta":124,"extra_data":126,"updated_unix":128},105,"en","product-design-schematics-structured-diagramming-for-requirements-engineering","PRODUCT DESIGN SCHEMATICS - Structured diagramming for requirements engineering","","Product Design Schematics (PDS) propose structured diagramming to improve requirements engineering during early product design. The approach argues that many design errors originate from overly simple or overlooked requirements and often surface late. PDS uses diagrams instead of lengthy text to clarify holistic, coarse-level requirements, support stakeholder agreement, and stimulate innovative designer cognition. It is framed within Artefact-Centred Modelling (ACM) and uses concept-map style networks to represent system-wide requirements relationships.",{"@graph":69,"@context":121},[70,84,104],{"@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/product-design-schematics-structured-diagramming-for-requirements-engineering/649978/",{"url":83,"name":65,"@type":85,"image":86,"author":91,"headline":65,"publisher":94,"fileFormat":97,"inLanguage":63,"description":67,"dateModified":98,"datePublished":98,"encodingFormat":97,"isAccessibleForFree":99,"interactionStatistic":100},"DigitalDocument",{"url":87,"@type":88,"width":89,"height":90},"https://docshare.wps.com/thumbnails/product-design-schematics-structured-diagramming-for-requirements-engineering/649978.png","ImageObject",300,407,{"name":92,"@type":93},"Well Done","Person",{"url":74,"name":95,"@type":96},"DocShare","Organization","application/pdf","2026-10-24",true,{"@type":101,"interactionType":102,"userInteractionCount":4},"InteractionCounter",{"@type":103},"ViewAction",{"@type":105,"mainEntity":106},"FAQPage",[107,113,117],{"name":108,"@type":109,"acceptedAnswer":110},"Why does the paper emphasize early requirements understanding in product design?","Question",{"text":111,"@type":112},"Many engineering errors trace back to simple requirements that seem obvious in hindsight, and these can occur early but remain undetected until later, causing significant losses. Early, holistic requirements understanding is therefore crucial.","Answer",{"name":114,"@type":109,"acceptedAnswer":115},"What is a product design schematic (PDS) and how is it used?",{"text":116,"@type":112},"A PDS is a diagram rather than a table or textual description. It helps convey requirements information clearly, reduce the burden of reading long linear text, and stimulate effective product design thinking.",{"name":118,"@type":109,"acceptedAnswer":119},"How do PDSs relate to Artefact-Centred Modelling (ACM)?",{"text":120,"@type":112},"PDSs fit into ACM by addressing requirements of the product only, not the product’s manufacture or the organization of designers. This positioning avoids certain reflective-system paradoxes and focuses on requirements representation.","https://schema.org",{"og:url":83,"og:type":123,"og:title":65,"og:site_name":95,"og:description":67},"article",{"robots":125,"canonical":83},"index,follow",{"doc_id":127,"site_id":62},649978,1792813053,{"code":4,"msg":5,"data":130},{"doc_id":127,"user_id":131,"nickname":92,"user_avatar":132,"doc_module":4,"category_id":39,"category_name":40,"doc_title":65,"doc_description":67,"doc_content":133,"file_id":134,"file_url":135,"file_type":136,"file_size":137,"view_count":4,"is_deleted":4,"is_public":8,"is_downloadable":8,"audit_status":8,"page_count":39,"language":138,"language_code":63,"site_id":62,"html_lang":63,"table_of_contents":139,"faqs":140,"seo_title":141,"seo_description":67,"update_tm":128,"read_time":46},5909892210082,"https://ap-avatar.wpscdn.com/avatar/56001069da27c9f41e8?x-image-process=image/resize,m_fixed,w_180,h_180&k=1789614185077863061","INTERNATIONAL DESIGN CONFERENCE-DESIGN 2004 Dubrovnik, May 18-21, 2004.  \nPRODUCT DESIGN SCHEMATICS: STRUCTURED DIAGRAMMING FOR REQUIREMENTS ENGI  \nNEERING  \nF. A. Salustri and J. Parmar  \nKeywords: requirements engineering, diagrammatic representation, design problem analysis, concept maps  \n1. Introduction and Objectives  \nA clear understanding of a design problem is essential for designing an effective product. That understanding is reflected in a well-specified set of requirements. Many engineering problems can be traced back to extremely simple requirements problems that seem “obvious” in hindsight (e.g. the fuselage of the Sikorsky S-92 helibus was originally designed without a pass-through for wiring bundles to connect cockpit instrumentation to control surfaces in the tail) . Such errors often occur early in the design process, but might not be caught until much later, resulting in significant losses. Analysis of detailed requirements, often the focus of many development projects, rarely treats the holistic world-view of the product’s requirements at the coarsest levels – yet it is at the coarse level where many errors occur. The issue is more that just requirements analysis. It also involves eliciting the requirements and representing them in a way that stimulates the design of effective products, and the establishment of rational cognitive product models in designers’minds. Also, all the designers must agree that they are using the same (mental) model of the problem and its solutions.  \nDesign requirements must therefore (a) focus the designers’ attention on key issues, (b) help ensure that all product stakeholders (including the client) agree on the nature of the problem, (c) stimulate innovative thinking,(d) incur relatively low administrative overhead, and (e) facilitate navigation and searching of requirements information.  \nThe authors’ solution, called a product design schematic (PDS), is being developed to meet these criteria. A PDS is a diagram rather than a table or textual description. Diagrams can alleviate the sometimes onerous burden of understanding long, linear, text-based descriptions of requirements. PDSs are part of a larger project, called design schematics, intended to develop diagramming tools for all the early stages of design. In this paper, however, only PDSs will be discussed. While it will become obvious that software to draw PDSs is very important, that software is still under development. In this paper, we will focus on the PDS format itself and not on the implementation of a PDS tool.  \nIt is essential to understand that the focus here is on stimulating the human designer to recognise key system-wide requirements, rather than focusing on the (partial) automation of detailed requirements management.  \n2. Method of Development  \nPDSs fit into Salustri’s overall research framework, Artefact-Centred Modelling (ACM) [Salustri, 1995] . ACM distinguishes between models, languages, and theories with respect to products, designers, and design management agents. This limits the possibility of reflection, which can lead to paradoxical situations. (The classic example of the kind of paradox that can arise from reflective systems is the single statement This sentence is false.) PDSs fit into this scheme by addressing only requirements of the product and not of the product’s manufacture, the designers who create it, or the organisation where the designers work. While this may seem to be a limitation, PDSs are just one kind of design schematic. The complete tool set will cover all these sectors of design engineering. More information on design schematics is available in [Salustri and Parmar, 2003] .  \nThe authors examined a number of works in requirements specification and design problem analysis (e.g. Dym and Little, Suh, Pugh, and Steward) . Additionally, our work was informed by experiences in teaching design and the observation that a simple but systematic approach to requirements engineering helps ","cbCainmvetKI2XaU","https://ap.wps.com/l/cbCainmvetKI2XaU","pdf",202284,"English","# Introduction and Objectives\n## Method of Development\n## Concept maps and diagramming techniques","[{\"question\":\"Why does the paper emphasize early requirements understanding in product design?\",\"answer\":\"Many engineering errors trace back to simple requirements that seem obvious in hindsight, and these can occur early but remain undetected until later, causing significant losses. Early, holistic requirements understanding is therefore crucial.\"},{\"question\":\"What is a product design schematic (PDS) and how is it used?\",\"answer\":\"A PDS is a diagram rather than a table or textual description. It helps convey requirements information clearly, reduce the burden of reading long linear text, and stimulate effective product design thinking.\"},{\"question\":\"How do PDSs relate to Artefact-Centred Modelling (ACM)?\",\"answer\":\"PDSs fit into ACM by addressing requirements of the product only, not the product’s manufacture or the organization of designers. This positioning avoids certain reflective-system paradoxes and focuses on requirements representation.\"}]","PRODUCT DESIGN SCHEMATICS - Structured diagramming for requirements engineering | PDF"]