Design, testing and go-live
In design we turn requirements into specifications the team can build from: the database design (try it in the ERD Studio), screen wireframes, and the architecture: a mobile app, a server, a database and a payment-gateway integration.
Open the ERD Studio and design the café database →| Unit testing | Each part on its own, such as the VAT function. |
| Integration testing | Parts together, such as the app with the payment gateway. |
| System testing | The whole system against the requirements, including performance and security. |
| Acceptance testing (UAT) | Real users try it and sign off. |
Then we choose a conversion strategy from the old system to the new one:
| Strategy | How | Risk and cost |
|---|---|---|
| Direct | Switch off the old, switch on the new in one day | Cheapest, riskiest |
| Parallel | Run both systems for a while | Safest, most expensive |
| Pilot | Launch in one branch or department first | Contained risk |
| Phased | Release the system module by module | Moderate, takes longer |
Watch outFor the café: run a pilot at the computer-college branch for two weeks, fix the issues, then roll out to the other branches.
Put it all together: write a requirements document (SRS) for your project →