Clay Williams
ABSTRACT
Today, large enterprises create a significant body of commercially available software. As a result, the key stakeholders include not only those typically responsible for software development, but also stakeholders not typically involved in software engineering discussions. Current software development approaches ignore or poorly manage these enterprise level concerns. This hampers the ability to create connections among the stakeholders responsible for enterprise wide issues, the development team, and the artifacts with which they are concerned. In this paper we identify a set of propositions for coordination in enterprise software engineering environments and describe a preliminary framework to support such interactions.
- S. Bosworth. Open services for lifecycle collaboration. http://open-services.net/ September 2009.Google Scholar
- E. Carmel. Global Software Teams: Collaborating Across Borders and Time Zones. Prentice Hall, Upper Saddle River, NJ, 1999. Google ScholarDigital Library
- M. Cataldo, P. A. Wagstrom, J. D. Herbsleb, and K. M. Carley. Identification of coordination requirements: implications for the design of collaboration and awareness tools. In Proceedings of the 2006 20th Anniversary Conference on Computer Supported Cooperative Work, pages 353--362. ACM, November 2006. Google ScholarDigital Library
- L. Chung and J. do Prado Leite. On non-functional requirements in software engineering. In Conceptual Modeling: Foundations and Applications, pages 363--379. Springer, Berlin, 2009. Google Scholar
- E. Glynn, B. Fitzgerald, and C. Exton. Commercial adoption of open source software: an empirical study. In Proceedings of the 2005 International Symposium on Empirical Software Engineering. November 2005.Google ScholarCross Ref
- J. D. Herbsleb. Global software engineering: the future of socio-technical coordination. In 2007 Future of Software Engineering, pages 188--198. IEEE Computer Society, May 2007. Google ScholarDigital Library
- J. D. Herbsleb, A. Mockus, T. A. Finholt, and R. E. Grinter. An empirical study of global software development: distance and speed. In Proceedings of the 23rd International Conference on Software Engineering, pages 81--90. IEEE Computer Society, 2001. Google ScholarDigital Library
- R. Kraut and L. Streeter. Coordination in software development. Comm. ACM, 38(3):69--81, March 1995. Google ScholarDigital Library
- D. Leffingwell and D. Widrig. Managing Software Requirements: A Unified Approach. Addison-Wesley Longman Publishing Co., Boston, 2000. Google ScholarDigital Library
- B. Nuseibeh and S. Easterbrook. Requirements engineering: a roadmap. In 2000 Future of Software Engineering, pages 35--46. ACM, June 2000. Google ScholarDigital Library
- H. Sharp, A. Finkelstein, and G. Galal. Stakeholder identification in the requirements engineering process. In Proceedings of the 10th International Workshop on Database & Expert Systems Applications, pages 387--391. IEEE Computer Society, 1999. Google ScholarDigital Library
- M. E. Sosa, S. D. Eppinger, M. Pich, D. G. McKendrick, and S. K. Stout. Factors that influence technical communication in distributed product development: an empirical study in the telecommunications industry. IEEE Trans. Engr. Mgmt., 49(1):45--58, February 2002.Google ScholarCross Ref
Index Terms
- Supporting enterprise stakeholders in software projects
Recommendations
Coordination of Software Development Teams across Organizational Boundary -- An Exploratory Study
ICGSE '13: Proceedings of the 2013 IEEE 8th International Conference on Global Software EngineeringCoordinating teams across geographical, temporal and cultural boundaries has been identified as a critical task to achieve the success of global software projects. Organizational boundary is another dimension of global distribution, which is a less ...
Business Process Design Meets Business Practices Through Enterprise Patterns: A Case Study
Every day companies deal with internal problems in order to manage human resources during the execution of business processes. The ability to quickly identify and rapidly apply effective business practices to recurring problems becomes crucial in order ...
Collaborative Process Management for the Networked Enterprise: A Case Study
WAINA '12: Proceedings of the 2012 26th International Conference on Advanced Information Networking and Applications WorkshopsThe ability to quickly identify and rapidly apply effective business practices makes the difference between companies that manage to remain competitive even in crisis situations and companies that suffer from short-term market changes. To seize the ...
Comments