Programming and software development · ENGLISH
Service page for projects serving Bogota. Specify inputs, outcomes and expected errors for each application feature. In Bogota, products with several modules need clear distinctions between frequent tasks, permissions and pending states.
01 · CONTEXT
In Bogota, products with several modules need clear distinctions between frequent tasks, permissions and pending states.
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 Bogota, confirm with the people involved: In Bogota, products with several modules need clear distinctions between frequent tasks, permissions and pending states.
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.