ABSTRACT
This research study was on An Expert System for Mobile Software Reliability (A Case Study of Idem Electronic, Uyo). The research study was necessary so as to provide a automated system to evaluate the level of reliability of the different software available in the mobile industry. Limited research work had been conducted on assessment of mobile software reliability and this has also brought about limited information on the reliability index of mobile software. Since there are numerous mobile software application in the market that perform specific function, there is need to determine their level of ease of usage, fault detection rate, rate of break down, etc in relation to one another. This information will enable manufactures and vendors of the software to determine which mobile software is more reliable and which needs improvement. The software development methodology used is object oriented Analysis and Design Methodology (OOADM) and the programming language used is Visual BASIC 6.0.
TABLE OF CONTENT
Cover Page – – – – – – – – i
Title Page – – – – – – – – – ii
Dedication – – – – – – – – – iii
Certification – – – – – – – – iv
Acknowledgement – – – – – – – – v
Table Of Content – – – – – – – – vii
CHAPTER ONE: INTRODUCTION
1.0 Introduction – – – – – – – – 1
1.1 Theoretical Background – – – – – – 1-4
1.2 Statement of the Problem- – – – – – 4
1.3 Aim and Objectives of the Study – – – – 4
1.4 Significance of Study – – – – – – – 5
1.5 Scope of the Study – – – – – – – 5
1.6 Organization of Research – – – – – – 5
1.7 Definition of Terms – – – – – – 6
CHAPTER TWO: LITERATURE REVIEW
2.0 Introduction – – – – – – – – 7
2.1 Software Reliability Overview – – – – 7-9
2.2 Software Engineering and Mobile Application Development – 9-11
2.3 A Research Agenda for Mobile Engineering – – – 11-13
2.4 Expert System – – – – – – – 13-17
CHAPTER THREE: ANALYSIS AND DESIGN
3.0 Introduction – – – – – – – – 18
3.1 Research Methodology – – – – – – 18
3.2 System Analysis – – – – – – – 18
3.2.1 Analysis of the Existing System – – – – 19
3.2.2 Problem of the Existing System – – – – 19
3.2.3 Analysis of the Proposed System – – – 19
3.2.3.1 Advantages of the Proposed System – 19
3.2.3.2 Disadvantages of the Proposed System 20
3.3 System Design – – – – – – – 20
3.3.1 Input Layout – – – – – – 20-21
3.3.2 Algorithm – – – – – – – 22
3.3.3 Program Flowchart – – – – – 23-27
CHAPTER FOUR: IMPLEMENTATION AND DOCUMENTATION
4.0 Introduction – – – – – – – – 28
4.1 System Design Diagram – – – – – – 28
4.2 Choice of Programming Language – – – – 29
4.3 Analysis of Modules – – – – – – 29
4.4 Programming Environment – – – – – 29-30
4.5 Implementation – – – – – – – 30
4.6 Software Testing – – – – – – – 30-31
CHAPTER FIVE: SUMMARY, CONCLUSION AND RECOMMENDATIONS
5.0 Introduction – – – – – – – – 32
5.1 Summary – – – – – – – – 32
5.2 Constraint of the Study – – – – – – 32
5.3 Conclusion – – – – – – – – 33
5.4 Recommendation – – – – – – – 33
References
Appendix A
Appendix B
CHAPTER ONE
INTRODUCTION
1.0 Introduction
This chapter presents the introduction to expert system for mobile software reliability. It presents the introduction, theoretical background, statement of the problem, aim and objective of the study, significance of the study, scope of the study organization of the research and definition of terms.
1.1 Theoretical Background Mobile software systems are sometimes characterized by their highly dynamic configuration unknown operation profile, and fluctuating execution conditions. Most existing software reliability analysis approaches are geared to traditional desktop software systems, which are relatively stable and static throughout their execution. Therefore, assessing the reliability of mobile software systems requires new principles, models and tools that incorporate the underlying uncertainties associated with such systems. At the same time, since often an accurate estimation of the mobile software system’s execution context is not available at design-time, it is infeasible to determine an optimally reliable architectural configuration for the software system prior to its deployment. Therefore, a run-time reconfiguration of the software system may be necessary to improve its reliability. While application development for mobile devices goes back at least 10 years, there has been exponential growth in mobile application development since the iPhone AppStore opened in July, 2008. Since then, device makers have created outlets for other mobile devices, including Android, BlackBerry, Nokia Ovi, Window Phone, and more. Industry analysts estimate that there are more than 250,000 application available through the various stores and markerplaces, some of which are available for multiple types of devices. There are numerous comprehensive programming environment available for the major mobile platforms. Apple’s iOS Dev Center offers the Xcode package, which include an Interface Builder, an iphone emulator, and a complete development environment that can be used across all Apple product. For Android, developers can use the Android Development Tools plug in for the Eclipse programming environment. For Windows Phone, developers can use a specialized version of Microsoft’s Visual Studio environment. Similarly, there are application development tools for Blackberry, Symbian and other platforms. In addition, there are now some cross-platform development tools such as RhoMobile’s Rhodes and the open source PhoneGap, which can be used to create native application on various brand of Smartphone. Along the same lines, Netbisciuts, Appcelerator, Kyte and other companies provide tools and framework to support the creation of mobile web and hybrid sites using their SDK or one of the preciously mentioned environment. These powerful development tools and framework greatly simply the task of implementing a mobile application (Agrawal, 2010).