[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-240393-105":53,"doc-detail-240393-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","in-search-of-excellent-requirements-process-impact-optimizing-customer-involvement","In Search of Excellent Requirements - Process Impact - OPTIMIZING CUSTOMER INVOLVEMENT","","Requirements specification quality determines whether software meets stated specifications and truly satisfies customer needs. The document argues that aligning those two notions requires rigor in gathering, documenting, and validating user requirements. It presents an approach from a multiyear process improvement effort, using active customer participation via a project champion, structured IEEE-like specification documents, dialogue maps for UI abstraction, and extensive prototypes. Results include reduced expectation gaps between the needed problem solution and what developers build.",{"@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":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/in-search-of-excellent-requirements-process-impact-optimizing-customer-involvement/240393/",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/in-search-of-excellent-requirements-process-impact-optimizing-customer-involvement/240393.png","ImageObject",442,249,{"name":88,"@type":89},"Đào","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-11-02","2026-09-11",true,{"@type":98,"interactionType":99,"userInteractionCount":30},"InteractionCounter",{"@type":100},"ViewAction",{"@type":102,"mainEntity":103},"FAQPage",[104,110,114],{"name":105,"@type":106,"acceptedAnswer":107},"What is the core problem addressed about requirements quality?","Question",{"text":108,"@type":109},"Requirements quality is framed as both meeting stated specifications and satisfying actual customer needs, which often diverge. The document emphasizes unifying these into a single vision for the final product.","Answer",{"name":111,"@type":106,"acceptedAnswer":112},"What does the “project champion” model require?",{"text":113,"@type":109},"A project champion is an actual end user with management support and a clear vision of the product. The champion represents the full customer community’s interests and mediates between customers and developers.",{"name":115,"@type":106,"acceptedAnswer":116},"Which four practices make up the quest for excellent requirements specifications?",{"text":117,"@type":109},"The document lists four components: strong customer participation through project champions, structured specification documents like IEEE format, dialogue maps for high-level modeling of complex user interfaces, and extensive use of prototypes to clarify needs and explore design alternatives.","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},240393,1791729937,{"code":4,"msg":5,"data":127},{"doc_id":124,"user_id":128,"nickname":88,"user_avatar":129,"doc_module":9,"category_id":8,"category_name":11,"doc_title":59,"doc_description":61,"doc_content":130,"file_id":131,"file_url":132,"file_type":133,"file_size":134,"view_count":30,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":135,"language":136,"language_code":57,"site_id":56,"html_lang":57,"table_of_contents":137,"faqs":138,"seo_title":139,"seo_description":61,"update_tm":140,"read_time":76},1374402968488,"https://ap-avatar.wpscdn.com/davatar_29158cc5080c5b710cf443261637dec0","In Search of Excellent Requirements1  \nKarl E. Wiegers  \nProcess Impact  \n[www.processimpact.com](www.processimpact.com)  \n“I’ll go find out what they want, and the rest of you start coding.” This caption from a cartoon is uncomfortably close to the way some software organizations still treat the requirements specification process. Contemporary definitions of“quality” include the concepts of both meeting stated specifications and satisfying the actual customer requirements, which sadly are not always the same thing. Converging these two components into a unified vision of the final product is the linchpin of successful software development.  \nThe problem of informal, incomplete, and poorly documented requirements is prevalent in small software groups, where a more casual development process lacks the rigor (and perhaps the rigidity) often found in larger organizations. As part of a multiyear process improvement effort [1, 2], our small software group focused on improved requirements specifications as the starting point for increasing our software quality and productivity.  \nOur quest for excellent requirements specifications has four components, which address the challenges of gathering, documenting, and validating user needs:  \n1. A high degree of customer participation in the development effort through a “project champion” model.  \n2. Preparation of structured specification documents in a format similar to the IEEE standard for software requirements specifications.  \n3. Construction of“dialog maps,” a variant of state transition diagrams that model complex user interfaces at a high level of abstraction.  \n4. Extensive use of prototypes to more fully elucidate user needs and explore alternative designs for satisfying them.  \nWhile these practices have not been universally applied on every project, we invariably obtain better results when we use them. Our experience indicates that these techniques can greatly reduce the expectation gap between the system the customer really needs to solve his problems and the system the developer decides to build for him.  \nOPTIMIZING CUSTOMER INVOLVEMENT  \nLike many software organizations in large companies, our group develops products for internal corporate use only. The members of our software group are not experts in the specialized application domains that we support. Consequently, it is not reasonable to expect us to make sound business or technical decisions on behalf of the customers, or to resolve conflicting requirements supplied by different end users, or to set priorities for the many requirements that might be collected. On the other hand, we believe that customer involvement is the most critical factor in software quality, and that our most difficult problem is sharing the vision of the final product with the customer [3] .  \n1 Published in The Journal of the Quality Assurance Institute, January 1995. Reprinted with permission from the Quality Assurance Institute.  \nIn Search of Excellent Requirements Page 2  \nOur objective was to devise a mechanism by which the challenge of correctly defining anew system was shared by the developers and a small number of knowledgeable and energetic customer representatives. We wished to avoid the common scenario of requirements changing every day as yet another user heard about the program being built and threw in his two cents worth.  \nThe Project Champion  \nSince 1986, most of our projects have included one or more key customer representatives, or “project champions,” as integral members of the development team. The project champion isnot a manager or a funding sponsor, but an actual end user of the system being constructed. The ideal champion is a respected member of the user community, eagerly anticipates delivery of the product, has a vision of what it should be, and has management support.  \nOur expectations of project champions are part of our written software development guidelines. The project champion is empowered to represent and make","cbCailWSqvqAx562","https://ap.wps.com/l/cbCailWSqvqAx562","pdf",32299,9,"English","# Process Impact\n## OPTIMIZING CUSTOMER INVOLVEMENT\n## The Project Champion\n## Project Champion Expectations","[{\"question\":\"What is the core problem addressed about requirements quality?\",\"answer\":\"Requirements quality is framed as both meeting stated specifications and satisfying actual customer needs, which often diverge. The document emphasizes unifying these into a single vision for the final product.\"},{\"question\":\"What does the “project champion” model require?\",\"answer\":\"A project champion is an actual end user with management support and a clear vision of the product. The champion represents the full customer community’s interests and mediates between customers and developers.\"},{\"question\":\"Which four practices make up the quest for excellent requirements specifications?\",\"answer\":\"The document lists four components: strong customer participation through project champions, structured specification documents like IEEE format, dialogue maps for high-level modeling of complex user interfaces, and extensive use of prototypes to clarify needs and explore design alternatives.\"}]","In Search of Excellent Requirements - Process Impact - OPTIMIZING CUSTOMER INVOLVEMENT | PDF",1789160924]