Programming and software development · ENGLISH
Service page for projects serving Curitiba. Define API contracts, permissions and error responses before exposing data. For Curitiba, longer pages can organise requirements, deliverables and decisions by stage.
01 · CONTEXT
For Curitiba, longer pages can organise requirements, deliverables and decisions by stage.
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 Curitiba, confirm with the people involved: For Curitiba, longer pages can organise requirements, deliverables and decisions by stage.
An API contract covering schemas, authentication, permissions and error responses.
Verify responses and role permissions, along with limits and failure cases.
03 · METHOD
Implementation, architecture and maintenance
04 · ANSWERS
Define API contracts, permissions and error responses before exposing data. An API contract covering schemas, authentication, permissions and error responses.
Share expected behaviour, users, rules, existing technology and constraints. Do not send passwords; arrange access only if needed.
Verify responses and role permissions, along with limits and failure cases.