Register now or log in to join your professional community.
1- interviews with customers
2- UML for methodologies
Interviewing and discussion with the end users and the business stake holders.
Try user cases, get the user to write down each process and the data used and out put
Go through change proposals not only those accepted. Ones rejected though might have a good buissness reason might have been rejected due to being incompatible with or too costly on the legacy platform
Go back and find the buissness requirements for the existing system, incase it had been a forgotten requirement
Also check user logged errors/missing functions in your it support logs
Make sure you have captured all requirements at high level before going forward I like thediscipline from the togaf ADM model for this
Thank you friends for the updates.
Can you please share some link to read wireframes. Where should i start?
Regards
Agreeed. Though I did not require structured reviewing as it was a new product development. But, I have used Wireframes with a lot of success. In fact, I have made wireframes in a more informal format in PPT which give complete functional flow to the developer or any business stakeholder.
