Importance Of Software Engineering Process For Reducing The Product Or The System

If they pass the testing then they are progressed to the production area where they are finally put into the production and here the final system is set up.

Risk mitigation would allow the project manager to know the project’s strengths and weaknesses then evaluate the threats facing the project. The project manager would implement different strategies such as lowering exposure to threats or improving strengths of the project to make sure that the variance in schedule and cost is not very high when there are risk event occurrences. A risk mitigation strategy ensures that the project manager, the implementing team, and the project’s stakeholders are on the same page in the project implementation job. It also gives the project team an opportunity to address risks in advance so resolving additional issues becomes easy when the issues occur later during the implementation of the project. Moreover, the risk management strategy would fine-tune the parameters used for measuring the results of the project (Kerzner,

Risk management is an ongoing process that must continue through the life of a project. It includes processes for risk management planning, identification, analysis, monitoring, and control. These processes need to be reviewed throughout the project’s lifecycle as new risks arise throughout the implementation of the project. It is the objective of risk management to decrease the probability and impact of events adverse to the project. On the other hand, any event that could have a positive impact should be exploited.

In the end, each part would be subjected into multiple iterations and all these iterations will make a new module or will improve its existing module. This module would be integrated into a structure that would be tested at the end of the test cycle.

1. Use of phase gate model and project management tools same as traditional. On top of this, the Primavera software was used for the scheduling of the project.l

The project will be managed using a modified waterfall technique. In this approach, the initial two phases of the

* Any identifiable obstacles and risks (threats) that might prevent the successful attainment of the project goals must be considered. Each risk must be analyzed, quantified, and prioritized as much as possible with the information available at this stage of a new project. Risk responses, including mitigations, risk sharing, risk avoidance, and risk tolerances should be described in this portion of the project proposal.

The waterfall lifecycle was the first process model to be introduced and widely known. It is also known as the linear-sequential

Risk Reduction solutions allow information technology executives to reduce risk to their business operations from internal and external IT factors. The risk from internal factors is primarily attributed to poor planning and execution of projects and initiatives. The risk from external factors can be from competitors, suppliers, or unsatisfied customers.

Focus is kept on the recurrence of condensed work cycles and also at the functional product yielded by the outcome, but in waterfall technique only once chance is been given to the development team to keep the project aspects right. But under the agile technique each and every feature of development including the design, requirements, is thoroughly checked under its lifecycle (Mahfuj et al, 2012). There is always some time to steer in another direction if a team stops at regular interval say after every two weeks and re-evaluates the project done.

Risk response is the process of developing strategic options, and determining actions, to enhance opportunities and reduce threats to the project’s objectives. A project team member is assigned to take responsibility for each risk response. This process ensures that each risk requiring a response has an owner monitoring the responses, although the owner may delegate implementation of a response to someone else. There are several risk response strategies that can be discussed however; each of the strategies requires specific actions to be

Risk is a threat of destruction, injury, liability loss or any other negative incident caused by external or internal environments. Risk is unpredicted and nobody can guess it might happen in the near future. All of the projects exist risk and the project manager is responsible to identify those risk, which is a part of risk management planning process. Risk management is the procedure of distinguishing risk and reduce risk level. The risk management methodology decides the actions, strategies, instruments, and group parts and obligations regarding a particular task. A good risk management suggests control of possible future destruction and precautions for that risk. The risk management plan represents how administration will be organized and performed on the venture. As a management procedure, risk management is utilized to identify and preserve a strategic distance from the potential cost, timetable, and implementation or specialized dangers to a framework, take a proactive and organized way to deal with negative results. The risk management approach and arrangement operationalize these administration objectives.

As waterfall model has many advantages it is carrying a lot of disadvantages. It is hard to make changes after testing the stage. Once an application is in the testing stage, it is very difficult to go back and change something that was not well-thought out in the concept stage. The software never work tile the few last steps and it is very hard to identify the errors at the beginning. It is gambling operation to make a software and successful of the software is unknown. It is not suitable for a large complex project.

Waterfall development has distinct goals for each phase of development. This case because, due to difficulty of returning to an earlier phase. The model shown here is one of several more or less equivalent alternatives.

The waterfall model consists of five phases such as requirements, Design, implementation, verification and maintenance. The method is a sequential design process where progress is seen as flowing downwards in a steadily manner, each development phase has its own distinct goals. The model is similar to water flowing down a cliff it can only flow in one way and cannot go back up it is the same with waterfall development ,after a development phase is completed it proceeds to the next development phase you cannot go back.