– Software Bugs: Detection, Analysis and Fixing –
Download Software Bugs: Detection, Analysis and Fixing project materials: This project material is ready for students who are in need of it to aid their research.
ABSTRACT
This research work is concerned with the detection, analysis and fixing of software bugs. The objective of this work was to identify the software development process with a focus of identifying cost-effective methods of developing
and managing software systems by introducing a post-deployment debugging approach that helps track software’s stability and at same time serve as a software bug-data repository.
To achieve this objective, a web-based application –BugTracker was developed to manage software testing and post-deployment activities and at the same time serve as a bug-data repository.
The proposed approach allows testers and end-users of the system to report bugs which the developer analyses to resolve issues and thereafter update the program files with the newly updated versions.
UML and Overview models were used in the analysis and design of the BugTracker while PHP, HTML, JavaScript and MySQL database were used as the technology for the implementation of the system.
Evaluation and testing of BugTracker revealed an increase in developer’s productivity, reduction in production cost and an increase in software’s stability.
This research work reveals that it is possible to increase a software’s stability and reduce development cost if post-deployment activities are well managed.
TABLE OF CONTENTS
TITLE PAGE………………………. i
CERTIFICATION……………….. ii
APPROVAL……………………… iii
DEDICATION………………….. iv
ACKNOWLEDGEMENT………………….. v
ABSTRACT……………………… vii
TABLE OF CONTENTS………………….. viii
LIST OF FIGURES………………….. x
LIST OF TABLES………….. xi
CHAPTER ONE: INTRODUCTION
- BACKGROUND OF STUDY…………. 1
- STATEMENT OF PROBLEM………… 2
- OBJECTIVES……………… 3
- SIGNIFICANCE…………….. 3
- SCOPE………………… 4
- LIMITATIONS…………. 4
- DEFINITION OF TERMS……….. 4
CHAPTER TWO: LITERATURE REVIEW
2.1 THEORETICAL BACKGROUND………….. 6
CHAPTER THREE: SYSTEM ANALYSIS AND DESIGN
- EXISTING SYSTEM…………………. 17
- ANALYSIS OF THE PROPOSED SYSTEM………… 18
- DEPLOYMENT AND SYSTEM SPECIFICATION………… 24
- DATA BASE DESIGN………… 24
CHAPTER FOUR: SYSTEM IMPLEMENTATION
- CHOICE OF PROGRAMMING LANGUAGE…………… 29
- SOFTWARE PRODUCT RELIABILITY……… 31
- SAMPLE RUNS………….. 34
- SYSTEM TESTING…………. 40
- SYSTEM DOCUMENTATION………….. 42
CHAPTER FIVE: SUMMARY AND CONCLUSION
- REVIEW OF ACHIEVEMENTS……………. 44
- AREAS OF APPLICATION OF WORK………….. 44
- SUGGESTIONS FOR FURTHER WORK…………. 45
- RECOMMENDATIONS…………….. 45
- CONCLUSION…………………… 46
REFERENCES……………… 47
INTRODUCTION
1.1 Background of the Study
On the 4th of June 1996, the maiden flight of the Ariane 5 launcher ended in failure. Only about 40 seconds after initiation of the flight sequence, at an altitude of about 3700 m, the launcher veered off its flight path, broke up and exploded.
The failure of the Ariane 5 was caused by the complete loss of guidance and altitude information 37 seconds after start of the main engine ignition sequence (30 seconds after lift-off).
This loss of information was due to specification and design error in the software of the Inertial Reference System of the launcher.
Software has become a key feature of a rapidly growing range of products and services from all sectors of economic activity.
Software-intensive systems include large-scale heterogeneous systems, embedded systems for automotive applications, telecommunications, wireless ad-hoc systems, business applications with an emphasis on web services, etc.
REFERENCES
Tevfik, “Introduction to Software Engineering”, 2012 Available
Graham, E. V. Veenendaal, I. Evans, and R. Black,Foundations of Software Testing, London: Cengage Learning EMEA, United Kingdom, 2008.
Bell, Software Engineering for Students: A Programming Approach, England: Pearson Education Limited, 2005
IEEE Computer Society,IEEE Standard Glossary of Software Engineering Terminology: IEEE Standard 610.12-1990. Number 12- 1990 in IEEE Standard. 1990.
Fredericks, “Using defect tracking and analysis to improve software quality”. Experimental Software Engineering Group, University of Maryland, College Park,
Be the first to comment