[{"data":1,"prerenderedAt":678},["ShallowReactive",2],{"site-schema":3,"article-zh-tw-ai-assisted-development-process":85},{"@context":4,"@graph":5},"https://schema.org",[6,68,75],{"@type":7,"@id":8,"name":9,"alternateName":10,"legalName":9,"foundingDate":15,"url":16,"logo":17,"founder":18,"contactPoint":20,"address":34,"location":40,"sameAs":60},"Organization","https://joinx.co/#organization","哲煜科技股份有限公司",[11,12,13,14],"JoinX","TWJOIN","哲煜科技","JoinX 哲煜科技","2016","https://joinx.co","https://joinx.co/images/logo-with-name.png",{"@id":19},"https://joinx.co/#person-jack-lee",[21],{"@type":22,"contactType":23,"url":24,"telephone":25,"email":26,"areaServed":27,"availableLanguage":30},"ContactPoint","customer service","https://joinx.co/contact-us","+886-2-8771-9095","service@joinx.co",[28,29],"TW","JP",[31,32,33],"zh-Hant","en","ja",{"@type":35,"streetAddress":36,"postalCode":37,"addressLocality":38,"addressRegion":39,"addressCountry":28},"PostalAddress","民生東路二段170號8樓","104","台北市中山區","台灣",[41,48,54],{"@type":42,"name":43,"address":44},"Place","JoinX 台中辦公室",{"@type":35,"streetAddress":45,"postalCode":46,"addressLocality":47,"addressRegion":39,"addressCountry":28},"台灣大道二段360號21樓C室","40453","台中市北區",{"@type":42,"name":49,"address":50},"JoinX 高雄辦公室",{"@type":35,"streetAddress":51,"postalCode":52,"addressLocality":53,"addressRegion":39,"addressCountry":28},"民族一路80號2樓之一(B4)","807","高雄市三民區",{"@type":42,"name":55,"address":56},"JoinX 東京辦公室",{"@type":35,"streetAddress":57,"postalCode":58,"addressLocality":59,"addressCountry":29},"東五反田5-22-37 Office Circle N 五反田 9樓","141-0022","東京都品川區",[61,62,63,64,65,66,67],"https://www.facebook.com/JoinX.TW","https://www.linkedin.com/company/%E5%93%B2%E7%85%9C%E7%A7%91%E6%8A%80","https://www.youtube.com/c/joinstuido哲煜科技","https://medium.com/twjoin","https://www.104.com.tw/company/1a2x6bjomb","https://podcasts.apple.com/tw/podcast/jack%E5%8F%AD%E5%8F%AD/id1859867414","https://open.spotify.com/show/236PYieEt3gQ30bfk7iE3J",{"@type":69,"@id":19,"name":70,"alternateName":71,"jobTitle":72,"worksFor":73,"url":74},"Person","李秉哲","Jack Lee","創辦人暨執行長",{"@id":8},"https://joinx.co/about",{"@type":76,"@id":77,"url":16,"name":78,"alternateName":79,"publisher":80,"inLanguage":81},"WebSite","https://joinx.co/#website","JoinX哲煜科技",[11,13,78],{"@id":8},[82,83,84],"zh-Hant-TW","en-US","ja-JP",{"id":86,"title":87,"author":88,"authorUrl":88,"body":89,"category":640,"cover":641,"ctaFirstContent":88,"ctaFirstLinkText":88,"ctaFirstLinkUrl":88,"ctaLastContent":642,"ctaLastLinkText1":643,"ctaLastLinkText2":88,"ctaLastLinkUrl1":604,"ctaLastLinkUrl2":88,"ctaMiddleContent":88,"ctaMiddleLinkText":88,"ctaMiddleLinkUrl":88,"ctaServiceName":644,"dateModified":645,"description":646,"extension":647,"faq":648,"hasCoverTitle":670,"hasCtaFirst":670,"hasCtaLast":670,"isDescriptionFirst":670,"locale":671,"meta":672,"navigation":670,"path":673,"seo":674,"stem":675,"time":645,"type":676,"__hash__":677},"content/zh-tw/article/ai-assisted-development-process.md","為什麼 AI 協作開發能省 30% 成本：JoinX 的實際流程公開",null,{"type":90,"value":91,"toc":607},"minimal",[92,99,102,107,110,113,120,142,145,149,152,276,279,283,286,408,411,414,418,423,426,429,433,436,439,443,446,449,453,456,459,462,465,468,471,474,477,481,484,502,505,509,513,516,520,523,527,530,534,537,541,544,548,551,555,558,562,565,569,577,581,584,588,591,594,599],[93,94,95],"p",{},[96,97,98],"strong",{},"AI 協作開發不是把需求丟給 AI，等它自動完成產品；而是由工程師主導，讓 AI 深度參與需求分析、規格整理、程式撰寫、測試與文件，再由人對架構、風險與交付結果負責。",[93,100,101],{},"這套方式讓 JoinX 能把大量重複、可驗證的工作交給 AI 加速，同時把工程師的時間留給真正影響產品成敗的判斷。依我們的流程成本模型，整體交付成本可降低約 30%；這不是刪掉測試、縮減人力或以低品質換速度，而是重新安排人與 AI 的分工。",[103,104,106],"h2",{"id":105},"ai-協作不是-vibe-coding","AI 協作不是 vibe coding",[93,108,109],{},"「vibe coding」常被用來形容：使用者用自然語言描述想法，讓 AI 一路產生程式，看到結果能跑就繼續往下疊。它很適合快速做概念、個人工具或驗證介面，但「可以執行」不等於「可以承擔正式營運」。",[93,111,112],{},"企業軟體還要回答更多問題：需求是否一致？資料權限是否正確？錯誤能否追蹤？第三方套件能否合法使用？部署失敗如何回復？三年後還能不能維護？",[93,114,115,116,119],{},"JoinX 所說的 ",[96,117,118],{},"AI 協作開發（AI-assisted development）"," 有三個必要條件：",[121,122,123,130,136],"ol",{},[124,125,126,129],"li",{},[96,127,128],{},"工程師是決策者。"," AI 可以提出方案、草擬程式與找出疑點，但不能自行核准需求、架構或上線。",[124,131,132,135],{},[96,133,134],{},"每個產出都可追溯。"," 需求、規格、程式碼、測試與部署記錄彼此連結，變更能找到理由與負責人。",[124,137,138,141],{},[96,139,140],{},"完成標準不因 AI 而降低。"," 程式仍要經過審查、測試、資安檢查與驗收；AI 產出和人工產出適用同一套品質門檻。",[93,143,144],{},"換句話說，AI 不是專案的無人駕駛，而是工程團隊的高效率副駕。",[103,146,148],{"id":147},"joinx-的七階段人機分工","JoinX 的七階段人機分工",[93,150,151],{},"AI 不只在「開發」階段補程式。真正的效益來自整條交付鏈都能共享清楚的上下文，同時在每個關鍵節點保留人工判斷。",[153,154,155,174],"table",{},[156,157,158],"thead",{},[159,160,161,165,168,171],"tr",{},[162,163,164],"th",{},"階段",[162,166,167],{},"工程團隊主導",[162,169,170],{},"AI 深度參與",[162,172,173],{},"人工把關點",[175,176,177,192,206,220,234,248,262],"tbody",{},[159,178,179,183,186,189],{},[180,181,182],"td",{},"1. 需求",[180,184,185],{},"訪談利害關係人、辨識商業目標、排定優先序",[180,187,188],{},"彙整訪談、找出矛盾與遺漏、產生待確認問題",[180,190,191],{},"決定真正要解決的問題與成功指標",[159,193,194,197,200,203],{},[180,195,196],{},"2. 規格",[180,198,199],{},"定義範圍、流程、資料與驗收條件",[180,201,202],{},"將需求轉成 user story、規格草稿、驗收案例與追蹤矩陣",[180,204,205],{},"確認規格符合現場流程，避免 AI 自行補假設",[159,207,208,211,214,217],{},[180,209,210],{},"3. 設計",[180,212,213],{},"決定資訊架構、系統架構、資料模型與整合邊界",[180,215,216],{},"比較方案、檢查例外情境、輔助產出圖表與文件",[180,218,219],{},"對效能、擴充性、成本與技術債做取捨",[159,221,222,225,228,231],{},[180,223,224],{},"4. 開發",[180,226,227],{},"拆解任務、選擇實作方式、審查與整合程式碼",[180,229,230],{},"產生樣板、重構重複程式、說明既有程式、補齊文件",[180,232,233],{},"確保正確性、可讀性、授權與架構一致性",[159,235,236,239,242,245],{},[180,237,238],{},"5. 測試",[180,240,241],{},"設計風險策略、決定覆蓋範圍、判讀失敗原因",[180,243,244],{},"依規格產生測試案例、邊界條件、測試資料與回歸清單",[180,246,247],{},"確認測到的是商業風險，而非只追求測試數量",[159,249,250,253,256,259],{},[180,251,252],{},"6. 部署",[180,254,255],{},"管理環境、權限、版本、變更窗口與回復方案",[180,257,258],{},"輔助檢查設定差異、整理發布說明、分析部署記錄",[180,260,261],{},"核准正式環境變更，確認監控與回復機制",[159,263,264,267,270,273],{},[180,265,266],{},"7. 維運",[180,268,269],{},"判斷事件優先級、根因、修復方案與後續責任",[180,271,272],{},"摘要日誌、比對異常、建立知識文件、提出排查路徑",[180,274,275],{},"決定修復範圍，避免局部修補造成新風險",[93,277,278],{},"這張表的重點不是「AI 做了多少」，而是每一階段都有明確的責任邊界：AI 擴大工程師能處理的資訊量，人仍對結果負責。",[103,280,282],{"id":281},"傳統開發與-ai-協作的成本怎麼變","傳統開發與 AI 協作的成本怎麼變",[93,284,285],{},"以下把一個專案的傳統交付工作量設為 100 個成本單位，比較 JoinX 導入 AI 協作後的工作分配。它是用來說明流程效益的成本模型，不是每個專案都適用的固定報價或折扣。",[153,287,288,305],{},[156,289,290],{},[159,291,292,295,299,302],{},[162,293,294],{},"工作項目",[162,296,298],{"align":297},"right","傳統開發",[162,300,301],{"align":297},"AI 協作",[162,303,304],{},"變化原因",[175,306,307,321,335,347,361,374,386],{},[159,308,309,312,315,318],{},[180,310,311],{},"需求分析與資訊整理",[180,313,314],{"align":297},"15",[180,316,317],{"align":297},"8",[180,319,320],{},"AI 協助整理訪談、比對矛盾並產生追問清單",[159,322,323,326,329,332],{},[180,324,325],{},"規格與文件",[180,327,328],{"align":297},"25",[180,330,331],{"align":297},"10",[180,333,334],{},"同一份結構化需求可延伸成規格、驗收條件與文件初稿",[159,336,337,340,342,344],{},[180,338,339],{},"架構與關鍵設計",[180,341,328],{"align":297},[180,343,328],{"align":297},[180,345,346],{},"商業限制、技術取捨與長期責任不能交給 AI 折抵",[159,348,349,352,355,358],{},[180,350,351],{},"程式開發",[180,353,354],{"align":297},"20",[180,356,357],{"align":297},"12",[180,359,360],{},"樣板、重複邏輯、重構與程式說明由 AI 加速",[159,362,363,366,368,371],{},[180,364,365],{},"測試與品質檢查",[180,367,331],{"align":297},[180,369,370],{"align":297},"5",[180,372,373],{},"AI 擴充測試案例，人員集中處理高風險情境與失敗判讀",[159,375,376,379,381,383],{},[180,377,378],{},"部署與維運準備",[180,380,370],{"align":297},[180,382,370],{"align":297},[180,384,385],{},"正式環境權限、回復與營運責任仍需完整投入",[159,387,388,393,398,403],{},[180,389,390],{},[96,391,392],{},"合計",[180,394,395],{"align":297},[96,396,397],{},"100",[180,399,400],{"align":297},[96,401,402],{},"65",[180,404,405],{},[96,406,407],{},"重複工時下降，關鍵判斷不打折",[93,409,410],{},"表中的流程工作量從 100 降到 65；換算成完整專案，還要納入溝通、治理、環境限制與不可預期風險，因此 JoinX 對外以「整體交付成本降低約 30%」作為較保守的說法。",[93,412,413],{},"這也解釋了為什麼 AI 協作不是單純讓工程師寫程式更快。最大幅度的改善往往出現在規格、文件、測試案例與資訊整理，而架構、部署與責任歸屬並沒有被刪除。",[103,415,417],{"id":416},"成本降低品質反而提升的三個原因","成本降低，品質反而提升的三個原因",[419,420,422],"h3",{"id":421},"_1-規格與實作更容易保持一致","1. 規格與實作更容易保持一致",[93,424,425],{},"傳統流程中，會議記錄、需求文件、任務、程式碼與測試可能分散在不同工具，資訊在交接時逐步失真。AI 可以在明確權限與上下文內協助比對它們：某個需求是否有驗收條件、某段實作是否偏離規格、某次變更是否需要更新文件。",[93,427,428],{},"工程師因此能更早發現不一致，而不是等到驗收才處理。",[419,430,432],{"id":431},"_2-邊界條件與回歸測試更完整","2. 邊界條件與回歸測試更完整",[93,434,435],{},"人擅長辨識最重要的商業風險，AI 則擅長從規則快速展開大量組合。兩者搭配後，測試不只覆蓋順利完成的主流程，也能更有系統地納入空值、權限不足、服務逾時、重複提交與資料格式錯誤等情境。",[93,437,438],{},"測試案例仍由工程師選擇與驗證，但建立清單與樣板的時間大幅減少。",[419,440,442],{"id":441},"_3-資深工程師能把時間用在高價值判斷","3. 資深工程師能把時間用在高價值判斷",[93,444,445],{},"如果資深工程師長時間忙著重寫相似文件、搬運欄位或整理日誌，就沒有足夠注意力處理架構、效能、資安與技術債。AI 承接可重複工作後，關鍵人力可以更早介入高風險決策，也有更多時間審查實作是否真的符合產品目標。",[93,447,448],{},"品質提升不是因為 AI 永遠正確，而是因為團隊能把有限的人類注意力放在最需要判斷的位置。",[103,450,452],{"id":451},"ai-不能取代的四件事","AI 不能取代的四件事",[419,454,455],{"id":455},"商業判斷",[93,457,458],{},"AI 可以分析訪談與列出選項，但不知道企業當下最重要的客戶、競爭策略與組織限制。要先做哪個功能、接受什麼風險、如何定義成功，仍是產品負責人與專案團隊的決定。",[419,460,461],{"id":461},"架構取捨",[93,463,464],{},"系統架構不是把流行技術拼在一起。資料一致性、流量、預算、團隊能力、舊系統限制與未來擴充都會互相牽動。AI 能提供候選方案，具備脈絡的架構師必須做出取捨並承擔後果。",[419,466,467],{"id":467},"資安與合規",[93,469,470],{},"AI 不會自動知道一份資料能否離開特定環境，也不能替企業判定法規、契約與稽核要求。資料分類、存取控制、個資處理、供應鏈風險與部署方式，都要由合格人員依專案情境確認。",[419,472,473],{"id":473},"最終責任",[93,475,476],{},"當系統發生錯誤，不能用「AI 產生的」作為免責理由。軟體公司必須說明誰審查、誰核准、如何回復，以及如何避免再次發生。JoinX 把 AI 視為工程工具，交付責任仍由團隊承擔。",[103,478,480],{"id":479},"導入-ai-協作前企業應確認什麼","導入 AI 協作前，企業應確認什麼",[93,482,483],{},"如果你正在比較開發夥伴，不必只問「有沒有使用 AI」。更有效的問題是：",[485,486,487,490,493,496,499],"ul",{},[124,488,489],{},"哪些資料可以提供給哪些工具？是否有資料分級、保留與刪除規則？",[124,491,492],{},"AI 產出的規格、程式與測試，由誰審查，留下哪些記錄？",[124,494,495],{},"如何檢查第三方套件授權、弱點與機密資訊外洩？",[124,497,498],{},"工具或模型不可用時，工程團隊能否接手並持續交付？",[124,500,501],{},"驗收依據是可操作的功能與品質指標，還是只展示一段 Demo？",[93,503,504],{},"AI 協作成熟度不在於使用多少模型，而在於流程是否能被說明、稽核與重現。",[103,506,508],{"id":507},"faqai-協作開發的-10-個常見問題","FAQ：AI 協作開發的 10 個常見問題",[419,510,512],{"id":511},"q1ai-協作開發真的能降低-30-成本嗎","Q1：AI 協作開發真的能降低 30% 成本嗎？",[93,514,515],{},"約 30% 是 JoinX 依實際協作流程建立的整體估算，不是所有專案的固定折扣。需求完整度、系統複雜度、法規要求與既有技術債都會影響最後效益；真正省下的是可重複、可驗證的工時，而不是必要的工程判斷。",[419,517,519],{"id":518},"q2把程式交給-ai資安風險會不會更高","Q2：把程式交給 AI，資安風險會不會更高？",[93,521,522],{},"風險取決於治理方式，而不是是否使用 AI。專案應先做資料分級、限制可輸入內容與工具權限，並保留程式碼審查、弱點掃描、依賴檢查與人工核准；機密、個資與正式環境憑證不得直接交給未核准的服務。",[419,524,526],{"id":525},"q3ai-產生的程式碼智慧財產權歸誰","Q3：AI 產生的程式碼，智慧財產權歸誰？",[93,528,529],{},"應以合約、採用工具條款與開源授權檢查共同管理。JoinX 的做法是由工程團隊承擔選用與整合責任，對產出進行審查與授權檢查；實際權利歸屬仍以個別專案合約為準。",[419,531,533],{"id":532},"q4ai-協作開發會使用哪些工具","Q4：AI 協作開發會使用哪些工具？",[93,535,536],{},"工具會依專案技術棧、資料敏感度與客戶政策選擇，可能涵蓋程式協作、文件整理、測試生成、程式碼分析與知識檢索。重點不是追逐單一模型，而是讓工具接入可稽核、可替換且有人負責的流程。",[419,538,540],{"id":539},"q5ai-協作開發能縮短多少交期","Q5：AI 協作開發能縮短多少交期？",[93,542,543],{},"無法只靠專案名稱給出固定天數。規格較清楚、重複性工作較多的專案通常受益較明顯；跨系統整合、法規驗證或大量利害關係人決策仍需足夠時間。JoinX 會在需求盤點後提供可驗收的里程碑。",[419,545,547],{"id":546},"q6專案資料會被-ai-拿去訓練嗎","Q6：專案資料會被 AI 拿去訓練嗎？",[93,549,550],{},"是否用於訓練取決於服務方案、供應商條款與專案設定，不能一概而論。導入前必須確認資料保留、訓練使用、部署區域與刪除機制；敏感資料應採遮罩、最小化輸入或使用符合要求的企業方案與部署方式。",[419,552,554],{"id":553},"q7小型專案也適合-ai-協作開發嗎","Q7：小型專案也適合 AI 協作開發嗎？",[93,556,557],{},"適合，但要先看工作內容。若需求明確且包含表單、串接、測試或文件等可標準化工作，即使範圍不大也能受益；如果核心仍在探索商業模式，應先投入需求驗證，而不是急著大量產碼。",[419,559,561],{"id":560},"q8舊系統可以導入-ai-協作開發嗎","Q8：舊系統可以導入 AI 協作開發嗎？",[93,563,564],{},"可以。AI 能協助理解既有程式、補文件、建立測試與規劃漸進式重構，但不能跳過系統盤點。缺少測試、依賴過時或規則只存在資深同仁腦中的系統，仍需要工程師先界定風險與改造邊界。",[419,566,568],{"id":567},"q9公司內部已經會使用-ai還需要找軟體公司嗎","Q9：公司內部已經會使用 AI，還需要找軟體公司嗎？",[93,570,571,572],{},"如果只是個人效率工具，內部使用 AI 可能已經足夠；若要交付正式產品，仍需有人負責需求、架構、整合、資安、測試、部署與維運。更完整的判斷方式可參考：",[573,574,576],"a",{"href":575},"/article/do-you-still-need-a-software-company-in-ai-era/","AI 時代還需要軟體公司嗎？",[419,578,580],{"id":579},"q10如何驗證廠商真的具備-ai-協作開發能力","Q10：如何驗證廠商真的具備 AI 協作開發能力？",[93,582,583],{},"請廠商展示可追溯的流程證據，而不只是一段生成程式的 Demo，包括需求如何轉成規格、AI 產出如何審查、測試與資安如何把關、問題由誰負責，以及工具失效時能否由工程團隊接手。",[103,585,587],{"id":586},"結語省下的是重複留下的是判斷","結語：省下的是重複，留下的是判斷",[93,589,590],{},"AI 協作開發的價值，不是把工程師從流程中移除，而是移除工程師每天反覆處理的低價值工作。需求整理、文件同步、樣板程式、測試展開與日誌摘要可以更快；商業判斷、架構、資安合規與最終責任則完整保留。",[93,592,593],{},"對 JoinX 而言，能降低約 30% 的成本只是結果。更重要的是，在相同預算與時間裡，團隊能把更多注意力放在產品真正要解決的問題上。",[93,595,596],{},[96,597,598],{},"省下的是重複，留下的是判斷。",[93,600,601,602,606],{},"如果你想評估自己的專案適合怎麼導入 AI 協作，歡迎 ",[573,603,605],{"href":604},"/contact-us","與 JoinX 對焦需求","。",{"title":608,"searchDepth":609,"depth":609,"links":610},"",2,[611,612,613,614,620,626,627,639],{"id":105,"depth":609,"text":106},{"id":147,"depth":609,"text":148},{"id":281,"depth":609,"text":282},{"id":416,"depth":609,"text":417,"children":615},[616,618,619],{"id":421,"depth":617,"text":422},3,{"id":431,"depth":617,"text":432},{"id":441,"depth":617,"text":442},{"id":451,"depth":609,"text":452,"children":621},[622,623,624,625],{"id":455,"depth":617,"text":455},{"id":461,"depth":617,"text":461},{"id":467,"depth":617,"text":467},{"id":473,"depth":617,"text":473},{"id":479,"depth":609,"text":480},{"id":507,"depth":609,"text":508,"children":628},[629,630,631,632,633,634,635,636,637,638],{"id":511,"depth":617,"text":512},{"id":518,"depth":617,"text":519},{"id":525,"depth":617,"text":526},{"id":532,"depth":617,"text":533},{"id":539,"depth":617,"text":540},{"id":546,"depth":617,"text":547},{"id":553,"depth":617,"text":554},{"id":560,"depth":617,"text":561},{"id":567,"depth":617,"text":568},{"id":579,"depth":617,"text":580},{"id":586,"depth":609,"text":587},"技術分享","/images/blog/ai-assisted-development-process.webp","想知道你的產品需求是否適合 AI 協作開發，以及哪些環節有機會縮短工時？\u003Cbr/>JoinX 可從需求、既有系統與資安條件出發，和你一起評估合適的交付方式。","預約需求對焦","AI 協作開發","2026/07/22","AI 協作開發是由工程師主導、AI 深度參與需求分析、程式撰寫、測試與文件的開發模式。JoinX 公開實際流程與各階段效益，說明為什麼交付成本能降低約 30%。","md",[649,651,653,655,657,659,661,663,665,668],{"question":650,"answer":515},"AI 協作開發真的能降低 30% 成本嗎？",{"question":652,"answer":522},"把程式交給 AI，資安風險會不會更高？",{"question":654,"answer":529},"AI 產生的程式碼，智慧財產權歸誰？",{"question":656,"answer":536},"AI 協作開發會使用哪些工具？",{"question":658,"answer":543},"AI 協作開發能縮短多少交期？",{"question":660,"answer":550},"專案資料會被 AI 拿去訓練嗎？",{"question":662,"answer":557},"小型專案也適合 AI 協作開發嗎？",{"question":664,"answer":564},"舊系統可以導入 AI 協作開發嗎？",{"question":666,"answer":667},"公司內部已經會使用 AI，還需要找軟體公司嗎？","如果只是個人效率工具，內部使用 AI 可能已經足夠；若要交付正式產品，仍需有人負責需求、架構、整合、資安、測試、部署與維運。可參考 JoinX 的「AI 時代還需要軟體公司嗎？」進一步判斷合作邊界。",{"question":669,"answer":583},"如何驗證廠商真的具備 AI 協作開發能力？",true,"zh-tw",{},"/zh-tw/article/ai-assisted-development-process",{"title":87,"description":646},"zh-tw/article/ai-assisted-development-process","blog","q28QLeBitK2QZKnZR_Bk8n1La__QBx8uD3IiSHiFQ8M",1784898721416]