Abstract
In the software system development, requirement engineering plays a great role because system successfulness depends on it. If the requirements are clear and unambiguous in every aspect then the system will be developed error free. A number of clients that are not educated and illiterate, then in this scenario, the given requirements are not clear and full of ambiguous. In this paper, we proposed a method to resolve this problem in the shape of break the requirements, filter it (separate the necessary and un-necessary requirements), break into little bits, numbering them and prioritize them, after it is documented, the requirement that is very helpful for current and future changing in software system and finally shift to the development team for develop the project. We will apply this proposed method on case study as experimental to find out the definite and relevant results.
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 callMore From: Lahore Garrison University Research Journal of Computer Science and Information Technology
Disclaimer: 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.
