Thursday, 22 August 2013

First step in analysing a proposed system [duplicate]

First step in analysing a proposed system [duplicate]

div class=question-status question-originals-of-duplicate pThis question
already has an answer here:/p ul li a
href=/questions/171295/how-to-manage-and-estimate-unstructured-requirements-received-from-customers
dir=ltrHow to manage and estimate unstructured requirements received from
customers/a span class=question-originals-answer-count 2 answers /span /li
/ul /div pA client asked us to automate his offline paper-based processes.
He sent us a copy of the physical forms that he uses./p pOur team met and
discussed how the navigation should be, what major components would exist
in the UI. That's it./p pProblem is, we don't have actual written
requirements. With a lack of an actual business/system analyst in our
company, what are the steps that we should take to reach the point where
we are ready to start developing the system?/p

No comments:

Post a Comment