Programming and software development · ENGLISH
Service page for projects serving Sao Paulo. Specify inputs, outcomes and expected errors for each application feature. For Sao Paulo, separating audiences, features and priorities helps review products with multiple goals.
01 · CONTEXT
For Sao Paulo, separating audiences, features and priorities helps review products with multiple goals.
02 · PRACTICAL BRIEF
Implementation, architecture and maintenance
Describe the problem, intended users, what exists today, technology constraints and one example of the expected result. Do not share passwords; arrange temporary access only when needed. Before finalising the brief for Sao Paulo, confirm with the people involved: For Sao Paulo, separating audiences, features and priorities helps review products with multiple goals.
A feature-by-feature specification of inputs, expected results, validation and errors.
Test valid, invalid and boundary inputs, and check that error messages help users.
03 · METHOD
Implementation, architecture and maintenance
04 · ANSWERS
Specify inputs, outcomes and expected errors for each application feature. A feature-by-feature specification of inputs, expected results, validation and errors.
Share expected behaviour, users, rules, existing technology and constraints. Do not send passwords; arrange access only if needed.
Test valid, invalid and boundary inputs, and check that error messages help users.