Requirements planning
Software requirements form
Describe today’s workflow and the change you need, so the next requirements discussion can be specific.
For business owners, project managers and users requesting software changes.
The original file is in Chinese. If preview is unavailable, download it and open it in a compatible reader.
Read the usage guideUsage guide
From business needs to technical review
Record the project context
Enter the project, organization, current software version and contact details. Record the form date separately from the requested completion date.
- Have ready
- The modules and software version in use, plus the person who will confirm requirements.
Describe each requested change
Record the source, urgency, affected module and change type. In the change description, explain current and target behavior, who uses it, when and the expected result.
- Be specific
- Tie each requirement to a usage scenario. Add a relevant screen or workflow description.
Arrange technical review
Developers complete the lower section: technical assessment, assigned staff, planned days and the effects on schedule, cost, quality and live operation.
- Agree together
- Target timing, implementation scope and the work plan after review.
Discuss the scope of your changes
Save a completed copy, then use the project inquiry to describe the context and requested changes. Agree how to share the full document once in contact. Keep passwords and keys out of the form.