A Weakly Constrained Approach to Software Change Coordination

ABSTRACT

The development of a software system of any reasonable size from initial conception through ongoing maintenance and evolution accrues significant coordination overheads.Often the mechanisms used to manage change and coordination detract from the time developers have to pursue the principal goal of constructing the desired system.This is one of the motivators behind the emerging agile methodologies. By permitting people to work as independently as possible and yet be aware of each others dependencies and constraints, it is believed that these secondary costs can be minimised. The position taken in the research summarised here is that better support can be provided for this type of weakly constrained coordination by enhancing the awareness, automated traceability, and constraint checking capabilities of software configuration management systems. Current progress in the research and plans for future work are described.

References

1. {1} B. Boehm. Get ready for agile methods, with care. Computer , 35(1):64-69, 2002.
2. {2} F. P. Brooks. The Mythical Man-Month: Essays on Software Engineering. Addison-Wesley, United States of America, 20th anniversary edition, 1995.
3. {3} M. C. Chu-Carroll and J. Wright. Supporting distributed collaboration through multidimensional software configuration management. In 10th International Workshop on Software Configuration Management (SCM-10), pages 40-53, 2001.
4. {4} S. Clarke, W. Harrison, H. Ossher, and P. Tarr. Subject-oriented design: Towards improved alignment of requirements, design and code. In Proceedings of the 1999 ACM SIGPLAN conference on Object-Oriented Programming, Systems, Languages, and Applications, pages 325- 339, 1999.
5. {5} G. Clemm, R. Conradi, A. van der Hoek, W. Tichy, and D. Wiborg-Weber. Impact of the research community for the field of software configuration management. In Proceedings of the 24th International Conference on Software Engineering , pages 634-644, 2002.
6. {6} A. Cockburn. Agile Software Development. The Agile Development Series. Pearson Education, Inc., United States of America, 2002.
7. {7} A. Egyed. A scenario-driven approach to traceability. In Proceedings of the 23rd International Conference on Software Engineering, pages 123-132, 2001.
8. {8} J. Estublier. Software configuration management: A roadmap. In ICSE Proceedings of the conference on the future of Software Engineering, pages 279-289, 2000.
9. {9} H. Gall, M. Jazayeri, and J. Krajewski. CVS release history data for detecting logical couplings. In Sixth International Workshop on Principles of Software Evolution (IWPSE 2003), pages 13-23, 2003.
10. {10} A. M. J. Hass. Configuration Management Principles and Practice. The Agile Development Series. Pearson Education, Inc., United States of America, 2003.
11. {11} M. Lycett, R. D. Macredie, C. Patel, and R. J. Paul. Migrating agile methods to standardized development practices. Computer , 36(6):79-85, 2003.
12. {12} A. Marcus and J. I. Maletic. Recovering documentation-to-source- code traceability links using latent semantic indexing. In Proceedings of the 25th International Conference on Software Engineering, pages 125-135, 2003.
13. {13} C. O'Reilly, P. Morrow, and D. Bustard. Improving conflict detection in optimistic concurrency control models. In 11th International Workshop on Software Configuration Management (SCM-11), pages 191-205, 2003.
14. {14} C. O'Reilly, P. Morrow, and D. Bustard. Lightweight prevention of architectural erosion. In International Workshop on Principles of Software Evolution (IWPSE-03), pages 59-64, 2003.
15. {15} D. E. Perry, H. P. Siy, and L. G. Votta. Parallel changes in large-scale software development: An observational case study. ACM Transactions of Software Engineering and Methodology, 10(3):308-337, 2001.
16. {16} B. Ramesh and M. Jarke. Towards reference models for requirements traceability. In IEEE Transactions on Software Engineering, volume 27, pages 58-93, 2001.
17. {17} A. Sarma, Z. Noroozi, and A. van der Hoek. Palantir: Raising awareness among configuration management workspaces. In Proceedings of the 25th International Conference on Software Engineering, pages 444-454, 2003.
18. {18} A. von Knethen. A trace model for system requirements changes on embedded systems. In Proceedings of the 4th international workshop on Principles of Software Evolution, pages 17-26, 2001.

Index Terms

• Software and its engineering

  • Software creation and management

    • Software post-development issues

      • Software reverse engineering

      • Software version control

  • Software notations and tools

    • Software configuration management and version control systems