Goal-driven software development

Proceedings of the 30th Annual IEEE/NASA Software Engineering Workshop, SEW-30

Volumn , Issue , 2006, Pages 59-65

  Schnabel, Ingo ^a   Pizka, Markus ^b  

^a ITESTRA GMBH   (Germany)

^b TECHNICAL UNIVERSITY OF MUNICH   (Germany)

Author keywords

[No Author keywords available]

Indexed keywords

SOFTWARE ENGINEERING;

(E ,3E) PROCESS; (OTDR) TECHNOLOGY; APPLIED (CO); BUSINESS DOMAINS; BUSINESS GOALS; BUSINESS PROCESSES (BP); COMMERCIAL SOFTWARES; HIGH QUALITY SOFTWARE; ITERATIVE PROCESSING; LOW COSTS; NEW PROCESSES; PROJECT CANCELLATION; REQUIREMENTS ELICITATION; SOFTWARE DEVELOPMENT; SOFTWARE DEVELOPMENT PROCESSES; SOFTWARE PROJECTS; TECHNICAL IMPLEMENTATION;

SOFTWARE DESIGN;

EID: 46449118620     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/SEW.2006.21     Document Type: Conference Paper

References (20)

1. The chaos report. Technical report, Standish Group, 1994.
2. P. Abrahamsson, O. Salo, J. Ronkainen, and J. Warsta. Agile software development methods. Review and Analysis VTT Publication 478, VTT Electronics, 2002.
3. V. R. Basili, G. Caldiera, and K. D. Rombach. Goal question metric paradigm. In J. J. Marciniak, editor, Encyclopedia of Software Engineering, volume 1, pages 527-532. John Wiley & Sons, 1994.
4. K. Beck. Extreme Programming Explained: Embrace Change. Addison-Wesley, 2000.
5. K. Beck, M. Beedle, A. van Bennekum, A. Cockburn, W. Cunningham, M. Fowler, J. Grenning, J. Highsmith, A. Hunt, R. Jeffries, J. Kern, B. Marick, R. C. Martin, S. Mellor, K. Schwaber, J. Sutherland, and D. Thomas. Manifesto for agile software development. www, 2001. http://agilemanifesto.org/.
6. B.Boehm. Software Engineering Economics. Prentice-Hall, 1981.
7. G. Booch. Object Solutions: Managing the Object-oriented Project. Addison-Wesley, 1996.
8. T. DeMarco and T. Lister. Peopleware: productive projects and teams. Dorset House, New York, 1987.
9. M. Fowler. Who needs an architect? IEEE Software, 20(5):11-13, Sept. 2003.
10. J. Greenfield. The case for software factories. Microsoft Architects Journal, (3), July 2004.
11. F. P. B. jr. The Mythical Man-Month. Addison Wesley, 1995.
12. P. Kruchten. The Rational Unified Process: An Introduction, Second Edition. Addison-Wesley Longman Publishing Co., Inc., Boston, MA, USA, 2000.
13. C. Larman, P. Kruchten, and K. Bittner. How to fail with the rational unified process: Seven steps to pain and suffering. Technical report, Valtech Technologies and Rational Software, 2001.
14. M. A. Lazzara, J. Benson, R. Fox, D. Laitsch, J. Rueden, D. Santek, D. Wade, and J. T. Y. T. Whittaker. Man computer interactive data access system (mcidas): 25 years of interactive processing. Bull. Amer. Meteor. Soc, jan 1999.
15. M. Lehman and J. F. Ramil. Rules and tools for software evolution planning and management. Annals of Software Engineering, 2001.
16. M. Meisinger, A. Rausch, M. Deubler, M. Gnatz, U. Hammerschall, I. Küffer, and S. Vogel. Das V Modell 200x - ein modulares Vorgehensmodell. In R. Kneuper, R. Petrasch, and M. Wiemers, editors, 11. Workshop der Fachgruppe WI-VM der Gesellschaft für Informatik e.V. (GI) zur Akzeptanz von Vorgehensmodellen. Shaker Verlag, 2004.
17. T. Panas, W. Löwe, and U. As̈mann. Towards the unified recovery architecture for reverse engineering. In B. Al-Ani, H. R. Arabnia, and Y. Mun, editors, Proc. of the Intern. Conf. on Software Engineering and Practice SERP'03, volume 1, pages 854-860, Las Vegas, NV, June 2003. CSREA Press.
18. M. Pizka and A. Bauer. A brief top-down and bottom-up philosophy on software evolution. In Proc. of the Int. Workshop on Principles of Software Evolution (IWPSE), Kyoto, Japan, Sept. 2004. IEEE Computer Society.
19. L. Rising and N. S. Janoff. The scrum software development process for small teams. IEEE Softw., 17(4):26-32, 2000.
20. W. W. Royce. Managing the development of large software systems. In IEEE Wescon, pages 1-9, 1970.