Quality and security of software are key factors in the software development. This thesis deals with the quality of open source software (OSS for short) and different questions that are related with open source and close source software has discussed in the thesis proposal. Open source software is a process by which we can produce cheap and qualitative software and its source could be re-use in the development of the software. Close source software is more expensive than open source software and we can not re-use its source code, so there should be a way by which cheap and qualitative software should be produced. This thesis describes that how the quality of the open source software can be evaluated and increased. There are different factors which are helpful to increase the software quality these factors are low cycle time, low cost and small size of software. These factors are also helpful for the development of software product according to the requirement of clients and the users of that software. This thesis also describes the security and performance of close and open source software and it also analyze different software development processes. The quality of OSS can be increased by use of best evaluation techniques, best quality measurement, best development tools and best development process. There are also many challenges for OSS, which it has to face for improvement of the quality of OSS. Initially there were many drawbacks in open source software but with the passage of time improvement has produced in it. This thesis also describes the compression, advantages and disadvantages of the close source and open source software.
Contents
Introduction
Open-Source Challenges
1.0 Problem Definition and Expected Outcome
1.1 Problem Definition
1.2 Expected Outcome
2.0 Research Methodology
3.0 Theoretical backgrounds
3.1 How can we achieve the quality in open source software?
3.1.1 Quality of Open Source Software by Best Quality Assessment
3.1.1.1 Rahul’s OSS Selection Model
3.1.1.2 McCall’s Model
3.1.2 Quality of Open Source Software by Best Measurement
3.1.2.1 Metrics Choice
3.1.3 Quality of Open Source Software by Best Process
3.1.3.1 Total Quality Management
3.1.3.2 ISO 9000 Standard
3.1.3.3 Personal Software Process Model
3.1.4 Quality of Open Source Software by Best Tools
3.1.4.1 CASE Tools
3.1.4.2 SE Environments
3.1.4.3 Using of Refactoring
3.1.5 Quality and Quality Work in Market
3.1.6 Quality And Quality Work In Different Open Source Software Systems
3.1.6.1 Real Time Systems
3.1.6.2 Operating systems
3.1.6.3 Web Systems
3.1.6.4 Differences between Three Systems
3.1.7 Quality Dimensions of Open Source Software
3.1.8 Similarities in Software and Goods
3.1.9 Differences in Software and Goods
3.1.10 Similarities in Software and Services
3.1.11 Differences in Software and Services
3.1.11.1 Collection of Data
3.1.11.2 Histogram
3.1.11.3 Pareto Chart
3.1.11.4 Cause-and-Effect Diagrams
3.1.11.5 Stratification
3.1.11.6 Scatter Plots
3.1.11.7 Control chart
3.1.12 Quality Aspects of Supply Management
3.1.12 .1 Affect of Supply Process
3.1.12 .2 Inspection to Achieve Quality
3.1.12.3 Customer Involvement
3.1.12 .4 Continuous Improvement
3.1.12 .5 Continuous Improvement Through TQM
3.1.12 .6 Rational for Supplier Products
3.1.13 Phases of Quality Vs Open Source Software Quality Activities
3.1.13.1 Quality Inspection
3.1.13.2 Quality Control
3.1.13.3 Quality Assurance
3.1.13.4 Quality Management
3.2 Question No 2 & 3
3.2.1 ISO 9126 Quality Model (Recent Model)
3.2.1.1 Functionality
3.2.1.2 Usability
3.2.1.3 Portability
3.2.1.4 Reliability
3.2.1.5 Efficiency
3.2.1.6 Maintainability
3.2.2 ISO 9001
3.2.3 Quality Evaluation Method
3.2.4 Process Centric Approach
3.2.5 Software Process and Development Method
3.2.5.1 Standards & Methods
3.2.5.2 Process Completeness
3.2.5.3 Modifiability & Readability
3.2.5.4 Traceability
3.2.6 Analysis
3.2.6.1 Sources Completeness
3.2.6.2 Analysis Model s Consistency
3.2.6.3 Analysis Model s Completeness
3.2.6.4 Context Definition s Completeness
3.2.6.5 Functionality Completeness
3.2.6.6 User Interface Prototype s Usability (UIP)
3.2.6.7 Data Model s Correctness
3.2.6.8 Non Functional Requirements Completeness
3.2.6.9 Non Functional Requirements Verifiability
3.2.6.10 Verification Credibility
3.2.7 CMMI
3.2.7.1 Characteristics of CMMI / ISO
3.2.7.2 Difference between CMMI / ISO:
3.2.7.3 Strengths of CMMI Include
4.0 Comparison of open source and closed source software products
4.1 Problems for Open Source Software
4.1.1 Coordination Mechanisms
4.1.2 Maintainability
4.1.3 Open Availability of the Source Code
4.2.1 Cost Advantage
4.2.2 Free Availability of Source Code
4.2.3 Maturity
4.2.4 Reliability
4.2.5 Open Source as a New Way to Develop Software
4.2.6 Open Source and the Protection of Customers
4.2.7 Open Source Software and Safety
4.2.8 Motivation
4.3 Problems for Close Source Software
4.4 Benefits of Close Source Software
5.0 Discussion
6.0 Conclusions
Future Work
References
Author: Muhammad Tahir and Aleem Tariq
Source: Blekinge Institute of Technology
Reference URL 1: Visit Now