# Custom software project brief
Source guide: https://yenra.com/custom-software-development/
Use one copy per proposed project. Fill evidence and an owner beside each answer.
1. User and task: Who needs to do what, and how is it done today?
2. Baseline: Which observed delay/error are we addressing? Units and measurement period:
3. Small first release: One complete workflow and the explicitly deferred workflows:
4. Alternatives: Existing product, configuration/integration, custom build; evidence from a trial:
5. Data: Authoritative system, identifiers, migration volume, retention and export format:
6. Roles: Who can create, approve, view, correct and export each record?
7. Acceptance: Given [starting state], when [action], then [observable result].
8. Failure cases: Duplicate submission, unavailable dependency, rejected input, interrupted save:
9. Constraints: User volume, response time target, devices, accessibility, hosting and recovery:
10. Delivery: Small working increment, reviewer, test dataset, demonstration date:
11. Ownership: Repository, credentials, documentation, licensing, service and update responsibility:
12. Exit: Export/recovery demonstration and operational handover evidence:
Decision: proceed / revise scope / choose existing product. Owner and review date:

Fictional example: A repair desk keeps one traceable record from intake through
collection. On an intake with serial DEMO-104 already open, show the existing
repair. Let the worker cancel or create a separate repair with a recorded reason,
according to the agreed policy. Record worker, time and resulting repair ID.
Test missing serials, corrections and unavailable services separately. Set actual
performance and recovery targets using observed working conditions.