Module 6: Software Technology & System Development (Supplement)

[Deutsch]

Books

1. Boehm, Barry W. (1981): Software Engineering Economics. Englewood Cliffs (NJ): Prentice-Hall.
2. Boehm, Barry W.; Abts, Chris;  Brown, A. Winsor (2000): Software Cost Estimation with Cocomo II, with CD-ROM. London: Prentice-Hall
3. Budde, R.;  Kuhlenkamp, K.; Mathiassen, L.; Zullinghoven H. (1984): Approaches to Prototyping. Berlin et al.: Springer.
4. Booch, Grady (1998): The Unifed Modeling Language User Guide. Reading (MA): Addison-Wesley.
5. Coad, Peter; Yourdan, Edward (1991): Object-Oriented Analysis. 2nd Edition. Englewood Cliffs (NJ): Prentice-Hall.
6. Denert, Ernst  (1998): Software Engineering. Methodische Projektabwicklung. Berlin u.a.: Springer.
7. Fairley, Richard E. (1985): Software Engineering Concepts. Hillsdale (NJ): McGraw-Hill.
8. Fensel, Dieter (2000): Problem-Solving Methods. Understanding, Description, Development, and Reuse (Lecture Notes in Computer Science Vol. 1791). Berlin et al.: Springer

9. Gamma, Erich (1995): Design Patterns. 5th Edition. Reading (MA): Addison-Wesley.

10. Harmon, P., Watson, M. (1998): Understanding UML: The Developers Guide, San Francisco: Morgan Kaufman.
11. Garmus, David; Herron, David (2000):  Function Point Analysis. Reading (MA): Addison Wesley.
12. Jones, Capers (2000): Software Assessments, Benchmarks, and Best Practices. Reading (MA): Addison Wesley.
13. Marca, D. A.; McGowan, C. L. (1988): SADT- Structured Analysis and Design Technique, New York: McGraw- Hill.
14. McDermid John (1991): Software engineer's reference book. London: Butterworth-Heinemann.
15. Pressman, Roger S. (1988):  Software Engineering: a beginner’s guide. New York: McGraw Hill.
16. Schwalbe, Kathy (2002): Information Technology Project Management. Second Edition. Boston (MA): Thomson Course Technology.

17. Sommerville, Ian (1995): Software Engineering. 5th Edition. Reading (MA): Addison-Wesley.

18. Thalheim, Bernhard (2000): Entity-Relationship Modeling. Foundations of Database Technology. Berlin et al.: Springer.

1. Boehm, Barry  W. (1988): A spiral model of software development and enhancement. IEEE Computer, 21 (5), 61-72.
2. Boehm, Barry  W.; Basili, V. R. (2001): Software Defect Reduction Top 10 List. IEEE Computer, 34 (1), 135-137.
3. Boehm, Barry W. (2000): Safe and Simple Software Cost Analysis. IEEE Software. September/October 2000, Vol. 17, No. 5, 14-17.
4. Brooks, Frederick P. (1995): The mythical man-month after 20 years. IEEE Software, 12 (5), 57-60.
5. Chen, Peter (1976): The Entity-Relationship Model - Toward a Unified View of Data.  ACM Transactions on Database Systems, Vol. 1, No 1, March 1976,9-36
6. Floyd, Christiane; Reisin, F. M.; Schmidt, G. (1989): Steps to Software Development with Users. In: Ghezzi, C.; McDermid, J.A., eds., Nr. 287 Lecture Notes in Computer Science, 48-64.
7. Jezequel, Jean-Marc; Meyer, Bertrand (1997): Design by contract: The lessons of Ariane. IEEE Computer, 30 (1):129-130.
8. Jones, Capers (1995): Backfiring: Converting Lines-of-Code to Function Points, IEEE Computer November 1995, Vol. 28, No. 11,  87-88
9. Parnas, David L. (1972): On the criteria to be used in decomposing systems into modules. Communications of the ACM, 15, 1053-1058.
10. Parnas, David L. (1985): Software aspects of strategic defense systems. Communications of the ACM, 28 (12):1326-1335.
11. Raccoon, L. B. S. (1997): Fifty years of progress in software engineering. ACM Software Engineering Notes, 22 (1), 88-104.
12. Whitaker, James A. (2000): What is Software Testing? And Why Is It So Hard? IEEE Software. 17 (1): 70-79.
13. Wirth, Niklas (1995): A Plea for Lean Software. IEEE Computer, 28 (2), 64-68.
14. Zemanek, Heinz (1979):  Architecture: General Concepts for Systems Design. In: Bjorner, Dines, ed. Abstract Software, Proceedings of 1979 Copenhagen Winter School, Nr. 86 in Lecture Notes in Computer Science, 1-42.

Thank you for your kind interest and patience.