Technical requirements
For a new application, describe the task and the records it must read or change. For existing software, include the behavior to repair and what is known about its repository and deployment setup. Access to sensitive systems is arranged separately.
Scope and review criteria
The proposal sets the boundary of the assignment: functions to develop, data to move, connections to build and supporting materials to supply. It records dependencies, responsibilities and exclusions. The review criteria, commercial terms and any maintenance coverage are agreed in writing.
Implementation and verification
An application review exercises screens, permissions and changes to records. An integration review checks field mappings and transfer behavior, including rejected or repeated requests. A migration compares the destination with the source and accounts for records held for correction.
A reported problem needs the affected version, input and steps that reproduce it. We use that record to check the correction. Additional functionality is considered separately from a defect against the agreed requirements.
Source code and documentation
The exact handoff depends on the service. It can include:
- Application, connector or script source in the agreed repository.
- Runtime, installation, build and deployment instructions.
- Configuration names and ownership of hosting or external accounts.
- Data models, field mappings and migration scripts.
- Relevant checks and verification results.
- Logs, recovery procedures and a record of remaining limitations.
Store secret values in the appropriate account or secret store. Handoff documents identify configuration names and access responsibilities. Ongoing maintenance and response arrangements require their own defined coverage.