- Measurements are collected as per their definition at defined points as mentioned in Organization Metrics File
- Data is collected and compiled by using Project Summary, Help Desk, eRMS, Analysis Reports, Peer Review Analysis Reports etc
- Verification of the measurement data is done independently to check completeness, integrity, accuracy by SQA & SEG for the data that they provide to each other
- Once the data is collected will be assessed independently by QE
- Project may consider additional metrics to better manage their project
- Data should be available for use only by appropriate groups and personnel.
Showing posts with label Integrity. Show all posts
Showing posts with label Integrity. Show all posts
Monday, June 15, 2009
How data is collected for metrics and measurements?
There are some ways for metrics and measurements for data
Labels:
accuracy SQA,
Analysis Reports,
completeness,
eRMS,
helpdesk,
Integrity,
measure,
measurement,
metric,
metrics,
organization metrics files,
peer reviews,
Project Summary,
QE,
SEG,
verification
Monday, April 27, 2009
What are test case types?
Test Case Types
Functional Test Cases:
Functional test cases are used to test screen level functionalities of the product. For field level validation, testers can either use GUI review checklist embedded within the test case or can develop separate field level validation test cases. Functional test cases along with field level test cases are executed before business test cases in order to test the functionalities of the individual screens thoroughly. Functional test cases are based on the FS as the primary source but can also be based on prototypes (if available) or the design document.Field Validation Test Cases:
Field level test cases are developed using AF TOD to validate individual fields on a screen using a black box testing methodology. DB verification can also be the purpose of such test cases.Business test cases:
Business test cases are used to test the business scenarios and require extensive knowledge of the requirements and business process flow of the application. Business test cases are normally based on RS and business flows as the primary source.Performance test cases:
Performance test cases are developed to determine/measure the system performance under the particular workload. It serves to validate and verify resource usage with volume of data. Performance test cases are developed to measure and analyzed application response time at the following level- Application level
- Database level
Recoverability test cases: Recovery test cases are developed to conduct reasonable test to ensure that the implemented security measures function properly and how well the software is able to recover from crashes, hardware failures and other similar problems
Security test cases:
Security Test cases are developed to determine that an Information system protects data and maintain functionality as intended. Following basic measures should be covered in security test cases- Confidentiality
- Integrity
- Authentication
- Authorization
Replication test cases: Replication Test cases are developed to verify the replication of data across the software components & validate the Data Integrity, Consistency and accuracy.
Labels:
Application level,
Authentication,
Authorization,
Confidentiality,
database level,
defect test cases,
Field Validation,
Functional,
Integrity,
performance,
Replication,
Security,
test case types
Tuesday, March 24, 2009
what are quality attributes and quality factors?
There are three types of quality attributes:
1.Product Operations:
2.Product Revision:
3.Product Transition:
*I have explained for understandability of the reader
- Product Operations
- Product Revision
- Product Transition
1.Product Operations:
- Correctness: does it do what i want?
- Reliability: does it do accurately all the time?
- Efficiency: will it run on my machine as well as it can?
- Integrity: is it secure?
- Usability: can i run it?
2.Product Revision:
- Maintainability: can i fix it?
- Flexibility: can i change it?
- Testability: can i test it?
3.Product Transition:
- Portability: will i be able to use on another machine?
- Reusability:will i be able to reuse some of the software?
- Interoperability: will i be able to interface it with another machine?
*I have explained for understandability of the reader
Labels:
correctness,
efficiency,
flexibility,
Integrity,
interoperabilty,
maintainability,
Operations,
portability,
Product,
reliability,
resuability,
revisions,
testability,
transition,
Usability
Subscribe to:
Posts (Atom)