Fault Prediction On The Object Oriented Software Metrics Essay

Like any other complex structure, software must be built on a solid foundation. Failing to see the big picture or consider key scenarios, failing to design for common problems, or failing to appreciate the long term consequences of key decisions can put your application at risk. Modern tools and platforms help to simplify the task of building applications, but they do not replace the need to design your application carefully, based on your specific scenarios and requirements. The risks exposed by poor architecture include software that is unstable, is unable to support existing or future business requirements, or is difficult to deploy or manage in a production environment. Software architecture must be distinguished from lower-level design (e.g., design of component internals and algorithms) and implementation.

“During the object-oriented analysis (OOA) phase object-modeling techniques are used to analyze the functional requirements for a system and create models which reflect the logical design of the system. During the object-oriented design (OOD) phase of the system, models are elaborated upon to include implementation specific details that show how the physical design of the system will come together. OOA focuses on what the system does (its static structure and behavior), OOD on how the system does it (its run-time implementation).”

Objective of this research paper is to learn and understand the recent changes in software engineering and how it can pave way to an advanced method of software engineering in the coming future. Hence this paper will be based on how current trends in software development would affect the future.

While developing a system the developers should be aware of all kinds of software design principles. Some of the principles like cohesion, coupling, Object Oriented principles will help to design a software application. If all the principles are applied correctly, than there is a chance to reduce software coding errors. First when developers start writing code, the back end code starts with classes they should take appropriate decisions in constructing the classes.

For the system, which should never be failed, the reliability test of the software should be done. For this, the black box and white box testing should be done on the software. After the successful development of the software, a beta version should be released. The errors and bugs related to the security and functional requirements can be find out in an easy manner.

In terms of systems and processes, in my opinion, one of the most interesting models used to improve quality is the “API Improvement Model”. This is a simple model based

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

This article addresses some of the common coding errors and suggests some ways in how to preventing them. This is knowing where the traps are and how to help to avoid them.

Abstract— Reliable software is defined as the probability of failure-fee operation of a software system for a specified time in a specified environment. Unreliable software is defined as the when a software system has failures and faults within its operation. Software is unreliable when a computer program cannot perform their assigned functions in the system’s environment and ends up crashing. Many computer software specialists have been used to thinking that if a program has one or more errors in it, it is 0% reliable; if no errors 100% reliable [3].

Malfunction: software malfunction is mostly caused by poor development practices where security has not been built in the software development life cycle but rather incorporated at a latter phase when the software is already fully developed. By doing this, most of the vulnerabilities won’t be handled which latter leads to either crash or malfunctioning of the software, whereby the attacker has an easy time breaking into the system and causing damage or customer’s data disclosure.

Shaw puts forth the hypothesis that research in software engineering should be characterized by research processes in other science and engineering disciplines which include research questions, results and validation. Highlighting related work, she mentions previous research efforts to characterize

Abstract--A number of software fault tolerance methods have been proposed to achieve high reliability. However, these methods suffer from the lack of considering the possibility of correlated failures, where the failure of multiple components leads to system failure. Furthermore, previous methods to assess the impact of correlated failure on software fault tolerance require extensive testing of data and are therefore less suitable to conduct reliability analysis in the early design stages. Hence, these types of failures must be explicitly incorporated into reliability analysis. The influence of correlated failures on application reliability must be analyzed within the context of the application architecture. This paper provides a survey of some of the studies conducted so far in the field of software reliability and gives a summary of the models proposed to study the impact of correlated failures on the software reliability. The paper concludes by highlighting the major contributions of some studies and provides a direction for the future study in the field.

In recently years, requirements of software products from economic markets in all over the world become stronger and frequently. Software companies need to complete software programs which come from huge amounts of users, and at the same time, software companies also need to fulfilled users’ requirements for function and requirements for high quality products. Most of times these develop companies need to do excellent products without a long development period and plenty of

The modern programming is based on the concept that “program little and use more”. The object oriented programming languages are playing a vital role in the industry of development. The OOP introduced following concepts:

Pressman, Roger S., Software Engineering: A Practitioner's Approach (4th Edition), McGraw-Hill International Editions, 1997. Pages 400 to 405.