Combining DEMO and Normalized Systems for Developing Agile Enterprise Information Systems

  • Marien R. Krouwel
  • Martin Op ’t Land
Part of the Lecture Notes in Business Information Processing book series (LNBIP, volume 79)


Our research aims at finding key concepts to link agile enterprises with agile automated information systems. To effectively respond to environmental changes, such as in market needs, technology, regulations or law, enterprises need to be able to change their supporting information system(s) accordingly. The Design and Engineering Methodology for Organizations (DEMO) has already proven to be an effective tool in designing and realizing agile organizations. The Normalized System (NS) approach, on the other hand, has proven to be the key for developing agile Information and Communication Technology (ICT) systems, which support such agile organizations.

We found that DEMO and its underlying PSI-theory, and the principles and elements of the Normalized Systems approach match. Also we designed, using two cases of Dutch governmental subsidy schemes, a few simple and automatable steps to derive a Normalized System from the ontological model of the B-organization, provided by applying DEMO to an enterprise, while retaining the implementation freedom of the organization under consideration. Finally we found that the impact of implementation choices is minimal and that it is clear how they affect the automated information system. With this result, one vital cornerstone for achieving enterprise agility has been covered.


DEMO Normalized Systems Agile Enterprise Engineering 


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Tsourveloudis, N.C., Valavanis, K.P.: On the Measurement of Enterprise Agility. Journal of Intelligent and Robotic Systems (33), 329–342 (2002)CrossRefGoogle Scholar
  2. 2.
    Arnold, B., Engels, A., Op ’t Land, M.: FPS: een andere kijk op componenten en architectuur in de financiële wereld (deel 2). A & I, 24–32 (2000)Google Scholar
  3. 3.
    Dietz, J.L.G.: Enterprise Ontology. Springer, Heidelberg (2006)CrossRefGoogle Scholar
  4. 4.
    Mannaert, H., Verelst, J.: Normalized systems: re-creating information technology based on laws for software evolvability. Koppa, Kermt (2009)Google Scholar
  5. 5.
    Lehman, M.: On understanding laws, evolution, and conservation in the large-program life cycle. Journal of Systems and Software 1, 213–221 (1980)CrossRefGoogle Scholar
  6. 6.
    De Rijksoverheid : (Algemene wet bestuursrecht),
  7. 7.
    Huysmans, P., Bellens, D., Van Nuffel, D., Ven, K.: Aligning the Constructs of Enterprise Ontology and Normalized Systems. In: Albani, A., Dietz, J.L.G. (eds.) CIAO! 2010. Lecture Notes in Business Information Processing, vol. 49, pp. 1–15. Springer, Heidelberg (2010)CrossRefGoogle Scholar
  8. 8.
    Nuffel, D.V., Huysmans, P., Bellens, D., Ven, K.: Translating Ontological Business Transactions into Evolvable Information Systems. In: 5th International Conference on Software Engineering Advances, ICSEA 2010 (2010)Google Scholar
  9. 9.
    Op ’t Land, M.: Applying architecture and ontology to the splitting and allying of enterprises. PhD thesis. Delft University of Technology (2008)Google Scholar
  10. 10.
    de Jong, J., Dietz, J.L.: Understanding the realization of organizations. In: Albani, A., Dietz, J.L. (eds.) CIAO! 2010. Lecture Notes in Business Information Processing, vol. 49, pp. 31–49. Springer, Heidelberg (2010)CrossRefGoogle Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2011

Authors and Affiliations

  • Marien R. Krouwel
    • 1
  • Martin Op ’t Land
    • 1
    • 2
  1. 1.Capgemini NetherlandsUtrechtThe Netherlands
  2. 2.Delft University of TechnologyDelftThe Netherlands

Personalised recommendations