Blueprint template — copy it into your project
See it filled first: the blueprint example (also as a PDF), an invented chain of phone shops with every section filled in.
Copy this file into your project, change this heading to Blueprint: and the project's name, and fill it in: each section's line in italics says what goes there. The project blueprint says how to fill each section. To fill it on paper instead, print the blueprint form (PDF).
| Field | Your answer |
|---|---|
| Prepared by (one of: iVendNext Partner · Licensed customer · CitiXsys Consulting Team) | |
| Date | |
| Version | |
| Kit version (the version of the kit you worked from) | |
| Sandbox / staging site (the site you tried it on) |
(a) The project in two lines
What the customer wants, and what you will deliver. Two lines, no more.
(b) Fit-gap
One row per need, in the customer's words: its card, the card's verdict and door, and every limit.
| # | Need (customer's words) | Card | Status | Door | Limits and note |
|---|---|---|---|---|---|
| 1 | |||||
| 2 | |||||
| 3 |
(c) Scale profile
Real figures, or a guess marked as one; then work out the peak and check it against the known limits.
| Measure | Value | Basis (counted / estimated) |
|---|---|---|
| Stores | ||
| Tills per store, by kind (counter · phone · tablet · Handheld) | ||
| Active products (and variants) | ||
| Customers on file | ||
| Sales per day per till — an average day | ||
| Sales per day per till — the busiest day | ||
| Lines per sale (average) | ||
| Peak-hour share (share of a day's sales in the busiest hour) | ||
| Offline hours expected per till per week; the longest single outage | ||
| Integration event volume per day; at the peak hour |
(d) Integration map
One row per outside system and direction: its door, what moves, how much, and what happens when it is down.
| System | Direction | Door | What moves | Volume (per day / peak hour) | Who owns the far side | Our connector or your app | Identity map kept by | If the far side is down |
|---|---|---|---|---|---|---|---|---|
(e) What this blueprint switches on
Each module on or off, and the row or figure that decides it.
| Module | On / off | Because (row or figure) |
|---|---|---|
| Joint extension-point lane | ||
| Scale proof | ||
| Release gate in the customer's CI | ||
| Dedicated bench (CitiXsys Consulting Team only) |
(f) Risks and open questions
What you do not know yet, what would settle it, and who can answer.
| # | Risk or question | Touches | What would settle it | Who can answer |
|---|---|---|---|---|
| 1 | ||||
| 2 | ||||
| 3 |