[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-243100-105":53,"doc-detail-243100-en":127},{"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":120,"head_meta":122,"extra_data":124,"updated_unix":126},105,"en","guidelines-for-planning-and-development-of-software-for-buildings-and-building-systems-abstract-templates","Guidelines for Planning and Development of Software for Buildings and Building Systems - Abstract & Templates","","From inception to completion, software development projects need structure and organization to deliver good-quality, user-friendly software on time and within budget. The paper presents a structured approach built around the System Development Life Cycle (SDLC), explaining how selecting and applying an SDLC model throughout development supports clear phase-by-phase progress. Using a Waterfall model, it details research team steps and supplies checklists, requirements/specification templates, and a project schedule template.",{"@graph":63,"@context":119},[64,80,102],{"@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/guidelines-for-planning-and-development-of-software-for-buildings-and-building-systems-abstract-templates/243100/",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/guidelines-for-planning-and-development-of-software-for-buildings-and-building-systems-abstract-templates/243100.png","ImageObject",442,249,{"name":88,"@type":89},"Mia  ","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-10-19","2026-09-12",true,{"@type":98,"interactionType":99,"userInteractionCount":101},"InteractionCounter",{"@type":100},"ViewAction",9,{"@type":103,"mainEntity":104},"FAQPage",[105,111,115],{"name":106,"@type":107,"acceptedAnswer":108},"What purpose do the guidelines serve in software development projects?","Question",{"text":109,"@type":110},"They provide structured steps to organize and structure software development from inception to completion, supporting on-time delivery and staying within budget.","Answer",{"name":112,"@type":107,"acceptedAnswer":113},"How does the paper explain the SDLC in relation to development phases?",{"text":114,"@type":110},"It presents SDLC as a conceptual model that divides development into phases, where each phase has a distinct role and serves as a building block for the next.",{"name":116,"@type":107,"acceptedAnswer":117},"What does the paper include to help teams track and document progress?",{"text":118,"@type":110},"It provides a one-page summary usable as a checklist of team progress, blank and case illustration templates for requirements/specifications, and a blank project schedule template.","https://schema.org",{"og:url":78,"og:type":121,"og:title":59,"og:site_name":91,"og:description":61},"article",{"robots":123,"canonical":78},"index,follow",{"doc_id":125,"site_id":56},243100,1791727928,{"code":4,"msg":5,"data":128},{"doc_id":125,"user_id":129,"nickname":88,"user_avatar":130,"doc_module":9,"category_id":8,"category_name":11,"doc_title":59,"doc_description":61,"doc_content":131,"file_id":132,"file_url":133,"file_type":134,"file_size":135,"view_count":101,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":136,"language":137,"language_code":57,"site_id":56,"html_lang":57,"table_of_contents":138,"faqs":139,"seo_title":140,"seo_description":61,"update_tm":141,"read_time":35},687207024478,"https://ap-avatar.wpscdn.com/davatar_a8503ba1806abce46bf441b54a3ca4cd","NISTIR 7499  \n| U.S. Department of Commerce National Institute of Standards and Technology |  | Office of Applied Economics\u003Cbr>Building and Fire Research Laboratory Gaithersburg, MD 20899 |\n| --- | --- | --- |\n\nGuidelines for Planning and Development of Software for Buildings and Building Systems  \nPriya D. Lavappa  \nNISTIR 7499  \n\n| U.S. Department of Commerce National Institute of Standards and Technology |  | Office of Applied Economics\u003Cbr>Building and Fire Research Laboratory Gaithersburg, MD 20899 |\n| --- | --- | --- |\n\nGuidelines for Planning and Development of Software for Buildings and Building Systems  \nPriya D. Lavappa  \nSponsored by:  \nNational Institute of Standards and Technology Building and Fire Research Laboratory  \nJune 2008  \nU.S. DEPARTMENT OF COMMERCE  \nCarlos M. Gutierrez, Secretary  \nNATIONAL INSTITUTE OF STANDARDS AND TECHNOLOGY James Turner, Deputy Director  \nAbstract  \nFrom inception to completion, software development projects need structure and organization so that good quality, user-friendly software is produced on time and within budget. The structured approach presented in this paper helps achieve those goals.  \nThe System Development Life Cycle (SDLC) is a conceptual model for software development that divides up the process into different phases. Each phase has a distinct role to play in the development life cycle, and is a building block for the next phase. There are many SDLC models, each emphasizing different aspects of the life-cycle. Implementing a structured approach requires selecting a model and utilizing it throughout the development life cycle.  \nThis paper selects a Waterfall model for planning and executing a software project; describes the steps each research team member takes, by project phase, in the development of the software product; provides a one-page summary of those steps for making a checklist of team progress; provides a blank and case illustration template for each team member to fill out in providing requirements or specifications ofthe software and provides a blank project schedule template for documenting the tasks required to implement the software project design.  \nFollowing a structured process enables software development projects to be organized and have a clear path to completion. Implementing a structured process is crucial for developing good quality software in an efficient manner.  \nKeywords: System Development Life Cycle, Waterfall model, software project management, software development, software requirements template.  \niv  \nPreface  \nThis paper describes the steps in the software development process, knowledge of which is useful to organize and structure software development projects. Structuring a software development project from inception provides a clear path to completion. This set of guidelines provides a software development team with a progression of steps to conceive code, test, revise, and publish software applications that will best satisfy clients’ software needs. Following these steps will clarify the respective roles for a software development team, show how their tasks fit together in a time schedule, and contribute to an on-time, successful, within budget software product. These steps have been used by the author on numerous software development projects, both large and small, using an assortment of technologies. These projects have focused on various topics including: economics, biological sciences, insurance, taxation, and accounting. The staff members of the Office of Applied Economics in the Building and Fire Research Laboratory at the National Institute of Standards and Technology use these guidelines and templates in their software development projects.  \nDisclaimer: Certain trade names and company products are mentioned in the text in order to adequately specify the technical procedures and equipment used. In no case does such identification imply recommendation or endorsement by the National Institute of Standards and Technology, ","cbCaicsDB3zDeIvd","https://ap.wps.com/l/cbCaicsDB3zDeIvd","pdf",506915,49,"English","# Abstract\n# Preface\n## Structured software development workflow\n## SDLC and Waterfall model approach\n## Templates for requirements and scheduling\n# Disclaimer\n# Acknowledgments","[{\"question\":\"What purpose do the guidelines serve in software development projects?\",\"answer\":\"They provide structured steps to organize and structure software development from inception to completion, supporting on-time delivery and staying within budget.\"},{\"question\":\"How does the paper explain the SDLC in relation to development phases?\",\"answer\":\"It presents SDLC as a conceptual model that divides development into phases, where each phase has a distinct role and serves as a building block for the next.\"},{\"question\":\"What does the paper include to help teams track and document progress?\",\"answer\":\"It provides a one-page summary usable as a checklist of team progress, blank and case illustration templates for requirements/specifications, and a blank project schedule template.\"}]","Guidelines for Planning and Development of Software for Buildings and Building Systems - Abstract & Templates | PDF",1789199995]