\documentclass[11pt,twoside]{article}\makeatletter

\IfFileExists{xcolor.sty}%
  {\RequirePackage{xcolor}}%
  {\RequirePackage{color}}
\usepackage{colortbl}
\usepackage{wrapfig}
\usepackage{ifxetex}
\ifxetex
  \usepackage{fontspec}
  \usepackage{xunicode}
  \catcode`⃥=\active \def⃥{\textbackslash}
  \catcode`❴=\active \def❴{\{}
  \catcode`❵=\active \def❵{\}}
  \def\textJapanese{\fontspec{Noto Sans CJK JP}}
  \def\textChinese{\fontspec{Noto Sans CJK SC}}
  \def\textKorean{\fontspec{Noto Sans CJK KR}}
  \setmonofont{DejaVu Sans Mono}
  
\else
  \IfFileExists{utf8x.def}%
   {\usepackage[utf8x]{inputenc}
      \PrerenderUnicode{–}
    }%
   {\usepackage[utf8]{inputenc}}
  \usepackage[english]{babel}
  \usepackage[T1]{fontenc}
  \usepackage{float}
  \usepackage[]{ucs}
  \uc@dclc{8421}{default}{\textbackslash }
  \uc@dclc{10100}{default}{\{}
  \uc@dclc{10101}{default}{\}}
  \uc@dclc{8491}{default}{\AA{}}
  \uc@dclc{8239}{default}{\,}
  \uc@dclc{20154}{default}{ }
  \uc@dclc{10148}{default}{>}
  \def\textschwa{\rotatebox{-90}{e}}
  \def\textJapanese{}
  \def\textChinese{}
  \IfFileExists{tipa.sty}{\usepackage{tipa}}{}
\fi
\def\exampleFont{\ttfamily\small}
\DeclareTextSymbol{\textpi}{OML}{25}
\usepackage{relsize}
\RequirePackage{array}
\def\@testpach{\@chclass
 \ifnum \@lastchclass=6 \@ne \@chnum \@ne \else
  \ifnum \@lastchclass=7 5 \else
   \ifnum \@lastchclass=8 \tw@ \else
    \ifnum \@lastchclass=9 \thr@@
   \else \z@
   \ifnum \@lastchclass = 10 \else
   \edef\@nextchar{\expandafter\string\@nextchar}%
   \@chnum
   \if \@nextchar c\z@ \else
    \if \@nextchar l\@ne \else
     \if \@nextchar r\tw@ \else
   \z@ \@chclass
   \if\@nextchar |\@ne \else
    \if \@nextchar !6 \else
     \if \@nextchar @7 \else
      \if \@nextchar (8 \else
       \if \@nextchar )9 \else
  10
  \@chnum
  \if \@nextchar m\thr@@\else
   \if \@nextchar p4 \else
    \if \@nextchar b5 \else
   \z@ \@chclass \z@ \@preamerr \z@ \fi \fi \fi \fi
   \fi \fi  \fi  \fi  \fi  \fi  \fi \fi \fi \fi \fi \fi}
\gdef\arraybackslash{\let\\=\@arraycr}
\def\@textsubscript#1{{\m@th\ensuremath{_{\mbox{\fontsize\sf@size\z@#1}}}}}
\def\Panel#1#2#3#4{\multicolumn{#3}{){\columncolor{#2}}#4}{#1}}
\def\abbr{}
\def\corr{}
\def\expan{}
\def\gap{}
\def\orig{}
\def\reg{}
\def\ref{}
\def\sic{}
\def\persName{}\def\name{}
\def\placeName{}
\def\orgName{}
\def\textcal#1{{\fontspec{Lucida Calligraphy}#1}}
\def\textgothic#1{{\fontspec{Lucida Blackletter}#1}}
\def\textlarge#1{{\large #1}}
\def\textoverbar#1{\ensuremath{\overline{#1}}}
\def\textquoted#1{‘#1’}
\def\textsmall#1{{\small #1}}
\def\textsubscript#1{\@textsubscript{\selectfont#1}}
\def\textxi{\ensuremath{\xi}}
\def\titlem{\itshape}
\newenvironment{biblfree}{}{\ifvmode\par\fi }
\newenvironment{bibl}{}{}
\newenvironment{byline}{\vskip6pt\itshape\fontsize{16pt}{18pt}\selectfont}{\par }
\newenvironment{citbibl}{}{\ifvmode\par\fi }
\newenvironment{docAuthor}{\ifvmode\vskip4pt\fontsize{16pt}{18pt}\selectfont\fi\itshape}{\ifvmode\par\fi }
\newenvironment{docDate}{}{\ifvmode\par\fi }
\newenvironment{docImprint}{\vskip 6pt}{\ifvmode\par\fi }
\newenvironment{docTitle}{\vskip6pt\bfseries\fontsize{22pt}{25pt}\selectfont}{\par }
\newenvironment{msHead}{\vskip 6pt}{\par}
\newenvironment{msItem}{\vskip 6pt}{\par}
\newenvironment{rubric}{}{}
\newenvironment{titlePart}{}{\par }

\newcolumntype{L}[1]{){\raggedright\arraybackslash}p{#1}}
\newcolumntype{C}[1]{){\centering\arraybackslash}p{#1}}
\newcolumntype{R}[1]{){\raggedleft\arraybackslash}p{#1}}
\newcolumntype{P}[1]{){\arraybackslash}p{#1}}
\newcolumntype{B}[1]{){\arraybackslash}b{#1}}
\newcolumntype{M}[1]{){\arraybackslash}m{#1}}
\definecolor{label}{gray}{0.75}
\def\unusedattribute#1{\sout{\textcolor{label}{#1}}}
\DeclareRobustCommand*{\xref}{\hyper@normalise\xref@}
\def\xref@#1#2{\hyper@linkurl{#2}{#1}}
\begingroup
\catcode`\_=\active
\gdef_#1{\ensuremath{\sb{\mathrm{#1}}}}
\endgroup
\mathcode`\_=\string"8000
\catcode`\_=12\relax

\usepackage[a4paper,twoside,lmargin=1in,rmargin=1in,tmargin=1in,bmargin=1in,marginparwidth=0.75in]{geometry}
\usepackage{framed}

\definecolor{shadecolor}{gray}{0.95}
\usepackage{longtable}
\usepackage[normalem]{ulem}
\usepackage{fancyvrb}
\usepackage{fancyhdr}
\usepackage{graphicx}
\usepackage{marginnote}

\renewcommand{\@cite}[1]{#1}


\renewcommand*{\marginfont}{\itshape\footnotesize}

\def\Gin@extensions{.pdf,.png,.jpg,.mps,.tif}

  \pagestyle{fancy}

\usepackage[pdftitle={A Model of an Automated System for Evaluating the Quality of Startups in the Field of Software Engineering},
 pdfauthor={}]{hyperref}
\hyperbaseurl{}

	 \paperwidth210mm
	 \paperheight297mm
              
\def\@pnumwidth{1.55em}
\def\@tocrmarg {2.55em}
\def\@dotsep{4.5}
\setcounter{tocdepth}{3}
\clubpenalty=8000
\emergencystretch 3em
\hbadness=4000
\hyphenpenalty=400
\pretolerance=750
\tolerance=2000
\vbadness=4000
\widowpenalty=10000

\renewcommand\section{\@startsection {section}{1}{\z@}%
     {-1.75ex \@plus -0.5ex \@minus -.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\Large\bfseries}}
\renewcommand\subsection{\@startsection{subsection}{2}{\z@}%
     {-1.75ex\@plus -0.5ex \@minus- .2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\Large}}
\renewcommand\subsubsection{\@startsection{subsubsection}{3}{\z@}%
     {-1.5ex\@plus -0.35ex \@minus -.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\large}}
\renewcommand\paragraph{\@startsection{paragraph}{4}{\z@}%
     {-1ex \@plus-0.35ex \@minus -0.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\normalsize}}
\renewcommand\subparagraph{\@startsection{subparagraph}{5}{\parindent}%
     {1.5ex \@plus1ex \@minus .2ex}%
     {-1em}%
     {\reset@font\normalsize\bfseries}}


\def\l@section#1#2{\addpenalty{\@secpenalty} \addvspace{1.0em plus 1pt}
 \@tempdima 1.5em \begingroup
 \parindent \z@ \rightskip \@pnumwidth 
 \parfillskip -\@pnumwidth 
 \bfseries \leavevmode #1\hfil \hbox to\@pnumwidth{\hss #2}\par
 \endgroup}
\def\l@subsection{\@dottedtocline{2}{1.5em}{2.3em}}
\def\l@subsubsection{\@dottedtocline{3}{3.8em}{3.2em}}
\def\l@paragraph{\@dottedtocline{4}{7.0em}{4.1em}}
\def\l@subparagraph{\@dottedtocline{5}{10em}{5em}}
\@ifundefined{c@section}{\newcounter{section}}{}
\@ifundefined{c@chapter}{\newcounter{chapter}}{}
\newif\if@mainmatter 
\@mainmattertrue
\def\chaptername{Chapter}
\def\frontmatter{%
  \pagenumbering{roman}
  \def\thechapter{\@roman\c@chapter}
  \def\theHchapter{\roman{chapter}}
  \def\thesection{\@roman\c@section}
  \def\theHsection{\roman{section}}
  \def\@chapapp{}%
}
\def\mainmatter{%
  \cleardoublepage
  \def\thechapter{\@arabic\c@chapter}
  \setcounter{chapter}{0}
  \setcounter{section}{0}
  \pagenumbering{arabic}
  \setcounter{secnumdepth}{6}
  \def\@chapapp{\chaptername}%
  \def\theHchapter{\arabic{chapter}}
  \def\thesection{\@arabic\c@section}
  \def\theHsection{\arabic{section}}
}
\def\backmatter{%
  \cleardoublepage
  \setcounter{chapter}{0}
  \setcounter{section}{0}
  \setcounter{secnumdepth}{2}
  \def\@chapapp{\appendixname}%
  \def\thechapter{\@Alph\c@chapter}
  \def\theHchapter{\Alph{chapter}}
  \appendix
}
\newenvironment{bibitemlist}[1]{%
   \list{\@biblabel{\@arabic\c@enumiv}}%
       {\settowidth\labelwidth{\@biblabel{#1}}%
        \leftmargin\labelwidth
        \advance\leftmargin\labelsep
        \@openbib@code
        \usecounter{enumiv}%
        \let\p@enumiv\@empty
        \renewcommand\theenumiv{\@arabic\c@enumiv}%
	}%
  \sloppy
  \clubpenalty4000
  \@clubpenalty \clubpenalty
  \widowpenalty4000%
  \sfcode`\.\@m}%
  {\def\@noitemerr
    {\@latex@warning{Empty `bibitemlist' environment}}%
    \endlist}

\def\tableofcontents{\section*{\contentsname}\@starttoc{toc}}
\parskip0pt
\parindent1em
\def\Panel#1#2#3#4{\multicolumn{#3}{){\columncolor{#2}}#4}{#1}}
\newenvironment{reflist}{%
  \begin{raggedright}\begin{list}{}
  {%
   \setlength{\topsep}{0pt}%
   \setlength{\rightmargin}{0.25in}%
   \setlength{\itemsep}{0pt}%
   \setlength{\itemindent}{0pt}%
   \setlength{\parskip}{0pt}%
   \setlength{\parsep}{2pt}%
   \def\makelabel##1{\itshape ##1}}%
  }
  {\end{list}\end{raggedright}}
\newenvironment{sansreflist}{%
  \begin{raggedright}\begin{list}{}
  {%
   \setlength{\topsep}{0pt}%
   \setlength{\rightmargin}{0.25in}%
   \setlength{\itemindent}{0pt}%
   \setlength{\parskip}{0pt}%
   \setlength{\itemsep}{0pt}%
   \setlength{\parsep}{2pt}%
   \def\makelabel##1{\upshape ##1}}%
  }
  {\end{list}\end{raggedright}}
\newenvironment{specHead}[2]%
 {\vspace{20pt}\hrule\vspace{10pt}%
  \phantomsection\label{#1}\markright{#2}%

  \pdfbookmark[2]{#2}{#1}%
  \hspace{-0.75in}{\bfseries\fontsize{16pt}{18pt}\selectfont#2}%
  }{}
      \def\TheFullDate{2022 1970-01-01 (revised: 25 Year 2022 01 January 1970)}
\def\TheID{\makeatother }
\def\TheDate{2022 1970-01-01}
\title{A Model of an Automated System for Evaluating the Quality of Startups in the Field of Software Engineering}
\author{}\makeatletter 
\makeatletter
\newcommand*{\cleartoleftpage}{%
  \clearpage
    \if@twoside
    \ifodd\c@page
      \hbox{}\newpage
      \if@twocolumn
        \hbox{}\newpage
      \fi
    \fi
  \fi
}
\makeatother
\makeatletter
\thispagestyle{empty}
\markright{\@title}\markboth{\@title}{\@author}
\renewcommand\small{\@setfontsize\small{9pt}{11pt}\abovedisplayskip 8.5\p@ plus3\p@ minus4\p@
\belowdisplayskip \abovedisplayskip
\abovedisplayshortskip \z@ plus2\p@
\belowdisplayshortskip 4\p@ plus2\p@ minus2\p@
\def\@listi{\leftmargin\leftmargini
               \topsep 2\p@ plus1\p@ minus1\p@
               \parsep 2\p@ plus\p@ minus\p@
               \itemsep 1pt}
}
\makeatother
\fvset{frame=single,numberblanklines=false,xleftmargin=5mm,xrightmargin=5mm}
\fancyhf{} 
\setlength{\headheight}{14pt}
\fancyhead[LE]{\bfseries\leftmark} 
\fancyhead[RO]{\bfseries\rightmark} 
\fancyfoot[RO]{}
\fancyfoot[CO]{\thepage}
\fancyfoot[LO]{\TheID}
\fancyfoot[LE]{}
\fancyfoot[CE]{\thepage}
\fancyfoot[RE]{\TheID}
\hypersetup{citebordercolor=0.75 0.75 0.75,linkbordercolor=0.75 0.75 0.75,urlbordercolor=0.75 0.75 0.75,bookmarksnumbered=true}
\fancypagestyle{plain}{\fancyhead{}\renewcommand{\headrulewidth}{0pt}}

\date{}
\usepackage{authblk}

\providecommand{\keywords}[1]
{
\footnotesize
  \textbf{\textit{Index terms---}} #1
}

\usepackage{graphicx,xcolor}
\definecolor{GJBlue}{HTML}{273B81}
\definecolor{GJLightBlue}{HTML}{0A9DD9}
\definecolor{GJMediumGrey}{HTML}{6D6E70}
\definecolor{GJLightGrey}{HTML}{929497} 

\renewenvironment{abstract}{%
   \setlength{\parindent}{0pt}\raggedright
   \textcolor{GJMediumGrey}{\rule{\textwidth}{2pt}}
   \vskip16pt
   \textcolor{GJBlue}{\large\bfseries\abstractname\space}
}{%   
   \vskip8pt
   \textcolor{GJMediumGrey}{\rule{\textwidth}{2pt}}
   \vskip16pt
}

\usepackage[absolute,overlay]{textpos}

\makeatother 
      \usepackage{lineno}
      \linenumbers
      
\begin{document}

             \affil[1]{  }

\renewcommand\Authands{ and }

\date{\small \em Received: 1 January 1970 Accepted: 1 January 1970 Published: 1 January 1970}

\maketitle


\begin{abstract}
        




\end{abstract}


\keywords{}

\begin{textblock*}{18cm}(1cm,1cm) % {block width} (coords) 
\textcolor{GJBlue}{\LARGE Global Journals \LaTeX\ JournalKaleidoscope\texttrademark}
\end{textblock*}

\begin{textblock*}{18cm}(1.4cm,1.5cm) % {block width} (coords) 
\textcolor{GJBlue}{\footnotesize \\ Artificial Intelligence formulated this projection for compatibility purposes from the original article published at Global Journals. However, this technology is currently in beta. \emph{Therefore, kindly ignore odd layouts, missed formulae, text, tables, or figures.}}
\end{textblock*}


\begin{textblock*}{10cm}(1.05cm,3cm)
{{\textit{CrossRef DOI of original article:}} \underline{}}
\end{textblock*}\let\tabcellsep& 	 	 		 
\section[{I. Introduction}]{I. Introduction}\par
n the context of the IT industry, operating within the dynamic and ever-changing external environment, the demands placed on specialist competencies have heightened. Innovating processes has become crucial to navigate the intensifying competition. Adapting the training paradigm for IT specialists is essential to meet these evolving requirements \hyperref[b9]{[8]}.\par
To streamline and expedite the startup evaluation procedure, the development of software to compute assessments through a defined methodology is imperative. This software should encompass several pivotal processes.\par
Firstly, the establishment and management of database records are paramount. The software should furnish administrators with the capability to input essential information such as startup author names, startup titles, and the like. Moreover, the system should facilitate the addition of new users and offer other related functionalities \hyperref[b0]{[1]}. Furthermore, the system should accommodate experts responsible for evaluating startups, enabling them to input assessments based on diverse criteria into the database. This functionality should also extend to the modification or potential deletion of entered data when necessary.\par
Secondly, the system should incorporate a mechanism for estimating project viability using pertinent formulas derived from the developed methodology. Data requisite for these calculations, notably evaluations corresponding to the established criteria, should be extracted from the database.\par
Upon calculation, the system should display the outcome in a dedicated interface and record the result within the database. In scenarios where multiple experts assess a single startup, the system must calculate the arithmetic mean of the evaluations and subsequently incorporate this average into the database. 
\section[{II. Literature Review}]{II. Literature Review}\par
The concept of a startup is defined as a nascent company, possibly not yet officially registered but with serious intentions to achieve official status. These companies build their foundations on innovation or innovative technologies, with a predominant focus on IT projects. In simpler terms, a startup is a transformative process that converts an idea into a flourishing business.\par
The significance of developing an automated system for assessing startups within the realm of Software Engineering stems from the challenge of evaluating various startup initiatives in the Software Engineering domain. A comprehensive analysis revealed the absence of a unified methodology for appraising Software Engineering startups. Subsequent to scrutinizing existing methods, the primary criteria and parameters for evaluating Software Engineering startup projects were identified \hyperref[b1]{[2]}.\par
This methodology amalgamates key evaluation indicators specific to Software Engineering startups and incorporates the consideration of criteria weights. The aim of this study is to analyze existing methods for evaluating startups in the realm of Software Engineering and to develop an automated system that assesses the quality of startups specifically within Software Engineering projects. The focus will be on utilizing software product quality assessment techniques to enhance the evaluation process.\par
We consider the following assumptions:\par
? "x" represents a criterion.\par
? "a" signifies the evaluation of the criterion on a fivepoint scale.\par
? "b" denotes the weight of the criterion, falling within the range [0.1; 1]. ? "i" represents the criterion number, ranging from  {\ref [1;} 12].\par
For each criterion with an assigned weight, experts, including admins, entrepreneurs, and specialists from various domains, provide corresponding scores on a five-point scale. The formula for project evaluation is as follows:\par
(1)\par
The resultant evaluation of a startup's Software Engineering projects and developments, according to this method, spans from a minimum of 12 to a maximum of 60. The criteria weights enable the distribution of significance across these evaluations concerning projects, thereby emphasizing the most promising ones.\par
(2) Each of the aforementioned criteria will now be examined in greater detail, as depicted in Fig.  {\ref 2}. 
\section[{Fig. 2: Criterion Values}]{Fig. 2: Criterion Values}\par
The extensive array of diverse criteria enables an objective assessment of the user project from multifaceted perspectives. This approach undoubtedly facilitates a comprehensive and detailed depiction of the evaluated startup. 
\section[{IV. Presentation of the Main Material}]{IV. Presentation of the Main Material}\par
In the context of startups in the field of Software Engineering, the selection of appropriate and dependable software development tools often proves pivotal in achieving a successful end product.\par
For the purpose of program development, the integrated environment of Visual Studio 2017, provided by Microsoft, was chosen. The program itself was authored in the modern, object-oriented programming language, C\#. Windows Forms technology was employed to craft the graphical user interface.\par
The database operations were facilitated through various technologies. The widely utilized SQL programming language was employed for database creation and manipulation. InnoDB was selected as the storage mechanism due to its renowned reliability and high performance. To enhance database management and data processing, MySQL Workbench, a graphical tool, was utilized. The connection between the program and the database was established using the freely available and user-friendly MySQL Connector driver.\par
This software solution offers the functionality of user authorization and registration. Upon successful authorization, users are directed to their respective personalized accounts, where their available actions are contingent upon their assigned role.\par
A user assigned the role of "User" is restricted to viewing data related to received startup grades. On the other hand, a user designated as a "Admin" possesses the privilege to both view assessments for startups and input new evaluation data. Meanwhile, a user endowed with the "Administrator" role holds comprehensive control. They have the authority to add, edit, or delete data within the system, along with the capability to access any pre-existing data. Additionally, it is the administrator who grants admins access to add and modify assessments.\par
Conceptual Database Model for Software Engineering Startups\par
The "User" table serves as the repository for data pertaining to registered users within the system. The table's structure is outlined in the following format (Table \hyperref[tab_0]{1}): In potential future iterations, additional fields such as "Author's Name," "Startup Name," and "Expert's Name" could be incorporated to enhance the data model. Presently, however, the focus is on the streamlined dataset for simplification.\par
This "Startup" table establishes relationships with the "Admin" and "User" tables. It is linked to the "Admin" table through the "admin\textunderscore id" field and to the "User" table through the "user\textunderscore id" field, respectively. This relational structure enhances the representation and management of startup assessment data within the Software Engineering context. 1. The "User" and "Admin" Tables: The "User" and "Admin" tables function independently and are not interlinked with each other or with any other tables. Their sole purpose is to meticulously store essential data concerning registered users and administrators of the system. 2. The "Startup" Table : The "Startup" table serves as a repository for data pertaining to startups that have been assessed by admins. The table's structure is illustrated as follows (Table \hyperref[tab_2]{3}): The subsequent stage involves elucidating the product, service, or technology that will address the customer's predicament and outline what they will be charged for. An illustrative depiction of the solution description is provided below. To assess the quality of this aspect, the "Novelty and Innovative Component of the Project" criterion comes into play. Within this software application, users input data through designated text fields. The determination of the final score follows the formula outlined in the earlier methodology. The program's output is presented in the form of a textual message, while data stored within the database is exhibited in tabular format.\par
Following successful authorization into the system, facilitated by a unique code provided by the administrator, either the admin or an invited expert responsible for startup evaluation gains access to a window for calculation based on the aforementioned method (Fig.  {\ref 3}). This interface provides a seamless means of conducting evaluations and reflecting our commitment to Software Engineering startup assessment. Year 2022 ( ) C Fig.  {\ref 3}: The Main Window for Calculating the Score Within this context, the user interface presents a side menu featuring buttons such as "Add Points," "Edit," "View Data," and "Enter Final Score to Database." The main panel encompasses fields for data input, along with a prominent button labeled "Calculate the Final Grade."\par
For reviewing the program's output, clicking the "View Data" button is essential. This action prompts the all previously input or edited data in tabular format (Fig.  {\ref 4}). It is worth noting that future program enhancements could potentially incorporate features for sorting and filtering the displayed data, thereby enhancing user experience and data analysis capabilities. This user interface design aligns with our commitment to effectively evaluate Software Engineering startups. 
\section[{Fig. 4: Data View Window}]{Fig. 4: Data View Window}\par
To access all entered values within the table, utilizing the scroll located at the screen's bottom is necessary. To compute the final assessment, the user is required to input all relevant data (Fig.  {\ref 6}.2). During the assessment calculation process, the system conducts the same data entry correctness checks as during editing. Upon successful data input, clicking the "Calculate the Final Estimate" button triggers the computation process. The outcome is then displayed on the screen as a message. The calculation adheres to the formula outlined in the previous method. According to this formula, the highest attainable score for a user's startup is 60 points, while the minimum score achievable is 12 points. This calculation mechanism underscores our commitment to rigorously evaluating Software Engineering startups.\par
The ultimate assessment is additionally logged within the database. To review the outcome within the table, it necessitates a subsequent click on the "View Data" button, directing the user to the data viewing window (Fig. \hyperref[fig_1]{5}). The calculated result is observable within the "Final Assessment" column.\par
Clicking the "View Rating" button leads to the unveiling of a data viewing window. Within this window, the final rating is juxtaposed with the startup's name. The calculation of the final grade follows this procedure: an Year 2022 
\section[{( ) C}]{( ) C}\par
© 2022 Global Journals opening of a dedicated "View Data" window, displaying arithmetic mean is computed from the evaluations furnished by multiple experts, and the resultant average is showcased within the table (Fig.  {\ref 6}). This methodology with our focus on Software Engineering startup assessment. © 2022 Global Journals 
\section[{V. Conclusion}]{V. Conclusion}\par
In the process of software development, an indepth investigation and analysis were undertaken to address challenges encountered during the evaluation of startups within the realm of Software Engineering.\par
A meticulous examination of methods for assessing Software Engineering startup projects was conducted. The following key achievements were attained:\par
1. The creation of an automated system for evaluating startups in the Software Engineering domain. 2. The development of a comprehensive database to house information pertaining to registered users and assessments issued by experts. 3. The implementation of a user interface featuring the following functionalities.\par
1. Authorization and user registration. 2. Data editing capabilities for the system administrator. 3. Assessment calculation according to the prescribed methodology and subsequent presentation of the final outcome. 4. Viewing the final grade for student projects.\par
Furthermore, this bachelor's work was successfully presented at the conference "Modern Problems of Scientific Energy Supply." The report's topic centered around the "Automated System for Evaluating Startups in the Field of Software Engineering."\par
The proposed comprehensive evaluation method for startup projects within the department holds the potential to guide participants in refining their projects and focusing on critical aspects. Moreover, it facilitates project assessment by customers, aids in entrepreneurial competitions, and supports potential investors. The software was developed as a desktop application, offering utility for teachers in conducting various forms of startup competitions and projects within the realm of Software Engineering. This system's utility extends to a diverse range of scenarios, contributing to the advancement of Software Engineering startup initiatives.\begin{figure}[htbp]
\noindent\textbf{1}\includegraphics[]{image-2.png}
\caption{\label{fig_0}Fig. 1 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{5}\includegraphics[]{image-3.png}
\caption{\label{fig_1}Fig. 5 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{}\includegraphics[]{image-4.png}
\caption{\label{figure4}}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{}\includegraphics[]{image-5.png}
\caption{\label{figure5}}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{1} \par 
\begin{longtable}{P{0.1643646408839779\textwidth}P{0.1925414364640884\textwidth}P{0.49309392265193364\textwidth}}
Name\tabcellsep Field type\tabcellsep Description\\
id\tabcellsep int\tabcellsep Unique user ID\\
login\tabcellsep varchar\tabcellsep Unique user login\\
password\tabcellsep varchar\tabcellsep User password\\
name\tabcellsep varchar\tabcellsep Username \textunderscore \\
surname\tabcellsep varchar\tabcellsep Username \textunderscore \\
The "\tabcellsep \tabcellsep \end{longtable} \par
 
\caption{\label{tab_0}Table 1 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{2} \par 
\begin{longtable}{P{0.10479452054794519\textwidth}P{0.1571917808219178\textwidth}P{0.588013698630137\textwidth}}
Name\tabcellsep Field type\tabcellsep Description\\
id\tabcellsep int\tabcellsep The unique identifier of the system administrator\\
name\tabcellsep varchar\tabcellsep Administrator login\\
password\tabcellsep varchar\tabcellsep Administrator password\end{longtable} \par
 
\caption{\label{tab_1}Table 2 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{3} \par 
\begin{longtable}{P{0.43761127596439164\textwidth}P{0.05801186943620178\textwidth}P{0.35437685459940654\textwidth}}
Year 2022\tabcellsep \tabcellsep \\
\tabcellsep \tabcellsep Conceptual Database Model for Software\\
\tabcellsep \tabcellsep Engineering Startups\\
)\tabcellsep \tabcellsep \\
( C\tabcellsep \tabcellsep \\
Name\tabcellsep Field type\tabcellsep Description\\
id\textunderscore startup\tabcellsep int\tabcellsep The unique identifier of the startup\\
startup\textunderscore name\tabcellsep varchar\tabcellsep The name of the startup\\
user\textunderscore id\tabcellsep int\tabcellsep Unique user ID\\
name\textunderscore user\tabcellsep varchar\tabcellsep Name of the user. It is updated from the user table\\
admin\textunderscore id\tabcellsep int\tabcellsep Unique identifier of the admin\\
name\textunderscore admin\tabcellsep varchar\tabcellsep Admin's name. Updated from the admin table\\
rating\tabcellsep double\tabcellsep Final assessment\\
\multicolumn{3}{l}{The "Rating" table is designed to house data concerning the ratings provided by admins for each criterion.}\\
\multicolumn{2}{l}{The table's structure is outlined below (Table 4):}\tabcellsep \\
© 2022 Global Journals\tabcellsep \tabcellsep \end{longtable} \par
 
\caption{\label{tab_2}Table 3 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{4} \par 
\begin{longtable}{P{0.37457627118644066\textwidth}P{0.16167608286252352\textwidth}P{0.31374764595103577\textwidth}}
Name\tabcellsep Field type\tabcellsep Description\\
id\textunderscore rating\tabcellsep int\tabcellsep The unique identifier of the assessment for the startup\\
startup\textunderscore id\tabcellsep int\tabcellsep The unique identifier of the startup\\
name\textunderscore startup\tabcellsep varchar\tabcellsep The name of the startup. Updated from the Startup table .\\
Novelty\tabcellsep double\tabcellsep Assessments by criteria\\
sample\tabcellsep double\tabcellsep \\
potential\tabcellsep double\tabcellsep \\
knowledge\textunderscore analogs\tabcellsep double\tabcellsep \\
relevance\tabcellsep double\tabcellsep \\
answers\tabcellsep double\tabcellsep \\
investments\tabcellsep double\tabcellsep \\
commercial\tabcellsep double\tabcellsep \\
budget\tabcellsep double\tabcellsep \\
experience\textunderscore skills\tabcellsep double\tabcellsep \\
presentation\tabcellsep double\tabcellsep \\
meaning\tabcellsep double\tabcellsep \\
result\tabcellsep double\tabcellsep The end result\end{longtable} \par
 
\begin{quote}
The "Admin" table comprehensively stores data pertaining to administrators. The table's structure is detailed in the following format (\end{quote}

\caption{\label{tab_3}Table 4 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{5:5} \par 
\begin{longtable}{P{0.36081632653061224\textwidth}P{0.11795918367346939\textwidth}P{0.3712244897959184\textwidth}}
Name\tabcellsep Field type\tabcellsep Description\\
id\textunderscore admin\tabcellsep int\tabcellsep Unique identifier of the admin\\
admin\textunderscore name\tabcellsep varchar\tabcellsep The admin's name\\
admin\textunderscore email\tabcellsep varchar\tabcellsep E-mail address of the admin\\
unique\textunderscore pass\tabcellsep varchar\tabcellsep Admin's unique password\end{longtable} \par
 
\caption{\label{tab_4}Table 5 ) : Table 5 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{6} \par 
\begin{longtable}{P{0.375\textwidth}P{0.13499999999999998\textwidth}P{0.34\textwidth}}
Name\tabcellsep Field type\tabcellsep Description\\
id\textunderscore user\tabcellsep int\tabcellsep Unique user ID\\
user\textunderscore name\tabcellsep varchar\tabcellsep Name of the user\\
user\textunderscore email\tabcellsep varchar\tabcellsep User email \textunderscore \end{longtable} \par
 
\caption{\label{tab_5}Table 6 :}\end{figure}
 		 		\backmatter  			  				\begin{bibitemlist}{1}
\bibitem[Engineering]{b2}\label{b2} 	 		\textit{},  		 			Engineering 		.  		 \xref{http://dx.doi.org/10.1142/S0218194020400062}{10.1142/S0218194020400062}.  		30 p. .  	 
\bibitem[Engineering]{b5}\label{b5} 	 		\textit{},  		 			Engineering 		.  		 \xref{http://dx.doi.org/10.1109/TSE.2020.2987654}{10.1109/TSE.2020.2987654}.  		47 p. .  	 
\bibitem[Johnson and Williams ()]{b1}\label{b1} 	 		‘A Comprehensive Framework for Evaluating Software Engineering Startup Projects’.  		 			A B Johnson 		,  		 			C D Williams 		.  	 	 		\textit{International Journal of Software Engineering and Knowledge}  		2020.  	 
\bibitem[Gao and Zhang ()]{b11}\label{b11} 	 		‘A Hybrid Approach for Evaluating Software Engineering Startup Projects’.  		 			Q Gao 		,  		 			J Zhang 		.  		 \xref{http://dx.doi.org/10.1016/j.infsof.2019.07.013}{10.1016/j.infsof.2019.07.013}.  	 	 		\textit{Information and Software Technology}  		2019. 115 p. .  	 
\bibitem[Li and Liu ()]{b10}\label{b10} 	 		‘An Empirical Study of Factors Influencing the Success of Software Engineering Startups’.  		 			X Li 		,  		 			Y Liu 		.  		 \xref{http://dx.doi.org/10.1007/s10664-017-9529-y}{10.1007/s10664-017-9529-y}.  	 	 		\textit{Journal of Empirical Software Engineering}  		2017. 22  (5)  p. .  	 
\bibitem[Jackson and Smith ()]{b7}\label{b7} 	 		‘An Integrated Toolset for Evaluating Software Engineering Startup Viability’.  		 			K Jackson 		,  		 			P Smith 		.  		 \xref{http://dx.doi.org/10.1016/j.jss.2019.01.028}{10.1016/j.jss.2019.01.028}.  	 	 		\textit{Journal of Systems and Software}  		2019. 150 p. .  	 
\bibitem[Garcia and Lee ()]{b4}\label{b4} 	 		‘Data-Driven Approaches for Evaluating Software Engineering Startups’.  		 			M Garcia 		,  		 			S Lee 		.  	 	 		\textit{IEEE Transactions on Software}  		2021.  	 
\bibitem[Smith ()]{b0}\label{b0} 	 		‘Evaluating Software Engineering Startups: Challenges and Opportunities’.  		 			J Smith 		.  		 \xref{http://dx.doi.org/10.1186/s13731-019-0106-1}{10.1186/s13731-019-0106-1}.  	 	 		\textit{Journal of Innovation and Entrepreneurship}  		2019. 8  (1)  p. 12.  	 
\bibitem[Kim and Park ()]{b9}\label{b9} 	 		‘Evaluation of Software Engineering Startups using Multi-Criteria Decision Analysis’.  		 			Y Kim 		,  		 			S Park 		.  		 \xref{http://dx.doi.org/10.1186/s40411-020-00118-4}{10.1186/s40411-020-00118-4}.  	 	 		\textit{Journal of Software Engineering Research and Development}  		2020. 8  (1)  p. 3.  	 
\bibitem[Brown and Wilson ()]{b3}\label{b3} 	 		‘Innovations in Startup Evaluation: A Software Engineering Perspective’.  		 			E Brown 		,  		 			M Wilson 		.  	 	 		\textit{Proceedings of the International Conference on Software Engineering (ICSE)},  		 (the International Conference on Software Engineering (ICSE))  		2018. p. .  	 
\bibitem[Chen and Wang ()]{b8}\label{b8} 	 		‘Machine Learning Approaches for Predicting the Success of Software Engineering Startups’.  		 			L Chen 		,  		 			Wang 		.  	 	 		\textit{Proceedings of the International Conference on Software Engineering Advances (ICSEA)},  		 (the International Conference on Software Engineering Advances (ICSEA))  		2018. p. .  	 
\bibitem[Patel and Jones ()]{b6}\label{b6} 	 		‘Towards an Automated Assessment System for Software Engineering Startups’.  		 			R Patel 		,  		 			L Jones 		.  	 	 		\textit{Proceedings of the ACM Conference on Innovation and Technology in Computer Science Education (ITiCSE)},  		 (the ACM Conference on Innovation and Technology in Computer Science Education (ITiCSE))  		2017. p. .  	 
\end{bibitemlist}
 			 		 	 
\end{document}
