Loading article...
Loading article...
Stream/Area:
-
Subject:
-
Paper ID:
IJSREM68738
Volume:
10 |
11 |
Nov 2026
Pages:
1-10
Publication Frequency:
Monthly (12 issues per year)
License:International Journal of Scientific Research in Engineering and Management follows the Creative Commons Attribution 4.0 (CC BY 4.0) License, allowing free use and distribution with proper attribution.

Department of Computer Science and Engineering
Hyderabad Institute of Technology and Management (HITAM)

Department of Computer Science and Engineering
Hyderabad Institute of Technology and Management (HITAM)

Department of Computer Science and Engineering
Hyderabad Institute of Technology and Management (HITAM)

Department of Computer Science and Engineering
Hyderabad Institute of Technology and Management (HITAM)

Department of Computer Science and Engineering
Hyderabad Institute of Technology and Management (HITAM)
Selecting an appropriate technology stack is one of the earliest and most consequential decisions in a software project, yet undergraduate students and small development teams often make this choice informally, relying on familiarity or prevailing trends rather than a structured assessment of project requirements. This paper presents TechManager, a rulebased decision support system implemented as a Flask web application that assists a user in obtaining a suitable frontend technology, backend technology, database, hosting platform and software architecture for a proposed project. The system accepts four inputs — project name, project type, team size and budget — and applies a set of predefined domain rules to generate a recommendation together with an estimated development complexity, a scalability indication, an estimated development time and cost, suggested team roles, a development roadmap, security recommendations and alternative technology options. Six project domains are currently supported: portfolio, education, hospital, banking, e-commerce and e-sports. Every generated recommendation is persisted in a SQLite database, enabling recommendation history, search/filter and deletion through the web interface. Unlike systems that rely on machine learning or statistical inference from historical project data, the TechManager recommendation engine is entirely rule-based, which makes its outputs transparent, explainable and straightforward to modify or extend. This paper describes the motivation, system architecture, methodology, rule-processing algorithm, implementation and a functional, test-case-based evaluation of TechManager, and discusses the advantages and limitations that follow from adopting a rule-based approach to technology-stack recommendation for student and small-team software projects.
KEYWORDS
This paper presented TechManager, a rule-based decision support system that helps students and small development teams select a technology stack and plan a software project from four simple inputs: project name, project type, team size and budget. The system's recommendation engine encodes domain knowledge for six project types as explicit rules governing technology selection, architecture, complexity and scalability, and combines this with straightforward estimation rules for development time, cost, team roles, a development roadmap, security recommendations and alternative technologies. The system is implemented as a Flask web application backed by a SQLite database and deployed on Render, and its behaviour was evaluated functionally against a representative set of test cases spanning all supported project domains, team sizes and budget levels. The central contribution of this work is not a claim that TechManager identifies the universally optimal technology stack for a given project — no rule-based system operating on three coarse inputs could credibly make such a claim — but rather a demonstration that a transparent, explainable and easily maintainable rule-based tool can provide a consistent, well-reasoned starting point for technology-selection and project-planning decisions that students and small teams currently make informally. The limitations discussed in Section XIII, particularly the system's dependence on manually maintained rules and its restriction to six project domains, define the boundaries within which this contribution should be understood, and motivate the future extensions outlined in Section XIV.
[1] P. Jackson, Introduction to Expert Systems, 3rd ed. Harlow, U.K.: Addison-Wesley, 1999. [2] M. Y. İmamoğlu and D. Çetinkaya, “A rule based decision support system for programming language selection,” in Proc. 2017 2nd Int. Conf. on Knowledge Engineering and Applications (ICKEA), London, U.K., 2017, doi: 10.1109/ICKEA.2017.8169904. [3] S. Farshidi, S. Jansen, R. de Jong, and S. Brinkkemper, “A decision support system for software technology selection,” Journal of Decision Systems, vol. 27, sup. 1, pp. 98–110, 2018, doi: 10.1080/12460125.2018.1464821. [4] A. Jedlitschka, D. Pfahl, and F. Bomarius, “A framework for experience-based decision support for software engineering technology selection,” in Proc. 16th Int. Conf. on Software Engineering and Knowledge Engineering (SEKE 2004), Banff, Canada, 2004, pp. 342–345. [5] M. Anvaari, “A rule-based framework for enhancing architectural decision guidance,” Ph.D. dissertation, Dept. of Computer Science, Norwegian Univ. of Science and Technology (NTNU), Trondheim, Norway, 2016. [6] S. Akbar, R. Ullah, R. Khan, I. Asghar, M. Zubair, and Z. Zheng, “A multi-criteria decision-making framework for software project management tool selection,” in Proc. 2023 9th Int. Conf. on Computer Technology Applications (ICCTA 2023), Vienna, Austria, ACM, 2023, doi:10.1145/3605423.3605454. [7] B. W. Boehm, Software Engineering Economics. Englewood Cliffs, NJ, USA: Prentice-Hall, 1981. [8] Pallets Projects, “Flask Documentation,” flask.palletsprojects.com, accessed Sept. 2026. [9] SQLite Consortium, “SQLite Documentation,” sqlite.org, accessed Sept. 2026.
Publication Date
11/5/2026
Peer Review Type
Double-Blind Peer Review
Review Rounds: 2
Documents
Article Views
2
Total views since publication
PDF Downloads
7
Total downloads since publication
Geographic Reach
5
Digital Preservation: This article is permanently archived on Zenodo and complies with all data preservation standards across major indexing platforms.
Plagiarism Screening
This manuscript has been checked for plagiarism using TurnitinPlagiarismChecker software.
Conflict of Interest
The authors declare no conflict of interest related to this research work.
Funding Information
No funding information available for this research.
Related research in the same subject area
Loading similar articles...