The evaluation activities of the quality of software can be divided into two main categories which are static analysis and dynamic analysis.
1o Static Analysis: It is based on a survey of a number of documents and requirements documents, software models, design documents and source code. Traditional static code analysis includes examination, inspection, virtual tours, analysis of algorithms, and proof of correctness. This is not the actual execution of the code being developed and examines the code and think about all sorts of behaviors that may arise during driving time. compiler optimizations are standard static analysis.
2nd Dynamic analysis: The dynamic analysis software includes the effective implementation of the program in order to identify any shortcomings in the program. Behavior and performance characteristics are also discussed observed. The programs will be implemented, as well as local and carefully selected input values. Often the contribution of a number of program may be impractical for large and for practical reasons, a finite subset of the set of input can be selected.
Testing, we find some representative of the behavior of the program and conclude the quality of the system. A careful selection of finite test set is important to reach a reliable conclusion.
By performing static analysis and dynamic testers to identify as many errors as possible so that these bugs are fixed at an early stage of software development. Static analysis and dynamic analysis are complementary in nature, and for better efficiency, both must be performed repeatedly and alternately.
Tests commonly used two methods to test a software product.
1.CHECK: This kind of activity helps us to evaluate a software system by determining if the product of a given development phase satisfy the requirements before the start of this phase. A product may be a different specification requirements, design specifications, code, user manual, or even the final product. Activities to verify the accuracy of development activities called for verification.
2. Validation: Activities of this nature help us to confirm that a product meets its intended use. Validation activities are intended to confirm that the product meets customer expectations. Validation activities focuses on the final product is rigorously tested in terms of the customer. Validation determines whether the product meets the general expectations of users.
No comments:
Post a Comment