Programming and software development · ENGLISH
Service page for projects serving Medellin. Define how data, users and services relate before building the system. For Medellin, catalogue and enquiry journeys should keep their context from search to detail and contact.
01 · CONTEXT
For Medellin, catalogue and enquiry journeys should keep their context from search to detail and contact.
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 Medellin, confirm with the people involved: For Medellin, catalogue and enquiry journeys should keep their context from search to detail and contact.
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.