Abstract
A great variety of methods, techniques, or approaches have been proposed to systematize and facilitate activities of software systems’ requirements elicitation and specification. Each of them has its specific purposes and contributes in its own way for obtaining a good understanding of software requirements. However, in practice, using an unique method is not enough to cover all tasks required during software-intensive system’s requirement engineering. This work does not aim to propose a new or a hybrid method, since each software project has its own characteristics, and methods must be selected and sometimes adapted to fit in each project specificities. This work reports the authors’ experience on how different methods were used together in a coordinated way for requirements specification. Also, possible benefits and drawbacks found by combining methods are also presented.
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
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.