[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-240855-105":53,"doc-detail-240855-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","forward-engineering-completeness-for-software-using-requirements-validation-framework-abstract","Forward Engineering Completeness for Software Using Requirements Validation Framework - Abstract","","Software development environments often underemphasize validating user requirements during requirement gathering, which drives expensive modifications later in maintenance. Identifying accurate requirements from user stories and assessing how effective delivered work is for the software industry remains a difficult task. The study proposes a new measurement method for forward engineering completeness using a requirements validation framework. Completeness is evaluated through functional and non-functional attributes and unadopted reuse-code attributes, with attribute quality levels derived from source-code internal quality, reducing development time and costs. A case study details the measurement process.",{"@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":51,"@type":70,"position":76},"https://docshare.wps.com/template/general/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/forward-engineering-completeness-for-software-using-requirements-validation-framework-abstract/240855/",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/forward-engineering-completeness-for-software-using-requirements-validation-framework-abstract/240855.png","ImageObject",442,249,{"name":88,"@type":89},"Elsa","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-09-20","2026-09-11",true,{"@type":98,"interactionType":99,"userInteractionCount":73},"InteractionCounter",{"@type":100},"ViewAction",{"@type":102,"mainEntity":103},"FAQPage",[104,110,114],{"name":105,"@type":106,"acceptedAnswer":107},"Why is forward engineering completeness difficult to measure in practice?","Question",{"text":108,"@type":109},"Software companies often ignore user requirements validation during requirement gathering, leading to many later modifications. This makes it challenging to identify accurate requirements and judge whether delivered deliverables meet customer needs.","Answer",{"name":111,"@type":106,"acceptedAnswer":112},"How does the proposed measurement approach evaluate forward engineering completeness?",{"text":113,"@type":109},"The approach measures completeness in two steps: building a software component structure to find functional and non-functional requirements rejected in the validation framework, then determining completeness from component-based development while considering functional and non-functional completeness attributes and unadopted reuse-code attributes.",{"name":115,"@type":106,"acceptedAnswer":116},"What role do source-code quality and unadopted attributes play?",{"text":117,"@type":109},"Quality levels for the attributes are assigned based on the internal quality of the source code. Attributes that negate to be used are treated as unadopted attributes in the completeness measurement.","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},240855,1789166534,{"code":4,"msg":5,"data":127},{"doc_id":124,"user_id":128,"nickname":88,"user_avatar":129,"doc_module":9,"category_id":50,"category_name":51,"doc_title":59,"doc_description":61,"doc_content":130,"file_id":131,"file_url":132,"file_type":133,"file_size":134,"view_count":73,"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":125,"read_time":73},137455077381,"https://ap-avatar.wpscdn.com/davatar_994ba38a5ba835b3df7d355c54d3ed8d","Forward Engineering Completeness for Software by Using Requirements Validation Framework  \nNayyar Iqbal 1,2,3, Jun Sang1,2, Min Gao1,2, Haibo Hu 1,2, Hong Xiang 1,2  \n1Key Laboratory of Dependable Service Computing in Cyber Physical Society of Ministry of Education,  \nChongqing University, Chongqing 400044, China  \n2School of Big Data & Software Engineering, Chongqing University, Chongqing 401331, China 3Department of Computer Science, University of Agriculture Faisalabad, Faisalabad 38000, Pakistan  \n[nayyariqbal@cqu.edu.cn](nayyariqbal@cqu.edu.cn), [jsang@cqu.edu.cn](jsang@cqu.edu.cn), [gaomin@cqu.edu.cn](gaomin@cqu.edu.cn), [haibo.hu@cqu.edu.cn](haibo.hu@cqu.edu.cn), [xianghong@cqu.edu.cn](xianghong@cqu.edu.cn)  \nAbstract—In software development environment, software companies usually ignore the user requirements validation process in requirement gathering phase, which results in large number of modifications being required in the software maintenance phase to fulfill the customer requirements. Identification of accurate requirements from user stories and determining the effectiveness of work deliverable of software industry has always been a challenging task. In this paper, a new measurement approach for forward engineering completeness for software was introduced by using requirements validation framework. The forward engineering completeness for software was measured in two steps. In the first step, software component structure was developed in order to find the functional and nonfunctional requirements rejected by the customers in the requirement validation framework. In the second step, completeness of software from component-based development was determined in which the following parameters, such as functional, non-functional completeness attributes, were considered in the measurement process, and the unadopted attributes of the reuse code were also considered. Quality level for the attributes were assigned based upon the valuation of interior quality of the source code. Therefore, it resulted in the reduction of development time required for the software and the cost required for the software development was also reduced. A case study was incorporated in this research to explain the measurement process of forward engineering completeness. If the forward engineering code is satisfying the quality standards, then the code is in the completeness form. The attributes of code that negates to be used were considered as unadopted attributes.  \nKeywords-completeness; forward engineering; functional requirements; non-functional requirements; requirements engineering; validation  \nI. INTRODUCTION  \nIt has been observed that software industries that abused the Requirement Engineering (RE) in the software development process resulted in the project failures [1-6] . Ana-Maria et al. [7] argued that business analysts needed to focus on requirement gathering techniques in a technically responsible way. Question had been raised as to the  \nDOI reference number: 10. 18293/SEKE2019-144  \nrelationship between the functional and non-functional requirements, with some, such as Vishal and Xiaoqing [8], argued that there was reciprocal relationship. Software quality measurement is one of the most complicated tasks in software design methodology [9] . Quality of the software can be determined by the success of software system for this various parameters, framework and methodologies has been proposed [10] . Forward Engineering as defined by Pressman [11] “Inmost cases, forward engineering does not simply create a modern equivalent of an older program. Rather, new user and technology requirements are integrated into the reengineering effort. The redeveloped program extends the capabilities of the older application”. Reverse and forward engineering are practiced in the legacy systems to extend the system usable lifespan [12] .  \nRequirements are client’s invariant statements related to sub system or system [13] . Functional requirement describ","cbCairGFcUfp6RF9","https://ap.wps.com/l/cbCairGFcUfp6RF9","pdf",632267,6,"English","# Abstract\n# Introduction","[{\"question\":\"Why is forward engineering completeness difficult to measure in practice?\",\"answer\":\"Software companies often ignore user requirements validation during requirement gathering, leading to many later modifications. This makes it challenging to identify accurate requirements and judge whether delivered deliverables meet customer needs.\"},{\"question\":\"How does the proposed measurement approach evaluate forward engineering completeness?\",\"answer\":\"The approach measures completeness in two steps: building a software component structure to find functional and non-functional requirements rejected in the validation framework, then determining completeness from component-based development while considering functional and non-functional completeness attributes and unadopted reuse-code attributes.\"},{\"question\":\"What role do source-code quality and unadopted attributes play?\",\"answer\":\"Quality levels for the attributes are assigned based on the internal quality of the source code. Attributes that negate to be used are treated as unadopted attributes in the completeness measurement.\"}]","Forward Engineering Completeness for Software Using Requirements Validation Framework - Abstract | PDF"]