<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="static/style.xsl"?><OAI-PMH xmlns="http://www.openarchives.org/OAI/2.0/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/ http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd"><responseDate>2026-05-14T06:44:27Z</responseDate><request verb="GetRecord" identifier="oai:riubu.ubu.es:10259/10022" metadataPrefix="etdms">https://riubu.ubu.es/oai/request</request><GetRecord><record><header><identifier>oai:riubu.ubu.es:10259/10022</identifier><datestamp>2025-01-24T01:05:43Z</datestamp><setSpec>com_10259_4386</setSpec><setSpec>com_10259_5086</setSpec><setSpec>com_10259_2604</setSpec><setSpec>col_10259_4387</setSpec></header><metadata><thesis xmlns="http://www.ndltd.org/standards/metadata/etdms/1.0/" xmlns:doc="http://www.lyncode.com/xoai" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.ndltd.org/standards/metadata/etdms/1.0/ http://www.ndltd.org/standards/metadata/etdms/1.0/etdms.xsd">
<title>Diagnosis of Software Projects Based on the Viable System Model</title>
<creator>Puche Regaliza, Julio César</creator>
<creator>Jiménez Palmero, Alfredo</creator>
<creator>Arranz Val, Pablo</creator>
<subject>Software project</subject>
<subject>Structural diagnosis</subject>
<subject>Cybernetics</subject>
<subject>Organizational cybernetics</subject>
<subject>Viable system model</subject>
<subject>Organizational change management</subject>
<description>This work aims to identify the shortcomings that may impair or endanger the viability of software&#xd;
projects, and attemps to reduce their failure rates. A diagnosis based on the Viable System Model&#xd;
of software projects is shown. The data collection processes necessary to make a diagnosis have&#xd;
been carried out through a questionnaire and personal interviews with 38 companies in the&#xd;
Information and Communications Technology (ICT) sector. The subsequent descriptive analysis&#xd;
allows us to detect 8 weak points in the organizational structure of the software projects. We&#xd;
highlight two of the 8 weak points in particular: the nondefinition of the next lower level of&#xd;
recursion and the need to improve the exploration mechanisms used to evaluate future scenarios.&#xd;
Although the sample seems small, a great effort was expended to interview the 38 companies due&#xd;
to an extension of the interview time (approximately 75 min) and the confidentiality and&#xd;
complexity of the topic, which required gathering a high level of detail and in-depth information&#xd;
on each of the projects and companies in the survey. This work offers managers a detailed&#xd;
reference for the diagnosis or design of viable software projects. The novel aspect of the work&#xd;
focuses on the application of the Viable System Model for proposing organizational changes in&#xd;
the development of software projects. This holistic perspective of the organizational structure of&#xd;
software projects will allow an increase in their success rate.</description>
<date>2025-01-23</date>
<date>2025-01-23</date>
<date>2019-05</date>
<type>info:eu-repo/semantics/article</type>
<identifier>1094-429X</identifier>
<identifier>http://hdl.handle.net/10259/10022</identifier>
<identifier>10.1007/s11213-019-09491-y</identifier>
<identifier>1573-9295</identifier>
<language>eng</language>
<relation>Systemic Practice and Action Research. 2019, V. 33, n. 2, p. 215-236</relation>
<relation>https://doi.org/10.1007/s11213-019-09491-y</relation>
<rights>info:eu-repo/semantics/openAccess</rights>
<publisher>Springer</publisher>
</thesis></metadata></record></GetRecord></OAI-PMH>