成果範例
標準版方案範例
Technical specification: booking website for a yoga studio
1. Project goals
- Let clients see the timetable and book a class in under one minute, from a phone.
- Sell class passes and memberships online.
- Cut the time staff spend on bookings from about 10 hours a week to under 2.
Success measures (3 months after launch): 70% of bookings made online; no-shows below 10%.
2. Users
| Role | What they need |
|---|---|
| Visitor | See classes, prices and teachers; buy a first-class trial |
| Client | Book and cancel classes, see remaining passes, join a waitlist |
| Teacher | See their own classes and the list of booked clients |
| Admin | Manage timetable, prices, passes, teachers and refunds |
3. Pages and screens
- Home: next classes today, trial offer, studio address.
- Timetable: week view, filters by class type, level, teacher and room.
- Class page: description, teacher, length, places left, Book button.
- Prices: single class, 5- and 10-class passes, monthly membership.
- Teachers: list and individual profiles.
- Account: upcoming bookings, history, passes, payment methods.
- Admin panel: timetable editor, client list, sales report.
4. Key features
4.1 Booking
- A client can book if they have a valid pass or pay for a single class.
- Class capacity is set per room (Room A: 18, Room B: 10).
- When a class is full, the client can join a waitlist; if a place opens, the first person in line gets it and receives an email and text message.
4.2 Cancellation
- Free cancellation up to 12 hours before class; the pass credit returns.
- Later cancellation or a no-show uses up the credit.
4.3 Payments
- Card payments through a payment provider chosen by the studio.
- Passes expire: 5-class after 2 months, 10-class after 3 months.
4.4 Notifications
- Booking confirmation, reminder 3 hours before class, waitlist updates.
5. Non-functional requirements
- Mobile-first; pages load in under 2 seconds on 4G.
- Works in the two latest versions of major browsers.
- Personal data stored in line with local data protection law.
6. Open questions
| # | Question | Who decides |
|---|---|---|
| 1 | Do teachers mark attendance in the app, or does the front desk? | Studio owner |
| 2 | Is a 2-week trial pass needed in addition to a single trial class? | Studio owner |
| 3 | Should the timetable be embedded on the current website or replace it? | Owner + developer |
| 4 | Which payment provider and text-message service are preferred? | Owner |
Client: Lotus Lane Yoga, a studio with 2 rooms, 9 teachers and about 60 classes a week. Today bookings go through direct messages and a paper sign-up sheet. Standard package: specification up to 10 pages. Excerpt below.
客戶與所有細節皆為虛構。
關於此服務
像「結帳又壞了」這樣的訊息，會讓開發人員在開始修復前白白猜一個小時。請貼上您的粗略筆記、聊天訊息或測試人員的意見，我們會把每個問題整理成一份錯誤回報，包含簡短標題、環境、編號的重現步驟、預期與實際結果、嚴重程度，以及要附上的佐證。當您的筆記有缺漏，例如瀏覽器版本或確切的按鈕，回報中會標示為問題，而不是自行捏造。
包含內容
- 您將獲得整理完成的錯誤回報，每個問題一份，包含標題、環境、步驟、預期與實際結果、嚴重程度與優先順序，寫法方便貼進 Jira、Linear、GitHub Issues、Trello 或您選用的追蹤工具。
- 重現步驟開發人員可重複的編號動作
- 預期與實際應該發生什麼，以及實際發生什麼
- 嚴重程度與優先順序依您描述的影響程度建議
- 標註缺漏的細節寄出前需要回答的問題
- 合併重複項目關於同一個錯誤的多則筆記合併成一份回報
服務流程
- 1筆記您貼上所見內容與發生位置
- 2整理我們拆分、合併並排序問題
- 3回報由您將每份回報貼進追蹤工具
需要您提供的資料
您對每個問題的筆記、發生時您在做什麼、裝置、瀏覽器或應用程式版本、發生的頻率，以及您的團隊使用的追蹤工具欄位。
我們會詢問您：
- 錯誤發生在哪個產品與版本？
- 回報會放進哪個追蹤工具？
- 您的團隊使用自己的嚴重程度分級嗎？
- 誰會閱讀這些回報：內部開發人員還是外部團隊？
比較方案
付款保障
下單時付款，但只有在驗收成果後，款項才會撥付。
- 固定價格付款後，方案價格不會變動。
- 款項先行保留付款時，金額只會先保留，在您驗收後才會撥付給服務。
- 交付前檢查每份成果在交到您手上之前都會經過品質檢查，您也可以在驗收前於訂單頁面查看成果。
- 免費修改在需求說明範圍內，可依方案允許的次數提出修改。
- 3 天後自動驗收若您在交付後 3 天內未驗收也未提出修改，成果將自動驗收。若您在交付後於訂單聊天室留言，訂單會暫停自動驗收；我們回覆後，可能會重新起算 3 天，並會在聊天室中告知。
- 重新製作或全額退款若成果不符合您的需求說明且修改後仍未改善，或製作時間超過交付期限的兩倍，請在訂單聊天室留言：我們將重新製作，或全額退還款項。
常見問題
你們會在我的網站或應用程式上重現錯誤嗎？
不會。我們根據您的筆記與描述撰寫回報；在真實裝置上驗證步驟仍由您的團隊負責。
如果我的筆記非常凌亂怎麼辦？
這很正常。請照原樣貼上，我們會把問題分開；任何不清楚之處都會成為回報中的問題。
你們會建議修復方法嗎？
只有在筆記指向某個可能原因時，才會提出並標示為推測。找出真正的原因是開發人員的工作。
沒有找到您要的答案？