[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-243671-105":53,"doc-detail-243671-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","system-development-lifecycle-section-iii-overview","System Development Lifecycle - Section III - Overview","","System Development Lifecycle (SDLC) Section III provides a structured overview of the standard phases and major processes for New York State system development projects. It explains why teams must follow common stages despite differences in tools, software architecture, and build-versus-buy decisions. The section details six core phases—system initiation, requirements analysis, design, construction, acceptance, and implementation—describing the re-examination of business cases, validation of requirements, creation of technical solutions, and shift from building to deployment and data conversion.",{"@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/system-development-lifecycle-section-iii-overview/243671/",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/system-development-lifecycle-section-iii-overview/243671.png","ImageObject",442,249,{"name":88,"@type":89},"Genevieve","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",10,{"@type":103,"mainEntity":104},"FAQPage",[105,111,115],{"name":106,"@type":107,"acceptedAnswer":108},"What is the purpose of the SDLC Section III introduction for New York State agencies?","Question",{"text":109,"@type":110},"It standardizes how system development projects proceed across different environments by describing the six phases and major processes in sufficient detail for project planning and management.","Answer",{"name":112,"@type":107,"acceptedAnswer":113},"What happens during System Initiation in this lifecycle?",{"text":114,"@type":110},"The business case and proposed solution are re-examined to confirm they still address an organizational need, and this validation supports detailed scheduling and staffing estimates.",{"name":116,"@type":107,"acceptedAnswer":117},"How does the project focus change from System Acceptance to System Implementation?",{"text":118,"@type":110},"System Acceptance shifts validation toward users who will operate the system, including checks for data conversion and deployment readiness, while System Implementation covers deployment activities such as training, installation, and transition of ownership.","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},243671,1791728985,{"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":142},1374391974585,"https://ap-avatar.wpscdn.com/davatar_276721f389ce27ea32af1340a28f341c","S E C T I O N T H R E E  \nSystem Development Lifecycle  \nSECTION III: SYSTEM DEVELOPMENT LIFECYCLE  \nTABLE OF CONTENTS  \nIntroduction 3  \n1. SYSTEM INITIATION 15  \n1.1 Prepare for System Initiation 18  \n1.2 Validate Proposed Solution 19  \n1.3 Develop System Schedule 23  \nMeasurements of Success 25  \nPhase Risks/Ways to Avoid Pitfalls 26  \n2. SYSTEM REQUIREMENTS  ANALYSIS 31  \n2.1 Prepare for System Requirements Analysis 36  \n2.2 Determine Business Requirements 38  \n2.3 Define Process Model 49  \n2.4 Define Logical Data Model 51  \n2.5 Reconcile Business Requirements with Models 54  \n2.6 Produce Functional Specification 56  \nMeasurements of Success 63  \nPhase Risks/Ways to Avoid Pitfalls 64  \n3. SYSTEM DESIGN 71  \n3.1 Prepare for System Design 76  \n3.2 Define Technical Architecture 78  \n3.3 Define System Standards 85  \n3.4 Create Physical Database 92  \n3.5 Prototype System Components 94  \n3.6 Produce Technical Specifications 97  \nMeasurements of Success 120  \n4. SYSTEM CONSTRUCTION 129  \n4.1 Prepare for System Construction 134  \n4.2 Refine System Standards 136  \n4.3 Build, Test and Validate (BTV) 137  \n4.4 Conduct Integration and  \nSystem Testing 142  \n4. 5 Produce User and Training Materials147  \n4.6 Produce Technical Documentation 148 Measurements of Success 149 Phase Risks/Ways to Avoid Pitfalls 151  \n5. SYSTEM ACCEPTANCE 157  \n5. 1 Prepare for System Acceptance 162 5.2 Validate Data Initialization  \nand Conversion 163  \n5.3 Test, Identify, Evaluate, React (TIER) 165  \n5.4 Refine Supporting Materials 170  \nMeasurements of Success 171  \nPhase Risks/Ways to Avoid Pitfalls 172  \n6. SYSTEM IMPLEMENTATION 177  \n6.1 Prepare for System  \nImplementation 181  \n6.2 Deploy System 183  \n6.3 Transition to Performing Organization 187  \nMeasurements of Success 188  \nPhase Risks/Ways to Avoid Pitfalls 189  \nPhase Risks/Ways to Avoid Pitfalls 121  \nSection III Introduction  \nThere are currently many different methodologies employed for system development projects within New York State agencies. Many methodologies are driven by the application development tools, by the software architecture within which the application will operate, or by the “build versus buy” decision. There are standard phases and processes, however, that all system development projects should follow, regardless of environment and tools. This section describes the standard phases and major processes of the New York State System Development Lifecycle (SDLC), using a common language and in sufficient detail to enable a Project Manager to plan and manage a system development project.  \nSystem Development Lifecycle Overview  \nThe material in this section is organized according to a generic system development lifecycle. While no two development efforts are exactly alike, all projects should progress through the same six phases:  \n1. System Initiation – in which the Business Case and Proposed Solution developed during Project Origination are re-examined to ensure that they are still appropriately defined and address an existing organizational need. This validation effort provides the Project Team with the basis fora detailed schedule defining the steps needed to obtain a thorough understanding of the business requirements and an initial view of staffing needs. In addition, a high level schedule is developed for subsequent system development lifecycle phases.  \n2. System Requirements Analysis – in which the needs of the business are captured in as much detail as possible. The Project Manager leads the Project Team in working with the Customers to define what it is that the new system must do. By obtaining a detailed and comprehensive understanding of the business requirements, the Project Team can develop the Functional Specification that will drive the system design.  \n3. System Design – which builds upon the work performed during System Requirements Analysis, and results in a translation of the functional requirements into a complete technical solution. This solution dictates the","cbCaieD0hsSyyCVO","https://ap.wps.com/l/cbCaieD0hsSyyCVO","pdf",3279102,192,"English","# Section III Introduction\n## System Development Lifecycle Overview\n## System Initiation\n## System Requirements Analysis\n## System Design\n## System Construction\n## System Acceptance\n## System Implementation","[{\"question\":\"What is the purpose of the SDLC Section III introduction for New York State agencies?\",\"answer\":\"It standardizes how system development projects proceed across different environments by describing the six phases and major processes in sufficient detail for project planning and management.\"},{\"question\":\"What happens during System Initiation in this lifecycle?\",\"answer\":\"The business case and proposed solution are re-examined to confirm they still address an organizational need, and this validation supports detailed scheduling and staffing estimates.\"},{\"question\":\"How does the project focus change from System Acceptance to System Implementation?\",\"answer\":\"System Acceptance shifts validation toward users who will operate the system, including checks for data conversion and deployment readiness, while System Implementation covers deployment activities such as training, installation, and transition of ownership.\"}]","System Development Lifecycle - Section III - Overview | PDF",1789206979,67]