Bibliographies thématiques / Software risk mitigation

Littérature scientifique sur le sujet « Software risk mitigation »

Auteur : Grafiati
Publié le 14 mars 2023

Créez une référence correcte selon les styles APA, MLA, Chicago, Harvard et plusieurs autres

Choisissez une source :

Sommaire

Consultez les listes thématiques d’articles de revues, de livres, de thèses, de rapports de conférences et d’autres sources académiques sur le sujet « Software risk mitigation ».

À côté de chaque source dans la liste de références il y a un bouton « Ajouter à la bibliographie ». Cliquez sur ce bouton, et nous générerons automatiquement la référence bibliographique pour la source choisie selon votre style de citation préféré : APA, MLA, Harvard, Vancouver, Chicago, etc.

Vous pouvez aussi télécharger le texte intégral de la publication scolaire au format pdf et consulter son résumé en ligne lorsque ces informations sont inclues dans les métadonnées.

Articles de revues sur le sujet "Software risk mitigation"

1

Mittal, Sonam. « Risk Analysis and Mitigation Steps in Different Phases of Software Development ». International Journal of Scientific Research 2, no 6 (1 juin 2012) : 241–43. http://dx.doi.org/10.15373/22778179/june2013/77.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
2

Rahman, Tania, Shanto Kumar Saha, Md Sajjadur Rahman Sohel, Md Tamim Maula, Abhijit Bowmik et Rashidul Hasan Nabil. « Risk Identification and Analysis in Software Development in Bangladesh IT Industry : A Hybrid Model ». AIUB Journal of Science and Engineering (AJSE) 21, no 1 (12 mai 2022) : 37–44. http://dx.doi.org/10.53799/ajse.v21i1.308.

Texte intégral
Résumé :
Software risk management is a critical and multi-stage process. All over the world, IT Industries face some threats during software risk management processes. Bangladesh is not exceptional. Our principal goal is to manage risk for Bangladesh's IT Industry. To gain a clear and transparent idea survey is the most effective way. And so, we arranged a survey questionnaire and collected data for risk impact areas on Bangladesh IT Industry. A workable and feasible risk management approach prompts an idea for the risk-mitigating plan. In any case, the high proportion of IT project failures demonstrates the futility of risk mitigation activities. From the survey, it is discovered that the most irritating obstructions behind software disappointment for the presence of covered-up and inconspicuous risks and lack of user communication, and lack of proper training on new technology which is overlooked in the greater part of the models. The proposed model works with the improvement of the risk mitigation plan through four phases, the DVC committee, and the NUT train-up team. Depending upon the survey replies added another unique feature called the NUT train-up team. The model considered all four phases of risk management, with the mitigation phase and training on new technologies receiving the greatest attention.
Styles APA, Harvard, Vancouver, ISO, etc.
3

Verner, J. M., O. P. Brereton, B. A. Kitchenham, M. Turner et M. Niazi. « Risks and risk mitigation in global software development : A tertiary study ». Information and Software Technology 56, no 1 (janvier 2014) : 54–78. http://dx.doi.org/10.1016/j.infsof.2013.06.005.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
4

., S. Rehman. « SOFTWARE SECURITY RISK MITIGATION USING OBJECT ORIENTED DESIGN PATTERNS ». International Journal of Research in Engineering and Technology 02, no 07 (25 juillet 2013) : 71–89. http://dx.doi.org/10.15623/ijret.2013.0207010.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
5

Frydman, Maxime, Guifré Ruiz, Elisa Heymann, Eduardo César et Barton P. Miller. « Automating Risk Analysis of Software Design Models ». Scientific World Journal 2014 (2014) : 1–12. http://dx.doi.org/10.1155/2014/805856.

Texte intégral
Résumé :
The growth of the internet and networked systems has exposed software to an increased amount of security threats. One of the responses from software developers to these threats is the introduction of security activities in the software development lifecycle. This paper describes an approach to reduce the need for costly human expertise to perform risk analysis in software, which is common in secure development methodologies, by automating threat modeling. Reducing the dependency on security experts aims at reducing the cost of secure development by allowing non-security-aware developers to apply secure development with little to no additional cost, making secure development more accessible. To automate threat modeling two data structures are introduced, identification trees and mitigation trees, to identify threats in software designs and advise mitigation techniques, while taking into account specification requirements and cost concerns. These are the components of our model for automated threat modeling, AutSEC. We validated AutSEC by implementing it in a tool based on data flow diagrams, from the Microsoft security development methodology, and applying it to VOMS, a grid middleware component, to evaluate our model's performance.
Styles APA, Harvard, Vancouver, ISO, etc.
6

Taylor, David, Derek Williamson, Harprit Kaur, Kevin Macintosh, Leo Brewster et Ramon Roach. « BARBADOS NATIONAL COASTAL RISK INFORMATION AND PLANNING PLATFORM A SOFTWARE SYSTEM FOR HAZARDS, VULNERABILITY & ; RISK ». Coastal Engineering Proceedings, no 36 (30 décembre 2018) : 55. http://dx.doi.org/10.9753/icce.v36.risk.55.

Texte intégral
Résumé :
The Barbados National Coastal Risk Information and Planning Platform (NCRIPP) is a study nearing completion to quantify coastal risk and develop a software system to serve this information country-wide. The NCRIPP follows extensive coastal baseline studies and includes assessment of eight hazards, vulnerability assessment and finally a risk assessment. The software platform is a cloud-based system that includes a large catalogue of assets, hazard overlays, and the ability to calculate damages , and mitigation alternatives.
Styles APA, Harvard, Vancouver, ISO, etc.
7

Marx, Ben, et Deon Oosthuizen. « Risk assessment and mitigation at the information technology companies ». Risk Governance and Control : Financial Markets and Institutions 6, no 2 (2016) : 44–51. http://dx.doi.org/10.22495/rcgv6i2art6.

Texte intégral
Résumé :
Developing computer software that is free from material defects is the ultimate goal for software developers; however, due to the cost and complexity of software development, it is a goal that is unlikely to be achieved. As a consequence of the inevitable defects that manifest within computer software, the task of software patch management becomes a key focus area for software companies, IT departments, and even end users. Audit departments, as part of their responsibilities, are required to provide assurance on the patching process and therefore need to understand the various decision-making factors. Software flaws that exist within computer systems may put confidential information at risk and may also compromise the availability of such systems. The study investigated the recommended approaches for the task of software patching, with a view to balancing the sometimes conflicting requirements of security and system availability. The study found that there are a number of key aspects that are required to ensure a successful patching process and that the internal auditors of the ‘big four’ South African banks considered most of these factors to be important.
Styles APA, Harvard, Vancouver, ISO, etc.
8

Yan, Shujie, Liangzhu (Leon) Wang, Michael J. Birnkrant, Zhiqiang (John) Zhai et Shelly L. Miller. « Multizone Modeling of Airborne SARS-CoV-2 Quanta Transmission and Infection Mitigation Strategies in Office, Hotel, Retail, and School Buildings ». Buildings 13, no 1 (31 décembre 2022) : 102. http://dx.doi.org/10.3390/buildings13010102.

Texte intégral
Résumé :
Airborne transmission of SARS-CoV-2 mostly occurs indoors, and effective mitigation strategies for specific building types are needed. Most guidance provided during the pandemic focused on general strategies that may not be applicable for all buildings. A systematic evaluation of infection risk mitigation strategies for different public and commercial buildings would facilitate their reopening process as well as post-pandemic operation. This study evaluates engineering mitigation strategies for five selected US Department of Energy prototype commercial buildings (i.e., Medium Office, Large Office, Small Hotel, Stand-Alone Retail, and Secondary School). The evaluation applied the multizone airflow and contaminant simulation software, CONTAM, with a newly developed CONTAM-quanta approach for infection risk assessment. The zone-to-zone quanta transmission and quanta fate were analyzed. The effectiveness of mechanical ventilation, and in-duct and in-room air treatment mitigation strategies were evaluated and compared. The efficacy of mitigation strategies was evaluated for full, 75%, 50% and 25% of design occupancy of these buildings under no-mask and mask-wearing conditions. Results suggested that for small spaces, in-duct air treatment would be insufficient for mitigating infection risks and additional in-room treatment devices would be needed. To avoid assessing mitigation strategies by simulating every building configuration, correlations of individual infection risk as a function of building mitigation parameters were developed upon extensive parametric studies.
Styles APA, Harvard, Vancouver, ISO, etc.
9

Biro, Miklos, Atif Mashkoor, Johannes Sametinger et Remzi Seker. « Software Safety and Security Risk Mitigation in Cyber-physical Systems ». IEEE Software 35, no 1 (janvier 2018) : 24–29. http://dx.doi.org/10.1109/ms.2017.4541050.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
10

Hasni, Mohamed S. M., et Turhan Köprübaşı. « Controlling Task Dependency as a Risk Mitigation Process ». International Journal of Emerging Research in Management and Technology 6, no 11 (13 juin 2018) : 19. http://dx.doi.org/10.23956/ijermt.v6i11.42.

Texte intégral
Résumé :
The construction of highly reliable software projects requires that these projects meet the objectives for which they have been set, and therefore failure to meet any of these objectives and needs will make the software project prone to failure. Thus, ignoring strong needs and not including users adequately especially in identifying their needs and tracking their dependencies clearly can be considered one of the main risks of failure. In this paper, we present a systematic approach to addressing this phenomenon and its mitigation mechanism.
Styles APA, Harvard, Vancouver, ISO, etc.
Plus de sources

Thèses sur le sujet "Software risk mitigation"

1

Rode, Karl. « Using risk mitigation approaches to define the requirements for software escrow ». Thesis, Rhodes University, 2015. http://hdl.handle.net/10962/d1017936.

Texte intégral
Résumé :
Two or more parties entering into a contract for service or goods may make use of an escrow of the funds for payment to enable trust in the contract. In such an event the documents or financial instruments, the object(s) in escrow, are held in trust by a trusted third party (escrow provider) until the specified conditions are fulfilled. In the scenario of software escrow, the object of escrow is typically the source code, and the specified release conditions usually address potential scenarios wherein the software provider becomes unable to continue providing services (such as due to bankruptcy or a change in services provided, etc.) The subject of software escrow is not well documented in the academic body of work, with the largest information sources, active commentary and supporting papers provided by commercial software escrow providers, both in South Africa and abroad. This work maps the software escrow topic onto the King III compliance framework in South Africa. This is of value since any users of bespoke developed applications may require extended professional assistance to align with the King III guidelines. The supporting risk assessment model developed in this work will serve as a tool to evaluate and motivate for software escrow agreements. It will also provide an overview of the various escrow agreement types and will transfer the focus to the value proposition that they each hold. Initial research has indicated that current awareness of software escrow in industry is still very low. This was evidenced by the significant number of approached specialists that declined to participate in the survey due to their own admitted inexperience in applying the discipline of software escrow within their companies. Moreover, the participants that contributed to the research indicated that they only required software escrow for medium to highly critical applications. This proved the value of assessing the various risk factors that bespoke software development introduces, as well as the risk mitigation options available, through tools such as escrow, to reduce the actual and residual risk to a manageable level.
Styles APA, Harvard, Vancouver, ISO, etc.
2

Licorish, Sherlock Anthony. « Tool support for social risk mitigation in agile projects a thesis submitted in partial fulfilment of the degree of Master of Computer and Information Sciences (MCIS) at the Auckland University of Technology, Auckland, June 2007 / ». Click here to access this resource online, 2007. http://repositoryaut.lconz.ac.nz/theses/1354/.

Texte intégral
Résumé :
Thesis (MCIS - Computer and Information Sciences) -- AUT University, 2007.
Primary supervisor: Anne Philpott. Co-supervisor: Professor Stephen MacDonell. Includes bibliographical references. Also held in print (x, 147 leaves : ill. ; 30 cm.) in City Campus Theses Collection (T 005.12 LIC)
Styles APA, Harvard, Vancouver, ISO, etc.
3

Ginn, Robert C. « A software assurance framework for mitigating the risks of malicious software in embedded systems used in aircraft ». Thesis, Monterey, California. Naval Postgraduate School, 2011. http://hdl.handle.net/10945/5593.

Texte intégral
Résumé :
Approved for public release; distribution is unlimited.
techniques that can be used to detect malicious code in individual aircraft Weapons Replaceable Assemblies (WRAs)
risks and mitigation strategies related to a generic aircraft software development process
system level techniques to prevent embedded malicious software from causing harm in aircraft
and a technique for documenting Software Assurance (SwA) arguments being made about the system and the individual WRAs.
Malicious software represents a significant and growing threat to Defense systems. Threats to airborne systems in particular can be characterized not by system vulnerability to Internet based exploits but rather by the risk posed by malicious code already present in the system's software. Although there are software techniques to detect and prevent certain types of attacks, a Systems Engineer has access to system level information and system design techniques that can quantify and in many cases mitigate the risks posed by potential malicious code present in the system. These techniques are especially applicable to malicious code in embedded airborne system although they can be applied to other systems that share certain traits. This thesis provides an overview of the types of threat involved
Styles APA, Harvard, Vancouver, ISO, etc.
4

Denys, Paul. « Security of Personal Information in Cloud Computing : Identifying and mitigating against risks to privacy in the deployment of Enterprise Systems Applications on the Software as a Service platform ». Thesis, Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation, 2012. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-5726.

Texte intégral
Résumé :
The emergence and subsequent growth of Cloud computing has brought with it a great deal of change in the manner in which the world undertakes to compute and store information. This new technology has brought with it immense possibilities as far as processing of information and the pooling of resources is concerned. This potential has also been noticed by the public sector, as Governments all over the world have undertaken to introduce what has come to be known as e-Government, the provisioning of Government services and communications via Web based applications, rather than the traditional means of in person contact and paper based collection of personal information. While the move to Web based Government has been occurring for the last 20 or so years, a new development in this area is the introduction of Cloud computing and Cloud-based computing platforms, most notably Software-as-a-Service (SaaS) in the provisioning of these services. The computing and efficiency potential of this technology cannot be disputed, yet it’s important to recognize that taking advantage of this computing power does come at a price. That price being significant threats to personal privacy and security of personally identifiable information. This thesis will make it easier for government agencies to make informed decisions about whether or not to migrate data and applications into the cloud. The identification and analysis of potential risks to data security and personal information has drawn together key information from a multitude of both academic and industry sources to make such a decision plausible.
Styles APA, Harvard, Vancouver, ISO, etc.

Livres sur le sujet "Software risk mitigation"

1

Polydys, Mary Linda. Software assurance in acquisition : Mitigating risks to the enterprise : a reference guide for security-enhanced software acquisition and outsourcing. Washington, D.C : National Defense University Press, 2009.

Trouver le texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
2

Analyzing the Role of Risk Mitigation and Monitoring in Software Development. IGI Global, 2018.

Trouver le texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
3

Kieras, Tim, Quanyan Zhu et Junaid Farooq. IoT Supply Chain Security Risk Analysis and Mitigation : Modeling, Computations, and Software Tools. Springer International Publishing AG, 2022.

Trouver le texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
4

Falco, Gregory J., et Eric Rosenbach. Confronting Cyber Risk. Oxford University Press, 2021. http://dx.doi.org/10.1093/oso/9780197526545.001.0001.

Texte intégral
Résumé :
Confronting Cyber Risk: An Embedded Endurance Strategy for Cybersecurity is a practical leadership handbook defining a new strategy for improving cybersecurity and mitigating cyber risk. Written by two leading experts with extensive professional experience in cybersecurity, the book provides CEOs and cyber newcomers alike with novel, concrete guidance on how to implement a cutting-edge strategy to mitigate an organization’s overall risk to malicious cyberattacks. Using short, real-world case studies, the book highlights the need to address attack prevention and the resilience of each digital asset while also accounting for an incident’s potential impact on overall operations. In a world of hackers, artificial intelligence, and persistent ransomware attacks, the Embedded Endurance strategy embraces the reality of interdependent digital assets and provides an approach that addresses cyber risk at both the micro level (people, networks, systems and data) and the macro level (the organization). Most books about cybersecurity focus entirely on technology; the Embedded Endurance strategy recognizes the need for sophisticated thinking about hardware and software while also extending beyond to address operational, reputational and litigation risk. This book both provides the reader with a solid grounding in important prevention-focused technologies—such as cloud-based security and intrusion detection—and emphasizes the important role of incident response. By implementing an Embedded Endurance strategy, you can guide your team to blunt major cyber incidents with preventative and resilience measures engaged systematically across your organization.
Styles APA, Harvard, Vancouver, ISO, etc.

Chapitres de livres sur le sujet "Software risk mitigation"

1

Podari, Zuriyaninatasa, Adila Firdaus Arbain, Noraini Ibrahim et Endah Sudarmilah. « Risk Mitigation Framework for Agile Global Software Development ». Dans Lecture Notes on Data Engineering and Communications Technologies, 1233–46. Cham : Springer International Publishing, 2021. http://dx.doi.org/10.1007/978-3-030-70713-2_110.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
2

Zhou, Peng, et Hareton K. N. Leung. « Strategies for Scheduling Risk Mitigation in Software Project Management ». Dans Communications in Computer and Information Science, 3–23. Berlin, Heidelberg : Springer Berlin Heidelberg, 2014. http://dx.doi.org/10.1007/978-3-662-45943-0_1.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
3

Arbain, Adila Firdaus, Muhammad Akil Rafeek, Zuriyaninatasa Podari et Cik Feresa Mohd Foozy. « Measuring Risk Mitigation Techniques in Agile Global Software Development ». Dans Lecture Notes on Data Engineering and Communications Technologies, 1225–32. Cham : Springer International Publishing, 2021. http://dx.doi.org/10.1007/978-3-030-70713-2_109.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
4

Regano, Leonardo, Daniele Canavese, Cataldo Basile, Alessio Viticchié et Antonio Lioy. « Towards Automatic Risk Analysis and Mitigation of Software Applications ». Dans Information Security Theory and Practice, 120–35. Cham : Springer International Publishing, 2016. http://dx.doi.org/10.1007/978-3-319-45931-8_8.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
5

Hauge, Øyvind, Daniela Soares Cruzes, Reidar Conradi, Ketil Sandanger Velle et Tron André Skarpenes. « Risks and Risk Mitigation in Open Source Software Adoption : Bridging the Gap between Literature and Practice ». Dans IFIP Advances in Information and Communication Technology, 105–18. Berlin, Heidelberg : Springer Berlin Heidelberg, 2010. http://dx.doi.org/10.1007/978-3-642-13244-5_9.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
6

Chadli, Saad Yasser, et Ali Idri. « A Survey on the Impact of Risk Factors and Mitigation Strategies in Global Software Development ». Dans Advances in Intelligent Systems and Computing, 408–17. Cham : Springer International Publishing, 2018. http://dx.doi.org/10.1007/978-3-319-77712-2_39.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
7

Seyff, Norbert. « Mitigating Risks in Mobile System Development ». Dans Extreme Programming and Agile Processes in Software Engineering, 437–38. Berlin, Heidelberg : Springer Berlin Heidelberg, 2003. http://dx.doi.org/10.1007/3-540-44870-5_75.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
8

Stephansen, Cathrine, Anders Bjørgesæter, Odd Willy Brude, Ute Brönner, Tonje Waterloo Rogstad, Grethe Kjeilen-Eilertsen, Jean-Marie Libre et Christian Collin-Hansen. « Environmental Risk Management Applications of ERA Acute ». Dans Assessing Environmental Risk of Oil Spills with ERA Acute, 21–31. Cham : Springer International Publishing, 2021. http://dx.doi.org/10.1007/978-3-030-70176-5_2.

Texte intégral
Résumé :
AbstractERA Acute supports a variety of analyses, from simple screening studies based on oil spill statistics and potential impact areas to more in-depth impact and recovery calculations on species and habitats. The ERA Acute software tool has been built to enable and provide ease of use of the methodology and results. Visualizations of impact and risk areas can be made at several levels, from simulations and scenarios to whole cases. Results can have a monthly resolution to show variations throughout the year. This enables a wide range of decision-support from risk screening studies, impact assessments, risk quantification, risk management including effect of mitigating measures (NEBA/SIMA) evaluations to properly inform oil spill response planning. The methodology is suitable for global use and will be the recommended approach for oil spill risk assessments for offshore operators on the NCS.
Styles APA, Harvard, Vancouver, ISO, etc.
9

« Risk Assessment and Risk Mitigation Activities in the SDLC ». Dans Security Software Development, 235–50. Auerbach Publications, 2008. http://dx.doi.org/10.1201/9781420063813-12.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
10

« Risk Assessment and Risk Mitigation Activities in the SDLC ». Dans Security Software Development, 217–32. Auerbach Publications, 2008. http://dx.doi.org/10.1201/9781420063813.ch8.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.

Actes de conférences sur le sujet "Software risk mitigation"

1

Kazmi, Syeda Hina Mazhar, Yaser Hafeez et Sadia Ali. « Software outsourcing model for risk mitigation ». Dans 2018 International Conference on Computing, Mathematics and Engineering Technologies (iCoMET). IEEE, 2018. http://dx.doi.org/10.1109/icomet.2018.8346317.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
2

« Scheduling Strategies for Risk Mitigation ». Dans International Conference on Software Engineering and Applications. SciTePress - Science and and Technology Publications, 2013. http://dx.doi.org/10.5220/0004409203650376.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
3

Shahzad, Basit, et Abdullah S. Al-Mudimigh. « Risk Identification, Mitigation and Avoidance Model for Handling Software Risk ». Dans 2010 2nd International Conference on Computational Intelligence, Communication Systems and Networks (CICSyN 2010). IEEE, 2010. http://dx.doi.org/10.1109/cicsyn.2010.82.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
4

Zhou, Peng, et Hareton K. N. Leung. « A New Scheduling Strategy for Risk Mitigation ». Dans 2013 20th Asia-Pacific Software Engineering Conference (APSEC). IEEE, 2013. http://dx.doi.org/10.1109/apsec.2013.76.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
5

Shahzad, Basit, Ihsan Ullah et Naveed Khan. « Software Risk Identification and Mitigation in Incremental Model ». Dans 2009 International Conference on Information and Multimedia Technology. IEEE, 2009. http://dx.doi.org/10.1109/icimt.2009.104.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
6

Fesas, Nestor, et Donald F. Shafer. « Getting Software Risk Mitigation Right from the Start ». Dans SPE Digital Energy Conference and Exhibition. Society of Petroleum Engineers, 2011. http://dx.doi.org/10.2118/143797-ms.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
7

Ebert, Christof. « Supplier Performance Management : Risk Mitigation and Industry Benchmarks ». Dans 2017 IEEE 12th International Conference on Global Software Engineering (ICGSE). IEEE, 2017. http://dx.doi.org/10.1109/icgse.2017.5.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
8

Xu, Xiwei, Chen Wang, Zhen Wang, Qinghua Lu et Liming Zhu. « Dependency Tracking for Risk Mitigation in Machine Learning (ML) Systems ». Dans 2022 IEEE/ACM 44th International Conference on Software Engineering : Software Engineering in Practice (ICSE-SEIP). IEEE, 2022. http://dx.doi.org/10.1109/icse-seip55303.2022.9794111.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
9

Masticola, Stephen P. « Lightweight Risk Mitigation for Software Development Projects Using Repository Mining ». Dans Fourth International Workshop on Mining Software Repositories. IEEE, 2007. http://dx.doi.org/10.1109/msr.2007.16.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
10

Meslem, Abdelghani, Håvard Iversen, Dominik Lang, Tina Kaschwich, Linn Sir Drange et Keith Jones. « The LRG Software for liquefaction mitigation planning and decision support ». Dans IABSE Symposium, Guimarães 2019 : Towards a Resilient Built Environment Risk and Asset Management. Zurich, Switzerland : International Association for Bridge and Structural Engineering (IABSE), 2019. http://dx.doi.org/10.2749/guimaraes.2019.1681.

Texte intégral
Résumé :
<p>LIQUEFACT Reference Guide (LRG) software is one of the main products of the LIQUEFACT, a multi- disciplinary project funded under the European Commission’s Horizon 2020 framework program. The software, which incorporates both data and methodologies collected and elaborated in the project’s various work packages, has been developed for liquefaction mitigation planning and decision support, able to estimate and predict the likely consequences of Earthquake-Induced Liquefaction Disaster (EILD) to the most vulnerable region of Europe. In contrast to other seismic risk assessment software tools, the LRG software is targeting a wider range of user groups with different levels of technical background (urban planners, facility managers, structural and geotechnical engineers, or seismic risk modelers) as well as requirements. In doing so, the LRG software toolbox shall allow users assessing the liquefaction-related risk as well as assisting them in liquefaction mitigation planning.</p>
Styles APA, Harvard, Vancouver, ISO, etc.

Rapports d'organisations sur le sujet "Software risk mitigation"

1

Dodson, Donna, Murugiah Souppaya et Karen Scarfone. Mitigating the Risk of Software Vulnerabilities by Adopting a Secure Software Development Framework (SSDF). National Institute of Standards and Technology, avril 2020. http://dx.doi.org/10.6028/nist.cswp.04232020.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
2

Dodson, Donna. Mitigating the Risk of Software Vulnerabilities by Adopting a Secure Software Development Framework (SSDF). Gaithersburg, MD : National Institute of Standards and Technology, 2020. http://dx.doi.org/10.6028/nist.cswp.13.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
3

Polydys, Mary L., et Stan Wisseman. Software Assurance in Acquisition : Mitigating Risks to the Enterprise. A Reference Guide for Security-Enhanced Software Acquisition and Outsourcing. Fort Belvoir, VA : Defense Technical Information Center, février 2009. http://dx.doi.org/10.21236/ada495389.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
Vous pouvez également être intéressé par les bibliographies sur le sujet « Software risk mitigation » pour d’autres types de sources :
Articles de revues
Nous offrons des réductions sur tous les plans premium pour les auteurs dont les œuvres sont incluses dans des sélections littéraires thématiques. Contactez-nous pour obtenir un code promo unique!

Vers la bibliographie