Agile Models Need to be Bottom-up - Adding Productivity to a Late Project Makes it Later

Pietu Pohjalainen

Abstract

Model-driven architecture is a top-down approach to software engineering. Due to its heavy emphasis on tools and process, it has not been considered to be not a good fit for agile time-boxed iterations. Lightweight models are often a better alternative in agile development. However, we argue that in order to realize productivity gains, these models can and should be brought as software architecture level entities.

References

  1. Ambler, S. (2004). The Object Primer: Agile Model-Driven Development with UML 2.0. Cambridge University Press, 3rd edition.
  2. Biron, P. V. and Malhotra, A., editors (2004). XML Schema Part 2: Datatypes. W3C Recommendation. W3C, second edition.
  3. Brooks, Jr., F. P. (1995). The mythical man-month (anniversary ed.). Addison-Wesley Longman Publishing Co., Inc., Boston, MA, USA.
  4. Clau, M. and Jena, I. (2001). Modeling variability with UML. In In GCSE 2001Young Researchers Workshop.
  5. Czarnecki, K. and Eisenecker, U. W. (2000). Generative programming: methods, tools, and applications. ACM Press/Addison-Wesley Publishing Co., New York, NY, USA.
  6. Griss, M. L., Favaro, J., and Alessandro, M. d. (1998). Integrating feature modeling with the RSEB. In Proceedings of the 5th International Conference on Software Reuse, ICSR 7898, pages 76-, Washington, DC, USA. IEEE Computer Society.
  7. Kang, K. C., Cohen, S. G., Hess, J. A., Novak, W. E., and Peterson, A. S. (1990). Feature-oriented domain analysis (foda) feasibility study. Technical report, Carnegie-Mellon University Software Engineering Institute.
  8. Martens, W., Neven, F., Schwentick, T., and Bex, G. J. (2006). Expressiveness and complexity of xml schema. ACM Trans. Database Syst., 31(3):770-813.
  9. Mernik, M., Heering, J., and Sloane, A. M. (2005). When and how to develop domain-specific languages. ACM Comput. Surv., 37(4):316-344.
  10. Miller, J. and Mukerji, J. (2003). MDA guide version 1.0.1. Technical report, Object Management Group (OMG).
  11. Pohjalainen, P. (2011). Bottom-up modeling for a software product line: An experience report on agile modeling of governmental mobile networks. Software Product Line Conference, International, pages 323-332.
Download


Paper Citation


in Harvard Style

Pohjalainen P. (2012). Agile Models Need to be Bottom-up - Adding Productivity to a Late Project Makes it Later . In Proceedings of the 14th International Conference on Enterprise Information Systems - Volume 2: MDDIS, (ICEIS 2012) ISBN 978-989-8565-11-2, pages 395-400. DOI: 10.5220/0004155903950400


in Bibtex Style

@conference{mddis12,
author={Pietu Pohjalainen},
title={Agile Models Need to be Bottom-up - Adding Productivity to a Late Project Makes it Later},
booktitle={Proceedings of the 14th International Conference on Enterprise Information Systems - Volume 2: MDDIS, (ICEIS 2012)},
year={2012},
pages={395-400},
publisher={SciTePress},
organization={INSTICC},
doi={10.5220/0004155903950400},
isbn={978-989-8565-11-2},
}


in EndNote Style

TY - CONF
JO - Proceedings of the 14th International Conference on Enterprise Information Systems - Volume 2: MDDIS, (ICEIS 2012)
TI - Agile Models Need to be Bottom-up - Adding Productivity to a Late Project Makes it Later
SN - 978-989-8565-11-2
AU - Pohjalainen P.
PY - 2012
SP - 395
EP - 400
DO - 10.5220/0004155903950400