Abstract
Requirement Analysis pertains to extracting the requirement out of the heaps of information that the Business analyst has acquired from various stakeholders and Requirement communication or documentation is putting it down in a form that is easily understood by the stakeholders, development and testing teams. Starting from Requirements gathering, Requirements management, Solution assessment, validation, testing to the final go live. Once the solution is implemented and user acceptance is completed. The solution is evaluated for how it is being used, what is the positive effect of solution implementation, what is the negative impact of solution implementation. Solutions may be adapted, changed or partially used by the users , manual processes might still be followed, redundant information may still be captured manually, these need to be studied and analyzed to understand why this is happening and can this be resolved, and can the adoption of new solution be increased. This paper focuses on what precedes the implementation and what follows the implementation in the post implementation evaluation phase.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
