 Hello and welcome to this session in which I will discuss 10 different risks that deals with software development cycle or system development cycle. First is what is software development cycle which we covered in the prior session in a summary it's a framework used by software development team to plan design develop test deploy and maintain software application. Now while this approach is a structural approach step by step there are several risks that we need to be aware of that could impact the success of the software development of any project. What I'm going to do I'm going to list those risks and discuss them briefly. The first risk is incomplete requirement. What does that mean? It means if the requirements are not fully understood by the developer or by the customer but let's talk about the developer the resulting software may not need the needs of the end users. Simply put the software development team was asked to create a new inventory system but they did not fully understand the complex requirement for the different department involved. What's going to happen you're going to have a bad product so incomplete requirement is a risk for any software development life cycle. Another risk is poor project management or poor project scheduling. What does that mean? A lack of planning communication coordination between the team members can lead to delays which is not good cost overrun it will cost you more and other problem. So let's assume a team is working on a new mobile app but they failed to communicate effectively with the client and did not provide regular updates on the progress. What would happen this is going to lead to misunderstanding delays and maybe the client might eventually decide to terminate the contract so that's another risk in software development life cycle. Before we proceed any further I have a public announcement about my company farhatlectures.com. Farhat accounting lectures is a supplemental educational tool that's going to help you with your CPA exam preparation as well as your accounting courses. My CPA material is aligned with your CPA review course such as Becker, Roger, Wiley, Gleam, Myles. My accounting courses are aligned with your accounting courses broken down by chapter and topics. My resources consist of lectures, multiple choice questions, true-false questions as well as exercises. Go ahead start your free trial today no obligation no credit card required. A third risk scope creep what does that mean it means you keep making changes outside the requirement the scope of what we agreed upon initially so changes to project scope or requiring during development can lead to delays cost overrun failure to deliver for example a team was developing a new website but the client kept requesting additional features and functionality during the development process so it's very important to have everything clear upfront so you don't get into the scope creep issues risk. Insufficient testing what does that mean it means you did not perform enough testing and we're going to talk about testing much much more later on can result in software that's unreliable or vulnerable to security breaches so a software company would release a new app without thoroughly testing and they quickly discovered that the app had a major security flaw that could be exploited by hackers that could be a risk so the company had to release an emergency patch to fix the issue this way it's going to cost more money and most importantly damage the reputation reputation is one of the most important risks when it comes to it related issues right something related to this is an inadequate security well if the security is not built into the software from the beginning it will be very difficult later on and expensive to add it later and maybe sometime you can't add it so or add it properly so a company developed a new customer portal but did not include strong security features well hackers were able to exploit it easily stealing sensitive customer information again this is a reputational issue which is really bad and it could also lead to significant financial losses more risks is poor quality control well if you don't pay attention to detail failure to follow best practices during the project development cycle and other quality issues that in a software that is unreliable or difficult to maintain could raise some serious risks so a software development team did not follow best practices for coding testing result and final product that's riddled with bugs and difficult to maintain is a risk of a software development life cycle okay what would that do it's going to cost significant frustration think about it from a user's perspective it'll be very expensive to fix especially in terms of reputation you could also have failure and hardware or software what does that mean it means you have issues with the hardware and software that they are using that could cause delays or make it impossible to complete the project so a software development team let's assume they're developing an application that is depending on a specific version of an operating system however the operating system was updated during development causing compatibility issues and delays that could be a big problem so the software the hardware they're not comparable anymore one of the most important risk is lack of user involvement slash adoption so users are not involved or they don't adopt the new system the new software so failure to involve users in the development process can lead to software that's difficult to use or does not meet their needs and it's going to create a challenging and adoption so software development development team develop a new system without consulting end users that's not good so the final product was difficult to use and did not meet the user's resulting and low adoption rate and that's very risky because customers the end users are dissatisfied more risks would involve poor documentation an adequate documentation can make it difficult to maintain or modify the software you really did not keep track you did not really plan this properly and put everything down here actually put everything down so when I go back and make any changes you have nothing to reference so maybe a company the the company developed a custom software solution but did not document the code or the development process so no one can follow so when the original developer left the company it will be difficult and expensive to find new developer to maintain the system this is the risk of a software development lifecycle the 10th risk is the resource risk simply put you did not provide enough resources whether it's money people expertise time a software development team was tasked with developing a new mobile app but they did not have the necessary resources hardware software people funds time this could lead to delays increase in cost as the team have to acquire the necessary resources could be a major risk as well what should you do now just go to far hat lectures and you know answer some mcq's that's gonna help you consolidate this knowledge it's pretty much in my opinion that's a straightforward topic risks for software development lifecycle make sure you know what software development lifecycle so you have an overall idea about this lifecycle from a to z including the risks good luck study hard and invest in yourself you