The work
We build web applications for work that needs a shared record: entering a request, checking its details, approving a change and finding the result later. Screens can include searchable lists, forms, status views and exports. The application reads or updates other systems where their interfaces allow it.
The data model and permissions are part of that work. We define which values are required, who can change them and which actions need approval. Server-side checks enforce those rules when a request reaches the application, including requests made outside its normal screens.
For a first brief, describe one task from entry to completion and identify the records involved. That is enough to begin discussing the application; the detailed requirements can be developed as part of the assignment.
Technical considerations
- Authentication and access rules depend on who will use the application and which systems already manage their accounts.
- Imports, exports and external connections need defined formats, record identifiers and rules for rejected data.