How do you show your clients / employers that you understand their requirements?
What do you recommend to use? Examples of using charts? Flowchart? Stream data schema? Decision trees?
I do not really ask for a very detailed answer. Just something simple to help me communicate with the person who wrote the requirements and see if you are both on the same page.
I usually collect a PowerPoint deck quite early in the project, giving a high-level overview of the project, as well as some architectural diagrams (the simpler the better) and layouts / wireframes on the screen. Then I have a “kick-off” meeting to review the requirements, and also discuss the business problem and the proposed solution.
I simply explain the requirements in my language, providing my assumptions and adding restrictions.
The requirement may be "The button turns green when pressed."
I would ask: "Okay, so when the user clicks on the button, the background color of the button turns green, but the text remains the same color?"
Basically the motivation of the claimant is to explain how THEY suggest his work.
. , , - , PowerPoint, , . , , " ", " ?". , . -, , , .
. "i" "t". - , POC. , .
UML , , . , , ", ", .
, , , . - , .
, , - , , , , , . , , , , .
, , , , .
Edit- - PM, . PM , . POC - , , , .
, 20 . , .
( OHP) - .
-, , (.. ), . , - , , - .
, .
, , . honnest .
, , , - .
, Engineering Engineering (MERE), Siemens , ( , ), .
, , . .
, , " ".
, , , , , .