Abstract
At the heart of software requirements elicitation lies the communication between customer and developer. There are several valuable components of communication such as medium, sender, receiver, and messages, which relates to the input and output from both parties. Most of these messages are delivered through incompletely, inconsistently or inaccurately defined communication medium. This study has been done to look into the communication content of the current communication practices between developer and customer in Malaysia. The results of this study revealed some important notes on the practices of communication content during software requirements elicitation process in Malaysia.
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.
