A view-based approach for improving software documentation practices

Proceedings of the International Symposium and Workshop on Engineering of Computer Based Systems

Volumn , Issue , 2006, Pages 269-278

  Bayer, Joachim ^a   Muthig, Dirk ^a  

^a FRAUNHOFER IESE   (Germany)

Author keywords

[No Author keywords available]

Indexed keywords

CASE BASED REASONING; OBJECT ORIENTED PROGRAMMING; SOFTWARE DESIGN;

CASE STUDIES; SOFTWARE DOCUMENTATION; SOFTWARE SYSTEMS;

PROGRAM DOCUMENTATION;

EID: 34250011529     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/ECBS.2006.18     Document Type: Conference Paper

References (23)

1. S. W. Ambler, agile modeling. John Wiley & Sons, 2002.
2. C. Atkinson, J. Bayer, C. Bunse, E. Kamsties, O. Laitenberger, R. Laqua, D. Muthig, B. Paech, J. Wüst, and J. Zettel. Component-based Product Line Engineering with UML. Addison-Wesley, 2001.
3. T. T. Barker. Writig Software Documentation - A Task-Oriented Aproach. Allyn and Bacon, 1998.
4. V. R. Basili and H. D. Rombach. The TAME Project: Towards Improvement-Oriented Software Environments. In IEEE Transactions on Software Engineering, pp. 758-773, vol. 16, no. 6, June 1988.
5. J. Bayer, D. Muthig, and B. Goepfert. The Library System Product Line - A KobrA Case Study. Technical Report 024/01.E Fraunhofer IESE, 2001.
6. th International Workshop on Software Product-Family Engineering (PFE-4), 2001.
7. J. Bayer. View-Based Software Documentation. PhD Thesis, Fraunhofer IRB Verlag, 2004.
8. K. Beck, extreme Programming explained: embrace change. Addison-Wesley, 1999.
9. A. M. Davis. Software Requirements: Objects, Functions, and States. Prentice Hall, 1993.
10. A. Finkelstein, J. Kramer, B. Nuseibeh, L. Finkelstein, and M. Goedicke. Viewpoints: A Framework for Integrating Multiple Perspectives in System Development. In International Journal of Software Engineering and Knowledge Engineering, Vol. 2, No. 1, pp. 31-57, 1992.
11. L. Groves, R. Nickson, G. Reeve, S. Reeve, and M. Utting. A Survey of Software Development Practices in the New Zealand Software Industry. In Australian Software Engineering Conference, pp. 189-201, 2000.
12. W. Harrison and H. Ossher. Subject-Oriented Programming (A Critique of Pure Objects). In Proceedings of the 8th Conference on Object-Oriented Programming, Systems, Languages, and Applications (OOPSLA'93), 1993.
13. C. Hofmeister, R. Nord, and D. Soni. Applied Software Architecture. Addison-Wesley, 1999.
14. IEEE Recommended Practice for Software Requirements Specification, IEEE Standard 830, 1998.
15. IEEE Standard for Software User Documentation, IEEE Standard 1063, 1987.
16. I. John and D. Muthig. The State of the Practice of Systematic Software Development / Product Line Development in Germany, ViSEK Report 010/E 2003.
17. G. Kiczales, J. Lamping, A. Medhekar, C. Medea, C. Lopes, J.-M. Loingtier, and J. Irwin. Aspect-Oriented Programming. In Proceedings of the 11th European Conference on Object-Oriented Programming (ECOOP'97), June 1997.
18. P. Kruchten. The 4+1 View Model of Architecture. In IEEE Software, pp. 42-50, November 1995.
19. T. Olsson and P. Runeson. Document Use in Software Development: A Qualitative Survey. In Software Engineering Research and Practice in Sweden (SERPS'02), 2002.
20. A. Rüping. Agile Documentation - A Pattern Guide to Producing Lightweight Documents for Software Projects. John Wiley & Sons, 2003.
21. J. Sametinger. Software Engineering with Resuable Components. Springer, 1997.
22. P. Tarr, H. Ossher, W. Harrison, and S. M. Sutton, N Degrees of Separation: Multi-Dimensional Separation of Concerns. In Proceedings of ICSE'99, May 1999.
23. H. van Vliet. Software Engineering. Principles and Practice, 2nd ed., John Wiley & Sons, 2000.