Advertisement

Agile and FBM: A Match Made in Heaven

  • Inge LemmensEmail author
  • Rob Arntz
Conference paper
Part of the Lecture Notes in Computer Science book series (LNCS, volume 11231)

Abstract

The agile way of working is often abbreviated to the principle: “working software over comprehensive documentation”, which is interpreted as “not need for documentation at all”. Looking carefully at the Agile manifesto, one also discovers the principle “continuous attention to technical excellence and good design enhances agility”. In this paper, we will cover the Agile principles and values mentioned in this manifesto and demonstrate how well fact-based modelling fits these principles and values.

Keywords

Fact-based model Agile Agile manifesto 

References

  1. 1.
    Schwaber, K., Beedle, M.: Agile Software Development with SCRUM, 1st edn. Prentice Hall PTR, Upper Saddle River (2001)Google Scholar
  2. 2.
    Beck, K., Andres, C.: Extreme Programming Explained: Embrace Change. Addison-Wesley Professional, Boston (2004)Google Scholar
  3. 3.
    Cockburn, A.: Agile Software Development. Addison-Wesley Professional, Boston (2001)zbMATHGoogle Scholar
  4. 4.
    Highsmith, J., Cockburn, A.: Agile software development: the business of innovation. Computer 34(9), 120–127 (2001)CrossRefGoogle Scholar
  5. 5.
    Cockburn, A., Highsmith, J.: Agile Software development: the people factor. Computer 34(11), 131–133 (2001)CrossRefGoogle Scholar
  6. 6.
    Fowler, M.: The new methodology. https://www.martinfowler.com/articles/newMethodology.html. Accessed 25 July 2018
  7. 7.
    Highsmith, J.: Adaptive Software Development: A Collaborative Approach to Managing Complex Systems. Dorset House Publishing, New York (2000)Google Scholar
  8. 8.
    Lemmens, I., Sgaramella, F., Valera, S.: Development of tooling to support fact-oriented modeling at ESA. In: Meersman, R., Herrero, P., Dillon, T. (eds.) OTM 2009. LNCS, vol. 5872, pp. 714–722. Springer, Heidelberg (2009).  https://doi.org/10.1007/978-3-642-05290-3_87CrossRefGoogle Scholar
  9. 9.
    Halpin, T.: Object-role modeling (ORM/NIAM). In: Bernus, P., Mertins, K., Schmidt, G. (eds.) Handbook on Architectures of Information System, pp. 81–101. Springer, Berlin (1998).  https://doi.org/10.1007/978-3-662-03526-9_4CrossRefGoogle Scholar
  10. 10.
    Homepage manifesto for agile software development. http://agilemanifesto.org/. Accessed 24 July 2018
  11. 11.
    Wendorff, P.: An essential distinction of agile software development processes based on systems thinking in software engineering management. In: Third International Conference on eXtreme Programming and Agile Processes in Software Engineering (2002)Google Scholar
  12. 12.
    Van Griethuysen, J.: Information processing systems – concepts and terminology for the conceptual schema and the information base. Technical report ISO TR9007 (1987)Google Scholar
  13. 13.
    INCOSE: Systems Engineering Vision 2020 (incose-tp-2004-004-02), INCOSE (2007)Google Scholar
  14. 14.
    Lemmens, I., Koster, J.P.: The rule configurator: a tool to execute a model and play with the rules. In: Debruyne, C., Ciuciu, J., Panetto, H., et al. (eds.) OTM 2016 Workshops. LNCS, pp. 155–163. Springer, Heidelberg (2016).  https://doi.org/10.1007/978-3-319-55961-2_15CrossRefGoogle Scholar
  15. 15.
    Lemmens, I., van de Laar, B., Saton, J., Bulles, J.: How to fulfil regulatory requirements consistently: a semantic-based approach. In: Debruyne, C., et al. (eds.) OTM 2017. LNCS, vol. 10697, pp. 202–211. Springer, Cham (2018).  https://doi.org/10.1007/978-3-319-73805-5_21CrossRefGoogle Scholar
  16. 16.
    Paulk, M.C.: Agile methodologies and process disciplines. Crosstalk: J. Defense Softw. Eng., 15(10) (2002)Google Scholar

Copyright information

© Springer Nature Switzerland AG 2019

Authors and Affiliations

  1. 1.PNAHeerlenThe Netherlands
  2. 2.i-Refact’s HertogenboschThe Netherlands

Personalised recommendations