ISO 9126 - Software Quality Risks

1. Functionality
1.1. Suitability
1.2. Accuracy
1.3. Interoperability
1.4. Compliance
1.5. Security
2. Reliability
2.1. Maturity
2.2. Recoverability
2.3. Fault Tolerance
3. Usability
3.1. Learn ability
3.2. Understandability
3.3. Operability
4. Efficiency
4.1. Time Behavior
4.2. Resource Behavior
5. Maintainability
5.1. Stability
5.2. Analyzability
5.3. Changeability
5.4. Testability
6. Portability
6.1. Install ability
6.2. Replacibility
6.3. Adaptability
6.4. Conformance (e.g. conformance to particular db standard)

Comments

Post a Comment

Popular posts from this blog

How to Report Bugs Effectively

As per defined in wikipedia – “A software bug is the common term used to describe an error, flaw, mistake, failure, or fault in a computer program or system that produces an incorrect or unexpected result, or causes it to behave in unintended ways. Most bugs arise from mistakes and errors made by people in either a program's source code or its design, and a few are caused by compilers producing incorrect code. Reports detailing bugs in a program are commonly known as bug reports, fault reports, problem reports, trouble reports, change requests, and so forth.” There might be many fields (information) need to be filled while reporting a bug.  The number of fields, mandatory fields, optional fields etc. differs from team to team.  But few bare minimum fields that are required during reporting a bug in almost all teams are as follows: Title Description Steps to Repro Expectation Severity / Priority Most of the time, testers go and try to provide these information in hurry,...
Read more

Refactoring Methods

Refactoring List Composing Methods Properly Extract Method Turn the fragment into a method whose name explains the purpose of the method Benefit is that original method become shorter and easier to comprehend Inline Method A method's body is just as clear as its name Put the method's body into the body of its callers and remove the method Inline Temp You have a temp that is assigned to once with a simple expression and the temp is getting in the way of other refactorings Replace all references to that temp with the expression Replace Temp with Query You are using a temporary variable to hold the result of an expression Extract the expression into a method. Replace all references to the temp with the expression. The new method can then be used in other methods By replaceing the temp with a query method, any method in the class can get the information cleanly Introduce Explaining Variable Put the result of the complicated expression, or parts of the...
Read more

Mobile Performance Testing Checklist

Mobile Performance Testing Checklist Smartphones & tablets are the reality and a large mass of people are moving to use it for bussiness applications, entertainment, social networking, healthcare applications etc. It's mandatory for businesses to assess performance of mobile apps before releasing it to public. Responsiveness of mobile apps is one of the big factor for organization to capture the market. Below are list of things to consider specific to mobile performance testing. Have you considered- Client side considerations Application performance against different mobile phones in the market? CPU utilization Memory utilization I/O Cache size availability Rendering (2D / 3D) Application performance against different mobile phones & browsers in the market? JS Engine processing Number of threads executing the requests Memory leakage by the application? Battery consumption by the application? Internet data usage by the a...
Read more