The Main Issues Involved in the Software Engineering Process - Coursework Example

This paper will outline some of the main issues (which cause software failures) that are involved in the software engineering process and will suggest solutions to resolve these issues and problems. Seeing that, a major reason for software failure is the poor development process for software development. However, this is because of the complex nature of contemporary software. In fact, when designing or programming a section of the software, we are frequently dealing with a lot of issues simultaneously. Additionally, some of them can distract our focus from the particular problem which we are attempting to resolve. In this scenario, the issues and problems we are dealing with in a software development process can comprise the following: (Roodyn, 2005)

• Need to strictly follow the design of the system
• Ensuring our new code/routine does not break some of the existing modules
• Making sure we are following the coding/designing principles
• Taking care of how this resolution will influence future jobs that require being finished

That is what we are going to try to attain through the software development process. In the first step, we look at what makes a high-quality solution. After that, we work through an idea that shows how we are able to perform focused small jobs that guide us towards the implementation of that solution (Roodyn, 2005).

I have presented below some of the main issues in the overall software development process: 

Poor software development practices issues can be the errors that occur due to the mistake of a software developer. This kind of issue involves: (BenmeadowCroft, 2011)

• Less focus on testing of the program
• Making wrong assumptions from the requirements of the system
• Producing less effective documentation
• Less effective user interface

Another class of problems is known as end-user or entity problems. These issues or problems occur due to the errors in the piece of either the end-user or the unit that is making use of the system. These problems and issues can comprise: (BenmeadowCroft, 2011)

• Recording incorrect requirements for the system
• Entering and using wrong data
• Not giving training to the end-user
• Damaged expensive hardware
• Poorly designed hardware
• A less effective poor fit between the system and the organization

http://www.benmeadowcroft.com/reports/systemfailure/

Moreover, effective software development and management quality are attained through intense product examination. Like that inspection consumes a great deal of the business resources. In the same way, if a product fails in testing, it requires to be revised or scraped. Additionally, a product can encompass a large number of faults or errors if it follows minimum quality principles and standards. It outlines that the clients are willing to pay for a “buggy” thus far working product. In this scenario, the quality is a split job and focused on the assessment of the product. However, it is assumed that the software development group/team will always welcome such a self-governing quality function. Developers are blamed for poor quality is an approach that can resolve these issues. Though, replacing a worker does not denote humanizing quality. Also, less effective quality can come from the supplier side (Li et al., 2000).

For the effective management of issues we will take the below-given measures:

Taking Measures

A good idea can be to request the team and other stakeholders to join a risk recognition workshop. Additionally, the software development stakeholder needs to play a direct role in the software development process but he would not need to perform any function. In this scenario, a manager from the relevant business department is responsible for informing us whether a user conditionally assigned to our project has the necessary skills, will authentically be accessible, and will be authorized to stand for their part of the business (Roberts, 2011; Carnegie Mellon University, 2011).

Priorities the risks

Prioritizing the risks is also one of the main techniques for the risk management of the issues regarding software development. In this scenario, we need to resolve and manage the high probability risks that will evidently require the most attention. In addition, we can well decide to pay no more attention to the low probability of low influence of the risks to keep away from cluttering up our risk management procedure (Roberts, 2011; Carnegie Mellon University, 2011).

Minimize Risks

The majority of software development companies record how projects are completed successfully with risks as well as make this information available to future project managers. Thus, by getting a list of dozen of ways project managers can get an idea that how the risk in the past could offer us a number of extremely useful pointers from how we might diminish the risk in our project  (Roberts, 2011; Carnegie Mellon University, 2011).

Monitoring

We need to monitor some of the vital risks of the project by creating a risk register that outlines the risks in priority order (Roberts, 2011; Carnegie Mellon University, 2011).