Editing
Web design glossary
(section)
Jump to navigation
Jump to search
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
== 產品規格文件 / 不同階段設計文件 == RFP (Request For Proposal) [http://wiki.mbalib.com/zh-tw/%E9%9C%80%E6%B1%82%E5%BB%BA%E8%AE%AE%E4%B9%A6 需求建議書] / 企劃書,由發案單位提供。 {{exclaim}} 功能規格的文字,需要可以準確作為驗收或交付的項目。例如將模糊的大功能,展開為子項功能。相關頁面: [[Writing suggestion of request for proposal | 避免這樣寫 RFP (Request For Proposal) 需求建議書]] * 軟體需求說明 ([https://en.wikipedia.org/wiki/Software_requirements_specification Software requirements specification], SRS) [http://templates.openoffice.org/zh-hant/node/5693 範本],由發案單位提供。產品規格文件(BRD, MRD, PRD)撰寫<ref>[http://www.coolseo.org/operation/pm-mrd-prd-brd 產品經理(PM)一秒理解MRD、PRD、BRD | Cool SEO]</ref>: ** [https://en.wikipedia.org/wiki/Business_requirements Business Requirement Document] (BRD) [繁體] 商業需求文件; [簡體] 商业需求描述 ** [https://en.wikipedia.org/wiki/Market_requirements_document Market Requirement Document] (MRD) [繁體] 市場需求文件; [簡體] 市场需求文档 ** [https://en.wikipedia.org/wiki/Product_requirements_document Product Requirements Document] (PRD) [繁體] 產品需求文件、產品需求文稿; [簡體] [http://www.woshipm.com/pmd/561615.html 产品需求文档]、产品需求档案 ** Design Requirements Document (DRD) [繁體] 互動設計文件、互動設計說明文件; [簡體] 交互设计文档、交互设计说明文档、交互设计规范性文档 * 服務建議書或服務企劃書(service suggestions) [http://lmgtfy.com/?q=%E6%9C%8D%E5%8B%99%E5%BB%BA%E8%AD%B0%E6%9B%B8%20%E7%AF%84%E6%9C%AC 範本]。由接案單位撰寫。 [[Functional map | 功能地圖, Functional map]] * 將使用者需求,轉換成功能地圖 草稿、手繪 (sketching)、產品設計手繪 (product design sketching) * [https://en.wikipedia.org/wiki/Paper_prototyping Paper prototyping - Wikipedia, the free encyclopedia] Wireframe [繁體] 線框圖、框線稿、線稿; [簡體] 线框图。「線稿又稱頁面示意圖 (page schematic) 或螢幕藍圖 (screen blueprint)。以網站線稿為例,視覺化方式呈現網站的『骨骼圖』。線稿目的是說明如何配置網站元件,以符合特定目的。」(資料來源: [https://en.wikipedia.org/wiki/Website_wireframe Wikipedia]) * 功能地圖 (Functional Map): [http://blog.akanelee.me/posts/168560-functional-map/ 初學者的 Functional Map · 嫁給 RD 的 UI Designer] * 使用者流程圖 (User Flow Diagram)、[https://zh.wikipedia.org/zh-tw/%E6%B5%81%E7%A8%8B%E5%9B%BE 流程圖] (Flow chart, Logicflow): ** [https://free.com.tw/flow-chart-symbols-and-usage/ 流程圖(Flow Chart)常用符號說明] ** [http://blog.akanelee.me/posts/276159-flow-chart-and-ui-flow/ Flow Chart 和 UI Flow · 嫁給 RD 的 UI Designer] * 操作流程、頁面流程 (UI flow): [http://blog.akanelee.me/posts/168863-the-beginner-ui-flow/ 初學者的 UI Flow · 嫁給 RD 的 UI Designer] * [https://zh.wikipedia.org/wiki/%E7%B6%B2%E7%AB%99%E5%9C%B0%E5%9C%96 網站地圖] ([https://en.wikipedia.org/wiki/Site_map Site map]) * [[Information Architecture | 資訊架構]][https://zh.wikipedia.org/wiki/%E8%B3%87%E8%A8%8A%E6%9E%B6%E6%A7%8B] ([https://en.wikipedia.org/wiki/Information_architecture Information architecture]) Mockup [繁體] 視覺稿; [簡體] 视觉稿 * [https://en.wikipedia.org/wiki/Mockup Mockup - Wikipedia] Prototype [繁體]雛形、原型; [簡體] 原型 * fidelity: [繁體] 保真度、逼真度<ref>[http://terms.naer.edu.tw/detail/473018/ fidelity - 保真(度),逼真(度)]</ref>; [簡體] 保真度<ref>[http://www.baike.com/wiki/%E4%BF%9D%E7%9C%9F%E5%BA%A6 保真度_互动百科]</ref>。接近實際產品的畫面或互動方式的程度。 * High-fidelity prototype [繁體] 高逼真原型、高完成度原型; [簡體] 高保真原型。相反詞: Low-fidelity prototype * Low-fidelity prototype [繁體] 低逼真原型、低完成度原型; [簡體] 低保真原型。相反詞: High-fidelity prototype * 延伸閱讀: wesley (2016). [https://heywesley.wordpress.com/2016/08/25/prototyping-easy-in-easy-out/ 介面設計Prototyping 淺入淺出 – DESIGNING BY LEARNING] {{access | date = 2016-08-25}} * 原型工具比較: ** [http://uxtools.co/tools/#/ Uxtools.co] ** [https://www.cooper.com/prototyping-tools Prototyping Tools | Cooper] ** [http://prototypingtools.design/ Pikatool: Compare Prototyping Tools] 比較 speed, fidelity, user testing, wireframing, collaboration 設計系統 (Design System)、設計規範、視覺方針 ([https://en.wikipedia.org/wiki/Style_guide Style guide], Style guideline)、介面模式 (UI Pattern) ex: * 範例: [https://playbook.cio.gov/designstandards/ U.S. Web Design Standards] 其他範例請見 [[I_need_inspiration#Style_guideline_.26_UI_patterns | Style guideline & UI patterns]] * 教學: ** [http://www.woshipm.com/ucd/228968.html 设计规范如何写?这20个精选案例让你大开眼界 | 人人都是产品经理] {{access | date =2015-11-06}} ** HOWLIN YANG (2016). [https://www.facebook.com/notes/howlin-yang/%E5%A6%82%E4%BD%95%E8%A8%82%E5%AE%9A%E6%9C%89%E6%95%88%E7%9A%84design-guideline/1359293960750875?hc_ref=NEWSFEED 如何訂定有效的Design Guideline] {{access | date =2016-08-21}} ** Abby Chiu (2017). [https://medium.com/as-a-product-designer/design-system-practice-f460a60c5169 Design System Practice – As A Product Designer – Medium] {{access | date =2017-05-23}} "初次設計系統經驗分享" 使用者驗收測試(User Acceptance Test, UAT) * [[Software acceptance test plan]] (left blank intentionally)
Summary:
Please note that all contributions to LemonWiki共筆 are considered to be released under the Creative Commons Attribution-NonCommercial-ShareAlike (see
LemonWiki:Copyrights
for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource.
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)
Navigation menu
Personal tools
Not logged in
Talk
Contributions
Log in
Namespaces
Page
Discussion
English
Views
Read
Edit
View history
More
Search
Navigation
Main page
Current events
Recent changes
Random page
Help
Categories
Tools
What links here
Related changes
Special pages
Page information