Programming and software development · ENGLISH
Service page for projects serving Santiago. Specify inputs, outcomes and expected errors for each application feature. For teams in Santiago, forms and multi-state journeys need clear, consistent messages.
01 · CONTEXT
For teams in Santiago, forms and multi-state journeys need clear, consistent messages.
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 Santiago, confirm with the people involved: For teams in Santiago, forms and multi-state journeys need clear, consistent messages.
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.