For This or a Similar Paper Click To Order Now

Please reply to the Discussion Board post below: Describe the processes involved
Please reply to the Discussion Board post below: Describe the processes involved in software change management? Software change development is where software phases out and needs to be upgraded or remodified to change with current software, applications, or hardware. This task can be a very daunting task for an organization especially for a large organization that has a ton of devices on their network. Because this task can be so daunting their was a model created in the 1960’s called System Development Life Cycle (SDLC) to assist in modifying and creating software. (Michael Solomon). This model is a 10-step approach and is used as needed meaning that some organizations do not use every step of the process but use it as a best practice to assist in software change management. The steps are initiation, modeling, planning, requirements, analysis, coding, testing, implementation, maintenance, and disposition. The point of using SDLC is to identify and resolve problems found during the change management process which assist in increasing the probability of success. So how do these processes or steps work in SDLC, the first step initiation which is exactly what it sounds like you initiate the process like cost, time, or materials. Modeling is gathering all the required information you will need throughout the process to ensure it is a success this is where you plan ahead for problems that may arise. Planning is where you plan the process like materials needed and create a schedule for the process. Requirements is where you identify what the software is needed for, what is its current importance. Analysis is where you design the software ensure it fulfils business requirements or whoever it is that is utilizing that software. Coding is where the coding of the software is checked to make sure it functions as intended. Testing is where you test everything you have done up until this point however, it is best practice to test after each step to find any errors early on in the process instead of letting mistakes pile up. Implementation is where the software moves into the production phase and next is maintenance is where the software is modified which is usually for two reason which are to enhance the software or resolve bugs that may have been found. And lastly is disposition, disposition is where you safely get rid of old software or hardware once you have transferred it to its new device you then ensure the old devices are wiped clean and recycled or destroyed properly. All these steps are used in creating new software and updating new systems. References Michael Solomon, Security Strategies in Windows Platforms and Applications, Third Edition, Jones & Bartlett Learning,

For This or a Similar Paper Click To Order Now

Leave a Reply

Your email address will not be published.

For This or a Similar Paper Click To Order Now