Combining Low-Code Platforms with Traditional Software Engineering for Agile Development

  • Authors

    • Mr. Ajay Krishnan Technical Lead, Tech Mahindra, India. Author
    • Ms. Ritu Agarwal Finance Manager, Capgemini, India. Author

    DOI:

    https://doi.org/10.67228/30713315/IJAIDT-2018PIIABX

    Published 09-05-2018

  • Low-Code Platforms, Traditional Software Engineering, Agile Development, Hybrid Development Model, Software Development Efficiency, Case Studies, Best Practices

    Issue

    Vol. 1 No. 2 (2018)

    Section

    Articles

    How to Cite

    [1]
    A. Krishnan and R. Agarwal, “Combining Low-Code Platforms with Traditional Software Engineering for Agile Development”, IJAIDT, vol. 1, no. 2, pp. 01–09, Sep. 2018, doi: 10.67228/30713315/IJAIDT-2018PIIABX.

  • Abstract

    The integration of low-code platforms with traditional software engineering practices presents a transformative approach to agile development. Low-code platforms enable rapid application development through visual interfaces and minimal coding, fostering increased collaboration and faster time-to-market. However, challenges such as limited customization and potential technical debt necessitate the involvement of experienced software engineers. This paper explores the synergies between low-code platforms and traditional development methodologies, proposing a hybrid model that leverages the strengths of both. We examine case studies where this integration has led to improved development efficiency and product quality, and discuss best practices for implementing this combined approach in agile environments.

  • References

    [1] Richardson, C., & Rymer, J. R. (2014). Vendor landscape: The new wave of low-code platforms. Forrester Research.

    [2] Mellor, S. J., Clark, A. N., & Futagami, T. (2003). Model-driven development: Guest editors’ introduction. IEEE Software, 20(5), 14–18.

    [3] Schmidt, D. C. (2006). Model-driven engineering. Computer, 39(2), 25–31.

    [4] Fowler, M. (2005). Domain-specific languages. Addison-Wesley.

    [5] Greenfield, J., Short, K., Cook, S., & Kent, S. (2004). Software factories: Assembling applications with patterns, models, frameworks, and tools. Wiley.

    [6] Boehm, B., & Turner, R. (2004). Balancing agility and discipline: A guide for the perplexed. Addison-Wesley.

    [7] Beck, K., et al. (2001). Manifesto for Agile Software Development. Agile Alliance.

    [8] Highsmith, J. (2002). Agile software development ecosystems. Addison-Wesley.

    [9] Pressman, R. S. (2010). Software engineering: A practitioner’s approach (7th ed.). McGraw-Hill.

    [10] Sommerville, I. (2016). Software engineering (10th ed.). Pearson.

    [11] Bass, L., Clements, P., & Kazman, R. (2012). Software architecture in practice (3rd ed.). Addison-Wesley.

    [12] Erdogmus, H. (2005). The economic impact of learning and flexibility in software development. IEEE Software, 22(3), 76–83.

    [13] Ambler, S. W. (2002). Agile modeling: Effective practices for extreme programming and the unified process. Wiley.

    [14] Koskela, L., & Howell, G. (2002). The theory of project management: Explanation to novel methods. Proceedings of the International Group for Lean Construction.

    [15] Avison, D., & Fitzgerald, G. (2006). Information systems development: Methodologies, techniques and tools (4th ed.). McGraw-Hill.

  • Downloads