The Analysis And Fault Tolerence Of Software Environment

A successful IT system is something that is composed of several different functional components to make it a whole. It takes each component to efficiently work so that the entire system runs smoothly. When one or more parts of the system are not properly working it can affect the entire IT system as a whole and render it completely vulnerable to people with malicious intentions. In this paper I will discuss the role of each component in it and shed some light as to why each is needed.

Reliability refers to system live time, that is, system is running efficiently most of the time. Availability is the probability that the system is continuously available (usable or accessible) during a time interval.

The reliability of a system can be improved through the introduction of redundancy in the system. Some of the examples of redundancy in the operation are as below:

This type of failure can only happen on a distributed system. An example of this is: in a distributed system, 1 computer sends a message to another computer either asking the computer if it’s responsive, requesting information from the computer, or replying back to the other computer that asked if it is responsive. This can cause problems when computer A sends computer B a message asking if it’s responsive, however the message never gets to computer B therefore computer B never responds and computer A assumes that computer B is down.

MPI: The fault-tolerance mechanism in MPI depends either on handling failure in the application itself or implementing regular checkpoint files.

Information will only have value if customers can access it at the right times. Availability can be affected by system errors, and malicious attacks as well as infrastructure problems. Availability is ensured by maintaining hardware as well as repairing hardware immediately when need arise. A correct functioning operating system should also be maintained in the environment free of software conflicts. Adequate communication bandwidth should also be addressed as well as preventing bottlenecks from occurrence.

Network reliability is the ability of a network to maintain or restore an acceptable level of performance during network failures by application various restoration techniques and prevention of service outages from network failures by applying preventative techniques. (Network Survivability, 2001). Computing the reliability of a network is quite difficult; therefore estimation by means of simulation is a popular choice for determining network reliability.

software development. It provides a background in applications software development and testing techniques through a

Dependency Failures Include systems or personal that become inoperable that are outside our control to repair. This includes 3rd party application or cloud storage, also includes the termination of critical employee example would be a system administrator resigns, or subject matter expert was terminated.

IEEE Std 982.1-2005 (Revision of IEEE Std 982.1-1988) - IEEE Standard Dictionary of Measures of the Software Aspects of Dependability

An industry-wide effort to develop systems that can configure, optimize, tune, and heal themselves when broken, and protect themselves from outside intruders and self-destruction is called:

Faults are a precise interaction of hardware and software that can be fixed given enough time.

The proposed system can be used to scan the apex code and it will report vulnerabilities present in the software. The proposed system is helpful for

Availability: Ensuring that systems and data are accessible to authorized users when they need it.

Precise offered the software that helped its clients to manage the performance of their information technology (IT) systems. Precise is in the performance management and availability market. Its products are designed to manage the performance applications utilizing Oracle database. The company had focus on a small range of core products but provided users high quality that promised. Precise offered the software license and services. The main products were insight products, SQL and Presto. Precise/SQL accounted for 86% of all Precise’s software licensing fees. The company has strong trained account reps with very strong relationships with key clients. End-to-end response time is extremely important to ensure the system ran efficiently and effectively. All of the available products focused on the performance of each of the components of the system. The sales cycle is 6 to 12 months on average. Precise realized from the feedback of its consumers that they should provide right solutions to its clients rather than the products. However, a full-functionality end-to-end performance tool needs a long time to be developed. It’s going to take six and nine months to get a basic product with purely monitoring only. The fully