Programming and software development · ENGLISH
Service page for projects serving Bogota. Define how data, users and services relate before building the system. 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 diagram of services, data entities and exchanges between components.
Check contracts, failure responses and data consistency across services.
03 · METHOD
Implementation, architecture and maintenance
04 · ANSWERS
Define how data, users and services relate before building the system. A diagram of services, data entities and exchanges between components.
Share expected behaviour, users, rules, existing technology and constraints. Do not send passwords; arrange access only if needed.
Check contracts, failure responses and data consistency across services.