How to name the section of the TK with a description of what we can implement from the requirements?

Question

Preparation of terms of reference

Developed software. Gave it to the client. Gathered new user requirements from a domain expert. They are in the form of a document. Statement for programmers and for system analysts. How to name the sections:
1. Which describes what we can implement from the requirements already now
2 which describes what we can implement, but will require a lot of improvements

Answer 1

In general, this can be conditionally divided into stages.
Versions are already a matter of delivery, although iteratively and already depends on the method of shipment, but the conditions for "we can not" do this already in stages. They have relationships. Just right for you, the first stage is what you can do and understandably, the second stage is what needs to be discussed, analyzed, agreed upon.

Answer 2

Example: From 2 requirements: a) The user wants a red button. b) The user wants a sales report....
a) can be implemented now, and b) needs more work. What is the most important of this if you are making any kind of CPM system? Is it really a red button? :)
I agree with the above colleague. If the requirements are defined, their volumes are defined, you now need to determine their priority depending on the tasks and goals.