After the requirement gathering and analysis and requirements defining is

completed by the Software System Analyst and Senior Team Members with
inputs from the stakeholders, and has been properly documented. Then it
would be handed over to me, the Software Architect. Based solely on my
design/architectural decision, I would receive the requirements with which I
would work. I would meticulously design the project in accordance with the
Software Architectural Professional Ethics with highlights to the non-functional
requirements. After weeks of design and review (with the submission deadline
in mind) I would then proceed to hand it to the Programmers to code and
officially implement after which it would be tested, deployed, and afterwards
maintained, thus following the Software Development Life Cycle.
To ensure I get reliable feedback;
Once the product is deployed, I will make sure to keep in touch with the
customer. Pay visits regularly to wherever the product is being used to enable
me use it first-hand. In that vein, I can be rest assured I did an excellent work.
Else, I would chip in the Software Reliability Metrics which are MTBF, MTTF
and MTTR meaning Mean Time Before Failure, Mean Time To Failure and Mean
Time To Repair respectively.
Secondly, I will always attempt to talk to as many potential customers. I would
also never take the marketing departments word on customer requirements,
rather I would contact the System Analysts directly.
In Summary, I will talk to people, listen, get my own hands dirty in
implementation and bug-fixing not just constraining myself to architectural
design but assist the coders, only then would I be able to change what needs to
be changed. That’s how you get reliable feedback!