Skip to main content
Log in

Weil Aufwand wichtig ist!

Ein Zuordnungsmodell zur Bewertung des Projektaufwands im Requirements Engineering

Because Effort Matters!

  • Aufsatz
  • Published:
WIRTSCHAFTSINFORMATIK

Zusammenfassung

Anfallender Projektaufwand ist kritisch für den Erfolg von Softwareentwicklungsprojekten. Er hat wesentlich Einfluss darauf, ob Zeit- und Budgetbeschränkungen eingehalten werden können. Aber obwohl Anforderungen den Projektaufwand beeinflussen, können ihn Methoden des Requirements Engineering (RE) nicht berechnen.

In dieser Arbeit stellen wir unser Zuordnungsmodell zur Bewertung des Projektaufwands (MMAPE) dar. MMAPE bezieht die Berechnung des aus Anforderungen resultierenden Projektaufwands in das RE mit ein, indem es die Semantik des RE Verfahrens KAOS den Strukturen zuordnet, die in Funktionspunktanalysen gezählt werden. In einer Fallstudie haben wir MMAPE anhand eines Softwareentwicklungsprojekts eines großen Finanzinstituts angewendet. Die Gültigkeit des MMAPE Ansatzes wird durch die Übereinstimmung von MMAPE berechneten und aus der Fallstudie stammenden Daten unterstützt.

Abstract

Project effort is critical for the success of software development projects. It has a major impact on whether constraints in time and budget can be complied with. But although requirements affect project effort, requirements engineering (RE) methods are not capable of assessing project effort.

In this paper, we present our mapping model for assessing project effort (MMAPE). MMAPE incorporates into RE the assessment of project effort resulting from requirements for software development projects. It maps semantics of the RE method KAOS onto structures that are counted in function point analyses. We applied MMAPE in a case study on a software development project within a large financial institution. The validity of MMAPE is supported, since we found throughout consistent statements between information provided by MMAPE and data gathered from the case.

This is a preview of subscription content, log in via an institution to check access.

Access this article

Price excludes VAT (USA)
Tax calculation will be finalised during checkout.

Instant access to the full article PDF.

Abb. 1
Abb. 2
Abb. 3
Abb. 4
Abb. 5
Abb. 6
Abb. 7

Literatur

  • Abdel-Hamid T, Madnick S (1991) Software project dynamics. Prentice Hall, Englewood Cliffs

    Google Scholar 

  • Abran A, Robillard PN (1994) Function points: a study of their measurement processes and scale transformations. J Syst Softw 25:171–184

    Article  Google Scholar 

  • Albrecht AA (1979) Measuring application development productivity. In: Proc IBM App Dev Symp

  • Bergman M, King JL, Lyytinen K (2002) Large-scale requirements analysis revisited: the need for understanding the political ecology of requirements engineering. Requir Eng J 7(3):152–171

    Article  Google Scholar 

  • Boehm BW (1984) Software engineering economics. IEEE Trans Soft Eng 10(1):4–21

    Article  Google Scholar 

  • Campbell DJ (1988) Task complexity: a review and analysis. Acad Manage Rev 13(1):40–52

    Article  Google Scholar 

  • Cheung Y, Willis R, Milne B (1999) Software benchmarks using function point analysis. Benchmarking Int J 6(3):269–279

    Article  Google Scholar 

  • Dardenne A, van Lamsweerde A, Fickas S (1993) Goal-directed requirements acquisition. Sci Comput Program 20(1–2):3–50

    Article  Google Scholar 

  • Gencel C, Demirors O (2008) Functional size measurement revisited. ACM Trans Softw Eng Methodol 17(8):15–36

    Google Scholar 

  • Glinz M (2007) On non-functional requirements. In: Proc IEEE Joint Int Conf Req Eng, Delhi

  • Heemstra FJ (1992) Software cost estimation. Inform Softw Technol 34(10):627–639

    Article  Google Scholar 

  • IFPUG (1999) Function point counting practices manual release 4.1. International Function Point Users Group, Westerville

  • Jackson M Zave P (1995) Deriving specifications from requirements: an example. In: Proc 17th Int Conf Softw Eng (ICSE’95). ACM Press, New York, S 15–24

    Chapter  Google Scholar 

  • Kemerer CF (1993) Reliability of function points measurement. Commun ACM 36(2):85–97

    Article  Google Scholar 

  • Kotonya G, Sommerville I (1998) Requirements engineering: processes and techniques. Wiley, New York

    Google Scholar 

  • Letier E, van Lamsweerde A (2002) Deriving operational software specifications from system goals. In: Proc 10th ACM, SIGSOFT Symp Found Softw Eng, Charleston

  • Letier E, van Lamsweerde A (2004) Reasoning about partial goal satisfaction for requirements and design engineering. ACM SIGSOFT Softw Eng Notes 29(6):53–62

    Article  Google Scholar 

  • Marengoa L, Dosi G (2005) Division of labor, organizational coordination and market mechanisms in collective problem-solving. J Econ Behav Org 58:303–326

    Article  Google Scholar 

  • Markus ML (1983) Power, politics, and MIS implementation. Commun ACM 26(6):430–444

    Article  Google Scholar 

  • McCann JE, Ferry DL (1979) An approach for assessing and managing inter-unit interdependence. Acad Manage Rev 4(1):113–119

    Article  Google Scholar 

  • Mihm J, Loch C, Huchzermeier A (2003) Problem-solving oscillations in complex engineering projects. Manage Sci 49(6):733–750

    Article  Google Scholar 

  • Natt och Dag J, Regnell B, Carlshamre P, Andersson M, Karlsson J (2002) A feasibility study of automated natural language requirements analysis in market-driven development. Requir Eng 7(1):20–33

    Article  Google Scholar 

  • Robinson WN (1990) Negotiation behavior during requirement specification. In: Proc 12th Int Conf Softw Eng, Nice

  • Ryan K (1993) The role of natural language in requirements engineering. In: Proc IEEE Int Symp Req Eng, San Diego

  • Shaw M (1990) Prospect for an engineering discipline of software. IEEE Softw 7(6):15–24

    Article  Google Scholar 

  • Simon HA (1996) The sciences of the artificial. MIT Press, Cambridge

    Google Scholar 

  • van Lamsweerde A (2001) Goal-oriented requirements engineering: a guided tour. Invited Paper. In: 5th IEEE Int Symp Req Eng, Toronto

  • van Lamsweerde A (2004) Goal-oriented requirements engineering: a roundtrip from research to practice. In: 12th IEEE Int Req Eng Conf, Kyoto

  • van Lamsweerde A, Willemet L (1998) Inferring declarative requirements specifications from operational scenarios. IEEE Trans Sofw Eng 24(12):1089–1114

    Article  Google Scholar 

  • van Lamsweerde A, Darimont R, Letier E (1998) Managing conflicts in goal-driven requirements engineering. IEEE Trans Softw Eng 24(11):908–926

    Article  Google Scholar 

  • Yu E (1997) Towards modelling and reasoning support for early-phase requirements engineering. In: Proc 3rd IEEE Int Symp Req Eng

Download references

Danksagung

Diese Arbeit ist als Teil eines Forschungsprojekts am E-Finance Lab der Goethe Universität Frankfurt entstanden. In dieser Arbeit ausgedrückte Meinungen, Erkenntnisse, Schlussfolgerungen oder Empfehlungen sind die der Autoren und müssen nicht die Ansicht des E-Finance Labs oder seiner unterstützenden Partner widerspiegeln. Die Autoren danken den beteiligten Universitäten und den Industriepartnern für ihre Unterstützung.

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to Frank Zickert.

Additional information

Angenommen nach einer Überarbeitung durch die Herausgeber des Schwerpunktthemas.

This article is also available in English via http://www.springerlink.com and http://www.bise-journal.org: Zickert F, Beck R (2010) Because Effort Matters! A Mapping Model for Assessing Project Effort in Requirements Engineering. Bus Inf Syst Eng. doi: 10.1007/s12599-010-0103-y.

Rights and permissions

Reprints and permissions

About this article

Cite this article

Zickert, F., Beck, R. Weil Aufwand wichtig ist!. WIRTSCHAFTSINFORMATIK 52, 161–171 (2010). https://doi.org/10.1007/s11576-010-0225-3

Download citation

  • Received:

  • Accepted:

  • Published:

  • Issue Date:

  • DOI: https://doi.org/10.1007/s11576-010-0225-3

Schlüsselwörter

Keywords

Navigation