Software Project Management Opinion Writing

Question: Write the opinion either supporting or opposing the author and add the references? Answer: According to the topic cited by Bourque and Fairley (2014), it is the prime responsibility of the software engineers to develop an acceptable equilibrium within the different aspects of the direct and the indirect stakeholders. This is fully acceptable. The main reason behind this acceptance is to become a software engineer it is very much necessary to have a very strong analytical skills. Every organization develops their internal or external operating software according to their own business needs. However, it has been seen that sometimes that only focusing on the business needs has created a major problem in the middle of the software development. The main reason behind this is that only focusing upon the business need overlooks the basic minimum needs of the other direct and indirect stakeholders (Hsieh and Pan, 2014). Therefore, while developing software it is the role of a software engineer to identify and analyze the key stake of the different stakeholders. According to the book, there are five key stakeholders remains within a software development cycle. Those five are: regulators, customers, users, market analysts and the software engineers (Bourque and Fairley, 2014). However, software engineers are those persons who actually develop the software. Therefore, while doing the software requirement analysis and developing the prototype of the software, it is sole responsibility of the software engineers to identify and analyze the stakeholders and their respective influences on the system (Saranya, 2014). According to Schmidt (2013) as the software engineers have to done the entire coding and the maintenance of the data processing, it is their responsibility to maintain the interests of the different stakeholders. However, it has been observed that over the times the requirements of the stakeholders especially the users and the customers frequently changes their likings and demands. Therefore, every time it is not possible for the software engineers to satisfy all the demands of every stakeholder. However, according to Shah and Patel (2014) it is very much required to reach the basic requirements of every stakeholder so that the entire data processing mechanism reaches the required standard. According to Patil and Ade (2014) the flow of data within a system is very much dependent upon multiple sources and majorly the members of the sources are the main stakeholders of the software. Moreover, every stakeholder maintains a basic format of standardization that is directed by the corresponding regulators. Therefore, while developing the basic requirements of any software the associated software engineers should identify and analyze the stake of the stakeholders. The main reason behind this logic is that through identifying and analyzing the minimum basic requirements of the related stakeholders the software (Dittrich, 2014). This will help the software engineers to develop a system that can satisfy the requirements of the stakeholders through reaching a acceptable point of standardization. References Bourque, P. and Fairley, R. (2014). SWEBOK V3.0- Guide to the Software Engineering Body of Knowledge. 3rd ed. IEEE Computer Scoiety. Dittrich, Y. (2014). Software engineering beyond the project Sustaining software ecosystems. Information and Software Technology, 56(11), pp.1436-1456. Hsieh, Y. and Pan, M. (2014). ESFM: An Essential Software Framework for Meshfree Methods. Advances in Engineering Software, 76, pp.133-147. Patil, S. and Ade, R. (2014). Software Requirement Engineering Risk Prediction Model. International Journal of Computer Applications, 102(2), pp.1-6. Saranya, R. (2014). Survey on Security Measures of Software Requirement Engineering. International Journal of Computer Applications, 90(17), pp.12-19. Schmidt, R. (2013). Software engineering. Waltham, MA: Morgan Kaufmann, an imprint of Elsevier. Shah, T. and V Patel, S. (2014). A Review of Requirement Engineering Issues and Challenges in Various Software Development Methods. International Journal of Computer Applications, 99(15), pp.36-45.