Importance of Communication During the Analysis Phase of Software Deve

Question: Create an post in which you analyse the importance of communication during the analysis phase of software development. Answer: The entire aspect of any project is characterized and driven mainly by the course of its communication and its importance during various activities. During this phase various stake holders should be able to communicate all their requirements to their analysts, external stake holders and most of the times to their internal stake holders as well who take a lot of decisions related to the finalization of their projects. In this article we would discuss about the importance of communication during the analysis phase of software development. Most often people are associated with various official duties which is dependent on the career paths which they choose and most often the organizations are into various international projects related to software development in which various roles are generally a part of like analysts, software engineers, software developers, program managers, project managers and support employees who are involved in training and other activities (Robinson, K. Schmidt (Eds.) nd). There are various types of communication barriers in the present scenario which cause a major delay and failure in the software projects (Curtis et al 1988). This has been proved in all the different types of socio technical settings environment where software development is a major part of the projects. The organizational domains where in the software development is made an essential part are generally very intricate where it is difficult for the employees of the domain organization and the software organization to understand the requirements completely. Software specification document like the RFP might be so complicated that it could be difficult for the software development team to understand the requirements most of the times as well (Gotel, O. and Finkelstein, A 1994). One way communication channels and in efficiency in terms of team coordination could be the other reason for maintaining the communication effectively in the process (Curtis et al 1988). An implicit over the wall model exists in almost all the software development projects where the specifications and their related communication is thrown over the wall and the other teams would receive it and are generally waiting for it without any proper communication passed between each other. There are 2 specific solutions to tackle this issue like the first one is the emphasis of the development of notations and effective electronic repositories. In this model the communication is noted down and is documented and it can be shared as it is saved in the repository. In the second model the importance of contact between the development team and the other stake holders has given rise to practices like participation activities and ethnographic methods which have a dependency on the teams however might solve the issues atleast to some extent (Mintzberg, H 1979). References Mintzberg, H. (1979). The Structuring of organisations. Prentice-Hall. Robinson, M. and Bannon, L. (1991). Questioning Representations. In L. Bannon, M. Robinson, K. Schmidt (Eds.), Proceedings of the Second European Conference on ComputerSupported Co-operative Work (ECSCW-91), 25-27 September, Amsterdam, The Netherlands. pp. 219-233. Curtis, B. (1990). Empirical Studies of the Software Design Process., In Diaper et. al. (Eds), Human-Computer Interaction - INTERACT '90, Elsevier Science Publishers, North-Holland. pp.35-40. Gotel, O. and Finkelstein, A. (1994). An Analysis of the Requirements Traceability Problem., Proceedings of the First IEEE International Conference on Requirements Engineering, Colorado springs, 18-22 April. pp.94-101.