Advertisement

Tamed Agility in Developing Mobile Business Systems

  • Volker Gruhn
  • Matthias Book
Part of the Lecture Notes in Computer Science book series (LNCS, volume 8093)

Abstract

Mobile systems are determined by requirements which tend to change over time. Agile approaches seem to address this, but fail to provide reliable project plans, budget estimations and capacity forecasts. Thus, mobile enterprise applications demand for tamed agility, reconciling advantages of agile development and plan-driven approaches. In this paper, this tradeoff is addressed. The Interaction Room method is introduced as a low-tech method to support value-oriented development of mobile applications.

Keywords

Mobile systems agile development modeling team interaction 

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    Curtis, B., Krasner, H., Iscoe, N.: A field study of the software design process for large systems. Communications of the ACM 31(11), 1268–1287 (1988)CrossRefGoogle Scholar
  2. 2.
    Kautz, K., Madsen, S., Nørbjerg, J.: Persistent problems and practices in information systems development. Inf. Sys. J. 17(3), 217–239 (2007)CrossRefGoogle Scholar
  3. 3.
    Whitehead, J.: Collaboration in software engineering: A roadmap. In: Proc. Future of Software Engineering (FOSE 2007), pp. 214–225. IEEE Computer Society (2007)Google Scholar
  4. 4.
    Larman, C., Basili, V.: Iterative and incremental developments – a brief history. IEEE Computer 36(6), 47–56 (2003)CrossRefGoogle Scholar
  5. 5.
    Boehm, B., Huang, L.: Value-based software engineering. ACM Software Engineering Notes 28, 4–10 (2003)CrossRefGoogle Scholar
  6. 6.
    Davidson, E.: Joint application design (JAD) in practice. Journal of Systems and Software 45(3), 215–223 (1999)CrossRefGoogle Scholar
  7. 7.
    Burge, J., Carroll, J., McCall, R., Mistrík, I.: Rationale-based software engineering. Springer (2008)Google Scholar
  8. 8.
    Schwaber, K., Beedle, M.: Agile Software Development with Scrum. Prentice Hall (2002)Google Scholar
  9. 9.
    Pavlovski, C.J., Zou, J.: Non-functional requirements in business process modeling. In: Proc. 5th Asia-Pacific Conference on Conceptual Modeling (APCCM 2008), pp. 103–112. Australian Computer Society (2008)Google Scholar
  10. 10.
    Bocciarelli, P., d’Ambrogio, A.: A BPMN extension for modeling non-functional properties of business processes. In: Proc. 2011 Symposium on Theory of Modeling & Simulation (TMS-DEVS 2011), pp. 160–168. Society for Computer Simulation (2011)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2013

Authors and Affiliations

  • Volker Gruhn
    • 1
  • Matthias Book
    • 1
  1. 1.paluno – The Ruhr Institute for Software TechnologyUniversity of Duisburg-EssenEssenGermany

Personalised recommendations