Relevant bibliographies by topics / Software risk management

Contents

  1. Journal articles
  2. Dissertations / Theses
  3. Books
  4. Book chapters
  5. Conference papers
  6. Reports

Academic literature on the topic 'Software risk management'

Author: Grafiati
Published: 4 June 2021
Last updated: 14 March 2023

Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles

Select a source type:

Consult the lists of relevant articles, books, theses, conference reports, and other scholarly sources on the topic 'Software risk management.'

Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.

You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.

Journal articles on the topic "Software risk management"

1

Fairley, R. E. "Software Risk Management." IEEE Software 22, no. 3 (May 2005): 101. http://dx.doi.org/10.1109/ms.2005.77.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Boehm, B. W., and T. DeMarco. "Software risk management." IEEE Software 14, no. 3 (May 1997): 17–19. http://dx.doi.org/10.1109/ms.1997.589225.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Murthi, S. "Preventive risk management software for software projects." IT Professional 4, no. 5 (September 2002): 9–15. http://dx.doi.org/10.1109/mitp.2002.1041172.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Lyytinen, Kalle, Lars Mathiassen, and Janne Ropponen. "A Framework for Software Risk Management." Journal of Information Technology 11, no. 4 (December 1996): 275–85. http://dx.doi.org/10.1177/026839629601100402.

Full text
Abstract:
We present a simple, but powerful framework for software risk management. The framework synthesizes, refines, and extends current approaches to managing software risks. We illustrate its usefulness through an empirical analysis of two software development episodes involving high risks. The framework can be used as an analytical device to evaluate and improve risk management approaches and as a practical tool to shape the attention and guide the actions of risk managers.
APA, Harvard, Vancouver, ISO, and other styles
5

Cui, Wei, Jia Ye, Yan Lin, Si Yu Qian, Yang Liu, Hai Feng Yang, and Ya Jun Li. "Japan Software Project Risk Management." Advanced Materials Research 267 (June 2011): 175–78. http://dx.doi.org/10.4028/www.scientific.net/amr.267.175.

Full text
Abstract:
With the current domestic software outsourcing business with Japan's rise of a large number of outsourcing projects from Japan such as NEC, Hitachi, Toshiba and other large Japanese companies over billing, not only promoted the growth of the domestic economy, but also led to domestic software improve the overall business. In Dalian, the Dalian City party committee and government attach great importance to the development of the software industry, software industry has become the revitalization of old industrial bases to accelerate the economic development of Dalian's one of the important strategies. However, orders easier to do a single hard, if we really want Japan to do a good job outsourcing, is not so simple. How to make the project successful? In the process of the project will encounter those problems? What is the project's impact? These issues will be troubled by the development of each project managers. These are the risks of the project, how to effectively manage the risks, the success of the project is to explore the theme of this article.
APA, Harvard, Vancouver, ISO, and other styles
6

Fairley, R. "Risk management for software projects." IEEE Software 11, no. 3 (May 1994): 57–67. http://dx.doi.org/10.1109/52.281716.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Dedolph, F. Michael. "The neglected management activity: Software risk management." Bell Labs Technical Journal 8, no. 3 (December 9, 2003): 91–95. http://dx.doi.org/10.1002/bltj.10077.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Valério, Karollay Giuliani Oliveira, Carlos Eduardo Sanches da Silva, and Sandra Miranda Neves. "Risk Management in Software Development Projects." International Journal of Open Source Software and Processes 11, no. 1 (January 2020): 1–22. http://dx.doi.org/10.4018/ijossp.2020010101.

Full text
Abstract:
Effective risk management contributes to the success of the software development project. The goal of this work was to identify risk management gaps, perspectives, the evolution of the theme and the study trends, in software development projects, using systematic literature review as a method. For the bibliometric analysis, articles referring to the topic were selected in the period from 2010 to 2018. As tools of analysis, Citespace and VOS Viewer software were used, allowing a comparative evaluation between the articles, as well as the analysis of clusters. Beyond content analysis of articles found. Gaps were identified for performance; team involvement; attention to failures; identification of tools for decision-making; and business strategy. In turn, perspectives were determined for research trends, such as the close relationship between business strategy, risk management and new management models. The research can propose new strategies and perspectives for risk management in software development and show their importance to the academic and practical spheres, demonstrating that the themes are complementary and important in the current technological and innovation sector.
APA, Harvard, Vancouver, ISO, and other styles
9

Soni, Dr Rachna. "Potential Factors for Software Risk Management." International Journal for Research in Applied Science and Engineering Technology 6, no. 4 (April 30, 2018): 3227–31. http://dx.doi.org/10.22214/ijraset.2018.4537.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Lyytinen, Kalle, Lars Mathiassen, and Janne Ropponen. "A Framework for software risk management." Journal of Information Technology 11, no. 4 (December 1996): 275–85. http://dx.doi.org/10.1057/jit.1996.2.

Full text
APA, Harvard, Vancouver, ISO, and other styles
More sources

Dissertations / Theses on the topic "Software risk management"

1

Fontoura, Lisandra Manzoni. "PRiMA : project risk management approach." reponame:Biblioteca Digital de Teses e Dissertações da UFRGS, 2006. http://hdl.handle.net/10183/6947.

Full text
Abstract:
Esta tese propõe uma abordagem sistemática para gerenciar riscos em projetos de software, por meio da adaptação de processos. O objetivo da abordagem é permitir a elaboração de um processo específico para um dado projeto, visando minimizar a exposição do projeto aos riscos, identificados de acordo com o contexto do projeto. As atividades, possíveis de serem executadas em processos de projetos de uma organização, são estruturadas em um framework de processo (PRiMA-F), que inclui também os padrões de processo e organizacionais usados para descrever ações preventivas e corretivas aos riscos. A estruturação do framework básico, construído pela organização, poderá permitir distintas instanciações, como por exemplo, processos de acordo com o paradigma ágil ou planejado, ou em conformidade com normas de qualidade, como CMM e outras; além dos padrões organizacionais e de processo para gestão de riscos de projeto. PRiMA-F define o escopo maior do processo de software da organização e este é adaptado de acordo com os riscos identificados para o projeto e suas necessidades específicas, dando origem ao processo a ser usado no projeto. adaptação. Os guias descrevem como adaptar elementos de processo de acordo com o tamanho e o formalismo do projeto. Configurações de processo são modelos prédefinidos, visando atender projetos típicos ou modelos de qualidade. Prima-F pode ser estendida para novos riscos, padrões e processos, de acordo com as necessidades da organização. Utilizando o paradigma Goal/Question/Metric, no framework de processo (PRiMAF), são definidas métricas do processo de software, associadas aos riscos, para serem usadas para acompanhar o progresso dos fatores de risco, possibilitando ao gerente de projeto tomar ações corretivas, quando necessário e no momento adequado. As ações corretivas são descritas usando padrões organizacionais e de processo. Uma ferramenta de apoio à sistemática proposta (PRiMA-Tool) foi desenvolvida. Estudos de caso foram elaborados para validar a sistemática proposta
APA, Harvard, Vancouver, ISO, and other styles
2

Greer, Desmond. "Software engineering risk : understanding and management." Thesis, University of Ulster, 2000. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.326127.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Gabriš, Ondrej. "Software Projects Risk Management Support Tool." Master's thesis, Vysoké učení technické v Brně. Fakulta informačních technologií, 2011. http://www.nusl.cz/ntk/nusl-412827.

Full text
Abstract:
Management projektů a jejich rizik je v současnosti rozvíjející se disciplína, která si získává stále větší pozornost a uplatnění v praxi. Tato práce popisuje úvod do problematiky řízení rizik, zkoumání metod jejich identifikace, vyhodnocení a managementu, předcházení jejich následkům a jejich zvládání. V další části práce byla provedena analýza vzorků rizik z reálných projektů, byly popsány metody pro identifikaci a vyhodnocení následků rizik v úvodních fázích softwarového projektu, taktéž byly popsány atributy rizik a navržen způsob jejich dokumentace. V závěrečné části zadání byl navržen a implementován prototyp modelové aplikace pro podporu managementu rizik softwarových projektů.
APA, Harvard, Vancouver, ISO, and other styles
4

Crosby, Dave. "Project risk management in smaller software teams." Click here to access this resource online, 2007. http://hdl.handle.net/10292/378.

Full text
Abstract:
This thesis investigates project risk management issues in smaller software teams. Certain gaps in the literature are identified. There is limited literature on what risk management techniques software practitioners use. The studies that are published tend to focus on large software teams. This thesis investigates what risks these smaller teams consider to be important. It also investigates what techniques are perceived to address these risks and how effective those techniques are considered to be. One of those risks is found to be of primary importance, yet this risk is not suggested by the project management literature. This thesis goes on to conduct a more in-depth exploration of that specific risk in the context of these smaller teams Interviews were selected as the most appropriate method to achieve the objectives of the thesis. Nineteen interviews in eight software organisations are conducted to collect data for this thesis. Three different perspectives on project risk were investigated. Those were the perspectives of the; service managers, project managers and developers. Hence a large store of rich information is collated. The results are analysed and a rich set of information is presented in this thesis. As a result of this research it is suggested that smaller software teams may find it useful to consider the 16 risks discussed in this research and how applicable those risks are to their individual organisation. Service managers may need to do more to raise the awareness of the importance of risks associated with ‘customer relationship issues’ within their own organisations. Three risks stood out as areas where future research might be most fruitful. They were; customer relationship issues, introduction of new technology and unrealistic schedules and budgets. Risks related to customer relationship issues were of particular significance and have tended to be over looked in the project management literature. It is submitted that research into standard project risk management approaches may need to be combined with business risk management approaches to gain a full understanding of the risks faced and addressed by these smaller teams.
APA, Harvard, Vancouver, ISO, and other styles
5

Chiste, Brandão Ana Beatriz. "Risk Management in Software projectsusing Scrum framework." Thesis, KTH, Tillämpad maskinteknik (KTH Södertälje), 2013. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-122857.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

JUNIOR, JOSE LUIS COUTO LYRA. "SOFTWARE IMPLEMENTATION FOR OPERATIONAL RISK MANAGEMENT SUPPORT." PONTIFÍCIA UNIVERSIDADE CATÓLICA DO RIO DE JANEIRO, 2005. http://www.maxwell.vrac.puc-rio.br/Busca_etds.php?strSecao=resultado&nrSeq=7631@1.

Full text
Abstract:
PONTIFÍCIA UNIVERSIDADE CATÓLICA DO RIO DE JANEIRO
O gerenciamento de risco em instituições bancárias, mais do que mera imposição das agências reguladoras distingue-se como fator de sucesso na melhoria dos processos, aumentando o resultado financeiro. Após o Acordo da Basiléia, a gerência de riscos de mercado e de crédito, cuja atuação se dá sobre as receitas, passou a ser realizada. Entretanto, alguns riscos atuam sobre as despesas, destacando-se o operacional, que é o risco de perdas oriundas de problemas com controles internos, sistemas, pessoas e eventos externos. O objetivo deste trabalho foi elaborar uma revisão abrangente da literatura e um protótipo de sistema computacional que permite medir o VaR do risco operacional de uma unidade de risco, utilizando o Modelo de Distribuição de Perdas (LDA), e aplicar modelos causais que expliquem estas perdas. Este protótipo é uma aplicação Internet/intranet desenvolvida na linguagem ASP e utilizou o MS-Access como banco de dados. Para os cálculos estatísticos, implementou-se uma interface de comunicação aplicação/MATLAB. A revisão da literatura objetivou a familiarização com conceitos básicos de risco operacional descritos pelo Comitê da Basiléia. Adicionalmente, apresentou detalhes técnicos para implementação do LDA, tais como Distribuição de Freqüência e de Severidade, métodos para determinação da distribuição de perdas operacionais e construção da base de dados de perdas. Independente das particularidades institucionais, esse protótipo permite a visualização das providências estratégicas e operacionais a serem tomadas para implementação e implantação de um sistema similar. Marca um ponto de partida para o desenvolvimento de um produto abrangente de gerenciamento de risco operacional nas mais variadas instituições e segmentos de mercado.
The risk management in financial institutions, more than just an imposition of the regulatory agencies, represents a success factor in the processes enhancement, elevating the financial results. After Basel Accord, credit and market risks management, which acts over earnings, were implemented. However, some risks are associated to the expenses, such as the operational risk, related to the losses from internal control, systems, human and external events problems. The aim of the present study was the elaboration of an extensive literature review and the development of a computation system prototype able to measure the operational risk VaR of a risk unit, using the Loss Distribution Approach (LDA) and to apply causal models that explain these losses. This prototype is an Internet/intranet application developed in ASP language, using MS-Access as database. For statistical evaluation, an interface between the application and MATLAB was implemented. The literature review pretended to give a better understanding of the basic concepts of operational risk described by the Basel Committee. In addition, it presented technical details for LDA implementation, such as Frequency and Severity Distribution, methods for the distribution of the operational losses determination and losses database construction. Independent of institutional peculiarities, this prototype allows the observation of strategic and operational providences to be taken for implementation and implantation of a similar system. It determines a startingpoint in the development of an operational risk management product valuable in several institutions and market segments.
APA, Harvard, Vancouver, ISO, and other styles
7

Yakin, Cenkler. "Quantifying Risk Management Process In A Software Organization." Master's thesis, METU, 2006. http://etd.lib.metu.edu.tr/upload/12607138/index.pdf.

Full text
Abstract:
This study presents a quantifying risk management process and its application on a software organization in terms of risk items mitigated, exposures covered, costs, and expected exposures covered. Risk management is defined as setting forth a discipline and environment of proactive decisions and actions to assess continuously what can go wrong (risks), to determine what risks are important to deal with, and to implement strategies to deal with those risks. Risk management can be applied in all of the business areas. In the literature, there are sources for risk management. Some of them are qualitative, and some of them are quantitative. However, there is no much source about the application study of a quantifying risk management process on a software organization. In order to obtain insight about this issue, this study presents a quantifying risk management system to the literature and also compares the quantifying risk management policies on the data set of a software organization by finding out and analyzing their performance with respect to designated decision parameters and preference profiles for risk items mitigated, exposures covered, costs, and expected exposures covered. At the end of this study, suitable quantifying risk management policies for each profile are recommended by considering the analysis of the data set as base.
APA, Harvard, Vancouver, ISO, and other styles
8

Nilsson, Peter, and Erik Ohlsson. "Categorisation and formulation in risk management : Essential parts of a future Experience based Risk Management model within software engineering." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik och datavetenskap, 2003. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-1727.

Full text
Abstract:
This software engineering thesis addresses three main issues. When creating the risk documents for this master thesis project, we became even more aware of the problems with categorization and formulation of risk statements and the scope is now focusing on categorization and formulation as a necessity for Experience based Risk Management (EbRM). The EbRM process is the foundation of the thesis and the categorisation and formulation parts had to be solved before implementing the EbRM model. To give the reader a notion about the background of this work, a brief introduction to the Experience based Risk Management model is given in the thesis. The thesis is based on literature studies, experiences and experiments. The formulation system is gathered from the Software Engineering Institute (SEI) and is called the CTC-format (Condition, Transition, Consequence). This format allows you to separate conditions and consequence of the risk and thereby provides you with easier categorisation and understandability. The categorisation system used is the SEI Taxonomy Based Categorisation (TBC). A categorisation system built as a search tree where each leaf represents a rather narrow risk domain. In order to evaluate those two different systems we performed an experiment showing that the combination thereof gave a much higher match in sorting risks between different groups. The conclusions of this work are that the TBC in connection with the CTC structure forms a very good basis for risk management when it comes to categorisation and formulation. In addition to properly formulated and tagged names and a thorough process when identifying and documenting risks, the risk management will be facilitated by using our conclusions in further risk management. Oral information must as well be on a sufficient level to gain full benefits from a risk management process.
APA, Harvard, Vancouver, ISO, and other styles
9

Burd, Elizabeth L. "Reuse with risk management : a decision support approach." Thesis, University of York, 1999. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.247526.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Olagbemiro, Albert O. "Application of Real Options theory to software engineering for strategic decision making in software related capital investments." Monterey, Calif. : Naval Postgraduate School, 2008. http://edocs.nps.edu/npspubs/scholarly/dissert/2008/Dec/08Dec%5FOlagbemiro_PhD.pdf.

Full text
Abstract:
Dissertation (Ph.D. in Software Engineering)--Naval Postgraduate School, December 2008.
Dissertation Supervisor(s): Shing, Man-Tak ; Mun, Jonathan. "December 2008." Description based on title screen as viewed on January 29, 2009. Includes bibliographical references (p. 175-181). Also available in print.
APA, Harvard, Vancouver, ISO, and other styles
More sources

Books on the topic "Software risk management"

1

W, Boehm Barry, ed. Software risk management. Washington, D.C: IEEE Computer Society Press, 1989.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
2

Software risk management. Los Alamitos, Calif: IEEE Computer Society Press, 1996.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
3

Pandian, C. Ravindranath. Applied Software Risk Management. London: Taylor and Francis, 2006.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
4

Coleman, Michael, 1946 May 12- and Absolon Peter 1948-, eds. Risk management for software projects. London: McGraw-Hill Book Co., 1994.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
5

Moran, Alan. Agile risk management. New York: Springer, 2014.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
6

Sherer, Susan A. Software failure risk: Measurement and management. New York: Plenum Press, 1992.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
7

Risk management in software development projects. Burlington, MA: Elsevier Butterworth-Heinemann, 2004.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
8

Greer, Desmond. Software engineering risk: Understanding and management. [S.l: The Author], 2000.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
9

Charette, Robert N. Software engineering risk analysis and management. New York: Intertext Publications, 1989.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
10

Sherer, Susan A. Software Failure Risk: Measurement and Management. Boston, MA: Springer US, 1992.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
More sources

Book chapters on the topic "Software risk management"

1

Rose, Robert. "Risk Management." In Software Development Activity Cycles, 149–65. Berkeley, CA: Apress, 2022. http://dx.doi.org/10.1007/978-1-4842-8239-7_8.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Boehm, Barry. "Software risk management." In Lecture Notes in Computer Science, 1–19. Berlin, Heidelberg: Springer Berlin Heidelberg, 1989. http://dx.doi.org/10.1007/3-540-51635-2_29.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Moran, Alan. "Agile Software Development." In Agile Risk Management, 1–16. Cham: Springer International Publishing, 2014. http://dx.doi.org/10.1007/978-3-319-05008-9_1.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Sherer, Susan A. "Risk Analysis and Management." In Software Failure Risk, 13–24. Boston, MA: Springer US, 1992. http://dx.doi.org/10.1007/978-1-4615-3020-6_2.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Gorrod, Martin. "The software development lifecycle." In Risk Management Systems, 93–120. London: Palgrave Macmillan UK, 2004. http://dx.doi.org/10.1057/9780230510296_4.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Solozhentsev, E. D. "Software for Risks Management Technologies." In Risk Management Technologies, 93–101. Dordrecht: Springer Netherlands, 2012. http://dx.doi.org/10.1007/978-94-007-4288-8_8.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Liu, Sifeng, Yingjie Yang, and Jeffrey Forrest. "Introduction to Grey Systems Modeling Software." In Computational Risk Management, 285–99. Singapore: Springer Singapore, 2016. http://dx.doi.org/10.1007/978-981-10-1841-1_12.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Cairó, Osvaldo, Julio Barreiro, and Francisco Solsona. "Software Methodologies at Risk." In Knowledge Acquisition, Modeling and Management, 323–28. Berlin, Heidelberg: Springer Berlin Heidelberg, 1999. http://dx.doi.org/10.1007/3-540-48775-1_21.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Apine, Baiba. "Software Development Risk Management Survey." In Information Systems Development, 241–51. Boston, MA: Springer US, 2002. http://dx.doi.org/10.1007/978-1-4615-0167-1_22.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Chittister, Clyde G., and Yacov Y. Haimes. "Risk Management for Software Engineering." In Encyclopedia of Operations Research and Management Science, 1335–45. Boston, MA: Springer US, 2013. http://dx.doi.org/10.1007/978-1-4419-1153-7_899.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Conference papers on the topic "Software risk management"

1

Avdoshin, Sergey M., and Elena Y. Pesotskaya. "Software risk management." In 2011 7th Central and Eastern European Software Engineering Conference in Russia (CEE-SECR 2011). IEEE, 2011. http://dx.doi.org/10.1109/cee-secr.2011.6188471.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Zardari, Shehnila. "Software Risk Management." In 2009 International Conference on Information Management and Engineering. IEEE, 2009. http://dx.doi.org/10.1109/icime.2009.138.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Wang Can, Hou Hongfeng, Xu Chunming, and Zeng Weijia. "Risk management in software project management." In 2012 4th Electronic System-Integration Technology Conference (ESTC). IEEE, 2012. http://dx.doi.org/10.1109/estc.2012.6485832.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Alexe, Catalina monica, Catalin george Alexe, Mirona ana maria Popescu, and Sorina Costinas. "SOFTWARE SOLUTIONS FOR RISK MANAGEMENT WITHIN ORGANIZATIONS." In eLSE 2020. University Publishing House, 2020. http://dx.doi.org/10.12753/2066-026x-20-057.

Full text
Abstract:
Regardless of the size and type of the organization, absolutely all the organizations face business risks that they must identify, evaluate, treat and manage them as best as they can. Nowadays, every business is based, more or less, on technology. Compared to other companies, high technology organizations have a greater capacity for innovation, greater technological efficiency and, consequently, high exposure to the risks related to the technology. In increasingly dynamic and complex business environments, the software solutions of risk management address a number of challenges related to how to identify and assess risks that are constantly changing. In the present paper we will conduct a research regarding the identification of the most suitable software solutions for risk management within organizations, taking into account several variables, including: the industry to which it is addressed, the size of the organization, the stages of the risk management process, the costs involved and so on. Such software solutions for risk management in organizations can support aspects such as: process analysis, integration with the existing collaboration tools within the company, data consolidation; quantifying risks, creating links between losses and risks, researching risks; quantitative and qualitative assessment of the risks; testing, acting, carrying out the risk reduction plan; sensitivity analysis, application of dashboards to track loss values and their influence on key performance indicators of the organization. The paper is of interest to managers, entrepreneurs and all those who want to find out how they can select the most appropriate software solutions needed for risk management within organizations.
APA, Harvard, Vancouver, ISO, and other styles
5

Islam, Shareeful. "Software development risk management model." In the doctoral symposium for ESEC/FSE. New York, New York, USA: ACM Press, 2009. http://dx.doi.org/10.1145/1595782.1595785.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Kontio, Jyrki. "Risk management in software development." In the 21st international conference. New York, New York, USA: ACM Press, 1999. http://dx.doi.org/10.1145/302405.302954.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Lee, Sang-Young. "Design of Risk Management Process for Concurrent." In Software 2013. Science & Engineering Research Support soCiety, 2013. http://dx.doi.org/10.14257/astl.2013.35.04.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Lobato, Luanna, and Thiago Bittar. "A Risk Management Approach for Software Product Line Engineering." In XI Simpósio Brasileiro de Sistemas de Informação. Sociedade Brasileira de Computação, 2015. http://dx.doi.org/10.5753/sbsi.2015.5834.

Full text
Abstract:
Software Product Line (SPL) Engineering is a software development paradigm that fosters systematic reuse. It is focused on improving software practices, leading companies to experience benefits, such as reduced time-to-market and effort, and higher quality for the products delivered to customers. However, establishing a SPL is neither a simple nor a cheap task, and may affect several aspects of a software company. Besides, it involves a range of risks that may hinder project success. These have to be managed accordingly, so as to minimize the likelihood of project failure. Despite the importance of Risk Management (RM) for SPL Engineering, little has been published in terms of suitable and structured practices to cope with that. This present paper reports an approach for RM in SPL Engineering, named RiPLERM (Rise Product Line Engineering – Risk Management). The approach presents activities to structure RM in SPL projects, The design of the RiPLE-RM approach elaborated on results from empirical investigations, and was proposed to facilitate the management and provide significant insights that can be used to avoid and solve risks.
APA, Harvard, Vancouver, ISO, and other styles
9

Mudumba, V., and One-Ki Lee. "A New Perspective on GDSD Risk Management: Agile Risk Management." In 2010 Fifth IEEE International Conference Global Software Engineering (ICGSE 2010). IEEE, 2010. http://dx.doi.org/10.1109/icgse.2010.33.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Machado, Valeska, Paulo Afonso, and Heitor Costa. "Risk Catalogs in Software Project Management." In 2019 XLV Latin American Computing Conference (CLEI). IEEE, 2019. http://dx.doi.org/10.1109/clei47609.2019.9089044.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Reports on the topic "Software risk management"

1

Gallagher, Brian P. Software Acquisition Risk Management Key Process Area (KPA)- A Guidebook Version 1.02. Fort Belvoir, VA: Defense Technical Information Center, October 1999. http://dx.doi.org/10.21236/ada370385.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Gallagher, Brian P., Christopher J. Alberts, and Richard E. Barbour. Software Acquisition Risk Management Key Process Area (KPA) - A Guidebook Version 1.0. Fort Belvoir, VA: Defense Technical Information Center, August 1997. http://dx.doi.org/10.21236/ada328098.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

SCHAEFER, J. C. Software requirements specification for the program analysis and control system risk management module. Office of Scientific and Technical Information (OSTI), June 1999. http://dx.doi.org/10.2172/782400.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Tripathi, Poonam, Manish Shrestha, Deepak Kumar Shah, and Kiran Shakya. Using Earth observation and geospatial applications for disaster preparednessv - training manual. International Centre for Integrated Mountain Development (ICIMOD), February 2023. http://dx.doi.org/10.53055/icimod.1021.

Full text
Abstract:
This manual has been prepared for use by the disaster management community. It introduces remote sensing and geospatial concepts, ICIMOD’s science applications and their applications in disaster preparedness. The manual’s contents were used in training sessions on using Earth observation and geospatial applications for disaster preparedness in Nepal. It provides a step-by-step guide to using free and open-source geospatial software, remote sensing data, and ICIMOD’s science applications for preparedness, management, and risk reduction of disasters. It uses examples and sample datasets from Nepal.
APA, Harvard, Vancouver, ISO, and other styles
5

Wayant, Nicole. Adapting agile philosophies and tools for a research environment. Engineer Research and Development Center (U.S.), September 2022. http://dx.doi.org/10.21079/11681/45442.

Full text
Abstract:
There exist myriad project management methodologies, but none is focused solely on scientific research. Research projects are unique compared to other types of projects, including software development, manufacturing, and drug trials; research projects inherently have unplanned risks. These risks provide a challenge to managing resources, developing schedules, and providing team ownership while still achieving project goals. To help mitigate the risks and the challenges associated with scientific research, a methodology to manage research projects needs to be developed.
APA, Harvard, Vancouver, ISO, and other styles
6

Shabelnyk, Tetiana V., Serhii V. Krivenko, Nataliia Yu Rotanova, Oksana F. Diachenko, Iryna B. Tymofieieva, and Arnold E. Kiv. Integration of chatbots into the system of professional training of Masters. [б. в.], June 2021. http://dx.doi.org/10.31812/123456789/4439.

Full text
Abstract:
The article presents and describes innovative technologies of training in the professional training of Masters. For high-quality training of students of technical specialties, it becomes necessary to rethink the purpose, results of studying and means of teaching professional disciplines in modern educational conditions. The experience of implementing the chatbot tool in teaching the discipline “Mathematical modeling of socio-economic systems” in the educational and professional program 124 System Analysis is described. The characteristics of the generalized structure of the chatbot information system for investment analysis are presented and given: input information, information processing system, output information, which creates a closed cycle (system) of direct and feedback interaction. The information processing system is represented by accounting and analytical data management blocks. The investment analysis chatbot will help masters of the specialty system analysis to manage the investment process efficiently based on making the right decisions, understanding investment analysis in the extensive structure of financial management and optimizing risks in these systems using a working mobile application. Also, the chatbot will allow you to systematically assess the disadvantages and advantages of investment projects or the direction of activity of a system analyst, while increasing interest in performing practical tasks. A set of software for developing a chatbot integrated into training is installed: Kotlin programming, a library for network interaction Retrofit, receiving and transmitting data, linking processes using the HTTP API. Based on the results of the study, it is noted that the impact of integrating a chatbot into the training of Masters ensures the development of their professional activities, which gives them the opportunity to be competent specialists and contributes to the organization of high-quality training.
APA, Harvard, Vancouver, ISO, and other styles
You might also be interested in the extended bibliographies on the topic 'Software risk management' for particular source types:
Journal articles Dissertations / Theses Books
We offer discounts on all premium plans for authors whose works are included in thematic literature selections. Contact us to get a unique promo code!

To the bibliography