When it comes to software quality, it is easy to think of software defects.
From the user's point of view, software quality is the degree to which software functions meet user needs, including: clearly stated needs and potential needs, software that meets the needs, the fewer bugs, the software system is fully functional, and all aspects of performance meet the requirements , can run reliably, has a friendly and easy-to-understand user interface, and is considered to be of better quality if it is easier for users to use.
From the developer's point of view, the better the quality is, the easier it is to build an architecture that is easy to expand, with modules with low coupling, strong code reusability, concise and easy to understand, easy to maintain, easy to configure, and easy to manage.
The reason for looking at software quality from two perspectives is that some software quality is not shown on the surface. Such as software design quality, if we measure software quality only from the perspective of users, the importance of design quality will be ignored.
Software quality is involved in all stages of software product execution, and neglect of quality issues at each stage may have a negative impact on software quality.
Software quality includes many quality characteristics, and each link of software quality is manifested through various quality characteristics. Through the improvement of software quality characteristics, the purpose of improving the overall quality of software is achieved. In order to ensure the software quality in the software development process, every stage of the whole software life cycle requires software quality assurance activities.