<?xml version="1.0" encoding="UTF-8"?>
<TEI xml:space="preserve" xmlns="http://www.tei-c.org/ns/1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://www.tei-c.org/ns/1.0 https://raw.githubusercontent.com/kermitt2/grobid/master/grobid-home/schemas/xsd/Grobid.xsd"
 xmlns:xlink="http://www.w3.org/1999/xlink">
	<teiHeader xml:lang="en">
		<fileDesc>
			<titleStmt>
				<title level="a" type="main">Analysis and Risk Management in Software Development Using the Logical-Algebraic Model</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author role="corresp">
							<persName><forename type="first">Khansaa</forename><surname>Azeez</surname></persName>
							<email>azeezkhansaa@gmail.com</email>
							<affiliation key="aff0">
								<orgName type="department">Babylon Technical Institute</orgName>
								<orgName type="institution">Al-Furat Al-Awsat Technical University</orgName>
								<address>
									<postCode>51015</postCode>
									<settlement>Babylon</settlement>
									<country key="IQ">Iraq</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Obayes</forename><surname>Al-Husseini</surname></persName>
							<affiliation key="aff1">
								<orgName type="department">Babylon Technical Institute</orgName>
								<orgName type="institution">Al-Furat Al-Awsat Technical University</orgName>
								<address>
									<postCode>51015</postCode>
									<settlement>Babylon</settlement>
									<country key="IQ">Iraq</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Ali</forename><forename type="middle">Hamzah</forename><surname>Obaid</surname></persName>
						</author>
						<title level="a" type="main">Analysis and Risk Management in Software Development Using the Logical-Algebraic Model</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">43219B77133557E5D9EF02429776E193</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-23T22:04+0000">
					<desc>GROBID - A machine learning software for extracting information from scholarly documents</desc>
					<ref target="https://github.com/kermitt2/grobid"/>
				</application>
			</appInfo>
		</encodingDesc>
		<profileDesc>
			<textClass>
				<keywords>
					<term>Risk Management</term>
					<term>Software Intensive Systems (SIS)</term>
					<term>information technology (IT)</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>In this paper, we construct a logical-algebraic model that covers all the parameters and operations of the risk process and create Specification of risk assessment processes based on logical-algebraic formalisms-sets, matches, relations, tuples, predicates, and Specification tools to automate the process of risk assessment. And addressing concerns in a change in the software development life cycle that changes requirements depending on the requirements of the development work.</p></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1">Introduction</head><p>Risk is an increased probability of loss, The risk is an increased probability at losses, a possible problem that is or not to occur. This, as a rule, arises from the loss of input, control in time. And the possibility of a loss in the process of software development is called the risk of software development. The loss can be any, for example, increasing the cost of production, reducing the quality of software development, the inability to complete the project on time. The risk of software development exists because the future remains uncertain, and there are many known and unknown things that cannot be included in the project plan. The risk of software development There are two types of risks that are either internal and controlled by the project manager or external risks that are outside the control of the project manager To automate the processes of risk assessment, first of all, it is necessary to build the most general model that reflects common entities: the totality of the parameters used and the operations used. Logical algebraic models are most often used to specify objects of modeling at the most general level. When modeling the risk assessment processes, this reveals a multitude of parameter values and a variety of operations of the risk assessment process. When creating appropriate automation tools in the logical-algebraic model, multiple specifications appear that are involved in risk assessment, as well as many software functions for processing these specifications and generating estimates.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2">Software development methodology</head><p>is the operation of dividing software development work into distinct stages And aiming to a good organization and to improve the design.   Figure <ref type="bibr" target="#b1">(2)</ref> above oversimplifies the process subtleties The first step is ideas in the process, extract and form these ideas of the requirements, the requirements that feed the process are ideas. Program objectives can be set at the requirements stage.</p><p>In the second step, the output of a development process, The user manual, software development documentation, testing, and maintenance is the product of the development process to help developers improve and develop the software in the future</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4">Risk Management in Software Development</head><p>Risk is the probability of loss. This depends both on the likelihood of adverse events and the consequences of these events; The impact is manifested in a blend of money related misfortunes, time delays and loss of productivity. Hazard is an antecedent to the issue, the probability that at some random point in the product life cycle, Because of these and other factors, every software development project contains elements of uncertainty. the predicted goals will become unattainable within the accessible assets.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>5</head><p>Empirical Data Sample Analysis is a proof-based way to deal with the investigation and translation of data. The exact methodology depends on genuine information, measurements, and results as opposed to speculations and ideas. The data sample provided by project consists the following assumptions about the data sample were made:</p><p> Duration of the project.  Start and finish date.  Development cost.  Rate software development.</p><p>These findings suggest that the data sample provided by the project the specific features of risk data. Software Development projects have a high rate of failure. A model of software development using the Logical-Algebraic Model describes managerial processes that can be used to reduce software development difficulties from the managerial control perspective.</p><p>Our study examined the performance of projects Software Development in relation to the activities of maturity. activities associated with the Software Development control of development-related positively to project performance measures.</p><p>Measure of probability Probability measures in Software Development risk analysis must relate to a specified level of exposure which can, for example, be the consumption of a particular quantity of Project time without work, or an individual exposure event.</p><p>. The probability measures are generally expressed in one of two forms: • The probability of the risk event occurring with a specified exposure event (e.g. probability of illness),</p><p>• The average number of risk events that may occur within a specified period.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="6">Description of the Risk Assessment Process</head><p>Software Development projects have a high rate of failure. Organizations have tried to reduce the rate through methodological approaches but with little perceived success.</p><p>A model of software development maturity using the Logical-Algebraic Model describes managerial processes that can be used to attack software development difficulties from the managerial control perspective. Our study examined the performance of projects Software Development in relation to the activities of maturity. activities associated with the Software Development control of development-related positively to project performance measures. Work on risk analysis and the construction of an adequate model of its assessment is very time-consuming. This is due, on the one hand, to the instability of the causes of risk factors, and on the other hand, to the complexity of formalizing the quantitative assessment of performance. Therefore, the justification and development of risk assessment models require a thorough analysis of the nature of the initial information on the causes and risk factors, as well as the purpose of the study.</p><p>Depending on the nature of the initial information available at the time of problem statement and the chosen method of uncertainty description, the following classes of mathematical models of risk impact assessment are most common: deterministic; stochastic; linguistic and non-stochastic.</p><p>In its most general form, parameterization of risk assessment processes covers the following entities:</p><p>where R is an assessment of the consequences of a risk event; P-probability of occurrence of a risk event; I-potential consequences of the risk factor.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="7">Development of Logical-Algebraic Model</head><p>The above description shows that the risk assessment process involves different in nature and mechanisms of representation of the entity, which causes the multi-grade algebraic model. To formalize using the technique of multi-sorted algebras (algebras multistoried) you must first specify the underlying set. This specification is given below.</p><p>PSPEC ={ PSpec1, PSpec2, …} -project specification,</p><p>Where PSpeci =&lt; attгi ,vali&gt; -significant specifier, attг i -attribute і-rо specifier's, vali -attribute value і-rо specifier's.</p><p>Pnp: RF × PR × SF × PF → {true, false} -the predicate initiate the prototyping process in order to clarify the risk factors.</p><p>Composing a system of supporting sets and functions involved in risk assessment, as well as a set of predicates that serve the process, we obtain the following logical-algebraic model in the format of a multi-grade algebra specification: Risk assessment -a set of analytical measures to predict the possibility of obtaining additional business income or a certain amount of damage from the risk situation and late adoption of measures to prevent the risk. The degree of risk is the probability of occurrence of a loss event, as well as the amount of possible damage from it. Risk can be:</p><p>acceptable-there is a threat of complete loss of profit from the implementation of the planned project; critical-possible non-receipt of not only profits, but also revenue and loss coverage at the expense of the entrepreneur; catastrophic-possible loss of capital, property, and bankruptcy of the entrepreneur.</p><p>The risk impact assessment model can be summarized as follows: F = f(P, I)…… where: F -assessment of the consequences of a risk event; P-probability of occurrence of a risk event; I-potential consequences of a risk event.</p><p>In General, the construction of a risk assessment model is complicated by the instability of causes or risk factors and the complexity of formalizing the results of activities. Therefore, when justifying and developing risk assessment models, a thorough analysis of the nature of the initial information on the causes and risk factors is required.</p><p>From the above we come to an Algebraic model of the process Figure <ref type="bibr" target="#b2">(3)</ref>. PPstop = Predicate that detects that all the possibilities to Refine the risk assessment have been exhausted</p><p>Pstop=( T Bound Fig. <ref type="figure">3</ref>. Algebraic model of the process.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="9">Conclusion</head><p>The practical importance of research is the ability to use theoretical and methodological results in practice to ensure risk calculation and thus the stability of the means of implementation and development of the project as there are many risks associated with creating high-quality programs on time and with a specific budget. Nevertheless, in order to make sense to take these risks, they should be compensated with sufficient remuneration. The developed tools help the project manager to provide for risk response measures, based on more reliable information. Reliable and more detailed information allows making more effective decisions, which in turn reduces the possibility of risk occurrence. The product of probability and impact determines the importance of risk -its value is an indicator that can be used in the decision-making process.</p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head>Fig. 1 .</head><label>1</label><figDesc>Fig. 1. The basic approaches</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_1"><head>Fig. 2 .</head><label>2</label><figDesc>Fig. 2. Software development process.</figDesc><graphic coords="2,227.28,531.42,145.20,81.66" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_2"><head></head><label></label><figDesc>RfsckA =(RF, PSPEC, EST, EXP | Fest, Frf select, Pspec_select, Flog, P_stop, Prt,Perr,………)Where Prt -the predicate of the decision about the need to create and execute a prototype of profiling .Perr -The predicate of the decision about the need to create and perform a prototype evaluation of accuracy.</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_0"><head></head><label></label><figDesc>Common methodologies include a prototyping, Development (RAD) , Rational Unified Process (RUP) ,waterfall, Most theories attempt to minimize risk by using developing software in little time, called restoration, which typically lasts one week to one month and includes all the tasks necessary " planning, requirements analysis, design, coding, testing, and documentation". Figure<ref type="bibr" target="#b0">(1)</ref> </figDesc><table /></figure>
		</body>
		<back>
			<div type="annex">
<div xmlns="http://www.tei-c.org/ns/1.0" />			</div>
			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<monogr>
		<title level="m" type="main">pseudo-code control of work flows in the design of automated systems</title>
		<author>
			<persName><surname>Sosnin P.I</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2012">2012</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<analytic>
		<title level="a" type="main">simulation programs generation based on decision tables translation technics</title>
		<author>
			<persName><surname>Negoda V.N</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">proceedings of the international conference</title>
				<meeting>the international conference</meeting>
		<imprint>
			<publisher>ulianovsk</publisher>
			<date type="published" when="2001">2001</date>
			<biblScope unit="page" from="92" to="93" />
		</imprint>
	</monogr>
	<note>interactive systems: the problem of iluman-computer interaction</note>
</biblStruct>

<biblStruct xml:id="b2">
	<monogr>
		<author>
			<persName><forename type="first">Khansaa</forename><surname>Azeez</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Obayes</forename><surname>Al-Husseini</surname></persName>
		</author>
		<title level="m">Information security in the field of technical development and information, Interactive Systems: Problems of Human-Computer Interaction Ulyanovsk</title>
				<imprint>
			<publisher>USTU</publisher>
			<date type="published" when="2015">2015</date>
			<biblScope unit="page" from="71" to="80" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<analytic>
		<title level="a" type="main">question-answer processor for cooperative work in human-computer environment</title>
		<author>
			<persName><surname>Sosnin P</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">proceeding the 2 international ieee conference intelligent system</title>
				<meeting>eeding the 2 international ieee conference intelligent system</meeting>
		<imprint>
			<date type="published" when="2004">2004</date>
			<biblScope unit="page" from="452" to="456" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<analytic>
		<title/>
		<author>
			<persName><surname>Allison Robin</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">msf risk management discipline</title>
		<imprint>
			<biblScope unit="volume">1</biblScope>
			<biblScope unit="issue">1</biblScope>
			<date type="published" when="2002">2002</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<analytic>
		<title level="a" type="main">methods and models of adaptation to students in computer training systems</title>
		<author>
			<persName><forename type="first">Lv</forename><surname>Zaitseva</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">educational technology &amp; society</title>
		<imprint>
			<biblScope unit="volume">4</biblScope>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<analytic>
		<title level="a" type="main">development of risk management tools in question-answering based software design environment</title>
		<author>
			<persName><forename type="first">Khansaa</forename><surname>Azeez</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Obayes</forename><surname>Al-Husseini</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Ali</forename><surname>Hamzah Obaid</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">international journal of computer science and mobile computing ijcsmc</title>
		<idno type="ISSN">2320-088x</idno>
		<imprint>
			<biblScope unit="volume">7</biblScope>
			<biblScope unit="issue">6</biblScope>
			<biblScope unit="page" from="165" to="174" />
			<date type="published" when="2018-06">june 2018</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<analytic>
		<title level="a" type="main">tools for conceptual-algorithmic prototyping of project solutions in software intensive systems design</title>
		<author>
			<persName><forename type="first">Ali</forename><surname>Hamzah Obaid</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Khansaa</forename><surname>Azeez</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Obayes</forename><surname>Al-Husseini</surname></persName>
		</author>
		<idno type="DOI">10.5281/zenodo.1491903</idno>
	</analytic>
	<monogr>
		<title level="j">international journal of engineering technologies and management research</title>
		<idno type="ISSN">2454-1907</idno>
		<imprint>
			<biblScope unit="volume">5</biblScope>
			<biblScope unit="issue">10</biblScope>
			<biblScope unit="page" from="117" to="122" />
			<date type="published" when="2018-10">october 2018</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b8">
	<analytic>
		<title level="a" type="main">usage of prototyping in software testing</title>
		<author>
			<persName><forename type="first">Khansaa</forename><surname>Azeez</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Obayes</forename><surname>Al-Husseini</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Ali</forename><surname>Hamzah Obaid</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">multi-knowledge electronic comprehensive journal for education and science publications</title>
		<imprint>
			<biblScope unit="issue">14</biblScope>
			<date type="published" when="2018-11">nov (2018</date>
		</imprint>
	</monogr>
	<note>issue</note>
</biblStruct>

<biblStruct xml:id="b9">
	<monogr>
		<author>
			<persName><forename type="first">Khansaa</forename><surname>Azeez</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Obayes</forename><surname>Al-Husseini</surname></persName>
		</author>
		<title level="m">risk management tools in the design of automated systems . p 287 interactive systems: problems of human-computer interaction</title>
				<imprint>
			<date type="published" when="2017">2017</date>
			<biblScope unit="page">290</biblScope>
		</imprint>
	</monogr>
	<note>ulyanovsk , russia: ustu</note>
</biblStruct>

<biblStruct xml:id="b10">
	<monogr>
		<author>
			<persName><forename type="first">Obaid</forename><surname>Ali Hamzah</surname></persName>
		</author>
		<title level="m">tools for conceptual-algorithmic prototyping in solving design problems in the development of systems with software ,interactive systems: problems of human-computer interaction</title>
				<imprint>
			<date type="published" when="2017">2017</date>
			<biblScope unit="page">290</biblScope>
		</imprint>
	</monogr>
	<note>ulyanovsk , russia: ustu</note>
</biblStruct>

<biblStruct xml:id="b11">
	<monogr>
		<author>
			<persName><surname>Kotov V. Ye</surname></persName>
		</author>
		<title level="m">petri networks .-moscow: nauka</title>
				<imprint>
			<date type="published" when="2013">2013</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b12">
	<monogr>
		<title level="m">kurgan gs, models, methods and technology of differentiated learning on the basis of the internet</title>
				<imprint>
			<date type="published" when="2011">2011</date>
		</imprint>
	</monogr>
	<note>m. williams</note>
</biblStruct>

<biblStruct xml:id="b13">
	<analytic>
		<title level="a" type="main">Information hiding techniques for steganography and digital watermarking</title>
		<author>
			<persName><forename type="first">Ali</forename><surname>Obaid</surname></persName>
		</author>
		<author>
			<persName><surname>Hamzah</surname></persName>
		</author>
		<idno>-306</idno>
	</analytic>
	<monogr>
		<title level="m">INTERACTIVE S&lt;STEMS: Problems of Human-Computer Interaction.-Collection of scientific papers</title>
				<meeting><address><addrLine>Ulyanovsk</addrLine></address></meeting>
		<imprint>
			<publisher>USTU</publisher>
			<date type="published" when="2015">2015. 2015</date>
			<biblScope unit="volume">681</biblScope>
			<biblScope unit="page">63</biblScope>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b14">
	<monogr>
		<author>
			<persName><forename type="first">C</forename><forename type="middle">A</forename><surname>Alexander</surname></persName>
		</author>
		<title level="m">the timeless way of building</title>
				<meeting><address><addrLine>new york</addrLine></address></meeting>
		<imprint>
			<date type="published" when="1979">1979</date>
		</imprint>
	</monogr>
	<note>google scholar</note>
</biblStruct>

<biblStruct xml:id="b15">
	<monogr>
		<title level="m" type="main">software lifecycle models</title>
		<author>
			<persName><surname>Karlm</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2006">2006</date>
			<pubPlace>kth</pubPlace>
		</imprint>
	</monogr>
</biblStruct>

				</listBibl>
			</div>
		</back>
	</text>
</TEI>
